mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: "shifu0704@thundersoft.com" <shifu0704@thundersoft.com>
Cc: lgirdwood <lgirdwood@gmail.com>, perex <perex@perex.cz>,
	tiwai <tiwai@suse.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	alsa-devel <alsa-devel@alsa-project.org>,
	Dan?Murphy <dmurphy@ti.com>,
	"Navada Kanyana, Mukund" <navada@ti.com>
Subject: Re: [PATCH]Add tas2770 driver code
Date: Thu, 5 Sep 2019 18:00:06 +0100	[thread overview]
Message-ID: <20190905170006.GF4053@sirena.co.uk> (raw)
In-Reply-To: <201909051335040840918@thundersoft.com>

[-- Attachment #1: Type: text/plain, Size: 952 bytes --]

On Thu, Sep 05, 2019 at 01:35:04PM +0800, shifu0704@thundersoft.com wrote:
> From 5b539e7dbebebf7e58c38a6b54f222bc116d63f3 Mon Sep 17 00:00:00 2001
> From: Shi Fu <shifu0704@thundersoft.com>
> Date: Mon, 1 Jul 2019 11:00:13 +0800
> Signed-off-by: Shi Fu <shifu0704@thundersoft.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.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

           reply	other threads:[~2019-09-05 17:00 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <201909051335040840918@thundersoft.com>]

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=20190905170006.GF4053@sirena.co.uk \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=dmurphy@ti.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=navada@ti.com \
    --cc=perex@perex.cz \
    --cc=shifu0704@thundersoft.com \
    --cc=tiwai@suse.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

all inboxes | Powered by JetHome®