public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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 V3 0/6] Destage gpib drivers
Date: Fri, 14 Nov 2025 09:49:03 +0100	[thread overview]
Message-ID: <aRbs_4yzncsoAkB2@hovoldconsulting.com> (raw)
In-Reply-To: <20251113104543.5875-1-dpenkler@gmail.com>

On Thu, Nov 13, 2025 at 11:45:37AM +0100, Dave Penkler wrote:
> This patch series is for moving the gpib drivers out of the staging area.
> 
> As many changes as possible (patches 1-5) are done in the staging area
> to prepare for the move. Patch 6 does the move and completes 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: Add SPDX syscall note to uapi gpib headers
> Patch 6: Complete the destaging of gpib
>       - Move the common gpib/uapi headers to include/uapi/linux
>       - Move the gpib tree out of staging
>       - Delete the word Linux from gpib Kconfig option title
>       - Add gpib to Kconfig and Makefile in drivers
>       - Update MAINTAINERS
> 
> Dave Penkler (6):
>   staging: Remove gpib build from staging
>   staging: gpib: Remove gpib/uapi from search path
>   staging: gpib: Change file path for uapi headers

Sorry if it wasn't clear, but I meant that you should squash also these
three into the patch moving things out of staging.

>   staging: gpib: Update TODO file
>   staging: gpib: Fix SPDX license for gpib headers
>   gpib: Destage gpib

So in the end you'd only have these three patches.

Johan

  parent reply	other threads:[~2025-11-14  8:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-13 10:45 [PATCH V3 0/6] Destage gpib drivers Dave Penkler
2025-11-13 10:45 ` [PATCH V3 1/6] staging: Remove gpib build from staging Dave Penkler
2025-11-13 10:45 ` [PATCH V3 2/6] staging: gpib: Remove gpib/uapi from search path Dave Penkler
2025-11-13 10:45 ` [PATCH V3 3/6] staging: gpib: Change file path for uapi headers Dave Penkler
2025-11-13 10:45 ` [PATCH V3 4/6] staging: gpib: Update TODO file Dave Penkler
2025-11-13 10:45 ` [PATCH V3 5/6] staging: gpib: Fix SPDX license for gpib headers Dave Penkler
2025-11-13 10:45 ` [PATCH V3 6/6] gpib: Destage gpib Dave Penkler
2025-11-14  6:45   ` kernel test robot
2025-11-14  6:46   ` kernel test robot
2025-11-14  6:47   ` kernel test robot
2025-11-14  8:49 ` Johan Hovold [this message]
2025-11-14 10:21   ` [PATCH V3 0/6] Destage gpib drivers Greg KH

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=aRbs_4yzncsoAkB2@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