From: Sam James <sam@gentoo.org>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linmag7@gmail.com, Al Viro <viro@ftp.linux.org.uk>,
arnd@arndb.de, chris@zankel.net, dinguyen@kernel.org,
glaubitz@physik.fu-berlin.de, ink@unseen.parts,
jcmvbkbc@gmail.com, kees@kernel.org,
linux-alpha@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-csky@vger.kernel.org, linux-hexagon@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-m68k@lists.linux-m68k.org,
linux-mips@vger.kernel.org, linux-openrisc@vger.kernel.org,
linux-parisc@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-s390@vger.kernel.org, linux-sh@vger.kernel.org,
linux-snps-arc@lists.infradead.org,
linux-um@lists.infradead.org, linuxppc-dev@lists.ozlabs.org,
loongarch@lists.linux.dev, mattst88@gmail.com,
monstr@monstr.eu, richard.henderson@linaro.org,
sparclinux@vger.kernel.org, x86@kernel.org
Subject: Re: [PATCH v2 1/1] mm: pgtable: fix pte_swp_exclusive
Date: Mon, 02 Jun 2025 16:16:14 +0100 [thread overview]
Message-ID: <878qma41j5.fsf@gentoo.org> (raw)
In-Reply-To: <20250602041118.GA2675383@ZenIV>
Al Viro <viro@zeniv.linux.org.uk> writes:
> On Sat, Apr 05, 2025 at 06:09:11PM +0100, Sam James wrote:
>> Sam James <sam@gentoo.org> writes:
>>
>> > Lovely cleanup and a great suggestion from Al.
>> >
>> > Reviewed-by: Sam James <sam@gentoo.org>
>> >
>> > I'd suggest adding a:
>> > Suggested-by: Al Viro <viro@zeniv.linux.org.uk>
>>
>> Al, were you planning on taking this through your tree?
>
> FWIW, I expected it to get sent to Linus as "please, run this
> sed script before -rc1" kind of thing, script being something
> like
>
> sed -i -e 's/int pte_swp_exclusive/bool pte_swp_exclusive/' \
> `git grep -l 'int pte_swp_exclusive'`
>
> with suggested commit message... It's absolutely regular and
> that kind of tree-wide change is easier handled that way.
Ah, sorry. Both Magnus and I are new and irregular kernel contributors,
but I've seen that before and should've thought of it.
> [...]
cheers,
sam
WARNING: multiple messages have this Message-ID (diff)
From: Sam James <sam@gentoo.org>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linmag7@gmail.com, Al Viro <viro@ftp.linux.org.uk>,
arnd@arndb.de, chris@zankel.net, dinguyen@kernel.org,
glaubitz@physik.fu-berlin.de, ink@unseen.parts,
jcmvbkbc@gmail.com, kees@kernel.org,
linux-alpha@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-csky@vger.kernel.org, linux-hexagon@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-m68k@lists.linux-m68k.org,
linux-mips@vger.kernel.org, linux-openrisc@vger.kernel.org,
linux-parisc@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-s390@vger.kernel.org, linux-sh@vger.kernel.org,
linux-snps-arc@lists.infradead.org,
linux-um@lists.infradead.org, linuxppc-dev@lists.ozlabs.org,
loongarch@lists.linux.dev, mattst88@gmail.com,
monstr@monstr.eu, richard.henderson@linaro.org,
sparclinux@vger.kernel.org, x86@kernel.org
Subject: Re: [PATCH v2 1/1] mm: pgtable: fix pte_swp_exclusive
Date: Mon, 02 Jun 2025 16:16:14 +0100 [thread overview]
Message-ID: <878qma41j5.fsf@gentoo.org> (raw)
In-Reply-To: <20250602041118.GA2675383@ZenIV>
Al Viro <viro@zeniv.linux.org.uk> writes:
> On Sat, Apr 05, 2025 at 06:09:11PM +0100, Sam James wrote:
>> Sam James <sam@gentoo.org> writes:
>>
>> > Lovely cleanup and a great suggestion from Al.
>> >
>> > Reviewed-by: Sam James <sam@gentoo.org>
>> >
>> > I'd suggest adding a:
>> > Suggested-by: Al Viro <viro@zeniv.linux.org.uk>
>>
>> Al, were you planning on taking this through your tree?
>
> FWIW, I expected it to get sent to Linus as "please, run this
> sed script before -rc1" kind of thing, script being something
> like
>
> sed -i -e 's/int pte_swp_exclusive/bool pte_swp_exclusive/' \
> `git grep -l 'int pte_swp_exclusive'`
>
> with suggested commit message... It's absolutely regular and
> that kind of tree-wide change is easier handled that way.
Ah, sorry. Both Magnus and I are new and irregular kernel contributors,
but I've seen that before and should've thought of it.
> [...]
cheers,
sam
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
WARNING: multiple messages have this Message-ID (diff)
From: Sam James <sam@gentoo.org>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linmag7@gmail.com, Al Viro <viro@ftp.linux.org.uk>,
arnd@arndb.de, chris@zankel.net, dinguyen@kernel.org,
glaubitz@physik.fu-berlin.de, ink@unseen.parts,
jcmvbkbc@gmail.com, kees@kernel.org,
linux-alpha@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-csky@vger.kernel.org, linux-hexagon@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-m68k@lists.linux-m68k.org,
linux-mips@vger.kernel.org, linux-openrisc@vger.kernel.org,
linux-parisc@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-s390@vger.kernel.org, linux-sh@vger.kernel.org,
linux-snps-arc@lists.infradead.org,
linux-um@lists.infradead.org, linuxppc-dev@lists.ozlabs.org,
loongarch@lists.linux.dev, mattst88@gmail.com,
monstr@monstr.eu, richard.henderson@linaro.org,
sparclinux@vger.kernel.org, x86@kernel.org
Subject: Re: [PATCH v2 1/1] mm: pgtable: fix pte_swp_exclusive
Date: Mon, 02 Jun 2025 16:16:14 +0100 [thread overview]
Message-ID: <878qma41j5.fsf@gentoo.org> (raw)
In-Reply-To: <20250602041118.GA2675383@ZenIV>
Al Viro <viro@zeniv.linux.org.uk> writes:
> On Sat, Apr 05, 2025 at 06:09:11PM +0100, Sam James wrote:
>> Sam James <sam@gentoo.org> writes:
>>
>> > Lovely cleanup and a great suggestion from Al.
>> >
>> > Reviewed-by: Sam James <sam@gentoo.org>
>> >
>> > I'd suggest adding a:
>> > Suggested-by: Al Viro <viro@zeniv.linux.org.uk>
>>
>> Al, were you planning on taking this through your tree?
>
> FWIW, I expected it to get sent to Linus as "please, run this
> sed script before -rc1" kind of thing, script being something
> like
>
> sed -i -e 's/int pte_swp_exclusive/bool pte_swp_exclusive/' \
> `git grep -l 'int pte_swp_exclusive'`
>
> with suggested commit message... It's absolutely regular and
> that kind of tree-wide change is easier handled that way.
Ah, sorry. Both Magnus and I are new and irregular kernel contributors,
but I've seen that before and should've thought of it.
> [...]
cheers,
sam
_______________________________________________
linux-snps-arc mailing list
linux-snps-arc@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-snps-arc
next prev parent reply other threads:[~2025-06-02 15:16 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-18 17:55 [PATCH v2 0/1] mm: pgtable: fix pte_swp_exclusive Magnus Lindholm
2025-02-18 17:55 ` Magnus Lindholm
2025-02-18 17:55 ` Magnus Lindholm
2025-02-18 17:55 ` [PATCH v2 1/1] " Magnus Lindholm
2025-02-18 17:55 ` Magnus Lindholm
2025-02-18 17:55 ` Magnus Lindholm
2025-02-19 14:06 ` Sam James
2025-02-19 14:06 ` Sam James
2025-02-19 14:06 ` Sam James
2025-04-05 17:09 ` Sam James
2025-04-05 17:09 ` Sam James
2025-04-05 17:09 ` Sam James
2025-06-02 4:11 ` Al Viro
2025-06-02 4:11 ` Al Viro
2025-06-02 4:11 ` Al Viro
2025-06-02 15:16 ` Sam James [this message]
2025-06-02 15:16 ` Sam James
2025-06-02 15:16 ` Sam James
2025-04-05 17:21 ` John Paul Adrian Glaubitz
2025-04-05 17:21 ` John Paul Adrian Glaubitz
2025-04-05 17:21 ` John Paul Adrian Glaubitz
2025-04-07 8:06 ` Geert Uytterhoeven
2025-04-07 8:06 ` Geert Uytterhoeven
2025-04-07 8:06 ` Geert Uytterhoeven
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=878qma41j5.fsf@gentoo.org \
--to=sam@gentoo.org \
--cc=arnd@arndb.de \
--cc=chris@zankel.net \
--cc=dinguyen@kernel.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=ink@unseen.parts \
--cc=jcmvbkbc@gmail.com \
--cc=kees@kernel.org \
--cc=linmag7@gmail.com \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-csky@vger.kernel.org \
--cc=linux-hexagon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-openrisc@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=linux-um@lists.infradead.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=loongarch@lists.linux.dev \
--cc=mattst88@gmail.com \
--cc=monstr@monstr.eu \
--cc=richard.henderson@linaro.org \
--cc=sparclinux@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@ftp.linux.org.uk \
--cc=viro@zeniv.linux.org.uk \
--cc=x86@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 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.