Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Jack Yu <jack.yu@realtek.com>
Cc: "Oder Chiou" <oder_chiou@realtek.com>,
	"Rob Herring" <robh@kernel.org>,
	"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	"lars@metafoo.de" <lars@metafoo.de>,
	"kent_chen@realtek.com [陳建宏]" <kent_chen@realtek.com>,
	陳昶志 <kenny_chen@realtek.com>,
	"lgirdwood@gmail.com" <lgirdwood@gmail.com>,
	"Derek [方德義]" <derek.fang@realtek.com>,
	"Shuming [范書銘]" <shumingf@realtek.com>,
	"Flove(HsinFu)" <flove@realtek.com>
Subject: Re: [PATCH v2] ASoC: rt1019: add rt1019 amplifier driver
Date: Mon, 29 Mar 2021 16:37:02 +0100	[thread overview]
Message-ID: <20210329153702.GC5166@sirena.org.uk> (raw)
In-Reply-To: <1b6969cffa9e4a65be0d2df114d2ef21@realtek.com>

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

On Mon, Mar 29, 2021 at 08:09:26AM +0000, Jack Yu wrote:

> > Bindings should also be sent to the DT list. get_maintainer.pl will tell you this.

> 1. Does it mean I should add my name in MAINTAINERS?

It means you should have sent the patch with the binding changes to the
DT list and maintainers as well as everyone else.

> 2. Is below warning message caused by #1 question?

No, it's the content of the change that's introduced problems in the
binding.

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

  parent reply	other threads:[~2021-03-29 15:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-11  2:58 [PATCH v2] ASoC: rt1019: add rt1019 amplifier driver jack.yu
2021-03-18 18:33 ` Mark Brown
2021-03-18 18:36   ` Mark Brown
2021-03-26 20:34 ` Rob Herring
     [not found]   ` <1b6969cffa9e4a65be0d2df114d2ef21@realtek.com>
2021-03-29 15:37     ` Mark Brown [this message]
     [not found]       ` <c414d49d283947878a0c5021388b8ac0@realtek.com>
2021-03-30 13:12         ` Rob Herring

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=20210329153702.GC5166@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=derek.fang@realtek.com \
    --cc=flove@realtek.com \
    --cc=jack.yu@realtek.com \
    --cc=kenny_chen@realtek.com \
    --cc=kent_chen@realtek.com \
    --cc=lars@metafoo.de \
    --cc=lgirdwood@gmail.com \
    --cc=oder_chiou@realtek.com \
    --cc=robh@kernel.org \
    --cc=shumingf@realtek.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