From: Andrew Morton <akpm@linux-foundation.org>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: mm snapshot broken-out-2007-06-20-10-12.tar.gz uploaded
Date: Thu, 21 Jun 2007 16:01:35 -0700 [thread overview]
Message-ID: <20070621160135.f5bcd428.akpm@linux-foundation.org> (raw)
In-Reply-To: <4679F17E.4060305@goop.org>
> On Wed, 20 Jun 2007 20:33:18 -0700 Jeremy Fitzhardinge <jeremy@goop.org> wrote:
> akpm@linux-foundation.org wrote:
> > git-r8169-fixup.patch
> >
> This causes a compile failure:
>
> /home/jeremy/hg/xen/paravirt/linux/drivers/net/r8169.c: In function 'rtl8169_rx_interrupt':
> /home/jeremy/hg/xen/paravirt/linux/drivers/net/r8169.c:2569: error: too many arguments to function 'rtl8169_try_rx_copy'
>
> with an allyesconfig on x86-64. Should git-r8169-fixup.patch also be
> changing the callers?
>
git-r8169-fixup is a fix for git-r8169, which I'd in fact dropped, so
it should't be there at all.
Sorry, that was just a heading-for-the-airport-quick-dump-my-queue
thing. I have some serious catching up to do.
prev parent reply other threads:[~2007-06-21 23:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-20 17:14 mm snapshot broken-out-2007-06-20-10-12.tar.gz uploaded akpm
2007-06-20 18:45 ` [PATCH] fs/quota.c build fix (Re: mm snapshot broken-out-2007-06-20-10-12.tar.gz uploaded) Michal Piotrowski
2007-06-21 14:17 ` Vasily Tarasov
2007-06-21 0:51 ` mm snapshot broken-out-2007-06-20-10-12.tar.gz uploaded Bob Picco
2007-06-21 1:07 ` Randy Dunlap
2007-06-21 1:14 ` Bob Picco
2007-06-21 4:54 ` Randy Dunlap
2007-06-26 4:12 ` Andrew Morton
2007-06-21 0:52 ` Bob Picco
2007-06-21 2:55 ` Jeremy Fitzhardinge
2007-06-21 3:33 ` Jeremy Fitzhardinge
2007-06-21 23:01 ` Andrew Morton [this message]
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=20070621160135.f5bcd428.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
/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.