linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Amit Kucheria <amit.kucheria@linaro.org>
To: Andy Gross <andy.gross@linaro.org>
Cc: Eduardo Valentin <edubezval@gmail.com>,
	Arnd Bergmann <arnd@arndb.de>,
	arm@kernel.org, khilman@baylibre.com,
	Olof Johansson <olof@lixom.net>,
	linux-arm-msm <linux-arm-msm@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Douglas Anderson <dianders@chromium.org>,
	Bjorn Andersson <bjorn.andersson@linaro.org>
Subject: Re: [GIT PULL] Qualcomm ARM64 DT updates for 4.20
Date: Sun, 28 Oct 2018 23:24:19 +0530	[thread overview]
Message-ID: <CAHLCerOd0BqAG+MVx1icm-yNMiW1U--iNzK9eeP7km1GnOx_PA@mail.gmail.com> (raw)
In-Reply-To: <20181025160822.GA16095@hector.c.hoisthospitality.com>

On Thu, Oct 25, 2018 at 9:38 PM Andy Gross <andy.gross@linaro.org> wrote:
>
> On Thu, Oct 25, 2018 at 10:55:32AM +0530, Amit Kucheria wrote:
>
> <snip>
>
> > Andy,
> >
> > While you acked the tsens thermal DT patches[1] so they could go
> > through the thermal tree[2] to avoid a dependency, Eduardo would
> > prefer the DT changes for tsens to go through the arch tree.
> >
> > To avoid a scenario where these DT changes don't get merged until the
> > next merge window, would you or arm-soc maintainers consider merging
> > them in -rc2 (after the thermal-soc tree gets merged)?
> >
> > For convenience, I've provided just the DT changes with all tags in a
> > separate branch on top of v4.19 here:
> > https://git.linaro.org/people/amit.kucheria/kernel.git/log/?h=up/thermal/tsens-preirq-cleanup-v4
> >
> > Regards,
> > Amit
> > [1] Here is a reference to the patch series with Andy's acks:
> > https://lore.kernel.org/lkml/cover.1536744310.git.amit.kucheria@linaro.org/T/
> > [2] Here is a link to Eduardo's tree containing a subset of the above
> > series (I don't yet see a pull request):
> > https://git.kernel.org/pub/scm/linux/kernel/git/evalenti/linux-soc-thermal.git/log/?h=linus
>
> I can just send a pull request for -rc1.  No biggie.
>

Thanks Andy.

FWIW, the dependency patches landed in Linus' tree.

  reply	other threads:[~2018-10-28 17:54 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-30 18:37 [GIT PULL] Qualcomm ARM64 Defconfig updates for 4.20 Andy Gross
2018-09-30 18:37 ` [GIT PULL] Qualcomm ARM64 DT " Andy Gross
2018-10-02  9:30   ` Arnd Bergmann
2018-10-05 14:29     ` Andy Gross
2018-10-25  5:25       ` Amit Kucheria
2018-10-25 16:08         ` Andy Gross
2018-10-28 17:54           ` Amit Kucheria [this message]
2018-11-07  6:15             ` Amit Kucheria
2018-09-30 18:38 ` [GIT PULL] Qualcomm Defconfig " Andy Gross
2018-10-01 15:59   ` Arnd Bergmann
2018-09-30 18:38 ` [GIT PULL] Qualcomm Driver " Andy Gross
2018-10-02  8:14   ` Arnd Bergmann
2018-09-30 18:38 ` [GIT PULL] Qualcomm Device Tree " Andy Gross
2018-10-02  9:36   ` Arnd Bergmann
2018-10-05 14:28     ` Andy Gross
2018-10-05 14:31       ` Arnd Bergmann
2018-11-29 10:10     ` Clément Péron
2018-10-01 16:00 ` [GIT PULL] Qualcomm ARM64 Defconfig " Arnd Bergmann

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=CAHLCerOd0BqAG+MVx1icm-yNMiW1U--iNzK9eeP7km1GnOx_PA@mail.gmail.com \
    --to=amit.kucheria@linaro.org \
    --cc=andy.gross@linaro.org \
    --cc=arm@kernel.org \
    --cc=arnd@arndb.de \
    --cc=bjorn.andersson@linaro.org \
    --cc=dianders@chromium.org \
    --cc=edubezval@gmail.com \
    --cc=khilman@baylibre.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olof@lixom.net \
    /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).