From: Greg KH <greg@kroah•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
Kukjin Kim <kgene.kim@samsung•com>,
Russell King <rmk@arm•linux.org.uk>,
Kay Sievers <kay.sievers@vrfy•org>
Subject: Re: linux-next: manual merge of the driver-core tree with the arm tree
Date: Wed, 4 Jan 2012 15:09:13 -0800 [thread overview]
Message-ID: <20120104230913.GJ24583@kroah.com> (raw)
In-Reply-To: <20111228162431.206d16c1671679526958bf7e@canb.auug.org.au>
On Wed, Dec 28, 2011 at 04:24:31PM +1100, Stephen Rothwell wrote:
> Hi again,
>
> On Wed, 28 Dec 2011 16:12:31 +1100 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
> >
> > Today's linux-next merge of the driver-core tree got a conflict in
> > arch/arm/mach-s3c64xx/common.c between commit b024043b6d0d ("ARM: 7245/1:
> > S3C64XX: introduce arch/arm/mach-s3c64xx/common.[ch]") from the arm tree
> > and commit edbaa603eb80 ("driver-core: remove sysdev.h usage") from the
> > driver-core tree (where it is called arch/arm/mach-s3c64xx/irq-eint.c).
> >
> > Just context changes. I fixed it up (see below) and can carry the fix as
> > necessary.
>
> Actually, I the fix was more extensive (see below).
Ick, messy, thanks, that looks good.
greg k-h
next prev parent reply other threads:[~2012-01-04 23:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-28 5:12 linux-next: manual merge of the driver-core tree with the arm tree Stephen Rothwell
2011-12-28 5:24 ` Stephen Rothwell
2012-01-04 23:09 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-12-28 5:35 Stephen Rothwell
2012-01-04 23:08 ` Greg KH
2011-12-28 5:40 Stephen Rothwell
2012-01-04 23:08 ` Greg KH
2012-01-06 6:52 Stephen Rothwell
2012-01-06 7:08 ` Kukjin Kim
2012-01-06 19:20 ` 'Greg KH'
2012-01-06 6:57 Stephen Rothwell
2012-01-06 7:13 ` 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=20120104230913.GJ24583@kroah.com \
--to=greg@kroah$(echo .)com \
--cc=kay.sievers@vrfy$(echo .)org \
--cc=kgene.kim@samsung$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=rmk@arm$(echo .)linux.org.uk \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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