From: Francesco Dolcini <francesco.dolcini@toradex.com>
To: Tom Rini <trini@konsulko.com>
Cc: Marcel Ziswiler <marcel.ziswiler@toradex.com>,
"festevam@gmail.com" <festevam@gmail.com>,
"u-boot@lists.denx.de" <u-boot@lists.denx.de>,
"uboot-imx@nxp.com" <uboot-imx@nxp.com>,
"sbabic@denx.de" <sbabic@denx.de>,
Francesco Dolcini <francesco.dolcini@toradex.com>
Subject: Re: [PATCH] ARM: dts: colibri-imx6ull: fix mac address passing
Date: Fri, 1 Apr 2022 16:05:44 +0200 [thread overview]
Message-ID: <20220401140544.GA48207@francesco-nb.int.toradex.com> (raw)
In-Reply-To: <20220401140404.GY14476@bill-the-cat>
On Fri, Apr 01, 2022 at 10:04:04AM -0400, Tom Rini wrote:
> On Fri, Apr 01, 2022 at 02:01:25PM +0000, Marcel Ziswiler wrote:
> > On Fri, 2022-04-01 at 09:43 -0400, Tom Rini wrote:
> > > On Fri, Apr 01, 2022 at 12:57:40PM +0000, Marcel Ziswiler wrote:
> > >
> > > > May I inquire about the status of this one? Thanks!
> > >
> > > Should I take it for this release?
> >
> > Yes, please. Thanks!
>
> And, re-reading the whole thread in patchwork, I'm going to assume /
> hope for a full dts resync for the next merge window.
We are in process to update the Linux kernel DTS files now, as soon as
this is done we will do the sync. Doing it now would not make sense.
Francesco
next prev parent reply other threads:[~2022-04-01 14:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-23 7:55 [PATCH] ARM: dts: colibri-imx6ull: fix mac address passing Francesco Dolcini
2021-09-23 11:36 ` Tom Rini
2021-09-23 11:50 ` Francesco Dolcini
2021-09-23 11:57 ` Tom Rini
2022-02-04 17:41 ` Marcel Ziswiler
2022-02-04 17:55 ` Fabio Estevam
2022-04-01 12:57 ` Marcel Ziswiler
2022-04-01 13:43 ` Tom Rini
2022-04-01 14:01 ` Marcel Ziswiler
2022-04-01 14:02 ` Tom Rini
2022-04-01 14:04 ` Tom Rini
2022-04-01 14:05 ` Francesco Dolcini [this message]
2022-04-01 14:28 ` 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=20220401140544.GA48207@francesco-nb.int.toradex.com \
--to=francesco.dolcini@toradex.com \
--cc=festevam@gmail.com \
--cc=marcel.ziswiler@toradex.com \
--cc=sbabic@denx.de \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=uboot-imx@nxp.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 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.