public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@Oracle•com>
To: Paul Mackerras <paulus@samba•org>
Cc: linux-kernel@vger•kernel.org, linuxppc-dev@ozlabs•org,
	Andrew Morton <akpm@linux-foundation•org>,
	torvalds@linux-foundation•org,
	"\"Zhang Wei\" rdunlap@xenotime•net" <Wei.Zhang@freescale•com>
Subject: Re: [PATCH] docbook: fix fatal rapidio yet again (and more to come)
Date: Wed, 30 Apr 2008 15:11:49 -0700	[thread overview]
Message-ID: <20080430151149.063920cf.randy.dunlap@oracle.com> (raw)
In-Reply-To: <18456.60948.463017.139935@cargo.ozlabs.ibm.com>

On Thu, 1 May 2008 08:09:24 +1000 Paul Mackerras wrote:

> Andrew Morton writes:
> 
> > > Odd.  I thought Paul had picked up a docbook RapidIO patch from you in  
> > > the latest merge round.
> > > 
> > 
> > Well it's more than "a" patch.  The six-week-old patch series is:
> > 
> > rapidio-add-memory-mapping-driver-to-rapidio.patch
> > rapidio-add-rapidio-space-allocation-bitmap-arithmetic.patch
> > rapidio-add-fsl-rapidio-controller-memory-ops-functions.patch
> > rapidio-add-the-rapidio-master-port-maintance-and-doorbell-window-to-space-resources.patch
> > rapidio-add-rapidio-proc-fs-for-memory-mapping-debugging.patch
> > rapidio-add-the-memory-mapping-support-in-rionet-driver.patch
> > rapidio-fix-docbook-references.patch
> > rapidio-fix-kernel-doc-problems.patch
> 
> What happened is that you (Andrew) sent them on to me pretty much
> unexamined.  I took a look at them and dropped one of them because it
> created a new /proc file.  I asked Kumar to look at them and he had
> issues with another three of the patches, and dropping those meant
> that all the following ones (including the fix-kernel-doc one)
> wouldn't apply, so I dropped them too.  I applied the rest and sent
> them to Linus.
> 
> > (seems that I forgot to cc Jeff on the rionet change too).
> 
> Yeah.  I nearly dropped that one too.  I probably should have. :)
> 
> > Oh well.  If nobody puts their hand up in the next 24 hours or so I'll just
> > send it all in to Linus.
> 
> Please don't.  At this stage I think the best thing is for Kumar to
> talk to Zhang Wei (they both work for Freescale, so that should be
> possible in theory :) and get him to rework the remaining patches as
> required for inclusion in 2.6.27.

Just to be clear, the docbook changes shouldn't wait for 2.6.27.
There's no need for that.

---
~Randy

  reply	other threads:[~2008-04-30 23:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.64.0804292009000.18219@shark.he.net>
2008-04-30 18:35 ` [PATCH] docbook: fix fatal rapidio yet again (and more to come) Andrew Morton
2008-04-30 18:48   ` Randy Dunlap
2008-04-30 19:01   ` Kumar Gala
2008-04-30 19:12     ` Andrew Morton
2008-04-30 20:31       ` Kumar Gala
2008-04-30 22:09       ` Paul Mackerras
2008-04-30 22:11         ` Randy Dunlap [this message]
2008-04-30 22:14           ` Kumar Gala
2008-04-30 22:17             ` Randy Dunlap
2008-04-30 23:45               ` [PATCH] rapidio: fix current kernel-doc notation Randy Dunlap
2008-05-01  3:57                 ` Kumar Gala

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=20080430151149.063920cf.randy.dunlap@oracle.com \
    --to=randy.dunlap@oracle$(echo .)com \
    --cc=Wei.Zhang@freescale$(echo .)com \
    --cc=akpm@linux-foundation$(echo .)org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linuxppc-dev@ozlabs$(echo .)org \
    --cc=paulus@samba$(echo .)org \
    --cc=torvalds@linux-foundation$(echo .)org \
    /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