From: Greg KH <gregkh@linuxfoundation.org>
To: Dave Penkler <dpenkler@gmail.com>
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
johan@kernel.org
Subject: Re: [PATCH V4 0/4] Destage gpib drivers
Date: Mon, 24 Nov 2025 17:53:19 +0100 [thread overview]
Message-ID: <2025112409-laundry-strained-a24e@gregkh> (raw)
In-Reply-To: <20251117144021.23569-1-dpenkler@gmail.com>
On Mon, Nov 17, 2025 at 03:40:17PM +0100, Dave Penkler wrote:
> This patch series is for moving the gpib drivers out of the staging area.
>
> Patches 1-3 make some preliminary changes in staging to prepare for the move.
> Patch 4 does the move and completes the destage.
>
> Patch 1: Change // comments in uapi header file
> Patch 2: Remove comment item in TODO file
> Patch 3: Add SPDX syscall note to uapi gpib headers
> Patch 4: Complete the destaging of gpib
> - Remove gpib from Kconfig and Makefile in staging
> - Remove the gpib/uapi directory from include search path in Makefile
> - In the code change the uapi include file paths to <linux/xxx.h>
> - Move the common gpib/uapi headers to include/uapi/linux
> - Move the gpib tree out of staging
> - Delete the word Linux from gpib Kconfig file
> - Add gpib to Kconfig and Makefile in drivers
> - Update MAINTAINERS
Now queued up, nice work!
greg k-h
prev parent reply other threads:[~2025-11-24 16:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 14:40 [PATCH V4 0/4] Destage gpib drivers Dave Penkler
2025-11-17 14:40 ` [PATCH V4 1/4] staging: gpib: Change // comments in uapi header file Dave Penkler
2025-11-17 14:40 ` [PATCH V4 2/4] staging: gpib: Update TODO file Dave Penkler
2025-11-17 14:40 ` [PATCH V4 3/4] staging: gpib: Fix SPDX license for gpib headers Dave Penkler
2025-11-17 14:40 ` [PATCH V4 4/4] gpib: Destage gpib Dave Penkler
2025-11-24 16:42 ` Greg KH
2025-11-24 16:53 ` Greg KH [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=2025112409-laundry-strained-a24e@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=dpenkler@gmail.com \
--cc=johan@kernel.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;
as well as URLs for NNTP newsgroup(s).