From: Kumar Gala <galak@kernel.crashing.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: rdunlap@xenotime.net, linux-kernel@vger.kernel.org,
torvalds@linux-foundation.org, mporter@kernel.crashing.org,
paulus@samba.org, benh@kernel.crashing.org,
linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] docbook: fix fatal rapidio yet again (and more to come)
Date: Wed, 30 Apr 2008 15:31:48 -0500 [thread overview]
Message-ID: <B50A5950-3660-4866-A59A-5C2317444875@kernel.crashing.org> (raw)
In-Reply-To: <20080430121239.28492328.akpm@linux-foundation.org>
On Apr 30, 2008, at 2:12 PM, Andrew Morton wrote:
> On Wed, 30 Apr 2008 14:01:12 -0500
> Kumar Gala <galak@kernel.crashing.org> wrote:
>
>>
>> On Apr 30, 2008, at 1:35 PM, Andrew Morton wrote:
>>> On Tue, 29 Apr 2008 20:10:55 -0700 (PDT)
>>> "Randy.Dunlap" <rdunlap@xenotime.net> wrote:
>>>
>>>> From: Randy Dunlap <randy.dunlap@oracle.com>
>>>>
>>>> Don't refer to file that no longer exists:
>>>> docproc: linux-2.6.25-git14/arch/powerpc/kernel/rio.c: No such file
>>>> or directory
>>>>
>>>> Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
>>>> ---
>>>> Documentation/DocBook/rapidio.tmpl | 1 -
>>>> 1 file changed, 1 deletion(-)
>>>>
>>>> --- linux-2.6.25-git14.orig/Documentation/DocBook/rapidio.tmpl
>>>> +++ linux-2.6.25-git14/Documentation/DocBook/rapidio.tmpl
>>>> @@ -133,7 +133,6 @@
>>>> !Idrivers/rapidio/rio-sysfs.c
>>>> </sect1>
>>>> <sect1 id="PPC32_support"><title>PPC32 support</title>
>>>> -!Iarch/powerpc/kernel/rio.c
>>>> !Earch/powerpc/sysdev/fsl_rio.c
>>>> !Iarch/powerpc/sysdev/fsl_rio.c
>>>> </sect1>
>>>
>>> grumble.
>>>
>>> This is a subset of rapidio-fix-docbook-references.patch, but I
>>> appear to
>>> be unable to interest anyone in merging/reviewing/accepting/
>>> anything-
>>> else
>>> that quite large set of patches.
>>>
>>> Guys, those patches were sent six weeks ago and it now looks like
>>> they will
>>> miss 2.6.26. This is pretty slack of us. Help?
>>
>> 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
>
> totalling:
>
> arch/powerpc/sysdev/fsl_rio.c | 13 +
> include/linux/rio.h | 10
> drivers/net/Kconfig | 10
> drivers/net/rionet.c | 324 ++++++++++++++++++++++++++
> ++++
> drivers/rapidio/Makefile | 1
> drivers/rapidio/rio.c | 10
> drivers/rapidio/sallocator/Kconfig | 9
> drivers/rapidio/sallocator/Makefile | 12 +
> drivers/rapidio/sallocator/bitmap.c | 384 ++++++++++++++++++++++++++
> ++++++++++
> include/linux/rio.h | 10
> include/linux/rio_drv.h | 41 +++
> 16 files changed, 1425 insertions(+), 14 deletions(-)
>
>
> (seems that I forgot to cc Jeff on the rionet change too).
>
>
> Oh well. If nobody puts their hand up in the next 24 hours or so
> I'll just
> send it all in to Linus.
I'm raising my hand. The memory map driver needs further review. If
the Docbook issues can be applied w/o the other patches I suggest we
go forward with those.
- k
next prev parent reply other threads:[~2008-04-30 20:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-30 3:10 Randy.Dunlap
2008-04-30 18:35 ` 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 [this message]
[not found] ` <18456.60948.463017.139935@cargo.ozlabs.ibm.com>
2008-04-30 22:11 ` Randy Dunlap
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=B50A5950-3660-4866-A59A-5C2317444875@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=akpm@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mporter@kernel.crashing.org \
--cc=paulus@samba.org \
--cc=rdunlap@xenotime.net \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®