All of lore.kernel.org
 help / color / mirror / Atom feed
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 16:35:12 +0200	[thread overview]
Message-ID: <1484058912.2133.22.camel@linux.intel.com> (raw)
In-Reply-To: <adfd384d-edb7-1255-f614-174a6793a2a8@nod.at>

On Tue, 2017-01-10 at 15:16 +0100, Richard Weinberger wrote:
> Am 10.01.2017 um 15:11 schrieb Andy Shevchenko:
> > On Tue, 2017-01-10 at 14:54 +0100, Richard Weinberger wrote:
> > > Am 10.01.2017 um 14:48 schrieb Andy Shevchenko:

> > > > Permissions 0000 are error prone.
> > > 
> > > Why?
> > 
> > Because of a trick is being used here.
> 
> You are not really the answering questions kind of guy? ;-)

You see, you have to keep in mind that you are not allowed to use
anything except 0 because parser is gone, variable is gone. I'm talking
about module_param_cb(..., 0) cases only.

> > P.S. If you strongly against it I will give up, it doesn't cost my
> > efforts anymore. That's why one of the possible "solution" is to put
> > comment there for other brave guys.

> 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.

-- 
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy

  reply	other threads:[~2017-01-10 14:35 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 [this message]
2017-01-10 15:31               ` Richard Weinberger
2017-01-10 15:38                 ` Andy Shevchenko

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=1484058912.2133.22.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.