All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Barker <pbarker@toganlabs.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: yocto@lists.yoctoproject.org
Subject: Re: [PATCH][meta-raspberrypi] linux-raspberrypi_dev: don't use AUTOREV
Date: Thu, 1 Jun 2017 12:23:08 +0100	[thread overview]
Message-ID: <CAPyrkgwPwe_Fqi0nGna=ud4opuWFVGntUh8=0Kg95OzxTui-9w@mail.gmail.com> (raw)
In-Reply-To: <CA+chaQcufcNiAh2s5PCtQc1ES4B0uYcsBotV3BG0uqG0NRgw0w@mail.gmail.com>

On Thu, Jun 1, 2017 at 8:10 AM, Martin Jansa <martin.jansa@gmail.com> wrote:
> And it's not clear from the diff you send, but like linux-yocto-dev.bb
> example above, the recipe needs to be renamed from linux-raspberrypi_dev.bb
> to linux-raspberrypi-dev.bb to make it different provider.
>
> On Thu, Jun 1, 2017 at 9:08 AM, Martin Jansa <martin.jansa@gmail.com> wrote:
>>
>> Yes, Paul approach looks good to me, I think it was what was suggested in
>> first replies to my SRCREV change and I agree with that, I just haven't had
>> time to send updated patch.
>>
>> Paul if you have the patch ready please send it, thanks!.
>>

I've submitted the patch via GitHub as per the new contributing
instructions for meta-raspberrypi.

https://github.com/agherzan/meta-raspberrypi/pull/82

Cheers,

-- 
Paul Barker
Co-Founder & Principal Engineer
Togán Labs Ltd


  reply	other threads:[~2017-06-01 11:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-30  7:57 [PATCH][meta-raspberrypi] linux-raspberrypi_dev: don't use AUTOREV Martin Jansa
2017-05-30 16:07 ` Khem Raj
2017-05-30 17:15   ` Paul Barker
2017-05-30 17:25     ` Andre McCurdy
2017-05-30 17:29       ` Khem Raj
2017-06-01  0:00         ` Andrei Gherzan
2017-06-01  0:17           ` Khem Raj
2017-06-01  6:10             ` Paul Barker
2017-06-01  7:08               ` Martin Jansa
2017-06-01  7:10                 ` Martin Jansa
2017-06-01 11:23                   ` Paul Barker [this message]
2017-06-01 12:48                     ` 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='CAPyrkgwPwe_Fqi0nGna=ud4opuWFVGntUh8=0Kg95OzxTui-9w@mail.gmail.com' \
    --to=pbarker@toganlabs.com \
    --cc=martin.jansa@gmail.com \
    --cc=yocto@lists.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.