From: "Coly Li" <colyli@fygo.io>
To: "Jing Wu" <realwujing@gmail.com>
Cc: <kent.overstreet@linux.dev>, <colyli@fnnas.com>,
<linux-bcache@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<yuanql9@chinatelecom.cn>, <akpm@linux-foundation.org>,
<kuba@kernel.org>, <brauner@kernel.org>, <eddyz87@gmail.com>
Subject: Re: [PATCH v3] bcache: avoid holding bch_register_lock across cache_set recovery
Date: Wed, 8 Jul 2026 19:35:23 +0800 [thread overview]
Message-ID: <ak4zj99pJClmDEva@studio.local> (raw)
In-Reply-To: <20260708084907.436861-1-realwujing@gmail.com>
On Wed, Jul 08, 2026 at 04:49:07PM +0800, Jing Wu wrote:
> On Wed, Jul 08, 2026 at 04:25:23PM +0800, Coly Li wrote:
> > On Mon, Jul 06, 2026 at 10:08:59PM +0800, Qiliang Yuan wrote:
> > > Large-scale bcache device registration and concurrent sysfs access can
> > > hang unrelated tasks for a long time, e.g.:
> > >
> > [snipped]
> >
> > >
> > > Co-developed-by: Qiliang Yuan <yuanql9@chinatelecom.cn>
> > > Signed-off-by: Qiliang Yuan <yuanql9@chinatelecom.cn>
> > > Signed-off-by: Jing Wu <realwujing@gmail.com>
> >
> > I just realize this patch was sent out by Qiliang Yuan, but the
> > email address is from realwujing@gmail.com which owned by Jing Wu.
> >
> > How and why does this happen?
>
> Jing Wu and Qiliang Yuan are on the same team. The git send-email
> configuration was mixed up when preparing this submission, and the
> patch ended up going out under the wrong author address. Apologies
> for the confusion.
>
> The solution itself is the result of team collaboration: both of
> us worked on the analysis, design, implementation and testing, so
> both Signed-off-bys are correct and intentional.
>
It seems all patches authored by Qiliang Yuan used realwujing@gmail.com
as the email address, even your name didn't show up in the patches.
Since you and Qiliang are in same team, why you didn't use
chinatelecom.cn email address in your SOB ?
This is not a common situation, so I need to make it clear for the
supply chain security reason.
Thanks.
Coly Li
next prev parent reply other threads:[~2026-07-08 11:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-06 14:08 [PATCH v3] bcache: avoid holding bch_register_lock across cache_set recovery Qiliang Yuan
2026-07-06 15:15 ` Coly Li
2026-07-07 1:51 ` Jing Wu
2026-07-07 12:29 ` Jing Wu
2026-07-08 8:25 ` Coly Li
2026-07-08 8:46 ` Jing Wu
2026-07-08 8:49 ` Jing Wu
2026-07-08 11:35 ` Coly Li [this message]
2026-07-08 11:40 ` Jing Wu
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=ak4zj99pJClmDEva@studio.local \
--to=colyli@fygo.io \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=colyli@fnnas.com \
--cc=eddyz87@gmail.com \
--cc=kent.overstreet@linux.dev \
--cc=kuba@kernel.org \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=realwujing@gmail.com \
--cc=yuanql9@chinatelecom.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