devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Rob Herring <robh@kernel.org>
Cc: devicetree-compiler@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: Device Tree Compiler v1.7.1
Date: Tue, 17 Sep 2024 10:17:36 +1000	[thread overview]
Message-ID: <ZujKoLT9VBHATtyP@zatzit.fritz.box> (raw)
In-Reply-To: <CAL_Jsq+P6j70L=Sr=a5cBrGEMswZN0fYdaeOeDxGFG-VJgWNbg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 938 bytes --]

On Mon, Sep 16, 2024 at 02:45:23PM -0500, Rob Herring wrote:
> On Sat, Aug 17, 2024 at 4:39 AM David Gibson
> <david@gibson.dropbear.id.au> wrote:
> >
> > Rob Herring pointed out it's been a year and a half since the last dtc
> > release.  There haven't actually been any headline changes since then,
> > but there has been a steady stream of small updates.  So, I've rolled
> > up a new release.
> >
> > As usual, the git tree can be had from:
> >         git://git.kernel.org/pub/scm/utils/dtc/dtc.git
> > and tarballs can be had from:
> >         https://mirrors.edge.kernel.org/pub/software/utils/dtc/
> 
> The tarballs are there, but it doesn't look like you pushed the tag
> to git repo.

Oops, sorry.  FIxed now.

-- 
David Gibson (he or they)	| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you, not the other way
				| around.
http://www.ozlabs.org/~dgibson

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2024-09-17  1:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-17  9:38 Device Tree Compiler v1.7.1 David Gibson
2024-09-16 19:45 ` Rob Herring
2024-09-17  0:17   ` David Gibson [this message]
2024-09-17 18:22     ` Rob Herring
2024-09-18  0:03       ` 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=ZujKoLT9VBHATtyP@zatzit.fritz.box \
    --to=david@gibson.dropbear.id.au \
    --cc=devicetree-compiler@vger.kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=robh@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;
as well as URLs for NNTP newsgroup(s).