From: Coly Li <colyli@suse.de>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-raid <linux-raid@vger.kernel.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: bcache patches for Linux v5.18
Date: Sun, 6 Mar 2022 22:55:36 +0800 [thread overview]
Message-ID: <3b93c0db-316e-d227-e98e-be7a6f4e2907@suse.de> (raw)
In-Reply-To: <c94f9c70-7052-0bae-ca0e-9b9ccc48c46b@kernel.dk>
On 3/6/22 10:17 PM, Jens Axboe wrote:
> On 3/6/22 3:35 AM, Coly Li wrote:
>> Hi Jens,
>>
>> I have technical problem to send patches via email this time, please
>> consider to pull the bcache changes from my bcache tree. They can be
>> applied on top of your for-5.18/drivers branch.
>>
>> We have 2 patches for Linux v5.18, both of them are from Mingzhe Zou.
>> The first patch improves bcache initialization speed by avoid
>> unnecessary cost of cache consistency, the second one fixes a
>> potential NULL pointer deference in bcache initialization time,
>>
>> Please take them for Linux v5.18, thanks in advance.
> I can take a git pull, but don't base it on something that isn't a tree
> of mine. If I pull your branch right now, I'll get a ton of unrelated
> changes.
I see, my for-next branch is not 100% clone the for-5.18/drivers branch,
although the patches are verified on top of it.
> If you want to do a git pull vs sending patches, base it on
> for-5.18/drivers instead.
>
Copied. Now I pull my for-next branch from your for-5.18/drivers branch,
and they are same, and the two patches are added on top of it.
Here is the updated pull request, could you please try it again? Thanks.
The following changes since commit 13d4ef0f66b7ee9415e101e213acaf94a0cb28ee:
floppy: use memcpy_{to,from}_bvec (2022-03-04 12:29:21 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/colyli/linux-bcache.git
for-next
for you to fetch changes up to 887554ab96588de2917b6c8c73e552da082e5368:
bcache: fixup multiple threads crash (2022-03-06 22:33:45 +0800)
----------------------------------------------------------------
Mingzhe Zou (2):
bcache: fixup bcache_dev_sectors_dirty_add() multithreaded CPU
false sharing
bcache: fixup multiple threads crash
drivers/md/bcache/btree.c | 6 ++++--
drivers/md/bcache/writeback.c | 17 +++++++++++------
2 files changed, 15 insertions(+), 8 deletions(-)
next prev parent reply other threads:[~2022-03-06 14:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-06 10:35 bcache patches for Linux v5.18 Coly Li
2022-03-06 14:17 ` Jens Axboe
2022-03-06 14:55 ` Coly Li [this message]
2022-03-06 15:15 ` Jens Axboe
2022-03-06 15:53 ` 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=3b93c0db-316e-d227-e98e-be7a6f4e2907@suse.de \
--to=colyli@suse.de \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-raid@vger.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