From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Francois Romieu <romieu@cogenit.fr>
Cc: linux-kernel@vger.kernel.org, torvalds@transmeta.com,
khc@pm.waw.pl, Alan Cox <alan@redhat.com>
Subject: Re: [PATCH] Re: [PATCH] Re: [PATCH] 2.4.3-pre6 - hdlc/dscc4 missing bits
Date: Wed, 21 Mar 2001 12:10:57 -0500 [thread overview]
Message-ID: <3AB8E0A1.43C61083@mandrakesoft.com> (raw)
In-Reply-To: <20010321163031.A28981@se1.cogenit.fr> <3AB8CDE0.2B2619AF@mandrakesoft.com> <20010321173930.A29474@se1.cogenit.fr>
Francois Romieu wrote:
>
> Jeff Garzik <jgarzik@mandrakesoft.com> écrit :
> > You should use this patch instead, from Alan's tree, for updating
> > include/linux/if_arp.h...
>
> It adds confusion: do you imagine the poor soul who discovers hdlc in Linux
> and sees ARPHRD_CISCO and ARPHRD_HDLC for the same use after some hours
> of code-greping (both will be used at the moment if hdlc.c do so) ?
> Don't be surprised if he ends using label pointers everywhere. :o)
>
> What about the following (2.5 ?):
That looks like 2.5 material to me. Personally I wouldn't want to
remove identifiers during 2.4 stable series.. Changing all 2.4 code to
use one identifier or the other seems reasonable.
Make sure to sync with Alan. WAN stuff has been occurring in his tree,
and we want to make sure everybody's on the same page..
--
Jeff Garzik | May you have warm words on a cold evening,
Building 1024 | a full mooon on a dark night,
MandrakeSoft | and a smooth road all the way to your door.
next prev parent reply other threads:[~2001-03-21 17:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-21 15:30 [PATCH] 2.4.3-pre6 - hdlc/dscc4 missing bits Francois Romieu
2001-03-21 15:50 ` [PATCH] " Jeff Garzik
2001-03-21 16:39 ` [PATCH] " Francois Romieu
2001-03-21 17:10 ` Jeff Garzik [this message]
2001-03-21 18:53 ` Krzysztof Halasa
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=3AB8E0A1.43C61083@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=alan@redhat.com \
--cc=khc@pm.waw.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=romieu@cogenit.fr \
--cc=torvalds@transmeta.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