From: Niklas Cassel <cassel@kernel.org>
To: Rosen Penev <rosenp@gmail.com>
Cc: linux-ide@vger.kernel.org, Damien Le Moal <dlemoal@kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/3] ata: pata_ep93xx: COMPILE_TEST and ARM fixups
Date: Mon, 1 Jun 2026 10:54:23 +0200 [thread overview]
Message-ID: <ah1Iv88PGkU54T65@ryzen> (raw)
In-Reply-To: <20260530003627.42473-1-rosenp@gmail.com>
Hello Rosen,
On Fri, May 29, 2026 at 05:36:24PM -0700, Rosen Penev wrote:
> This small series cleans up pata_ep93xx to allow COMPILE_TEST on
> non-ARM platforms. Patch 1 avoids including ARM-specific asm headers,
> patch 2 switches to unsigned long for the data variable, and patch 3
> enables COMPILE_TEST.
>
> Rosen Penev (3):
> ata: pata_ep93xx: avoid asm on non ARM
> ata: pata_ep93xx: use unsigned long for data
> ata: pata_ep93xx: add COMPILE_TEST support
>
> drivers/ata/Kconfig | 2 +-
> drivers/ata/pata_ep93xx.c | 7 ++++++-
> 2 files changed, 7 insertions(+), 2 deletions(-)
Your series looks good to me.
I do not think that you need to address the pre-existing issues reported
by Sashiko.
Intend to wait 1-2 days before picking this up, to hopefully get R-b tag
or two.
Kind regards,
Niklas
next prev parent reply other threads:[~2026-06-01 8:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-30 0:36 [PATCH 0/3] ata: pata_ep93xx: COMPILE_TEST and ARM fixups Rosen Penev
2026-05-30 0:36 ` [PATCH 1/3] ata: pata_ep93xx: avoid asm on non ARM Rosen Penev
2026-05-30 0:49 ` sashiko-bot
2026-05-30 0:36 ` [PATCH 2/3] ata: pata_ep93xx: use unsigned long for data Rosen Penev
2026-05-30 4:49 ` sashiko-bot
2026-05-30 0:36 ` [PATCH 3/3] ata: pata_ep93xx: add COMPILE_TEST support Rosen Penev
2026-05-30 4:57 ` sashiko-bot
2026-06-01 8:54 ` Niklas Cassel [this message]
2026-06-01 18:12 ` [PATCH 0/3] ata: pata_ep93xx: COMPILE_TEST and ARM fixups Rosen Penev
2026-06-01 18:34 ` Niklas Cassel
2026-06-01 18:39 ` Rosen Penev
2026-06-02 11:15 ` 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=ah1Iv88PGkU54T65@ryzen \
--to=cassel@kernel.org \
--cc=dlemoal@kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rosenp@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.