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

Date:	Fri, 8 Aug 2008 11:28:53 +0200
From:	Jean Delvare <khali@...ux-fr.org>
To:	mkrufky@...uxtv.org
Cc:	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!

Hi Michael,

On Thu, 7 Aug 2008 17:34:30 -0400 , mkrufky@...uxtv.org wrote:
> Jean Delvare wrote:
> > Why not, please? A vast majority of drivers work fine that way today. I
> > am still waiting for someone to give me a good reason why some other
> > drivers supposedly can't be merged upstream (something better than
> > "believe me, it's impossible".)
> 
> Nobody said that a driver "...can't be merged upstream" ...  but 
> REQUIRING a driver to be merged upstream to allow development and / or 
> testing is a problem, IMHO.
> 
> If you required that all of my development happens within a git 
> development repository, preventing me from working against distro-kernel 
> xyz, then I would simply spend more time on Windows driver development 
> and my Linux contributions would cease.

Not my goal, obviously.

> External subsystem development repositories allow us to work against 
> stable kernels at our own pace.  When driver X is ready to be merged, it 
> gets merged.
>
> 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?

Some distributions do package linux-next. And this seems to be a very
easy way to get end users to test bleeding edge code. You just tell the
user to install the linux-next package and he/she's done. No need to
build anything.

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