mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Adam Thomson <Adam.Thomson.Opensource@diasemi.com>
Cc: Mark Brown <broonie@kernel.org>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Takashi Iwai <tiwai@suse.com>, Jaroslav Kysela <perex@perex.cz>,
	Mark Rutland <mark.rutland@arm.com>,
	alsa-devel@alsa-project.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Support Opensource <support.opensource@diasemi.com>
Subject: Re: [PATCH 2/2] ASoC: da7218: Correct IRQ level in DT binding example
Date: Mon, 20 Nov 2017 14:44:25 -0600	[thread overview]
Message-ID: <20171120204425.4fltek756ggpp3ps@rob-hp-laptop> (raw)
In-Reply-To: <c57eabe7cd6bb5a5466c774725c5150cc33d1ab5.1510930791.git.Adam.Thomson.Opensource@diasemi.com>

On Fri, Nov 17, 2017 at 03:09:28PM +0000, Adam Thomson wrote:
> Current DT binding documentation shows an example where the IRQ
> for the device is chosen to be ACTIVE_HIGH. This is incorrect as
> the device only supports ACTIVE_LOW, so this commit fixes that
> discrepancy.
> 
> Signed-off-by: Adam Thomson <Adam.Thomson.Opensource@diasemi.com>
> ---
>  Documentation/devicetree/bindings/sound/da7218.txt | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

Acked-by: Rob Herring <robh@kernel.org>

  reply	other threads:[~2017-11-20 20:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-17 15:09 [PATCH 0/2] ASoC: Correct DT binding examples IRQ usage for da7218/9 Adam Thomson
2017-11-17 15:09 ` [PATCH 1/2] ASoC: da7219: Correct IRQ level in DT binding example Adam Thomson
2017-11-20 20:44   ` Rob Herring
2017-11-27 18:52   ` Applied "ASoC: da7219: Correct IRQ level in DT binding example" to the asoc tree Mark Brown
2017-11-17 15:09 ` [PATCH 2/2] ASoC: da7218: Correct IRQ level in DT binding example Adam Thomson
2017-11-20 20:44   ` Rob Herring [this message]
2017-11-27 18:52   ` Applied "ASoC: da7218: Correct IRQ level in DT binding example" to the asoc tree Mark Brown

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=20171120204425.4fltek756ggpp3ps@rob-hp-laptop \
    --to=robh@kernel.org \
    --cc=Adam.Thomson.Opensource@diasemi.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=perex@perex.cz \
    --cc=support.opensource@diasemi.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®