Linux block layer
 help / color / mirror / Atom feed
From: Sergei Shtepa <sergei.shtepa@veeam.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: <axboe@kernel.dk>, <corbet@lwn.net>, <snitzer@kernel.org>,
	<viro@zeniv.linux.org.uk>, <brauner@kernel.org>,
	<willy@infradead.org>, <dlemoal@kernel.org>, <wsa@kernel.org>,
	<heikki.krogerus@linux.intel.com>, <ming.lei@redhat.com>,
	<gregkh@linuxfoundation.org>, <linux-block@vger.kernel.org>,
	<linux-doc@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH v4 00/11] blksnap - block devices snapshots module
Date: Mon, 12 Jun 2023 11:03:49 +0200	[thread overview]
Message-ID: <1bfc8c1d-f49a-2128-a457-4651832f3d2a@veeam.com> (raw)
In-Reply-To: <ZIaVz62ntyrhHdup@infradead.org>



On 6/12/23 05:49, Christoph Hellwig wrote:
> Hi Sergei,
> 
> what tree does this apply to?  New block infrastructure and drivers
> should be against Jen's for-6.5/block tree, and trying to apply the
> series against that seems to fail in patch 1 already.
> 

Hi.

Thank you. My mistake is that for the base branch I used this:
Link: https://github.com/torvalds/linux

> Jen's for-6.5/block tree
Link: https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git/log/?h=for-6.5/block
I have to prepare a patch for this branch.

I'm sorry if I remind you of a kitten who is just learning how to
properly lap milk from a bowl :)

I guess I don't need to increment the patch version.
Is it enough to do a "RESEND"?

  reply	other threads:[~2023-06-12  9:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-09 11:51 [PATCH v4 00/11] blksnap - block devices snapshots module Sergei Shtepa
2023-06-12  3:49 ` Christoph Hellwig
2023-06-12  9:03   ` Sergei Shtepa [this message]
2023-06-12  9:23     ` Greg KH

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=1bfc8c1d-f49a-2128-a457-4651832f3d2a@veeam.com \
    --to=sergei.shtepa@veeam.com \
    --cc=axboe@kernel.dk \
    --cc=brauner@kernel.org \
    --cc=corbet@lwn.net \
    --cc=dlemoal@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hch@infradead.org \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ming.lei@redhat.com \
    --cc=snitzer@kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    --cc=willy@infradead.org \
    --cc=wsa@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