From: Sylwester Nawrocki <s.nawrocki@samsung.com>
To: cw00.choi@samsung.com
Cc: Valentin Rothberg <valentinrothberg@gmail.com>,
Tomasz Figa <tomasz.figa@gmail.com>,
Mike Turquette <mturquette@linaro.org>,
Stephen Boyd <sboyd@codeaurora.org>,
Inki Dae <inki.dae@samsung.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-samsung-soc <linux-samsung-soc@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
devicetree <devicetree@vger.kernel.org>,
Paul Bolle <pebolle@tiscali.nl>
Subject: Re: ARCH_EXYNOS5433 missing in Kconfig
Date: Tue, 28 Apr 2015 11:58:36 +0200 [thread overview]
Message-ID: <553F59CC.7040008@samsung.com> (raw)
In-Reply-To: <CAGTfZH2yttvRsHXZUXQ7t37wmU=seg8Qoa=h=nat4EwJDY42Kw@mail.gmail.com>
Hello,
On 28/04/15 11:25, Chanwoo Choi wrote:
> Hi Valentin,
>
> On Mon, Apr 27, 2015 at 3:31 PM, Valentin Rothberg
> <valentinrothberg@gmail.com> wrote:
>> > Hi Chanwoo,
>> >
>> > this is a kind reminder that the issue mentioned below is still
>> > present and made its way to v4.1-rc1.
>
> I sent the patch[1] to fix it. And Sylwester said that he will pick
> this patchset on patch[2].
> [1] https://lkml.org/lkml/2015/4/27/237
> [2] https://lkml.org/lkml/2015/4/28/117
>
> Hi Sylwester,
> Could you apply a patch[1] on 4.2-rc2 to fix build warning?
Sure, I plan to send a pull request this week.
--
Regards,
Sylwester
next prev parent reply other threads:[~2015-04-28 9:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-10 15:32 ARCH_EXYNOS5433 missing in Kconfig Valentin Rothberg
2015-03-11 1:10 ` Chanwoo Choi
2015-03-11 8:21 ` Valentin Rothberg
2015-04-27 6:31 ` Valentin Rothberg
2015-04-28 9:25 ` Chanwoo Choi
2015-04-28 9:58 ` Sylwester Nawrocki [this message]
2015-04-28 10:21 ` Chanwoo Choi
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=553F59CC.7040008@samsung.com \
--to=s.nawrocki@samsung.com \
--cc=cw00.choi@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=inki.dae@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=mturquette@linaro.org \
--cc=pebolle@tiscali.nl \
--cc=sboyd@codeaurora.org \
--cc=tomasz.figa@gmail.com \
--cc=valentinrothberg@gmail.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;
as well as URLs for NNTP newsgroup(s).