From: Kumar Gala <galak@kernel.crashing.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Linux Kernel Development <linux-kernel@vger.kernel.org>,
ppc-dev dev ML <linuxppc-dev@ozlabs.org>,
Simon Horman <horms@verge.net.au>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Paul Mackerras <paulus@samba.org>
Subject: Re: Kconfig warnings on latest GIT
Date: Wed, 23 May 2007 09:14:07 -0500 (CDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0705230913420.535@localhost.localdomain> (raw)
In-Reply-To: <1179928646.14317.6.camel@johannes.berg>
On Wed, 23 May 2007, Johannes Berg wrote:
> On Wed, 2007-05-23 at 07:37 -0500, Kumar Gala wrote:
>
> > Was my patch ok, if so I'll push it up through my git tree to paul?
>
> Yeah, looks fine to me, or will the ARCH=ppc folks then scream and want
> that added to the Kconfig there as well?
I can't imagine they will since pmac is only supported in ARCH=powerpc.
- k
next prev parent reply other threads:[~2007-05-23 14:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200705080004.14570.ismail@pardus.org.tr>
[not found] ` <20070508143127.38fafa3c.kim.phillips@freescale.com>
[not found] ` <4640D988.1040504@freescale.com>
[not found] ` <20070510051042.GA16812@verge.net.au>
[not found] ` <1178811570.3806.18.camel@johannes.berg>
[not found] ` <20070511012216.GB10715@verge.net.au>
[not found] ` <1178883937.8896.11.camel@johannes.berg>
[not found] ` <20070514013230.GJ3588@verge.net.au>
[not found] ` <1179147311.2647.47.camel@johannes.berg>
[not found] ` <Pine.LNX.4.64.0705140923470.24559@gate.crashing.org>
[not found] ` <1179159951.2647.49.camel@johannes.berg>
2007-05-23 12:37 ` Kconfig warnings on latest GIT Kumar Gala
2007-05-23 13:57 ` Johannes Berg
2007-05-23 14:14 ` Kumar Gala [this message]
2007-05-23 14:26 ` Johannes Berg
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=Pine.LNX.4.64.0705230913420.535@localhost.localdomain \
--to=galak@kernel.crashing.org \
--cc=geert@linux-m68k.org \
--cc=horms@verge.net.au \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).