linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, Mike Travis <travis@sgi.com>
Subject: Re: linux-next: rr tree build failure
Date: Thu, 27 Nov 2008 18:41:08 +1030	[thread overview]
Message-ID: <200811271841.08825.rusty@rustcorp.com.au> (raw)
In-Reply-To: <200811251336.26864.borntraeger@de.ibm.com>

On Tuesday 25 November 2008 23:06:26 Christian Borntraeger wrote:
> Am Dienstag, 25. November 2008 schrieb Rusty Russell:
> > > Also, the x86_64 allmodconfig build failed like this:
> > >
> > > ERROR: "hvc_resize" [drivers/char/virtio_console.ko] undefined!
> > >
> > > hvc_resize is currently not exported to modules.
> > >
> > > I have dropped the rr tree again.
> >
> > OK, I've dropped Christian's patch for the moment until he fixes this. 
> > I'm travelling to Sydney for the day so I won't get a chance to fix this
> > if it breaks tomorrow :(
>
> Ok. Sorry about that. allmodconfig on s390 and i386 select VIRTIO_CONSOLE
> as (y) and not as (m), therefore my tests did not trigger this problem. I
> will try to get an x86_64 box to test on in the future.

Thanks, applied.

For future reference I've taken to preferring fixup patches, which I can fold 
later.

Cheers,
Rusty.

  reply	other threads:[~2008-11-27  8:11 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-25  6:45 linux-next: rr tree build failure Stephen Rothwell
2008-11-25 11:47 ` Rusty Russell
2008-11-25 12:36   ` Christian Borntraeger
2008-11-27  8:11     ` Rusty Russell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-12-11  1:26 Stephen Rothwell
2009-12-14  4:35 ` Stephen Rothwell
2009-12-15  3:52   ` Rusty Russell
2009-12-15  4:36     ` Stephen Rothwell
2009-12-17 22:05     ` Stephen Rothwell
2009-11-12  8:03 Stephen Rothwell
2009-11-12  9:02 ` Benjamin Herrenschmidt
2009-11-12 10:50   ` Stephen Rothwell
2009-11-12  7:48 Stephen Rothwell
2009-11-11  3:01 Stephen Rothwell
2009-11-11  8:33 ` Rusty Russell
2009-09-09  3:47 Stephen Rothwell
2009-09-09 14:32 ` Siarhei Liakh
2009-09-11  3:00 ` Siarhei Liakh
2009-09-15  3:27 ` Stephen Rothwell
2009-09-22  5:15   ` Rusty Russell
2009-08-03  3:32 Stephen Rothwell
2009-08-03 17:55 ` Bjorn Helgaas
2009-08-03 20:22 ` Bjorn Helgaas
2009-08-03 23:18   ` Rusty Russell
2009-08-10  3:55     ` Stephen Rothwell
2009-08-10  3:56       ` Stephen Rothwell
2009-06-23  6:14 Stephen Rothwell
2009-06-24  3:24 ` Rusty Russell
2009-06-24  6:31   ` Stephen Rothwell
2009-06-15  6:40 Stephen Rothwell
2009-06-15  7:26 ` Stephen Rothwell
2009-06-15  8:52   ` David Miller
2009-06-15 10:39 ` Rusty Russell
2009-06-11  9:07 Stephen Rothwell
2009-06-11 13:08 ` Rusty Russell
2009-06-09 10:12 Stephen Rothwell
2009-06-10  7:26 ` Rusty Russell
2009-06-10  8:11   ` Stephen Rothwell
2009-03-17  2:45 Stephen Rothwell
2009-03-05  8:33 Stephen Rothwell
2009-03-06  5:23 ` Rusty Russell
2009-01-07  3:04 Stephen Rothwell
2009-01-06  3:41 Stephen Rothwell
2008-12-29  8:12 Stephen Rothwell
2008-12-29 15:23 ` Mike Travis
2008-12-29 21:01 ` Rusty Russell
2008-11-24  3:31 Stephen Rothwell
2008-11-24 17:07 ` Rusty Russell
2008-11-21  3:19 Stephen Rothwell
2008-11-21 10:58 ` Rusty Russell
2008-11-21 18:34   ` Greg KH
2008-11-20  3:50 Stephen Rothwell
2008-10-23  4:52 Stephen Rothwell
2008-10-23 13:31 ` Rusty Russell
2008-10-23  4:51 Stephen Rothwell
2008-10-23 13:02 ` Rusty Russell
2008-06-26  6:50 Stephen Rothwell
2008-06-26  7:49 ` Christian Borntraeger
2008-06-27  3:15   ` Rusty Russell
2008-06-25  6:58 Stephen Rothwell
2008-06-25  7:35 ` Christian Borntraeger
2008-06-25  8:30   ` Rusty Russell
2008-06-25  9:08     ` Christian Borntraeger
2008-06-25  6:44 Stephen Rothwell

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=200811271841.08825.rusty@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=borntraeger@de.ibm.com \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=travis@sgi.com \
    /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).