From: Wolfram Sang <w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
To: Guennadi Liakhovetski <g.liakhovetski-Mmb7MZpHnFY@public.gmane.org>
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-sh-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Magnus Damm <magnus.damm-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Simon Horman <horms-/R6kz+dDXgpPR4JQBCEnsQ@public.gmane.org>
Subject: Re: [PATCH 0/4] i2c: sh_mobile: fix STOP condition generation
Date: Sun, 10 Feb 2013 15:53:46 +0100 [thread overview]
Message-ID: <20130210145346.GA6282@nekote.pengutronix.de> (raw)
In-Reply-To: <Pine.LNX.4.64.1302050942140.1275-0199iw4Nj15frtckUFj5Ag@public.gmane.org>
> Thanks, yes, we could try usleep_range(), but these delays could be a bit
> sensitive, so, such a change would require a new round of testing. Maybe
> we could commit these patches in this form and then I could try
> usleep_range() as a separate patch to also make any regression tracking
> easier?
Sure. So, series applied to for-next, thanks!
prev parent reply other threads:[~2013-02-10 14:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-17 9:45 [PATCH 0/4] i2c: sh_mobile: fix STOP condition generation Guennadi Liakhovetski
[not found] ` <1358415957-8371-1-git-send-email-g.liakhovetski-Mmb7MZpHnFY@public.gmane.org>
2013-01-17 9:45 ` [PATCH 1/4] i2c: i2c-sh_mobile.c: cosmetic: trivially simplify 2 functions Guennadi Liakhovetski
2013-01-17 9:45 ` [PATCH 2/4] i2c: sh_mobile: fix timeout error handling Guennadi Liakhovetski
2013-01-17 9:45 ` [PATCH 3/4] i2c: sh_mobile: eliminate an open-coded "goto" loop Guennadi Liakhovetski
2013-01-17 9:45 ` [PATCH 4/4] i2c: sh_mobile: don't send a stop condition by default inside transfers Guennadi Liakhovetski
2013-01-24 7:27 ` [PATCH 0/4] i2c: sh_mobile: fix STOP condition generation Wolfram Sang
[not found] ` <20130124072748.GK8364-8EAEigeeuNG034pCzgS/Qg7AFbiQbgqx@public.gmane.org>
2013-02-05 8:45 ` Guennadi Liakhovetski
[not found] ` <Pine.LNX.4.64.1302050942140.1275-0199iw4Nj15frtckUFj5Ag@public.gmane.org>
2013-02-10 14:53 ` Wolfram Sang [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=20130210145346.GA6282@nekote.pengutronix.de \
--to=w.sang-bicnvbalz9megne8c9+irq@public.gmane.org \
--cc=g.liakhovetski-Mmb7MZpHnFY@public.gmane.org \
--cc=horms-/R6kz+dDXgpPR4JQBCEnsQ@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-sh-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=magnus.damm-Re5JQEeQqe8AvxtiuMwx3w@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).