From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Kumar Gala <galak@codeaurora.org>
Cc: Jiri Slaby <jslaby@suse.cz>,
linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH 4/4] tty: serial: msm: Enable building msm_serial for ARCH_QCOM
Date: Thu, 30 Jan 2014 14:36:19 -0800 [thread overview]
Message-ID: <20140130223619.GB4046@kroah.com> (raw)
In-Reply-To: <1391107002-21470-5-git-send-email-galak@codeaurora.org>
On Thu, Jan 30, 2014 at 12:36:42PM -0600, Kumar Gala wrote:
> We've split Qualcomm MSM support into legacy and multiplatform. So add
> the ability to build the serial driver on the newer ARCH_QCOM
> multiplatform.
>
> Signed-off-by: Kumar Gala <galak@codeaurora.org>
> ---
> Greg,
>
> If we can get an ack on this, will probably go via the arm-soc tree to keep
> the patchset together.
Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
next prev parent reply other threads:[~2014-01-30 22:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-30 18:36 [PATCH 0/4] Split mach-msm into legacy and mach-qcom (multiplatform) Kumar Gala
2014-01-30 18:36 ` [PATCH 1/4] clocksource: qcom: Move clocksource code out of mach-msm Kumar Gala
2014-01-30 18:36 ` [PATCH 2/4] arm: qcom: Split Qualcomm support into legacy and multiplatform Kumar Gala
2014-01-31 19:10 ` Olof Johansson
2014-01-31 19:20 ` Arnd Bergmann
2014-01-31 19:25 ` Kumar Gala
2014-01-31 19:34 ` Arnd Bergmann
2014-01-31 19:45 ` Kumar Gala
2014-01-31 20:11 ` Rob Herring
2014-02-26 14:22 ` Kevin Hilman
2014-02-26 17:22 ` Kumar Gala
2014-02-26 23:03 ` Kevin Hilman
2014-01-30 18:36 ` [PATCH 3/4] clocksource: qcom: split building of legacy vs multiplatform support Kumar Gala
2014-01-30 18:36 ` [PATCH 4/4] tty: serial: msm: Enable building msm_serial for ARCH_QCOM Kumar Gala
2014-01-30 22:36 ` Greg Kroah-Hartman [this message]
2014-01-31 19:11 ` [PATCH 0/4] Split mach-msm into legacy and mach-qcom (multiplatform) 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=20140130223619.GB4046@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=galak@codeaurora.org \
--cc=jslaby@suse.cz \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.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).