From: Michael Schmitz <schmitzmic@gmail.com>
To: will@sowerbutts.com, linux-m68k@vger.kernel.org
Cc: rz@linux-m68k.org, geert@linux-m68k.org
Subject: Re: [PATCH RFC v3 0/2] Q40 IDE fixes
Date: Thu, 17 Aug 2023 15:56:54 +1200 [thread overview]
Message-ID: <fb01c784-a7ea-a9b2-6761-7ae5fb1e4369@gmail.com> (raw)
In-Reply-To: <20230817035001.8400-1-schmitzmic@gmail.com>
$subject meant to say v4, of course ...
Cheers,
Michael
Am 17.08.2023 um 15:49 schrieb Michael Schmitz:
> v4 of the Q40 IDE patch, split into two parts. First patch just fixes the
> bug introduced when converting Q40 to use pata_falcon, second patch adds the
> byte-swapping option requested by William.
>
> Please review this again, just to make sure I haven't messed up anything
> when applying the review comments to the split patches.
>
> Cheers,
>
> Michael
>
next prev parent reply other threads:[~2023-08-17 3:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-17 3:49 [PATCH RFC v3 0/2] Q40 IDE fixes Michael Schmitz
2023-08-17 3:50 ` [PATCH RFC v3 1/2] m68k/q40: fix IO base selection for Q40 in pata_falcon.c Michael Schmitz
2023-08-17 3:50 ` [PATCH RFC v3 2/2] m68k/q40: add data_swab option for pata_falcon to byte-swap disk data Michael Schmitz
2023-08-17 10:15 ` Finn Thain
2023-08-17 11:47 ` Geert Uytterhoeven
2023-08-17 19:21 ` Michael Schmitz
2023-08-17 21:28 ` Michael Schmitz
2023-08-18 14:33 ` Geert Uytterhoeven
2023-08-18 23:53 ` Finn Thain
2023-08-21 7:46 ` Geert Uytterhoeven
2023-08-21 11:08 ` Finn Thain
2023-08-21 20:36 ` Michael Schmitz
2023-08-21 23:18 ` Finn Thain
[not found] ` <F32F62FE-2A74-4648-8BF1-0D1A1E76309B@linux-m68k.org>
2023-08-17 19:07 ` Michael Schmitz
2023-08-17 19:14 ` Michael Schmitz
2023-08-18 0:36 ` Finn Thain
2023-08-17 3:56 ` Michael Schmitz [this message]
2023-08-17 9:20 ` [PATCH RFC v3 0/2] Q40 IDE fixes William R Sowerbutts
2023-08-17 20:25 ` William R Sowerbutts
2023-08-17 21:29 ` 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=fb01c784-a7ea-a9b2-6761-7ae5fb1e4369@gmail.com \
--to=schmitzmic@gmail.com \
--cc=geert@linux-m68k.org \
--cc=linux-m68k@vger.kernel.org \
--cc=rz@linux-m68k.org \
--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