From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: Aravind Machiry <machiry@cs.ucsb.edu>
Cc: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: [BlueZ] lib: Replace malloc/memset(..0..) with malloc0
Date: Sat, 3 Oct 2020 14:49:42 -0700 [thread overview]
Message-ID: <CABBYNZJzbn2p7BNrcUOmSWKPhKcpDUcH_kL6oWLuE7H8gjy0RA@mail.gmail.com> (raw)
In-Reply-To: <CANozA0hYY6M_We73Zummfodk_g1HhWsyHiLP8Gw17rR+X89dpQ@mail.gmail.com>
Hi Aravind,
On Sat, Oct 3, 2020 at 11:14 AM Aravind Machiry <machiry@cs.ucsb.edu> wrote:
>
> Gentle reminder!
>
> On Mon, Sep 28, 2020 at 12:30 PM <bluez.test.bot@gmail.com> wrote:
> >
> > This is automated email and please do not reply to this email!
> >
> > Dear submitter,
> >
> > Thank you for submitting the patches to the linux bluetooth mailing list.
> > This is a CI test results with your patch series:
> > PW Link:https://patchwork.kernel.org/project/bluetooth/list/?series=356715
> >
> > ---Test result---
> >
> > ##############################
> > Test: CheckPatch - PASS
> >
> > ##############################
> > Test: CheckGitLint - PASS
> >
> > ##############################
> > Test: CheckBuild - PASS
> >
> > ##############################
> > Test: MakeCheck - PASS
> >
> >
> >
> > ---
> > Regards,
> > Linux Bluetooth
There seems to be a mixture of malloc0 or bt_malloc0 when I guess the
later should be preferred.
--
Luiz Augusto von Dentz
next prev parent reply other threads:[~2020-10-03 21:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-28 19:20 [PATCH BlueZ] lib: Replace malloc/memset(..0..) with malloc0 Aravind Machiry
2020-09-28 19:30 ` [BlueZ] " bluez.test.bot
2020-10-03 18:11 ` Aravind Machiry
2020-10-03 21:49 ` Luiz Augusto von Dentz [this message]
2020-10-04 0:36 ` Aravind Machiry
2020-10-08 0:01 ` Luiz Augusto von Dentz
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=CABBYNZJzbn2p7BNrcUOmSWKPhKcpDUcH_kL6oWLuE7H8gjy0RA@mail.gmail.com \
--to=luiz.dentz@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=machiry@cs.ucsb.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.