linux-kernel - Re: [PATCH] mtd: fix section mismatch for doc_probe

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Thu, 15 Mar 2012 19:04:25 +0900
From:	Ryosuke Saito <raitosyo@...il.com>
To:	dwmw2@...radead.org
Cc:	robert.jarzmik@...e.fr, mikedunn@...sguy.com,
	ivan.djelic@...rot.com, artem.bityutskiy@...ux.intel.com,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] mtd: fix section mismatch for doc_probe_device

Sorry, please ignore it.
I will re-send a plain text message.

Best regards,
Ryosuke

On Thu, Mar 15, 2012 at 6:24 PM, Ryosuke Saito <raitosyo@...il.com> wrote:
> doc_probe_device() is only called from docg3_probe() which is in .init.text,
> so it must be in the same section to avoid a section mismatch warning.
>
> Signed-off-by: Ryosuke Saito <raitosyo@...il.com>
> ---
>  drivers/mtd/devices/docg3.c |    4 ++--
>  1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/mtd/devices/docg3.c b/drivers/mtd/devices/docg3.c
> index 25f688c..db9a4b7 100644
> --- a/drivers/mtd/devices/docg3.c
> +++ b/drivers/mtd/devices/docg3.c
> @@ -1846,8 +1846,8 @@ static void __init doc_set_driver_info(int chip_id,
> struct mtd_info *mtd)
>   * if a memory allocation failed. If floor 0 is checked, a reset of the
> ASIC is
>   * launched.
>   */
> -static struct mtd_info *doc_probe_device(void __iomem *base, int floor,
> -  struct device *dev)
> +static struct mtd_info * __init
> +doc_probe_device(void __iomem *base, int floor, struct device *dev)
>  {
>   int ret, bbt_nbpages;
>   u16 chip_id, chip_id_inv;
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/