From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Matteo Fortini <m.fortini@selcomgroup.com>
Cc: linuxppc-dev@ozlabs.org, John Rigby <jrigby@freescale.com>
Subject: Re: [PATCH] ADS5121 Fix: put dummy byte to enable fixing EOF bug to first place in order not to break some drivers\nUse ALARM interrupt to avoid waiting for data to come in
Date: Thu, 11 Dec 2008 10:06:35 +1100 [thread overview]
Message-ID: <20081211100635.be00463c.sfr@canb.auug.org.au> (raw)
In-Reply-To: <49400F56.2040008@selcomgroup.com>
[-- Attachment #1: Type: text/plain, Size: 672 bytes --]
Hi Matteo,
On Wed, 10 Dec 2008 19:49:58 +0100 Matteo Fortini <m.fortini@selcomgroup.com> wrote:
>
> From d500e922b750a2bea554d32d8f12937f4da9c80a Mon Sep 17 00:00:00 2001
> From: Matteo Fortini <m.fortini@selcomgroup.com>
> Date: Wed, 10 Dec 2008 19:33:16 +0100
> Subject: [PATCH] Fix: put dummy byte to enable fixing EOF bug to first
> place in order not to break some drivers
> Use ALARM interrupt to avoid waiting for data to come in
Please don't make unrelated cleanups in patches - it makes it very hard
for the reviewers to do their work.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-12-10 23:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-10 18:49 [PATCH] ADS5121 Fix: put dummy byte to enable fixing EOF bug to first place in order not to break some drivers\nUse ALARM interrupt to avoid waiting for data to come in Matteo Fortini
2008-12-10 23:06 ` Stephen Rothwell [this message]
2008-12-11 14:35 ` Josh Boyer
2008-12-11 18:39 ` [RESEND] " Matteo Fortini
2008-12-11 18:46 ` Josh Boyer
2008-12-11 21:57 ` Matteo Fortini
2008-12-11 22:06 ` Josh Boyer
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=20081211100635.be00463c.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=jrigby@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=m.fortini@selcomgroup.com \
/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).