From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: will_schmidt@vnet.ibm.com
Cc: linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH] Use 1TB segments
Date: Fri, 03 Aug 2007 08:37:25 +1000 [thread overview]
Message-ID: <1186094245.5495.637.camel@localhost.localdomain> (raw)
In-Reply-To: <1186087283.22717.80.camel@farscape.rchland.ibm.com>
> Is there technical reason why the 'local' variable remains at the end of
> the parm list for these? In other cases 'ssize' simply gets added to
> the end of the parm list.
Looks nicer to have psize and ssize together :-)
Ben.
next prev parent reply other threads:[~2007-08-02 22:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-01 2:04 [PATCH] Use 1TB segments Paul Mackerras
2007-08-02 20:41 ` Will Schmidt
2007-08-02 22:37 ` Benjamin Herrenschmidt [this message]
2007-08-02 23:56 ` Will Schmidt
2007-08-03 2:53 ` David Gibson
2007-08-06 22:23 ` Jon Tollefson
2007-08-10 3:53 ` Michael Neuling
2007-10-02 18:37 ` Will Schmidt
2007-10-03 2:11 ` Olof Johansson
2007-10-03 3:07 ` Paul Mackerras
2007-10-03 3:27 ` Olof Johansson
2007-10-03 3:13 ` Paul Mackerras
2007-10-03 14:22 ` Will Schmidt
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=1186094245.5495.637.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=will_schmidt@vnet.ibm.com \
/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;
as well as URLs for NNTP newsgroup(s).