From: "David S. Miller" <davem@redhat.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Marcelo Tosatti <marcelo@conectiva.com.br>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] sch_ingress.c includes <asm/smp.h>
Date: 09 Jun 2003 04:50:14 -0700 [thread overview]
Message-ID: <1055159413.9884.4.camel@rth.ninka.net> (raw)
In-Reply-To: <200306091037.h59Abpox012149@callisto.of.borg>
On Mon, 2003-06-09 at 03:37, Geert Uytterhoeven wrote:
> sch_ingress.c includes <asm/smp.h>, causing build failures on UMP-only
> architectures
Geert you should know better than anyone else that
you should send NET fixes to the NET maintainers.
So why aren't you doing that?
--
David S. Miller <davem@redhat.com>
next prev parent reply other threads:[~2003-06-09 11:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-09 10:37 [PATCH] sch_ingress.c includes <asm/smp.h> Geert Uytterhoeven
2003-06-09 11:50 ` David S. Miller [this message]
2003-06-09 12:02 ` Geert Uytterhoeven
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=1055159413.9884.4.camel@rth.ninka.net \
--to=davem@redhat.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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).