From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: Andy Gross <agross@codeaurora.org>, linux-kernel@vger.kernel.org
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-arm-msm@vger.kernel.org, Kumar Gala <galak@codeaurora.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [Patch v2 1/4] soc: Placeholder files for drivers/soc
Date: Thu, 24 Apr 2014 12:36:25 -0400 [thread overview]
Message-ID: <53593D89.1020703@ti.com> (raw)
In-Reply-To: <1398357082-5102-2-git-send-email-agross@codeaurora.org>
On Thursday 24 April 2014 12:31 PM, Andy Gross wrote:
> Add placeholder Kconfig and linkage for driver/soc.
>
> The first patch set that implemented this was authored by Santosh Shilimkar:
> https://lkml.org/lkml/2014/2/28/567
>
> Signed-off-by: Andy Gross <agross@codeaurora.org>
> ---
Good to see these patches on the list. Me and Kumar spoke about it
many times before.
BTW, I just posted updated version. Feel free to use the from it instead
of 4subject one.
Regards,
Santosh
next prev parent reply other threads:[~2014-04-24 16:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-24 16:31 [Patch v2 0/4] Introduce drivers/soc and add QCOM GSBI driver Andy Gross
2014-04-24 16:31 ` [Patch v2 1/4] soc: Placeholder files for drivers/soc Andy Gross
2014-04-24 16:36 ` Santosh Shilimkar [this message]
2014-05-06 17:06 ` Kumar Gala
2014-04-24 16:31 ` [Patch v2 2/4] soc: qcom: Add device tree binding for GSBI Andy Gross
2014-04-24 16:31 ` [Patch v2 3/4] soc: qcom: Add GSBI driver Andy Gross
2014-05-23 18:52 ` Stephen Boyd
2014-04-24 16:31 ` [Patch v2 4/4] tty: serial: msm: Remove direct access to GSBI Andy Gross
2014-05-29 15:14 ` Kumar Gala
[not found] ` <A56B810D-869A-4E4F-BC29-C9B0F6CDCE79-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2014-05-29 15:43 ` Greg Kroah-Hartman
2014-05-29 16:05 ` Kumar Gala
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=53593D89.1020703@ti.com \
--to=santosh.shilimkar@ti.com \
--cc=agross@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@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).