From: Greg KH <gregkh@linuxfoundation.org>
To: Chanwoo Choi <cw00.choi@samsung.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Chanwoo Choi (chanwoo@kernel.org)" <chanwoo@kernel.org>,
함명주 <myungjoo.ham@samsung.com>
Subject: Re: [GIT PULL] extcon next for v5.18
Date: Fri, 11 Mar 2022 07:20:14 +0100 [thread overview]
Message-ID: <YirqHsUPTJZGFCEx@kroah.com> (raw)
In-Reply-To: <59f03dd1-6731-87f2-7d4b-51e5058fb9da@samsung.com>
On Fri, Mar 11, 2022 at 11:28:52AM +0900, Chanwoo Choi wrote:
> On 3/11/22 6:47 AM, Greg KH wrote:
> > On Tue, Mar 08, 2022 at 11:48:53AM +0900, Chanwoo Choi wrote:
> >> Dear Greg,
> >>
> >> This is extcon-next pull request for v5.18. I add detailed description of
> >> this pull request on below. Please pull extcon with following updates.
> >>
> >> Best Regards,
> >> Chanwoo Choi
> >>
> >> The following changes since commit 7e57714cd0ad2d5bb90e50b5096a0e671dec1ef3:
> >>
> >> Linux 5.17-rc6 (2022-02-27 14:36:33 -0800)
> >>
> >> are available in the Git repository at:
> >>
> >> git://git.kernel.org/pub/scm/linux/kernel/git/chanwoo/extcon.git tags/extcon-next-for-5.18
> >
> > You signed this tag with a gpg key that is expired, so my check failed
> > when pulling :(
> >
> > Can you please fix your key and get the update in the kernel.org gpg
> > database?
>
> I'm sorry to bother you. After fixing key issue, I'll resend pull request.
In the meantime, you can send me changes by email.
thanks,
greg k-h
prev parent reply other threads:[~2022-03-11 6:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20220308022359epcas1p2d145af3c2f462bb6e69da46663c38c95@epcas1p2.samsung.com>
2022-03-08 2:48 ` Chanwoo Choi
2022-03-10 21:47 ` Greg KH
2022-03-11 2:28 ` Chanwoo Choi
2022-03-11 6:20 ` Greg KH [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=YirqHsUPTJZGFCEx@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=chanwoo@kernel.org \
--cc=cw00.choi@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=myungjoo.ham@samsung.com \
/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
all inboxes | Powered by JetHome®