Checks
| Context |
Check |
Description |
| dj/TryBot-apply_patch |
success
|
Patch applied to master at the time it was sent
|
| dj/TryBot-32bit |
success
|
Build for i686
|
Commit Message
---
manual/string.texi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Comments
On 15/1/23 19:37, Martin Joerg via Libc-alpha wrote:
> ---
> manual/string.texi | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
* Martin Joerg via Libc-alpha:
> ---
> manual/string.texi | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/manual/string.texi b/manual/string.texi
> index 0b60b3fbb4..7578aa1c26 100644
> --- a/manual/string.texi
> +++ b/manual/string.texi
> @@ -2396,7 +2396,7 @@ is better than not using it. At present, the only way to do a more
> thorough job is to write the entire sensitive operation in assembly
> language. We anticipate that future compilers will recognize calls to
> @code{explicit_bzero} and take appropriate steps to erase all the
> -copies of the affected data, whereever they may be.
> +copies of the affected data, wherever they may be.
>
> @deftypefun void explicit_bzero (void *@var{block}, size_t @var{len})
> @standards{BSD, string.h}
Carlos, still okay to merge this?
Thanks,
Florian
On 1/18/23 09:52, Florian Weimer wrote:
> * Martin Joerg via Libc-alpha:
>
>> ---
>> manual/string.texi | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/manual/string.texi b/manual/string.texi
>> index 0b60b3fbb4..7578aa1c26 100644
>> --- a/manual/string.texi
>> +++ b/manual/string.texi
>> @@ -2396,7 +2396,7 @@ is better than not using it. At present, the only way to do a more
>> thorough job is to write the entire sensitive operation in assembly
>> language. We anticipate that future compilers will recognize calls to
>> @code{explicit_bzero} and take appropriate steps to erase all the
>> -copies of the affected data, whereever they may be.
>> +copies of the affected data, wherever they may be.
>>
>> @deftypefun void explicit_bzero (void *@var{block}, size_t @var{len})
>> @standards{BSD, string.h}
>
> Carlos, still okay to merge this?
Absolutely. Please feel free to adjust the manual as required to correct typos
and fix bugs in the manual.
@@ -2396,7 +2396,7 @@ is better than not using it. At present, the only way to do a more
thorough job is to write the entire sensitive operation in assembly
language. We anticipate that future compilers will recognize calls to
@code{explicit_bzero} and take appropriate steps to erase all the
-copies of the affected data, whereever they may be.
+copies of the affected data, wherever they may be.
@deftypefun void explicit_bzero (void *@var{block}, size_t @var{len})
@standards{BSD, string.h}