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  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Wed, 8 Aug 2018 16:10:47 +0200
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Greg Gallagner <greg@...eddedgreg.com>
Cc:     Stefan Wahren <stefan.wahren@...e.com>, devel@...verdev.osuosl.org,
        Florian Fainelli <f.fainelli@...il.com>,
        Scott Branden <sbranden@...adcom.com>,
        Ray Jui <rjui@...adcom.com>, linux-kernel@...r.kernel.org,
        Eric Anholt <eric@...olt.net>,
        bcm-kernel-feedback-list@...adcom.com,
        linux-rpi-kernel@...ts.infradead.org,
        linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v2] staging/bcm2835-audio: Fix alignment of function
 arguments - Style

On Wed, Aug 08, 2018 at 08:54:49AM -0400, Greg Gallagner wrote:
> On 08/08/2018 08:26 AM, Greg Kroah-Hartman wrote:
> > On Tue, Aug 07, 2018 at 09:40:47PM -0400, Greg Gallagher wrote:
> >> Fix warnings generated by checkpatch.pl for alignment should match open
> >> parenthesis.  This is a coding style change only.
> >>
> >> Signed-off-by: Greg Gallagher <greg@...eddedgreg.com>
> >> ---
> >> Changes in v2:
> >>     - Clean up all the alignment warnings in the file
> >> ---
> >>  .../staging/vc04_services/bcm2835-audio/bcm2835-ctl.c  | 18 +++++++++---------
> >>  1 file changed, 9 insertions(+), 9 deletions(-)
> > You sent 2 patches that did the same thing, with different subjects :(
> >
> > Please fix up and send only the "correct" one.
> >
> > greg k-h
> Sorry, the first one was a mistake and I should have sent something saying
> to ignore it.  I will double check the second one is correct.  Is there
> a best
> practice when I'd like a patch ignored?

Just respond to the email and say "please ignore this patch" or
something like that.

thanks,
greg k-h

Powered by blists - more mailing lists