[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20190905170006.GF4053@sirena.co.uk>
Date: Thu, 5 Sep 2019 18:00:06 +0100
From: Mark Brown <broonie@...nel.org>
To: "shifu0704@...ndersoft.com" <shifu0704@...ndersoft.com>
Cc: lgirdwood <lgirdwood@...il.com>, perex <perex@...ex.cz>,
tiwai <tiwai@...e.com>,
linux-kernel <linux-kernel@...r.kernel.org>,
alsa-devel <alsa-devel@...a-project.org>,
Dan?Murphy <dmurphy@...com>,
"Navada Kanyana, Mukund" <navada@...com>
Subject: Re: [PATCH]Add tas2770 driver code
On Thu, Sep 05, 2019 at 01:35:04PM +0800, shifu0704@...ndersoft.com wrote:
> From 5b539e7dbebebf7e58c38a6b54f222bc116d63f3 Mon Sep 17 00:00:00 2001
> From: Shi Fu <shifu0704@...ndersoft.com>
> Date: Mon, 1 Jul 2019 11:00:13 +0800
> Signed-off-by: Shi Fu <shifu0704@...ndersoft.com>
> Subject: [PATCH v5] dt: tas2770: Add tas2770 smart PA dt bindings.
>
> Add tas2770 smart PA dt bindings.
> ---
This looks like it's a whole patch series sent as a single mail, and
there's some confusing with things like Signed-off-by and general
formatting. Please see submitting-patches.rst in the kernel source for
how to send patches, it's worth taking a look at other posts on the list
and trying to ensure that your mails look the same as them. As things
stand it's really hard to read this since whatever happened with the way
this has been sent seems to have mangled the indention so it doesn't
look like normal kernel code unfortunately.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists