From: Lee Jones <lee@kernel.org>
To: Binbin Zhou <zhoubb.aaron@gmail.com>
Cc: Corey Minyard <minyard@acm.org>,
Huacai Chen <chenhuacai@kernel.org>,
Binbin Zhou <zhoubinbin@loongson.cn>,
Xuerui Wang <kernel@xen0n.name>,
loongarch@lists.linux.dev, linux-kernel@vger.kernel.org,
openipmi-developer@lists.sourceforge.net, jeffbai@aosc.io,
kexybiscuit@aosc.io, wangyao@lemote.com
Subject: Re: (subset) [PATCH v11 0/3] LoongArch: Add Loongson-2K BMC support
Date: Tue, 16 Sep 2025 09:40:02 +0100 [thread overview]
Message-ID: <20250916084002.GF1637058@google.com> (raw)
In-Reply-To: <CAMpQs4JbQU3D-Bs2687BXSC=FKJBS6RMvWAKb6AJEtzit6hWqw@mail.gmail.com>
On Fri, 12 Sep 2025, Binbin Zhou wrote:
> Hi Lee:
>
> On Thu, Sep 11, 2025 at 10:33 PM Lee Jones <lee@kernel.org> wrote:
> >
> > On Thu, 04 Sep 2025 20:35:04 +0800, Binbin Zhou wrote:
> > > This patchset introduces the Loongson-2K BMC.
> > >
> > > It is a PCIe device present on servers similar to the Loongson-3 CPUs.
> > > And it is a multifunctional device (MFD), such as display as a sub-function
> > > of it.
> > >
> > > For IPMI, according to the existing design, we use software simulation to
> > > implement the KCS interface registers: Stauts/Command/Data_Out/Data_In.
> > >
> > > [...]
> >
> > Applied, thanks!
> >
> > [1/3] mfd: ls2kbmc: Introduce Loongson-2K BMC core driver
> > commit: 67c2639e1fc1a07b45d216af659c0dd92a370c68
> > [2/3] mfd: ls2kbmc: Add Loongson-2K BMC reset function support
> > commit: 2364ccc827e44064e9763f2ae2d1dcc5f945fdf3
>
> Thanks for acknowledging my patchset.
>
> I can't confirm why you didn't apply the IPMI patch, but this appears
> to break the patchset's integrity, potentially causing missing Kconfig
> dependencies (IPMI_LS2K select MFD_LS2K_BMC_CORE).
Pretty sure this doesn't break anything.
What build errors do you see as a result?
> Additionally, as Corey previously explained[1], this patch can be
> applied through your side.
>
> [1]: https://lore.kernel.org/all/aFVtNAY4u2gDiLDS@mail.minyard.net/
We only apply cross-subsystem patch-sets to a single tree if there are
good reasons to do so. In this instance, I can't see any reason why the
IPMI driver cannot go in via it's own repo.
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2025-09-16 8:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-04 12:35 [PATCH v11 0/3] LoongArch: Add Loongson-2K BMC support Binbin Zhou
2025-09-04 12:35 ` [PATCH v11 1/3] mfd: ls2kbmc: Introduce Loongson-2K BMC core driver Binbin Zhou
2025-09-04 12:35 ` [PATCH v11 2/3] mfd: ls2kbmc: Add Loongson-2K BMC reset function support Binbin Zhou
2025-09-04 12:35 ` [PATCH v11 3/3] ipmi: Add Loongson-2K BMC support Binbin Zhou
2025-09-11 14:33 ` (subset) [PATCH v11 0/3] LoongArch: " Lee Jones
2025-09-12 1:22 ` Binbin Zhou
2025-09-16 8:40 ` Lee Jones [this message]
2025-09-16 10:04 ` Binbin Zhou
2025-09-16 10:14 ` Lee Jones
2025-09-16 10:51 ` Binbin Zhou
2025-09-16 15:18 ` Corey Minyard
2025-09-16 16:08 ` Lee Jones
2025-09-16 23:20 ` Corey Minyard
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=20250916084002.GF1637058@google.com \
--to=lee@kernel.org \
--cc=chenhuacai@kernel.org \
--cc=jeffbai@aosc.io \
--cc=kernel@xen0n.name \
--cc=kexybiscuit@aosc.io \
--cc=linux-kernel@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=minyard@acm.org \
--cc=openipmi-developer@lists.sourceforge.net \
--cc=wangyao@lemote.com \
--cc=zhoubb.aaron@gmail.com \
--cc=zhoubinbin@loongson.cn \
/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