linux-kernel - Re: [PATCH] docbook: fix fatal rapidio yet again (and more to come)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <63DC9937-3C82-4744-8281-B9FDB941FEE1@kernel.crashing.org>
Date:	Wed, 30 Apr 2008 17:14:26 -0500
From:	Kumar Gala <galak@...nel.crashing.org>
To:	Randy Dunlap <randy.dunlap@...cle.com>
Cc:	Paul Mackerras <paulus@...ba.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	"\"Zhang Wei\" rdunlap@...otime.net" <Wei.Zhang@...escale.com>,
	linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
	mporter@...nel.crashing.org, benh@...nel.crashing.org,
	linuxppc-dev@...abs.org
Subject: Re: [PATCH] docbook: fix fatal rapidio yet again (and more to come)


On Apr 30, 2008, at 5:11 PM, Randy Dunlap wrote:
> 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.

Can the docbook be respun against linus's tree?

-k
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/