All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Liu <jeff.liu@oracle.com>
To: linux-btrfs@vger.kernel.org
Cc: anand.jain@oracle.com, miaox@cn.fujitsu.com,
	Goffredo Baroncelli <kreijack@dgmail.com>,
	dsterba@suse.cz
Subject: [RFC PATCH v9 0/2] Btrfs: get/set label for a mounted file system
Date: Sat, 05 Jan 2013 10:47:54 +0800	[thread overview]
Message-ID: <50E7945A.4000108@oracle.com> (raw)

Hello,

There have a couple of changes in this version which were shown as following:

- Don't reserve an unit of transactions for set filesystem label.

- Replace the old warning message to "btrfs: label is too long, return the first %zu bytes"
  in btrfs_ioc_get_fslabel() is the existing label length is longer than than
  BTRFS_LABEL_SIZE - 1. Otherwise, checkpatch.pl would give a warning as:
  "WARNING: quoted string split across lines".

- btrfs_ioc_set_fslabel(): drop an error message if the input label length is too long for
  debugging purpose.


The old versions can be found at:
v8:
http://permalink.gmane.org/gmane.comp.file-systems.btrfs/21906

v7:
http://www.spinics.net/lists/linux-btrfs/msg20994.html

v6:
http://www.spinics.net/lists/linux-btrfs/msg20922.html

v5:
http://www.spinics.net/lists/linux-btrfs/msg20888.html

v4:
http://permalink.gmane.org/gmane.comp.file-systems.btrfs/21618

v3:
https://patchwork.kernel.org/patch/1124642/

v2:
http://permalink.gmane.org/gmane.comp.file-systems.btrfs/12877

v1:
http://permalink.gmane.org/gmane.comp.file-systems.btrfs/12872

Thanks,
-Jeff

             reply	other threads:[~2013-01-05  2:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-05  2:47 Jeff Liu [this message]
2013-01-05  2:48 ` [RFC PATCH v9 1/2] Btrfs: Add a new ioctl to get the label of a mounted file system Jeff Liu
2013-01-06 18:44   ` Goffredo Baroncelli
2013-01-07  6:24     ` Jeff Liu
2013-01-07 17:32       ` Goffredo Baroncelli
2013-01-08  7:58         ` Jeff Liu
2013-01-05  2:48 ` [RFC PATCH v9 2/2] Btrfs: set/change " Jeff Liu
2013-01-06 18:32   ` Goffredo Baroncelli

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=50E7945A.4000108@oracle.com \
    --to=jeff.liu@oracle.com \
    --cc=anand.jain@oracle.com \
    --cc=dsterba@suse.cz \
    --cc=kreijack@dgmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=miaox@cn.fujitsu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.