From: Jens Axboe <axboe@kernel.dk>
To: Stephen Zhang <starzhangzsd@gmail.com>
Cc: Coly Li <colyli@fnnas.com>,
Kent Overstreet <kent.overstreet@linux.dev>,
Sasha Levin <sashal@kernel.org>,
Christoph Hellwig <hch@infradead.org>,
linux-bcache@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
zhangshida <zhangshida@kylinos.cn>
Subject: Re: Fwd: [PATCH v3] bcache: use bio cloning for detached device requests
Date: Wed, 21 Jan 2026 19:22:44 -0700 [thread overview]
Message-ID: <0a1bd601-7f66-428e-ae1a-4972f383258f@kernel.dk> (raw)
In-Reply-To: <CANubcdUPFU_75YkNORATSFdn05_UeXbm4w90OuJMg1TZj=z5dw@mail.gmail.com>
On 1/21/26 7:20 PM, Stephen Zhang wrote:
> Jens Axboe <axboe@kernel.dk> 于2026年1月22日周四 10:08写道:
>>
>> On 1/21/26 6:40 PM, Stephen Zhang wrote:
>>> ---------- Forwarded message ---------
>>
>> Can you please just send it out as a regular patch? The forward has
>> complete whitespace damage (it's all spaces, no tabs), and when you
>> forward, b4 doesn't pick it up either. Maybe there's some reason for
>> why you are doing these as forwards, if so do tell?
>>
>
> Apologies for the formatting issues with the forwarded patch. When I try
> using git send-email, I'm encountering server rejection issues.
> Interestingly, I found that if I cut the patch content in half, it goes
> through without rejection. This suggests there may be a size limit or
> specific content filter causing the problem.
>
> I'm investigating which part triggers the rejection and will resend the
> patch properly once resolved.
Can you put it in a git tree? Your original patches seem to have been
applied by Coly just fine, so maybe just go that route again?
--
Jens Axboe
next prev parent reply other threads:[~2026-01-22 2:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260122013650.321766-1-zhangshida@kylinos.cn>
2026-01-22 1:40 ` Fwd: [PATCH v3] bcache: use bio cloning for detached device requests Stephen Zhang
2026-01-22 2:08 ` Jens Axboe
2026-01-22 2:20 ` Stephen Zhang
2026-01-22 2:22 ` Jens Axboe [this message]
2026-01-22 3:25 ` Coly Li
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=0a1bd601-7f66-428e-ae1a-4972f383258f@kernel.dk \
--to=axboe@kernel.dk \
--cc=colyli@fnnas.com \
--cc=hch@infradead.org \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=starzhangzsd@gmail.com \
--cc=zhangshida@kylinos.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