From: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Santosh Shilimkar <santosh.shilimkar-l0cyMroinI0@public.gmane.org>
Cc: Olof Johansson <olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org>,
"linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] spi: davinci: Fix the build warning with CONFIG_ARM_LPAE=y
Date: Sun, 24 Nov 2013 13:31:03 +0000 [thread overview]
Message-ID: <20131124133103.GS14725@sirena.org.uk> (raw)
In-Reply-To: <52911B64.3020009-l0cyMroinI0@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 468 bytes --]
On Sat, Nov 23, 2013 at 04:17:24PM -0500, Santosh Shilimkar wrote:
> On Wednesday 13 November 2013 08:29 AM, Mark Brown wrote:
> > Looks lie it never got pushed and nobody looked at the warnings for over
> > a month. Oh well, sorry about that.
> Are you going to push this one ? The warning is still showing up at
> 3.13-rc1.
It's a warning fix only so no, I was going to leave it till the next
merge window. It'll appear in -next as soon as Linus releases -rc1.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2013-11-24 13:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1380567179-20174-1-git-send-email-santosh.shilimkar@ti.com>
[not found] ` <20131001104840.GL19304@sirena.org.uk>
[not found] ` <20131001104840.GL19304-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2013-11-13 6:38 ` [PATCH] spi: davinci: Fix the build warning with CONFIG_ARM_LPAE=y Olof Johansson
[not found] ` <CAOesGMhRoEvsQoSvoCSY=zm71zeZec3MG_FpHOy1zUkYronZcw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-11-13 13:29 ` Mark Brown
[not found] ` <20131113132952.GK878-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2013-11-13 21:34 ` Olof Johansson
2013-11-23 21:17 ` Santosh Shilimkar
[not found] ` <52911B64.3020009-l0cyMroinI0@public.gmane.org>
2013-11-24 13:31 ` Mark Brown [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=20131124133103.GS14725@sirena.org.uk \
--to=broonie-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org \
--cc=santosh.shilimkar-l0cyMroinI0@public.gmane.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).