All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Saravana Kannan <saravanak@google.com>
Cc: stable@vger.kernel.org
Subject: Re: device link patches on 4.19.99 breaks functionality
Date: Fri, 28 Feb 2020 08:06:10 +0100	[thread overview]
Message-ID: <20200228070610.GA2895159@kroah.com> (raw)
In-Reply-To: <CAGETcx8kFOHMmCd3gopUmQgFp+DfC45gVqVkNbb4TwWmvZOJkA@mail.gmail.com>

On Thu, Feb 27, 2020 at 02:17:38PM -0800, Saravana Kannan wrote:
> On Thu, Feb 27, 2020 at 1:26 PM Saravana Kannan <saravanak@google.com> wrote:
> >
> > On Thu, Feb 27, 2020 at 1:51 AM Greg KH <gregkh@linuxfoundation.org> wrote:
> > >
> > > On Fri, Feb 21, 2020 at 01:21:00AM -0800, Saravana Kannan wrote:
> > > > 4.19.99 seems to have picked up quite a few device link patches.
> > > > However, one of them [1] broke the ability to add stateful and
> > > > stateless links between the same two devices. Looks like the breakage
> > > > was fixed in the mainline kernel in subsequent commits [2] and [3].
> > > >
> > > > Can we pull [2] and [3] into 4.19 please? And any other intermediate
> > > > device link patches up to [3].
> > > >
> > > > [1] - 6fdc440366f1a99f344b629ac92f350aefd77911
> > > > [2] - 515db266a9da
> > > > [3] - fb583c8eeeb1 (this fixed a bug in [2])
> > >
> > > "up to"?
> > >
> > > 515db266a9da does not apply to 4.19, so should I just drop [1] instead?
> > >
> > > Or, can you provided a backported set of patches so I know exactly what
> > > to apply?
> >
> > Let me take a stab at backporting [2] and [3] or whatever else might
> > be necessary. What git repo/branch did you want me to try that on?
> 
> I'm assuming this one:
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/log/?h=linux-4.19.y

Yes, that is the one, thanks.

greg k-h

      reply	other threads:[~2020-02-28  7:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-21  9:21 device link patches on 4.19.99 breaks functionality Saravana Kannan
2020-02-27  9:51 ` Greg KH
2020-02-27 21:26   ` Saravana Kannan
2020-02-27 22:17     ` Saravana Kannan
2020-02-28  7:06       ` 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=20200228070610.GA2895159@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=saravanak@google.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 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.