From: Ben Dooks <ben.dooks@codethink.co.uk>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Ben Dooks <ben@trinity.fluff.org>
Cc: Linux-ALSA <alsa-devel@alsa-project.org>,
Mark Brown <broonie@kernel.org>,
Kuninori Morimoto <kuninori.morimoto.gx@gmail.com>,
Simon <horms@verge.net.au>, Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: [PATCH] ASoC: rsnd: fixup SSI interrupts style of DeviceTree
Date: Mon, 02 Jun 2014 22:39:29 +0100 [thread overview]
Message-ID: <538CEF11.8020803@codethink.co.uk> (raw)
In-Reply-To: <87fvjrpl1g.wl%kuninori.morimoto.gx@renesas.com>
On 30/05/14 12:23, Kuninori Morimoto wrote:
>
> Hi Ben
>
>>> Hmm...
>>> This driver is still under developing.
>>> And it is very difficult for me to care about out-of-tree Linux.
>>
>> Ok, but we really need to keep in mind that the DT should be kept as
>> stable as possible. We may be out of tree at the moment, but we are
>> trying our best to keep track and feed back our work. This is not
>> helped if we have to do these changes when re-basing.
>>
>> In my view this change does not help the readability, as we now have
>> a large block of interrupts, where before we could easily work out
>> which interrupt was mapped to which SSI.
>
> OK.
> I thought that 1) current style was not good DT style
> 2) there is a chance to exchange it because upstream
> doesn't have user at this point.
> Can you accept if it can keep compatibility ?
I think the current method is the nicer, it keeps the descriptions
each ssi as close as possible to the ssi. So, in answer to #1 I
think it is the best.
In answer to #2, it would be nicer not to unless you have a good
reason to do this.
--
Ben Dooks http://www.codethink.co.uk/
Senior Engineer Codethink - Providing Genius
next prev parent reply other threads:[~2014-06-02 21:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-30 10:10 [PATCH] ASoC: rsnd: fixup SSI interrupts style of DeviceTree Kuninori Morimoto
2014-05-30 10:23 ` Ben Dooks
2014-05-30 10:43 ` Kuninori Morimoto
2014-05-30 10:53 ` Ben Dooks
2014-05-30 11:23 ` Kuninori Morimoto
2014-06-02 21:39 ` Ben Dooks [this message]
2014-06-02 23:52 ` Kuninori Morimoto
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=538CEF11.8020803@codethink.co.uk \
--to=ben.dooks@codethink.co.uk \
--cc=alsa-devel@alsa-project.org \
--cc=ben@trinity.fluff.org \
--cc=broonie@kernel.org \
--cc=horms@verge.net.au \
--cc=kuninori.morimoto.gx@gmail.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lgirdwood@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.