tree 0f9bf918d0be79198d42c9d23f7d69aed7b09460
parent 273a920f84e8b0b258737cea0f2f24627e8c5ed9
author David Benjamin <davidben@google.com> 1715568489 -0400
committer Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> 1716486636 +0000

Don't bother checking for NULL pointers in AES key schedule assembly

Some of the AES implementations tried to cleanly check for NULL input
and output pointers, but others did not, so callers could not rely on
this.

(If we end up needing to check this for some reason, we should do it in
the C wrapper.)

Change-Id: I495e5b3689837242b5c51bf01840997845190754
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/68688
Reviewed-by: Bob Beck <bbe@google.com>
Commit-Queue: David Benjamin <davidben@google.com>