From: Takashi Iwai <tiwai@suse.de>
To: Ming Lei <ming.lei@canonical.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
Dave Jones <davej@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: dell_rbu: Select CONFIG_FW_LOADER_USER_HELPER explicitly
Date: Tue, 09 Jul 2013 16:45:03 +0200 [thread overview]
Message-ID: <s5h4nc3g5cg.wl%tiwai@suse.de> (raw)
In-Reply-To: <CACVXFVN-Qt8PP1YspX_M8H1W_-9Q-f8u1xPKcsqSWsqZqkhVyw@mail.gmail.com>
At Tue, 9 Jul 2013 22:39:36 +0800,
Ming Lei wrote:
>
> On Tue, Jul 9, 2013 at 9:32 PM, Takashi Iwai <tiwai@suse.de> wrote:
> > At Tue, 9 Jul 2013 16:43:30 +0800,
> >> Actually from view of distribution, dell rbu has to be compiled in, then
> >> no code size can be saved any more, which means looks the introduced
> >> option in this patch isn't necessary.
> >
> > Well, but it means that there is no way not to compile user-helper
> > mode code in firmware_class.c. In other words, in which condition,
> > request_firmware_user() will be compiled?
>
> It can be always compiled in. Basically dell rbu is always enabled in
> distributions, which means the user helper code has to be compiled in.
But how non-distro kernel disables this being built-in...?
Or do you suggest to enable the user-helper codes always built, no
matter whether it's used or not?
Takashi
next prev parent reply other threads:[~2013-07-09 14:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130702192749.A2E7E660D9B@gitolite.kernel.org>
2013-07-06 22:14 ` Dave Jones
2013-07-06 22:30 ` Greg KH
2013-07-08 9:05 ` Takashi Iwai
2013-07-08 16:49 ` Greg KH
2013-07-08 17:52 ` Takashi Iwai
2013-07-09 3:15 ` Ming Lei
2013-07-09 5:33 ` Takashi Iwai
2013-07-09 8:43 ` Ming Lei
2013-07-09 13:32 ` Takashi Iwai
2013-07-09 14:39 ` Ming Lei
2013-07-09 14:45 ` Takashi Iwai [this message]
2013-07-09 15:06 ` Ming Lei
2013-07-09 15:13 ` Takashi Iwai
2013-07-09 15:22 ` Ming Lei
2013-07-09 15:26 ` Takashi Iwai
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=s5h4nc3g5cg.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=davej@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@canonical.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
all inboxes | Powered by JetHome®