From: Oliver Graute <oliver.graute@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-networking] [PATCH v2] nfacct: added nfacct recipe to meta-networking
Date: Thu, 6 Apr 2017 16:06:14 +0200 [thread overview]
Message-ID: <20170406140614.GA17864@graute-opti> (raw)
In-Reply-To: <20170405184218.GD3301@jama>
On 05/04/17, Martin Jansa wrote:
> On Wed, Apr 05, 2017 at 03:38:57PM +0200, Oliver Graute wrote:
> > this patch adds nfacct to meta-networking
>
> nfacct -> ${BPN}
> nfacct-1.0.2 -> ${BP}
>
> > +S = "${WORKDIR}/nfacct-${PV}"
>
> This is the default, drop.
just saw that first version of this patch was already applied. I'll send
a patch to fix the remarks.
Best Regards,
Oliver
prev parent reply other threads:[~2017-04-06 14:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-05 13:38 [meta-networking] [PATCH v2] nfacct: added nfacct recipe to meta-networking Oliver Graute
2017-04-05 18:42 ` Martin Jansa
2017-04-06 14:06 ` Oliver Graute [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=20170406140614.GA17864@graute-opti \
--to=oliver.graute@gmail.com \
--cc=openembedded-devel@lists.openembedded.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 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.