mirror of https://lore.kernel.org/linux-amlogic/
 help / color / mirror / Atom feed
From: patchwork-bot+linux-amlogic@kernel.org
To: Neil Armstrong <narmstrong@baylibre.com>
Cc: linux-amlogic@lists.infradead.org, khilman@kernel.org
Subject: Re: [PATCH] arm64: dts: meson-g12b-khadas-vim3: add missing frddr_a status property
Date: Fri, 18 Oct 2019 18:21:16 +0000	[thread overview]
Message-ID: <157142287693.4978.3071363286518113740.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20191018140216.4257-1-narmstrong@baylibre.com>

Hello:

This patch was applied to khilman/linux-amlogic.git (refs/heads/for-next).

On Fri, 18 Oct 2019 14:02:16 +0000 you wrote:
> In the process of moving the VIM3 audio nodes to a G12B specific dtsi
> for enabling the SM1 based VIM3L, the frddr_a status = "okay" property
> got dropped.
> This re-enables the frddr_a node to fix audio support.
> 
> Fixes: 4f26cc1c96c9 ("arm64: dts: khadas-vim3: move common nodes into meson-khadas-vim3.dtsi")
> Reported-by: Christian Hewitt <christianshewitt@gmail.com>
> Signed-off-by: Neil Armstrong <narmstrong@baylibre.com>
> 
> [...]


Here is a summary with links:
  - arm64: dts: meson-g12b-khadas-vim3: add missing frddr_a status property
    https://git.kernel.org/khilman/linux-amlogic/c/d5ad6db3742bbfb6d224704040ceab3a4efcdc6d

You are awesome, thank you!

-- 
Deet-doot-dot, I am a bot.
https://korg.wiki.kernel.org/userdoc/pwbot

_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic

      parent reply	other threads:[~2019-10-18 18:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-18 14:02 Neil Armstrong
2019-10-18 16:15 ` Jerome Brunet
2019-10-18 18:17   ` Kevin Hilman
2019-10-18 18:21 ` patchwork-bot+linux-amlogic [this message]

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=157142287693.4978.3071363286518113740.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-amlogic@kernel.org \
    --cc=khilman@kernel.org \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=narmstrong@baylibre.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®