From: Helge Deller <deller@gmx.de>
To: Rolf Eike Beer <eike-kernel@sf-tec.de>,
John David Anglin <dave.anglin@bell.net>
Cc: 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: Tue, 17 May 2022 22:00:05 +0200 [thread overview]
Message-ID: <3e255faa-25a7-b886-6956-239bdd88cbdf@gmx.de> (raw)
In-Reply-To: <4399477.LvFx2qVVIh@daneel.sf-tec.de>
On 5/17/22 20:28, Rolf Eike Beer wrote:
> Am Dienstag, 17. Mai 2022, 20:11:38 CEST schrieb Helge Deller:
>
>> I can easily split out the pr_warn("WARNING").
>
> Would make sense IMHO.
I split that patch out now.
Dave, can you please check if you are ok with it?
https://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux.git/commit/?h=for-next&id=67c35a3b646cc68598ff0bb28de5f8bd7b2e81b3
I used the wording from your other mail.
>> Moving the get_ptep() back to the original place seems ok, and I'll keep
>> the strange indenting which checkpatch want.
>
> If its back at the original place then there is no need to change as
> checkpatch will not complain on unmodified lines.
I meant "back to the place where it was versions before".
So, it has to move anyway now.
> If it needs to be moved and
> changed then I would say do it in it's own patch as well.
I kept it in the way Dave sent it (with the checkpatch fixups I added).
Just pushed a new "for-next" tree at the usual place:
https://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux.git/log/?h=for-next
Helge
next prev parent reply other threads:[~2022-05-17 20:00 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
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 [this message]
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=3e255faa-25a7-b886-6956-239bdd88cbdf@gmx.de \
--to=deller@gmx.de \
--cc=James.Bottomley@hansenpartnership.com \
--cc=dave.anglin@bell.net \
--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