From: Tony Lindgren <tony@atomide.com>
To: i2c-linux@vger.kernel.org, ben-linux@fluff.org
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH 00/12] Updates for i2c-omap for 2.6.29 merge window, v4
Date: Fri, 28 Nov 2008 17:31:26 -0800 [thread overview]
Message-ID: <20081129013124.GJ6640@atomide.com> (raw)
In-Reply-To: <20081129012612.13042.12283.stgit@localhost>
* Tony Lindgren <tony@atomide.com> [081128 17:28]:
> Hi all,
>
> Here are the i2c-omap patches again for next merge window.
Oops, please ignore this series, the i2c list address is wrong. Will
resend.
> Regards,
>
> Tony
>
> ---
>
> Chandra shekhar (1):
> i2c-omap: Add support for omap34xx
>
> Jarkko Nikula (1):
> i2c-omap: Do not use interruptible wait call in omap_i2c_xfer_msg
>
> Kalle Jokiniemi (1):
> i2c-omap: Enable I2C wakeups for 34xx
>
> Nishanth Menon (1):
> i2c-omap: FIFO handling support and broken hw workaround for i2c-omap
>
> Paul Walmsley (6):
> i2c-omap: reprogram OCP_SYSCONFIG register after reset
> i2c-omap: convert 'rev1' flag to generic 'rev' u8
> i2c-omap: fix I2C timeouts due to recursive omap_i2c_{un,}idle()
> i2c-omap: Don't compile in OMAP15xx I2C ISR for non-OMAP15xx builds
> i2c-omap: Mark init-only functions as __init
> i2c-omap: Close suspected race between omap_i2c_idle() and omap_i2c_isr()
>
> Syed Mohammed Khasim (1):
> i2c-omap: Add high-speed support to omap-i2c
>
> Tony Lindgren (1):
> i2c-omap: Clean-up i2c-omap
>
>
> arch/arm/mach-omap2/clock24xx.h | 4
> drivers/i2c/busses/i2c-omap.c | 420 ++++++++++++++++++++++++++++++---------
> 2 files changed, 330 insertions(+), 94 deletions(-)
>
> --
> Signature
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2008-11-29 1:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-29 1:28 [PATCH 00/12] Updates for i2c-omap for 2.6.29 merge window, v4 Tony Lindgren
2008-11-29 1:28 ` [PATCH 01/12] i2c-omap: Do not use interruptible wait call in omap_i2c_xfer_msg Tony Lindgren
2008-11-29 1:28 ` [PATCH 02/12] i2c-omap: Close suspected race between omap_i2c_idle() and omap_i2c_isr() Tony Lindgren
2008-11-29 1:28 ` [PATCH 03/12] i2c-omap: Add high-speed support to omap-i2c Tony Lindgren
2008-11-29 1:28 ` [PATCH 04/12] i2c-omap: FIFO handling support and broken hw workaround for i2c-omap Tony Lindgren
2008-11-29 1:28 ` [PATCH 05/12] i2c-omap: Add support for omap34xx Tony Lindgren
2008-11-29 1:28 ` [PATCH 06/12] i2c-omap: Mark init-only functions as __init Tony Lindgren
2008-11-29 1:28 ` [PATCH 07/12] i2c-omap: Don't compile in OMAP15xx I2C ISR for non-OMAP15xx builds Tony Lindgren
2008-11-29 1:29 ` [PATCH 08/12] i2c-omap: Clean-up i2c-omap Tony Lindgren
2008-11-29 1:29 ` [PATCH 09/12] i2c-omap: fix I2C timeouts due to recursive omap_i2c_{un, }idle() Tony Lindgren
2008-11-29 1:29 ` [PATCH 10/12] i2c-omap: convert 'rev1' flag to generic 'rev' u8 Tony Lindgren
2008-11-29 1:29 ` [PATCH 11/12] i2c-omap: reprogram OCP_SYSCONFIG register after reset Tony Lindgren
2008-11-29 1:29 ` [PATCH 12/12] i2c-omap: Enable I2C wakeups for 34xx Tony Lindgren
2008-11-29 1:31 ` Tony Lindgren [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20081129013124.GJ6640@atomide.com \
--to=tony@atomide.com \
--cc=ben-linux@fluff.org \
--cc=i2c-linux@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox