From: Andrew Lunn <andrew@lunn.ch>
To: "Köry Maincent" <kory.maincent@bootlin.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
netdev <netdev@vger.kernel.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Sergey Shtylyov <s.shtylyov@omp.ru>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>,
Biju Das <biju.das.jz@bp.renesas.com>,
Sergei Shtylyov <sergei.shtylyov@gmail.com>,
Adam Ford <aford173@gmail.com>,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
Yang Yingliang <yangyingliang@huawei.com>
Subject: Re: [PATCH] net: renesas: Fix rgmii-id delays
Date: Tue, 19 Oct 2021 17:41:49 +0200 [thread overview]
Message-ID: <YW7nPfzjstmeoMbf@lunn.ch> (raw)
In-Reply-To: <20211019173520.0154a8cb@kmaincent-XPS-13-7390>
> When people update the kernel version don't they update also the devicetree?
DT is ABI. Driver writers should not break old blobs running on new
kernels. Often the DT blob is updated with the kernel, but it is not
required. It could be stored in a hard to reach place, shared with
u-boot etc.
Andrew
next prev parent reply other threads:[~2021-10-19 15:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-19 14:57 [PATCH] net: renesas: Fix rgmii-id delays Kory Maincent
2021-10-19 15:13 ` Geert Uytterhoeven
2021-10-19 15:35 ` Köry Maincent
2021-10-19 15:41 ` Andrew Lunn [this message]
2021-10-19 15:57 ` Thomas Petazzoni
2021-10-19 20:05 ` Geert Uytterhoeven
2021-10-20 8:53 ` Köry Maincent
2021-10-20 9:05 ` Geert Uytterhoeven
2021-10-20 12:16 ` Andrew Lunn
2021-10-19 15:44 ` Geert Uytterhoeven
2021-10-19 15:47 ` Andrew Lunn
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=YW7nPfzjstmeoMbf@lunn.ch \
--to=andrew@lunn.ch \
--cc=aford173@gmail.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=davem@davemloft.net \
--cc=geert@linux-m68k.org \
--cc=kory.maincent@bootlin.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=s.shtylyov@omp.ru \
--cc=sergei.shtylyov@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=yangyingliang@huawei.com \
--cc=yoshihiro.shimoda.uh@renesas.com \
/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