From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Mark Brown <broonie@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 driver-core tree
Date: Fri, 11 Jul 2025 08:48:20 +0200 [thread overview]
Message-ID: <2025071106-mustang-encrypt-d307@gregkh> (raw)
In-Reply-To: <20250711162945.078138dc@canb.auug.org.au>
On Fri, Jul 11, 2025 at 04:29:45PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> The following commit is also in the regmap tree as a different commit
> (but the same patch):
>
> 8009fb751d2c ("regmap: get rid of redundant debugfs_file_{get,put}()")
>
> This is commit
>
> 9f711c9321cf ("regmap: get rid of redundant debugfs_file_{get,put}()")
>
> in the regmap tree.
Ah, sorry about that, I took the whole series. All should be fine when
they are merged together.
greg k-h
next prev parent reply other threads:[~2025-07-11 6:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-11 6:29 linux-next: duplicate patch in the driver-core tree Stephen Rothwell
2025-07-11 6:48 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-04-30 7:47 Stephen Rothwell
2025-04-30 18:34 ` Rafael J. Wysocki
2025-04-30 18:56 ` Greg KH
2023-12-18 4:40 Stephen Rothwell
2023-12-18 5:54 ` Andrew Morton
2023-12-18 6:35 ` Stephen Rothwell
2023-12-18 10:26 ` Greg KH
2023-02-20 2:38 Stephen Rothwell
2023-02-20 7:13 ` Greg KH
2023-02-14 1:57 Stephen Rothwell
2023-02-14 6:46 ` Greg KH
2023-02-14 16:47 ` Wysocki, Rafael J
2023-02-14 16:59 ` Greg KH
2023-02-20 12:16 ` Stephen Rothwell
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=2025071106-mustang-encrypt-d307@gregkh \
--to=greg@kroah.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.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 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.