Linux IIO development
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: William Breathitt Gray <wbg@kernel.org>
Cc: linux-iio@vger.kernel.org
Subject: Re: [PULL] counter: First set of Counter fixes for 6.0-rc5
Date: Thu, 22 Sep 2022 09:32:17 +0200	[thread overview]
Message-ID: <YywPgWIgkE76z48/@kroah.com> (raw)
In-Reply-To: <YytwQEV+ajrZELTm@ishi>

On Wed, Sep 21, 2022 at 04:12:48PM -0400, William Breathitt Gray wrote:
> On Wed, Sep 21, 2022 at 03:26:16PM +0200, Greg KH wrote:
> > On Thu, Sep 15, 2022 at 12:42:40PM -0400, William Breathitt Gray wrote:
> > > The following changes since commit 568035b01cfb107af8d2e4bd2fb9aea22cf5b868:
> > > 
> > >   Linux 6.0-rc1 (2022-08-14 15:50:18 -0700)
> > > 
> > > are available in the Git repository at:
> > > 
> > >   git://git.kernel.org/pub/scm/linux/kernel/git/wbg/counter.git tags/counter-fixes-for-6.0a
> > > 
> > > for you to fetch changes up to 8294b04153c33602e9c3dd21ac90c1e99bd0fdaf:
> > > 
> > >   counter: Realign counter_comp comment block to 80 characters (2022-09-11 11:45:02 -0400)
> > > 
> > > ----------------------------------------------------------------
> > > counter: First set of Counter fixes for 6.0-rc5
> > > 
> > > counter
> > >  - Realign counter_comp comment block to 80 characters
> > > 
> > > 104-quad-8
> > >  - Fix skipped IRQ lines during events configuration
> > > 
> > > ----------------------------------------------------------------
> > > William Breathitt Gray (2):
> > >       counter: 104-quad-8: Fix skipped IRQ lines during events configuration
> > >       counter: Realign counter_comp comment block to 80 characters
> > > 
> > >  drivers/counter/104-quad-8.c |  6 +++---
> > >  include/linux/counter.h      | 40 ++++++++++++++++++++--------------------
> > >  2 files changed, 23 insertions(+), 23 deletions(-)
> > 
> > 
> > You signed this pull request, yet I don't see your key in the kernel.org
> > pgp repo, and so I get this error when trying to merge:
> > 
> > # gpg: Signature made Thu 15 Sep 2022 06:40:07 PM CEST
> > # gpg:                using EDDSA key 8D37CDDDE0D22528F8E89FB6B54856CABE12232B
> > # gpg: Can't check signature: No public key
> > 
> > Did you use the right key, or is it somewhere else?
> > 
> > thanks,
> > 
> > greg k-h
> 
> It's located under pgpkeys/keys/B54856CABE12232B.asc in the kernel.org
> pgp repo: https://git.kernel.org/pub/scm/docs/kernel/pgpkeys.git/tree/keys/B54856CABE12232B.asc
> 
> I added wbg@kernel.org as a new UID and uploaded it to keys.openpgp.org:
> https://keys.openpgp.org/search?q=8D37CDDDE0D22528F8E89FB6B54856CABE12232B
> 
> Looks like the kernel.org pgp repo hasn't been synchronized yet with the
> updated key from keys.openpgp.org, so I suspect that's why you're
> getting the error right now.

Ok, can you just send me the patch through email for now until things
get propagated properly?

thanks,

greg k-h

  reply	other threads:[~2022-09-22  7:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-15 16:42 [PULL] counter: First set of Counter fixes for 6.0-rc5 William Breathitt Gray
2022-09-21 13:26 ` Greg KH
2022-09-21 20:12   ` William Breathitt Gray
2022-09-22  7:32     ` Greg KH [this message]
2022-09-22 10:56       ` William Breathitt Gray

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=YywPgWIgkE76z48/@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=wbg@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