From: Rob Herring <robh@kernel.org>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: devicetree-compiler@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: Device Tree Compiler v1.7.1
Date: Tue, 17 Sep 2024 13:22:45 -0500 [thread overview]
Message-ID: <CAL_JsqJ2dcng7xZoua-iAGi2FtPhddxgr9TJ5JdfC_wticW3cQ@mail.gmail.com> (raw)
In-Reply-To: <ZujKoLT9VBHATtyP@zatzit.fritz.box>
On Mon, Sep 16, 2024 at 8:24 PM David Gibson
<david@gibson.dropbear.id.au> wrote:
>
> 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.
Partially. The tag is there, but main/master don't include the tagged commit:
99031e3a4a6e (tag: v1.7.1) Bump version to v1.7.1
3d5e376925fd (HEAD -> master, origin/master, origin/main, origin/HEAD)
setup: Move setting of srcdir down to the bottom
e277553b9880 setup: Collect top-level code together
Rob
next prev parent reply other threads:[~2024-09-17 18:22 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
2024-09-17 18:22 ` Rob Herring [this message]
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=CAL_JsqJ2dcng7xZoua-iAGi2FtPhddxgr9TJ5JdfC_wticW3cQ@mail.gmail.com \
--to=robh@kernel.org \
--cc=david@gibson.dropbear.id.au \
--cc=devicetree-compiler@vger.kernel.org \
--cc=devicetree@vger.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).