From: ally heev <allyheev@gmail.com>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
Krzysztof Kozlowski <krzk@kernel.org>
Cc: Miri Korenblit <miriam.rachel.korenblit@intel.com>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND iwlwifi-next] wifi: iwlwifi: mld: remove unused variable in d3.c
Date: Mon, 24 Nov 2025 21:28:39 +0530 [thread overview]
Message-ID: <5d6e492ee9194b1125340a66fbd878279286e433.camel@gmail.com> (raw)
In-Reply-To: <20251124-terrestrial-mule-of-kindness-d8c4f5@lemur>
On Mon, 2025-11-24 at 10:38 -0500, Konstantin Ryabitsev wrote:
> On Sat, Nov 22, 2025 at 03:18:20PM +0100, Krzysztof Kozlowski wrote:
> > > Best regards,
> > > -----BEGIN PGP SIGNATURE-----
> > >
> > > iHUEABYKAB0WIQQBFRpOLrIakF7DYvaWPaLUP9d7HAUCaRLyowAKCRCWPaLUP9d7
> > > HLG9AQDZmggT93tMLv32pq5myG3e83t12KWON9efOBg//lH4vgD+Ppw3KoTpdYtJ
> > > 20VDaWuqUVj9KLqjx9hblfEiB7s9gQw=
> > > =A6F+
> > > -----END PGP SIGNATURE-----
> >
> > You should switch to patatt instead, not signing emails. We don't use
> > that, I think at all, unlike patatt which is being actively checked by
> > toolkit (b4).
>
> It's even more curious. The patch was sent with b4, but I'm pretty sure we
> wouldn't have put the PGP signature in like that, so I'm curious how that even
> happened.
>
> Ally, can you shed some light on that?
>
> -K
Yes, I use b4 for my patches. I work on other open source projects
which use Github. So, my global git config commit autosign is set to
`true`, hence you have seen PGP signatures.
I have disabled it locally now
Regards,
Ally
next prev parent reply other threads:[~2025-11-24 15:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-21 14:27 Ally Heev
2025-11-22 14:18 ` Krzysztof Kozlowski
2025-11-24 15:38 ` Konstantin Ryabitsev
2025-11-24 15:58 ` ally heev [this message]
2025-11-24 16:28 ` Konstantin Ryabitsev
2025-11-25 7:20 ` ally heev
2025-11-25 13:54 ` Konstantin Ryabitsev
2025-11-25 16:00 ` ally heev
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=5d6e492ee9194b1125340a66fbd878279286e433.camel@gmail.com \
--to=allyheev@gmail.com \
--cc=konstantin@linuxfoundation.org \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=miriam.rachel.korenblit@intel.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®