From: Peter Hurley <peter@hurleysoftware.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, Kumar Gala <galak@codeaurora.org>
Subject: Re: [PATCH] soc: Remove duplicate Kconfig include
Date: Tue, 30 Dec 2014 08:54:48 -0500 [thread overview]
Message-ID: <54A2AEA8.7060204@hurleysoftware.com> (raw)
In-Reply-To: <1419947424-9555-1-git-send-email-peter@hurleysoftware.com>
On 12/30/2014 08:50 AM, Peter Hurley wrote:
> commit 3a6e08218f36baa9c49282ad2fe0dfbf001d8f23
> ("soc: Introduce drivers/soc place-holder for SOC specific drivers")
> added a duplicate source for soc Kconfig, which had already been
> introduced by commit 41f93af900a20d1a0a358b522b5129c89677e9dc
> ("soc: ti: add Keystone Navigator QMSS driver").
Greg,
Would you take this patch please? Both Santosh and Sandeep's emails
bounced.
Regards,
Peter Hurley
prev parent reply other threads:[~2014-12-30 13:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-30 13:50 [PATCH] soc: Remove duplicate Kconfig include Peter Hurley
2014-12-30 13:54 ` Peter Hurley [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=54A2AEA8.7060204@hurleysoftware.com \
--to=peter@hurleysoftware.com \
--cc=galak@codeaurora.org \
--cc=gregkh@linuxfoundation.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