[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20191108123655.GA733294@kroah.com>
Date: Fri, 8 Nov 2019 13:36:55 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Georgi Djakov <georgi.djakov@...aro.org>
Cc: Linux PM list <linux-pm@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL v2] interconnect changes for 5.5
On Fri, Nov 08, 2019 at 01:47:51PM +0200, Georgi Djakov wrote:
> On 8.11.19 г. 12:53 ч., Greg Kroah-Hartman wrote:
> > On Fri, Nov 08, 2019 at 10:59:11AM +0200, Georgi Djakov wrote:
> >> Hi Greg,
> >>
> >> This is the updated pull request with interconnect patches for the 5.5 merge
> >> window. The details are in the signed tag. Please pull into char-misc-next.
> >
> > Ugh, ok, can we just go back to sending patches instead?
> >
> > The first two patches have "Fixes:" tags for older kernels, yet no
> > stable tags. That's not ok.
>
> These two patches are for the current 5.4 release and you have them in your
> char-misc-linus branch already. I assume that you will get them in -next later
> via back merge anyway, so will drop them.
Ah, yeah, that's odd, don't send me stuff like that unless there is a
build dependency on them.
> Should we use Fixes and stable tags always together and only when we fix
> something in older kernels and not in the current one?
stable, no, fixes is fine. It wasn't obvious that these were already in
another branch of mine.
Because of all of this, let's just stick to patches in emails please.
thanks,
greg k-h
Powered by blists - more mailing lists