From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Horia Geanta <horia.geanta@nxp.com>
Cc: Roy Pledge <roy.pledge@nxp.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
Aymen Sghaier <aymen.sghaier@nxp.com>,
Leo Li <leoyang.li@nxp.com>,
Madalin-cristian Bucur <madalin.bucur@nxp.com>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] crypto: caam/qi - simplify CGR allocation, freeing
Date: Mon, 29 Oct 2018 09:56:29 +0100 [thread overview]
Message-ID: <20181029085629.55exxlamujlyvs3n@linutronix.de> (raw)
In-Reply-To: <VI1PR0402MB3485A342A184BEBB004E74F998F70@VI1PR0402MB3485.eurprd04.prod.outlook.com>
On 2018-10-25 14:05:32 [+0000], Horia Geanta wrote:
> > Now, what is the problem with the CPU limitation? Is this a HW
> > limitation that you can access the registers from a certain CPU?
> >
> Roy confirmed the CPU limitation should actually be removed, there is nothing in
> HW requiring it.
> A clean-up patch will follow.
good. Thank you.
> Thanks,
> Horia
Sebastian
next prev parent reply other threads:[~2018-10-29 17:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-05 12:54 set_cpus_allowed_ptr() usage in FREESCALE CAAM Sebastian Andrzej Siewior
2018-10-08 11:09 ` [PATCH] crypto: caam/qi - simplify CGR allocation, freeing Horia Geantă
2018-10-09 17:11 ` Sebastian Andrzej Siewior
2018-10-25 14:05 ` Horia Geanta
2018-10-29 8:56 ` Sebastian Andrzej Siewior [this message]
2018-10-17 6:21 ` Herbert Xu
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=20181029085629.55exxlamujlyvs3n@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=aymen.sghaier@nxp.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=horia.geanta@nxp.com \
--cc=leoyang.li@nxp.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=madalin.bucur@nxp.com \
--cc=peterz@infradead.org \
--cc=roy.pledge@nxp.com \
--cc=tglx@linutronix.de \
/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).