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 3/3] staging: vme: "drivers/staging/vme" tree cleanup
Date: Tue, 12 Apr 2022 11:12:25 -0700 [thread overview]
Message-ID: <20220412181225.GC1236898@alison-desk> (raw)
In-Reply-To: <142698e3761c1e7ba8b17cdd9dc077472ef81668.1649721450.git.codeagain@codeagain.dev>
On Tue, Apr 12, 2022 at 03:58:25AM -0300, Bruno Moreira-Guedes wrote:
> [PATCH v2 3/3] staging: vme: "drivers/staging/vme" tree cleanup
Only the commit msg again ;)
staging: vme: Move drivers/vme to drivers/vme_user
I think that's the whole point here.
That's all!
snip
>
next prev parent reply other threads:[~2022-04-12 18:13 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 [this message]
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
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=20220412181225.GC1236898@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