From: Bruno Moreira-Guedes <codeagain@codeagain.dev>
To: 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: [PATCH v4 0/3] staging: vme: Cleanup driver tree old structures
Date: Thu, 21 Apr 2022 11:57:34 -0300 [thread overview]
Message-ID: <cover.1650544175.git.codeagain@codeagain.dev> (raw)
[-- Attachment #1: Type: text/plain, Size: 2492 bytes --]
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).
The 'vme_user/' driver is the only remaining vme-family driver in the
'staging/' tree, but its structure, entry in menuconfig and building
routines are still attached to the 'vme/' subtree now outside
'staging/'. The present patchset fixes it.
Signed-off-by: Bruno Moreira-Guedes <codeagain@codeagain.dev>
---
CHANGE SUMMARY
Version: v1 v2 v3 v4
[PATCH 1/3] * - * -
[PATCH 2/3] - * * -
[PATCH 3/3] - * * *
CHANGELOG
v4:
* Remove extraneous patch from set (Greg)
* Improve changelog format (Alison)
* Update commit message in PATCH 3/3
v3:
* Update Changelog to cover letter (Alison)
* Update commit messages and logs (Alison, Greg)
* Rename patches 2/3 and 3/3
v2:
* Add new patch to set: 2/3
* Add new patch to set: 3/3
OBSERVATIONS
As Martyn confirmed the devices are still being manufactured I'll keep
going on with this patch meanwhile.
PATCHES
[PATCH 1/3] staging: vme: Move vme_user to staging KConfig
[PATCH 2/3] staging: vme: Add VME_BUS dependency to Kconfig
[PATCH 3/3] staging: vme: Move 'vme/devices/' to 'vme_user/'
---
Bruno Moreira-Guedes (3):
staging: vme: Move vme_user to staging KConfig
staging: vme: Add VME_BUS dependency to Kconfig
staging: vme: Move 'vme/devices/' to 'vme_user/'
MAINTAINERS | 2 +-
drivers/staging/Kconfig | 1 +
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, 4 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.3
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next reply other threads:[~2022-04-21 14:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-21 14:57 Bruno Moreira-Guedes [this message]
2022-04-21 14:58 ` [PATCH v4 1/3] staging: vme: Move vme_user to staging KConfig Bruno Moreira-Guedes
2022-04-21 14:59 ` [PATCH v4 2/3] staging: vme: Add VME_BUS dependency to Kconfig Bruno Moreira-Guedes
2022-04-21 14:59 ` [PATCH v4 3/3] staging: vme: Move 'vme/devices/' to 'vme_user/' Bruno Moreira-Guedes
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=cover.1650544175.git.codeagain@codeagain.dev \
--to=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;
as well as URLs for NNTP newsgroup(s).