From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: [PATCH] ppc64 iommu rewrite part 3/5
Date: Fri, 27 Feb 2004 23:28:00 +1100 [thread overview]
Message-ID: <1077884879.22232.385.camel@gaston> (raw)
This one is probably too large for the list, sent privately
to the usual culprits, lurkers can find it at:
http://gate.crashing.org/~benh/iommu-rewrite-part3.diff
<<
Bulk of the iommu rewrite.
Lots of things renamed, sillicaps killed, stuffs moved around and
common code properly extracted from implementation specific code,
new allocator, etc... The code is overall a lot simpler, faster,
less prone to fail, and a lot more manageable.
I didn't use "bk mv", there is no need to keep the old history
attached to the new file.
>>
reply other threads:[~2004-02-27 12:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1077884879.22232.385.camel@gaston \
--to=benh@kernel.crashing.org \
--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