From: Andy Gross <agross@codeaurora.org>
To: Olof Johansson <olof@lixom.net>
Cc: arm@kernel.org, Arnd Bergmann <arnd@arndb.de>,
linux-arm-msm@vger.kernel.org,
Bjorn Andersson <bjorn.andersson@sonymobile.com>
Subject: Re: [GIT PULL] qcom fixes for 4.4
Date: Sun, 1 Nov 2015 22:54:20 -0600 [thread overview]
Message-ID: <20151102045420.GA2007@qualcomm.com> (raw)
In-Reply-To: <20151031015258.GD1722@localhost>
On Sat, Oct 31, 2015 at 01:52:58AM +0000, Olof Johansson wrote:
> Hi Andy,
>
>
> On Fri, Oct 30, 2015 at 12:41:07PM -0500, Andy Gross wrote:
> > The following changes since commit 163d956d49e0911af28ae6bc7d1cb0e53881fdea:
> >
> > Merge tag 'qcom-soc-for-4.4' into base-4.3 (2015-10-30 10:59:20 -0500)
> >
> > are available in the git repository at:
> >
> >
> > git://codeaurora.org/quic/kernel/agross-msm.git tags/qcom-fixes-for-4.4
> >
> > for you to fetch changes up to 5c5790a4eb77248965b5d8782debf4fc01687d0c:
> >
> > soc: qcom: smd-rpm: Correct size of outgoing message (2015-10-30 11:57:48 -0500)
>
> This branch has a quite complicated history with several merges. It
> seems to me that it can stand on its own as a fix on top of 50e1b29b4438,
> which is in our next/drivers branch.
>
> So, I've just cherry-picked this specific fix onto that branch. Given
> the proximity to the merge window I'm gambling that this doesn't mess
> up your downstream branches too much.
Yes, it should work just fine with the single cherrypick. Thanks for picking it
up.
--
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
prev parent reply other threads:[~2015-11-02 4:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-30 17:41 [GIT PULL] qcom fixes for 4.4 Andy Gross
2015-10-31 1:52 ` Olof Johansson
2015-11-02 4:54 ` Andy Gross [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=20151102045420.GA2007@qualcomm.com \
--to=agross@codeaurora.org \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=bjorn.andersson@sonymobile.com \
--cc=linux-arm-msm@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 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.