From: Alison Schofield <alison.schofield@intel.com>
To: Bruno Moreira-Guedes <codeagain@codeagain.dev>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Martyn Welch <martyn@welchs.me.uk>,
Manohar Vanga <manohar.vanga@gmail.com>,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
outreachy@lists.linux.dev,
Bruno's Patch Watchbox <patch-reply@codeagain.dev>
Subject: Re: [PATCH v2 0/3] staging: vme: Restructuring menuconfig and tree
Date: Tue, 12 Apr 2022 10:18:49 -0700 [thread overview]
Message-ID: <20220412171849.GA1236580@alison-desk> (raw)
In-Reply-To: <cover.1649721450.git.codeagain@codeagain.dev>
On Tue, Apr 12, 2022 at 03:53:46AM -0300, Bruno Moreira-Guedes wrote:
> This patch series modify the vme_user driver's place in
> menuconfig (1/3), fixes a missing `depends on` line in a Kconfig file
> (2/3), and rearrages the directory tree for the driver allowing a more
> straightforward comprehension of its contents (3/3).
For a patchset it (typically) is OK to put the changelog in the
cover letter. See the first patch tutorial for how to format that.
That give you a little less editing to do for each individual patch.
I do see that you responded to this cover letter with clarifications.
That is fine. Just be aware that it will probably stop reviewers from
continuing their review, because you've already alerted them a v3 is
in the works. I'm going to go ahead and comment on a few format things
in this set, so maybe you can tidy them up in v3.
Alison
>
> Signed-off-by: Bruno Moreira-Guedes <codeagain@codeagain.dev>
>
> Bruno Moreira-Guedes (3):
> staging: vme: Adjusted VME_USER in Kconfig
> staging: vme: Fix missing `depends on` at KConfig
> staging: vme: "drivers/staging/vme" tree cleanup
>
> MAINTAINERS | 2 +-
> drivers/staging/Kconfig | 2 ++
> drivers/staging/Makefile | 2 +-
> drivers/staging/vme/Makefile | 2 --
> drivers/staging/{vme/devices => vme_user}/Kconfig | 2 +-
> drivers/staging/{vme/devices => vme_user}/Makefile | 0
> drivers/staging/{vme/devices => vme_user}/vme_user.c | 0
> drivers/staging/{vme/devices => vme_user}/vme_user.h | 0
> drivers/vme/Kconfig | 2 --
> 9 files changed, 5 insertions(+), 7 deletions(-)
> delete mode 100644 drivers/staging/vme/Makefile
> rename drivers/staging/{vme/devices => vme_user}/Kconfig (93%)
> rename drivers/staging/{vme/devices => vme_user}/Makefile (100%)
> rename drivers/staging/{vme/devices => vme_user}/vme_user.c (100%)
> rename drivers/staging/{vme/devices => vme_user}/vme_user.h (100%)
>
> --
> 2.35.1
>
prev parent reply other threads:[~2022-04-12 17:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-12 6:53 [PATCH v2 0/3] staging: vme: Restructuring menuconfig and tree Bruno Moreira-Guedes
2022-04-12 6:55 ` [PATCH v2 1/3] staging: vme: Adjusted VME_USER in Kconfig Bruno Moreira-Guedes
2022-04-12 13:35 ` Greg Kroah-Hartman
2022-04-12 17:59 ` Alison Schofield
2022-04-12 6:56 ` [PATCH v2 2/3] staging: vme: Fix missing `depends on` at KConfig Bruno Moreira-Guedes
2022-04-12 18:03 ` Alison Schofield
2022-04-12 6:58 ` [PATCH v2 3/3] staging: vme: "drivers/staging/vme" tree cleanup Bruno Moreira-Guedes
2022-04-12 18:12 ` Alison Schofield
2022-04-12 7:12 ` [PATCH v2 0/3] staging: vme: Restructuring menuconfig and tree Bruno Moreira-Guedes
2022-04-12 17:18 ` Alison Schofield [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=20220412171849.GA1236580@alison-desk \
--to=alison.schofield@intel.com \
--cc=codeagain@codeagain.dev \
--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=patch-reply@codeagain.dev \
/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