[PATCH] x86: coral: Correct max98357 file

[PATCH] x86: coral: Correct max98357 file

[Simon Glass]

This somehow ended up as an empty file. Fix it.

Signed-off-by: Simon Glass <sjg@chromium.org>
---

 .../max98357-render-2ch-48khz-24b.dat             | Bin 0 -> 116 bytes
 1 file changed, 0 insertions(+), 0 deletions(-)

diff --git a/board/google/chromebook_coral/max98357-render-2ch-48khz-24b.dat b/board/google/chromebook_coral/max98357-render-2ch-48khz-24b.dat
index e69de29bb2d1d6434b8b29ae775ad8c2e48c5391..b0b5b9ba648c4546f98e15e42356a5fc4af6bb27 100644
GIT binary patch
literal 116
zcmZQzU|?WnWOx?=qy_%}|BnyXGahJUU??~MR0;$VT+Bccgqa+G1PJi6vnv28CMf>T
R&%gk}Aix2{5<r{+!~hE!AMpSH

literal 0
HcmV?d00001

-- 
2.29.2.222.g5d2a92d10f8-goog

[PATCH] x86: coral: Correct max98357 file

[Bin Meng]

Hi Simon,

On Mon, Nov 9, 2020 at 9:41 PM Simon Glass <sjg@chromium.org> wrote:
>
> This somehow ended up as an empty file. Fix it.
>
> Signed-off-by: Simon Glass <sjg@chromium.org>
> ---
>
>  .../max98357-render-2ch-48khz-24b.dat             | Bin 0 -> 116 bytes
>  1 file changed, 0 insertions(+), 0 deletions(-)
>

Acked-by: Bin Meng <bmeng.cn@gmail.com>

It seems that this patch did not arrive on patchwork, just as last
time in v3. That's probably why it was missed last time.

Regards,
Bin

[PATCH] x86: coral: Correct max98357 file

[Bin Meng]

On Tue, Nov 10, 2020 at 9:34 AM Bin Meng <bmeng.cn@gmail.com> wrote:
>
> Hi Simon,
>
> On Mon, Nov 9, 2020 at 9:41 PM Simon Glass <sjg@chromium.org> wrote:
> >
> > This somehow ended up as an empty file. Fix it.
> >
> > Signed-off-by: Simon Glass <sjg@chromium.org>
> > ---
> >
> >  .../max98357-render-2ch-48khz-24b.dat             | Bin 0 -> 116 bytes
> >  1 file changed, 0 insertions(+), 0 deletions(-)
> >
>
> Acked-by: Bin Meng <bmeng.cn@gmail.com>

applied to u-boot-x86, thanks!