[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <80e72876-da81-4694-86a2-835c049ed30f@yandex.ru>
Date: Wed, 24 Apr 2024 12:24:49 +0300
From: stsp <stsp2@...dex.ru>
To: David Laight <David.Laight@...LAB.COM>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Cc: Eric Biederman <ebiederm@...ssion.com>,
Alexander Viro <viro@...iv.linux.org.uk>,
Christian Brauner <brauner@...nel.org>, Jan Kara <jack@...e.cz>,
Andy Lutomirski <luto@...nel.org>,
"linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>
Subject: Re: [PATCH 1/2] fs: reorganize path_openat()
24.04.2024 12:17, David Laight пишет:
> From: Stas Sergeev
>> Sent: 22 April 2024 09:45
> I seem to have 5 copies of this patch.....
Yep, its re-sent with every new iteartion,
but doesn't change by itself (the other
one changes).
Is there anything I can do to avoid
unneeded duplicates of an unchanged
patch?
Manually reduce Cc list until the patch
changes? That looks too much of a trouble
though.
> You probably ought to merge the two 'unlikely' tests.
Ok.
> Copying op->open_flag to a local may also generate better code.
Can't gcc deduce this on its own?
But ok, will do.
Powered by blists - more mailing lists