From: Andi Shyti <andi.shyti@linux.intel.com>
To: Soumya Negi <soumya.negi97@gmail.com>
Cc: Martyn Welch <martyn@welchs.me.uk>,
Manohar Vanga <manohar.vanga@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
outreachy@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-staging@lists.linux.dev
Subject: Re: [PATCH 0/4] staging: vme_user: Coding style cleanup patches
Date: Sun, 15 Oct 2023 07:29:29 +0200 [thread overview]
Message-ID: <ZSt4uZcQxm4jN+Fy@ashyti-mobl2.lan> (raw)
In-Reply-To: <20231014200241.GA20874@Negi>
Hi Soumya,
On Sat, Oct 14, 2023 at 01:02:42PM -0700, Soumya Negi wrote:
> On Fri, Oct 13, 2023 at 04:47:12PM -0700, Soumya Negi wrote:
> > This patchset performs trivial code cleanups on the driver
> > staging/vme_user to improve code readability. All patches address
> > issues reported by checkpatch.pl, and may be applied in any sequence.
>
> I have made a mistake here in the cover letter message. These patches need to
> be applied in order. I think I will have to send a v2. Will hold off on
> sending it just in case any other problems are pointed out by someone after
> review.
No need to resend for this reason. Patches in patchsets are
anyway always applied in the sequence they are sent.
Andi
prev parent reply other threads:[~2023-10-15 5:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-13 23:47 [PATCH 0/4] staging: vme_user: Coding style cleanup patches Soumya Negi
2023-10-13 23:47 ` [PATCH 1/4] staging: vme_user: Correct spelling mistakes in comments Soumya Negi
2023-10-13 23:47 ` [PATCH 2/4] staging: vme_user: Fix unbalanced {} in if-else blocks Soumya Negi
2023-10-13 23:47 ` [PATCH 3/4] staging: vme_user: Add spaces around '*' Soumya Negi
2023-10-13 23:47 ` [PATCH 4/4] staging: vme_user: Add spaces around '<<' operator Soumya Negi
2023-10-14 20:02 ` [PATCH 0/4] staging: vme_user: Coding style cleanup patches Soumya Negi
2023-10-15 5:29 ` Andi Shyti [this message]
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=ZSt4uZcQxm4jN+Fy@ashyti-mobl2.lan \
--to=andi.shyti@linux.intel.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=outreachy@lists.linux.dev \
--cc=soumya.negi97@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).