ecdsa generic algorithm #709
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I think you're supposed to send these to the mailing list. |
|
Hi @SauloAlessandre! Thanks for your contribution to the Linux kernel! Linux kernel development happens on mailing lists, rather than on GitHub - this GitHub repository is a read-only mirror that isn't used for accepting contributions. So that your change can become part of Linux, please email it to us as a patch. Sending patches isn't quite as simple as sending a pull request, but fortunately it is a well documented process. Here's what to do:
How do I format my contribution?The Linux kernel community is notoriously picky about how contributions are formatted and sent. Fortunately, they have documented their expectations. Firstly, all contributions need to be formatted as patches. A patch is a plain text document showing the change you want to make to the code, and documenting why it is a good idea. You can create patches with Secondly, patches need 'commit messages', which is the human-friendly documentation explaining what the change is and why it's necessary. Thirdly, changes have some technical requirements. There is a Linux kernel coding style, and there are licensing requirements you need to comply with. Both of these are documented in the Submitting Patches documentation that is part of the kernel. Note that you will almost certainly have to modify your existing git commits to satisfy these requirements. Don't worry: there are many guides on the internet for doing this. Where do I send my contribution?The Linux kernel is composed of a number of subsystems. These subsystems are maintained by different people, and have different mailing lists where they discuss proposed changes. If you don't already know what subsystem your change belongs to, the
Make sure that your list of recipients includes a mailing list. If you can't find a more specific mailing list, then LKML - the Linux Kernel Mailing List - is the place to send your patches. It's not usually necessary to subscribe to the mailing list before you send the patches, but if you're interested in kernel development, subscribing to a subsystem mailing list is a good idea. (At this point, you probably don't need to subscribe to LKML - it is a very high traffic list with about a thousand messages per day, which is often not useful for beginners.) How do I send my contribution?Use For more information about using How do I get help if I'm stuck?Firstly, don't get discouraged! There are an enormous number of resources on the internet, and many kernel developers who would like to see you succeed. Many issues - especially about how to use certain tools - can be resolved by using your favourite internet search engine. If you can't find an answer, there are a few places you can turn:
If you get really, really stuck, you could try the owners of this bot, @daxtens and @ajdlinux. Please be aware that we do have full-time jobs, so we are almost certainly the slowest way to get answers! I sent my patch - now what?You wait. You can check that your email has been received by checking the mailing list archives for the mailing list you sent your patch to. Messages may not be received instantly, so be patient. Kernel developers are generally very busy people, so it may take a few weeks before your patch is looked at. Then, you keep waiting. Three things may happen:
Further information
Happy hacking! This message was posted by a bot - if you have any questions or suggestions, please talk to my owners, @ajdlinux and @daxtens, or raise an issue at https://github.com/ajdlinux/KernelPRBot. |
|
Thanks James!
I tryed send email to the mainteners [Herbert Xu at <
herbert@gondor.apana.org.au> and David S. Miller at <davem@davemloft.net>]
about 2 weeks ago, but the email for Herbert is returning.
I will wait for David response.
Best regards!
Em qui, 15 de ago de 2019 às 00:53, KernelPRBot <notifications@github.com>
escreveu:
… Hi @SauloAlessandre <https://github.com/SauloAlessandre>!
Thanks for your contribution to the Linux kernel!
Linux kernel development happens on mailing lists, rather than on GitHub -
this GitHub repository is a read-only mirror that isn't used for accepting
contributions. So that your change can become part of Linux, please email
it to us as a patch.
Sending patches isn't quite as simple as sending a pull request, but
fortunately it is a well documented process.
Here's what to do:
- Format your contribution according to kernel requirements
- Decide who to send your contribution to
- Set up your system to send your contribution as an email
- Send your contribution and wait for feedback
How do I format my contribution?
The Linux kernel community is notoriously picky about how contributions
are formatted and sent. Fortunately, they have documented their
expectations.
Firstly, all contributions need to be formatted as patches. A patch is a
plain text document showing the change you want to make to the code, and
documenting why it is a good idea.
You can create patches with git format-patch
<https://git-scm.com/docs/git-format-patch>.
Secondly, patches need 'commit messages', which is the human-friendly
documentation explaining what the change is and why it's necessary.
Thirdly, changes have some technical requirements. There is a Linux kernel
coding style, and there are licensing requirements you need to comply with.
Both of these are documented in the Submitting Patches documentation
<https://kernel.org/doc/html/latest/process/submitting-patches.html> that
is part of the kernel.
Note that you will almost certainly have to modify your existing git
commits to satisfy these requirements. Don't worry: there are many guides
on the internet for doing this.
Where do I send my contribution?
The Linux kernel is composed of a number of subsystems. These subsystems
are maintained by different people, and have different mailing lists where
they discuss proposed changes.
If you don't already know what subsystem your change belongs to, the
get_maintainer.pl
<https://github.com/torvalds/linux/blob/master/scripts/get_maintainer.pl>
script in the kernel source can help you.
get_maintainer.pl will take the patch or patches you created in the
previous step, and tell you who is responsible for them, and what mailing
lists are used. You can also take a look at the MAINTAINERS
<https://www.kernel.org/doc/linux/MAINTAINERS> file by hand.
Make sure that your list of recipients includes a mailing list. If you
can't find a more specific mailing list, then LKML - the Linux Kernel
Mailing List <http://vger.kernel.org/vger-lists.html#linux-kernel> - is
the place to send your patches.
It's not usually necessary to subscribe to the mailing list before you
send the patches, but if you're interested in kernel development,
subscribing to a subsystem mailing list is a good idea. (At this point, you
probably don't need to subscribe to LKML - it is a very high traffic list
with about a thousand messages per day, which is often not useful for
beginners.)
How do I send my contribution?
Use git send-email <https://git-scm.com/docs/git-send-email>, which will
ensure that your patches are formatted in the standard manner. In order to
use git send-email, you'll need to configure git to use your SMTP email
server.
For more information about using git send-email, look at the Git
documentation <https://git-scm.com/docs/git-send-email> or type git help
send-email. There are a number of useful guides and tutorials about git
send-email that can be found on the internet.
How do I get help if I'm stuck?
Firstly, don't get discouraged! There are an enormous number of resources
on the internet, and many kernel developers who would like to see you
succeed.
Many issues - especially about how to use certain tools - can be resolved
by using your favourite internet search engine.
If you can't find an answer, there are a few places you can turn:
- Kernel Newbies <https://kernelnewbies.org> - this website contains a
lot of useful resources for new kernel developers.
- The kernel documentation <https://www.kernel.org/doc/html/latest/> -
see also the Documentation directory in the kernel tree.
If you get really, really stuck, you could try the owners of this bot,
@daxtens <https://github.com/daxtens> and @ajdlinux
<https://github.com/ajdlinux>. Please be aware that we do have full-time
jobs, so we are almost certainly the slowest way to get answers!
I sent my patch - now what?
You wait.
You can check that your email has been received by checking the mailing
list archives for the mailing list you sent your patch to. Messages may not
be received instantly, so be patient. Kernel developers are generally very
busy people, so it may take a few weeks before your patch is looked at.
Then, you keep waiting. Three things may happen:
- You might get a response to your email. Often these will be
comments, which may require you to make changes to your patch, or explain
why your way is the best way. You should respond to these comments, and you
may need to submit another revision of your patch to address the issues
raised.
- Your patch might be merged into the subsystem tree. Code that
becomes part of Linux isn't merged into the main repository straight away -
it first goes into the subsystem tree, which is managed by the subsystem
maintainer. It is then batched up with a number of other changes sent to
Linus for inclusion. (This process is described in some detail in the
kernel development process guide
<https://www.kernel.org/doc/html/latest/process/development-process.html>
).
- Your patch might be ignored completely. This happens sometimes -
don't take it personally. Here's what to do:
- Wait a bit more - patches often take several weeks to get a
response; more if they were sent at a busy time.
- Kernel developers often silently ignore patches that break the
rules. Check for obvious violations of the Submitting Patches guidelines,
the style guidelines, and any other documentation you can find about your
subsystem. Check that you're sending your patch to the right place.
- Try again later. When you resend it, don't add angry commentary,
as that will get your patch ignored. It might also get you silently
blacklisted.
Further information
- Working with the kernel development community
<https://www.kernel.org/doc/html/latest/process/index.html> - the
official documentation for new kernel contributors
Happy hacking!
*This message was posted by a bot - if you have any questions or
suggestions, please talk to my owners, @ajdlinux
<https://github.com/ajdlinux> and @daxtens <https://github.com/daxtens>, or
raise an issue at https://github.com/ajdlinux/KernelPRBot
<https://github.com/ajdlinux/KernelPRBot>.*
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#709?email_source=notifications&email_token=ACD5RVEDCHDQYL43ME44T73QETHKLA5CNFSM4IK2UA32YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4KYBLY#issuecomment-521502895>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACD5RVFL7CBZP5ZN2WM7ULLQETHKLANCNFSM4IK2UA3Q>
.
--
[]'s
-----
*Saulo Alessandre*
|
fengguang
pushed a commit
to 0day-ci/linux
that referenced
this pull request
Mar 15, 2021
This commit fixes the following checkpatch.pl errors:
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
#70: FILE: ./hal/hal_btcoex.c:70:
+static u8 halbtcoutsrc_IsBtCoexistAvailable(struct BTC_COEXIST * pBtCoexist)
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
torvalds#104: FILE: ./hal/hal_btcoex.c:104:
+static void halbtcoutsrc_LeaveLps(struct BTC_COEXIST * pBtCoexist)
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
torvalds#117: FILE: ./hal/hal_btcoex.c:117:
+static void halbtcoutsrc_EnterLps(struct BTC_COEXIST * pBtCoexist)
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
torvalds#130: FILE: ./hal/hal_btcoex.c:130:
+static void halbtcoutsrc_NormalLps(struct BTC_COEXIST * pBtCoexist)
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
torvalds#152: FILE: ./hal/hal_btcoex.c:152:
+static void halbtcoutsrc_LeaveLowPower(struct BTC_COEXIST * pBtCoexist)
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
torvalds#187: FILE: ./hal/hal_btcoex.c:187:
+static void halbtcoutsrc_NormalLowPower(struct BTC_COEXIST * pBtCoexist)
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
torvalds#196: FILE: ./hal/hal_btcoex.c:196:
+static void halbtcoutsrc_DisableLowPower(struct BTC_COEXIST * pBtCoexist, u8 bLowPwrDisable)
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
torvalds#205: FILE: ./hal/hal_btcoex.c:205:
+static void halbtcoutsrc_AggregationCheck(struct BTC_COEXIST * pBtCoexist)
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
torvalds#283: FILE: ./hal/hal_btcoex.c:283:
+static u32 halbtcoutsrc_GetWifiLinkStatus(struct BTC_COEXIST * pBtCoexist)
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
torvalds#311: FILE: ./hal/hal_btcoex.c:311:
+static u32 halbtcoutsrc_GetBtPatchVer(struct BTC_COEXIST * pBtCoexist)
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
torvalds#342: FILE: ./hal/hal_btcoex.c:342:
+ struct BTC_COEXIST * pBtCoexist;
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
torvalds#448: FILE: ./hal/hal_btcoex.c:448:
+ struct RT_LINK_DETECT_T * plinkinfo;
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
torvalds#510: FILE: ./hal/hal_btcoex.c:510:
+ struct BTC_COEXIST * pBtCoexist;
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
torvalds#645: FILE: ./hal/hal_btcoex.c:645:
+static void halbtcoutsrc_DisplayFwPwrModeCmd(struct BTC_COEXIST * pBtCoexist)
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
torvalds#661: FILE: ./hal/hal_btcoex.c:661:
+ struct BTC_COEXIST * pBtCoexist;
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
torvalds#673: FILE: ./hal/hal_btcoex.c:673:
+ struct BTC_COEXIST * pBtCoexist;
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
torvalds#685: FILE: ./hal/hal_btcoex.c:685:
+ struct BTC_COEXIST * pBtCoexist;
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
torvalds#697: FILE: ./hal/hal_btcoex.c:697:
+ struct BTC_COEXIST * pBtCoexist;
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
torvalds#709: FILE: ./hal/hal_btcoex.c:709:
+ struct BTC_COEXIST * pBtCoexist;
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
torvalds#749: FILE: ./hal/hal_btcoex.c:749:
+ struct BTC_COEXIST * pBtCoexist;
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
torvalds#761: FILE: ./hal/hal_btcoex.c:761:
+ struct BTC_COEXIST * pBtCoexist = (struct BTC_COEXIST *)pBtcContext;
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
torvalds#772: FILE: ./hal/hal_btcoex.c:772:
+ struct BTC_COEXIST * pBtCoexist;
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
#785: FILE: ./hal/hal_btcoex.c:785:
+ struct BTC_COEXIST * pBtCoexist;
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
torvalds#797: FILE: ./hal/hal_btcoex.c:797:
+ struct BTC_COEXIST * pBtCoexist;
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
torvalds#809: FILE: ./hal/hal_btcoex.c:809:
+ struct BTC_COEXIST * pBtCoexist;
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
torvalds#821: FILE: ./hal/hal_btcoex.c:821:
+ struct BTC_COEXIST * pBtCoexist;
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
torvalds#857: FILE: ./hal/hal_btcoex.c:857:
+ struct BTC_COEXIST * pBtCoexist;
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
torvalds#869: FILE: ./hal/hal_btcoex.c:869:
+ struct BTC_COEXIST * pBtCoexist;
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
torvalds#891: FILE: ./hal/hal_btcoex.c:891:
+ struct BTC_COEXIST * pBtCoexist = &GLBtCoexist;
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
torvalds#917: FILE: ./hal/hal_btcoex.c:917:
+ struct BTC_COEXIST * pBtCoexist;
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
torvalds#963: FILE: ./hal/hal_btcoex.c:963:
+void EXhalbtcoutsrc_PowerOnSetting(struct BTC_COEXIST * pBtCoexist)
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
torvalds#975: FILE: ./hal/hal_btcoex.c:975:
+void EXhalbtcoutsrc_InitHwConfig(struct BTC_COEXIST * pBtCoexist, u8 bWifiOnly)
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
torvalds#988: FILE: ./hal/hal_btcoex.c:988:
+void EXhalbtcoutsrc_InitCoexDm(struct BTC_COEXIST * pBtCoexist)
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
torvalds#1003: FILE: ./hal/hal_btcoex.c:1003:
+void EXhalbtcoutsrc_IpsNotify(struct BTC_COEXIST * pBtCoexist, u8 type)
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
torvalds#1030: FILE: ./hal/hal_btcoex.c:1030:
+void EXhalbtcoutsrc_LpsNotify(struct BTC_COEXIST * pBtCoexist, u8 type)
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
torvalds#1053: FILE: ./hal/hal_btcoex.c:1053:
+void EXhalbtcoutsrc_ScanNotify(struct BTC_COEXIST * pBtCoexist, u8 type)
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
#1082: FILE: ./hal/hal_btcoex.c:1082:
+void EXhalbtcoutsrc_ConnectNotify(struct BTC_COEXIST * pBtCoexist, u8 action)
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
#1108: FILE: ./hal/hal_btcoex.c:1108:
+void EXhalbtcoutsrc_MediaStatusNotify(struct BTC_COEXIST * pBtCoexist, enum RT_MEDIA_STATUS mediaStatus)
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
#1135: FILE: ./hal/hal_btcoex.c:1135:
+void EXhalbtcoutsrc_SpecialPacketNotify(struct BTC_COEXIST * pBtCoexist, u8 pktType)
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
#1166: FILE: ./hal/hal_btcoex.c:1166:
+void EXhalbtcoutsrc_BtInfoNotify(struct BTC_COEXIST * pBtCoexist, u8 *tmpBuf, u8 length)
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
#1184: FILE: ./hal/hal_btcoex.c:1184:
+void EXhalbtcoutsrc_HaltNotify(struct BTC_COEXIST * pBtCoexist)
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
#1197: FILE: ./hal/hal_btcoex.c:1197:
+void EXhalbtcoutsrc_PnpNotify(struct BTC_COEXIST * pBtCoexist, u8 pnpState)
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
#1213: FILE: ./hal/hal_btcoex.c:1213:
+void EXhalbtcoutsrc_Periodical(struct BTC_COEXIST * pBtCoexist)
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
#1258: FILE: ./hal/hal_btcoex.c:1258:
+void EXhalbtcoutsrc_DisplayBtCoexInfo(struct BTC_COEXIST * pBtCoexist)
Signed-off-by: Marco Cesati <marcocesati@gmail.com>
fengguang
pushed a commit
to 0day-ci/linux
that referenced
this pull request
Mar 16, 2021
This commit fixes the following checkpatch.pl errors:
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
#70: FILE: ./hal/hal_btcoex.c:70:
+static u8 halbtcoutsrc_IsBtCoexistAvailable(struct BTC_COEXIST * pBtCoexist)
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
torvalds#104: FILE: ./hal/hal_btcoex.c:104:
+static void halbtcoutsrc_LeaveLps(struct BTC_COEXIST * pBtCoexist)
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
torvalds#117: FILE: ./hal/hal_btcoex.c:117:
+static void halbtcoutsrc_EnterLps(struct BTC_COEXIST * pBtCoexist)
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
torvalds#130: FILE: ./hal/hal_btcoex.c:130:
+static void halbtcoutsrc_NormalLps(struct BTC_COEXIST * pBtCoexist)
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
torvalds#152: FILE: ./hal/hal_btcoex.c:152:
+static void halbtcoutsrc_LeaveLowPower(struct BTC_COEXIST * pBtCoexist)
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
torvalds#187: FILE: ./hal/hal_btcoex.c:187:
+static void halbtcoutsrc_NormalLowPower(struct BTC_COEXIST * pBtCoexist)
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
torvalds#196: FILE: ./hal/hal_btcoex.c:196:
+static void halbtcoutsrc_DisableLowPower(struct BTC_COEXIST * pBtCoexist, u8 bLowPwrDisable)
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
torvalds#205: FILE: ./hal/hal_btcoex.c:205:
+static void halbtcoutsrc_AggregationCheck(struct BTC_COEXIST * pBtCoexist)
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
torvalds#283: FILE: ./hal/hal_btcoex.c:283:
+static u32 halbtcoutsrc_GetWifiLinkStatus(struct BTC_COEXIST * pBtCoexist)
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
torvalds#311: FILE: ./hal/hal_btcoex.c:311:
+static u32 halbtcoutsrc_GetBtPatchVer(struct BTC_COEXIST * pBtCoexist)
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
torvalds#342: FILE: ./hal/hal_btcoex.c:342:
+ struct BTC_COEXIST * pBtCoexist;
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
torvalds#448: FILE: ./hal/hal_btcoex.c:448:
+ struct RT_LINK_DETECT_T * plinkinfo;
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
torvalds#510: FILE: ./hal/hal_btcoex.c:510:
+ struct BTC_COEXIST * pBtCoexist;
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
torvalds#645: FILE: ./hal/hal_btcoex.c:645:
+static void halbtcoutsrc_DisplayFwPwrModeCmd(struct BTC_COEXIST * pBtCoexist)
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
torvalds#661: FILE: ./hal/hal_btcoex.c:661:
+ struct BTC_COEXIST * pBtCoexist;
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
torvalds#673: FILE: ./hal/hal_btcoex.c:673:
+ struct BTC_COEXIST * pBtCoexist;
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
torvalds#685: FILE: ./hal/hal_btcoex.c:685:
+ struct BTC_COEXIST * pBtCoexist;
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
torvalds#697: FILE: ./hal/hal_btcoex.c:697:
+ struct BTC_COEXIST * pBtCoexist;
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
torvalds#709: FILE: ./hal/hal_btcoex.c:709:
+ struct BTC_COEXIST * pBtCoexist;
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
torvalds#749: FILE: ./hal/hal_btcoex.c:749:
+ struct BTC_COEXIST * pBtCoexist;
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
torvalds#761: FILE: ./hal/hal_btcoex.c:761:
+ struct BTC_COEXIST * pBtCoexist = (struct BTC_COEXIST *)pBtcContext;
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
torvalds#772: FILE: ./hal/hal_btcoex.c:772:
+ struct BTC_COEXIST * pBtCoexist;
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
#785: FILE: ./hal/hal_btcoex.c:785:
+ struct BTC_COEXIST * pBtCoexist;
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
torvalds#797: FILE: ./hal/hal_btcoex.c:797:
+ struct BTC_COEXIST * pBtCoexist;
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
torvalds#809: FILE: ./hal/hal_btcoex.c:809:
+ struct BTC_COEXIST * pBtCoexist;
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
torvalds#821: FILE: ./hal/hal_btcoex.c:821:
+ struct BTC_COEXIST * pBtCoexist;
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
torvalds#857: FILE: ./hal/hal_btcoex.c:857:
+ struct BTC_COEXIST * pBtCoexist;
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
torvalds#869: FILE: ./hal/hal_btcoex.c:869:
+ struct BTC_COEXIST * pBtCoexist;
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
torvalds#891: FILE: ./hal/hal_btcoex.c:891:
+ struct BTC_COEXIST * pBtCoexist = &GLBtCoexist;
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
torvalds#917: FILE: ./hal/hal_btcoex.c:917:
+ struct BTC_COEXIST * pBtCoexist;
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
torvalds#963: FILE: ./hal/hal_btcoex.c:963:
+void EXhalbtcoutsrc_PowerOnSetting(struct BTC_COEXIST * pBtCoexist)
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
torvalds#975: FILE: ./hal/hal_btcoex.c:975:
+void EXhalbtcoutsrc_InitHwConfig(struct BTC_COEXIST * pBtCoexist, u8 bWifiOnly)
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
torvalds#988: FILE: ./hal/hal_btcoex.c:988:
+void EXhalbtcoutsrc_InitCoexDm(struct BTC_COEXIST * pBtCoexist)
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
torvalds#1003: FILE: ./hal/hal_btcoex.c:1003:
+void EXhalbtcoutsrc_IpsNotify(struct BTC_COEXIST * pBtCoexist, u8 type)
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
torvalds#1030: FILE: ./hal/hal_btcoex.c:1030:
+void EXhalbtcoutsrc_LpsNotify(struct BTC_COEXIST * pBtCoexist, u8 type)
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
torvalds#1053: FILE: ./hal/hal_btcoex.c:1053:
+void EXhalbtcoutsrc_ScanNotify(struct BTC_COEXIST * pBtCoexist, u8 type)
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
#1082: FILE: ./hal/hal_btcoex.c:1082:
+void EXhalbtcoutsrc_ConnectNotify(struct BTC_COEXIST * pBtCoexist, u8 action)
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
#1108: FILE: ./hal/hal_btcoex.c:1108:
+void EXhalbtcoutsrc_MediaStatusNotify(struct BTC_COEXIST * pBtCoexist, enum RT_MEDIA_STATUS mediaStatus)
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
#1135: FILE: ./hal/hal_btcoex.c:1135:
+void EXhalbtcoutsrc_SpecialPacketNotify(struct BTC_COEXIST * pBtCoexist, u8 pktType)
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
#1166: FILE: ./hal/hal_btcoex.c:1166:
+void EXhalbtcoutsrc_BtInfoNotify(struct BTC_COEXIST * pBtCoexist, u8 *tmpBuf, u8 length)
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
#1184: FILE: ./hal/hal_btcoex.c:1184:
+void EXhalbtcoutsrc_HaltNotify(struct BTC_COEXIST * pBtCoexist)
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
#1197: FILE: ./hal/hal_btcoex.c:1197:
+void EXhalbtcoutsrc_PnpNotify(struct BTC_COEXIST * pBtCoexist, u8 pnpState)
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
#1213: FILE: ./hal/hal_btcoex.c:1213:
+void EXhalbtcoutsrc_Periodical(struct BTC_COEXIST * pBtCoexist)
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
#1258: FILE: ./hal/hal_btcoex.c:1258:
+void EXhalbtcoutsrc_DisplayBtCoexInfo(struct BTC_COEXIST * pBtCoexist)
Reviewed-by: Dan Carpenter <dan.carpenter@oracle.com>
Signed-off-by: Marco Cesati <marcocesati@gmail.com>
Link: https://lore.kernel.org/r/20210315170618.2566-18-marcocesati@gmail.com
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
ojeda
pushed a commit
to ojeda/linux
that referenced
this pull request
Mar 16, 2022
rust: rename `FileOperations::Wrapper` to `FileOperations::Data`
gatieme
pushed a commit
to gatieme/linux
that referenced
this pull request
Nov 24, 2022
ANBZ: torvalds#709 commit ebe48d3 upstream. The maximum message size that can be send is bigger than the maximum site that skb_page_frag_refill can allocate. So it is possible to write beyond the allocated buffer. Fix this by doing a fallback to COW in that case. v2: Avoid get get_order() costs as suggested by Linus Torvalds. Fixes: cac2661 ("esp4: Avoid skb_cow_data whenever possible") Fixes: 03e2a30 ("esp6: Avoid skb_cow_data whenever possible") Reported-by: valis <sec@valis.email> Signed-off-by: Steffen Klassert <steffen.klassert@secunet.com> Fixes: CVE-2022-0886 Signed-off-by: Xuan Zhuo <xuanzhuo@linux.alibaba.com> Acked-by: Dust Li <dust.li@linux.alibaba.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Follow the ECDSA generic algorithm for linux kernel 5.3. This is part of work to signed modules with nist ECDSA p256 and p384.