mirror of https://lore.kernel.org/linux-amlogic/
 help / color / mirror / Atom feed
From: "Arnd Bergmann" <arnd@arndb.de>
To: "Neil Armstrong" <neil.armstrong@linaro.org>,
	soc@kernel.org, arm <arm@kernel.org>
Cc: linux-amlogic@lists.infradead.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL] Amlogic drivers updates for v6.14
Date: Thu, 16 Jan 2025 17:39:04 +0100	[thread overview]
Message-ID: <909e85a4-8861-41ee-8b4b-97d4bad29994@app.fastmail.com> (raw)
In-Reply-To: <724c4e81-184a-489c-aaaa-85c21a19b64a@linaro.org>

On Thu, Jan 16, 2025, at 16:23, Neil Armstrong wrote:
> On 06/01/2025 15:25, Neil Armstrong wrote:
>> Hi,
>> 
>> Here's the final DT bindings change that will give 100% success in Amlogic
>> ARM64 & ARM64 DT Bindings checks, with the mmc-slot bindings change routed
>> via the MMC tree.
>
> Gentle ping, it doesn't seem you pulled this PR.

Thanks for catching this, I had indeed missed it in my first pass
through the backlog.

When I first looked at the "drivers" branches, I decided to skip
it and instead merge it into the soc/dt branch since it's just
binding updates. I don't normally care which of the two (or both)
the binding updates go through, but if the drivers don't depend
on it, I pick soc/dt.

When I later looked through the dts branches, I skipped over this
because the subject said "drivers". I'm now in the second pass of
looking at everything I skipped originally, and would have
eventually caught it, but it does help to have you look at what
I'm doing to ensure it doesn't get lost entirely.

      Arnd

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

  reply	other threads:[~2025-01-16 16:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-06 14:25 Neil Armstrong
2025-01-16 15:23 ` Neil Armstrong
2025-01-16 16:39   ` Arnd Bergmann [this message]
2025-01-16 18:59     ` Neil Armstrong

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=909e85a4-8861-41ee-8b4b-97d4bad29994@app.fastmail.com \
    --to=arnd@arndb.de \
    --cc=arm@kernel.org \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=neil.armstrong@linaro.org \
    --cc=soc@kernel.org \
    /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®