From: Nishanth Menon <nm@ti.com>
To: Denys Dmytriyenko <denis@denix.org>
Cc: meta-arago <meta-arago@arago-project.org>
Subject: Re: [PATCH dunfell] cryptodev: Move to 1.12 revision
Date: Thu, 4 Mar 2021 17:14:34 -0600 [thread overview]
Message-ID: <20210304231434.qyeopkbutdrvohm7@elliptic> (raw)
In-Reply-To: <20210304194836.GK4892@denix.org>
On 14:48-20210304, Denys Dmytriyenko wrote:
> BTW, you'd need to ensure updating cryptodev from 1.10 to 1.12 does not affect
> current 5.4-based builds and/or releases. I'm sure it will build fine against
> this older kernel (most of Makefile changes), but concerned about any run-time
> regressions (the actual code changes).
Thank you, actually you bring out a very good point here. While I know
we can create our own internal private fork of arago for upstream
component testing, I am starting to wonder if creating either of:
a) meta-ti-mainline that builds on top of meta-ti
OR
b) meta-arago-mainline on top of meta-arago
is a smarter approach - personally, I prefer (a)? While, I don't want
to end up creating too many layers, but your point is valid that I
should also be careful to not mess with folks using the meta-arago in
production environments having to deal with challenges we are trying
to flush out by testing the bleeding edge of kernel - and I'd like to
make sure TI ecosystem is able to leverage/contribute as well (an
internal fork will not be that useful)..
Any thoughts?
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
next prev parent reply other threads:[~2021-03-04 23:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-04 6:52 [PATCH dunfell] cryptodev: Move to 1.12 revision Nishanth Menon
2021-03-04 18:48 ` Denys Dmytriyenko
2021-03-04 19:48 ` Denys Dmytriyenko
2021-03-04 23:14 ` Nishanth Menon [this message]
2021-03-05 0:58 ` Denys Dmytriyenko
2021-03-05 1:24 ` Nishanth Menon
2021-03-05 2:26 ` Denys Dmytriyenko
2021-03-05 2:34 ` Nishanth Menon
2021-03-04 23:18 ` Nishanth Menon
2021-03-05 0:27 ` Denys Dmytriyenko
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=20210304231434.qyeopkbutdrvohm7@elliptic \
--to=nm@ti.com \
--cc=denis@denix.org \
--cc=meta-arago@arago-project.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.