From: David Sterba <dsterba@suse.cz>
To: Anand Jain <anand.jain@oracle.com>
Cc: linux-btrfs@vger.kernel.org, Wolfgang_Mader@brain-frog.de,
dsterba@suse.cz
Subject: Re: [PATCH 1/2] Btrfs: log when missing device is created
Date: Tue, 5 May 2015 17:52:44 +0200 [thread overview]
Message-ID: <20150505155244.GL5099@twin.jikos.cz> (raw)
In-Reply-To: <1430109979-9397-2-git-send-email-anand.jain@oracle.com>
On Mon, Apr 27, 2015 at 12:46:18PM +0800, Anand Jain wrote:
> Signed-off-by: Anand Jain <anand.jain@oracle.com>
Reviewed-by: David Sterba <dsterba@suse.cz>
next prev parent reply other threads:[~2015-05-05 15:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-27 4:46 [PATCH 0/2] serviceability: add event log when missing device is created Anand Jain
2015-04-27 4:46 ` [PATCH 1/2] Btrfs: " Anand Jain
2015-05-05 15:52 ` David Sterba [this message]
2015-04-27 4:46 ` [PATCH 2/2] Btrfs: check error before reporting missing device and add uuid Anand Jain
2015-05-05 15:43 ` David Sterba
2015-05-07 20:34 ` Anand Jain
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=20150505155244.GL5099@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=Wolfgang_Mader@brain-frog.de \
--cc=anand.jain@oracle.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).