linux-bcache.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: Jan Kara <jack@suse.cz>, Jens Axboe <axboe@kernel.dk>,
	Christoph Hellwig <hch@infradead.org>,
	linux-block@vger.kernel.org, Coly Li <colyli@suse.de>,
	linux-bcache@vger.kernel.org
Subject: Re: [PATCH 1/2] bcache: Alloc holder object before async registration
Date: Thu, 22 Jun 2023 08:14:27 -0700	[thread overview]
Message-ID: <ZJRlU1/7mchdZyPF@infradead.org> (raw)
In-Reply-To: <20230622120548.molmqze2whj7ykj5@moria.home.lan>

On Thu, Jun 22, 2023 at 08:05:48AM -0400, Kent Overstreet wrote:
> Christoph - you really gotta start CCing people properly, the patch that
> broke this didn't even it linux-bcache. No bueno.

The series did absolutely go out to linux-bcache.  See here for v2:

https://lore.kernel.org/linux-bcache/20230608110258.189493-13-hch@lst.de/T/#u

  reply	other threads:[~2023-06-22 15:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-21 16:23 [PATCH 0/2] bcache: Fix block device claiming Jan Kara
2023-06-21 16:23 ` [PATCH 1/2] bcache: Alloc holder object before async registration Jan Kara
2023-06-21 17:56   ` Kent Overstreet
2023-06-22 10:09     ` Jan Kara
2023-06-22 12:05       ` Kent Overstreet
2023-06-22 15:14         ` Christoph Hellwig [this message]
2023-06-21 16:23 ` [PATCH 2/2] bcache: Fix bcache device claiming Jan Kara
2023-06-22  1:23   ` kernel test robot
2023-06-22 10:26     ` Jan Kara
2023-06-22  1:44   ` kernel test robot
2023-06-22  3:29   ` kernel test robot
2023-06-22 15:12   ` Christoph Hellwig

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=ZJRlU1/7mchdZyPF@infradead.org \
    --to=hch@infradead.org \
    --cc=axboe@kernel.dk \
    --cc=colyli@suse.de \
    --cc=jack@suse.cz \
    --cc=kent.overstreet@linux.dev \
    --cc=linux-bcache@vger.kernel.org \
    --cc=linux-block@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;
as well as URLs for NNTP newsgroup(s).