From: Andy Gross <andy.gross@linaro.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: arm-soc <arm@kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
linux-arm-msm@vger.kernel.org,
Sudeep Holla <sudeep.holla@arm.com>,
Loys Ollivier <lollivier@baylibre.com>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Rob Herring <robh@kernel.org>, DTML <devicetree@vger.kernel.org>
Subject: Re: [GIT PULL] Qualcomm Fixes for 4.16
Date: Mon, 22 Jan 2018 10:14:45 -0600 [thread overview]
Message-ID: <20180122161445.GB4402@hector> (raw)
In-Reply-To: <CAK8P3a2M4xqHO3tRokqaudxO8=+ifj6Ve3vW1L_Dv2KCykbUtw@mail.gmail.com>
On Mon, Jan 22, 2018 at 12:33:11PM +0100, Arnd Bergmann wrote:
> On Sun, Jan 21, 2018 at 11:02 PM, Andy Gross <andy.gross@linaro.org> wrote:
> > Arnd/Olof/Kevin,
> >
> > Please take this fix for 4.16. This applies on top of the current next
> > (next-20190119).
> >
> > Thanks,
> >
> > Andy
> >
> > The following changes since commit 761914dd2975bc443024f0ec10a66a26b7186ec2:
> >
> > Add linux-next specific files for 20180119 (2018-01-19 17:51:17 +1100)
> >
> > are available in the git repository at:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/agross/linux.git tags/qcom-fixes-for-4.16
>
> I assume you didn't actually mean to send a pull request based on top
> of linux-next
> but instead had a branch on top of the one you sent previously.
>
> I cherry-picked the one commit you want into the next/drivers branch!
Ack, not sure what I was thinking. Glad you sorted it out.
Thanks for taking this in!
Andy
WARNING: multiple messages have this Message-ID (diff)
From: andy.gross@linaro.org (Andy Gross)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Qualcomm Fixes for 4.16
Date: Mon, 22 Jan 2018 10:14:45 -0600 [thread overview]
Message-ID: <20180122161445.GB4402@hector> (raw)
In-Reply-To: <CAK8P3a2M4xqHO3tRokqaudxO8=+ifj6Ve3vW1L_Dv2KCykbUtw@mail.gmail.com>
On Mon, Jan 22, 2018 at 12:33:11PM +0100, Arnd Bergmann wrote:
> On Sun, Jan 21, 2018 at 11:02 PM, Andy Gross <andy.gross@linaro.org> wrote:
> > Arnd/Olof/Kevin,
> >
> > Please take this fix for 4.16. This applies on top of the current next
> > (next-20190119).
> >
> > Thanks,
> >
> > Andy
> >
> > The following changes since commit 761914dd2975bc443024f0ec10a66a26b7186ec2:
> >
> > Add linux-next specific files for 20180119 (2018-01-19 17:51:17 +1100)
> >
> > are available in the git repository at:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/agross/linux.git tags/qcom-fixes-for-4.16
>
> I assume you didn't actually mean to send a pull request based on top
> of linux-next
> but instead had a branch on top of the one you sent previously.
>
> I cherry-picked the one commit you want into the next/drivers branch!
Ack, not sure what I was thinking. Glad you sorted it out.
Thanks for taking this in!
Andy
next prev parent reply other threads:[~2018-01-22 16:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-21 22:02 [GIT PULL] Qualcomm Fixes for 4.16 Andy Gross
2018-01-21 22:02 ` Andy Gross
2018-01-22 11:33 ` Arnd Bergmann
2018-01-22 11:33 ` Arnd Bergmann
2018-01-22 16:14 ` Andy Gross [this message]
2018-01-22 16:14 ` Andy Gross
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=20180122161445.GB4402@hector \
--to=andy.gross@linaro.org \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=lollivier@baylibre.com \
--cc=robh@kernel.org \
--cc=sudeep.holla@arm.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.