Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Catalin Iacob <iacobcatalin@gmail.com>
To: Bart Van Assche <bvanassche@acm.org>
Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
	 Madhavan Srinivasan <maddy@linux.ibm.com>,
	Michael Ellerman <mpe@ellerman.id.au>,
	 Nicholas Piggin <npiggin@gmail.com>,
	"Christophe Leroy (CS GROUP)" <chleroy@kernel.org>,
	 Rich Felker <dalias@libc.org>,
	John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
	 "David S. Miller" <davem@davemloft.net>,
	Andreas Larsson <andreas@gaisler.com>,
	 "James E.J. Bottomley" <James.Bottomley@hansenpartnership.com>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	 Jens Axboe <axboe@kernel.dk>,
	Yoshinori Sato <ysato@users.sourceforge.jp>,
	 linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
	linuxppc-dev@lists.ozlabs.org,  linux-sh@vger.kernel.org,
	sparclinux@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: [PATCH v3 0/6] Remove remaining references to the pktcdvd driver
Date: Thu, 4 Jun 2026 23:59:21 +0300	[thread overview]
Message-ID: <aiHbj0zn4y9X6qV2@toolbx> (raw)
In-Reply-To: <96a48e65-6ee2-4b81-91f8-821a2de707db@acm.org>

On Thu, Jun 04, 2026 at 08:50:22AM -0700, Bart Van Assche wrote:
> If this series is reposted, please combine patches 1/6 and 2/6. Anyway,
> this series looks good to me.

Thanks for taking a look.

I will repost in a few days when back to a computer to fix the subject
of patch 2 since you are right, it does wrongly suggest that the
implementation is moved.

For learning purposes, do you mind quickly sharing your rationale for
combining 1 and 2? To me they are in the same area but still separate
things: one removes dead code, the other increases encapsulation. Each
is a small but worthwhile cleanup, they can be applied in any order and
each can be applied without the other. It's true that, while patch 2
without patch 1 works, it would increase confusion but I find that an
argument to order 2 after 1, not to say they are one thing.

I'd also find it hard to describe what that combined patch does except
by calling out two things: "remove dead code and move the declaration".
Your suggested "unexport" seems more confusing than clarifying, I'd
argue that today the symbol is not exported since that ifdef always
compiles the export out.

  reply	other threads:[~2026-06-04 20:58 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-30 12:31 [PATCH] scsi: core: Remove dead code export of scsi_device_from_queue Catalin Iacob
2026-05-30 12:46 ` John Paul Adrian Glaubitz
2026-06-03 13:27 ` [PATCH v2] scsi: core: Remove remaining references to the pktcdvd driver Catalin Iacob
2026-06-03 15:36   ` John Garry
2026-06-03 16:06   ` Bart Van Assche
2026-06-04 13:20 ` [PATCH v3 0/6] " Catalin Iacob
2026-06-04 13:20   ` [PATCH v3 1/6] scsi: core: Remove remaining reference " Catalin Iacob
2026-06-04 15:51     ` Bart Van Assche
2026-06-04 13:20   ` [PATCH v3 2/6] scsi: core: Move scsi_device_from_queue() to scsi_priv.h Catalin Iacob
2026-06-04 15:51     ` Bart Van Assche
2026-06-04 13:20   ` [PATCH v3 3/6] mips: Remove remaining defconfig references to the pktcdvd driver Catalin Iacob
2026-06-04 13:20   ` [PATCH v3 4/6] powerpc: " Catalin Iacob
2026-06-04 13:20   ` [PATCH v3 5/6] sh: Remove remaining defconfig reference " Catalin Iacob
2026-06-04 13:20   ` [PATCH v3 6/6] sparc: Remove remaining defconfig references " Catalin Iacob
2026-06-04 15:50   ` [PATCH v3 0/6] Remove remaining " Bart Van Assche
2026-06-04 20:59     ` Catalin Iacob [this message]
2026-06-04 21:17       ` Bart Van Assche

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=aiHbj0zn4y9X6qV2@toolbx \
    --to=iacobcatalin@gmail.com \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=andreas@gaisler.com \
    --cc=axboe@kernel.dk \
    --cc=bvanassche@acm.org \
    --cc=chleroy@kernel.org \
    --cc=dalias@libc.org \
    --cc=davem@davemloft.net \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=maddy@linux.ibm.com \
    --cc=martin.petersen@oracle.com \
    --cc=mpe@ellerman.id.au \
    --cc=npiggin@gmail.com \
    --cc=sparclinux@vger.kernel.org \
    --cc=tsbogend@alpha.franken.de \
    --cc=ysato@users.sourceforge.jp \
    /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