From: Arnaldo Carvalho de Melo <acme@redhat.com>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: "Wangnan (F)" <wangnan0@huawei.com>,
Florian Fainelli <f.fainelli@gmail.com>,
linux-kernel@vger.kernel.org, ast@kernel.org, jolsa@kernel.org
Subject: Re: [PATCH 0/2] bfp tools: Couple Coverity fixes
Date: Wed, 27 Apr 2016 11:24:47 -0300 [thread overview]
Message-ID: <20160427142447.GA2535@redhat.com> (raw)
In-Reply-To: <20160427030816.GA54649@ast-mbp.thefacebook.com>
Em Tue, Apr 26, 2016 at 08:08:18PM -0700, Alexei Starovoitov escreveu:
> On Wed, Apr 27, 2016 at 11:00:23AM +0800, Wangnan (F) wrote:
> >
> >
> > On 2016/4/27 10:46, Florian Fainelli wrote:
> > >Le 24/04/2016 19:34, Florian Fainelli a écrit :
> > >>Hi all,
> > >>
> > >>Two trivial patches that were flagged by Coverity.
> > >>
> > >>Thanks!
> > >Ping! Did I send this to the correct mailing-list?
> >
> > Sorry for the late. You are on the right list :)
>
> Arnaldo, please take a look. They look good to me.
Will do, just readying it a 30-patch long pull req to Ingo, will collect
those for the next one, with your Acked-by tags.
- Arnaldo
prev parent reply other threads:[~2016-04-27 14:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-25 2:34 [PATCH 0/2] bfp tools: Couple Coverity fixes Florian Fainelli
2016-04-25 2:34 ` [PATCH 1/2] bfp tools: Remove expression with no effect Florian Fainelli
2016-04-27 3:11 ` Wangnan (F)
2016-04-27 14:33 ` Arnaldo Carvalho de Melo
2016-05-01 7:36 ` [tip:perf/core] bpf " tip-bot for Florian Fainelli
2016-04-25 2:34 ` [PATCH 2/2] bfp tools: Fix syscall argument Florian Fainelli
2016-04-27 3:01 ` Wangnan (F)
2016-04-27 14:34 ` Arnaldo Carvalho de Melo
2016-05-01 7:37 ` [tip:perf/core] bpf " tip-bot for Florian Fainelli
2016-04-27 2:46 ` [PATCH 0/2] bfp tools: Couple Coverity fixes Florian Fainelli
2016-04-27 3:00 ` Wangnan (F)
2016-04-27 3:08 ` Alexei Starovoitov
2016-04-27 14:24 ` Arnaldo Carvalho de Melo [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=20160427142447.GA2535@redhat.com \
--to=acme@redhat.com \
--cc=alexei.starovoitov@gmail.com \
--cc=ast@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wangnan0@huawei.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 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.