All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ernst Sjöstrand" <ernstp@gmail.com>
To: "Richard Röjfors" <richard.rojfors@gmail.com>
Cc: meta-freescale@yoctoproject.org
Subject: Re: Is there any point in keeping linux-imx.inc?
Date: Fri, 16 Dec 2016 13:27:42 +0100	[thread overview]
Message-ID: <CAD=4a=X5qpBYe8aQBd8CU4W2mk0UvANTqdLX7CNRwQVNL4OOYQ@mail.gmail.com> (raw)
In-Reply-To: <CAHB-PjkOOpeu1LdLh_AsMKqp7_y_zp2zwHgLm280e60tsJkoxg@mail.gmail.com>

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

Hi,

well I'm just saying that
linux-fscl-imx is using the exact same code (SHA1:s even I would say!) as
linux-imx,
it's the same code in http://git.freescale.com/git/cgit.cgi/imx/linux-imx
as in
https://github.com/Freescale/linux-fslc/tree/4.1-2.0.x-imx

So there's no point having any reference to http://git.freescale.com,
and linux-fscl-imx.* makes linux-imx.inc and linux-imx_4.1.15.bb redundant.

Regards
//Ernst

2016-12-16 11:57 GMT+01:00 Richard Röjfors <richard.rojfors@gmail.com>:

> On Fri, Dec 16, 2016 at 9:56 AM, Ernst Sjöstrand <ernstp@gmail.com> wrote:
> >
> >
> > I'm trying to figure out the IMX/FSCL kernel branches and realized that
> > linux-fscl-imx and linux-imx is the same thing.
>
> I don't realise the same thing.
>
> My view is:
> -fslc- gets more stuff merged from upstreams and additional fixes brought
> in.
>
> linux-imx is FSL/NXP's slowly progressing tree. Why are they not
> trying to go mainline instead?
>
> --Richard
>

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

  reply	other threads:[~2016-12-16 12:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-16  8:56 Is there any point in keeping linux-imx.inc? Ernst Sjöstrand
2016-12-16 10:57 ` Richard Röjfors
2016-12-16 12:27   ` Ernst Sjöstrand [this message]
2016-12-16 15:38     ` Gary Bisson
2016-12-16 21:39       ` Ernst Sjöstrand
2016-12-17 12:41         ` 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='CAD=4a=X5qpBYe8aQBd8CU4W2mk0UvANTqdLX7CNRwQVNL4OOYQ@mail.gmail.com' \
    --to=ernstp@gmail.com \
    --cc=meta-freescale@yoctoproject.org \
    --cc=richard.rojfors@gmail.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.