From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: Fix duplicated Kconfig entries
Date: Wed, 12 Mar 2014 17:19:56 +0000 [thread overview]
Message-ID: <20140312171955.GR17083@arm.com> (raw)
In-Reply-To: <531F16C6.5030903@arm.com>
On Tue, Mar 11, 2014 at 01:59:34PM +0000, Sudeep Holla wrote:
> On 11/03/14 13:17, Mark Brown wrote:
> > From: Mark Brown <broonie@linaro.org>
> >
> > Probably due to rebasing over the lengthy time it took to get the patch
> > merged commit addea9ef055b (cpufreq: enable ARM drivers on arm64) added
> > a duplicate Power management options section. Add CPUfreq to the CPU
> > power management section and remove a duplicate include of the main
> > power section.
>
> This looks fine to me, but since commit addea9ef055b is only in Rafael's
> next tree, Catalin can't take this, so it makes sense to go through Rafael's
> tree, right ?
I actually took this patch and noticed that Rafael took it as well. The
above commit I think is only valid in the arm64 tree for -next.
--
Catalin
prev parent reply other threads:[~2014-03-12 17:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-11 13:17 [PATCH] arm64: Fix duplicated Kconfig entries Mark Brown
2014-03-11 13:59 ` Sudeep Holla
2014-03-12 17:19 ` Catalin Marinas [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=20140312171955.GR17083@arm.com \
--to=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.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.