[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-id: <2241214.NPvmYhqHCQ@amdc1032>
Date: Tue, 08 Oct 2013 11:33:29 +0200
From: Bartlomiej Zolnierkiewicz <b.zolnierkie@...sung.com>
To: Michael Ellerman <michael@...erman.id.au>
Cc: Benjamin Herrenschmidt <benh@...nel.crashing.org>,
linuxppc-dev@...ts.ozlabs.org,
Kyungmin Park <kyungmin.park@...sung.com>,
Paul Mackerras <paulus@...ba.org>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] powerpc/legacy_serial: fix incorrect placement of
__initdata tag
On Tuesday, October 08, 2013 02:56:23 PM Michael Ellerman wrote:
> On Thu, Oct 03, 2013 at 01:51:27PM +0200, Bartlomiej Zolnierkiewicz wrote:
> > On Tuesday, October 01, 2013 04:13:25 PM Michael Ellerman wrote:
> > > On Mon, Sep 30, 2013 at 03:11:42PM +0200, Bartlomiej Zolnierkiewicz wrote:
> > > > __initdata tag should be placed between the variable name and equal
> > > > sign for the variable to be placed in the intended .init.data section.
> > >
> > > I see lots of other occurences of that in arch/powerpc. Why not send a
> > > single patch to update them all?
> >
> > The other occurences while not following the preferred kernel coding style
> > are (probably) working OK with gcc. This particular occurence just doesn't
> > work as it should.
>
> Why would the other occurrences work but not this one?
Because gcc seems to generate the correct code for things like i.e. this one:
struct of_device_id __initdata legacy_serial_parents[]
but not for ones like this:
struct __initdata of_device_id legacy_serial_parents[]
> Regardless, why don't we just do a single patch to clean them all up to
> match coding style and (probably) do what they're intended.
Because:
- fixing this occurence changes runtime, fixing others won't
- there were no such request from powerpc Maintainers
Best regards,
--
Bartlomiej Zolnierkiewicz
Samsung R&D Institute Poland
Samsung Electronics
--
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/
Powered by blists - more mailing lists