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: <alpine.DEB.2.02.1406171530420.517@chino.kir.corp.google.com>
Date:	Tue, 17 Jun 2014 15:37:00 -0700 (PDT)
From:	David Rientjes <rientjes@...gle.com>
To:	werner <w.landgraf@...ru>
cc:	linux-kernel@...r.kernel.org
Subject: Re: 3.16-rc1 problems vdso_addr , _mb_cache_entry_ , rtl8723au

On Tue, 17 Jun 2014, werner wrote:

> Different to 3.15 , now for 3.16-rc1 the compiling list have warnings of any
> incompatibility for all subroutines
> 
> and it don't build, because problems in vdso_addr  and _mb_cache_entry_    The
> last is a problem occuring already in 3.15
> 
> also subroutine  rtl8723au  don't compile
> 

It's probably not a good idea to just post a collection of build errors in 
one email that isn't cc'd to anyone in particular and expect the issues to 
be addressed.

 - The staging errors should be reported directly to the people 
   responsible for those drivers, check git-blame for who to email: not
   everything in staging is guaranteed to compile at any time, it's very
   fluid.

 - The __builtin_log2() problem should be fixed with "fs/mbcache.c: 
   replacing __builtin_log2() with ilog2()" that was written specifically
   due to your previous error report, see 
   http://marc.info/?t=140147146600003

 - I can't reproduce your align_vdso_addr() problem, please send your 
   .config
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ