From: Mark Brown <broonie@kernel.org>
To: Tomasz Figa <tomasz.figa@gmail.com>
Cc: Kukjin Kim <kgene@kernel.org>, 'Olof Johansson' <olof@lixom.net>,
'Padmavathi Venna' <padma.v@samsung.com>,
linux-samsung-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
padma.kvr@gmail.com, 'Tushar Behera' <tushar.behera@linaro.org>
Subject: Re: [PATCH V5] ARM: dts: Change i2s compatible string on exynos5250
Date: Fri, 16 Aug 2013 10:59:25 +0100 [thread overview]
Message-ID: <20130816095925.GK30073@sirena.org.uk> (raw)
In-Reply-To: <1812843.09c8C6xn0E@flatron>
[-- Attachment #1: Type: text/plain, Size: 452 bytes --]
On Fri, Aug 16, 2013 at 09:53:23AM +0200, Tomasz Figa wrote:
> Sorry, I don't think this is a good idea, unless you can force the IP team
> to release a version table containing version of _every_ IP for _every_
> released SoC, including those historical ones, like S3C24xx and S3C64xx.
> Of course such tables should be available publicly.
I don't think public availability is much of an issue here, the
datasheets are all NDAed anyway.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: broonie@kernel.org (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V5] ARM: dts: Change i2s compatible string on exynos5250
Date: Fri, 16 Aug 2013 10:59:25 +0100 [thread overview]
Message-ID: <20130816095925.GK30073@sirena.org.uk> (raw)
In-Reply-To: <1812843.09c8C6xn0E@flatron>
On Fri, Aug 16, 2013 at 09:53:23AM +0200, Tomasz Figa wrote:
> Sorry, I don't think this is a good idea, unless you can force the IP team
> to release a version table containing version of _every_ IP for _every_
> released SoC, including those historical ones, like S3C24xx and S3C64xx.
> Of course such tables should be available publicly.
I don't think public availability is much of an issue here, the
datasheets are all NDAed anyway.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20130816/122ba697/attachment.sig>
next prev parent reply other threads:[~2013-08-16 9:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-16 4:26 [PATCH V5] ARM: dts: Change i2s compatible string on exynos5250 Padmavathi Venna
2013-08-16 4:26 ` Padmavathi Venna
2013-08-16 4:48 ` Olof Johansson
2013-08-16 4:48 ` Olof Johansson
2013-08-16 5:43 ` Kukjin Kim
2013-08-16 5:43 ` Kukjin Kim
2013-08-16 7:53 ` Tomasz Figa
2013-08-16 7:53 ` Tomasz Figa
2013-08-16 9:59 ` Mark Brown [this message]
2013-08-16 9:59 ` Mark Brown
2013-08-18 18:05 ` Kukjin Kim
2013-08-18 18:05 ` Kukjin Kim
2013-08-16 7:48 ` Tomasz Figa
2013-08-16 7:48 ` Tomasz Figa
2013-08-16 10:06 ` Mark Brown
2013-08-16 10:06 ` Mark Brown
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=20130816095925.GK30073@sirena.org.uk \
--to=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kgene@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=olof@lixom.net \
--cc=padma.kvr@gmail.com \
--cc=padma.v@samsung.com \
--cc=tomasz.figa@gmail.com \
--cc=tushar.behera@linaro.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.