[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a89a7147-57b3-4881-86e0-410eab56a91d@web.de>
Date: Wed, 24 Apr 2024 13:06:26 +0200
From: Markus Elfring <Markus.Elfring@....de>
To: John Paul Adrian Glaubitz <glaubitz@...sik.fu-berlin.de>,
Oreoluwa Babatunde <quic_obabatun@...cinc.com>, linux-sh@...r.kernel.org,
kernel-janitors@...r.kernel.org, kernel@...cinc.com,
Rich Felker <dalias@...c.org>, Rob Herring <robh@...nel.org>,
Yoshinori Sato <ysato@...rs.sourceforge.jp>
Cc: LKML <linux-kernel@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [v2] sh: Call paging_init() earlier in the init sequence
>> …
>>> Hence, move the call to paging_init() to be earlier in the init
>>> sequence so that the reserved memory regions are set aside before any
>>> allocations are done using memblock.
>> …
>>
>> Will the tag “Fixes” become relevant here?
>
> I'm not aware of any bugs that have been reported in this context.
Can the mentioned questionable function call ordering be interpreted
as a programming mistake?
Regards,
Markus
Powered by blists - more mailing lists