From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: WangYuli <wangyuli@uniontech.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
seanjc@google.com, pbonzini@redhat.com, tglx@linutronix.de,
mingo@redhat.com, bp@alien8.de, dave.hansen@linux.intel.com,
x86@kernel.org, hpa@zytor.com, dave@stgolabs.net,
jonathan.cameron@huawei.com, dave.jiang@intel.com,
alison.schofield@intel.com, vishal.l.verma@intel.com,
ira.weiny@intel.com, dan.j.williams@intel.com,
lucas.demarchi@intel.com, thomas.hellstrom@linux.intel.com,
rodrigo.vivi@intel.com, airlied@gmail.com, simona@ffwll.ch,
marcin.s.wojtas@gmail.com, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, arend.vanspriel@broadcom.com,
ilpo.jarvinen@linux.intel.com, jirislaby@kernel.org,
jgross@suse.com, sstabellini@kernel.org,
oleksandr_tyshchenko@epam.com, akpm@linux-foundation.org,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
ming.li@zohomail.com, linux-cxl@vger.kernel.org,
intel-xe@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
netdev@vger.kernel.org, kvalo@kernel.org,
johannes.berg@intel.com, quic_ramess@quicinc.com,
ragazenta@gmail.com, jeff.johnson@oss.qualcomm.com,
mingo@kernel.org, j@jannau.net, linux@treblig.org,
linux-wireless@vger.kernel.org, brcm80211@lists.linux.dev,
brcm80211-dev-list.pdl@broadcom.com,
linux-serial@vger.kernel.org, xen-devel@lists.xenproject.org,
shenlichuan@vivo.com, yujiaoliang@vivo.com,
colin.i.king@gmail.com, cvam0000@gmail.com,
zhanjun@uniontech.com, niecheng1@uniontech.com,
guanwentao@uniontech.com
Subject: Re: [PATCH] treewide: Fix typo "notifer"
Date: Tue, 15 Jul 2025 10:59:26 +0300 [thread overview]
Message-ID: <aHYKXgc2k5wDY32c@smile.fi.intel.com> (raw)
In-Reply-To: <5D06C25920559D71+06c9ce34-9867-495c-9842-dcfe9f1d51bb@uniontech.com>
On Tue, Jul 15, 2025 at 03:53:18PM +0800, WangYuli wrote:
> On 2025/7/15 15:22, Greg KH wrote:
> > Please break this up into one-patch-per-subsystem, like is required for
> > things like this.
> Honestly, I've always been quite unsure how to handle situations like this.
>
> It seems every subsystem maintainer has different preferences.
True, but at least if you see the specific driver in the MAINTAINERS, split for
that driver. For instance, 8250_dw in this patch is exactly the case.
> I've previously encountered some maintainers who suggested I split such
> patches by subsystem so each maintainer could merge them into their tree
> without contention. However, other ones have argued that fixing spelling
> errors isn't worth multiple commits, claiming it would create chaos.
> Since I genuinely discover these spelling errors by chance each time, and to
> avoid giving the impression I'm "spamming" the kernel tree for some ulterior
> motive, I've opted to squash them into a single commit.
>
> That said, I personally don't have any strong feelings or preferences on
> this matter. Since you've requested it, I'll go ahead and split it up and
> send a v2 patchset.
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2025-07-15 7:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-15 7:12 [PATCH] treewide: Fix typo "notifer" WangYuli
2025-07-15 7:22 ` Greg KH
2025-07-15 7:53 ` WangYuli
2025-07-15 7:59 ` Andy Shevchenko [this message]
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=aHYKXgc2k5wDY32c@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=airlied@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=alison.schofield@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=arend.vanspriel@broadcom.com \
--cc=bp@alien8.de \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=brcm80211@lists.linux.dev \
--cc=colin.i.king@gmail.com \
--cc=cvam0000@gmail.com \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=davem@davemloft.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=edumazet@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=guanwentao@uniontech.com \
--cc=hpa@zytor.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=ira.weiny@intel.com \
--cc=j@jannau.net \
--cc=jeff.johnson@oss.qualcomm.com \
--cc=jgross@suse.com \
--cc=jirislaby@kernel.org \
--cc=johannes.berg@intel.com \
--cc=jonathan.cameron@huawei.com \
--cc=kuba@kernel.org \
--cc=kvalo@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linux@treblig.org \
--cc=lucas.demarchi@intel.com \
--cc=marcin.s.wojtas@gmail.com \
--cc=ming.li@zohomail.com \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=niecheng1@uniontech.com \
--cc=oleksandr_tyshchenko@epam.com \
--cc=pabeni@redhat.com \
--cc=pbonzini@redhat.com \
--cc=quic_ramess@quicinc.com \
--cc=ragazenta@gmail.com \
--cc=rodrigo.vivi@intel.com \
--cc=seanjc@google.com \
--cc=shenlichuan@vivo.com \
--cc=simona@ffwll.ch \
--cc=sstabellini@kernel.org \
--cc=tglx@linutronix.de \
--cc=thomas.hellstrom@linux.intel.com \
--cc=vishal.l.verma@intel.com \
--cc=wangyuli@uniontech.com \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xenproject.org \
--cc=yujiaoliang@vivo.com \
--cc=zhanjun@uniontech.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.