linux-kernel - Re: [PATCH 1/2] i2c: Add possibility for user-defined (i2c-)devices for bus-drivers.

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

Message-ID: <50A4D5BB.6010301@ahsoftware.de>
Date:	Thu, 15 Nov 2012 12:44:59 +0100
From:	Alexander Holler <holler@...oftware.de>
To:	Till Harbaum <till@...baum.org>
CC:	Jean Delvare <khali@...ux-fr.org>, linux-kernel@...r.kernel.org,
	linux-i2c@...r.kernel.org
Subject: Re: [PATCH 1/2] i2c: Add possibility for user-defined (i2c-)devices
 for bus-drivers.

Hello,

Am 15.11.2012 12:04, schrieb Till Harbaum:

> There's actually one thing you can do: You device doesn't seem to expose
> the i2c bus, anyway. What you have is an rtc connected via usb. So why not
> move all the i2c intelligence into the device? Do pure usb-rtc's exist?
> Could you perhaps even make your device compatible to one of these?
> Then a driver for this would imho have good chances to find their way into
> the kernel.

Sorry, but I'm satisfied with what I've done and I didn't do it just to 
get "something" into the kernel. I don't need my patches to become part 
of in the kernel, I can handle them by myself. And my free resources to 
submit patches just became exhausted (again). Maybe in some weeks or 
month ..., I don't know.

Regards,

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