All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex J Lennon <ajlennon@dynamicdevices.co.uk>
To: Andrei Gherzan <andrei@gherzan.ro>
Cc: Yocto Project <yocto@yoctoproject.org>
Subject: Re: [meta-raspberrypi][PATCH 0/1] pi-blaster: Add recipe
Date: Wed, 11 Jun 2014 17:53:08 +0100	[thread overview]
Message-ID: <53988974.6090409@dynamicdevices.co.uk> (raw)
In-Reply-To: <CAK18fxGb7aYv1f-3qfoJDiNKM4C7FfiKVOUJk5D0JaU7uCEnig@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2140 bytes --]


On 10/06/2014 20:50, Andrei Gherzan wrote:
> Hi Alex,
>
>
> On Tue, May 20, 2014 at 5:40 PM, Alex J Lennon
> <ajlennon@dynamicdevices.co.uk <mailto:ajlennon@dynamicdevices.co.uk>>
> wrote:
>
>     Please see following patch for details.
>
>     The following changes since commit
>     f3a8693f08f99893453fd1fe282515b2f222c080:
>
>       omxplayer: Update to remote's HEAD (2014-05-09 14:56:59 +0300)
>
>     are available in the git repository at:
>
>       git://github.com/DynamicDevices/meta-raspberrypi
>     <http://github.com/DynamicDevices/meta-raspberrypi> ajl/pi-blaster
>       https://github.com/DynamicDevices/meta-raspberrypi/tree/master
>
>     Alex J Lennon (1):
>       pi-blaster: Added recipe
>
>      recipes-devtools/pi-blaster/files/initscript.patch | 71
>     ++++++++++++++++++++++
>      recipes-devtools/pi-blaster/pi-blaster.inc         | 36 +++++++++++
>      recipes-devtools/pi-blaster/pi-blaster_git.bb
>     <http://pi-blaster_git.bb>      |  3 +
>      3 files changed, 110 insertions(+)
>      create mode 100644 recipes-devtools/pi-blaster/files/initscript.patch
>      create mode 100644 recipes-devtools/pi-blaster/pi-blaster.inc
>      create mode 100644 recipes-devtools/pi-blaster/pi-blaster_git.bb
>     <http://pi-blaster_git.bb>
>
>
> You missed the actual patch so I will give my feedback listed below:
> 1. Refactor commit log.
> 2. One space left after "oe_runmake".
> 3. Why exactly do you need oe_runmake after all?
> 4. I would replace the do install/configure appends with a patch on
> Makefile (would be useful for the project's maintainer too).
> 5. Please add comments to patches too. Here is an example:
> http://git.yoctoproject.org/cgit/cgit.cgi/meta-raspberrypi/tree/recipes-bsp/rpi-mkimage/rpi-mkimage/open-files-relative-to-script.patch
>

Thanks for the comprehensive response Andrei, and also for the link to
the OpenEmbedded Commit Patch Message Guidelines - very useful.

I've reworked the pi-blaster recipe, hopefully in line with your
comments, and pushed a second patch-set up to the review server.

Regards,

Alex


[-- Attachment #2: Type: text/html, Size: 4356 bytes --]

  reply	other threads:[~2014-06-11 16:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-20 14:40 [meta-raspberrypi][PATCH 0/1] pi-blaster: Add recipe Alex J Lennon
2014-05-20 14:41 ` [meta-raspberrypi][PATCH 1/1] pi-blaster: Added recipe Alex J Lennon
     [not found]   ` <CAK18fxFixNCCVRt7An58rZSukfmcziprGitd6fFywkfeiupAww@mail.gmail.com>
2014-06-10 23:40     ` Alex J Lennon
2014-06-11  7:39       ` Andrei Gherzan
2014-06-10 19:50 ` [meta-raspberrypi][PATCH 0/1] pi-blaster: Add recipe Andrei Gherzan
2014-06-11 16:53   ` Alex J Lennon [this message]
2014-06-11 16:59     ` Andrei Gherzan

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=53988974.6090409@dynamicdevices.co.uk \
    --to=ajlennon@dynamicdevices.co.uk \
    --cc=andrei@gherzan.ro \
    --cc=yocto@yoctoproject.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.