From: Tony Lindgren <tony@atomide.com>
To: Felipe Balbi <balbi@ti.com>
Cc: Linux ARM Kernel Mailing List
<linux-arm-kernel@lists.infradead.org>,
Linux OMAP Mailing List <linux-omap@vger.kernel.org>
Subject: Re: [PATCH 0/7] OMAP compile warning fix
Date: Wed, 19 Jan 2011 17:25:46 -0800 [thread overview]
Message-ID: <20110120012545.GQ4957@atomide.com> (raw)
In-Reply-To: <1295238680-26738-1-git-send-email-balbi@ti.com>
* Felipe Balbi <balbi@ti.com> [110116 20:30]:
> Hi Tony,
>
> I gave it a shot at dropping a few compile warnings
> from omap1-only and omap2-only builds.
>
> Following are 7 patches which I came up with. All
> compile tested with omap1_defconfig and omap2_defconfig
> (the latter being a result of omap2plus_defconfig -
> omap3 and omap4 support and adding any other config option
> which was disabled)
>
> There are a few more warnings to clean up, though. I didn't
> tackle all of them.
Thanks, adding all but the last one into devel-cleanup
for the next merge window. Let's see what Paul says about
the last one.
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/7] OMAP compile warning fix
Date: Wed, 19 Jan 2011 17:25:46 -0800 [thread overview]
Message-ID: <20110120012545.GQ4957@atomide.com> (raw)
In-Reply-To: <1295238680-26738-1-git-send-email-balbi@ti.com>
* Felipe Balbi <balbi@ti.com> [110116 20:30]:
> Hi Tony,
>
> I gave it a shot at dropping a few compile warnings
> from omap1-only and omap2-only builds.
>
> Following are 7 patches which I came up with. All
> compile tested with omap1_defconfig and omap2_defconfig
> (the latter being a result of omap2plus_defconfig -
> omap3 and omap4 support and adding any other config option
> which was disabled)
>
> There are a few more warnings to clean up, though. I didn't
> tackle all of them.
Thanks, adding all but the last one into devel-cleanup
for the next merge window. Let's see what Paul says about
the last one.
Tony
next prev parent reply other threads:[~2011-01-20 1:25 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-17 4:31 [PATCH 0/7] OMAP compile warning fix Felipe Balbi
2011-01-17 4:31 ` Felipe Balbi
2011-01-17 4:31 ` [PATCH 1/7] arm: omap: i2c: fix compile warning Felipe Balbi
2011-01-17 4:31 ` Felipe Balbi
2011-01-17 4:31 ` [PATCH 2/7] arm: omap1: " Felipe Balbi
2011-01-17 4:31 ` Felipe Balbi
2011-01-17 4:31 ` [PATCH 3/7] arm: omap1: fix compile warnings Felipe Balbi
2011-01-17 4:31 ` Felipe Balbi
2011-01-17 4:31 ` [PATCH 4/7] arm: omap1: fix a bunch of section mismatches Felipe Balbi
2011-01-17 4:31 ` Felipe Balbi
2011-01-17 4:31 ` [PATCH 5/7] arm: omap2: mux: fix compile warning Felipe Balbi
2011-01-17 4:31 ` Felipe Balbi
2011-01-17 4:31 ` [PATCH 6/7] arm: omap2: irq: fix compile warning: Felipe Balbi
2011-01-17 4:31 ` Felipe Balbi
2011-01-17 4:31 ` [PATCH 7/7] arm: omap2: clksel: fix compile warning Felipe Balbi
2011-01-17 4:31 ` Felipe Balbi
2011-01-17 8:07 ` Varadarajan, Charulatha
2011-01-17 8:07 ` Varadarajan, Charulatha
2011-01-17 8:18 ` Felipe Balbi
2011-01-17 8:18 ` Felipe Balbi
2011-01-19 23:09 ` Tony Lindgren
2011-01-19 23:09 ` Tony Lindgren
2011-01-20 1:25 ` Tony Lindgren [this message]
2011-01-20 1:25 ` [PATCH 0/7] OMAP compile warning fix 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=20110120012545.GQ4957@atomide.com \
--to=tony@atomide.com \
--cc=balbi@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.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 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.