linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: clm@fb.com
Cc: David Sterba <dsterba@suse.cz>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 3.19-rc] btrfs: add read-only check to sysfs handler of features
Date: Fri, 30 Jan 2015 18:08:30 +0100	[thread overview]
Message-ID: <20150130170830.GO3641@twin.jikos.cz> (raw)
In-Reply-To: <1422035531-22930-1-git-send-email-dsterba@suse.cz>

On Fri, Jan 23, 2015 at 06:52:11PM +0100, David Sterba wrote:
> We don't want to trigger the change on a read-only filesystem, similar
> to what the label handler does.
> 
> Signed-off-by: David Sterba <dsterba@suse.cz>

Please drop this patch, seems that the right way to the ro/rw & freeze
protection is to use sb_start_write & co.

      reply	other threads:[~2015-01-30 17:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-23 17:52 [PATCH 3.19-rc] btrfs: add read-only check to sysfs handler of features David Sterba
2015-01-30 17:08 ` David Sterba [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=20150130170830.GO3641@twin.jikos.cz \
    --to=dsterba@suse.cz \
    --cc=clm@fb.com \
    --cc=linux-btrfs@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).