From: Al Viro <viro@ftp.linux.org.uk>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: net-2.6.20 rebased
Date: Thu, 16 Nov 2006 12:04:23 +0000 [thread overview]
Message-ID: <20061116120423.GF29920@ftp.linux.org.uk> (raw)
In-Reply-To: <20061116.055840.78704296.davem@davemloft.net>
On Thu, Nov 16, 2006 at 05:58:40AM -0500, David Miller wrote:
>
> I just rebased net-2.6.20 at:
>
> master.kernel.org:/pub/scm/linux/kernel/git/davem/net-2.6.20.git
>
> Al Viro has been going crazy with endianness and checksum type
> sparse annotations, which brings the patch count up to 171.
> Not bad for how long the net-2.6.20 tree has been open :-)
FWIW, with these patches in we have net/ nearly endian-clean. Two
major exceptions are ieee80211 and sctp. I think I've got more or
less sane way to deal with the latter, it won't be fun (and yes,
that's the queue I'm currently getting into shape). A bunch of
genuine bugs in there, too, especially when it comes to sctp+ipv6...
next prev parent reply other threads:[~2006-11-16 12:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-16 10:58 net-2.6.20 rebased David Miller
2006-11-16 12:04 ` Al Viro [this message]
2006-11-16 20:41 ` David Miller
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=20061116120423.GF29920@ftp.linux.org.uk \
--to=viro@ftp.linux.org.uk \
--cc=davem@davemloft.net \
--cc=netdev@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 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).