From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Christian Brauner <brauner@kernel.org>,
Danilo Krummrich <dakr@kernel.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: duplicate patch in the vfs-brauner tree
Date: Thu, 21 Aug 2025 07:24:29 +0200 [thread overview]
Message-ID: <2025082116-cupbearer-average-5627@gregkh> (raw)
In-Reply-To: <20250821110212.08c134db@canb.auug.org.au>
On Thu, Aug 21, 2025 at 11:02:12AM +1000, Stephen Rothwell wrote:
> Hi all,
>
> The following commit is also in the driver-core.current tree as a
> different commit (but the same patch):
>
> 8e7e265d558e ("debugfs: fix mount options not being applied")
>
> This is commit
>
> ba6cc29351b1 ("debugfs: fix mount options not being applied")
>
> in the driver-core.current tree.
Thanks, yeah, we both ended up picking this one up :(
next prev parent reply other threads:[~2025-08-21 5:24 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-21 1:02 linux-next: duplicate patch in the vfs-brauner tree Stephen Rothwell
2025-08-21 5:24 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-12-18 5:32 Stephen Rothwell
2025-07-07 23:51 Stephen Rothwell
2025-07-08 8:35 ` Christian Brauner
2025-07-08 21:51 ` Stephen Rothwell
2025-05-20 23:45 Stephen Rothwell
2025-05-20 23:48 ` Stephen Rothwell
2025-04-16 22:49 Stephen Rothwell
2025-04-22 8:03 ` Christian Brauner
2025-01-16 1:16 Stephen Rothwell
2025-01-19 21:06 ` Stephen Rothwell
2025-01-09 0:18 Stephen Rothwell
2025-01-20 21:39 ` Stephen Rothwell
2024-08-25 22:24 Stephen Rothwell
2024-08-26 12:13 ` Christian Brauner
2024-08-15 22:55 Stephen Rothwell
2024-07-01 3:21 Stephen Rothwell
2024-06-13 0:48 Stephen Rothwell
2024-06-13 0:51 ` Stephen Rothwell
2024-06-13 2:21 ` Andrew Morton
2024-06-13 12:17 ` Christian Brauner
2024-06-13 19:43 ` Andrew Morton
2024-06-13 20:06 ` Marion & Christophe JAILLET
2024-03-18 21:23 Stephen Rothwell
2024-03-06 22:02 Stephen Rothwell
2024-02-05 5:23 Stephen Rothwell
2023-09-14 23:39 Stephen Rothwell
2023-09-18 20:52 ` Darrick J. Wong
2023-09-19 12:34 ` Christian Brauner
2023-09-19 15:43 ` Darrick J. Wong
2023-09-20 12:09 ` Christian Brauner
2023-08-06 22:37 Stephen Rothwell
2023-07-17 0:11 Stephen Rothwell
2023-07-19 6:16 ` Christian Brauner
2023-07-19 23:28 ` Tyler Hicks
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=2025082116-cupbearer-average-5627@gregkh \
--to=greg@kroah.com \
--cc=brauner@kernel.org \
--cc=dakr@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=sfr@canb.auug.org.au \
/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