public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@amd64.org>
To: Lionel Debroux <lionel_debroux@yahoo.fr>
Cc: linux-kernel@vger.kernel.org, linux-edac@vger.kernel.org,
	kernel-janitors@vger.kernel.org
Subject: Re: [PATCH linux-next] edac: move const pci_device_id tables from __devinitdata to __devinitconst.
Date: Mon, 27 Feb 2012 10:28:38 +0100	[thread overview]
Message-ID: <20120227092838.GB3970@aftab> (raw)
In-Reply-To: <83869.69195.bm@smtp156.mail.ukl.yahoo.com>

On Mon, Feb 27, 2012 at 08:05:30AM +0100, Lionel Debroux wrote:
> Based on PaX and earlier work by Andi Kleen.
> 
> Patch against linux-next (20120224).
> 
> ---
> 
> From e4ed493cf2241f6ba880459e48674de0b2a394a3 Mon Sep 17 00:00:00 2001
> From: Lionel Debroux <lionel_debroux@yahoo.fr>
> Date: Mon, 27 Feb 2012 07:41:47 +0100
> Subject: edac: move const pci_device_id tables from __devinitdata to
>  __devinitconst.
> 
> These const tables are currently marked __devinitdata, but Documentation/PCI/pci.txt says:
> "
> o The ID table array should be marked __devinitconst; this is done
>   automatically if the table is declared with DEFINE_PCI_DEVICE_TABLE().
> "
> So use DEFINE_PCI_DEVICE_TABLE(x).
> 
> Based on PaX and earlier work by Andi Kleen.
> 
> Signed-off-by: Lionel Debroux <lionel_debroux@yahoo.fr>

Applied [with minor commit msg formatting changes], thanks.

-- 
Regards/Gruss,
Boris.

Advanced Micro Devices GmbH
Einsteinring 24, 85609 Dornach
GM: Alberto Bozzo
Reg: Dornach, Landkreis Muenchen
HRB Nr. 43632 WEEE Registernr: 129 19551

      reply	other threads:[~2012-02-27  9:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-27  7:05 [PATCH linux-next] edac: move const pci_device_id tables from __devinitdata to __devinitconst Lionel Debroux
2012-02-27  9:28 ` Borislav Petkov [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=20120227092838.GB3970@aftab \
    --to=bp@amd64.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lionel_debroux@yahoo.fr \
    /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