From: "David S. Miller" <davem@redhat.com>
To: Jeroen Vreeken <pe1rxq@amsat.org>
Cc: linux-hams@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: [PATCH] (resend) fix sock_raw behaviour
Date: Thu, 9 Oct 2003 23:53:38 -0700 [thread overview]
Message-ID: <20031009235338.7335b635.davem@redhat.com> (raw)
In-Reply-To: <20031008235150.A207@jeroen.pe1rxq.ampr.org>
On Wed, 8 Oct 2003 23:51:50 +0200
Jeroen Vreeken <pe1rxq@amsat.org> wrote:
> This is a resend of a patch from some weeks ago that doesn't appear to have
> made it in yet...
It doesn't apply, that's why. You patch ax25.h twice the same
exact way which causes the patch to not apply.
While we're talking about this, who is going to maintain AX25
in 2.6.x? I don't want to be taking bug fixes and other changes
to AX25 from random people, I'd like to have a single contact
that will review the AX25 patches from other people and then
forward them off to me.
next prev parent reply other threads:[~2003-10-10 6:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-08 21:51 [PATCH] (resend) fix sock_raw behaviour Jeroen Vreeken
2003-10-10 6:53 ` David S. Miller [this message]
2003-10-10 11:21 ` Jeroen Vreeken
2003-10-10 11:16 ` David S. 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=20031009235338.7335b635.davem@redhat.com \
--to=davem@redhat.com \
--cc=linux-hams@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=pe1rxq@amsat.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).