From: Greg KH <gregkh@linuxfoundation.org>
To: Conor.Dooley@microchip.com
Cc: Brice.Goglin@inria.fr, atishp@rivosinc.com, sudeep.holla@arm.com,
stable-commits@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Patch "riscv: topology: fix default topology reporting" has been added to the 6.0-stable tree
Date: Sun, 16 Oct 2022 12:30:32 +0200 [thread overview]
Message-ID: <Y0vdSPh3+vDJczzf@kroah.com> (raw)
In-Reply-To: <f97b84b7-9086-f83d-4edf-751873b7b26a@microchip.com>
On Sun, Oct 16, 2022 at 09:58:10AM +0000, Conor.Dooley@microchip.com wrote:
> On 16/10/2022 10:32, gregkh@linuxfoundation.org wrote:
> > EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> >
> > This is a note to let you know that I've just added the patch titled
> >
> > riscv: topology: fix default topology reporting
> >
> > to the 6.0-stable tree which can be found at:
> > http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> >
> > The filename of the patch is:
> > riscv-topology-fix-default-topology-reporting.patch
> > and it can be found in the queue-6.0 subdirectory.
> >
> > If you, or anyone else, feels it should not be added to the stable tree,
> > please let <stable@vger.kernel.org> know about it.
>
> Hey Greg,
> This breaks the build on 6.0 (and I can only assume on the other
> stable queues too).
>
> I put:
> > CC: stable@vger.kernel.org # 456797da792f: arm64: topology: move store_cpu_topology() to shared code
> in the patch itself, did I specify the dependency incorrectly?
No, that's my fault, you specified this wonderfully, I just missed it :(
Now fixed up, thanks!
greg k-h
prev parent reply other threads:[~2022-10-16 10:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <166591276524312@kroah.com>
2022-10-16 9:58 ` Patch "riscv: topology: fix default topology reporting" has been added to the 6.0-stable tree Conor.Dooley
2022-10-16 10:30 ` Greg KH [this message]
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=Y0vdSPh3+vDJczzf@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Brice.Goglin@inria.fr \
--cc=Conor.Dooley@microchip.com \
--cc=atishp@rivosinc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable-commits@vger.kernel.org \
--cc=sudeep.holla@arm.com \
/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