From: David Miller <davem@davemloft.net>
To: michal.simek@xilinx.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 2/2] net: ethernet: xilinx: Do not use NO_IRQ in axienet
Date: Thu, 10 Jan 2013 14:38:08 -0800 (PST) [thread overview]
Message-ID: <20130110.143808.1759152434749002223.davem@davemloft.net> (raw)
In-Reply-To: <1357837123-18996-2-git-send-email-michal.simek@xilinx.com>
From: Michal Simek <michal.simek@xilinx.com>
Date: Thu, 10 Jan 2013 17:58:43 +0100
> This driver is used on Microblaze and will be used
> on Arm Zynq.
> Microblaze doesn't define NO_IRQ and no IRQ is 0.
> Arm still uses NO_IRQ as -1 and there is no option
> to connect IRQ to irq 0.
>
> That's why <= 0 is only one option how to find out
> undefined IRQ.
>
> Signed-off-by: Michal Simek <michal.simek@xilinx.com>
Applied.
next prev parent reply other threads:[~2013-01-10 22:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-10 16:58 [PATCH 1/2] net: ethernet: xilinx: Do not use axienet on PPC Michal Simek
2013-01-10 16:58 ` [PATCH 2/2] net: ethernet: xilinx: Do not use NO_IRQ in axienet Michal Simek
2013-01-10 22:38 ` David Miller [this message]
2013-01-10 22:38 ` [PATCH 1/2] net: ethernet: xilinx: Do not use axienet on PPC David Miller
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=20130110.143808.1759152434749002223.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=michal.simek@xilinx.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).