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 11:53:55 +0100	[thread overview]
Message-ID: <20191108105355.GA683899@kroah.com> (raw)
In-Reply-To: <dd4ff7e3-920d-979b-c29b-7535d84d360f@linaro.org>

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.

For patch 5, you are playing "chicken" with what module gets loaded
first, and in the end you're not going to win, only delay the
inevitable.  We now have the driver core framework to support
dependencies like this, please use that instead.

So, can you drop patch 5, fix up patches 1 and 2, and go back to sending
patches instead of pull requests as if these were patches, I could have
fixed up 1 and 2 myself.

thanks,

greg k-h

  reply	other threads:[~2019-11-08 10:53 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 [this message]
2019-11-08 11:47   ` Georgi Djakov
2019-11-08 12:36     ` Greg Kroah-Hartman

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=20191108105355.GA683899@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).