From: "David S. Miller" <davem@redhat.com>
To: Kevin Curtis <kevin.curtis@farsite.co.uk>
Cc: khc@pm.waw.pl, torvalds@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [TRIVIAL] [PATCH] generic HDLC Cisco bugfix
Date: Sat, 11 Oct 2003 10:39:51 -0700 [thread overview]
Message-ID: <20031011103951.78b06186.davem@redhat.com> (raw)
In-Reply-To: <7C078C66B7752B438B88E11E5E20E72E25CA91@GENERAL.farsite.co.uk>
On Fri, 10 Oct 2003 16:56:00 +0100
Kevin Curtis <kevin.curtis@farsite.co.uk> wrote:
> Is this only for 2.6.x or does it also include 2.4.x and 2.2.x
> I ask this because I will need to submit a patch for the farsync WAN drivers
> soon which will need to be applied to all three kernels.
For 2.4.x too, yes. As for 2.2.x I want nothing to do with
that tree, and it's in "OOPS fixers only" mode these days.
next prev parent reply other threads:[~2003-10-11 17:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-10 15:56 [TRIVIAL] [PATCH] generic HDLC Cisco bugfix Kevin Curtis
2003-10-11 17:39 ` David S. Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-10-09 22:13 Krzysztof Halasa
2003-10-10 6:44 ` David S. Miller
2003-10-10 8:23 ` Jens Axboe
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=20031011103951.78b06186.davem@redhat.com \
--to=davem@redhat.com \
--cc=kevin.curtis@farsite.co.uk \
--cc=khc@pm.waw.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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