From: Greg KH <gregkh@linuxfoundation.org>
To: Sergei Shtepa <sergei.shtepa@veeam.com>
Cc: Christoph Hellwig <hch@infradead.org>,
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,
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:23:19 +0200 [thread overview]
Message-ID: <2023061204-jigsaw-punch-0e6a@gregkh> (raw)
In-Reply-To: <1bfc8c1d-f49a-2128-a457-4651832f3d2a@veeam.com>
On Mon, Jun 12, 2023 at 11:03:49AM +0200, Sergei Shtepa wrote:
>
>
> 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"?
It's a new version as you had to rebase it.
thanks,
greg k-h
prev parent reply other threads:[~2023-06-12 9:29 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
2023-06-12 9:23 ` Greg KH [this message]
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=2023061204-jigsaw-punch-0e6a@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=corbet@lwn.net \
--cc=dlemoal@kernel.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=sergei.shtepa@veeam.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;
as well as URLs for NNTP newsgroup(s).