From: David Miller <davem@davemloft.net>
To: lk-netdev@lk-netdev.nosense.org
Cc: netdev@vger.kernel.org, acme@redhat.com
Subject: Re: [PATCH net-next-2.6] Have atalk_route_packet() return NET_RX_SUCCESS not NET_XMIT_SUCCESS
Date: Mon, 14 Sep 2009 17:06:51 -0700 (PDT) [thread overview]
Message-ID: <20090914.170651.56087750.davem@davemloft.net> (raw)
In-Reply-To: <20090913161843.2e2174ba@opy.nosense.org>
From: Mark Smith <lk-netdev@lk-netdev.nosense.org>
Date: Sun, 13 Sep 2009 16:18:43 +0930
> Have atalk_route_packet() return NET_RX_SUCCESS not NET_XMIT_SUCCESS
>
> atalk_route_packet() returns NET_RX_DROP if it's call to
> aarp_send_ddp() returns NET_XMIT_DROP. If aarp_send_ddp() returns
> anything else atalk_route_packet() should return NET_RX_SUCCESS, not
> NET_XMIT_SUCCESS.
>
> Signed-off-by: Mark Smith <markzzzsmith@yahoo.com.au>
Applied.
prev parent reply other threads:[~2009-09-15 0:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-13 6:48 [PATCH net-next-2.6] Have atalk_route_packet() return NET_RX_SUCCESS not NET_XMIT_SUCCESS Mark Smith
2009-09-15 0:06 ` David Miller [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=20090914.170651.56087750.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=acme@redhat.com \
--cc=lk-netdev@lk-netdev.nosense.org \
--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).