All of lore.kernel.org
 help / color / mirror / Atom feed
From: Timur Tabi <timur@tabi.org>
To: Nicolin Chen <nicoleotsuka@gmail.com>
Cc: "Fabio.Estevam@freescale.com" <Fabio.Estevam@freescale.com>,
	"Li.Xiubo@freescale.com" <Li.Xiubo@freescale.com>,
	"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	"broonie@kernel.org" <broonie@kernel.org>
Subject: Re: [PATCH] ASoC: fsl_ssi: Remove unneeded 'i2s-slave' property
Date: Fri, 19 Sep 2014 18:49:18 -0500	[thread overview]
Message-ID: <541CC0FE.7050600@tabi.org> (raw)
In-Reply-To: <20140919172438.GA1736@Asurada>

Nicolin Chen wrote:
> I thought only the backward compatibility for DT is demanded.....

I have higher standards :-)

> But I still don't get why people would use new DT without updating
> kernel. It's pretty fair to use old DT with newer kernel because
> they want bug-fix patches.

The device tree is shipped with the kernel, so some people say that 
backwards compatibility is not needed anywhere.  I think it's important 
to provide backwards compatibility both ways.

I generally prefer some kind of transition period, where you can use new 
or old kernel with a new or old device tree.

However, let me look at Fabio's patches some more.

  reply	other threads:[~2014-09-19 23:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1411063877-1552-1-git-send-email-fabio.estevam@freescale.com>
     [not found] ` <20140918183251.GE6432@Asurada>
     [not found]   ` <541B2678.8000401@tabi.org>
2014-09-18 18:46     ` [PATCH] ASoC: fsl_ssi: Remove unneeded 'i2s-slave' property Fabio.Estevam
2014-09-18 19:43       ` Nicolin Chen
2014-09-19  0:29         ` Timur Tabi
2014-09-19  4:17           ` Nicolin Chen
2014-09-19 12:51             ` Timur Tabi
2014-09-19 17:24               ` Nicolin Chen
2014-09-19 23:49                 ` Timur Tabi [this message]
2014-09-20 18:07                   ` Nicolin Chen

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=541CC0FE.7050600@tabi.org \
    --to=timur@tabi.org \
    --cc=Fabio.Estevam@freescale.com \
    --cc=Li.Xiubo@freescale.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=nicoleotsuka@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.