All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/2] package/linuxptp: fix coding style issue
Date: Thu, 6 Jul 2017 21:09:35 +0200	[thread overview]
Message-ID: <20170706210935.4204fd61@windsurf.lan> (raw)
In-Reply-To: <20170706174336.12294-1-romain.naour@smile.fr>

Hello,

On Thu,  6 Jul 2017 19:43:35 +0200, Romain Naour wrote:
> Thanks to Yann for the live review during the Buildroot summer camp.
> 
> Signed-off-by: Romain Naour <romain.naour@smile.fr>
> Cc: Petr Kulhavy <brain@jikos.cz>
> Cc: "Yann E. MORIN" <yann.morin.1998@free.fr>
> ---
>  package/linuxptp/linuxptp.mk | 17 ++++++++++++-----
>  1 file changed, 12 insertions(+), 5 deletions(-)

I've applied both patches. However, the second patch created quite a
bit of duplication between the build and install steps, so I committed
an additional patch that creates and uses LINUXPTP_MAKE_ENV and
LINUXPTP_MAKE_OPTS variables.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  parent reply	other threads:[~2017-07-06 19:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-06 17:43 [Buildroot] [PATCH v2 1/2] package/linuxptp: fix coding style issue Romain Naour
2017-07-06 17:43 ` [Buildroot] [PATCH v2 2/2] package/linuxptp: set KBUILD_OUTPUT to STAGING_DIR Romain Naour
2017-07-06 22:03   ` Petr Kulhavy
2017-07-06 22:51     ` Arnout Vandecappelle
2017-07-07  9:29       ` Petr Kulhavy
2017-07-06 19:09 ` Thomas Petazzoni [this message]
2017-07-06 19:31   ` [Buildroot] [PATCH v2 1/2] package/linuxptp: fix coding style issue Romain Naour

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=20170706210935.4204fd61@windsurf.lan \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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.