public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matt Porter <mporter@kernel.crashing.org>
To: Andrew Morton <akpm@osdl.org>
Cc: Matt Porter <mporter@kernel.crashing.org>,
	kumar.gala@freescale.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][MM] rapidio: message interface updates
Date: Thu, 15 Sep 2005 14:48:05 -0700	[thread overview]
Message-ID: <20050915144805.C27452@cox.net> (raw)
In-Reply-To: <20050915122301.41da6fb3.akpm@osdl.org>; from akpm@osdl.org on Thu, Sep 15, 2005 at 12:23:01PM -0700

On Thu, Sep 15, 2005 at 12:23:01PM -0700, Andrew Morton wrote:
> Matt Porter <mporter@kernel.crashing.org> wrote:
> >
> > On Thu, Sep 15, 2005 at 10:05:43AM -0500, Kumar Gala wrote:
> > > I'm guessing we are looking at a 2.6.15 timeframe now for getting the  
> > > RapidIO subsystem in?  Are there any other changes beyond what is  
> > > setting in -mm that need to be done?
> > 
> > Well, at least 2.6.15, 2.6.14 cutoff has passed.
> 
> Merging rapidio has negligible chance of breaking any existing kernel code,
> but I suppose that to be good little kernel citizens we should await 2.6.15
> if that's OK.

That's fine with me.
 
> > We are waiting on
> > a review of of the rionet updates I reposted a week ago. I've held
> > off on going too far with MMIO and 8548 support since the last rionet
> > changes required changes to the messaging support.
> 
> Jeff added the rionet driver to his tree and I dropped it from -mm, so
> we're ready to go on that front.

Ok, I did see that. Guess that was an ack then. :)

-Matt

      reply	other threads:[~2005-09-15 21:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-07 15:13 [PATCH][MM] rapidio: message interface updates Matt Porter
2005-09-15 15:05 ` Kumar Gala
2005-09-15 15:24   ` Matt Porter
2005-09-15 19:23     ` Andrew Morton
2005-09-15 21:48       ` Matt Porter [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=20050915144805.C27452@cox.net \
    --to=mporter@kernel.crashing.org \
    --cc=akpm@osdl.org \
    --cc=kumar.gala@freescale.com \
    --cc=linux-kernel@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