On Tue, Dec 19, 2023 at 6:04 PM Caleb Connolly
wrote:
>
> Some of the db410c board support code was written to be generic and
> placed in mach-snapdragon. However, as the db410c is the only board
> using this, move the code out of mach-snapdragon. This makes is more
> obvious what code is relevant
On 20/12/2023 13:47, Sumit Garg wrote:
> Hi Caleb,
>
> On Tue, 19 Dec 2023 at 21:34, Caleb Connolly
> wrote:
>>
>> Some of the db410c board support code was written to be generic and
>> placed in mach-snapdragon. However, as the db410c is the only board
>> using this, move the code out of mac
On 19/12/2023 17:04, Caleb Connolly wrote:
Some of the db410c board support code was written to be generic and
placed in mach-snapdragon. However, as the db410c is the only board
using this, move the code out of mach-snapdragon. This makes is more
obvious what code is relevant for which targets a
Hi Caleb,
On Tue, 19 Dec 2023 at 21:34, Caleb Connolly wrote:
>
> Some of the db410c board support code was written to be generic and
> placed in mach-snapdragon. However, as the db410c is the only board
> using this, move the code out of mach-snapdragon. This makes is more
> obvious what code is
Some of the db410c board support code was written to be generic and
placed in mach-snapdragon. However, as the db410c is the only board
using this, move the code out of mach-snapdragon. This makes is more
obvious what code is relevant for which targets and helps tidy things up
a little more.
Signe
5 matches
Mail list logo