From: Thomas Gleixner <tglx@linutronix.de>
To: Huacai Chen <chenhuacai@kernel.org>,
Charlie Jenkins <charlie@rivosinc.com>
Cc: WANG Xuerui <kernel@xen0n.name>,
loongarch@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH core/entry] LoongArch: Fix include order
Date: Wed, 07 May 2025 11:04:52 +0200 [thread overview]
Message-ID: <87msbon64r.ffs@tglx> (raw)
In-Reply-To: <CAAhV-H7uvnqReegNM+L6Q=ScnXFmpgYnNNTmokBJe9RDSDDdWQ@mail.gmail.com>
On Wed, May 07 2025 at 15:26, Huacai Chen wrote:
> On Wed, May 7, 2025 at 3:11 PM Charlie Jenkins <charlie@rivosinc.com> wrote:
>>
>> Reorder some introduced include headers to keep alphabetical order.
>>
>> Signed-off-by: Charlie Jenkins <charlie@rivosinc.com>
>> Fixes: 7ace1602abf2 ("LoongArch: entry: Migrate ret_from_fork() to C")
>> ---
>> This is a very minor fix to a patch previously applied to the core/entry
>> tip.
> If possible, I prefer it to be squashed to the original patch.
The branch is immutable. It's fine to have it on top.
next prev parent reply other threads:[~2025-05-07 9:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-07 7:11 [PATCH core/entry] LoongArch: Fix include order Charlie Jenkins
2025-05-07 7:26 ` Huacai Chen
2025-05-07 9:04 ` Thomas Gleixner [this message]
2025-05-07 9:15 ` [tip: core/entry] LoongArch: entry: " tip-bot2 for Charlie Jenkins
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=87msbon64r.ffs@tglx \
--to=tglx@linutronix.de \
--cc=charlie@rivosinc.com \
--cc=chenhuacai@kernel.org \
--cc=kernel@xen0n.name \
--cc=linux-kernel@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
/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