From: David Miller <davem@davemloft.net>
To: bhutchings@solarflare.com
Cc: netdev@vger.kernel.org, linux-net-drivers@solarflare.com,
khali@linux-fr.org
Subject: Re: [PATCH -next] sfc: Don't specify unexistent IRQ
Date: Wed, 08 Apr 2009 16:00:02 -0700 (PDT) [thread overview]
Message-ID: <20090408.160002.119907202.davem@davemloft.net> (raw)
In-Reply-To: <20090408023819.GA14188@solarflare.com>
From: Ben Hutchings <bhutchings@solarflare.com>
Date: Wed, 8 Apr 2009 03:38:20 +0100
> Neither the lm90 driver nor the lm87 driver do support interrupts, so
> there is no point in specifying one when declaring the devices.
>
> Signed-off-by: Jean Delvare <khali@linux-fr.org>
> Signed-off-by: Ben Hutchings <bhutchings@solarflare.com>
Applied, thanks.
prev parent reply other threads:[~2009-04-08 23:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-08 2:38 [PATCH -next] sfc: Don't specify unexistent IRQ Ben Hutchings
2009-04-08 23:00 ` David Miller [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=20090408.160002.119907202.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bhutchings@solarflare.com \
--cc=khali@linux-fr.org \
--cc=linux-net-drivers@solarflare.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).