From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Cc: maxk@qualcomm.com, bluez-devel@lists.sourceforge.net,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [Bluez-devel] [PATCH] bluetooth: Eliminate checks for impossible conditions in irq handler
Date: Sat, 20 Oct 2007 15:52:15 +0200 [thread overview]
Message-ID: <1192888335.6184.115.camel@violet> (raw)
In-Reply-To: <20071019073132.GA5678@havoc.gtf.org>
Hi Jeff,
> [BLUETOOTH] Eliminate checks for impossible conditions in irq handler
>
> Our info structure and info->hdev is always passed to the irq handler,
> so we don't have to worry about these checks in every interrupt.
>
> Leave a BUG_ON() just to help unwary programmers, but these could
> probably be removed as well.
applied to my tree. Thanks.
Regards
Marcel
prev parent reply other threads:[~2007-10-20 13:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-19 7:31 [PATCH] bluetooth: Eliminate checks for impossible conditions in irq handler Jeff Garzik
2007-10-20 13:52 ` Marcel Holtmann [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=1192888335.6184.115.camel@violet \
--to=marcel@holtmann.org \
--cc=akpm@linux-foundation.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=maxk@qualcomm.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