public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Brian Norris <computersforpeace@gmail.com>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: linux-kernel@vger.kernel.org,
	David Woodhouse <dwmw2@infradead.org>,
	Greg Ungerer <gerg@snapgear.com>,
	linux-mtd@lists.infradead.org
Subject: Re: [PATCH] drivers/mtd: make maps/uclinux.c driver more explicitly non-modular
Date: Tue, 26 Apr 2016 00:18:52 -0600	[thread overview]
Message-ID: <20160426061852.GC25981@localhost> (raw)
In-Reply-To: <1459095234-20386-1-git-send-email-paul.gortmaker@windriver.com>

On Sun, Mar 27, 2016 at 12:13:54PM -0400, Paul Gortmaker wrote:
> The Kconfig for this support is currently declared with:
> 
> config MTD_UCLINUX
>         bool "Generic uClinux RAM/ROM filesystem support"
> 
> ...meaning that it currently is not being built as a module by anyone.
> Lets remove as much of the modular evidence that we can, so that when
> reading the driver there is less doubt it is builtin-only.
> 
> Since module_init translates to device_initcall in the non-modular
> case, the init ordering remains unchanged with this commit.
> 
> We also replace module.h with moduleparam.h since the file does use
> a module_param,  and leaving it as such is currently the easiest way
> to remain compatible with existing boot arg use cases.
> 
> We also delete the MODULE_LICENSE tag etc. since all that information
> was (or is now) contained at the top of the file in the comments.
> 
> Cc: David Woodhouse <dwmw2@infradead.org>
> Cc: Brian Norris <computersforpeace@gmail.com>
> Cc: Greg Ungerer <gerg@snapgear.com>
> Cc: linux-mtd@lists.infradead.org
> Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>

Applied to l2-mtd.git

      reply	other threads:[~2016-04-26  6:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-27 16:13 [PATCH] drivers/mtd: make maps/uclinux.c driver more explicitly non-modular Paul Gortmaker
2016-04-26  6:18 ` Brian Norris [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=20160426061852.GC25981@localhost \
    --to=computersforpeace@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=gerg@snapgear.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=paul.gortmaker@windriver.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