All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: lguest@ozlabs.org
Cc: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>,
	sfr@canb.auug.org.au, linux-next@vger.kernel.org,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [Lguest] linux-next: Tree for November 12 - lguest build failure
Date: Wed, 12 Nov 2008 22:56:00 +1030	[thread overview]
Message-ID: <200811122256.01487.rusty@rustcorp.com.au> (raw)
In-Reply-To: <200811122110.56290.rusty@rustcorp.com.au>

On Wednesday 12 November 2008 21:10:55 Rusty Russell wrote:
> On Wednesday 12 November 2008 19:41:02 Kamalesh Babulal wrote:
> > Hi Rusty,
> >
> >  lguest build fails with next-20081112 kernel,
> >
> > drivers/lguest/lguest_device.c: In function ‘lg_find_vq’:
> > drivers/lguest/lguest_device.c:252: error: too many arguments to function
> > ‘vring_size’ make[2]: *** [drivers/lguest/lguest_device.o] Error 1
>
> Hey, what idiot put in a patch which broke lguest?  Oh wait...
>
> Thanks, applied!
> Rusty.

Actually, I just reworked all these patches, so this is no longer necessary.

Thanks again,
Rusty.

  reply	other threads:[~2008-11-12 12:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-12  7:28 linux-next: Tree for November 12 Stephen Rothwell
2008-11-12  7:56 ` mac80211.h (was: Re: linux-next: Tree for November 12) Geert Uytterhoeven
2008-11-12 15:05   ` [PATCH] mac80211: add explicit padding in struct ieee80211_tx_info John W. Linville
2008-11-12 17:08     ` Johannes Berg
2008-11-12  9:11 ` linux-next: Tree for November 12 - lguest build failure Kamalesh Babulal
2008-11-12 10:40   ` Rusty Russell
2008-11-12 12:26     ` Rusty Russell [this message]
2008-11-12 21:01 ` [PATCH linux-next] : Tree for November 12 (libcrc32c) Randy Dunlap
2008-11-13 14:09   ` Herbert Xu
2008-11-12 21:05 ` [PATCH linux-next 3rd time] 9p: restrict RDMA usage Randy Dunlap
2008-11-12 21:10 ` linux-next: Tree for November 12 (ipw2200 build error) Randy Dunlap

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=200811122256.01487.rusty@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=kamalesh@linux.vnet.ibm.com \
    --cc=lguest@ozlabs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --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 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.