From: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: Rob Herring <robh@kernel.org>,
devicetree-compiler@vger.kernel.org,
Geert Uytterhoeven <geert@linux-m68k.org>,
Saravana Kannan <saravanak@google.com>,
devicetree@vger.kernel.org
Subject: Re: [PATCH] libfdt: overlay: Fix phandle overwrite check for new subtrees
Date: Fri, 5 Jul 2024 22:53:34 +0200 [thread overview]
Message-ID: <cjaomdfyojgsq3ykqezitfjdtjqhhetgcncdxs6uoj6llholut@nw4zhuwmht4u> (raw)
In-Reply-To: <ZofdvXLWunF4opJB@zatzit>
[-- Attachment #1: Type: text/plain, Size: 598 bytes --]
Hello David,
On Fri, Jul 05, 2024 at 09:49:17PM +1000, David Gibson wrote:
> On Wed, Jul 03, 2024 at 11:06:32AM -0600, Rob Herring wrote:
> > I think it's just waiting on David.
>
> Sorry, yes. I'm always finding it hard to find time for dtc/libfdt
> maintenance stuff, and I've been particularly busy lately. I did
> catch up on a bunch of trivial dtc/libfdt patches lately, but this
> one's a bit more complex so I didn't get to it yet.
Good to know it's on your radar. If you have questions or other needs to
talk about this, don't hesitate to contact me.
Best regards
Uwe
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2024-07-05 20:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-26 7:55 [PATCH] libfdt: overlay: Fix phandle overwrite check for new subtrees Uwe Kleine-König
2024-07-02 13:44 ` Uwe Kleine-König
2024-07-03 17:06 ` Rob Herring
2024-07-05 11:49 ` David Gibson
2024-07-05 20:53 ` Uwe Kleine-König [this message]
2024-07-05 23:46 ` David Gibson
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=cjaomdfyojgsq3ykqezitfjdtjqhhetgcncdxs6uoj6llholut@nw4zhuwmht4u \
--to=u.kleine-koenig@baylibre.com \
--cc=david@gibson.dropbear.id.au \
--cc=devicetree-compiler@vger.kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=robh@kernel.org \
--cc=saravanak@google.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).