public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcos Paulo de Souza <mpdesouza@suse.de>
To: dsterba@suse.cz, Marcos Paulo de Souza <marcos.souza.org@gmail.com>
Cc: dsterba@suse.com, wqu@suse.com, linux-btrfs@vger.kernel.org,
	hch@infradead.org, josef@toxicpanda.com,
	Marcos Paulo de Souza <mpdesouza@suse.com>
Subject: Re: [PATCHv3] btrfs: Introduce new BTRFS_IOC_SNAP_DESTROY_V2 ioctl
Date: Fri, 21 Feb 2020 13:05:20 -0300	[thread overview]
Message-ID: <90b60b225c4775e7b2df6956b508f53ce2a68708.camel@suse.de> (raw)
In-Reply-To: <20200221144426.GJ2902@twin.jikos.cz>

On Fri, 2020-02-21 at 15:44 +0100, David Sterba wrote:
> On Fri, Feb 07, 2020 at 10:05:46AM -0300, Marcos Paulo de Souza
> wrote:
> > Also in this patch:
> > * export get_subvol_name_from_objectid, adding btrfs suffix
> 
> I've split this part from the patch so the actual change is only the
> new
> ioctl

Good, thanks.

> 
> > * add BTRFS_SUBVOL_SPEC_BY_ID flag
> > * add subvolid as a union member in struct btrfs_ioctl_vol_args_v2.
> 
> and ported the patch on top of the vol args flag cleanups I sent
> today.
> This should be all the kernel side needs for the subvolume by-id
> deletion. The patches will be in for-next and moved to misc-next
> soon.

Thanks! 

> Thanks.


      reply	other threads:[~2020-02-21 16:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-07 13:05 [PATCHv3] btrfs: Introduce new BTRFS_IOC_SNAP_DESTROY_V2 ioctl Marcos Paulo de Souza
2020-02-10 23:41 ` Nathan Chancellor
2020-02-11 18:57   ` Marcos Paulo de Souza
2020-02-11 19:39     ` David Sterba
2020-02-21 14:44 ` David Sterba
2020-02-21 16:05   ` Marcos Paulo de Souza [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=90b60b225c4775e7b2df6956b508f53ce2a68708.camel@suse.de \
    --to=mpdesouza@suse.de \
    --cc=dsterba@suse.com \
    --cc=dsterba@suse.cz \
    --cc=hch@infradead.org \
    --cc=josef@toxicpanda.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=marcos.souza.org@gmail.com \
    --cc=mpdesouza@suse.com \
    --cc=wqu@suse.com \
    /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