public inbox for ath12k@lists.infradead.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: Jeff Johnson <quic_jjohnson@quicinc.com>
Cc: <linux-wireless@vger.kernel.org>,  <ath10k@lists.infradead.org>,
	<ath11k@lists.infradead.org>,  <ath12k@lists.infradead.org>,
	<quic_kvalo@quicinc.com>,
	 Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: Re: pull-request: ath-next-20240702
Date: Wed, 03 Jul 2024 17:49:17 +0300	[thread overview]
Message-ID: <87jzi2edjm.fsf@kernel.org> (raw)
In-Reply-To: <5b98e939-bfea-4a16-a116-5a00d3497190@quicinc.com> (Jeff Johnson's message of "Wed, 3 Jul 2024 07:06:58 -0700")

Jeff Johnson <quic_jjohnson@quicinc.com> writes:

> On 7/3/2024 12:14 AM, Kalle Valo wrote:
>> Kalle Valo <kvalo@kernel.org> writes:
>>> I see a weird warning from gpg which I have never seen before:
>>>
>>> merged tag 'ath-next-20240702'
>>> gpg: Signature made Tue 02 Jul 2024 05:55:42 PM EEST
>>> gpg:                using EDDSA key 3F9AD487CCF522D7A21F0C492C15BBA0898CCB7B
>>> gpg:                issuer "jjohnson@kernel.org"
>>> gpg: Good signature from "Jeff Johnson <quic_jjohnson@quicinc.com>" [full]
>>> gpg: WARNING: We do NOT trust this key!
>>> gpg:          The signature is probably a FORGERY.
>>>
>>> It first says that the signature is good and then claims it's a forgery,
>>> odd. Is this a problem between using different email addresses or what?
>> 
>> I did 'gpg --refresh-keys', now your key contains your kernel.org
>> address and I don't see the warning anymore.
>> 
>
> There had to be at least one issue with my first PR. Glad you sorted it out.
> Key management is still a mystery to me...

This wasn't a problem in your pull request, It was just a problem
between my chair and my display ;)

But I have to say that I hate PGP, "user friendly" is clearly not part
of their vocabulary.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches


  reply	other threads:[~2024-07-03 14:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-02 20:44 pull-request: ath-next-20240702 Jeff Johnson
2024-07-03  7:05 ` Kalle Valo
2024-07-03  7:14   ` Kalle Valo
2024-07-03 14:06     ` Jeff Johnson
2024-07-03 14:49       ` Kalle Valo [this message]
2024-07-03 13:57 ` Kalle Valo

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=87jzi2edjm.fsf@kernel.org \
    --to=kvalo@kernel.org \
    --cc=ath10k@lists.infradead.org \
    --cc=ath11k@lists.infradead.org \
    --cc=ath12k@lists.infradead.org \
    --cc=bartosz.golaszewski@linaro.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=quic_jjohnson@quicinc.com \
    --cc=quic_kvalo@quicinc.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