From: Imre Kaloz <kaloz@kernel.org>
To: Lee Jones <lee@kernel.org>
Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
mfd@lists.linux.dev, linux-ide@vger.kernel.org
Subject: Re: [PATCH v2 46/53] mfd: ioc3: Add IOC4 ATA/ATAPI cell
Date: Tue, 20 Oct 2026 23:08:17 +0200 [thread overview]
Message-ID: <20261020210818.27215-1-kaloz@kernel.org> (raw)
In-Reply-To: <179198336665.839288.12369537253671309518@kernel.org>
On Tue, 20 Oct 2026, Lee Jones wrote:
> > + {
> > + .name = "pata_sgiioc4",
> > + .resources = ioc4_ata_resources,
> > + .num_resources = ARRAY_SIZE(ioc4_ata_resources),
> > + },
>
> Shouldn't this have been added in Patch 31?
It should have, yes. In v3 the ATA cell, its resources and the
level-triggered other_ir bit move into the patch that adds the IOC4
cells (part of the split of 31 I described in my other reply) and
this one goes away.
Thanks for catching it,
Imre
prev parent reply other threads:[~2026-10-20 21:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 13:16 [PATCH v2 00/53] MIPS: SGI-IP27: add support for the IP35 (Bedrock hub) machines Imre Kaloz
2026-10-13 13:17 ` [PATCH v2 45/53] ata: add pata_sgiioc4 driver for the SGI IOC4 ATA/ATAPI controller Imre Kaloz
2026-10-13 13:17 ` [PATCH v2 47/53] MAINTAINERS: add an entry for the SGI IOC4 ATA driver Imre Kaloz
2026-10-13 13:25 ` Damien Le Moal
2026-10-13 13:38 ` Imre Kaloz
2026-10-13 15:13 ` Damien Le Moal
2026-10-13 13:35 ` [PATCH v2 00/53] MIPS: SGI-IP27: add support for the IP35 (Bedrock hub) machines Niklas Cassel
2026-10-13 14:25 ` Imre Kaloz
2026-10-20 18:06 ` Jakub Kicinski
2026-10-20 20:42 ` Imre Kaloz
2026-10-20 21:56 ` Jakub Kicinski
[not found] ` <754bae380c938b63eeaa87e3dccf9755314675ed.1791890466.git.kaloz@kernel.org>
[not found] ` <179198336665.839288.12369537253671309518@kernel.org>
2026-10-20 21:08 ` Imre Kaloz [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=20261020210818.27215-1-kaloz@kernel.org \
--to=kaloz@kernel.org \
--cc=lee@kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=mfd@lists.linux.dev \
--cc=tsbogend@alpha.franken.de \
/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