linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Mason <clm@fb.com>
To: Dan Carpenter <dan.carpenter@oracle.com>, <harald@redhat.com>
Cc: <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs: allow mounting btrfs subvolumes with different ro/rw options
Date: Mon, 14 Apr 2014 09:39:02 -0400	[thread overview]
Message-ID: <534BE4F6.9050300@fb.com> (raw)
In-Reply-To: <20140414131010.GA12764@mwanda>



On 04/14/2014 09:10 AM, Dan Carpenter wrote:
> Hello Harald Hoyer,
>
> The patch 0723a0473fb4: "btrfs: allow mounting btrfs subvolumes with
> different ro/rw options" from Nov 19, 2013, leads to the following
> static checker warning:

I'll fix this one up.  Harald's email has changed and I should have 
pulled the patch in long ago.

Thanks Dan!

-chris

  reply	other threads:[~2014-04-14 13:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-14 13:10 btrfs: allow mounting btrfs subvolumes with different ro/rw options Dan Carpenter
2014-04-14 13:39 ` Chris Mason [this message]
2014-04-14 16:17   ` David Sterba
2014-04-14 17:08     ` Dan Carpenter

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=534BE4F6.9050300@fb.com \
    --to=clm@fb.com \
    --cc=dan.carpenter@oracle.com \
    --cc=harald@redhat.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).