From: Stephen Boyd <sboyd@codeaurora.org>
To: Kumar Gala <galak@codeaurora.org>
Cc: arm@kernel.org, David Brown <davidb@codeaurora.org>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Kevin Hilman <khilman@linaro.org>,
Rohit Vaswani <rvaswani@codeaurora.org>
Subject: Re: [GIT PULL] qcom cleanups for v3.15
Date: Wed, 19 Feb 2014 10:56:11 -0800 [thread overview]
Message-ID: <5304FE4B.1020408@codeaurora.org> (raw)
In-Reply-To: <FE60A8A0-B1C4-46F2-96E8-95FE25503DAF@codeaurora.org>
On 02/19/14 07:20, Kumar Gala wrote:
> On Feb 18, 2014, at 6:06 PM, Stephen Boyd <sboyd@codeaurora.org> wrote:
>
>> On 02/10/14 15:23, Kumar Gala wrote:
>>> Kumar Gala (6):
>>> ARM: dts: msm: split out msm8660 and msm8960 soc into dts include
>>> ARM: msm: kill off hotplug.c
>>> clocksource: qcom: Move clocksource code out of mach-msm
>>> ARM: qcom: Split Qualcomm support into legacy and multiplatform
>> Sorry to nag, but can you please address my comment on this patch?
> Which comment? The copyright one or something else?
>
Yes the copyright one.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
WARNING: multiple messages have this Message-ID (diff)
From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] qcom cleanups for v3.15
Date: Wed, 19 Feb 2014 10:56:11 -0800 [thread overview]
Message-ID: <5304FE4B.1020408@codeaurora.org> (raw)
In-Reply-To: <FE60A8A0-B1C4-46F2-96E8-95FE25503DAF@codeaurora.org>
On 02/19/14 07:20, Kumar Gala wrote:
> On Feb 18, 2014, at 6:06 PM, Stephen Boyd <sboyd@codeaurora.org> wrote:
>
>> On 02/10/14 15:23, Kumar Gala wrote:
>>> Kumar Gala (6):
>>> ARM: dts: msm: split out msm8660 and msm8960 soc into dts include
>>> ARM: msm: kill off hotplug.c
>>> clocksource: qcom: Move clocksource code out of mach-msm
>>> ARM: qcom: Split Qualcomm support into legacy and multiplatform
>> Sorry to nag, but can you please address my comment on this patch?
> Which comment? The copyright one or something else?
>
Yes the copyright one.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
next prev parent reply other threads:[~2014-02-19 18:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-10 23:23 [GIT PULL] qcom cleanups for v3.15 Kumar Gala
2014-02-10 23:23 ` Kumar Gala
2014-02-18 16:41 ` Kumar Gala
2014-02-18 16:41 ` Kumar Gala
2014-02-19 0:06 ` Stephen Boyd
2014-02-19 0:06 ` Stephen Boyd
2014-02-19 15:20 ` Kumar Gala
2014-02-19 15:20 ` Kumar Gala
2014-02-19 18:56 ` Stephen Boyd [this message]
2014-02-19 18:56 ` Stephen Boyd
2014-02-19 19:30 ` Kumar Gala
2014-02-19 19:30 ` Kumar Gala
2014-02-19 20:13 ` Stephen Boyd
2014-02-19 20:13 ` Stephen Boyd
2014-02-20 8:52 ` Olof Johansson
2014-02-20 8:52 ` Olof Johansson
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=5304FE4B.1020408@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=davidb@codeaurora.org \
--cc=galak@codeaurora.org \
--cc=khilman@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--cc=rvaswani@codeaurora.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 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.