From: Artem Bityutskiy <dedekind1-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Michal Vanka <mv-Swe8ldf8qsBeoWH0uzbU5w@public.gmane.org>
Cc: nios2-dev-1eJk0qcHJCcaeqlQEoCUNoJY59XmG8rH@public.gmane.org,
lanconelli.claudio-DtroZxfa9uMAvxtiuMwx3w@public.gmane.org,
linux-mtd-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
devicetree-discuss
<devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org>
Subject: Re: [PATCH] Devicetree support for enc28j60 SPI Ethernet chip
Date: Thu, 18 Oct 2012 12:39:37 +0300 [thread overview]
Message-ID: <1350553177.5769.307.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <507B04AA.1050502-Swe8ldf8qsBeoWH0uzbU5w@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 466 bytes --]
On Sun, 2012-10-14 at 20:30 +0200, Michal Vanka wrote:
> Hi,
> the following patch adds generic openfirmware/devicetree support to
> enc28j60 driver.
>
> It also adds support for custom hardware based (FPGA) "interrupt line
> deasserter" for processors with level triggered interrupts
> (for example Altera Nios2).
Hi, please, re-send with
devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
in CC.
--
Best Regards,
Artem Bityutskiy
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 192 bytes --]
_______________________________________________
devicetree-discuss mailing list
devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
https://lists.ozlabs.org/listinfo/devicetree-discuss
next parent reply other threads:[~2012-10-18 9:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <507B04AA.1050502@vanka.net>
[not found] ` <507B04AA.1050502-Swe8ldf8qsBeoWH0uzbU5w@public.gmane.org>
2012-10-18 9:39 ` Artem Bityutskiy [this message]
2012-10-19 7:58 [PATCH] Devicetree support for enc28j60 SPI Ethernet chip Michal Vanka
-- strict thread matches above, loose matches on Subject: below --
2012-10-16 16:50 Michal Vanka
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=1350553177.5769.307.camel@sauron.fi.intel.com \
--to=dedekind1-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=lanconelli.claudio-DtroZxfa9uMAvxtiuMwx3w@public.gmane.org \
--cc=linux-mtd-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=mv-Swe8ldf8qsBeoWH0uzbU5w@public.gmane.org \
--cc=nios2-dev-1eJk0qcHJCcaeqlQEoCUNoJY59XmG8rH@public.gmane.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).