From: Greg KH <gregkh@linuxfoundation.org>
To: William Breathitt Gray <wbg@kernel.org>
Cc: linux-iio@vger.kernel.org
Subject: Re: [PULL] First set of Counter updates for the 6.2 cycle
Date: Tue, 31 Jan 2023 13:02:18 +0100 [thread overview]
Message-ID: <Y9kDSvCWNLoyIQKO@kroah.com> (raw)
In-Reply-To: <Y9kCIK2bkha/JYJS@ishi>
On Tue, Jan 31, 2023 at 06:57:20AM -0500, William Breathitt Gray wrote:
> On Tue, Jan 31, 2023 at 12:46:30PM +0100, Greg KH wrote:
> > On Tue, Jan 31, 2023 at 06:15:08AM -0500, William Breathitt Gray wrote:
> > > On Tue, Jan 31, 2023 at 08:31:50AM +0100, Greg KH wrote:
> > > > On Mon, Jan 30, 2023 at 04:40:00PM -0500, William Breathitt Gray wrote:
> > > > > The following changes since commit 1b929c02afd37871d5afb9d498426f83432e71c2:
> > > > >
> > > > > Linux 6.2-rc1 (2022-12-25 13:41:39 -0800)
> > > > >
> > > > > are available in the Git repository at:
> > > > >
> > > > > git://git.kernel.org/pub/scm/linux/kernel/git/wbg/counter.git tags/counter-updates-for-6.2a
> > > > >
> > > > > for you to fetch changes up to 01f714ee022ecb2667ca8ba909138b1af4cfff2c:
> > > > >
> > > > > counter: fix dependency references for config MICROCHIP_TCB_CAPTURE (2023-01-18 09:59:58 -0500)
> > > > >
> > > > > ----------------------------------------------------------------
> > > > > First set of Counter updates for the 6.2 cycle
> > > >
> > > > You mean 6.3, right? These aren't bugfixes for 6.2-final from what I
> > > > can tell.
> > > >
> > > > > This set of updates consists only of Kconfig cleanup and changes for the
> > > > > Counter subsystem. In particular, the Kconfig entries are reorganized to
> > > > > to alphabetical order, and dependencies added to restrict building
> > > > > certain drivers (intel-qep, ftm-quaddec, and microchip-tcp-capture) to
> > > > > systems that support them.
> > > > >
> > > > > Changes
> > > > > * counter
> > > > > - Sort the Kconfig entries alphabetically
> > > >
> > > > This isn't needed for 6.2-final at all from waht I can tell.
> > > >
> > > > thanks,
> > > >
> > > > greg k-h
> > >
> > > Oops I mistyped the version in the description; yes these are for the
> > > 6.3 merge. Would you like me to retag and resend?
> >
> > Please do. Also, I can't verify your signature:
> > # gpg: Signature made Mon 30 Jan 2023 10:27:41 PM CET
> > # gpg: using EDDSA key 8D37CDDDE0D22528F8E89FB6B54856CABE12232B
> > # gpg: Can't check signature: No public key
> >
> > Is it in the kernel.org keyring?
> >
> > thanks,
> >
> > greg k-h
>
> I'm not quite sure why it's returning an error for you, but here's the
> key (8D37CDDDE0D22528F8E89FB6B54856CABE12232B) in kernel.org pgpkeys
> tree:
> https://git.kernel.org/pub/scm/docs/kernel/pgpkeys.git/tree/keys/B54856CABE12232B.asc
>
> Does that work for you?
Yes, sorry for the noise, I hadn't updated from the key repo in a while
on this machine. It's all good now.
greg k-h
prev parent reply other threads:[~2023-01-31 12:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 21:40 [PULL] First set of Counter updates for the 6.2 cycle William Breathitt Gray
2023-01-31 7:31 ` Greg KH
2023-01-31 11:15 ` William Breathitt Gray
2023-01-31 11:41 ` William Breathitt Gray
2023-01-31 11:46 ` Greg KH
2023-01-31 11:57 ` William Breathitt Gray
2023-01-31 12:02 ` 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=Y9kDSvCWNLoyIQKO@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