From: Kevin Hilman <khilman@linaro.org>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>
Subject: Re: [PATCH] ARM: OMAP1: Fix a bunch of GPIO related section warnings after initdata got corrected
Date: Fri, 18 Oct 2013 10:54:59 -0700 [thread overview]
Message-ID: <87vc0uv4zw.fsf@linaro.org> (raw)
In-Reply-To: <20131018161017.GO15154@atomide.com> (Tony Lindgren's message of "Fri, 18 Oct 2013 09:10:18 -0700")
Tony Lindgren <tony@atomide.com> writes:
> * Tony Lindgren <tony@atomide.com> [131018 09:04]:
>> From: Tony Lindgren <tony@atomide.com>
>> Date: Fri, 18 Oct 2013 08:54:16 -0700
>> Subject: [PATCH] ARM: OMAP1: Fix a bunch of GPIO related section warnings after initdata got corrected
>
> Oops, sorry duplicate header. Below is a clean version that
> should apply with git am --scissors.
>
>> Arnd, Kevin, Olof, want to apply this directly on top of the fixes
>> I sent earlier?
Yup, I've applied this version to fixes-non-critical on top of your
other series.
Thanks for the quick fix, and nice to see at least someone besides me
and Olof are looking at the automated build/boot output. :)
Kevin
WARNING: multiple messages have this Message-ID (diff)
From: khilman@linaro.org (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: OMAP1: Fix a bunch of GPIO related section warnings after initdata got corrected
Date: Fri, 18 Oct 2013 10:54:59 -0700 [thread overview]
Message-ID: <87vc0uv4zw.fsf@linaro.org> (raw)
In-Reply-To: <20131018161017.GO15154@atomide.com> (Tony Lindgren's message of "Fri, 18 Oct 2013 09:10:18 -0700")
Tony Lindgren <tony@atomide.com> writes:
> * Tony Lindgren <tony@atomide.com> [131018 09:04]:
>> From: Tony Lindgren <tony@atomide.com>
>> Date: Fri, 18 Oct 2013 08:54:16 -0700
>> Subject: [PATCH] ARM: OMAP1: Fix a bunch of GPIO related section warnings after initdata got corrected
>
> Oops, sorry duplicate header. Below is a clean version that
> should apply with git am --scissors.
>
>> Arnd, Kevin, Olof, want to apply this directly on top of the fixes
>> I sent earlier?
Yup, I've applied this version to fixes-non-critical on top of your
other series.
Thanks for the quick fix, and nice to see at least someone besides me
and Olof are looking at the automated build/boot output. :)
Kevin
next prev parent reply other threads:[~2013-10-18 17:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-18 16:03 [PATCH] ARM: OMAP1: Fix a bunch of GPIO related section warnings after initdata got corrected Tony Lindgren
2013-10-18 16:03 ` Tony Lindgren
2013-10-18 16:10 ` Tony Lindgren
2013-10-18 16:10 ` Tony Lindgren
2013-10-18 17:54 ` Kevin Hilman [this message]
2013-10-18 17:54 ` Kevin Hilman
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=87vc0uv4zw.fsf@linaro.org \
--to=khilman@linaro.org \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=olof@lixom.net \
--cc=tony@atomide.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.