linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Alexander Stein <alexander.stein@informatik.tu-chemnitz.de>
Cc: linux-input@vger.kernel.org
Subject: Re: [PATCH] rotary_encoder: Use proper irqflags
Date: Wed, 2 Feb 2011 22:05:54 -0800	[thread overview]
Message-ID: <20110203060554.GB25739@core.coreip.homeip.net> (raw)
In-Reply-To: <1296682169-12653-1-git-send-email-alexander.stein@informatik.tu-chemnitz.de>

On Wed, Feb 02, 2011 at 10:29:29PM +0100, Alexander Stein wrote:
> IORESOURCE_IRQ_* is wrong for irq_request, use the correct IRQF_* instead.
> 
> Signed-off-by: Alexander Stein <alexander.stein@informatik.tu-chemnitz.de>

Applied, thank you Alexander.

-- 
Dmitry

      reply	other threads:[~2011-02-03  6:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-02 21:29 [PATCH] rotary_encoder: Use proper irqflags Alexander Stein
2011-02-03  6:05 ` Dmitry Torokhov [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=20110203060554.GB25739@core.coreip.homeip.net \
    --to=dmitry.torokhov@gmail.com \
    --cc=alexander.stein@informatik.tu-chemnitz.de \
    --cc=linux-input@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).