From: Paul Mackerras <paulus@samba.org>
To: Jean Delvare <khali@linux-fr.org>
Cc: sfr@canb.auug.org.au, linux-kernel@vger.kernel.org,
linuxppc-dev@ozlabs.org, i2c@lm-sensors.org,
scottwood@freescale.com, David Miller <davem@davemloft.net>
Subject: Re: [PATCH] [POWERPC] i2c: fix build breakage introduced by OF helpers
Date: Sat, 19 Apr 2008 21:45:46 +1000 [thread overview]
Message-ID: <18441.56170.464016.686497@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <20080419110934.672648e6@hyperion.delvare>
Jean Delvare writes:
> Guys, you're doing things the wrong way around. Breaking things to fix
> them later is not OK, it's a pain for testers and also when bisecting
> the kernel. Everything should still work after merging the powerpc
> tree. Dave, if you need to loosen the dependency, you should do it
> yourself _after_ having changed whatever needs to be in the sparc32 and
> sparc64 trees so that loosening the dependency doesn't break anything.
> As far as I can see it's only a matter of changing one line in a
> Kconfig file, that's not exactly difficult to do it in the right order.
You're right. I'll put in a dependency on PPC_OF for now and Dave can
take it out once sparc32/64 have irq_of_parse_and_map etc.
Paul.
prev parent reply other threads:[~2008-04-19 11:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-18 14:23 [PATCH] [POWERPC] i2c: fix build breakage introduced by OF helpers Jochen Friedrich
2008-04-19 4:04 ` Paul Mackerras
2008-04-19 4:09 ` David Miller
2008-04-19 5:22 ` Paul Mackerras
2008-04-19 6:11 ` David Miller
2008-04-19 9:09 ` Jean Delvare
2008-04-19 9:12 ` David Miller
2008-04-19 11:45 ` 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=18441.56170.464016.686497@cargo.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=davem@davemloft.net \
--cc=i2c@lm-sensors.org \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=scottwood@freescale.com \
--cc=sfr@canb.auug.org.au \
/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).