public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Pierre Ossman <drzeus-list@drzeus•cx>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Greg KH <greg@kroah•com>,
	linux-next@vger•kernel.org, Kay Sievers <kay.sievers@vrfy•org>,
	Anton Vorontsov <avorontsov@ru•mvista.com>
Subject: Re: linux-next: mmc/driver-core merge conflict
Date: Mon, 9 Jun 2008 09:14:52 +0200	[thread overview]
Message-ID: <20080609091452.5240892b@mjolnir.drzeus.cx> (raw)
In-Reply-To: <20080606155655.b72cff0d.sfr@canb.auug.org.au>

On Fri, 6 Jun 2008 15:56:55 +1000
Stephen Rothwell <sfr@canb•auug.org.au> wrote:

> Hi Pierre, Greg,
> 
> Today's linux-next merge of the mmc tree got a conflict in
> drivers/mmc/host/mmc_spi.c between commit
> b16fa5e051064488f241647a080271f1cd41d077 ("driver-core: prepare for
> removal of 20 char limit from struct device") from the driver-core tree
> and commit cd3c93fe826def37abc474e7a91bbf56444d7cd0 ("mmc_spi: add
> support for card-detection polling") from the mmc tree.
> 
> I fixed it up in the obvious manner.  Could be fixed by moving the
> drivers/mmc/host/mmc_spi.c part of the driver-core change to the mmc
> tree ...
> 

Sounds good to me. Greg, can you separate out that portion?

-- 
     -- Pierre Ossman

  Linux kernel, MMC maintainer        http://www.kernel.org
  rdesktop, core developer          http://www.rdesktop.org

  reply	other threads:[~2008-06-09  7:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-06  5:56 linux-next: mmc/driver-core merge conflict Stephen Rothwell
2008-06-09  7:14 ` Pierre Ossman [this message]
2008-06-17  3:15   ` Greg KH

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=20080609091452.5240892b@mjolnir.drzeus.cx \
    --to=drzeus-list@drzeus$(echo .)cx \
    --cc=avorontsov@ru$(echo .)mvista.com \
    --cc=greg@kroah$(echo .)com \
    --cc=kay.sievers@vrfy$(echo .)org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --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