All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org,
	Rusty Russell <rusty@rustcorp.com.au>,
	Jim Cromie <jim.cromie@gmail.com>,
	Borislav Petkov <borislav.petkov@amd.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Andi Kleen <ak@linux.intel.com>, Michal Marek <mmarek@suse.cz>,
	Tony Lindgren <tony@atomide.com>,
	Jonathan Kliegman <kliegs@chromium.org>,
	Chris Zankel <chris@zankel.net>,
	Bill Pemberton <wfp5p@viridian.itc.virginia.edu>,
	Fengguang Wu <fengguang.wu@intel.com>,
	linux-kbuild <linux-kbuild@vger.kernel.org>
Subject: Re: [PATCH 1/2] modpost.c: Stop checking __dev* section mismatches
Date: Fri, 30 Nov 2012 19:13:20 +0100	[thread overview]
Message-ID: <20121130181320.GB18287@merkur.ravnborg.org> (raw)
In-Reply-To: <20121129184502.GC15110@kroah.com>

On Thu, Nov 29, 2012 at 10:45:02AM -0800, Greg Kroah-Hartman wrote:
> From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> 
> Now that the __dev* sections are not being generated, we don't need to
> check for them in modpost.c.
> 
> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Acked-by: Sam Ravnborg <sam@ravnborg.org>

  reply	other threads:[~2012-11-30 18:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-29 18:41 [PATCH 0/2] Remove __dev* sections from the kernel Greg Kroah-Hartman
2012-11-29 18:43 ` [PATCH 1/2] init.h: " Greg Kroah-Hartman
2012-11-29 18:45   ` [PATCH 1/2] modpost.c: Stop checking __dev* section mismatches Greg Kroah-Hartman
2012-11-30 18:13     ` Sam Ravnborg [this message]
2012-11-30 18:11   ` [PATCH 1/2] init.h: Remove __dev* sections from the kernel Sam Ravnborg
2012-11-30 18:28     ` Greg Kroah-Hartman
2012-11-30 20:39   ` H. Peter Anvin
2012-11-30 20:43     ` Bill Pemberton
2012-11-30 20:43       ` Bill Pemberton
2012-11-30 20:45     ` Greg Kroah-Hartman
2012-11-30 20:39   ` H. Peter Anvin
2012-11-30 20:47     ` Greg Kroah-Hartman

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=20121130181320.GB18287@merkur.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=ak@linux.intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=borislav.petkov@amd.com \
    --cc=chris@zankel.net \
    --cc=fengguang.wu@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jim.cromie@gmail.com \
    --cc=kliegs@chromium.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mmarek@suse.cz \
    --cc=rusty@rustcorp.com.au \
    --cc=tony@atomide.com \
    --cc=wfp5p@viridian.itc.virginia.edu \
    /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.