From: David Miller <davem@davemloft.net>
To: swhiteho@redhat.com
Cc: ccaulfie@redhat.com, netdev@vger.kernel.org
Subject: Re: decnet: Use data ready call back, rather than hand coding it
Date: Sat, 09 May 2009 13:18:30 -0700 (PDT) [thread overview]
Message-ID: <20090509.131830.01270908.davem@davemloft.net> (raw)
In-Reply-To: <1241800225.29604.282.camel@localhost.localdomain>
From: Steven Whitehouse <swhiteho@redhat.com>
Date: Fri, 08 May 2009 17:30:25 +0100
> Chrissie, can you test this? I don't have a suitable set up at the
> moment. This should be correct though since its taken directly from
> sock_queue_rcv_skb from whence the original code was also take in times
> past. I did compile test it though.
>
> Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>
I'm tossing this into net-next-2.6 now, if there is some bug
we can add a follow-on fix.
Thanks!
next prev parent reply other threads:[~2009-05-09 20:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-08 16:30 decnet: Use data ready call back, rather than hand coding it Steven Whitehouse
2009-05-09 20:18 ` David Miller [this message]
2009-05-11 8:33 ` Chrissie Caulfield
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=20090509.131830.01270908.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ccaulfie@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=swhiteho@redhat.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).