From: Wolfram Sang <w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
To: Ben Dooks <ben-i2c-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org>
Cc: Ben Dooks <ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org>,
khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org,
Marc Kleine-Budde <mkl-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
Subject: Re: Please pull bjdooks' i2c-fixes
Date: Thu, 7 Oct 2010 08:43:52 +0200 [thread overview]
Message-ID: <20101007064352.GA12741@pengutronix.de> (raw)
In-Reply-To: <20101006221430.GW21564-SMNkleLxa3Z6Wcw2j4pizdi2O/JbrIOy@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 766 bytes --]
> > Is there a specific reason this patch was not picked up/commented (again)?
> >
> > http://thread.gmane.org/gmane.linux.drivers.i2c/6222/focus=6265
> >
> > It prevents getting a stalled bus, and we have done similar things for MPC and
> > other platforms.
>
> It got tagged onto the end of the previous thread, which was ages ago.
>
> In future, it would be helpful to send each major revision of a patch
> as a new thread, maybe with a reference to the previous one.
Okay, noted. Will do that next time.
> I'll try and add it before the next pull window, or in it.
Thanks a lot!
--
Pengutronix e.K. | Wolfram Sang |
Industrial Linux Solutions | http://www.pengutronix.de/ |
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2010-10-07 6:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-30 23:04 Please pull bjdooks' i2c-fixes Ben Dooks
2010-10-01 8:09 ` Wolfram Sang
[not found] ` <20101001080951.GA27870-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2010-10-06 22:14 ` Ben Dooks
[not found] ` <20101006221430.GW21564-SMNkleLxa3Z6Wcw2j4pizdi2O/JbrIOy@public.gmane.org>
2010-10-07 6:43 ` Wolfram Sang [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-10-18 0:31 Ben Dooks
2010-09-22 1:11 Ben Dooks
2010-01-24 15:33 Ben Dooks
2009-12-24 1:59 Ben Dooks
2009-08-20 21:32 Ben Dooks
2009-07-30 0:06 Ben Dooks
2009-07-14 23:06 Ben Dooks
2009-05-11 23:42 Ben Dooks
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=20101007064352.GA12741@pengutronix.de \
--to=w.sang-bicnvbalz9megne8c9+irq@public.gmane.org \
--cc=ben-i2c-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org \
--cc=ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org \
--cc=khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mkl-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org \
--cc=torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.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;
as well as URLs for NNTP newsgroup(s).