From: Christoph Hellwig <hch@infradead.org>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Christoph Hellwig <hch@infradead.org>, xfs-oss <xfs@oss.sgi.com>
Subject: Re: [PATCH V2] xfs: be more explicit if RT mount fails due to config
Date: Fri, 30 Apr 2010 12:45:43 -0400 [thread overview]
Message-ID: <20100430164543.GA4753@infradead.org> (raw)
In-Reply-To: <4BDB08C4.6070900@sandeen.net>
On Fri, Apr 30, 2010 at 11:43:48AM -0500, Eric Sandeen wrote:
> Recent testers were slightly confused that a realtime
> mount failed due to missing CONFIG_XFS_RT; we can make
> that a little more obvious.
>
> V2: drop the else as suggested by Christoph
>
> Signed-off-by: Eric Sandeen <sandeen@sandeen.net>
Looks good,
Reviewed-by: Christoph Hellwig <hch@lst.de>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2010-04-30 16:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-30 3:55 [PATCH] xfs: be more explicit if RT mount fails due to config Eric Sandeen
2010-04-30 16:40 ` Christoph Hellwig
2010-04-30 16:43 ` [PATCH V2] " Eric Sandeen
2010-04-30 16:45 ` Christoph Hellwig [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=20100430164543.GA4753@infradead.org \
--to=hch@infradead.org \
--cc=sandeen@sandeen.net \
--cc=xfs@oss.sgi.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