linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: kgene.kim@samsung.com (Kukjin Kim)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: S3C64XX: Fix dev-spi build
Date: Wed, 08 Sep 2010 21:21:02 +0900	[thread overview]
Message-ID: <003e01cb4f50$529dc380$f7d94a80$%kim@samsung.com> (raw)
In-Reply-To: <20100908121237.GA9196@rakim.wolfsonmicro.main>

Mark Brown wrote:
> 
> On Wed, Sep 08, 2010 at 08:52:48PM +0900, Kukjin Kim wrote:
> 
> > Anyway, this is ok to me...and how about mach-s5pc100/dev-spi.c?
> 
> I've not looked at S5PC100 since I don't have any boards with that.
> 
Ok..I will sort out others.

> > And I think, this should be gone to upstream via Ben's tree...
> 
> Yup, though the MAINTAINERS pattern matches you both.  I'm resending due
> to lack of any response from Ben.

mm...if he busy, I will/can do it :-)

Thanks.

Best regards,
Kgene.
--
Kukjin Kim <kgene.kim@samsung.com>, Senior Engineer,
SW Solution Development Team, Samsung Electronics Co., Ltd.

  reply	other threads:[~2010-09-08 12:21 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-08 10:25 [PATCH 1/2] ARM: S3C64XX: Fix dev-spi build Mark Brown
2010-09-08 10:25 ` [PATCH 2/2] ARM: S3C64XX: Prototype SPI devices Mark Brown
2010-09-08 12:39   ` Kukjin Kim
2010-09-08 12:46     ` Mark Brown
2010-09-09 11:18       ` Kukjin Kim
2010-09-09 11:33         ` Mark Brown
2010-09-08 11:52 ` [PATCH 1/2] ARM: S3C64XX: Fix dev-spi build Kukjin Kim
2010-09-08 12:12   ` Mark Brown
2010-09-08 12:21     ` Kukjin Kim [this message]
2010-09-08 14:17   ` Jassi Brar
2010-09-08 16:01     ` Mark Brown
2010-09-09  1:17       ` Jassi Brar
2010-09-09 11:11       ` Kukjin Kim
2010-09-09 11:34         ` Mark Brown
  -- strict thread matches above, loose matches on Subject: below --
2010-08-20 15:38 Mark Brown
2010-08-21  1:59 ` Jassi Brar

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='003e01cb4f50$529dc380$f7d94a80$%kim@samsung.com' \
    --to=kgene.kim@samsung.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 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).