public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Georgi Djakov <djakov@kernel.org>
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] interconnect changes for 5.20
Date: Fri, 15 Jul 2022 14:54:06 +0200	[thread overview]
Message-ID: <YtFjbhn3pveplLQb@kroah.com> (raw)
In-Reply-To: <YtFjOW77wGnToYt8@kroah.com>

On Fri, Jul 15, 2022 at 02:53:13PM +0200, Greg KH wrote:
> On Fri, Jul 15, 2022 at 01:10:21PM +0300, Georgi Djakov wrote:
> > Hello Greg,
> > 
> > This is the pull request with interconnect changes for the 5.20-rc1 merge
> > window. It contains driver updates. The details are in the signed tag.
> > 
> > All patches have been in linux-next during the last few days. No issues have
> > been reported so far. Please pull into char-misc-next.
> > 
> > Thanks,
> > Georgi
> > 
> > The following changes since commit f2906aa863381afb0015a9eb7fefad885d4e5a56:
> > 
> >   Linux 5.19-rc1 (2022-06-05 17:18:54 -0700)
> > 
> > are available in the Git repository at:
> > 
> >   git://git.kernel.org/pub/scm/linux/kernel/git/djakov/icc.git tags/icc-5.20-rc1
> 
> Pulled and pushed out, thanks.

Oops, nope, I got the following error:

Fixes tag: Fixes: f0d8048525d7d("interconnect: Add imx core driver")
	Has these problem(s):
		- missing space between the SHA1 and the subject

I can rebase this and fix it up myself, or you can do it, which ever is
easier for you.

thanks,

greg k-h

  reply	other threads:[~2022-07-15 12:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-15 10:10 [GIT PULL] interconnect changes for 5.20 Georgi Djakov
2022-07-15 12:53 ` Greg KH
2022-07-15 12:54   ` Greg KH [this message]
2022-07-15 15:30     ` Georgi Djakov
2022-07-16  5:21       ` Greg KH
2022-07-16  5:49         ` Georgi Djakov

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=YtFjbhn3pveplLQb@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=djakov@kernel.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