All of lore.kernel.org
 help / color / mirror / Atom feed
From: Otavio Salvador <otavio.salvador@ossystems.com.br>
To: Marek Vasut <marex@denx.de>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/2] u-boot: Factor out common bits
Date: Mon, 5 Sep 2016 13:26:52 -0300	[thread overview]
Message-ID: <CAP9ODKpB9ofyxgNJtt3DpxNiVzKvF_ta708xZvj9vuNUZFyoAg@mail.gmail.com> (raw)
In-Reply-To: <d3411db9-1d02-d493-72e6-e85625f849a9@denx.de>

On Mon, Sep 5, 2016 at 1:24 PM, Marek Vasut <marex@denx.de> wrote:
> On 09/05/2016 06:22 PM, Otavio Salvador wrote:
>> On Mon, Sep 5, 2016 at 1:16 PM, Marek Vasut <marex@denx.de> wrote:
>>> On 09/05/2016 03:51 PM, Otavio Salvador wrote:
>>>> On Mon, Sep 5, 2016 at 8:04 AM, Marek Vasut <marex@denx.de> wrote:
>>>>> Wouldn't that break some BSPs ? I factored out code from the u-boot.inc
>>>>> afterall.
>>>>
>>>> It will but I consider this fine for master as this clean up the
>>>> recipes and ensures people goes on the review process while upgrading
>>>> it.
>>>>
>>> The u-boot recipe mess would need _far_ more cleanup . If you don't mind
>>> me breaking all sorts of BSPs , I would gladly do far more intrusive
>>> changes. What do you say ?
>>
>> I would love to see the proposed patches.
>>
> That'd depend on whether they'd be NAK'd right away for breaking BSPs or
> not.

It will depends on the type of breakage and the benefits it puts on the table.

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750


  reply	other threads:[~2016-09-05 16:26 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-04 16:21 [PATCH 1/2] u-boot: Factor out common bits Marek Vasut
2016-09-04 16:21 ` [PATCH 2/2] u-boot: Update to 2016.07 release Marek Vasut
2016-09-14  8:48   ` Alexander Kanavin
2016-09-04 21:28 ` [PATCH 1/2] u-boot: Factor out common bits Richard Purdie
2016-09-04 21:49   ` Marek Vasut
2016-09-04 22:11     ` Richard Purdie
2016-09-04 22:23       ` Marek Vasut
2016-09-04 22:33         ` Marek Vasut
2016-09-05 11:02           ` Richard Purdie
2016-09-05 11:04             ` Marek Vasut
2016-09-05 13:51               ` Otavio Salvador
2016-09-05 16:16                 ` Marek Vasut
2016-09-05 16:22                   ` Otavio Salvador
2016-09-05 16:24                     ` Marek Vasut
2016-09-05 16:26                       ` Otavio Salvador [this message]
2016-09-05 19:33                         ` Richard Purdie
2016-09-05 19:47                           ` Marek Vasut
2016-09-05 19:52                             ` Otavio Salvador

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=CAP9ODKpB9ofyxgNJtt3DpxNiVzKvF_ta708xZvj9vuNUZFyoAg@mail.gmail.com \
    --to=otavio.salvador@ossystems.com.br \
    --cc=marex@denx.de \
    --cc=openembedded-core@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.