Re: [PATCH 3/5] cpukit/libmd/md5.c: fix warning

On Thu, Jun 9, 2022 at 12:09 AM Sebastian Huber wrote: > > On 08/06/2022 18:09, Joel Sherrill wrote: > > > > On Wed, Jun 8, 2022, 10:45 AM Gedare Bloom > > wrote: > > > > Does this code have an upstream? > > > > > > I tried to find it. Maybe whoever added it has memor

Re: [PATCH 3/5] cpukit/libmd/md5.c: fix warning

On 08/06/2022 18:09, Joel Sherrill wrote: On Wed, Jun 8, 2022, 10:45 AM Gedare Bloom > wrote: Does this code have an upstream? I tried to find it. Maybe whoever added it has memory of the source. As best I can tell, it is lightly or not maintained reference code

Re: [PATCH 3/5] cpukit/libmd/md5.c: fix warning

On Wed, Jun 8, 2022, 10:45 AM Gedare Bloom wrote: > Does this code have an upstream? > I tried to find it. Maybe whoever added it has memory of the source. As best I can tell, it is lightly or not maintained reference code. > On Wed, Jun 8, 2022 at 7:35 AM Matthew Joyce > wrote: > > > > Fro

Re: [PATCH 3/5] cpukit/libmd/md5.c: fix warning

Does this code have an upstream? On Wed, Jun 8, 2022 at 7:35 AM Matthew Joyce wrote: > > From: Matt Joyce > > Specify array size in parameter to match function prototype. This > fixes a new warning in gcc 12. > --- > cpukit/libmd/md5.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > >

[PATCH 3/5] cpukit/libmd/md5.c: fix warning

From: Matt Joyce Specify array size in parameter to match function prototype. This fixes a new warning in gcc 12. --- cpukit/libmd/md5.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/cpukit/libmd/md5.c b/cpukit/libmd/md5.c index 4c909f37a0..5e3a100c7b 100644 --- a/cpukit/li