linux-kernel - Re: [PATCH] include/asm-generic/io.h: add dummy fuctions to support 'COMPILE

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]

Date:	Wed, 03 Jul 2013 23:06:41 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Chen Gang F T <chen.gang.flying.transformer@...il.com>
Cc:	Chen Gang <gang.chen@...anux.com>,
	Greg KH <gregkh@...uxfoundation.org>,
	Arnd Bergmann <arnd@...db.de>,
	Geert Uytterhoeven <geert@...ux-m68k.org>,
	Richard Weinberger <richard@....at>,
	Jeff Dike <jdike@...toit.com>,
	David Sharp <dhsharp@...gle.com>,
	"sfr@...b.auug.org.au" <sfr@...b.auug.org.au>,
	Ingo Molnar <mingo@...nel.org>,
	uml-devel <user-mode-linux-devel@...ts.sourceforge.net>,
	uml-user <user-mode-linux-user@...ts.sourceforge.net>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Linux-Arch <linux-arch@...r.kernel.org>,
	Mark Brown <broonie@...nel.org>,
	David Miller <davem@...emloft.net>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Jiri Kosina <trivial@...nel.org>, Jiri Slaby <jslaby@...e.cz>
Subject: Re: [PATCH] include/asm-generic/io.h: add dummy fuctions to support
 'COMPILE_TEST' in 'asm-generic'.

On Thu, 2013-07-04 at 10:42 +0800, Chen Gang F T wrote:

> Hmm..., I think maybe also has another way: get rid of 'COMPILE_TEST'
> (regress the related patch, which is only existent in next-* tree).

I'm not working on linux-next at the moment. Hmm, I'm not even working
on mainline at the moment, the kernel I have is still 3.10-rc5.

> 
> Or could you provide your suggestions or completions about it ?
> 
> Thanks.
> 
> > I'm still confused by what you are trying to accomplish.
> 
> Currently, I am trying to compile all architectures with allmodconfig in
> next-* tree (which will have "COMPILE_TEST=y").
> 
> So I can find and solve the related issues (I am one of contributors).
> 

So, you want all archs to pass an allmodconfig?

Well, one thing is, if a module doesn't build for an arch, then why not
keep that module from building for that arch.

If module foo.ko doesn't build for arch bazinga, then just add in the
Kconfig for the module foo:

config FOO
  depends on !BAZINGA

Then that module wont build for the specific arch, and all are happy. If
someone someday wants to support module foo for arch bazinga, then they
can fix module foo for that arch.

-- Steve


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