From: Tony Lindgren <tony@atomide.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL] ARM: OMAP2+: resolve some sparse, cppcheck warnings
Date: Wed, 18 Apr 2012 10:20:01 -0700 [thread overview]
Message-ID: <20120418172000.GJ21106@atomide.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1204171729290.29048@utopia.booyaka.com>
* Paul Walmsley <paul@pwsan.com> [120417 16:33]:
> Hi Tony,
>
> The following changes since commit 0034102808e0dbbf3a2394b82b1bb40b5778de9e:
>
> Linux 3.4-rc2 (2012-04-07 18:30:41 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/pjw/omap-pending tags/omap-cleanup-a2-for-3.5
>
> for you to fetch changes up to eeb3711b89d68e147e05e7b43a49ecc5009dc157:
>
> ARM: OMAP2+: clean up some cppcheck warnings (2012-04-17 15:50:47 -0600)
>
> ----------------------------------------------------------------
> Resolve static analysis warnings generated by files in
> arch/arm/mach-omap1, arch/arm/mach-omap2, and arch/arm/plat-omap.
> Fixes all but one sparse warning and most of the useful
> cppcheck warnings (excepting the warnings generated by the
> dmtimer integration code which is going up via 3.4-rc fixes)
>
> ----------------------------------------------------------------
>
> This version drops the OMAP1 dmtimer integration patch ("ARM: OMAP1:
> DMTIMER: fix broken timer clock source selection") that will go
> upstream during 3.4-rc fixes. There are no other changes from the
> previous branch.
Thanks, pulled now into cleanup-sparse and merged into linux-omap
master for some testing.
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: OMAP2+: resolve some sparse, cppcheck warnings
Date: Wed, 18 Apr 2012 10:20:01 -0700 [thread overview]
Message-ID: <20120418172000.GJ21106@atomide.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1204171729290.29048@utopia.booyaka.com>
* Paul Walmsley <paul@pwsan.com> [120417 16:33]:
> Hi Tony,
>
> The following changes since commit 0034102808e0dbbf3a2394b82b1bb40b5778de9e:
>
> Linux 3.4-rc2 (2012-04-07 18:30:41 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/pjw/omap-pending tags/omap-cleanup-a2-for-3.5
>
> for you to fetch changes up to eeb3711b89d68e147e05e7b43a49ecc5009dc157:
>
> ARM: OMAP2+: clean up some cppcheck warnings (2012-04-17 15:50:47 -0600)
>
> ----------------------------------------------------------------
> Resolve static analysis warnings generated by files in
> arch/arm/mach-omap1, arch/arm/mach-omap2, and arch/arm/plat-omap.
> Fixes all but one sparse warning and most of the useful
> cppcheck warnings (excepting the warnings generated by the
> dmtimer integration code which is going up via 3.4-rc fixes)
>
> ----------------------------------------------------------------
>
> This version drops the OMAP1 dmtimer integration patch ("ARM: OMAP1:
> DMTIMER: fix broken timer clock source selection") that will go
> upstream during 3.4-rc fixes. There are no other changes from the
> previous branch.
Thanks, pulled now into cleanup-sparse and merged into linux-omap
master for some testing.
Tony
next prev parent reply other threads:[~2012-04-18 17:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-17 21:17 [GIT PULL] ARM: OMAP2+: resolve some sparse, cppcheck warnings Paul Walmsley
2012-04-17 21:17 ` Paul Walmsley
2012-04-17 23:29 ` Paul Walmsley
2012-04-18 17:20 ` Tony Lindgren [this message]
2012-04-18 17:20 ` 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=20120418172000.GJ21106@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
/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.