[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <dc9bd25b60c1185e28214293c015e2b3f30f76bf.camel@linux.ibm.com>
Date: Tue, 22 Apr 2025 20:42:16 -0400
From: Mimi Zohar <zohar@...ux.ibm.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>,
Mimi Zohar
<zohar@...ux.vnet.ibm.com>,
Dmitry Kasatkin <dmitry.kasatkin@...il.com>
Cc: Roberto Sassu <roberto.sassu@...wei.com>,
Linux Kernel Mailing List
<linux-kernel@...r.kernel.org>,
Linux Next Mailing List
<linux-next@...r.kernel.org>
Subject: Re: linux-next: duplicate patch in the integrity tree
Hi Stephen,
On Wed, 2025-04-23 at 08:39 +1000, Stephen Rothwell wrote:
> Hi all,
>
> The following commit is also in Linus Torvalds' tree as a different commit
> (but the same patch):
>
> 976e5b974fef ("ima: process_measurement() needlessly takes inode_lock() on MAY_READ")
>
> This is commit
>
> 30d68cb0c37e ("ima: process_measurement() needlessly takes inode_lock() on MAY_READ")
>
> in Linus' tree.
Yes, I know. Roberto unnecessarily rebased on -rc3 before sending the pull
request. As soon as -rc4 is out, I'll resync with Linus.
Mimi
Powered by blists - more mailing lists