linux-kernel - Re: [GIT PULL for v3.18-rc1] media updates

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <1415653538.21229.37.camel@x220>
Date:	Mon, 10 Nov 2014 22:05:38 +0100
From:	Paul Bolle <pebolle@...cali.nl>
To:	Mauro Carvalho Chehab <mchehab@....samsung.com>
Cc:	Valentin Rothberg <valentinrothberg@...il.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-media@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL for v3.18-rc1] media updates

On Mon, 2014-11-10 at 18:54 -0200, Mauro Carvalho Chehab wrote:
> Em Mon, 10 Nov 2014 21:45:56 +0100
> Paul Bolle <pebolle@...cali.nl> escreveu: 
> > This typo is still present in both next-20141110 and v3.18-rc4. And I've
> > first reported it nearly two months ago. I see two fixes:
> >     1) s/HAS_MMU/MMU/
> >     2) s/ || (COMPILE_TEST && HAS_MMU)//
> > 
> > Which would you prefer?
> 
> Hmm... Probably patchwork didn't get your patch.

There's no patch, not yet. I try to report stuff like this before
sending patches. The idea here being that the people familiar with the
code tend to fix things better and quicker.

> IMHO, the best would be:
> 
> 	depends on HAS_MMU

You really like the HAS_MMU symbol, don't you?

> 	depends on ARCH_OMAP2 || ARCH_OMAP3 || COMPILE_TEST

But I understand what you're suggesting here. Should I draft a, probably
untested, patch?


Paul Bolle

--
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/