linux-kernel - Re: [PATCH] staging: rtl8192u: Removing multiple blank lines

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:   Sat, 11 Feb 2017 09:34:12 +0530
From:   SIMRAN SINGHAL <singhalsimran0@...il.com>
To:     Greg KH <gregkh@...uxfoundation.org>
Cc:     linux-kernel@...r.kernel.org, devel@...verdev.osuosl.org
Subject: Re: [PATCH] staging: rtl8192u: Removing multiple blank lines

Multiple patches ...?
Can you please clarify what all patches you are including in "Multiple Patches".

And the Order you should go for is the order in which I submitted them.

On Sat, Feb 11, 2017 at 7:48 AM, SIMRAN SINGHAL
<singhalsimran0@...il.com> wrote:
> Multiple patches ...?
> Can you please clarify what all patches you are including in "Multiple
> Patches".
>
> And the Order you should go for is the order in which I submitted them.
>
> On Feb 10, 2017 19:34, "Greg KH" <gregkh@...uxfoundation.org> wrote:
>
> On Thu, Feb 09, 2017 at 06:02:12PM +0530, simran singhal wrote:
>> This patch fixes the checkpatch warning by removing multiple blank
>> lines.
>> CHECK: Please don't use multiple blank lines
>>
>> Signed-off-by: simran singhal <singhalsimran0@...il.com>
>> ---
>>  drivers/staging/rtl8192u/ieee80211/ieee80211_crypt_ccmp.c | 12
>> ------------
>>  1 file changed, 12 deletions(-)
>
> Hi,
>
> This is the friendly patch-bot of Greg Kroah-Hartman.  You have sent him
> a patch that has triggered this response.  He used to manually respond
> to these common problems, but in order to save his sanity (he kept
> writing the same thing over and over, yet to different people), I was
> created.  Hopefully you will not take offence and will fix the problem
> in your patch and resubmit it so that it can be accepted into the Linux
> kernel tree.
>
> You are receiving this message because of the following common error(s)
> as indicated below:
>
> - You sent multiple patches, yet no indication of which ones should be
>   applied in which order.  Greg could just guess, but if you are
>   receiving this email, he guessed wrong and the patches didn't apply.
>   Please read the section entitled "The canonical patch format" in the
>   kernel file, Documentation/SubmittingPatches for a description of how
>   to do this so that Greg has a chance to apply these correctly.
>
> If you wish to discuss this problem further, or you have questions about
> how to resolve this issue, please feel free to respond to this email and
> Greg will reply once he has dug out from the pending patches received
> from other developers.
>
> thanks,
>
> greg k-h's patch email bot
>
>