linux-kernel - Re: [PATCH] serial: omap: repair building without PM

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <871u8jm3ku.fsf@linaro.org>
Date:	Mon, 03 Jun 2013 11:50:09 -0700
From:	Kevin Hilman <khilman@...aro.org>
To:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:	Arnd Bergmann <arnd@...db.de>, linux-kernel@...r.kernel.org,
	linux-omap@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
	Sourav Poddar <sourav.poddar@...com>,
	Felipe Balbi <balbi@...com>
Subject: Re: [PATCH] serial: omap: repair building without PM_SLEEP

Greg Kroah-Hartman <gregkh@...uxfoundation.org> writes:

> On Sat, Jun 01, 2013 at 11:18:13AM +0200, Arnd Bergmann wrote:
>> A recent bug fix in 3.10, ddd85e225c "serial: omap: prevent runtime PM for
>> "no_console_suspend"", introduced a regression from an obvious typo:
>
> I don't see that commit id, or commit, in Linus's tree at all.  Where do
> you see it?

It's in linux-next (from your tty-next branch.)

>> drivers/tty/serial/omap-serial.c:1677:14: error: 'serial_omap_complete' 
>> 	undeclared here (not in a function)
>> 
>> This changes the incorrectly added macro to the one that we need instead.
>> 
>> Signed-off-by: Arnd Bergmann <arnd@...db.de>

Acked-by: Kevin Hilman <khilman@...aro.org>

>> ---
>> Please apply for 3.10-rc
>
> Really?  It doesn't apply to 3.10-rc3 or -rc4 from what I can tell.

Right, this is -next material, not v3.10.

Kevin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/