[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181210234730.GH6707@atomide.com>
Date: Mon, 10 Dec 2018 15:47:30 -0800
From: Tony Lindgren <tony@...mide.com>
To: Nishanth Menon <nm@...com>
Cc: Sekhar Nori <nsekhar@...com>, Faiz Abbas <faiz_abbas@...com>,
linux-kernel@...r.kernel.org, devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, mark.rutland@....com,
robh+dt@...nel.org, t-kristo@...com, kishon@...com,
ulf.hansson@...aro.org, adrian.hunter@...el.com,
michal.simek@...inx.com, Arnd Bergmann <arnd@...db.de>
Subject: Re: [PATCH 2/2] arm64: dts: ti: k3-am654-base-board: Add MMC/SD
support
* Nishanth Menon <nm@...com> [181210 12:07]:
> I really am curious how Arnd / Tony actually pull this one off.. If they
> have continous cron job for checking if your patch is ready... I doubt
> it..
The only way that works in a distributed manner is for the patch
authors to resend after the dependencies have cleared.
As some people don't know this, at least I try to reply with
something about tagging patch as read and assuming it will get
resent after dependencies have cleard.
Otherwise the todo list just keeps growing eternally :)
Regards,
Tony
Powered by blists - more mailing lists