devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
To: Jason Cooper <jason-NLaQJdtUoK4Be96aLqz0jA@public.gmane.org>
Cc: Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>,
	Olof Johansson <olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org>,
	arm-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
	Marc Zyngier <marc.zyngier-5wv7dgnIgG8@public.gmane.org>,
	devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Thomas Gleixner <tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org>,
	Linux ARM Kernel
	<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>
Subject: Re: 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-fahSIxCzskDQ+YiMSub0/l6hYfS7NtTn@public.gmane.org>

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
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      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
     [not found] ` <20150406144647.GC7873-fahSIxCzskDQ+YiMSub0/l6hYfS7NtTn@public.gmane.org>
2015-04-07  9:59   ` Thomas Petazzoni
     [not found]     ` <20150407115922.5d4c6233-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
2015-04-07 10:21       ` Marc Zyngier
     [not found]         ` <5523AFAF.6040000-5wv7dgnIgG8@public.gmane.org>
2015-04-07 13:06           ` Jason Cooper
2015-04-07 13:37             ` Mark Rutland
2015-04-07 12:40       ` Jason Cooper
     [not found]         ` <20150407124016.GD7873-fahSIxCzskDQ+YiMSub0/l6hYfS7NtTn@public.gmane.org>
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-wi1+55scjutkeb57/3fjtnbpr1lh4cv8@public.gmane.org \
    --cc=arm-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
    --cc=arnd-r2nGTMty4D4@public.gmane.org \
    --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=jason-NLaQJdtUoK4Be96aLqz0jA@public.gmane.org \
    --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=marc.zyngier-5wv7dgnIgG8@public.gmane.org \
    --cc=olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org \
    --cc=tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.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).