Skip to content

Commit 82a1d44

Browse files
Merge pull request #13190 from github/updates
Added 2023/04/2023-04-04-keil.md
2 parents 22e759e + 3bf0119 commit 82a1d44

File tree

1 file changed

+65
-0
lines changed

1 file changed

+65
-0
lines changed

2023/04/2023-04-04-keil.md

Lines changed: 65 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,65 @@
1+
Before disabling any content in relation to this takedown notice, GitHub
2+
- contacted the owners of some or all of the affected repositories to give them an opportunity to [make changes](https://docs.github.com/en/github/site-policy/dmca-takedown-policy#a-how-does-this-actually-work).
3+
- provided information on how to [submit a DMCA Counter Notice](https://docs.github.com/en/articles/guide-to-submitting-a-dmca-counter-notice).
4+
5+
To learn about when and why GitHub may process some notices this way, please visit our [README](https://github.com/github/dmca/blob/master/README.md#anatomy-of-a-takedown-notice).
6+
7+
---
8+
9+
**Are you the copyright holder or authorized to act on the copyright owner's behalf?**
10+
11+
Yes, I am authorized to act on the copyright owner's behalf.
12+
13+
**Are you submitting a revised DMCA notice after GitHub Trust & Safety requested you make changes to your original notice?**
14+
15+
No
16+
17+
**Does your claim involve content on GitHub or npm.js?**
18+
19+
GitHub
20+
21+
**Please describe the nature of your copyright ownership or authorization to act on the owner's behalf.**
22+
23+
I am an [private] for the copyright owner. Software and printed materials are being posted on github without authorization.
24+
25+
**Please provide a detailed description of the original copyrighted work that has allegedly been infringed. If possible, include a URL to where it is posted online.**
26+
27+
Go to http://www.keil.com/dd2/pack. Scroll down to "Keil" and find the first downloadable file under "Keil.V2M-MPS2_CMx_BSP.1.8.0.pack". The infringing content is the startup_CMSDK_CM3.s file is part of this CMSIS-Pack.
28+
29+
**What files should be taken down? Please provide URLs for each file, or if the entire repository, the repository’s URL.**
30+
31+
https://github.com/tianjin95/CortexM3_SoC/blob/master/SOFTWARE/startup_CMSDK_CM3.s
32+
33+
**Do you claim to have any technological measures in place to control access to your copyrighted content? Please see our <a href="https://docs.github.com/articles/guide-to-submitting-a-dmca-takedown-notice#complaints-about-anti-circumvention-technology">Complaints about Anti-Circumvention Technology</a> if you are unsure.**
34+
35+
No
36+
37+
**<a href="https://docs.github.com/articles/dmca-takedown-policy#b-what-about-forks-or-whats-a-fork">Have you searched for any forks</a> of the allegedly infringing files or repositories? Each fork is a distinct repository and must be identified separately if you believe it is infringing and wish to have it taken down.**
38+
39+
Yes. The forks of which we are aware have since been taken down.
40+
41+
**Is the work licensed under an open source license?**
42+
43+
No
44+
45+
**What would be the best solution for the alleged infringement?**
46+
47+
Reported content must be removed
48+
49+
**Do you have the alleged infringer’s contact information? If so, please provide it.**
50+
51+
**I have a good faith belief that use of the copyrighted materials described above on the infringing web pages is not authorized by the copyright owner, or its agent, or the law.**
52+
53+
**I have taken <a href="https://www.lumendatabase.org/topics/22">fair use</a> into consideration.**
54+
55+
**I swear, under penalty of perjury, that the information in this notification is accurate and that I am the copyright owner, or am authorized to act on behalf of the owner, of an exclusive right that is allegedly infringed.**
56+
57+
**I have read and understand GitHub's <a href="https://docs.github.com/articles/guide-to-submitting-a-dmca-takedown-notice/">Guide to Submitting a DMCA Takedown Notice</a>.**
58+
59+
**So that we can get back to you, please provide either your telephone number or physical address.**
60+
61+
[private]
62+
63+
**Please type your full legal name below to sign this request.**
64+
65+
[private]

0 commit comments

Comments
 (0)