From: Tony Lindgren <tony@atomide.com>
To: Nishanth Menon <nm@ti.com>
Cc: Sekhar Nori <nsekhar@ti.com>, Faiz Abbas <faiz_abbas@ti.com>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, mark.rutland@arm.com,
robh+dt@kernel.org, t-kristo@ti.com, kishon@ti.com,
ulf.hansson@linaro.org, adrian.hunter@intel.com,
michal.simek@xilinx.com, Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH 2/2] arm64: dts: ti: k3-am654-base-board: Add MMC/SD support
Date: Mon, 10 Dec 2018 15:47:30 -0800 [thread overview]
Message-ID: <20181210234730.GH6707@atomide.com> (raw)
In-Reply-To: <20181210120647.i3ply3p7umvedb3u@akan>
* Nishanth Menon <nm@ti.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
next prev parent reply other threads:[~2018-12-10 23:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-07 8:42 [PATCH 0/2] Add DT Support for MMCSD in Am65x-evm Faiz Abbas
2018-12-07 8:42 ` [PATCH 1/2] arm64: dts: ti: k3-am654: Add Support for MMC/SD Faiz Abbas
2018-12-08 5:26 ` Vignesh R
2018-12-08 15:45 ` Nishanth Menon
2018-12-10 13:30 ` Faiz Abbas
2018-12-07 8:42 ` [PATCH 2/2] arm64: dts: ti: k3-am654-base-board: Add MMC/SD support Faiz Abbas
2018-12-08 15:54 ` Nishanth Menon
2018-12-10 8:03 ` Sekhar Nori
2018-12-10 12:06 ` Nishanth Menon
2018-12-10 12:40 ` Sekhar Nori
2018-12-10 13:33 ` Faiz Abbas
2018-12-10 13:52 ` Nishanth Menon
2018-12-10 13:49 ` Nishanth Menon
2018-12-10 23:47 ` Tony Lindgren [this message]
2018-12-11 13:32 ` Sekhar Nori
2018-12-11 5:58 ` Vignesh R
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=20181210234730.GH6707@atomide.com \
--to=tony@atomide.com \
--cc=adrian.hunter@intel.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=faiz_abbas@ti.com \
--cc=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=michal.simek@xilinx.com \
--cc=nm@ti.com \
--cc=nsekhar@ti.com \
--cc=robh+dt@kernel.org \
--cc=t-kristo@ti.com \
--cc=ulf.hansson@linaro.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;
as well as URLs for NNTP newsgroup(s).