Linux-WPAN Archive on lore.kernel.org
 help / color / Atom feed
From: Alexander Aring <alex.aring@gmail.com>
To: Stefan Schmidt <stefan@datenfreihafen.org>
Cc: linux-wpan@vger.kernel.org
Subject: Re: [PATCH rpld 0/6] Mixed bag of rpld patches
Date: Thu, 9 Jan 2020 17:38:59 -0500
Message-ID: <20200109223859.kfveuy6tmwtzc5mm@ryzen> (raw)
In-Reply-To: <20190918195819.7492-1-stefan@datenfreihafen.org>

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.

- Alex

  parent reply index

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 [this message]
2020-01-10  8:54   ` Stefan Schmidt

Reply instructions:

You may reply publically 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=20200109223859.kfveuy6tmwtzc5mm@ryzen \
    --to=alex.aring@gmail.com \
    --cc=linux-wpan@vger.kernel.org \
    --cc=stefan@datenfreihafen.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

Linux-WPAN Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-wpan/0 linux-wpan/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-wpan linux-wpan/ https://lore.kernel.org/linux-wpan \
		linux-wpan@vger.kernel.org
	public-inbox-index linux-wpan

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-wpan


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git