Hi,
I wonder what happened to your patch. We were "hit" by it in v5.4-rc1 and
after finding, it made our OMAP based device bootable again (using our
own defconfig which optimizes for SIZE).
But it does not seem to have arrived in linux-next and should IMHO
be fixed during the v5.4 release candidate cycle.
BR and thanks,
Nikolaus Schaller
> Am 19.10.2019 um 03:59 schrieb Masahiro Yamada <[email protected]>:
>
> On Fri, Oct 18, 2019 at 7:06 PM H. Nikolaus Schaller <[email protected]> wrote:
>>
>> Hi,
>> I wonder what happened to your patch. We were "hit" by it in v5.4-rc1 and
>> after finding, it made our OMAP based device bootable again (using our
>> own defconfig which optimizes for SIZE).
>>
>> But it does not seem to have arrived in linux-next
>
> It is in linux-next.
Ah, now I found it.
It has a "8908/1:" in its title so that search by (full) subject could not find it. Thanks!
>
>
>> and should IMHO
>> be fixed during the v5.4 release candidate cycle.
>
> I agree.
>
>
> Masahiro
BR and thanks,
Nikolaus
On Fri, Oct 18, 2019 at 7:06 PM H. Nikolaus Schaller <[email protected]> wrote:
>
> Hi,
> I wonder what happened to your patch. We were "hit" by it in v5.4-rc1 and
> after finding, it made our OMAP based device bootable again (using our
> own defconfig which optimizes for SIZE).
>
> But it does not seem to have arrived in linux-next
It is in linux-next.
> and should IMHO
> be fixed during the v5.4 release candidate cycle.
I agree.
Masahiro
>
> BR and thanks,
> Nikolaus Schaller
>
--
Best Regards
Masahiro Yamada