From: Greg KH <gregkh@suse.de>
To: David Decotigny <david.decotigny@google.com>
Cc: Randy Dunlap <rdunlap@xenotime.net>,
Jason Wessel <jason.wessel@windriver.com>,
Rusty Russell <rusty@rustcorp.com.au>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
kgdb-bugreport@lists.sourceforge.net,
Michal Schmidt <mschmidt@redhat.com>,
Richard Kennedy <richard@rsk.demon.co.uk>,
Linus Walleij <linus.walleij@stericsson.com>,
Dmitry Torokhov <dtor@vmware.com>,
Kay Sievers <kay.sievers@vrfy.org>,
Lucas De Marchi <lucas.demarchi@profusion.mobi>,
Satoru Moriya <satoru.moriya@hds.com>
Subject: Re: [PATCH v2 3/3] param: make /sys/module/*/paramaters optional
Date: Wed, 2 Nov 2011 18:29:29 -0700 [thread overview]
Message-ID: <20111103012929.GA3449@suse.de> (raw)
In-Reply-To: <CAG88wWaZZj8k4KmgHdtYUiWQRcVTOaBDS0ik3bqj+VXzm5SQjQ@mail.gmail.com>
On Wed, Nov 02, 2011 at 04:02:24PM -0700, David Decotigny wrote:
> Thank you all for your feedback.
>
> FYI, this patch was meant to be an answer to a negative feedback I
> received when I proposed changing a few module_param(... perm=S_IRUGO)
> in forcedeth driver. But I agree the "price to pay" is very low.
Who gave you complaints about that? Really?
> Should I drop this patch?
Please do.
greg k-h
next prev parent reply other threads:[~2011-11-03 1:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-01 23:50 [PATCH v2 0/3] param: optional /sys/module/*/parameters David Decotigny
2011-11-01 23:50 ` [PATCH v2 1/3] param: make destroy_params() private David Decotigny
2011-11-01 23:50 ` [PATCH v2 2/3] param: simple refactoring David Decotigny
2011-11-01 23:50 ` [PATCH v2 3/3] param: make /sys/module/*/paramaters optional David Decotigny
2011-11-02 0:24 ` Greg KH
2011-11-02 23:02 ` David Decotigny
2011-11-03 1:29 ` Greg KH [this message]
2011-11-02 13:30 ` Jason Wessel
2011-11-02 16:24 ` [Kgdb-bugreport] " Tim Bird
2011-11-02 21:51 ` Rusty Russell
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=20111103012929.GA3449@suse.de \
--to=gregkh@suse.de \
--cc=david.decotigny@google.com \
--cc=dtor@vmware.com \
--cc=jason.wessel@windriver.com \
--cc=kay.sievers@vrfy.org \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linus.walleij@stericsson.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lucas.demarchi@profusion.mobi \
--cc=mschmidt@redhat.com \
--cc=rdunlap@xenotime.net \
--cc=richard@rsk.demon.co.uk \
--cc=rusty@rustcorp.com.au \
--cc=satoru.moriya@hds.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
Powered by JetHome