From: Johan Hovold <johan@kernel.org>
To: Dave Penkler <dpenkler@gmail.com>
Cc: gregkh@linuxfoundation.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2 00/10] staging: gpib: Destage gpib drivers
Date: Wed, 12 Nov 2025 18:12:17 +0100 [thread overview]
Message-ID: <aRS_8V5udtngcMhk@hovoldconsulting.com> (raw)
In-Reply-To: <20251111094512.6411-1-dpenkler@gmail.com>
On Tue, Nov 11, 2025 at 10:45:02AM +0100, Dave Penkler wrote:
> This patch series is for moving the gpib drivers out of the staging area.
Note that I have no idea whether this code is ready to be moved out of
staging, I'm just commenting on how it is done here.
> As many changes as possible (patches 1-6) are done in the staging area
> to prepare for the move. Patches 7-10 do the move and complete the destage.
>
> Patch 1: Remove gpib from Kconfig and Makefile in staging
> Patch 2: Remove the gpib/uapi directory from include search path
> Patch 3: In the code change the uapi include file paths to <linux/xxx.h>
> Patch 4: Remove comment item in TODO file
> Patch 5: Delete the word Linux from gpib Kconfig option title
> Patch 6: Add SPDX syscall note to uapi gpib headers
> Patch 7: Move the common gpib/uapi headers to include/uapi/linux
> Patch 8: Move the gpib tree out of staging
> Patch 9: Add gpib to Kconfig and Makefile in drivers
> Patch 10: Update MAINTAINERS for post destage
I still think most of these should be squashed into a single patch
that moves things out of staging.
> Dave Penkler (10):
> staging: Remove gpib build from staging
> staging: gpib: Remove gpib/uapi from search path
> staging: gpib: Change file path for uapi headers
> staging: gpib: Update TODO file
This can be done first before moving.
> staging: gpib: Change gpib Kconfig option title
This too, but it's hardly worth doing in a separate patch so can be
squashed as well.
> staging: gpib: Fix SPDX license for gpib headers
Can also be done before moving.
> uapi: linux: Add common gpib interface headers
> gpib: Move gpib drivers out of staging
> gpib: Add gpib build menu and rule to drivers
> MAINTAINERS: Update for gpib destage
And then squash the rest into a single patch that can be build tested.
Johan
prev parent reply other threads:[~2025-11-12 17:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-11 9:45 [PATCH V2 00/10] staging: gpib: Destage gpib drivers Dave Penkler
2025-11-11 9:45 ` [PATCH V2 01/10] staging: Remove gpib build from staging Dave Penkler
2025-11-11 9:45 ` [PATCH V2 02/10] staging: gpib: Remove gpib/uapi from search path Dave Penkler
2025-11-11 9:45 ` [PATCH V2 03/10] staging: gpib: Change file path for uapi headers Dave Penkler
2025-11-11 9:45 ` [PATCH V2 04/10] staging: gpib: Update TODO file Dave Penkler
2025-11-11 9:45 ` [PATCH V2 05/10] staging: gpib: Change gpib Kconfig option title Dave Penkler
2025-11-11 9:45 ` [PATCH V2 06/10] staging: gpib: Fix SPDX license for gpib headers Dave Penkler
2025-11-11 9:45 ` [PATCH V2 07/10] uapi: linux: Add common gpib interface headers Dave Penkler
2025-11-11 9:45 ` [PATCH V2 08/10] gpib: Move gpib drivers out of staging Dave Penkler
2025-11-11 9:45 ` [PATCH V2 09/10] gpib: Add gpib build menu and rule to drivers Dave Penkler
2025-11-11 9:45 ` [PATCH V2 10/10] MAINTAINERS: Update for gpib destage Dave Penkler
2025-11-12 17:12 ` Johan Hovold [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=aRS_8V5udtngcMhk@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=dpenkler@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.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