LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@kernel.crashing.org>
To: Georg Klug <gklug@giga-stream.de>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Possible problem in asm/bitops.h
Date: Tue, 17 Dec 2002 07:59:01 -0700	[thread overview]
Message-ID: <20021217145901.GH2513@opus.bloom.county> (raw)
In-Reply-To: <FFECLICFNBJAHONLGAKMAEFOCHAA.gklug@giga-stream.de>


On Tue, Dec 17, 2002 at 10:10:09AM +0100, Georg Klug wrote:

> > I suspect the actual problem is that iproute2 only needs
> > a very small amount of what is in include/linux/inetdev.h
>
> That might be true. But would the solution be to copy the linux/inetdev.h
> to a local directory and change that file until it doesn't need the file
> asm/bitops.h anymore?

Correct.

--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

      parent reply	other threads:[~2002-12-17 14:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-11 15:31 Possible problem in asm/bitops.h Georg Klug
2002-12-12 15:28 ` Tom Rini
2002-12-17  9:10   ` AW: " Georg Klug
2002-12-17 10:16     ` Paul Mackerras
2002-12-17 14:59     ` Tom Rini [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=20021217145901.GH2513@opus.bloom.county \
    --to=trini@kernel.crashing.org \
    --cc=gklug@giga-stream.de \
    --cc=linuxppc-embedded@lists.linuxppc.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