[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <5a74a371-c447-4fc6-abf1-08514de8fc00@sirena.org.uk>
Date: Thu, 14 Sep 2023 12:42:10 +0100
From: Mark Brown <broonie@...nel.org>
To: Uwe Kleine-König
<u.kleine-koenig@...gutronix.de>
Cc: Myunguk Kim <mwkim@...nchips.com>, alsa-devel@...a-project.org,
fido_max@...ox.ru, kuninori.morimoto.gx@...esas.com,
lgirdwood@...il.com, linux-kernel@...r.kernel.org, perex@...ex.cz,
tiwai@...e.com, xingyu.wu@...rfivetech.com
Subject: Re: [PATCH] [v2] ASoC: dwc: fix typo in comment
On Thu, Sep 14, 2023 at 08:32:48AM +0200, Uwe Kleine-König wrote:
> On Thu, Sep 14, 2023 at 09:56:34AM +0900, Myunguk Kim wrote:
> > > The patch is obviously corrupted, the { there should be on the prior
> > > line and even fixing that by hand there appear to be some other issues.
> > The patch file should have been attached as shown below.
> > Is there a problem with my git send-email?
> > + /* Error Handling: RX */
> > if (isr[i] & ISR_RXFO)
> > { dev_err_ratelimited(dev->dev, "RX overrun (ch_id=%d)\n", i);
> FTR: I get this mail directly (so no mailing list server involved), and
> the patch is mangled in the same way as broonie pointed out in his mail
> earlier in this thread.
Right, same here. I don't know where the problem might be, it's not a
pattern I've seen before.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists