From: Mark Brown <broonie@kernel.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Jaroslav Kysela <perex@perex.cz>,
Baolin Wang <baolin.wang@linaro.org>,
Takashi Iwai <tiwai@suse.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Takashi Sakamoto <o-takashi@sakamocchi.jp>,
Ingo Molnar <mingo@kernel.org>,
SF Markus Elfring <elfring@users.sourceforge.net>,
Dan Carpenter <dan.carpenter@oracle.com>,
jeeja.kp@intel.com, Vinod Koul <vinod.koul@intel.com>,
Guneshwor Singh <guneshwor.o.singh@intel.com>,
subhransu.s.prusty@intel.com, Bhumika Goyal <bhumirks@gmail.com>,
gudishax.kranthikumar@intel.com, Naveen M <naveen.m@intel.com>,
hardik.t.shah@intel.com, Arvind Yadav <arvind.yadav.cs@gmail.com>,
Fabian Frederick <fabf@skynet.be>,
alsa-devel@alsa-project.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/8] Fix year 2038 issue for sound subsystem
Date: Wed, 25 Apr 2018 12:56:03 +0100 [thread overview]
Message-ID: <20180425115603.GE24769@sirena.org.uk> (raw)
In-Reply-To: <CAK8P3a1P8+DDmqSZquFVUn7C7F7+8M=Xft+wbY_H7a6ptfXJeA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 810 bytes --]
On Wed, Apr 25, 2018 at 01:26:23PM +0200, Arnd Bergmann wrote:
> On Wed, Apr 25, 2018 at 9:23 AM, Jaroslav Kysela <perex@perex.cz> wrote:
> > We have almost everything hidden in the alsa-lib code for the
> > applications and there is the protocol versioning, so we can detect the
> > changes easily and handle the new fields in the library.
> I think we are both misunderstanding each other here, let's try
> to work out what changes are required in alsa-lib. The idea of
> Baolin's patches that you can simply rebuild alsa-lib (or any other
> library using the alsa kernel interface, if any exist) against a new
> C library and still have working audio.
It's probably also worth mentioning that there are userspaces that don't
use alsa-lib at all, at least tinyalsa and salsa (if anyone still uses
salsa).
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-04-25 11:56 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-24 12:06 Baolin Wang
2018-04-24 12:06 ` [PATCH 1/8] ALSA: Replace timespec with timespec64 Baolin Wang
2018-04-26 8:15 ` kbuild test robot
2018-04-26 8:30 ` Arnd Bergmann
2018-04-26 8:41 ` Baolin Wang
2018-04-24 12:06 ` [PATCH 2/8] ALSA: Avoid using timespec for struct snd_timer_status Baolin Wang
2018-04-24 12:06 ` [PATCH 3/8] ALSA: Avoid using timespec for struct snd_ctl_elem_value Baolin Wang
2018-04-24 12:06 ` [PATCH 4/8] ALSA: Avoid using timespec for struct snd_pcm_status Baolin Wang
2018-04-26 9:20 ` kbuild test robot
2018-04-26 10:53 ` Baolin Wang
2018-04-26 12:50 ` Arnd Bergmann
2018-04-24 12:06 ` [PATCH 5/8] ALSA: Avoid using timespec for struct snd_rawmidi_status Baolin Wang
2018-04-24 12:06 ` [PATCH 6/8] ALSA: Avoid using timespec for struct snd_timer_tread Baolin Wang
2018-04-24 12:06 ` [PATCH 7/8] ALSA: move snd_pcm_ioctl_sync_ptr_compat into pcm_native.c Baolin Wang
2018-04-24 12:06 ` [PATCH 8/8] ALSA: add new 32-bit layout for snd_pcm_mmap_status/control Baolin Wang
2018-04-24 13:27 ` Arnd Bergmann
2018-04-26 3:07 ` kbuild test robot
2018-04-26 11:34 ` Arnd Bergmann
2018-04-26 6:20 ` kbuild test robot
2018-04-26 6:23 ` kbuild test robot
2018-04-26 11:25 ` kbuild test robot
2018-04-26 11:31 ` Arnd Bergmann
2018-04-26 12:11 ` Takashi Iwai
2018-04-26 15:14 ` Arnd Bergmann
2018-04-24 13:29 ` [PATCH 0/8] Fix year 2038 issue for sound subsystem Jaroslav Kysela
2018-04-24 13:37 ` Arnd Bergmann
2018-04-25 7:23 ` Jaroslav Kysela
2018-04-25 11:26 ` Arnd Bergmann
2018-04-25 11:56 ` Mark Brown [this message]
2018-04-24 13:29 ` Arnd Bergmann
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=20180425115603.GE24769@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=arnd@arndb.de \
--cc=arvind.yadav.cs@gmail.com \
--cc=baolin.wang@linaro.org \
--cc=bhumirks@gmail.com \
--cc=dan.carpenter@oracle.com \
--cc=elfring@users.sourceforge.net \
--cc=fabf@skynet.be \
--cc=gudishax.kranthikumar@intel.com \
--cc=guneshwor.o.singh@intel.com \
--cc=hardik.t.shah@intel.com \
--cc=jeeja.kp@intel.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=naveen.m@intel.com \
--cc=o-takashi@sakamocchi.jp \
--cc=perex@perex.cz \
--cc=subhransu.s.prusty@intel.com \
--cc=tiwai@suse.com \
--cc=vinod.koul@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®