From: Johan Hedberg <johan.hedberg@gmail.com>
To: Colin Didier <didier@archos.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] An interrupted syscall is not an error when returning from poll() in audio/pcm_bluetooth.c
Date: Wed, 25 Aug 2010 14:28:31 +0300 [thread overview]
Message-ID: <20100825112831.GB23943@jh-x301> (raw)
In-Reply-To: <20100825085454.GB27072@cybione.org>
Hi Colin,
On Wed, Aug 25, 2010, Colin Didier wrote:
> An interrupted syscall is not an error when returning from poll() at
> line 240 of audio/pcm_bluetooth.c. So no need to freak out.
>
> Here is a patch to fix this.
The patch itself seems fine, but the same comments apply for the commit
message as with your other patch. I.e. prepare with git format-patch and
make sure that you don't have overly long lines (e.g. the summary line
is much too long in this one).
Johan
next prev parent reply other threads:[~2010-08-25 11:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-25 8:54 [PATCH] An interrupted syscall is not an error when returning from poll() in audio/pcm_bluetooth.c Colin Didier
2010-08-25 11:28 ` Johan Hedberg [this message]
2010-08-25 13:07 ` [PATCH] No error message on interrupted syscall Colin Didier
2010-08-25 13:29 ` Johan Hedberg
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=20100825112831.GB23943@jh-x301 \
--to=johan.hedberg@gmail.com \
--cc=didier@archos.com \
--cc=linux-bluetooth@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