Message ID | 1405440698-22961-1-git-send-email-mike.holmes@linaro.org |
---|---|
State | Rejected |
Headers | show |
Thanks, Mike. On Tue, Jul 15, 2014 at 11:11 AM, Mike Holmes <mike.holmes@linaro.org> wrote: > Signed-off-by: Mike Holmes <mike.holmes@linaro.org> > --- > crypto_design.dox | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/crypto_design.dox b/crypto_design.dox > index 869296e..05c620e 100644 > --- a/crypto_design.dox > +++ b/crypto_design.dox > @@ -157,7 +157,7 @@ The synchronization models of interest are summarized > in Figure 1: > > ![Figure 1: Synchronization Models](./images/syncmodels.png) > > -Note: Because few implementations are expected to offer the Parallel mode > of operation as described above, this mode is reserved for potential > future use. > +Note: Because few implementations are expected to offer the Parallel mode > of operation as described above, this mode is reserved for potential future > use. > For ODP only synchronous and asynchronous crypto operations are defined. > @section functional_definition Functional Definition > @subsection abstract_data_types Abstract data types > -- > 1.9.1 > > > _______________________________________________ > lng-odp mailing list > lng-odp@lists.linaro.org > http://lists.linaro.org/mailman/listinfo/lng-odp >
On 2014-07-15 12:11, Mike Holmes wrote: > Signed-off-by: Mike Holmes <mike.holmes@linaro.org> > --- > crypto_design.dox | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/crypto_design.dox b/crypto_design.dox > index 869296e..05c620e 100644 > --- a/crypto_design.dox > +++ b/crypto_design.dox > @@ -157,7 +157,7 @@ The synchronization models of interest are summarized in Figure 1: > > ![Figure 1: Synchronization Models](./images/syncmodels.png) > > -Note: Because few implementations are expected to offer the Parallel mode of operation as described above, this mode is reserved for potential future use. > +Note: Because few implementations are expected to offer the Parallel mode of operation as described above, this mode is reserved for potential future use. > For ODP only synchronous and asynchronous crypto operations are defined. > @section functional_definition Functional Definition > @subsection abstract_data_types Abstract data types > -- > 1.9.1 > > > _______________________________________________ > lng-odp mailing list > lng-odp@lists.linaro.org > http://lists.linaro.org/mailman/listinfo/lng-odp Applied! Thanks.
diff --git a/crypto_design.dox b/crypto_design.dox index 869296e..05c620e 100644 --- a/crypto_design.dox +++ b/crypto_design.dox @@ -157,7 +157,7 @@ The synchronization models of interest are summarized in Figure 1: ![Figure 1: Synchronization Models](./images/syncmodels.png) -Note: Because few implementations are expected to offer the Parallel mode of operation as described above, this mode is reserved for potential future use. +Note: Because few implementations are expected to offer the Parallel mode of operation as described above, this mode is reserved for potential future use. For ODP only synchronous and asynchronous crypto operations are defined. @section functional_definition Functional Definition @subsection abstract_data_types Abstract data types
Signed-off-by: Mike Holmes <mike.holmes@linaro.org> --- crypto_design.dox | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)