From: Kalle Valo <kvalo@kernel.org>
To: Yunbo Yu <yuyunbo519@gmail.com>
Cc: nbd@nbd.name, lorenzo@kernel.org, ryder.lee@mediatek.com,
shayne.chen@mediatek.com, sean.wang@mediatek.com,
davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
matthias.bgg@gmail.com, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mt76：mt7603： move spin_lock_bh() to spin_lock()
Date: Fri, 22 Apr 2022 09:12:28 +0300 [thread overview]
Message-ID: <87y1zxmysz.fsf@kernel.org> (raw)
In-Reply-To: <20220422060723.424862-1-yuyunbo519@gmail.com> (Yunbo Yu's message of "Fri, 22 Apr 2022 14:07:23 +0800")
Yunbo Yu <yuyunbo519@gmail.com> writes:
> It is unnecessary to call spin_lock_bh(), for you are already in a tasklet.
>
> Signed-off-by: Yunbo Yu <yuyunbo519@gmail.com>
Why do you use unicode character "=EF=BC=9A"[1] as colon in the title?
After all recent news about left-to-right trickery all special
characters make me suspicious.
https://www.fileformat.info/info/unicode/char/ff1a/index.htm
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@kernel.org>
To: Yunbo Yu <yuyunbo519@gmail.com>
Cc: nbd@nbd.name, lorenzo@kernel.org, ryder.lee@mediatek.com,
shayne.chen@mediatek.com, sean.wang@mediatek.com,
davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
matthias.bgg@gmail.com, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mt76：mt7603： move spin_lock_bh() to spin_lock()
Date: Fri, 22 Apr 2022 09:12:28 +0300 [thread overview]
Message-ID: <87y1zxmysz.fsf@kernel.org> (raw)
In-Reply-To: <20220422060723.424862-1-yuyunbo519@gmail.com> (Yunbo Yu's message of "Fri, 22 Apr 2022 14:07:23 +0800")
Yunbo Yu <yuyunbo519@gmail.com> writes:
> It is unnecessary to call spin_lock_bh(), for you are already in a tasklet.
>
> Signed-off-by: Yunbo Yu <yuyunbo519@gmail.com>
Why do you use unicode character "=EF=BC=9A"[1] as colon in the title?
After all recent news about left-to-right trickery all special
characters make me suspicious.
https://www.fileformat.info/info/unicode/char/ff1a/index.htm
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@kernel.org>
To: Yunbo Yu <yuyunbo519@gmail.com>
Cc: nbd@nbd.name, lorenzo@kernel.org, ryder.lee@mediatek.com,
shayne.chen@mediatek.com, sean.wang@mediatek.com,
davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
matthias.bgg@gmail.com, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mt76：mt7603： move spin_lock_bh() to spin_lock()
Date: Fri, 22 Apr 2022 09:12:28 +0300 [thread overview]
Message-ID: <87y1zxmysz.fsf@kernel.org> (raw)
In-Reply-To: <20220422060723.424862-1-yuyunbo519@gmail.com> (Yunbo Yu's message of "Fri, 22 Apr 2022 14:07:23 +0800")
Yunbo Yu <yuyunbo519@gmail.com> writes:
> It is unnecessary to call spin_lock_bh(), for you are already in a tasklet.
>
> Signed-off-by: Yunbo Yu <yuyunbo519@gmail.com>
Why do you use unicode character "=EF=BC=9A"[1] as colon in the title?
After all recent news about left-to-right trickery all special
characters make me suspicious.
https://www.fileformat.info/info/unicode/char/ff1a/index.htm
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-04-22 6:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 6:07 [PATCH] mt76：mt7603： move spin_lock_bh() to spin_lock() Yunbo Yu
2022-04-22 6:07 ` Yunbo Yu
2022-04-22 6:07 ` Yunbo Yu
2022-04-22 6:12 ` Kalle Valo [this message]
2022-04-22 6:12 ` Kalle Valo
2022-04-22 6:12 ` Kalle Valo
[not found] ` <CAD55h6Z0GfEMu25_1PXavRA9SGJ2zZC4-y=6Bo5+Fz=99J6_mg@mail.gmail.com>
2022-04-22 7:13 ` Kalle Valo
2022-04-22 7:13 ` Kalle Valo
2022-04-22 7:13 ` Kalle Valo
-- strict thread matches above, loose matches on Subject: below --
2022-04-18 8:18 Yunbo Yu
2022-04-18 8:18 ` Yunbo Yu
2022-04-18 8:18 ` Yunbo Yu
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=87y1zxmysz.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lorenzo@kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=nbd@nbd.name \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=ryder.lee@mediatek.com \
--cc=sean.wang@mediatek.com \
--cc=shayne.chen@mediatek.com \
--cc=yuyunbo519@gmail.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.