From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 0/5] Follow the Linux Kernel in building dtc as needed
Date: Sun, 24 Sep 2017 13:28:45 -0400 [thread overview]
Message-ID: <20170924172845.GV30205@bill-the-cat> (raw)
In-Reply-To: <61a675e1-a3ae-c8f4-32fd-cf548c4047df@denx.de>
On Sun, Sep 24, 2017 at 06:50:01PM +0200, Marek Vasut wrote:
> On 09/24/2017 04:26 PM, Tom Rini wrote:
> > The following series has been applied. I am posting this for the record.
> >
> > For the record, I do not believe that using git submodules is a good approach
> > here. We have a small amount of code that we need here, and happily we can
> > leverage infrastructur e from the Linux Kernel.
> >
> > Speaking of, this is not the first time we have run into problems deviating
> > from the workflow of the kernel. The problems of having large number of
> > warnings, or not stemmed from not just leve raging all of the infrastructure
> > from the kernel. So related, yes, fixes for these warnings should come in,
> > and as always, if they're in the upstream kernel dts as well, they should be
> > fixed there.
>
> So any comments regarding bundling external tools were ignored, even
> though the discussion was not finished, great.
>
> Furthermore, there was zero time to review this series, it was just
> applied and posted afterward ? What sort of practice is this ?
Yes. I put on my slightly-less-than-benevolent dictator hat today, and
explained my reasoning. I do feel bad that you're rather unhappy with
the overall situation, but no, I believe this is the right answer.
Now, there's some follow up further re-syncing with the kernel that
could be done (scripts/Makefile.lib/extrawarn can be further re-matched
up with the kernel now, but that would have made a larger delta than
"just migrate to providing the tool").
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20170924/3a82e835/attachment.sig>
next prev parent reply other threads:[~2017-09-24 17:28 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-24 14:26 [U-Boot] [PATCH 0/5] Follow the Linux Kernel in building dtc as needed Tom Rini
2017-09-24 14:26 ` [U-Boot] [PATCH 1/5] scripts/dtc: Update to upstream version v1.4.3 Tom Rini
2017-10-03 18:24 ` Rob Herring
2017-10-03 18:28 ` Tom Rini
2017-10-03 18:30 ` Rob Herring
2017-10-03 18:44 ` Tom Rini
2017-09-24 14:26 ` [U-Boot] [PATCH 2/5] scripts/dtc: Update to upstream version v1.4.4 Tom Rini
2017-09-24 14:27 ` [U-Boot] [PATCH 3/5] scripts/dtc: Update to upstream version v1.4.4-50-gfe50bd1ecc1d Tom Rini
2017-09-24 14:27 ` [U-Boot] [PATCH 4/5] dtc: Switch to building and using our own dtc unless provided Tom Rini
2017-09-24 14:27 ` [U-Boot] [PATCH 5/5] tools/mkimage: Make the path to the dtc binary that mkimage calls configurable Tom Rini
2017-09-24 16:50 ` [U-Boot] [PATCH 0/5] Follow the Linux Kernel in building dtc as needed Marek Vasut
2017-09-24 17:28 ` Tom Rini [this message]
2017-09-24 20:39 ` Łukasz Majewski
2017-09-24 22:00 ` Tom Rini
2017-09-25 8:32 ` Marek Vasut
2017-09-25 8:28 ` Wolfgang Denk
2017-09-27 14:15 ` [U-Boot] [PATCH 0/5] REVERT " Wolfgang Denk
2017-09-27 14:15 ` [U-Boot] [PATCH 1/5] Revert "tools/mkimage: Make the path to the dtc binary that mkimage calls configurable" Wolfgang Denk
2017-09-27 14:15 ` [U-Boot] [PATCH 2/5] Revert "dtc: Switch to building and using our own dtc unless provided" Wolfgang Denk
2017-09-27 14:15 ` [U-Boot] [PATCH 3/5] Revert "scripts/dtc: Update to upstream version v1.4.4-50-gfe50bd1ecc1d" Wolfgang Denk
2017-09-27 14:15 ` [U-Boot] [PATCH 4/5] Revert "scripts/dtc: Update to upstream version v1.4.4" Wolfgang Denk
2017-09-27 14:15 ` [U-Boot] [PATCH 5/5] Revert "scripts/dtc: Update to upstream version v1.4.3" Wolfgang Denk
2017-09-27 14:31 ` [U-Boot] [PATCH 0/5] REVERT Follow the Linux Kernel in building dtc as needed Tom Rini
2017-09-27 14:56 ` Wolfgang Denk
2017-09-27 15:23 ` Tom Rini
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=20170924172845.GV30205@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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