linux-kernel - Re: Problem with restricted I2C algorithms in kernel 2.6.26!

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:	Fri, 08 Aug 2008 02:17:52 +0200
From:	Stefan Richter <stefanr@...6.in-berlin.de>
To:	mkrufky@...uxtv.org
CC:	khali@...ux-fr.org, sam@...nborg.org, user.kernel@...il.com,
	linux-kernel@...r.kernel.org, i2c@...sensors.org
Subject: Re: Problem with restricted I2C algorithms in kernel 2.6.26!

mkrufky@...uxtv.org wrote:
> With the model that you propose, "use linux-next for development" ... 
> well then what about testing?  Who is going to test my driver if it 
> requires a full kernel compile?

We almost _never_ use linux-next in the way that we base our development 
on it.  We use it to prepare integration.


BTW, looking back at this thread in the list archive, I see some people 
thoroughly confusing
   - unmerged code,
   - external developer repositories/ external patchkits,
   - module source files outside a complete kernel source directory.
These are all independent matters.

All code starts as unmerged code.
All developers use external repositories.

However, module source files which are outside of the kernel source 
directory are not quite the norm.  (Because the kernel build system 
doesn't support this.)
-- 
Stefan Richter
-=====-==--- =--- -=---
http://arcgraph.de/sr/
--
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/