From: Kukjin Kim <kgene.kim@samsung.com>
To: Javier Martinez Canillas <javier@dowhile0.org>
Cc: Kukjin Kim <kgene.kim@samsung.com>,
Pankaj Dubey <pankaj.dubey@samsung.com>,
"linux-samsung-soc@vger.kernel.org"
<linux-samsung-soc@vger.kernel.org>,
Russell King <linux@arm.linux.org.uk>,
thomas.ab@samsung.com,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] ARM: EXYNOS: fix typo in static struct name "exynos5_list_diable_wfi_wfe"
Date: Thu, 13 Nov 2014 11:40:05 +0900 [thread overview]
Message-ID: <54641A05.9030107@samsung.com> (raw)
In-Reply-To: <CABxcv==Hjfi+-Mt63YQaCtC3Wj12WFfU6biwmiVEFQvqAp3DBA@mail.gmail.com>
On 11/11/14 18:54, Javier Martinez Canillas wrote:
> Hello Kukjin,
>
>>
>> After this patch, "[PATCH v9 1/2] ARM: EXYNOS: Add platform driver
>> support for Exynos PMU" [0] does not apply cleanly anymore.
>>
>
> I see that you already picked all the Exynos S2R patches on your
> v3.19-next/mach-exynos branch and also resolved that conflict.
>
Yes, but I couldn't merge it into -next because of some conflicts
between for-next and mach-exynos branch at that time.
Note I've merged into -next just now, so if any problems in -next,
please let us know.
> Is just that this branch was not merged in your for-next branch and
> that's why I didn't see the patches in linux-next.
>
> Sorry for the noise.
No problem, thanks.
- Kukjin
next prev parent reply other threads:[~2014-11-13 2:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-28 9:50 [PATCH] ARM: EXYNOS: fix typo in static struct name "exynos5_list_diable_wfi_wfe" Pankaj Dubey
2014-10-28 10:33 ` Kukjin Kim
2014-11-11 9:44 ` Javier Martinez Canillas
2014-11-11 9:54 ` Javier Martinez Canillas
2014-11-13 2:40 ` Kukjin Kim [this message]
2014-11-13 4:27 ` Pankaj Dubey
2014-11-13 4:42 ` Kukjin Kim
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=54641A05.9030107@samsung.com \
--to=kgene.kim@samsung.com \
--cc=javier@dowhile0.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=pankaj.dubey@samsung.com \
--cc=thomas.ab@samsung.com \
/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