From: Jeremy Kerr <jk@ozlabs.org>
To: linuxppc-dev@ozlabs.org
Cc: Nathan Lynch <ntl@pobox.com>,
matthltc@us.ibm.com, Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH] linux,tce-size property is 32 bits
Date: Fri, 6 Oct 2006 12:16:30 +1000 [thread overview]
Message-ID: <200610061216.32315.jk@ozlabs.org> (raw)
In-Reply-To: <20061005143244.GJ24705@localdomain>
> AFAICT this was introduced by the "Constify & voidify get_property()"
> series which went in post-2.6.18 so no backport for -stable is
> needed. Not sure about RHEL5.
That patch (954a46e2d5aec6f59976ddeb1d232b486e59b54a) did touch the
declaration of sizep, but only changed it from an unsigned long * to an
const unsigned long *.
Looking at the git log, it's been an unsigned long from the beginning
(ie, being moved from arch/ppc64). You may need to check the stable and
RHEL trees explicitly.
Regards,
Jeremy
next prev parent reply other threads:[~2006-10-06 2:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-05 3:28 [PATCH] linux,tce-size property is 32 bits Nathan Lynch
2006-10-05 9:18 ` Benjamin Herrenschmidt
2006-10-05 14:32 ` Nathan Lynch
2006-10-06 2:16 ` Jeremy Kerr [this message]
2006-10-06 2:22 ` Olof Johansson
2006-10-06 2:27 ` Jeremy Kerr
2006-10-05 15:36 ` Olof Johansson
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=200610061216.32315.jk@ozlabs.org \
--to=jk@ozlabs.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=matthltc@us.ibm.com \
--cc=ntl@pobox.com \
--cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).