public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Finn Thain <fthain@linux-m68k.org>
To: Michael Schmitz <schmitzmic@gmail.com>
Cc: will@sowerbutts.com, linux-m68k@vger.kernel.org,
	rz@linux-m68k.org, geert@linux-m68k.org
Subject: Re: [PATCH RFC v3] m68k/q40: fix IO base selection for Q40 in pata_falcon.c
Date: Wed, 16 Aug 2023 15:29:07 +1000 (AEST)	[thread overview]
Message-ID: <2371f714-e0a2-7c0e-d811-5b7ea7a6684f@linux-m68k.org> (raw)
In-Reply-To: <df430e28-9bca-4453-2c81-c50edbbf4f9e@gmail.com>


On Wed, 16 Aug 2023, Michael Schmitz wrote:

> 
> Right - I also wonder whether using priv->swap_data to skip the bit test in
> the most likely case (no byte swapping) is actually worth it.
> 

Given it's a platform device that's only ever instantiated once, you could 
just use the module-scope variable rather than device-scope.

BTW, the patch description could state some of the implications for the 
default setting i.e. interoperability with the vendor operating system 
(and IDE disks from Atari Falcon I guess) as opposed to interoperability 
with everyone else.

> I'll split this into bugfix and byte swap parts
> 
> Where should this go - linux-ide for sure, but is Bartlomiej still the 
> correct maintainer?
> 

The latest MAINTAINERS file says,

$ scripts/get_maintainer.pl -f drivers/ata/pata_falcon.c 
Sergey Shtylyov <s.shtylyov@omp.ru> (reviewer:LIBATA PATA DRIVERS)
Damien Le Moal <dlemoal@kernel.org> (maintainer:LIBATA SUBSYSTEM (Serial and Parallel ATA drivers))
linux-ide@vger.kernel.org (open list:LIBATA PATA DRIVERS)
linux-kernel@vger.kernel.org (open list)

See also c4f9c8bbcc24 and fd86194aca1f.

  reply	other threads:[~2023-08-16  5:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-15 22:32 [PATCH RFC v3] m68k/q40: fix IO base selection for Q40 in pata_falcon.c Michael Schmitz
2023-08-16  0:23 ` Finn Thain
2023-08-16  4:59   ` Michael Schmitz
2023-08-16  5:29     ` Finn Thain [this message]
2023-08-16  7:27       ` Michael Schmitz
2023-08-16  7:37       ` Finn Thain
2023-08-16  8:06         ` Michael Schmitz
2023-08-16  9:04           ` Finn Thain
2023-08-16 10:40             ` Finn Thain
2023-08-16  8:07 ` Geert Uytterhoeven
2023-08-16 19:40   ` Michael Schmitz
2023-08-16 22:36 ` William R Sowerbutts
2023-08-17  1:35   ` Michael Schmitz

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=2371f714-e0a2-7c0e-d811-5b7ea7a6684f@linux-m68k.org \
    --to=fthain@linux-m68k.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=rz@linux-m68k.org \
    --cc=schmitzmic@gmail.com \
    --cc=will@sowerbutts.com \
    /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