public inbox for linux-ide@vger.kernel.org
 help / color / mirror / Atom feed
From: Heiner Kallweit <hkallweit1@gmail.com>
To: Hannes Reinecke <hare@suse.de>,
	Damien Le Moal <dlemoal@kernel.org>,
	Niklas Cassel <cassel@kernel.org>
Cc: linux-ide@vger.kernel.org
Subject: Re: [PATCH 5/5] ata: libata-transport: remove static variable ata_scsi_transport_template
Date: Tue, 7 Apr 2026 14:44:19 +0200	[thread overview]
Message-ID: <d355f69a-5963-45e3-9908-1db79e29f37f@gmail.com> (raw)
In-Reply-To: <05030d56-c59d-474f-8b77-c5d0c456647e@suse.de>

On 07.04.2026 12:39, Hannes Reinecke wrote:
> On 3/30/26 17:21, Heiner Kallweit wrote:
>> Simplify the code by making struct ata_scsi_transportt public, instead
>> of using separate variable ata_scsi_transport_template.
>>
>> Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
>> ---
>>   drivers/ata/libata-scsi.c      | 2 +-
>>   drivers/ata/libata-transport.c | 9 ++-------
>>   drivers/ata/libata-transport.h | 2 +-
>>   3 files changed, 4 insertions(+), 9 deletions(-)
>>
> Huh. Not a big fan of this.
> 
> The idea of using a pointer is that it'll be initialized to 'NULL'
> if the module / file isn't present.
> Exposing a static pointer is tricky in that regard.
> 
Provider (libata-transport) and consumer (libata-scsi) of this static
struct are always built together:

libata-y	:= libata-core.o libata-scsi.o libata-eh.o \
	libata-transport.o libata-trace.o

> Not sure if that is the direction we want to go, but I'll leave it
> to the maintainers to decide.
> 
> Cheers,
> 
> Hannes


  reply	other threads:[~2026-04-07 12:44 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-30 15:17 [PATCH 0/5] ata: libata-transport: series with further refactorings Heiner Kallweit
2026-03-30 15:18 ` [PATCH 1/5] ata: libata-transport: instantiate struct ata_internal statically Heiner Kallweit
2026-03-31  1:26   ` Damien Le Moal
2026-04-07 10:29   ` Hannes Reinecke
2026-03-30 15:18 ` [PATCH 2/5] ata: libata-transport: inline ata_attach|release_transport Heiner Kallweit
2026-03-31  1:29   ` Damien Le Moal
2026-04-07 10:30   ` Hannes Reinecke
2026-03-30 15:19 ` [PATCH 3/5] ata: libata-transport: use static struct ata_transport_internal to simplify match functions Heiner Kallweit
2026-03-31  1:37   ` Damien Le Moal
2026-04-07 10:32   ` Hannes Reinecke
2026-03-30 15:20 ` [PATCH 4/5] ata: libata-transport: split struct ata_internal Heiner Kallweit
2026-03-31  1:41   ` Damien Le Moal
2026-04-07 10:33   ` Hannes Reinecke
2026-03-30 15:21 ` [PATCH 5/5] ata: libata-transport: remove static variable ata_scsi_transport_template Heiner Kallweit
2026-03-31  1:42   ` Damien Le Moal
2026-03-31 11:41     ` Sergey Shtylyov
2026-03-31 20:09       ` Damien Le Moal
2026-04-07 10:39   ` Hannes Reinecke
2026-04-07 12:44     ` Heiner Kallweit [this message]
2026-04-02  8:34 ` [PATCH 0/5] ata: libata-transport: series with further refactorings Niklas Cassel

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=d355f69a-5963-45e3-9908-1db79e29f37f@gmail.com \
    --to=hkallweit1@gmail.com \
    --cc=cassel@kernel.org \
    --cc=dlemoal@kernel.org \
    --cc=hare@suse.de \
    --cc=linux-ide@vger.kernel.org \
    /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