linux-kernel - Fwd: [PATCH] Staging: bcm2835-audio: bcm2835_ctl.c: Fixed a comment coding style issue

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>] [day] [month] [year] [list]

Date:   Thu, 18 May 2017 21:10:03 +0530
From:   srishti sharma <srishtishar@...il.com>
To:     devel@...verdev.osuosl.org,
        Florian Fainelli <f.fainelli@...il.com>, sbranden@...adcom.com,
        Stephen Warren <swarren@...dotorg.org>, rjui@...adcom.com,
        lee@...nel.org, Victor Vaschenko <vicmos89@...il.com>,
        linux-kernel@...r.kernel.org, Eric Anholt <eric@...olt.net>,
        bcm-kernel-feedback-list@...adcom.com,
        linux-rpi-kernel@...ts.infradead.org, mzoran@...wfest.net,
        dan.carpenter@...cle.com, linux-arm-kernel@...ts.infradead.org
Subject: Fwd: [PATCH] Staging: bcm2835-audio: bcm2835_ctl.c: Fixed a comment
 coding style issue

---------- Forwarded message ----------
From: srishti sharma <srishtishar@...il.com>
Date: Thu, May 18, 2017 at 9:06 PM
Subject: Re: [PATCH] Staging: bcm2835-audio: bcm2835_ctl.c: Fixed a
comment coding style issue
To: Greg KH <gregkh@...uxfoundation.org>


On Thu, May 18, 2017 at 7:28 PM, Greg KH <gregkh@...uxfoundation.org> wrote:
> On Thu, May 18, 2017 at 04:20:15PM +0530, srishti wrote:
>> From: srishti sharma <srishtishar@...il.com>
>>
>> Fixed a trailing */ issue.
>>
>> Signed-off-by: srishti sharma <srishtishar@...il.com>
>> ---
>>  drivers/staging/bcm2835-audio/bcm2835-ctl.c | 4 ++--
>>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> You sent two copies of this, which am I supposed to apply?  And what
> changed from the last version?
>
> I'm dropping this, please fix and only send _one_ copy of the patch.
>
> thanks,
>
> greg k-h


both the patches are same , the from and signed-off-by didn't have my
legal name in the patch that I had sent before these . My "send mail
as " settings already have my legal name but it is only accepting the
first name . So I edited the from line in the patch itself , if this
format is correct do I still need to send another patch ?  Please let
me know if it is still incorrect . I have also tried sending it with
my legal name as an alias name in "send email as" settings , but it
only reflects in the from header when I send an email directly from
gmail and not when using git send-email and hence two copies got sent
, I am sorry about that.

Regards,
Srishti