From: Georgi Djakov <djakov@kernel.org>
To: Greg KH <gregkh@linuxfoundation.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 18:30:36 +0300 [thread overview]
Message-ID: <2a2bb00a-28ae-ecd8-760a-a83cc14c02fa@kernel.org> (raw)
In-Reply-To: <YtFjbhn3pveplLQb@kroah.com>
On 15.07.22 15:54, Greg KH wrote:
> 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
>
Apologies for missing this. This was in linux-next for more than a week, but nobody
reported it. I'll create a script to check for this problem to my workflow.
Now sending you v2 pull request.
Thanks,
Georgi
next prev parent reply other threads:[~2022-07-15 15:30 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
2022-07-15 15:30 ` Georgi Djakov [this message]
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=2a2bb00a-28ae-ecd8-760a-a83cc14c02fa@kernel.org \
--to=djakov@kernel.org \
--cc=gregkh@linuxfoundation.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