From: Maurus Cuelenaere <mcuelenaere@gmail.com>
To: Kukjin Kim <kgene.kim@samsung.com>
Cc: 'Kyungmin Park' <kmpark@infradead.org>,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, ben-linux@fluff.org,
'Russell King' <rmk@arm.linux.org.uk>
Subject: Re: [PATCH] ARM: Update number of VIC
Date: Sun, 12 Sep 2010 23:08:30 +0200 [thread overview]
Message-ID: <4C8D414E.1010501@gmail.com> (raw)
In-Reply-To: <000001cb50e2$50f11940$f2d34bc0$%kim@samsung.com>
Op 10-09-10 14:18, Kukjin Kim schreef:
> Kyungmin Park wrote:
>>
>> Even though it required. I still think ben's patch is better approaches.
>
> Please let me know where it is...I couldn't find it.
I think he means this:
http://git.fluff.org/gitweb?p=bjdooks/linux.git;a=commitdiff;h=57c364b57fbcfd5b084e5edb6776da1ef583c2cf
--
Maurus Cuelenaere
WARNING: multiple messages have this Message-ID (diff)
From: mcuelenaere@gmail.com (Maurus Cuelenaere)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: Update number of VIC
Date: Sun, 12 Sep 2010 23:08:30 +0200 [thread overview]
Message-ID: <4C8D414E.1010501@gmail.com> (raw)
In-Reply-To: <000001cb50e2$50f11940$f2d34bc0$%kim@samsung.com>
Op 10-09-10 14:18, Kukjin Kim schreef:
> Kyungmin Park wrote:
>>
>> Even though it required. I still think ben's patch is better approaches.
>
> Please let me know where it is...I couldn't find it.
I think he means this:
http://git.fluff.org/gitweb?p=bjdooks/linux.git;a=commitdiff;h=57c364b57fbcfd5b084e5edb6776da1ef583c2cf
--
Maurus Cuelenaere
next prev parent reply other threads:[~2010-09-12 21:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-13 11:09 [PATCH] ARM: Update number of VIC Kukjin Kim
2010-08-13 11:09 ` Kukjin Kim
2010-08-16 1:01 ` Kyungmin Park
2010-08-16 1:01 ` Kyungmin Park
2010-09-10 12:18 ` Kukjin Kim
2010-09-10 12:18 ` Kukjin Kim
2010-09-12 21:08 ` Maurus Cuelenaere [this message]
2010-09-12 21:08 ` Maurus Cuelenaere
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=4C8D414E.1010501@gmail.com \
--to=mcuelenaere@gmail.com \
--cc=ben-linux@fluff.org \
--cc=kgene.kim@samsung.com \
--cc=kmpark@infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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.