linux-kernel - Where to put new sensor 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>] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 1 Mar 2009 13:41:34 +0100
From:	Daniel Mack <daniel@...aq.de>
To:	linux-kernel@...r.kernel.org
Cc:	Jean Delvare <khali@...ux-fr.org>
Subject: Where to put new sensor drivers?

Hi,

I wrote a driver for an I2C connected ambient light sensor and submitted
it to the linux-i2c list[1]. In the first place, I wasn't aware of
drivers/i2c/chips being deprecated and hencei, I subsequently moved it to
what seemed to match best in the current tree, drivers/hwmon. But as
Jean Delvare pointed out, this is not the place for it either because it
doesn't really monitor the hardware, which is true.

So I posted a proposal[2] patch series that adds drivers/sensors for
such cases (some of the drivers in the legacy folder drivers/i2c/chips
have the same problem than my new one has) but haven't got reply on it
yet, probably because linux-i2c is the wrong place to ask.

Maybe someone here has an oppinon about that?

Thanks,
Daniel

[1] http://article.gmane.org/gmane.linux.drivers.i2c/3148
[2] http://article.gmane.org/gmane.linux.drivers.i2c/3159

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