On Wed, May 24, 2023 at 06:13:52PM +0300, Doru Iorgulescu wrote:
> Awesome, thanks!
tl;dr: see [1].
(Hey, looks like complimenting noise here.)
[1]:
https://lore.kernel.org/regressions/5df92692-296e-3956-24fa-2bd439337...@gmail.com/
--
An old man doll... just what I always wanted! - Clara
Awesome, thanks!
On Wed, May 24, 2023, 6:03 PM Michael Ellerman wrote:
> Bagas Sanjaya writes:
> > On 5/24/23 17:58, Bagas Sanjaya wrote:
> >> Anyway, I'm adding it to regzbot:
> >>
> >> #regzbot introduced: 23baf831a32c04f
> https://bugzilla.kernel.org/show_bug.cgi?id=217477
> >> #regzbot
Glad to hear it!
Thank you
On Wed, May 24, 2023, 3:58 PM Bagas Sanjaya wrote:
> On 5/24/23 17:58, Bagas Sanjaya wrote:
> > Anyway, I'm adding it to regzbot:
> >
> > #regzbot introduced: 23baf831a32c04f
> https://bugzilla.kernel.org/show_bug.cgi?id=217477
> > #regzbot title: Allocator MAX_ORDER
On Thu, May 25, 2023 at 01:03:22AM +1000, Michael Ellerman wrote:
> Should be fixed properly by:
>
> https://patchwork.ozlabs.org/project/linuxppc-dev/patch/20230519113806.370635-1-...@ellerman.id.au/
>
> Which is in powerpc-fixes as 358e526a1648.
Telling regzbot:
#regzbot fix: 358e526a1648cd
Bagas Sanjaya writes:
> On 5/24/23 17:58, Bagas Sanjaya wrote:
>> Anyway, I'm adding it to regzbot:
>>
>> #regzbot introduced: 23baf831a32c04f
>> https://bugzilla.kernel.org/show_bug.cgi?id=217477
>> #regzbot title: Allocator MAX_ORDER exceeds SECTION_SIZE caused by MAX_ORDER
>> redefinition
On 5/24/23 20:11, Doru Iorgulescu wrote:
> Glad to hear it!
> Thank you
tl;dr:
> A: http://en.wikipedia.org/wiki/Top_post
> Q: Were do I find info about this thing called top-posting?
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad
On 5/24/23 17:58, Bagas Sanjaya wrote:
> Anyway, I'm adding it to regzbot:
>
> #regzbot introduced: 23baf831a32c04f
> https://bugzilla.kernel.org/show_bug.cgi?id=217477
> #regzbot title: Allocator MAX_ORDER exceeds SECTION_SIZE caused by MAX_ORDER
> redefinition
>
>From bugzilla [1], the
