From: Jonathan Nieder <jrnieder@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: acme@redhat.com, roel.kluin@gmail.com, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
Mason Loring Bliss <mason@blisses.org>,
Ben Hutchings <ben@decadent.org.uk>
Subject: Re: [PATCH] [NET]: da.s_net not copied but assigned to itself in aarp_rcv()
Date: Fri, 2 Mar 2012 13:34:16 -0600 [thread overview]
Message-ID: <20120302193416.GA22055@burratino> (raw)
In-Reply-To: <20100115.014943.39860500.davem@davemloft.net>
Hi Dave,
David Miller wrote:
>> Em Thu, Jan 14, 2010 at 09:32:11PM +0100, Roel Kluin escreveu:
>>> da.s_net was not copied but assigned to itself.
>>>
>>> Signed-off-by: Roel Kluin <roel.kluin@gmail.com>
[...]
> Applied, please always CC: on networking patches.
Thanks.
Without this patch (commit 2a04cd4c7 aka v2.6.33-rc6~29^2~33), Mason
(cc-ed) is not able to use appletalk[1]:
| With Linux 2.6.32 as supplied with Debian Squeeze, Netatalk is unable
| to thrive. Connections made to afpd will open, but attempting to transfer
| files will take a very long time and/or eventually time out.
|
| I've noted this with both Netatalk as supplied with Squeeze and with
| Netatalk 2.2.1 built from the Wheezy source package, which I evidently
| need for AFP 3 support.
|
| Installing Linux 3.2 from backports, with no other changes to the system,
| allows afpd to work correctly.
Ben sent a copy of this patch to try against 2.6.32.y and it worked.
Would it be possible to include this in the 2.6.32.y-longterm tree?
Sincerely,
Jonathan
[1] http://bugs.debian.org/660902
next prev parent reply other threads:[~2012-03-02 19:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-14 20:32 [PATCH] [NET]: da.s_net not copied but assigned to itself in aarp_rcv() Roel Kluin
2010-01-14 21:00 ` Arnaldo Carvalho de Melo
2010-01-15 9:49 ` David Miller
2012-03-02 19:34 ` Jonathan Nieder [this message]
2012-06-09 7:07 ` [2.6.32.y] Re: [PATCH] appletalk:: " Jonathan Nieder
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=20120302193416.GA22055@burratino \
--to=jrnieder@gmail.com \
--cc=acme@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=ben@decadent.org.uk \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mason@blisses.org \
--cc=netdev@vger.kernel.org \
--cc=roel.kluin@gmail.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 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.