From: Nicolin Chen <nicoleotsuka@gmail.com>
To: Timur Tabi <timur@tabi.org>
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: Sat, 20 Sep 2014 11:07:38 -0700 [thread overview]
Message-ID: <20140920180738.GA6976@Asurada> (raw)
In-Reply-To: <541CC0FE.7050600@tabi.org>
On Fri, Sep 19, 2014 at 06:49:18PM -0500, Timur Tabi wrote:
> 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.
I see..
> However, let me look at Fabio's patches some more.
Yes, please.
prev parent reply other threads:[~2014-09-20 18:07 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
2014-09-20 18:07 ` Nicolin Chen [this message]
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=20140920180738.GA6976@Asurada \
--to=nicoleotsuka@gmail.com \
--cc=Fabio.Estevam@freescale.com \
--cc=Li.Xiubo@freescale.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=timur@tabi.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.