From: "naohirot@fujitsu.com" <naohirot@fujitsu.com>
To: Carlos O'Donell <carlos@redhat.com>, DJ Delorie <dj@redhat.com>
Cc: "xuyang2018.jy@fujitsu.com" <xuyang2018.jy@fujitsu.com>,
"libc-alpha@sourceware.org" <libc-alpha@sourceware.org>
Subject: RE: [PATCH v2] tst-mallinfo2.c: Use correct multiple for total variable
Date: Wed, 19 May 2021 00:32:55 +0000 [thread overview]
Message-ID: <TYAPR01MB6025A9BA10A44021EE1DB956DF2B9@TYAPR01MB6025.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <TYCPR01MB654402411AFFCC32E506E14AFD539@TYCPR01MB6544.jpnprd01.prod.outlook.com>
Hi Carlos , DJ,
cc: Yang,
> From: Libc-alpha <libc-alpha-bounces@sourceware.org> On Behalf Of
> xuyang2018.jy@fujitsu.com
> Hi Carlos , DJ
>
> Fujitsu submitted signed assignment finally.
> So please kindly merge the following patch.
>
> https://patchwork.ozlabs.org/project/glibc/patch/1613616993-2623-1-git-send
> -email-xuyang2018.jy@cn.fujitsu.com/
Fujitsu has received FSF signed assignment.
So the contract process has completed.
Thanks.
Naohiro
> Best Regards
> Yang Xu
> -----Original Message-----
> From: Carlos O'Donell <carlos@redhat.com>
> Sent: Tuesday, February 23, 2021 10:30 AM
> To: Xu, Yang/徐 杨 <xuyang2018.jy@cn.fujitsu.com>;
> libc-alpha@sourceware.org; DJ Delorie <dj@redhat.com>
> Subject: Re: [PATCH v2] tst-mallinfo2.c: Use correct multiple for total variable
>
> On 2/17/21 9:56 PM, Yang Xu wrote:
> > Since test uses 160 multiple for malloc size, we should also use 160
> > multiple for total variable instead of 16, then comparison is meaningful. So fix it.
>
> > Also change the ">" to ">=" so that the test is technically valid.
>
> Yang,
>
> Thank you very much for your great work with this patch.
>
> I need your help in order to complete the FSF copyright assignment process with
> Fujitsu.
>
> I've sent you an Naohiro and email to start the process.
>
> Thank you for your help.
>
> > ---
> > malloc/tst-mallinfo2.c | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/malloc/tst-mallinfo2.c b/malloc/tst-mallinfo2.c index
> > 59a15cf7a8..7d00b65f6e 100644
> > --- a/malloc/tst-mallinfo2.c
> > +++ b/malloc/tst-mallinfo2.c
> > @@ -68,14 +68,14 @@ do_test (void)
> > for (i = 1; i < 20; ++i)
> > {
> > ptr = malloc (160 * i);
> > - total += 16 * i;
> > + total += 160 * i;
> > }
> >
> > mi2 = mallinfo2 ();
> > print_mi ("after", &mi2);
> >
> > /* Check at least something changed. */
> > - TEST_VERIFY (mi2.uordblks > mi1.uordblks + total);
> > + TEST_VERIFY (mi2.uordblks >= mi1.uordblks + total);
> >
> > return 0;
> > }
> >
>
>
> --
> Cheers,
> Carlos.
>
>
next prev parent reply other threads:[~2021-05-19 0:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-03 5:45 [PATCH] " Yang Xu
2021-02-03 22:31 ` DJ Delorie
2021-02-04 1:30 ` Yang Xu
2021-02-16 3:44 ` DJ Delorie
2021-02-18 2:38 ` Yang Xu
2021-02-18 2:56 ` [PATCH v2] " Yang Xu
2021-02-23 2:29 ` Carlos O'Donell
2021-05-11 5:52 ` xuyang2018.jy
2021-05-19 0:32 ` naohirot [this message]
2021-05-25 20:49 ` DJ Delorie
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=TYAPR01MB6025A9BA10A44021EE1DB956DF2B9@TYAPR01MB6025.jpnprd01.prod.outlook.com \
--to=naohirot@fujitsu.com \
--cc=carlos@redhat.com \
--cc=dj@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=xuyang2018.jy@fujitsu.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).