public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Arnaldo Carvalho de Melo <acme@conectiva.com.br>
Cc: "David S. Miller" <davem@redhat.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] tr: make CONFIG_TR depend on CONFIG_LLC=y
Date: Mon, 18 Nov 2002 18:22:02 -0500	[thread overview]
Message-ID: <3DD9761A.8030501@pobox.com> (raw)
In-Reply-To: <20021116111344.GD24641@conectiva.com.br>

Arnaldo Carvalho de Melo wrote:

> Em Mon, Nov 18, 2002 at 06:11:50PM -0500, Jeff Garzik escreveu:
>
> >David S. Miller wrote:
> >
> >
> >>On Sat, 2002-11-16 at 03:13, Arnaldo Carvalho de Melo wrote:
> >>
> >>
> >>>	Please pull from:
> >>>
> >>>master.kernel.org:/home/acme/BK/net-2.5
> >>
> >>
> >>Pulled, thanks.
> >
> >hmmm, did you look at the requirements here?
> >
> >when I looked at this a couple weeks ago, it did not seem like the best
> >fix, just the easiest...
>
>
> Previously the 802.2 llc1 code was statically linked when TR was selected,
> problem is now the llc1 code is not separated from the llc2 one, which is
> way bigger, my plans are to:
>
> 1. make llc1 be available separately, so that we can have the previous
>    behaviour
> 2. to make TR be available as a module
>
> Suggestions on better ways to deal with this are welcome...



I could have sworn I fixed this specific problem a month or so ago with 
a Makefile edit and maybe a tiny code edit....  I'll see if I can dig up 
the patch.

	Jeff




      parent reply	other threads:[~2002-11-18 23:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-16 11:13 [PATCH] tr: make CONFIG_TR depend on CONFIG_LLC=y Arnaldo Carvalho de Melo
2002-11-18 23:05 ` David S. Miller
2002-11-18 23:11 ` Jeff Garzik
2002-11-18 23:19   ` Arnaldo Carvalho de Melo
2002-11-18 23:22 ` Jeff Garzik [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=3DD9761A.8030501@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=acme@conectiva.com.br \
    --cc=davem@redhat.com \
    --cc=linux-kernel@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