From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Richard Weinberger <richard@nod.at>
Cc: Artem Bityutskiy <dedekind1@gmail.com>,
Boris Brezillon <boris.brezillon@free-electrons.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
Brian Norris <computersforpeace@gmail.com>
Subject: Re: [PATCH v2 2/2] UBI: Make mtd parameter readable
Date: Tue, 10 Jan 2017 17:38:59 +0200 [thread overview]
Message-ID: <1484062739.2133.25.camel@linux.intel.com> (raw)
In-Reply-To: <da5b6bae-8416-45ac-5153-d1a479715793@nod.at>
On Tue, 2017-01-10 at 16:31 +0100, Richard Weinberger wrote:
> Andy,
>
> Am 10.01.2017 um 15:35 schrieb Andy Shevchenko:
> > > Did you check? Do other drivers in the kernel that have a parser
> > > behind a non-trivial
> > > module parameter also expose it to user space?
> >
> > Just checked. The only one which is not, this one.
> >
>
> That's an excellent reason. :-)
> But I see also:
> mtd/devices/phram.c:module_param_call(phram, phram_param_call, NULL,
> NULL, 000);
>
> If these two are the only users of 000, let's rip them out to be
> consistent
> with the rest of the kernel.
Okay, this is full(?) list of those. 3 drivers.
$ git grep -n 'module_param_call(.*, 0\+)' drivers/
drivers/ide/ide.c:277:module_param_call(chs, ide_set_disk_chs, NULL,
NULL, 0);
drivers/ide/ide.c:351:module_param_call(ignore_cable,
ide_set_ignore_cable, NULL, NULL, 0);
drivers/mtd/devices/phram.c:301:module_param_call(phram,
phram_param_call, NULL, NULL, 000);
drivers/platform/x86/thinkpad_acpi.c:9666: module_param_call(featur
e, set_ibm_param, NULL, NULL, 0); \
$ git grep -n 'module_param_cb(.*, 0\+)' drivers/
drivers/mtd/ubi/block.c:168:module_param_cb(block, &ubiblock_param_ops,
NULL, 0);
I doubt about worth to fix IDE (last time I sent clean up maintainer
told me not to do).
For thinkpad I will look at.
For MTD let's do it now.
So, would you like me to resend with / send separate fix to the other
one?
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
prev parent reply other threads:[~2017-01-10 15:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-10 12:56 [PATCH v2 1/2] UBI: Fix section mismatch Andy Shevchenko
2017-01-10 12:56 ` [PATCH v2 2/2] UBI: Make mtd parameter readable Andy Shevchenko
2017-01-10 13:33 ` Richard Weinberger
2017-01-10 13:48 ` Andy Shevchenko
2017-01-10 13:54 ` Richard Weinberger
2017-01-10 14:11 ` Andy Shevchenko
2017-01-10 14:16 ` Richard Weinberger
2017-01-10 14:35 ` Andy Shevchenko
2017-01-10 15:31 ` Richard Weinberger
2017-01-10 15:38 ` Andy Shevchenko [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=1484062739.2133.25.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.