stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: Peter Chen <peter.chen@nxp.com>
Cc: "dan.carpenter@oracle.com" <dan.carpenter@oracle.com>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: patch "usb: chipidea: fix static checker warning for NULL pointer" added to usb-linus
Date: Mon, 21 Jan 2019 08:21:48 +0100	[thread overview]
Message-ID: <20190121072148.GA32637@kroah.com> (raw)
In-Reply-To: <VI1PR04MB5327D98EF458B564DCFDB5D78B9F0@VI1PR04MB5327.eurprd04.prod.outlook.com>

On Mon, Jan 21, 2019 at 05:29:19AM +0000, Peter Chen wrote:
>  
> > This is a note to let you know that I've just added the patch titled
> > 
> >     usb: chipidea: fix static checker warning for NULL pointer
> > 
> > to my usb git tree which can be found at
> >     git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git
> > in the usb-linus branch.
> > 
> > The patch will show up in the next release of the linux-next tree (usually sometime
> > within the next 24 hours during the week.)
> > 
> > The patch will hopefully also be merged in Linus's tree for the next -rc kernel
> > release.
> > 
> > If you have any questions about this process, please let me know.
> > 
> > 
> 
> Hi Greg,
> 
> This patch does not need to go stable tree, this issue is introduced by v5.0-rc1.

Next time please add a "Fixes:" tag so that it is more obvious :(

thanks,

greg k-h

  reply	other threads:[~2019-01-21  7:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-18  8:39 patch "usb: chipidea: fix static checker warning for NULL pointer" added to usb-linus gregkh
2019-01-21  5:29 ` Peter Chen
2019-01-21  7:21   ` gregkh [this message]
2019-01-21  7:26     ` Peter Chen
     [not found] ` <20190122155555.0AF57217D4@mail.kernel.org>
2019-01-22 16:07   ` 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=20190121072148.GA32637@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=dan.carpenter@oracle.com \
    --cc=peter.chen@nxp.com \
    --cc=stable@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).