From: jkrzyszt@tis.icnet.pl (Janusz Krzysztofik)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 3/5] First set of omap1 related changes
Date: Fri, 02 Mar 2012 18:20:38 +0100 [thread overview]
Message-ID: <35028515.2H84FQMe6Y@acer> (raw)
In-Reply-To: <20120301233101.GC18901@atomide.com>
On Thu, 1 Mar 2012 15:31:01 Tony Lindgren wrote:
>
> I've pushed ams-delta branch that's based on -rc5 merged
> with what Arnd pulled yesterday as -rc1 has i2c-omap.c
> a compile bug for omap1. I've applied these two patches
> there as the second one depends on what got pulled:
>
> ARM: OMAP1: ams-delta: clean up init data section assignments
> ARM: OMAP1: ams-delta: fix incorrect section tags
Thanks!
> Looks like your patch "ARM: OMAP1: ams-delta: set up regulator
> over modem reset GPIO pin" causes the following error with
> CONFIG_DEBUG_SECTION_MISMATCH=y:
>
> arch/arm/mach-omap1/board-ams-delta.c:273:36: error:
> modem_nreset_config causes a section type conflict
>
> So care to update and repost that (and possibly the following
> two patches) with your missing fixes?
OK, I will, in a couple of days.
Thanks,
Janusz
next prev parent reply other threads:[~2012-03-02 17:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0Mfo5g-1RocQt3wlY-00NttP@mx.kundenserver.de>
2012-02-29 21:06 ` [GIT PULL 3/5] First set of omap1 related changes Arnd Bergmann
2012-02-29 21:13 ` Tony Lindgren
2012-03-01 22:26 ` Janusz Krzysztofik
2012-03-01 23:31 ` Tony Lindgren
2012-03-02 17:20 ` Janusz Krzysztofik [this message]
2012-02-29 20:15 [GIT PULL 1/5] non-critical fixes for v3.4 merge window Tony Lindgren
2012-02-29 20:15 ` [GIT PULL 3/5] First set of omap1 related changes Tony Lindgren
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=35028515.2H84FQMe6Y@acer \
--to=jkrzyszt@tis.icnet.pl \
--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).