From: Stephen Boyd <sboyd@codeaurora.org>
To: Andy Gross <agross@codeaurora.org>, Kumar Gala <galak@codeaurora.org>
Cc: David Brown <davidb@codeaurora.org>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: update Qualcomm support entry
Date: Mon, 26 Jan 2015 16:51:11 -0800 [thread overview]
Message-ID: <54C6E0FF.9000103@codeaurora.org> (raw)
In-Reply-To: <1421901564-8854-1-git-send-email-agross@codeaurora.org>
On 01/21/15 20:39, Andy Gross wrote:
> Added myself as a co-maintainer. Updated the files to include the Qualcomm SoC
> directory. Added linux-soc mailing list.
>
> Signed-off-by: Andy Gross <agross@codeaurora.org>
> ---
> MAINTAINERS | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 93409ad..2af6e23 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -1284,9 +1284,12 @@ S: Maintained
> ARM/QUALCOMM SUPPORT
> M: Kumar Gala <galak@codeaurora.org>
> M: David Brown <davidb@codeaurora.org>
> +M: Andy Gross <agross@codeaurora.org>
> L: linux-arm-msm@vger.kernel.org
> +L: linux-soc@vger.kernel.org
Should this be here? I'd think we would want this on some more top-level
drivers/soc/ entry so that mach-qcom changes don't go to the linux-soc
list when they're not relevant to linux-soc.
> S: Maintained
> F: arch/arm/mach-qcom/
> +F: drivers/soc/qcom
> T: git git://git.kernel.org/pub/scm/linux/kernel/git/galak/linux-qcom.git
>
> ARM/RADISYS ENP2611 MACHINE SUPPORT
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
prev parent reply other threads:[~2015-01-27 0:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-22 4:39 [PATCH] MAINTAINERS: update Qualcomm support entry Andy Gross
2015-01-22 4:46 ` Joe Perches
2015-01-22 21:46 ` Andy Gross
2015-01-23 16:27 ` Kumar Gala
2015-01-27 0:51 ` Stephen Boyd [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=54C6E0FF.9000103@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=agross@codeaurora.org \
--cc=davidb@codeaurora.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