From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: alsa-devel@alsa-project.org, Jie Yang <yang.jie@linux.intel.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Vinod Koul <vkoul@kernel.org>, Mark Brown <broonie@kernel.org>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH v1] ASoC: Intel: Skylake: Switch to modern UUID API
Date: Mon, 7 Jan 2019 19:24:40 +0200 [thread overview]
Message-ID: <20190107172440.GX9170@smile.fi.intel.com> (raw)
In-Reply-To: <24418025-f870-8865-0fa2-6d443921ac02@linux.intel.com>
On Mon, Jan 07, 2019 at 10:33:21AM -0600, Pierre-Louis Bossart wrote:
> On 1/7/19 9:55 AM, Andy Shevchenko wrote:
> > On Mon, Jul 16, 2018 at 12:52:40PM +0300, Andy Shevchenko wrote:
> > > Switch the driver to use modern UUID API, i.e. guid_t type and
> > > accompanying functions, such as guid_equal().
> > >
> > Any comments on this?
>
> What is the motivation for this change, is this alignment to new APIs or
> that the legacy code will be removed?
The idea is to get rid of legacy API at some point. At least for now to
minimize its use in the kernel.
> I don't know enough about this API and I don't know if we can "prove" the
> changes are harmless, so my main concern is testing and backwards
> compatibility. This Skylake topology code is far from simple, I don't know
> if there's anyone that actually understands it and we already have some
> platforms where the mainline kernel doesn't seem to work due to obscure
> topology issues, so we might want to leave it alone. "If it ain't broke
> don't fix it" applies here.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2019-01-07 17:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-16 9:52 [PATCH v1] ASoC: Intel: Skylake: Switch to modern UUID API Andy Shevchenko
2019-01-07 15:55 ` Andy Shevchenko
2019-01-07 16:33 ` Pierre-Louis Bossart
2019-01-07 17:24 ` Andy Shevchenko [this message]
2019-01-21 8:53 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2019-06-19 15:02 Andy Shevchenko
2019-06-19 15:46 ` Pierre-Louis Bossart
2019-06-20 15:09 ` Andy Shevchenko
2019-06-21 3:41 ` Pierre-Louis Bossart
2019-06-24 8:51 ` Amadeusz Sławiński
2019-06-25 17:15 ` Andy Shevchenko
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=20190107172440.GX9170@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=hch@lst.de \
--cc=lgirdwood@gmail.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=vkoul@kernel.org \
--cc=yang.jie@linux.intel.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.