From: Greg KH <gregkh@linuxfoundation.org>
To: Benson Leung <bleung@google.com>
Cc: Won Chung <wonchung@google.com>, Takashi Iwai <tiwai@suse.de>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Benson Leung <bleung@chromium.org>,
Prashant Malani <pmalani@chromium.org>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v2] sound/hda: Add NULL check to component match callback function
Date: Thu, 31 Mar 2022 19:46:39 +0200 [thread overview]
Message-ID: <YkXo/8fEHmKxDM2S@kroah.com> (raw)
In-Reply-To: <YkXmBQ5TJ4JNnuQG@google.com>
On Thu, Mar 31, 2022 at 10:33:57AM -0700, Benson Leung wrote:
> Hi Greg,
>
> On Thu, Mar 31, 2022 at 07:18:00PM +0200, Greg KH wrote:
> > On Thu, Mar 31, 2022 at 09:58:43AM -0700, Won Chung wrote:
> > > > So is this actually triggering on 5.17 right now? Or is it due to some
> > > > other not-applied changes you are testing at the moment?
> > > >
> > > > confused,
> > > >
> > > > greg k-h
> > >
> > > Hi Greg,
> > >
> > > I believe it is not causing an issue in 5.17 at the moment. It is
> > > triggered when we try to apply new changes and test it locally.
> > > (registering a component for usb4_port)
> >
> > Then why would it ever be needed to be backported to a stable kernel?
> >
> > Please be more careful.
> >
> > greg k-h
>
> Sorry about that. I gave Won bad advice to cc stable. You're right, it will
> only be relevant when a future patch lands in usb4.
It isn't even relevant now, please only worry about this when you have
your patches ready for submission that causes this breakage.
thanks,
greg k-h
next prev parent reply other threads:[~2022-03-31 17:46 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-30 21:19 [PATCH v2] sound/hda: Add NULL check to component match callback function Won Chung
2022-03-31 7:27 ` Takashi Iwai
2022-03-31 8:38 ` Won Chung
2022-03-31 9:12 ` Takashi Iwai
2022-03-31 9:25 ` Heikki Krogerus
2022-03-31 9:28 ` Takashi Iwai
2022-03-31 9:34 ` Heikki Krogerus
2022-03-31 9:45 ` Takashi Iwai
2022-03-31 13:29 ` Takashi Iwai
2022-03-31 14:19 ` Takashi Iwai
2022-03-31 15:33 ` Benson Leung
2022-03-31 15:37 ` Takashi Iwai
2022-03-31 16:10 ` Mika Westerberg
2022-03-31 16:38 ` Greg KH
2022-03-31 16:58 ` Won Chung
2022-03-31 17:18 ` Greg KH
2022-03-31 17:33 ` Benson Leung
2022-03-31 17:46 ` Greg KH [this message]
2022-04-01 7:02 ` Heikki Krogerus
2022-03-31 11:39 ` Greg KH
2022-03-31 12:52 ` Heikki Krogerus
2022-03-31 12:56 ` Greg KH
2022-03-31 13:15 ` Takashi Iwai
-- strict thread matches above, loose matches on Subject: below --
2022-03-30 20:55 Won Chung
2022-03-30 21:15 ` Won Chung
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=YkXo/8fEHmKxDM2S@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=bleung@chromium.org \
--cc=bleung@google.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=perex@perex.cz \
--cc=pmalani@chromium.org \
--cc=stable@vger.kernel.org \
--cc=tiwai@suse.com \
--cc=tiwai@suse.de \
--cc=wonchung@google.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