linux-kernel - Re: [PATCH v2 1/4] staging: vme_user: fix check alignment of open parenthesis in vme

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

Message-ID: <ZOphYXeTMM+QhnTk@nam-dell>
Date:   Sat, 26 Aug 2023 22:32:33 +0200
From:   Nam Cao <namcaov@...il.com>
To:     Alexon Oliveira <alexondunkan@...il.com>
Cc:     gregkh@...uxfoundation.org, martyn@...chs.me.uk,
        manohar.vanga@...il.com, linux-kernel@...r.kernel.org,
        linux-staging@...ts.linux.dev
Subject: Re: [PATCH v2 1/4] staging: vme_user: fix check alignment of open
 parenthesis in vme_fake.c

On Sat, Aug 26, 2023 at 05:23:46PM -0300, Alexon Oliveira wrote:
> On Sat, Aug 26, 2023 at 09:47:16PM +0200, Nam Cao wrote:
> > On Sat, Aug 26, 2023 at 12:13:05PM -0300, Alexon Oliveira wrote:
> > > Fixed all CHECK: Alignment should match open parenthesis
> > > as reported by checkpatch to adhere to the Linux kernel
> > > coding-style guidelines.
> > > 
> > > Signed-off-by: Alexon Oliveira <alexondunkan@...il.com>
> > 
> > Patch series should be in a single email thread. But your 4 patches are sent
> > separately :(
> >
> 
> Hmm, ACK, I didn't know that.
> 
> > Have a look at how your patches are sent on https://lore.kernel.org/linux-staging/
> > and you will see what I am referring to.
> > 
> 
> Indeed they were sent as separate emails.
> 
> > Here's an example of how patch series should be:
> > https://lore.kernel.org/linux-staging/736c8159-90e9-4575-3c22-5a62515d5c03@gmail.com/T/#t
> >
> 
> Please, if you don't mind me to ask, how's the best way to do that?
> I've already wrote the cover letter, generated the patches' files again,
> but I don't know how is the best way to send them as you instructed me
> using mutt.

You must use the argument "--thread=shallow" while generating patch series
with git format-patch. Then mutt should correctly send them in a single thread.

The instructions can also be found here:
https://kernelnewbies.org/FirstKernelPatch

Best regards,
Nam