From: sudeep.holla@arm•com (Sudeep Holla)
To: linux-arm-kernel@lists•infradead.org
Subject: [Linaro-acpi] [PATCH] arm64: Fix duplicated Kconfig entries again
Date: Tue, 25 Mar 2014 10:00:31 +0000 [thread overview]
Message-ID: <533153BF.3070308@arm.com> (raw)
In-Reply-To: <1395738060-18489-1-git-send-email-hanjun.guo@linaro.org>
Hi Hanjun,
On 25/03/14 09:00, Hanjun Guo wrote:
> After commit 74397174989e5 (arm64: Fix duplicated Kconfig entries),
> I still get a duplicate Power management options section in linux-next
> git repo, may be due to some merge conflicts, anyway, fix that in this
> patch.
>
I reported this and Mark Brown posted the patch[1].
I assumed it is already pulled, but looks like that's not the case.
Regards,
Sudeep
[1] http://www.spinics.net/lists/arm-kernel/msg314472.html
next prev parent reply other threads:[~2014-03-25 10:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-25 9:00 [PATCH] arm64: Fix duplicated Kconfig entries again Hanjun Guo
2014-03-25 10:00 ` Sudeep Holla [this message]
2014-03-25 11:09 ` Hanjun Guo
2014-03-27 11:12 ` Sudeep Holla
2014-03-27 12:34 ` Hanjun Guo
2014-03-27 15:18 ` Rafael J. Wysocki
2014-04-03 8:35 ` Hanjun Guo
2014-04-03 8:41 ` Viresh Kumar
2014-04-03 8:51 ` Catalin Marinas
2014-04-03 9:27 ` Hanjun Guo
2014-04-03 9:30 ` Hanjun Guo
2014-04-03 9:38 ` Viresh Kumar
2014-04-03 11:01 ` Hanjun Guo
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=533153BF.3070308@arm.com \
--to=sudeep.holla@arm$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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