From: Jean Delvare <jdelvare@suse.de>
To: Alexandre Bounine <alexandre.bounine@idt.com>
Cc: Stef van Os <stef.van.os@Prodrive.nl>,
Micha Nelissen <micha.nelissen@Prodrive.nl>,
linux-kernel@vger.kernel.org,
Andre van Herk <andre.van.herk@Prodrive.nl>,
Andrew Morton <akpm@linux-foundation.org>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 0/7] rapidio: modularize rapidio subsystem
Date: Thu, 25 Jul 2013 18:03:43 +0200 [thread overview]
Message-ID: <1374768223.4604.207.camel@chaos.site> (raw)
In-Reply-To: <1372447136-5751-1-git-send-email-alexandre.bounine@idt.com>
Hi Alexandre,
Le Friday 28 June 2013 à 15:18 -0400, Alexandre Bounine a écrit :
> The following set of patches modifies kernel RapidIO subsystem to enable build
> and use of its components as loadable kernel modules. Combinations of statically
> linked and modular components are also supported.
> (...)
Thanks to this patch set, I was finally able to make all RapidIO support
modular in openSUSE kernels. This is very appreciated, thanks a lot!
--
Jean Delvare
Suse L3
prev parent reply other threads:[~2013-07-25 16:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-28 19:18 [PATCH 0/7] rapidio: modularize rapidio subsystem Alexandre Bounine
2013-06-28 19:18 ` [PATCH 1/7] rapidio: convert switch drivers to modules Alexandre Bounine
2013-06-28 19:18 ` [PATCH 2/7] rapidio/rionet: rework driver initialization and removal Alexandre Bounine
2013-06-28 19:18 ` [PATCH 3/7] rapidio: update enumerator registration mechanism Alexandre Bounine
2013-06-28 19:18 ` [PATCH 4/7] rapidio/tsi721: convert to modular mport driver Alexandre Bounine
2013-06-28 19:18 ` [PATCH 5/7] rapidio: add modular build option for the subsystem core Alexandre Bounine
2013-07-26 11:00 ` Jean Delvare
2013-07-26 12:17 ` Bounine, Alexandre
2013-06-28 19:18 ` [PATCH 6/7] rapidio: add udev notification Alexandre Bounine
2013-06-28 19:18 ` [PATCH 7/7] rapidio: documentation update Alexandre Bounine
2013-07-25 16:03 ` Jean Delvare [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=1374768223.4604.207.camel@chaos.site \
--to=jdelvare@suse.de \
--cc=akpm@linux-foundation.org \
--cc=alexandre.bounine@idt.com \
--cc=andre.van.herk@Prodrive.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=micha.nelissen@Prodrive.nl \
--cc=stef.van.os@Prodrive.nl \
/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).