From: Matthew Wilcox <matthew@wil.cx>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] cleanup swiotlb.c a bit
Date: Thu, 06 Jan 2005 19:47:33 +0000 [thread overview]
Message-ID: <20050106194733.GM27371@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <200501060945.12364.jbarnes@engr.sgi.com>
On Thu, Jan 06, 2005 at 11:38:07AM -0800, David Mosberger wrote:
> For example, something like this:
>
> + io_tlb_start = alloc_bootmem_low_pages(io_tlb_nslabs *
> + (1 << IO_TLB_SHIFT));
>
> I find more readable if it's formatted as:
>
> io_tlb_start = alloc_bootmem_low_pages(io_tlb_nslabs
> * (1 << IO_TLB_SHIFT));
I find the former more readable. It lets you know there's something
coming on the next line.
> Well, it probably should move outside of the ia64 tree anyhow. The
> way x86_64 includes swiotlb.c at the moment is just absolutely gross.
kernel/swiotlb.c would make most sense, I guess?
--
"Next the statesmen will invent cheap lies, putting the blame upon
the nation that is attacked, and every man will be glad of those
conscience-soothing falsities, and will diligently study them, and refuse
to examine any refutations of them; and thus he will by and by convince
himself that the war is just, and will thank God for the better sleep
he enjoys after this process of grotesque self-deception." -- Mark Twain
next prev parent reply other threads:[~2005-01-06 19:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-06 17:45 [PATCH] cleanup swiotlb.c a bit Jesse Barnes
2005-01-06 19:38 ` David Mosberger
2005-01-06 19:42 ` Jesse Barnes
2005-01-06 19:47 ` Matthew Wilcox [this message]
2005-01-06 19:48 ` David Mosberger
2005-01-06 19:50 ` Jesse Barnes
2005-01-06 20:00 ` David Mosberger
2005-01-06 20:00 ` David Mosberger
2005-01-06 20:01 ` Matthew Wilcox
2005-01-06 20:06 ` Andi Kleen
2005-01-06 20:07 ` Jesse Barnes
2005-01-06 20:10 ` Matthew Wilcox
2005-01-06 20:11 ` Luck, Tony
2005-01-06 21:19 ` David Mosberger
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=20050106194733.GM27371@parcelfarce.linux.theplanet.co.uk \
--to=matthew@wil.cx \
--cc=linux-ia64@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.