linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Georgi Djakov <georgi.djakov@linaro.org>
Cc: Linux PM list <linux-pm@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL v2] interconnect changes for 5.5
Date: Fri, 8 Nov 2019 13:36:55 +0100	[thread overview]
Message-ID: <20191108123655.GA733294@kroah.com> (raw)
In-Reply-To: <25808ada-dbe6-db38-c68d-26a263942a28@linaro.org>

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

      reply	other threads:[~2019-11-08 12:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-08  8:59 [GIT PULL v2] interconnect changes for 5.5 Georgi Djakov
2019-11-08 10:53 ` Greg Kroah-Hartman
2019-11-08 11:47   ` Georgi Djakov
2019-11-08 12:36     ` Greg Kroah-Hartman [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=20191108123655.GA733294@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=georgi.djakov@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@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).