All of lore.kernel.org
 help / color / mirror / Atom feed
From: Otavio Salvador <otavio@ossystems.com.br>
To: xxiao8 <xxiao8@fosiao.com>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: i.MX 3.10.31-1.1.0_beta release - community feedback requested
Date: Wed, 20 Aug 2014 16:41:07 -0300	[thread overview]
Message-ID: <CAP9ODKpLN0jpwS4F2_GHjU4RTk5hnciZidk+LQAPtfMSYC-03A@mail.gmail.com> (raw)
In-Reply-To: <53F4E509.1070509@fosiao.com>

On Wed, Aug 20, 2014 at 3:12 PM, xxiao8 <xxiao8@fosiao.com> wrote:
> I would have hoped Freescale stuck with 3.10.17 instead of 3.10.31 to make
> 3.10.17 solid in the first place, unless 3.10.31 brought in something that
> is a must-to-have I don't see the reason to make things unnecessarily
> complicated. Customer can always patch to whatever 3.10.x when they want to
> as those incremental patches are normally independent of Freescale's code
> changes. Not to mention nowadays it's 3.10.53 now.
>
> Backport 3.10.31-beta to 3.10.17 and make this a gold release kernel is the
> best option in my opinion. I again don't see the point to diverge at all.

Please, if you want your vote to be considered do it in the another
thread and inform your full name (as your name is not in from).

-- 
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:[~2014-08-20 19:41 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-20 18:12 i.MX 3.10.31-1.1.0_beta release - community feedback requested xxiao8
2014-08-20 19:41 ` Otavio Salvador [this message]
2014-08-20 23:11   ` xxiao8
     [not found] <b82299f1e1374ceea2a54dc92a7edc83@DM2PR0301MB0701.namprd03.prod.outlook.com>
     [not found] ` <8f1e8166115a4a4381ded78a5536c001@BY2PR03MB379.namprd03.prod.outlook.com>
2014-08-18 15:32   ` Lauren Post
2014-08-18 15:54     ` Alfonso Tamés
2014-08-18 17:28       ` Eric Nelson
2014-08-18 19:35       ` Carlos Rafael Giani
2014-08-18 21:14         ` John Weber
2014-08-19  0:34         ` Alfonso Tamés
2014-08-19  2:32     ` Sébastien Taylor
2014-08-19  6:56       ` Carlos Rafael Giani
2014-08-19 13:59     ` Otavio Salvador
2014-08-19 15:55       ` Eric Nelson
2014-08-19 16:01         ` Carlos Rafael Giani
2014-08-19 16:22           ` Eric Nelson
2014-08-19 17:21             ` Otavio Salvador
2014-08-19 18:25               ` Eric Nelson
2014-08-19 17:24         ` Otavio Salvador
2014-08-19 18:44           ` Eric Nelson
2014-08-19 19:23             ` Lauren Post
2014-08-19 20:00               ` Otavio Salvador
2014-08-19 20:13                 ` Eric Bénard
2014-08-19 20:20                 ` John Weber
2014-08-20 13:31                   ` Daiane Angolini
2014-08-20 17:32                 ` Sébastien Taylor
2014-08-20 22:53     ` Alexander Holler
2014-08-20 23:04       ` Lauren Post
2014-08-20 23:29         ` Alexander Holler

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=CAP9ODKpLN0jpwS4F2_GHjU4RTk5hnciZidk+LQAPtfMSYC-03A@mail.gmail.com \
    --to=otavio@ossystems.com.br \
    --cc=meta-freescale@yoctoproject.org \
    --cc=xxiao8@fosiao.com \
    /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.