From: Sudeep Holla <sudeep.holla@arm.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Greg KH <greg@kroah.com>, Sudeep Holla <sudeep.holla@arm.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Pierre Gondois <pierre.gondois@arm.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: duplicate patches in the driver-core tree
Date: Thu, 2 Feb 2023 06:53:53 +0000 [thread overview]
Message-ID: <20230202065353.x7wclzdeui4xylle@bogus> (raw)
In-Reply-To: <20230202121224.54425afd@canb.auug.org.au>
On Thu, Feb 02, 2023 at 12:12:24PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> The following commits are also in the scmi tree as different commits
> (but the same patches):
>
> ecaef469920f ("cacheinfo: Initialize variables in fetch_cache_info()")
> d931b83e62b1 ("cacheinfo: Make default acpi_get_cache_info() return an error")
> 921e672dee91 ("cacheinfo: Remove unused check in init_cache_level()")
>
> They are commits
>
> 7646b6682b41 ("cacheinfo: Initialize variables in fetch_cache_info()")
> 2ebcd557e000 ("cacheinfo: Make default acpi_get_cache_info() return an error")
> b73679f891d8 ("cacheinfo: Remove unused check in init_cache_level()")
>
> in the scmi tree.
Now dropped, sorry for the trouble.
--
Regards,
Sudeep
next prev parent reply other threads:[~2023-02-02 6:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 1:12 linux-next: duplicate patches in the driver-core tree Stephen Rothwell
2023-02-02 6:53 ` Sudeep Holla [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-15 11:34 Stephen Rothwell
2023-08-22 11:51 ` Greg KH
2023-12-11 4:24 Stephen Rothwell
2023-12-11 7:16 ` Greg KH
2024-10-16 4:12 Stephen Rothwell
2024-10-16 5:49 ` Greg KH
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=20230202065353.x7wclzdeui4xylle@bogus \
--to=sudeep.holla@arm.com \
--cc=greg@kroah.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=pierre.gondois@arm.com \
--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