linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, Kay Sievers <kay.sievers@vrfy.org>,
	Rusty Russell <rusty@rustcorp.com.au>,
	Mark McLoughlin <markmc@redhat.com>
Subject: Re: linux-next: manual merge of the rr tree
Date: Sun, 4 Jan 2009 20:36:23 -0800	[thread overview]
Message-ID: <20090105043623.GA16341@kroah.com> (raw)
In-Reply-To: <20090105103036.dacccbed.sfr@canb.auug.org.au>

On Mon, Jan 05, 2009 at 10:30:36AM +1100, Stephen Rothwell wrote:
> Hi Greg,
> 
> On Mon, 22 Dec 2008 17:32:13 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > Today's linux-next merge of the rr tree got a conflict in
> > drivers/virtio/virtio_pci.c between commit
> > b5146336e3bc3786712919e94106063036dae86b ("virtio: do not statically
> > allocate root device") from the driver-core tree and commits
> > f53dba3a1ea82dfb37f094a942ae74032413809f ("virtio: struct device -
> > replace bus_id with dev_name(), dev_set_name()") and
> > ab4e479d47ceac2fa5bebd5b99d27f01fe0e0c8b ("virtio: add PCI device release
> > () function") from the rr tree.
> > 
> > I fixed it up (see below) and can carry the fix as necessary.  Mark, does
> > this driver-core patch obsolete the second rr tree patch above?
> > -- 
> > Cheers,
> > Stephen Rothwell                    sfr@canb.auug.org.au
> > http://www.canb.auug.org.au/~sfr/
> > 
> > diff --cc drivers/virtio/virtio_pci.c
> > index f772cc4,265fdf2..0000000
> > --- a/drivers/virtio/virtio_pci.c
> > +++ b/drivers/virtio/virtio_pci.c
> > @@@ -324,7 -343,8 +340,8 @@@ static int __devinit virtio_pci_probe(s
> >   	if (vp_dev == NULL)
> >   		return -ENOMEM;
> >   
> >  -	vp_dev->vdev.dev.parent = &virtio_pci_root;
> >  +	vp_dev->vdev.dev.parent = virtio_pci_root;
> > + 	vp_dev->vdev.dev.release = virtio_pci_release_dev;
> >   	vp_dev->vdev.config = &virtio_pci_config_ops;
> >   	vp_dev->pci_dev = pci_dev;
> >   	INIT_LIST_HEAD(&vp_dev->virtqueues);
> 
> This conflict is now between Linus' tree and the driver-core tree.

Thanks for letting me know, I'll fix it up tomorrow when I get back to
the patch queues :)

greg k-h

  reply	other threads:[~2009-01-05  4:37 UTC|newest]

Thread overview: 94+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-22  6:32 linux-next: manual merge of the rr tree Stephen Rothwell
2008-12-22  7:58 ` Rusty Russell
2008-12-22  8:45   ` Mark McLoughlin
2009-01-04 23:30 ` Stephen Rothwell
2009-01-05  4:36   ` Greg KH [this message]
2009-01-05  5:56     ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2009-01-09  1:53 Stephen Rothwell
2009-01-06  3:11 Stephen Rothwell
2009-01-05  3:32 Stephen Rothwell
2009-01-05  6:57 ` Rusty Russell
2009-01-05 12:47   ` Ingo Molnar
2009-01-06  8:51     ` Rusty Russell
2009-01-06  9:20       ` Ingo Molnar
2009-01-06 13:13       ` Mike Travis
2009-01-06 13:19         ` Ingo Molnar
2009-01-06 14:21           ` Mike Travis
2009-01-06 14:59             ` Ingo Molnar
2009-01-07  2:46             ` Rusty Russell
2009-01-05 15:29   ` Christoph Lameter
2009-01-06  1:04     ` Rusty Russell
2009-01-06 15:05       ` Christoph Lameter
2009-01-07  2:47         ` Rusty Russell
2009-01-07 16:11           ` Christoph Lameter
2009-01-07 17:20             ` Andi Kleen
2009-01-07 19:01               ` Christoph Lameter
2009-01-08 20:48                 ` Andi Kleen
2009-01-08 20:50                   ` Andrew Morton
2009-01-08 21:15                   ` Christoph Lameter
2009-01-08 21:49                     ` Andi Kleen
2009-01-08 22:21                       ` Christoph Lameter
2009-01-08 22:25                         ` David Miller
2009-01-09 14:42                           ` Christoph Lameter
2009-01-09 22:54                             ` David Miller
2009-01-05 19:46   ` Mike Travis
2009-01-05  8:41 ` Rusty Russell
2009-01-06  3:46   ` Stephen Rothwell
2009-01-06 13:26     ` Ingo Molnar
2008-12-29  7:51 Stephen Rothwell
2008-12-29  7:47 Stephen Rothwell
2008-12-29  8:02 ` Stephen Rothwell
2008-12-16  5:29 Stephen Rothwell
2008-12-15  6:15 Stephen Rothwell
2008-11-24  3:20 Stephen Rothwell
2008-11-20  3:24 Stephen Rothwell
2008-11-20  4:28 ` Rusty Russell
2008-11-14  4:13 Stephen Rothwell
2008-11-14  4:20 ` Stephen Rothwell
2008-11-14  4:30   ` David Miller
2008-11-14  4:36     ` Stephen Rothwell
2008-11-14  4:41       ` David Miller
2008-11-14  5:06         ` Stephen Rothwell
2008-11-14  6:42           ` David Miller
2008-11-15 22:32             ` Rusty Russell
2008-11-17  2:57               ` David Miller
2008-11-07  5:01 Stephen Rothwell
2008-10-29  4:28 Stephen Rothwell
2008-10-29  4:33 ` Stephen Rothwell
2008-10-29 22:42 ` Rusty Russell
2008-10-28  2:55 Stephen Rothwell
2008-10-28  7:19 ` Heiko Carstens
2008-10-28  7:24   ` Stephen Rothwell
2008-10-27  3:32 Stephen Rothwell
2008-10-24  2:21 Stephen Rothwell
2008-10-23  4:12 Stephen Rothwell
2008-10-23  5:16 ` Rusty Russell
2008-10-23 12:26   ` Rusty Russell
2008-10-23 12:50   ` Mike Travis
2008-10-23  4:01 Stephen Rothwell
2008-10-23  7:17 ` Peter Zijlstra
2008-10-23 13:32 ` Rusty Russell
2008-10-23  3:56 Stephen Rothwell
2008-10-23 12:25 ` Rusty Russell
2008-09-12 21:53 Stephen Rothwell
2008-07-28  3:16 Stephen Rothwell
2008-07-28  3:13 Stephen Rothwell
2008-07-28  3:09 Stephen Rothwell
2008-07-22  4:58 Stephen Rothwell
2008-07-22 14:21 ` Mike Travis
2008-07-16  8:15 Stephen Rothwell
2008-07-17  5:46 ` Max Krasnyansky
2008-07-18  4:31   ` Rusty Russell
2008-07-14  6:52 Stephen Rothwell
2008-07-03  5:03 Stephen Rothwell
2008-07-03  5:56 ` Ingo Molnar
2008-07-03  8:07   ` Stephen Rothwell
2008-07-03  8:19     ` Ingo Molnar
2008-07-04  0:45       ` Rusty Russell
2008-07-04  0:29   ` Rusty Russell
2008-06-25  6:27 Stephen Rothwell
2008-06-25  6:38 ` Christian Borntraeger
2008-06-25 15:23   ` Stephen Rothwell
2008-06-25  6:27 Stephen Rothwell
2008-06-25  7:47 ` Ingo Molnar
2008-06-25  8:33   ` Rusty Russell

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=20090105043623.GA16341@kroah.com \
    --to=greg@kroah.com \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-next@vger.kernel.org \
    --cc=markmc@redhat.com \
    --cc=rusty@rustcorp.com.au \
    --cc=sfr@canb.auug.org.au \
    /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).