From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: irqchip heirarchy DT "break" series awareness?
Date: Tue, 7 Apr 2015 14:49:11 +0200 [thread overview]
Message-ID: <20150407144911.1736c162@free-electrons.com> (raw)
In-Reply-To: <20150407124016.GD7873@io.lakedaemon.net>
Jason,
On Tue, 7 Apr 2015 12:40:16 +0000, Jason Cooper wrote:
> Because my goal here was to give *every* possible chance for an
> objection. Hence, "dt" and "break" in the subject line, sent to the
> devicetree ML. Also, Marc mentioned the possibility in at least the
> cover letter of each of his series. I don't want anything hidden.
>
> But you are absolutely correct. (2) was never guaranteed, and it's also
> highly improbable as well. See below.
Right.
> > However, my slides are definitely not about #2 (which as said earlier,
> > was never planned to be something we should worry about), but really
> > about #1.
>
> I was referring to the slide where you mention that distros and vendors
> have tied the dtbs to the kernel versions (Slide 23/27, "Usefulness").
> I should have been more specific when taking something out of context.
> :-P
>
> My point, not well made, was that everyone has decided to slave the
> upgrade of the dtb to the upgrade of the kernel. There is no 'apt-get
> armv7-dtbs' that has no dependency structure on a kernel package. So we
> agree, (2) was never guaranteed, and isn't probable either.
And so is (1), then :-)
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-04-07 12:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-06 14:46 irqchip heirarchy DT "break" series awareness? Jason Cooper
2015-04-07 9:59 ` Thomas Petazzoni
2015-04-07 10:21 ` Marc Zyngier
2015-04-07 13:06 ` Jason Cooper
2015-04-07 13:37 ` Mark Rutland
2015-04-07 12:40 ` Jason Cooper
2015-04-07 12:49 ` Thomas Petazzoni [this message]
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=20150407144911.1736c162@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.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).