From: "Boy Wu (吳勃誼)" <Boy.Wu@mediatek.com>
To: "Markus.Elfring@web.de" <Markus.Elfring@web.de>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"cgroups@vger.kernel.org" <cgroups@vger.kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"boris@bur.io" <boris@bur.io>,
"axboe@kernel.dk" <axboe@kernel.dk>,
"Iverlin Wang (王苳霖)" <Iverlin.Wang@mediatek.com>,
"josef@toxicpanda.com" <josef@toxicpanda.com>,
"tj@kernel.org" <tj@kernel.org>,
"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
"angelogioacchino.delregno@collabora.com"
<angelogioacchino.delregno@collabora.com>
Subject: Re: blk-cgroup: add spin_lock for u64_stats_update
Date: Wed, 10 Jul 2024 06:19:07 +0000 [thread overview]
Message-ID: <9cd28aa03c353234c3ece1778e8d221d5c101217.camel@mediatek.com> (raw)
In-Reply-To: <9d07628a-eadd-4e50-b7a8-02adb25981ab@web.de>
On Mon, 2024-07-08 at 07:43 +0200, Markus Elfring wrote:
>
> External email : Please do not click links or open attachments until
> you have verified the sender or the content.
> > ************* MEDIATEK Confidentiality Notice ********************
> …
>
> Please omit such information from your patches for Linux software
> components.
> Such hints do probably not fit to communication characteristics of
> Linux mailing lists.
>
> Regards,
> Markus
The email system removing disclaimer is fixed. Can check with patch v2.
Boy.Wu
next prev parent reply other threads:[~2024-07-10 6:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-05 7:55 [PATCH] blk-cgroup: add spin_lock for u64_stats_update boy.wu
2024-07-05 17:05 ` Markus Elfring
2024-07-08 2:52 ` Boy Wu (吳勃誼)
2024-07-08 5:43 ` Markus Elfring
2024-07-10 6:19 ` Boy Wu (吳勃誼) [this message]
2024-07-05 17:13 ` [PATCH] " Tejun Heo
2024-07-08 2:00 ` Boy Wu (吳勃誼)
2024-07-08 18:36 ` tj
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=9cd28aa03c353234c3ece1778e8d221d5c101217.camel@mediatek.com \
--to=boy.wu@mediatek.com \
--cc=Iverlin.Wang@mediatek.com \
--cc=Markus.Elfring@web.de \
--cc=angelogioacchino.delregno@collabora.com \
--cc=axboe@kernel.dk \
--cc=boris@bur.io \
--cc=cgroups@vger.kernel.org \
--cc=josef@toxicpanda.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=tj@kernel.org \
/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