All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olof Johansson <olof@lixom.net>
To: Stefan Roese <sr@denx.de>
Cc: linuxppc-dev@ozlabs.org, jeff@garzik.org, netdev@vger.kernel.org
Subject: Re: [PATCH] net: NEWEMAC: Remove "rgmii-interface" from rgmii matching table
Date: Wed, 6 Feb 2008 10:01:57 -0600	[thread overview]
Message-ID: <20080206160157.GA18228@lixom.net> (raw)
In-Reply-To: <1202300519-7294-1-git-send-email-sr@denx.de>

On Wed, Feb 06, 2008 at 01:21:59PM +0100, Stefan Roese wrote:
> With the removal the the "rgmii-interface" device_type property from the
> dts files, the newemac driver needs an update to only rely on compatible
> property.

What about systems using an older dts, such as one kexec:ing from an
older kernel?

Just because the device tree source is distributed in the kernel tree
doesn't mean it can give up backwards compatibility.


-Olof

WARNING: multiple messages have this Message-ID (diff)
From: Olof Johansson <olof@lixom.net>
To: Stefan Roese <sr@denx.de>
Cc: jeff@garzik.org, linuxppc-dev@ozlabs.org, netdev@vger.kernel.org
Subject: Re: [PATCH] net: NEWEMAC: Remove "rgmii-interface" from rgmii matching table
Date: Wed, 6 Feb 2008 10:01:57 -0600	[thread overview]
Message-ID: <20080206160157.GA18228@lixom.net> (raw)
In-Reply-To: <1202300519-7294-1-git-send-email-sr@denx.de>

On Wed, Feb 06, 2008 at 01:21:59PM +0100, Stefan Roese wrote:
> With the removal the the "rgmii-interface" device_type property from the
> dts files, the newemac driver needs an update to only rely on compatible
> property.

What about systems using an older dts, such as one kexec:ing from an
older kernel?

Just because the device tree source is distributed in the kernel tree
doesn't mean it can give up backwards compatibility.


-Olof


  parent reply	other threads:[~2008-02-06 16:00 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-06 12:21 [PATCH] net: NEWEMAC: Remove "rgmii-interface" from rgmii matching table Stefan Roese
2008-02-06 12:21 ` Stefan Roese
2008-02-06 12:49 ` Josh Boyer
2008-02-06 12:49   ` Josh Boyer
2008-02-11 16:08   ` Jeff Garzik
2008-02-11 16:08     ` Jeff Garzik
2008-02-06 16:01 ` Olof Johansson [this message]
2008-02-06 16:01   ` Olof Johansson
2008-02-06 16:23   ` Josh Boyer
2008-02-06 16:23     ` Josh Boyer
2008-02-06 16:35     ` Olof Johansson
2008-02-06 16:35       ` Olof Johansson
2008-02-07  2:47       ` Benjamin Herrenschmidt
2008-02-07  2:47         ` Benjamin Herrenschmidt
  -- strict thread matches above, loose matches on Subject: below --
2008-01-16  9:37 Stefan Roese
2008-01-16  9:37 ` Stefan Roese
2008-01-16  9:39 ` David Gibson
2008-01-16  9:53 ` Benjamin Herrenschmidt
2008-01-16 15:01   ` Josh Boyer
2008-01-16 15:01     ` Josh Boyer
2008-01-30  6:16     ` Stefan Roese
2008-01-30  6:16       ` Stefan Roese
2008-01-30 23:14       ` Benjamin Herrenschmidt
2008-01-30 23:14         ` Benjamin Herrenschmidt
2008-02-05 21:12         ` Josh Boyer
2008-02-05 21:12           ` Josh Boyer
2008-02-05 21:18           ` Benjamin Herrenschmidt
2008-02-06 12:12           ` Jeff Garzik
2008-02-06 12:12             ` Jeff Garzik
2008-02-06 12:16             ` Stefan Roese
2008-02-06 12:16               ` Stefan Roese
2008-01-17 20:53 ` Benjamin Herrenschmidt

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=20080206160157.GA18228@lixom.net \
    --to=olof@lixom.net \
    --cc=jeff@garzik.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=netdev@vger.kernel.org \
    --cc=sr@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.