From: Patrick Wildt <patrick@blueri.se>
To: Tom Rini <trini@konsulko.com>
Cc: Stefano Babic <sbabic@denx.de>,
Fabio Estevam <festevam@gmail.com>,
u-boot@lists.denx.de, "Lukas F. Hartmann" <lukas@mntre.com>,
Heiko Thiery <heiko.thiery@gmail.com>,
Vagrant Cascadian <vagrant@debian.org>
Subject: Re: [PATCH v4 0/2] Add MNT Reform 2 board support
Date: Wed, 12 Jan 2022 23:05:27 +0100 [thread overview]
Message-ID: <Yd9Qp4Z8FEvSzzyS@ryzen.fritz.box> (raw)
In-Reply-To: <20220112220328.GF9207@bill-the-cat>
On Wed, Jan 12, 2022 at 05:03:28PM -0500, Tom Rini wrote:
> On Wed, Jan 12, 2022 at 10:29:50PM +0100, Patrick Wildt wrote:
>
> > Hi,
> >
> > is there anything I can do to help get attention on this patchset?
>
> Not a whole lot, sorry. The big hold up right now is that Stefano is
> out currently and that means a number of imx patches are still
> outstanding.
>
> > I'm now regularly rebasing the patchset and adjusting it to all the
> > changes that happen in-tree to the other boards to keep the patchset
> > compiling and working.
> >
> > Right now I'd have to send a v5 to remove a single define that's now
> > obsolete and hence breaks compilation, but I'm not sure it's worth
> > sending it out if there's gonna be a v6 and v7 for another rebase
> > soon anyway.
>
> Aside from what I just sent out in reply to Fabio's comment, it probably
> makes sense to hold off on reposting until Stefano is back.
Thanks to both of you for the feedback!
Cheers,
Patrick
prev parent reply other threads:[~2022-01-12 22:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-08 15:04 [PATCH v4 0/2] Add MNT Reform 2 board support Patrick Wildt
2022-01-08 15:04 ` [PATCH v4 1/2] arm: dts: imx8mq: add MNT Reform 2 Patrick Wildt
2022-01-12 21:35 ` Fabio Estevam
2022-01-08 15:05 ` [PATCH v4 2/2] board: mntre: imx8mq: Add MNT Reform 2 board support Patrick Wildt
2022-01-12 21:47 ` Fabio Estevam
2022-01-12 22:00 ` Tom Rini
2022-02-18 19:21 ` Stefano Babic
2022-01-12 21:29 ` [PATCH v4 0/2] " Patrick Wildt
2022-01-12 22:03 ` Tom Rini
2022-01-12 22:05 ` Patrick Wildt [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=Yd9Qp4Z8FEvSzzyS@ryzen.fritz.box \
--to=patrick@blueri.se \
--cc=festevam@gmail.com \
--cc=heiko.thiery@gmail.com \
--cc=lukas@mntre.com \
--cc=sbabic@denx.de \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=vagrant@debian.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