From: Arnd Bergmann <arnd@arndb.de>
To: linuxppc-dev@ozlabs.org
Cc: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>,
linux-arch@vger.kernel.org, Matthew Wilcox <matthew@wil.cx>,
Rusty Russell <rusty@rustcorp.com.au>,
linux-kernel <linux-kernel@vger.kernel.org>,
Al Viro <viro@zeniv.linux.org.uk>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [RFC 2/3] powerpc: export all symbols from the definition file
Date: Mon, 11 Aug 2008 17:27:07 +0200 [thread overview]
Message-ID: <200808111727.07720.arnd@arndb.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0808111653170.3030@vixen.sonytel.be>
On Monday 11 August 2008, Geert Uytterhoeven wrote:
> > drivers/macintosh/adb.c | 5 +++++
> > drivers/macintosh/via-cuda.c | 3 +++
>
> I think these 2 belong to patch 3?
I tried to come up with other ways of splitting up the patch,
but since these come from ppc_ksyms, it makes sense to keep
them with the rest.
Maybe I could split the exports for C functions from those
in assember files that depend on patch 1.
Arnd <><
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: linuxppc-dev@ozlabs.org
Cc: linux-arch@vger.kernel.org, Matthew Wilcox <matthew@wil.cx>,
Rusty Russell <rusty@rustcorp.com.au>,
linux-kernel <linux-kernel@vger.kernel.org>,
Al Viro <viro@zeniv.linux.org.uk>,
Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [RFC 2/3] powerpc: export all symbols from the definition file
Date: Mon, 11 Aug 2008 17:27:07 +0200 [thread overview]
Message-ID: <200808111727.07720.arnd@arndb.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0808111653170.3030@vixen.sonytel.be>
On Monday 11 August 2008, Geert Uytterhoeven wrote:
> > =A0drivers/macintosh/adb.c =A0 =A0 =A0 =A0 =A0 =A0 =A0| =A0 =A05 +++++
> > =A0drivers/macintosh/via-cuda.c =A0 =A0 =A0 =A0 | =A0 =A03 +++
>=20
> I think these 2 belong to patch 3?
I tried to come up with other ways of splitting up the patch,
but since these come from ppc_ksyms, it makes sense to keep
them with the rest.
Maybe I could split the exports for C functions from those
in assember files that depend on patch 1.
Arnd <><
next prev parent reply other threads:[~2008-08-11 15:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-11 14:06 RFC: killing ksyms.c Arnd Bergmann
2008-08-11 14:17 ` [RFC 2/3] powerpc: export all symbols from the definition file Arnd Bergmann
2008-08-11 14:17 ` Arnd Bergmann
2008-08-11 14:53 ` Geert Uytterhoeven
2008-08-11 14:53 ` Geert Uytterhoeven
2008-08-11 15:27 ` Arnd Bergmann [this message]
2008-08-11 15:27 ` Arnd Bergmann
2008-08-11 14:18 ` [RFC 1/3] add support for exporting symbols from .S files Arnd Bergmann
2008-08-11 14:18 ` Arnd Bergmann
2008-08-11 14:56 ` David Woodhouse
2008-08-11 14:56 ` David Woodhouse
2008-08-12 2:03 ` Rusty Russell
2008-08-12 2:03 ` Rusty Russell
2008-08-12 6:43 ` Stephen Rothwell
2008-08-12 6:43 ` Stephen Rothwell
2008-08-12 13:58 ` Arnd Bergmann
2008-08-12 13:58 ` Arnd Bergmann
2008-08-11 14:25 ` [RFC 3/3] powerpc: remove ppc_ksyms.c Arnd Bergmann
2008-08-11 14:25 ` Arnd Bergmann
2008-08-11 15:03 ` RFC: killing ksyms.c Adrian Bunk
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=200808111727.07720.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=Geert.Uytterhoeven@sonycom.com \
--cc=dwmw2@infradead.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=matthew@wil.cx \
--cc=rusty@rustcorp.com.au \
--cc=viro@zeniv.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.