From: khali@linux-fr.org (Jean Delvare)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3] ARM: OMAP: I2C: fix compilation when !CONFIG_OF
Date: Sun, 22 Jan 2012 21:07:40 +0100 [thread overview]
Message-ID: <20120122210740.735d8ca5@endymion.delvare> (raw)
In-Reply-To: <alpine.DEB.2.00.1201221250510.26641@utopia.booyaka.com>
On Sun, 22 Jan 2012 12:54:21 -0700 (MST), Paul Walmsley wrote:
> cc Ben, Jean
I'm not involved in this at all.
Jean
>
> On Sun, 22 Jan 2012, Cousson, Benoit wrote:
>
> > http://lists.ozlabs.org/pipermail/devicetree-discuss/2011-December/010541.html
> >
> > But it looks like it was stuck in linux-omap dt branch and not pulled for 3.3.
> > Maybe Tony can try to sent it during -rc phase.
> >
> > That being said, this will be valid for OMAP2+ only and will still break OMAP1
> > platform :-(
> >
> > Tony reported that 2 days ago, and I sent the fix for it.
> > http://www.mail-archive.com/linux-omap at vger.kernel.org/msg61520.html
>
> Will drop patch 3 from my series. Incidentally, it doesn't seem necessary
> to wait for Ben's ack after commit
> 046d0a37024a5b1e66ec9314e5e7feba42feb811 ("ARM: OMAP: I2C: fix compilation
> when !CONFIG_OF"), unless Ben disagrees with that change.
>
>
> - Paul
prev parent reply other threads:[~2012-01-22 20:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-22 11:02 [PATCH 0/3] ARM: OMAP: fix compilation problems with v3.3-rc1 Paul Walmsley
2012-01-22 11:02 ` [PATCH 1/3] ARM: OMAP: PRM: fix missing plat/irqs.h build breakage Paul Walmsley
2012-01-22 11:02 ` [PATCH 2/3] ARM: OMAP2+: io: fix compilation breakage on 2420-only configs Paul Walmsley
2012-01-22 11:02 ` [PATCH 3/3] ARM: OMAP: I2C: fix compilation when !CONFIG_OF Paul Walmsley
2012-01-22 15:40 ` Rob Herring
2012-01-22 15:46 ` Grant Likely
2012-01-22 15:45 ` Grant Likely
2012-01-22 16:06 ` Rob Herring
2012-01-22 16:59 ` Cousson, Benoit
2012-01-22 19:54 ` Paul Walmsley
2012-01-22 20:07 ` Jean Delvare [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=20120122210740.735d8ca5@endymion.delvare \
--to=khali@linux-fr.org \
--cc=linux-arm-kernel@lists.infradead.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).