public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: "Fejes József" <jozsef.fejes@gmail.com>,
	linux-kernel@vger.kernel.org, linux-stable@vger.kernel.org,
	"David E. Box" <david.e.box@linux.intel.com>
Subject: Re: Problem with commit: x86, iosf: Make IOSF driver modular and usable by more drivers
Date: Sat, 23 Aug 2014 10:40:14 -0700	[thread overview]
Message-ID: <53F8D1FE.5050205@infradead.org> (raw)
In-Reply-To: <CALU-w9-ZjjnrYW5HxRCe-HGZWSK0JMwNU_zcSbKXM4JgGyLdbw@mail.gmail.com>

On 08/23/14 02:31, Fejes József wrote:
> Hi,
> 
> I think there's a problem with commit
> 6b8f0c8780c71d78624f736d7849645b64cc88b7: config IOSF_MBI is
> automatically a module and I cannot change that.
> 
> I've been using 3.15.* stable kernels. I have module support enabled,
> but I build everything into the kernel, so I don't actually have any
> modules built. I just upgraded to 3.16.1, and found out that I now
> have this one module. I cannot find it in the menu, so I edited the
> .config file by hand, but it changes back from =y to =m. Could you
> please look into fixing it, and push it to 3.16.* stable branch?

[adding David E. Box to email]

This is a mainline issue, not just a -stable issue.
Once fixed in mainline (if ever), then that fix can be added to -stable.

Fejes, you could just disable module support and then iosf_mbi would be built
into the kernel.  But as a loadable module, it won't waste memory if it's
not needed.

David, any other suggestions?
Why can't the users of IOSF_MBI just select it?  That's what many other
drivers do when they need to be sure that some functionality is present.

I'm surprised that someone else (e.g. Linus) has not complained about the
'default m' for this driver.


-- 
~Randy

  reply	other threads:[~2014-08-23 17:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-23  9:31 Problem with commit: x86, iosf: Make IOSF driver modular and usable by more drivers Fejes József
2014-08-23 17:40 ` Randy Dunlap [this message]
2014-08-24 23:57   ` David E. Box
2014-08-25 19:02   ` One Thousand Gnomes

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=53F8D1FE.5050205@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=david.e.box@linux.intel.com \
    --cc=jozsef.fejes@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-stable@vger.kernel.org \
    /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