All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: Arnaud Pouliquen <arnaud.pouliquen@st.com>,
	alsa-devel@alsa-project.org, dri-devel@lists.freedesktop.org
Cc: kernel@stlinux.com, Takashi Iwai <tiwai@suse.de>,
	lgirdwood@gmail.com, Jyri Sarha <jsarha@ti.com>,
	David Airlie <airlied@linux.ie>,
	broonie@kernel.org, Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [PATCH 0/2] Generic HDMI codec: Add channel mapping control
Date: Sun, 11 Dec 2016 10:16:16 +0900	[thread overview]
Message-ID: <773cb1e2-cdd2-fee9-4d2b-fa6580b18b47@sakamocchi.jp> (raw)
In-Reply-To: <fffbf15e-ac95-a203-357f-01044614372a@st.com>

On Dec 9 2016 23:06, Arnaud Pouliquen wrote:
>> Anyway, we're mostly on the end of development for 4.10 cycle, and the
>> review process for new feature might be delay till 4.10-rc1 release, two
>> weeks later. During the weeks. bug fixes are preferable to be applied.
>
> Thank you for warning me. No problem for the delay, i fully understand
> that focus is on bug fixes.
> Notice that it is quite difficult for developers to find the best timing
> to address this kind of patch, as integration process is not always
> simple to follow... this probably come with experience.

ALSA is a development project for sound subsystem of Linux operating 
system, and our work is a part of Linux kernel. Therefore, it's better 
to follow generic behavior in Linux kernel development.

> So if i well understand your remark the best windows to integrate a
> feature for the version N+1, is to propose patch from N-rc1 tag.
> (expecting that patch-set is enough mature to be integrated in N+1...)

It's a better way if you're aware of maintainers' work and your task 
allows you to do things steadily.


Regards

Takashi Sakamoto

      reply	other threads:[~2016-12-11  1:16 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-08 16:37 [PATCH 0/2] Generic HDMI codec: Add channel mapping control Arnaud Pouliquen
2016-12-08 16:37 ` [PATCH 1/2] DRM: add help to get ELD speaker allocation Arnaud Pouliquen
2017-01-20 15:29   ` Applied "DRM: add help to get ELD speaker allocation" to the asoc tree Mark Brown
2016-12-08 16:37 ` [PATCH 2/2] ASoC: hdmi-codec: add channel mapping control Arnaud Pouliquen
2016-12-11  6:09   ` Takashi Sakamoto
2016-12-12  9:38     ` Arnaud Pouliquen
2016-12-12  9:54       ` Takashi Iwai
2016-12-12 12:12         ` Takashi Sakamoto
2016-12-12 12:55           ` Takashi Iwai
2016-12-12 14:05             ` Takashi Sakamoto
2016-12-12 15:12               ` Arnaud Pouliquen
2016-12-12 12:03       ` Takashi Sakamoto
2016-12-12 13:46         ` Arnaud Pouliquen
2016-12-13 13:23           ` Takashi Sakamoto
2016-12-13 13:58             ` Takashi Sakamoto
2016-12-13 14:49               ` Arnaud Pouliquen
2016-12-12 17:16         ` Arnaud Pouliquen
2016-12-08 20:52 ` [PATCH 0/2] Generic HDMI codec: Add " Takashi Sakamoto
2016-12-08 21:13   ` Takashi Sakamoto
2016-12-09 14:06     ` Arnaud Pouliquen
2016-12-11  1:16       ` Takashi Sakamoto [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=773cb1e2-cdd2-fee9-4d2b-fa6580b18b47@sakamocchi.jp \
    --to=o-takashi@sakamocchi.jp \
    --cc=airlied@linux.ie \
    --cc=alsa-devel@alsa-project.org \
    --cc=arnaud.pouliquen@st.com \
    --cc=broonie@kernel.org \
    --cc=daniel.vetter@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jsarha@ti.com \
    --cc=kernel@stlinux.com \
    --cc=lgirdwood@gmail.com \
    --cc=tiwai@suse.de \
    /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.