From: Mark Brown <broonie@kernel.org>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Mathias Nyman <mathias.nyman@linux.intel.com>,
Aishwarya TCV <aishwarya.tcv@arm.com>,
Greg KH <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org, Klara Modin <klarasmodin@gmail.com>
Subject: Re: [PATCH] usb: usb-acpi: Fix oops due to freeing uninitialized pld pointer
Date: Mon, 18 Mar 2024 15:10:03 +0000 [thread overview]
Message-ID: <1ef6601b-bdb3-41f1-b3ce-07418dd9c031@sirena.org.uk> (raw)
In-Reply-To: <19ec72e2-8273-43a0-bbeb-706565e926f2@rowland.harvard.edu>
[-- Attachment #1: Type: text/plain, Size: 852 bytes --]
On Mon, Mar 18, 2024 at 10:55:54AM -0400, Alan Stern wrote:
> On Mon, Mar 18, 2024 at 02:40:31PM +0000, Mark Brown wrote:
> > On Mon, Mar 18, 2024 at 04:36:24PM +0200, Mathias Nyman wrote:
> > > We are already mid merge window.
> > > Not sure if there's some way Greg can still get this in, otherwise I'm
> > > afraid we need wait for rc1, and try to get this into rc2.
> > Given that it's a bug fix for a fairly serious issue (it's causing boot
> > failures) it should be perfectly fine to apply during the merge window?
> Greg is away on vacation until this weekend. If the bug is all that
> serious, you could consider sending the fix directly to Linus.
I can do that, or Mathias do you want to resend it? Boot breaks in -rc1
tend to be pretty miserable for testing since a lot of people use it as
a base for their branches.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 484 bytes --]
next prev parent reply other threads:[~2024-03-18 15:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-08 11:34 [PATCH] usb: usb-acpi: Fix oops due to freeing uninitialized pld pointer Mathias Nyman
2024-03-18 13:30 ` Aishwarya TCV
2024-03-18 14:36 ` Mathias Nyman
2024-03-18 14:40 ` Mark Brown
2024-03-18 14:55 ` Alan Stern
2024-03-18 15:10 ` Mark Brown [this message]
2024-03-19 7:29 ` Mathias Nyman
2024-03-19 11:37 ` Mark Brown
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=1ef6601b-bdb3-41f1-b3ce-07418dd9c031@sirena.org.uk \
--to=broonie@kernel.org \
--cc=aishwarya.tcv@arm.com \
--cc=gregkh@linuxfoundation.org \
--cc=klarasmodin@gmail.com \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@linux.intel.com \
--cc=stern@rowland.harvard.edu \
/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.