From: Alexon Oliveira <alexondunkan@gmail.com>
To: Nam Cao <namcaov@gmail.com>
Cc: gregkh@linuxfoundation.org, martyn@welchs.me.uk,
manohar.vanga@gmail.com, linux-kernel@vger.kernel.org,
linux-staging@lists.linux.dev
Subject: Re: [PATCH v2 1/4] staging: vme_user: fix check alignment of open parenthesis in vme_fake.c
Date: Sat, 26 Aug 2023 17:23:46 -0300 [thread overview]
Message-ID: <ZOpfUjRy3jDwZixX@alolivei-thinkpadt480s.gru.csb> (raw)
In-Reply-To: <ZOpWxBjONs0QpFlU@nam-dell>
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@gmail.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.
> Best regards,
> Nam
Thank you.
Alexon Oliveira
next prev parent reply other threads:[~2023-08-26 20:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-26 15:13 Alexon Oliveira
2023-08-26 19:47 ` Nam Cao
2023-08-26 20:23 ` Alexon Oliveira [this message]
2023-08-26 20:32 ` Nam Cao
2023-08-26 21:13 ` Alexon Oliveira
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZOpfUjRy3jDwZixX@alolivei-thinkpadt480s.gru.csb \
--to=alexondunkan@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=manohar.vanga@gmail.com \
--cc=martyn@welchs.me.uk \
--cc=namcaov@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®