[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <3dbebac5b8404d3082a45cbe5610471f@ti.com>
Date: Fri, 11 Oct 2024 09:23:35 +0000
From: "Ding, Shenghao" <shenghao-ding@...com>
To: Mario Limonciello <superm1@...il.com>,
"linux-firmware@...nel.org"
<linux-firmware@...nel.org>
CC: "Xu, Baojun" <baojun.xu@...com>,
"derekjohn.clark@...il.com"
<derekjohn.clark@...il.com>,
"13916275206@....com" <13916275206@....com>,
"romangg@...jaro.org" <romangg@...jaro.org>,
"linux-sound@...r.kernel.org"
<linux-sound@...r.kernel.org>,
"Chen, Robin" <robinchen@...com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Yi, Ken"
<k-yi@...com>, "philm@...jaro.org" <philm@...jaro.org>,
"jlobue10@...il.com"
<jlobue10@...il.com>,
"luke@...nes.dev" <luke@...nes.dev>,
"antheas.dk@...il.com" <antheas.dk@...il.com>
Subject: RE: [EXTERNAL] Re: [PATCH v1] Upload dsp firmware for ASUS laptop
1EB30 & 1EB31 and Update WHENCE for both
Hi Mario
Thanks for your support. Finally "make check" works, following is the log.
root@...TOP-70RJ5B8Q:/usr/local/src/fw_new# make check
Check that executables have shebangs.....................................Passed
Forbid new submodules....................................................Passed
Check Yaml...............................................................Passed
Check for broken symlinks............................(no files to check)Skipped
Detect Destroyed Symlinks................................................Passed
shellcheck...............................................................Passed
black....................................................................Passed
markdownlint............................................................Skipped
Check whence.............................................................Passed
root@...TOP-70RJ5B8Q:/usr/local/src/fw_new#
> On 10/10/24 08:30, Mario Limonciello wrote:
> >> Although TAS2XXX1EB30.bin and TAS2XXX1EB31.bin are both in
> >> ti/tas2781, yet it reported "does not exist".
> >> I have no idea why the file is there while report "does not exist".
> >> After I removed the newly-merged, no such report.
> >
> > I think you forgot to git add them to the commit?
> >
> >>
................................
> I'll merge this and if you have any follow ups you can do them on top as future
> MR (preferred!) or patches to M/L.
It seemed that I was not used to submitting patch via gitlab.
So, finally I have to submit the patch to the git.kernel.com
I'll try submitting next firmware binary file via Gitlab. Thanks.
>
> Thanks!
Powered by blists - more mailing lists