From: Sam James <sam@gentoo.org>
To: Helge Deller <deller@gmx.de>
Cc: Rolf Eike Beer <eike-kernel@sf-tec.de>,
John David Anglin <dave.anglin@bell.net>,
linux-parisc@vger.kernel.org, Deller <deller@kernel.org>,
James Bottomley <James.Bottomley@hansenpartnership.com>
Subject: Re: [PATCH, V3] parisc: Rewrite cache flush code for PA8800/PA8900
Date: Mon, 16 May 2022 23:54:44 +0100 [thread overview]
Message-ID: <F63F43FC-D3BA-4477-B4F0-B4BCABA61878@gentoo.org> (raw)
In-Reply-To: <2df8c4f1-f93d-8ef0-3bfd-9249d43953fc@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 827 bytes --]
> On 16 May 2022, at 23:24, Helge Deller <deller@gmx.de> wrote:
>
> On 5/17/22 00:09, Sam James wrote:
>>> On 16 May 2022, at 22:49, Helge Deller <deller@gmx.de> wrote:
>>>
>>> [snip]
>> Hi Helge,
>>
>>> FWIW, I've done some cleanups to this patch and committed it to my for-next tree.
>>> In case it's split up, please use the revised version.
>>>
>>
>> Should I be testing with for-next (which contains this patch) or for-next-next (which has some smaller bits)?
>
> for-next is for v5.18.
>
> for-next-next is planed to for v5.19
>
> so, please use for-next, since we want to get 5.18 finally fixed.
>
Got it, thanks to both you and Dave!
I'll be testing it on RP3440 (PA8800) and C8000 (PA8900). If you need it, I can test on C3600 (PA8600) too.
Best,
sam
> Thanks!
> Helge
[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 618 bytes --]
next prev parent reply other threads:[~2022-05-16 22:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-16 15:14 [PATCH, V3] parisc: Rewrite cache flush code for PA8800/PA8900 John David Anglin
2022-05-16 21:28 ` Rolf Eike Beer
2022-05-16 21:49 ` Helge Deller
2022-05-16 22:09 ` Sam James
2022-05-16 22:24 ` Helge Deller
2022-05-16 22:54 ` Sam James [this message]
2022-05-16 23:41 ` John David Anglin
2022-05-16 22:24 ` John David Anglin
2022-05-17 13:19 ` Rolf Eike Beer
2022-05-17 13:24 ` Helge Deller
2022-05-17 14:26 ` John David Anglin
2022-05-17 18:11 ` Helge Deller
2022-05-17 18:28 ` Rolf Eike Beer
2022-05-17 18:44 ` John David Anglin
2022-05-17 20:00 ` Helge Deller
2022-05-17 20:19 ` John David Anglin
2022-05-17 18:51 ` John David Anglin
2022-05-17 13:06 ` Rolf Eike Beer
2022-05-17 14:05 ` John David Anglin
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=F63F43FC-D3BA-4477-B4F0-B4BCABA61878@gentoo.org \
--to=sam@gentoo.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=dave.anglin@bell.net \
--cc=deller@gmx.de \
--cc=deller@kernel.org \
--cc=eike-kernel@sf-tec.de \
--cc=linux-parisc@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