From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: James Bottomley <James.Bottomley@hansenpartnership.com>
Cc: <fengguang.wu@intel.com>,
"James E.J. Bottomley" <jejb@parisc-linux.org>,
Helge Deller <deller@gmx.de>, <linux-parisc@vger.kernel.org>
Subject: Re: [PATCH] parisc: don't use module_init for non-modular core pdc_cons code
Date: Wed, 22 Jan 2014 14:33:04 -0500 [thread overview]
Message-ID: <52E01CF0.4040307@windriver.com> (raw)
In-Reply-To: <1390418450.2372.83.camel@dabdike.int.hansenpartnership.com>
On 14-01-22 02:20 PM, James Bottomley wrote:
> On Wed, 2014-01-22 at 13:19 -0500, Paul Gortmaker wrote:
>> The pdc_cons.c code is always built in. It will never be modular,
>> so using module_init as an alias for __initcall is rather
>> misleading.
>>
>> Fix this up now, so that we can relocate module_init from
>> init.h into module.h in the future. If we don't do this, we'd
>> have to add module.h to obviously non-modular code, and that
>> would be a worse thing.
>
> I don't buy this. We've already had an argument about using MODULE_
> tags in non-modular code here:
>
> http://marc.info/?t=138947344500007
>
> The consensus was that we'd continue to do so, so that would seem to
> invalidate the rationale for doing this patch set.
>
> Without the rationale, this is churn for no gain, so I'd rather not do
> it.
Hi James,
Thanks for the link. Here is another one.
https://lkml.org/lkml/2014/1/21/434
In there I explain the rationale for doing this and what value add we
get from it. Perhaps you'll say those things aren't important, and
then I guess we'll have to agree to disagree then... but I hope not.
Thanks,
Paul.
--
>
> Thanks,
>
> James
>
>
next prev parent reply other threads:[~2014-01-22 19:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <52df8b79.riaKReY/RZZi2qvy%fengguang.wu@intel.com>
2014-01-22 18:19 ` [PATCH] parisc: don't use module_init for non-modular core pdc_cons code Paul Gortmaker
2014-01-22 19:20 ` James Bottomley
2014-01-22 19:33 ` Paul Gortmaker [this message]
2014-01-22 19:57 ` James Bottomley
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=52E01CF0.4040307@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=deller@gmx.de \
--cc=fengguang.wu@intel.com \
--cc=jejb@parisc-linux.org \
--cc=linux-parisc@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 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.