From: Sudeep Holla <sudeep.holla@kernel.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Cristian Marussi <cristian.marussi@arm.com>,
arm-scmi@vger.kernel.org, Sudeep Holla <sudeep.holla@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] firmware: arm_scmi: Spelling s/mulit/multi/, s/currenly/currently/
Date: Mon, 9 Mar 2026 09:29:29 +0000 [thread overview]
Message-ID: <20260309-bold-space-ibis-fbff63@sudeepholla> (raw)
In-Reply-To: <CAMuHMdXkyrDRLyDf77TFFjAX_Q_fnA_OwmbkoaEicd+F9JP2aA@mail.gmail.com>
On Mon, Mar 09, 2026 at 09:16:29AM +0100, Geert Uytterhoeven wrote:
> Hi Sudeep,
>
> On Sun, 8 Mar 2026 at 14:01, Sudeep Holla <sudeep.holla@kernel.org> wrote:
> > On Fri, 20 Feb 2026 10:55:15 +0100, Geert Uytterhoeven wrote:
> > > Fix misspellings of "multi" and "currently".
> >
> > Applied to sudeep.holla/linux (for-next/scmi/fixes), thanks!
> >
> > [1/1] firmware: arm_scmi: Spelling s/mulit/multi/, s/currenly/currently/
> > https://git.kernel.org/sudeep.holla/c/4e701b47c3ba
>
> Thank you!
>
> BTW, I noticed some of your commits use the non-standard
> "Message-Id:"-tag, while others use the standard "Link:"-tag (albeit
> with the lore.kernel.org instead of the recommended patch.msgid.link
> domain) to record the origin of patches. Do you have different git
> setups on different machines?
>
Not really. I used to use "Link:" and switched to "Message-Id" a while ago.
I use only one setup and if you are observing something like above, I am
doing something different. I need to check what is that, but the intention
is to use "Message-Id". Let me have a look.
--
Regards,
Sudeep
next prev parent reply other threads:[~2026-03-09 9:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-20 9:55 [PATCH] firmware: arm_scmi: Spelling s/mulit/multi/, s/currenly/currently/ Geert Uytterhoeven
2026-03-08 13:01 ` Sudeep Holla
2026-03-09 8:16 ` Geert Uytterhoeven
2026-03-09 9:29 ` Sudeep Holla [this message]
2026-03-09 9:38 ` Sudeep Holla
2026-03-09 9:53 ` Geert Uytterhoeven
2026-03-09 10:26 ` Sudeep Holla
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=20260309-bold-space-ibis-fbff63@sudeepholla \
--to=sudeep.holla@kernel.org \
--cc=arm-scmi@vger.kernel.org \
--cc=cristian.marussi@arm.com \
--cc=geert@linux-m68k.org \
--cc=linux-arm-kernel@lists.infradead.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