From: "Ding, Shenghao" <shenghao-ding@ti.com>
To: Mario Limonciello <superm1@gmail.com>,
"linux-firmware@kernel.org" <linux-firmware@kernel.org>
Cc: "Xu, Baojun" <baojun.xu@ti.com>,
"derekjohn.clark@gmail.com" <derekjohn.clark@gmail.com>,
"13916275206@139.com" <13916275206@139.com>,
"romangg@manjaro.org" <romangg@manjaro.org>,
"linux-sound@vger.kernel.org" <linux-sound@vger.kernel.org>,
"Chen, Robin" <robinchen@ti.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Yi, Ken" <k-yi@ti.com>, "philm@manjaro.org" <philm@manjaro.org>,
"jlobue10@gmail.com" <jlobue10@gmail.com>,
"luke@ljones.dev" <luke@ljones.dev>,
"antheas.dk@gmail.com" <antheas.dk@gmail.com>
Subject: RE: [EXTERNAL] Re: [PATCH v1] Upload dsp firmware for ASUS laptop 1EB30 & 1EB31 and Update WHENCE for both
Date: Fri, 11 Oct 2024 09:23:35 +0000 [thread overview]
Message-ID: <3dbebac5b8404d3082a45cbe5610471f@ti.com> (raw)
In-Reply-To: <50daaa7a-d590-4ae5-b33f-8f51d0c2f457@gmail.com>
Hi Mario
Thanks for your support. Finally "make check" works, following is the log.
root@LAPTOP-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@LAPTOP-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!
prev parent reply other threads:[~2024-10-11 9:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-09 10:18 [PATCH v1] Upload dsp firmware for ASUS laptop 1EB30 & 1EB31 and Update WHENCE for both Shenghao Ding
2024-10-10 3:06 ` Mario Limonciello
2024-10-10 11:29 ` [EXTERNAL] " Ding, Shenghao
2024-10-10 13:30 ` Mario Limonciello
2024-10-10 13:39 ` Mario Limonciello
2024-10-10 13:52 ` Antheas Kapenekakis
2024-10-11 9:23 ` Ding, Shenghao [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3dbebac5b8404d3082a45cbe5610471f@ti.com \
--to=shenghao-ding@ti.com \
--cc=13916275206@139.com \
--cc=antheas.dk@gmail.com \
--cc=baojun.xu@ti.com \
--cc=derekjohn.clark@gmail.com \
--cc=jlobue10@gmail.com \
--cc=k-yi@ti.com \
--cc=linux-firmware@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=luke@ljones.dev \
--cc=philm@manjaro.org \
--cc=robinchen@ti.com \
--cc=romangg@manjaro.org \
--cc=superm1@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox