From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: WangYuli <wangyuli@uniontech.com>
Cc: airlied@gmail.com, akpm@linux-foundation.org,
alison.schofield@intel.com, andrew+netdev@lunn.ch,
andriy.shevchenko@linux.intel.com, bp@alien8.de,
brcm80211-dev-list.pdl@broadcom.com, brcm80211@lists.linux.dev,
colin.i.king@gmail.com, cvam0000@gmail.com,
dan.j.williams@intel.com, dave.hansen@linux.intel.com,
dave.jiang@intel.com, dave@stgolabs.net, davem@davemloft.net,
dri-devel@lists.freedesktop.org, edumazet@google.com,
gregkh@linuxfoundation.org, guanwentao@uniontech.com,
hpa@zytor.com, ilpo.jarvinen@linux.intel.com,
intel-xe@lists.freedesktop.org, ira.weiny@intel.com,
j@jannau.net, jeff.johnson@oss.qualcomm.com, jgross@suse.com,
jirislaby@kernel.org, johannes.berg@intel.com,
jonathan.cameron@huawei.com, kuba@kernel.org, kvalo@kernel.org,
kvm@vger.kernel.org, linux-cxl@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
linux-wireless@vger.kernel.org, linux@treblig.org,
lucas.demarchi@intel.com, marcin.s.wojtas@gmail.com,
ming.li@zohomail.com, mingo@kernel.org, mingo@redhat.com,
netdev@vger.kernel.org, niecheng1@uniontech.com,
oleksandr_tyshchenko@epam.com, pabeni@redhat.com,
pbonzini@redhat.com, quic_ramess@quicinc.com,
ragazenta@gmail.com, rodrigo.vivi@intel.com, seanjc@google.com,
shenlichuan@vivo.com, simona@ffwll.ch, sstabellini@kernel.org,
tglx@linutronix.de, thomas.hellstrom@linux.intel.com,
vishal.l.verma@intel.com, x86@kernel.org,
xen-devel@lists.xenproject.org, yujiaoliang@vivo.com,
zhanjun@uniontech.com
Subject: Re: [PATCH v2 5/8] wifi: brcmfmac: Fix typo "notifer"
Date: Fri, 18 Jul 2025 12:26:43 +0200 [thread overview]
Message-ID: <4445c7ec-a580-4c28-89cf-2df5790de6ac@broadcom.com> (raw)
In-Reply-To: <F92035B0A9123150+20250715134407.540483-5-wangyuli@uniontech.com>
On 7/15/2025 3:44 PM, WangYuli wrote:
> There is a spelling mistake of 'notifer' in the comment which
> should be 'notifier'.
>
> Link:https://lore.kernel.org/all/B3C019B63C93846F+20250715071245.398846-1-
> wangyuli@uniontech.com/
I think it has been said on other patches but it is not common to link
to obsolete version of the patch series. Apart from that:
Acked-by: Arend van Spriel <arend.vanspriel@broadcom.com>>
Signed-off-by: WangYuli<wangyuli@uniontech.com>
> ---
> drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
next prev parent reply other threads:[~2025-07-18 10:26 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-15 13:40 [PATCH v2 0/8] treewide: Fix typo "notifer" WangYuli
2025-07-15 13:44 ` [PATCH v2 1/8] KVM: x86: " WangYuli
2025-07-15 13:44 ` [PATCH v2 2/8] cxl: mce: " WangYuli
2025-07-15 13:48 ` Jonathan Cameron
2025-07-15 15:09 ` Dave Jiang
2025-07-15 13:44 ` [PATCH v2 3/8] drm/xe: " WangYuli
2025-07-23 18:40 ` Matthew Brost
2025-07-15 13:44 ` [PATCH v2 4/8] net: mvneta: " WangYuli
2025-07-16 7:36 ` Simon Horman
2025-07-15 13:44 ` [PATCH v2 5/8] wifi: brcmfmac: " WangYuli
2025-07-18 10:26 ` Arend van Spriel [this message]
2025-07-15 13:44 ` [PATCH v2 6/8] serial: 8250_dw: " WangYuli
2025-07-16 7:35 ` Andy Shevchenko
2025-07-16 8:08 ` Greg KH
2025-07-22 7:22 ` WangYuli
2025-07-22 7:57 ` Greg KH
2025-07-22 16:58 ` H. Peter Anvin
2025-07-15 13:44 ` [PATCH v2 7/8] xen/xenbus: " WangYuli
2025-07-18 13:36 ` Jürgen Groß
2025-07-15 13:44 ` [PATCH v2 8/8] scripts/spelling.txt: Add notifer||notifier to spelling.txt WangYuli
2025-07-15 13:50 ` Jonathan Cameron
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=4445c7ec-a580-4c28-89cf-2df5790de6ac@broadcom.com \
--to=arend.vanspriel@broadcom.com \
--cc=airlied@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=alison.schofield@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=andriy.shevchenko@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox