From: Ralf Baechle <ralf@linux-mips.org>
To: Greg KH <greg@kroah.com>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
David Miller <davem@davemloft.net>,
akpm@linux-foundation.org, alan@linux.intel.com,
bcasavan@sgi.com, airlied@linux.ie, grundler@parisc-linux.org,
perex@perex.cz, rpurdie@rpsys.net,
klassert@mathematik.tu-chemnitz.de, tj@kernel.org,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
linux-mips@linux-mips.org, linux-scsi@vger.kernel.org,
linux-serial@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH 00/12] Fix various section mismatches and build errors.
Date: Wed, 29 Jun 2011 17:19:21 +0100 [thread overview]
Message-ID: <20110629161921.GA25833@linux-mips.org> (raw)
In-Reply-To: <20110629151424.GD18023@kroah.com>
On Wed, Jun 29, 2011 at 08:14:24AM -0700, Greg KH wrote:
>
> On Wed, Jun 29, 2011 at 08:58:19AM -0500, James Bottomley wrote:
> > I think we should simply concentrate on __init and __exit; that's where
> > most of the discard value lies and stop expending huge efforts on the
> > __devX stuff which adds huge complexity for no real gain.
>
> I have long felt that those __devX markings should just go away as they
> cause nothing but problems and have no real gain as you point out.
The suggestion to do that has been floated around before but seems to
have missed sufficient thrust. I'm all for it; the manual tagging with
__devX has not been very efficient on developer time. I just want to see
meaningful warnings again over all that noise the current mechanisn may
produce.
Ralf
next prev parent reply other threads:[~2011-06-29 16:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-26 11:19 [PATCH 00/12] Fix various section mismatches and build errors Ralf Baechle
2011-06-27 13:26 ` [PATCH 10/12] SERIAL: SC26xx: Fix link error Ralf Baechle
2011-06-28 8:25 ` Alan Cox
2011-06-28 5:12 ` [PATCH 00/12] Fix various section mismatches and build errors David Miller
2011-06-29 13:07 ` Ralf Baechle
2011-06-29 13:58 ` James Bottomley
2011-06-29 15:14 ` Greg KH
2011-06-29 16:19 ` Ralf Baechle [this message]
2011-06-29 17:24 ` 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=20110629161921.GA25833@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=airlied@linux.ie \
--cc=akpm@linux-foundation.org \
--cc=alan@linux.intel.com \
--cc=bcasavan@sgi.com \
--cc=davem@davemloft.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=greg@kroah.com \
--cc=grundler@parisc-linux.org \
--cc=klassert@mathematik.tu-chemnitz.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=perex@perex.cz \
--cc=rpurdie@rpsys.net \
--cc=tj@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;
as well as URLs for NNTP newsgroup(s).