netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: roel.kluin@gmail.com
Cc: netdev@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [PATCH] WARNING: some request_irq() failures ignored in el2_open()
Date: Wed, 02 Sep 2009 23:10:49 -0700 (PDT)	[thread overview]
Message-ID: <20090902.231049.224678267.davem@davemloft.net> (raw)
In-Reply-To: <4A9D4AD5.1010404@gmail.com>

From: Roel Kluin <roel.kluin@gmail.com>
Date: Tue, 01 Sep 2009 18:24:53 +0200

> Request_irq() may fail in different ways, handle accordingly.
> 
> Signed-off-by: Roel Kluin <roel.kluin@gmail.com>
> ---
> Don't we have to do something like this? 

Looks good, applied to net-next-2.6, thanks!

      reply	other threads:[~2009-09-03  6:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-01 16:24 [PATCH] WARNING: some request_irq() failures ignored in el2_open() Roel Kluin
2009-09-03  6:10 ` 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=20090902.231049.224678267.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=akpm@linux-foundation.org \
    --cc=netdev@vger.kernel.org \
    --cc=roel.kluin@gmail.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).