From: Stephen Rothwell <sfr@canb.auug.org.au>
To: David Miller <davem@davemloft.net>
Cc: linux-next@vger.kernel.org, alex.williamson@hp.com,
rusty@rustcorp.com.au, linux-kernel@vger.kernel.org
Subject: Re: linux-next: upstream tree build warnings
Date: Thu, 23 Apr 2009 22:51:08 +1000 [thread overview]
Message-ID: <20090423225108.600a6e8e.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20090423215533.157df0e0.sfr@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 635 bytes --]
Hi Dave,
On Thu, 23 Apr 2009 21:55:33 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> The callers came in throught commit
> 0bde95690d65653e420d04856c5d5783155c747c ("virtio_net: Add support for
> VLAN filtering in the hypervisor") which I assume came in throught the
> net tree (it has you SOB on it). Committed Feb 5, 2009, went into Linus'
> tree before 2.6.30-rc1.
>
> scatterlist.h hasn't changed since July, 2008.
In other words, I think the bug has always been there and just never hit
(yet).
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-04-23 12:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090423163847.200f227e.sfr@canb.auug.org.au>
2009-04-23 7:24 ` linux-next: upstream tree build warnings David Miller
2009-04-23 11:55 ` Stephen Rothwell
2009-04-23 12:51 ` Stephen Rothwell [this message]
2009-04-23 16:46 ` Alex Williamson
2009-04-26 12:23 ` Rusty Russell
2009-04-27 6:32 ` David Miller
2009-04-24 14:37 ` [PATCH] virtio_net: memset scatterlist before using Alex Williamson
2009-04-26 12:58 ` Rusty Russell
2009-04-27 6:30 ` David Miller
2009-04-27 15:50 ` [PATCH] virtio_net: Cleanup command queue scatterlist usage Alex Williamson
2009-04-28 9:30 ` David Miller
2009-05-01 22:33 ` David Miller
2009-05-01 22:43 ` Alex Williamson
2009-05-01 22:52 ` David Miller
2009-05-02 3:27 ` Alex Williamson
2009-05-02 4:26 ` David Miller
2009-05-05 3:21 ` 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=20090423225108.600a6e8e.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=alex.williamson@hp.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rusty@rustcorp.com.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).