From: Michael Ellerman <mpe@ellerman.id.au>
To: Vineeth Vijayan <vvijayan@mvista.com>
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: powerpc: Fix Text randomization
Date: Fri, 14 Nov 2014 17:20:50 +1100 [thread overview]
Message-ID: <1415946050.26378.3.camel@concordia> (raw)
In-Reply-To: <CAOpNGcsQX1d4=MpHKKKnBotBb11dq55_kQp4PG8OA++U6peqKg@mail.gmail.com>
On Fri, 2014-11-14 at 11:03 +0530, Vineeth Vijayan wrote:
> ping !
>
> any update on this ? As i understand, only powerpc and s390 uses the
> randomize_et_dyn call; for all other architecture this is an obsolete
> function call.
I asked:
> >> I'm not clear on what has changed to break this?
And you didn't tell me.
> this call for another patch where randomize_et_dyn is removed.
Patches welcome :)
cheers
next prev parent reply other threads:[~2014-11-14 6:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-10 5:45 [PATCH] powerpc: Fix Text randomization Vineeth Vijayan
2014-10-15 2:08 ` Michael Ellerman
2014-10-15 6:38 ` Vineeth Vijayan
2014-11-14 5:31 ` Vineeth Vijayan
2014-11-14 5:33 ` Vineeth Vijayan
2014-11-14 6:20 ` Michael Ellerman [this message]
2014-11-14 8:48 ` Vineeth Vijayan
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=1415946050.26378.3.camel@concordia \
--to=mpe@ellerman.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=vvijayan@mvista.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).