From: Kay Sievers <kay.sievers@vrfy.org>
To: Peter Korsgaard <jacmet@sunsite.dk>
Cc: Michael Tokarev <mjt@tls.msk.ru>,
gregkh@suse.de, linux-kernel@vger.kernel.org,
linux-embedded@vger.kernel.org
Subject: Re: [PATCH] devtmpfs: support !CONFIG_TMPFS
Date: Fri, 12 Mar 2010 14:02:57 +0100 [thread overview]
Message-ID: <ac3eb2511003120502y2953ff0au81ee5c4d76261a87@mail.gmail.com> (raw)
In-Reply-To: <87aaud22jj.fsf@macbook.be.48ers.dk>
On Fri, Mar 12, 2010 at 12:38, Peter Korsgaard <jacmet@sunsite.dk> wrote:
>>>>>> "Michael" == Michael Tokarev <mjt@tls.msk.ru> writes:
> >> +#ifdef CONFIG_TMPFS
> >> return get_sb_single(fs_type, flags, data, shmem_fill_super, mnt);
> >> +#else
> >> + return get_sb_single(fs_type, flags, data, ramfs_fill_super, mnt);
> >> +#endif
> >> }
>
> Michael> May be completely not to the point or even wrong, but I were
> Michael> starring at this change for quite some time trying to understand
> Michael> what's the difference. Can we do it like this:
>
> Michael> #ifdef CONFIG_TMPFS
> Michael> # define devtmpfs_fill_super shmem_fill_super
> Michael> #else
> Michael> # define devtmpfs_fill_super ramfs_fill_super
> Michael> #endif
> Michael> return get_sb_single(fs_type, flags, data, devtmpfs_fill_super, mnt);
> Sure, if people find that cleaner - Kay?
For the style:
I would prefer your original version.
For the patch:
Acked-by: Kay Sievers <kay.sievers@vrfy.org>
Thanks,
Kay
next prev parent reply other threads:[~2010-03-12 13:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-12 10:25 [PATCH] devtmpfs: support !CONFIG_TMPFS Peter Korsgaard
2010-03-12 11:28 ` Michael Tokarev
2010-03-12 11:38 ` Peter Korsgaard
2010-03-12 13:02 ` Kay Sievers [this message]
2010-03-16 13:04 ` Peter Korsgaard
2010-03-16 13:37 ` Greg KH
2010-03-16 19:00 ` Greg KH
2010-03-16 19:14 ` Peter Korsgaard
2010-03-16 20:17 ` Greg KH
2010-03-16 20:55 ` [PATCH-V2] " Peter Korsgaard
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=ac3eb2511003120502y2953ff0au81ee5c4d76261a87@mail.gmail.com \
--to=kay.sievers@vrfy.org \
--cc=gregkh@suse.de \
--cc=jacmet@sunsite.dk \
--cc=linux-embedded@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjt@tls.msk.ru \
/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).