public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation•org>
To: Alexandre Bounine <alexandre.bounine@idt•com>
Cc: linux-kernel@vger•kernel.org, Thomas Moll <thomas.moll@sysgo•com>,
	linuxppc-dev@lists•ozlabs.org
Subject: Re: [PATCH -mm 0/4] RapidIO: Misc updates
Date: Fri, 10 Dec 2010 15:19:24 -0800	[thread overview]
Message-ID: <20101210151924.333afed7.akpm@linux-foundation.org> (raw)
In-Reply-To: <1292013498-31406-1-git-send-email-alexandre.bounine@idt.com>

On Fri, 10 Dec 2010 15:38:14 -0500
Alexandre Bounine <alexandre.bounine@idt•com> wrote:

> The following four patches are follow-up to two RapidIO patches
> that are in the -mm tree now.
> 
> Alexandre Bounine (4):
>   RapidIO: Add definitions of Component Tag fields
>   RapidIO: Add device object linking into discovery
>   RapidIO: Use Component Tag for unified switch identification
>   RapidIO: Add new sysfs attributes
> 

I held
rapidio-use-common-destid-storage-for-endpoints-and-switches.patch and
rapidio-integrate-rio_switch-into-rio_dev.patch back from 2.6.37 due to
ongoing discussion.  What is the situation now?

  parent reply	other threads:[~2010-12-10 23:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-10 20:38 [PATCH -mm 0/4] RapidIO: Misc updates Alexandre Bounine
2010-12-10 20:38 ` [PATCH -mm 1/4] RapidIO: Add definitions of Component Tag fields Alexandre Bounine
2010-12-10 20:38 ` [PATCH -mm 2/4] RapidIO: Add device object linking into discovery Alexandre Bounine
2010-12-10 20:38 ` [PATCH -mm 3/4] RapidIO: Use Component Tag for unified switch identification Alexandre Bounine
2010-12-10 20:38 ` [PATCH -mm 4/4] RapidIO: Add new sysfs attributes Alexandre Bounine
2010-12-10 23:22   ` Andrew Morton
2010-12-11 18:49     ` Bounine, Alexandre
2010-12-12 18:48   ` Greg KH
2010-12-13 13:55     ` Bounine, Alexandre
2010-12-10 23:19 ` Andrew Morton [this message]
2010-12-11 19:18   ` [PATCH -mm 0/4] RapidIO: Misc updates Bounine, Alexandre

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=20101210151924.333afed7.akpm@linux-foundation.org \
    --to=akpm@linux-foundation$(echo .)org \
    --cc=alexandre.bounine@idt$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linuxppc-dev@lists$(echo .)ozlabs.org \
    --cc=thomas.moll@sysgo$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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