All of lore.kernel.org
 help / color / mirror / Atom feed
From: kgene.kim@samsung.com (Kukjin Kim)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] ARM: S3C64XX: Use module identification for Craggamore system builds
Date: Sat, 20 Aug 2011 09:41:35 +0900	[thread overview]
Message-ID: <007401cc5ed1$ea70ab50$bf5201f0$%kim@samsung.com> (raw)
In-Reply-To: <20110819220210.GB3772@opensource.wolfsonmicro.com>

Mark Brown wrote:
> 
> On Fri, Aug 19, 2011 at 10:52:26PM +0900, Kukjin Kim wrote:
> > Mark Brown wrote:
> 
Hi Mark,

> Please delete unneeded context from mails, it makes it much easier to
> find the reply.
> 
Yes, I did. As you know, 'git am' can handle it.

> > > -#include <sound/wm8996.h>
> 
> > Hmm...Why is this <sound/wm8915.h> in my tree?
> 
This was my question when I found conflict during applying...

> This was waiting for cross tree issues to settle down in the merge
> window before being applied - it's in -rc2 which appeared last week or
> you can pull the individual change from:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound-2.6.git
wm8996-rename

Yes, so I applied this in my tree after rebasing -rc2 :)

You can find this in my for-next and next-samsung-devel.
If any problems, please let me know.

Have a nice day.
Thanks.

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

  reply	other threads:[~2011-08-20  0:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-16 12:42 [PATCH v2] ARM: S3C64XX: Use module identification for Craggamore system builds Mark Brown
2011-08-19 13:52 ` Kukjin Kim
2011-08-19 22:02   ` Mark Brown
2011-08-20  0:41     ` Kukjin Kim [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-08-14 10:54 [PATCH] " Mark Brown
2011-08-14 11:02 ` [PATCH v2] " Mark Brown

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='007401cc5ed1$ea70ab50$bf5201f0$%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 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.