From: Paul Mackerras <paulus@samba.org>
To: mod+linuxppc-dev@MissionCriticalLinux.com
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: [PATCH] Link-time failures from "simple" CFLAGS changes
Date: Wed, 9 Jan 2002 10:03:31 +1100 (EST) [thread overview]
Message-ID: <15419.31427.603521.763333@argo.ozlabs.ibm.com> (raw)
In-Reply-To: <200201072328.SAA07991@missioncriticallinux.com>
mod+linuxppc-dev@MissionCriticalLinux.com writes:
> >> Sheesh! Well, OK then: please apply this patch:
> >
> >Feel free to pass it onto Marcelo and/or Linus.
>
> I can wait - it'll eventually make it into the main
> branch when the linuxppc work gets merged, right?
Tom, Ben and I will send off stuff in arch/ppc, include/asm-ppc, and
some of the PPC-specific drivers to Marcelo or Linus. For other
stuff, like this documentation change, the people who want the change
need to send the patch to Marcelo, Linus, or the appropriate driver or
subsystem maintainer.
In particular, the top-level Makefile in linuxppc_2_4_devel has an
extra line in the TAGS target. I'm not going to send this in; someone
who wants this change to go in should take on the job of submitting it
to Marcelo (or Linus) and the linux-kernel mailing list. It may take
multiple attempts. :)
Paul.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2002-01-08 23:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-07 22:23 [PATCH] Link-time failures from "simple" CFLAGS changes mod+linuxppc-dev
2002-01-07 23:00 ` Tom Rini
2002-01-07 23:28 ` mod+linuxppc-dev
2002-01-08 0:21 ` Tom Rini
2002-01-08 23:03 ` Paul Mackerras [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=15419.31427.603521.763333@argo.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=mod+linuxppc-dev@MissionCriticalLinux.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;
as well as URLs for NNTP newsgroup(s).