From: Stefan Schmidt <stefan@datenfreihafen.org>
To: Alexander Aring <alex.aring@gmail.com>
Cc: linux-wpan@vger.kernel.org
Subject: Re: [PATCH rpld 0/6] Mixed bag of rpld patches
Date: Fri, 10 Jan 2020 09:54:26 +0100 [thread overview]
Message-ID: <a1493f2c-887e-7552-7d44-09ead5c6af79@datenfreihafen.org> (raw)
In-Reply-To: <20200109223859.kfveuy6tmwtzc5mm@ryzen>
Hello.
On 09.01.20 23:38, Alexander Aring wrote:
> Hi Stefan,
>
> On Wed, Sep 18, 2019 at 09:58:13PM +0200, Stefan Schmidt wrote:
>> Hello.
>>
>> This series does really not have any theme, besides me starting
>> to look into rpld and playing around with it.
>>
>> I had to fix meson for my lua detection and make sure the ifdef
>> for SCOPE_ID is honoured. After getting it all building locally
>> I added Travis support and submitted builds to Coverity.
>> Afterwards I did a quick run through the reports from address
>> sanitizer and coverity scan.
>>
>> Not sure if you would prefer review for rpld as patches here on
>> the list or as pull requests on github. Up to you.
>>
>> Stefan Schmidt (6):
>> build: test various names for our lua dependency
>> send: make sure we check on scope id usage
>> ci: travis: initial setup for CI testing with Travis
>> config : fix leaks on error paths
>> socket: make sure we close our socket if setsockopt() fails
>> send: ensure we free the buffer after sending the message
>
> I tested the patch series and so far it still compiles on my machine.
>
> Reviewed-by: Alexander Aring <alex.aring@gmail.com>
>
> on all patches.
Thanks. I landed them in master now.
regards
Stefan Schmidt
prev parent reply other threads:[~2020-01-10 8:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190918195819.7492-1-stefan@datenfreihafen.org>
[not found] ` <20190918195819.7492-3-stefan@datenfreihafen.org>
2019-12-20 22:52 ` [PATCH rpld 2/6] send: make sure we check on scope id usage Alexander Aring
2019-12-20 23:06 ` [PATCH rpld 0/6] Mixed bag of rpld patches Alexander Aring
2019-12-22 22:07 ` Stefan Schmidt
2020-01-09 22:38 ` Alexander Aring
2020-01-10 8:54 ` Stefan Schmidt [this message]
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=a1493f2c-887e-7552-7d44-09ead5c6af79@datenfreihafen.org \
--to=stefan@datenfreihafen.org \
--cc=alex.aring@gmail.com \
--cc=linux-wpan@vger.kernel.org \
/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 NNTP newsgroup(s).