All of lore.kernel.org
 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-g12: remove spurious blank line
Date: Wed, 29 Apr 2020 19:41:13 +0000	[thread overview]
Message-ID: <158818927395.21662.3176540147299415461.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20200420080018.11607-1-narmstrong@baylibre.com>

Hello:

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

On Mon, 20 Apr 2020 10:00:18 +0200 you wrote:
> Remove spurious blank line introduced in f12a463d2f43 but was not part
> of the original patch at [1].
> 
> [1] http://lore.kernel.org/r/20200313090713.15147-3-narmstrong@baylibre.com
> 
> Fixes: f12a463d2f43 ("arm64: dts: meson-g12: add the SPIFC nodes")
> Signed-off-by: Neil Armstrong <narmstrong@baylibre.com>
> 
> [...]


Here is a summary with links:
  - arm64: dts: meson-g12: remove spurious blank line
    https://git.kernel.org/khilman/linux-amlogic/c/adf27a87eb4e85bb2136572121e06ad83e5f1407

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:[~2020-04-29 19:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-20  8:00 [PATCH] arm64: dts: meson-g12: remove spurious blank line Neil Armstrong
2020-04-20  8:00 ` Neil Armstrong
2020-04-20  8:00 ` Neil Armstrong
2020-04-29 19:13 ` Kevin Hilman
2020-04-29 19:13   ` Kevin Hilman
2020-04-29 19:13   ` Kevin Hilman
2020-04-29 19:41 ` 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=158818927395.21662.3176540147299415461.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.