Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755307Ab2FNKW5 (ORCPT ); Thu, 14 Jun 2012 06:22:57 -0400 Received: from na3sys009aog105.obsmtp.com ([74.125.149.75]:60402 "EHLO na3sys009aog105.obsmtp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750972Ab2FNKW4 (ORCPT ); Thu, 14 Jun 2012 06:22:56 -0400 From: Felipe Balbi To: ben-linux@fluff.org Cc: Tony Lindgren , w.sang@pengutronix.de, Linux OMAP Mailing List , linux-i2c@vger.kernel.org, Linux ARM Kernel Mailing List , Linux Kernel Mailing List , Felipe Balbi Subject: [PATCH 00/17] Big OMAP I2C Cleanup Date: Thu, 14 Jun 2012 13:20:33 +0300 Message-Id: <1339669250-9183-1-git-send-email-balbi@ti.com> X-Mailer: git-send-email 1.7.10.4 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1379 Lines: 39 Hi guys, I have dropped a few patches from the series and also tested every single patch on my pandaboard. I2C messages are still working fine with panda after each patch. There's still lots of work to be done on the i2c-omap.c driver but it's now easier to read, IMO. Felipe Balbi (17): i2c: omap: simplify num_bytes handling i2c: omap: decrease indentation level on data handling i2c: omap: add blank lines i2c: omap: simplify omap_i2c_ack_stat() i2c: omap: split out [XR]DR and [XR]RDY i2c: omap: improve 1p153 errata handling i2c: omap: re-factor receive/transmit data loop i2c: omap: switch over to do {} while loop i2c: omap: ack IRQ in parts i2c: omap: get rid of the "complete" label i2c: omap: switch to devm_* API i2c: omap: switch to platform_get_irq() i2c: omap: bus: add a receiver flag i2c: omap: simplify errata check i2c: omap: always return IRQ_HANDLED i2c: omap: simplify IRQ exit path i2c: omap: resize fifos before each message drivers/i2c/busses/i2c-omap.c | 388 +++++++++++++++++++++++------------------ 1 file changed, 222 insertions(+), 166 deletions(-) -- 1.7.10.4 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/