From: "Robert P. J. Day" <rpjday@mindspring.com>
To: David Rientjes <rientjes@google.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] Extract common MODULE_INFO content into new moduleinfo.h.
Date: Sun, 20 May 2007 13:15:54 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0705201314590.22771@localhost.localdomain> (raw)
In-Reply-To: <alpine.DEB.0.99.0705200934580.30819@chino.kir.corp.google.com>
On Sun, 20 May 2007, David Rientjes wrote:
> On Sun, 20 May 2007, Robert P. J. Day wrote:
>
> > i can do that as long as there's no way that those changes can
> > (even theoretically) make a difference in the build. in order to
> > make sure this patch didn't break anything, i went with a straight
> > cut-and-paste of the content to go into the new moduleinfo.h.
>
> __attribute_used__ is pointless outside of function definitions so
> the way it is currently written is incorrect.
>
> > so while i agree that those changes shouldn't hurt, personally,
> > i'd prefer to just put this patch through as is and come back
> > later to do any tidying related to attribute rewording.
>
> __attribute_used__ is deprecated so it would be helpful to change it
> now instead of requiring a second patch. It's better if new patches
> no longer use a deprecated attribute.
fair enough. i'll submit a revised patch shortly.
rday
p.s. um ... just off-hand, i'm hoping that people understand the
rationale behind this patch.
--
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA
http://fsdev.net/wiki/index.php?title=Main_Page
========================================================================
prev parent reply other threads:[~2007-05-20 17:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-20 7:57 Robert P. J. Day
2007-05-20 8:47 ` David Rientjes
2007-05-20 10:28 ` Robert P. J. Day
2007-05-20 16:38 ` David Rientjes
2007-05-20 17:15 ` Robert P. J. Day [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=Pine.LNX.4.64.0705201314590.22771@localhost.localdomain \
--to=rpjday@mindspring.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rientjes@google.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®