From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1761885AbYCDRpj (ORCPT ); Tue, 4 Mar 2008 12:45:39 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1757823AbYCDRpQ (ORCPT ); Tue, 4 Mar 2008 12:45:16 -0500 Received: from smtp-102-tuesday.nerim.net ([62.4.16.102]:51823 "EHLO kraid.nerim.net" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1754641AbYCDRpP (ORCPT ); Tue, 4 Mar 2008 12:45:15 -0500 Date: Tue, 4 Mar 2008 18:45:12 +0100 From: Jean Delvare To: Linux I2C , LKML Subject: Wanted: i2c subsystem co-maintainer Message-ID: <20080304184512.3f78d296@hyperion.delvare> X-Mailer: Sylpheed-Claws 2.5.5 (GTK+ 2.10.6; x86_64-suse-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi all, I have a hard time maintaining the i2c subsystem alone. New drivers and, more importantly, subsystem evolutions are submitted much faster than I can review and merge them. I am hearing complaints about this. It has been lasting for a while now and it doesn't seem like the situation is going to improve. Thus, I think it would be better if someone was co-maintaining the i2c subsystem with me. So, if anyone is interested in co-maintaining the i2c subsystem with me, please let me know. The ideal candidate would come from the embedded world, as I have absolutely no experience with this myself and most of the new drivers are for embedded devices, and should have contributed to the kernel in a significant way already. Thanks, -- Jean Delvare