All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julia Lawall <julia.lawall@lip6.fr>
To: Joe Perches <joe@perches.com>
Cc: Mark Brown <broonie@kernel.org>,
	Liam Girdwood <lgirdwood@gmail.com>,
	kernel-janitors@vger.kernel.org, Jaroslav Kysela <perex@perex.cz>,
	Takashi Iwai <tiwai@suse.com>,
	alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/7] ASoC: constify snd_soc_ops structures
Date: Tue, 25 Oct 2016 10:39:59 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.10.1610251038570.3039@hadrien> (raw)
In-Reply-To: <1477382672.1998.5.camel@perches.com>



On Tue, 25 Oct 2016, Joe Perches wrote:

> On Tue, 2016-10-25 at 07:55 +0200, Julia Lawall wrote:
> > On Mon, 24 Oct 2016, Mark Brown wrote:
> > > On Sat, Oct 15, 2016 at 04:55:49PM +0200, Julia Lawall wrote:
> > > > ---
> > > >  sound/soc/generic/simple-card.c                 |    2 +-
> [...]
> > > >  sound/soc/mxs/mxs-sgtl5000.c                    |    2 +-
> > > >  16 files changed, 28 insertions(+), 28 deletions(-)
> > >
> > > You split out a few drivers as separate patches but not these
ones -
> > > what's special about these ones?
> >
>u > If it's preferred, I could send them all one file at a time, or when
the
> > maintainers are very similar just send one patch to all the maintainers.
>
> Whatever works.
> There's no single style appropriate for the entire kernel.

Actually, I was wondering for this kind of patch specifically.

thanks,
julia

WARNING: multiple messages have this Message-ID (diff)
From: Julia Lawall <julia.lawall@lip6.fr>
To: Joe Perches <joe@perches.com>
Cc: Mark Brown <broonie@kernel.org>,
	Liam Girdwood <lgirdwood@gmail.com>,
	kernel-janitors@vger.kernel.org, Jaroslav Kysela <perex@perex.cz>,
	Takashi Iwai <tiwai@suse.com>,
	alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/7] ASoC: constify snd_soc_ops structures
Date: Tue, 25 Oct 2016 08:39:59 +0000	[thread overview]
Message-ID: <alpine.DEB.2.10.1610251038570.3039@hadrien> (raw)
In-Reply-To: <1477382672.1998.5.camel@perches.com>



On Tue, 25 Oct 2016, Joe Perches wrote:

> On Tue, 2016-10-25 at 07:55 +0200, Julia Lawall wrote:
> > On Mon, 24 Oct 2016, Mark Brown wrote:
> > > On Sat, Oct 15, 2016 at 04:55:49PM +0200, Julia Lawall wrote:
> > > > ---
> > > >  sound/soc/generic/simple-card.c                 |    2 +-
> [...]
> > > >  sound/soc/mxs/mxs-sgtl5000.c                    |    2 +-
> > > >  16 files changed, 28 insertions(+), 28 deletions(-)
> > >
> > > You split out a few drivers as separate patches but not these
ones -
> > > what's special about these ones?
> >
>u > If it's preferred, I could send them all one file at a time, or when
the
> > maintainers are very similar just send one patch to all the maintainers.
>
> Whatever works.
> There's no single style appropriate for the entire kernel.

Actually, I was wondering for this kind of patch specifically.

thanks,
julia

  reply	other threads:[~2016-10-25  8:40 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-15 14:55 [PATCH 0/7] constify snd_soc_ops structures Julia Lawall
2016-10-15 14:55 ` Julia Lawall
2016-10-15 14:55 ` Julia Lawall
2016-10-15 14:55 ` [PATCH 1/7] ASoC: intel: broadwell: " Julia Lawall
2016-10-15 14:55   ` Julia Lawall
2016-10-17  2:22   ` [alsa-devel] " Keyon Jie
2016-10-17  2:22     ` Keyon Jie
2016-10-24 18:01   ` Applied "ASoC: intel: broadwell: constify snd_soc_ops structures" to the asoc tree Mark Brown
2016-10-24 18:01     ` Mark Brown
2016-10-24 18:01     ` Mark Brown
2016-10-15 14:55 ` [PATCH 2/7] ASoC: atmel_wm8904: constify snd_soc_ops structures Julia Lawall
2016-10-15 14:55   ` Julia Lawall
2016-10-18  8:13   ` Nicolas Ferre
2016-10-18  8:13     ` Nicolas Ferre
2016-10-18  8:13     ` Nicolas Ferre
2016-10-24 18:01   ` Applied "ASoC: atmel_wm8904: constify snd_soc_ops structures" to the asoc tree Mark Brown
2016-10-24 18:01     ` Mark Brown
2016-10-24 18:01     ` Mark Brown
2016-10-15 14:55 ` [PATCH 3/7] ASoC: rockchip: constify snd_soc_ops structures Julia Lawall
2016-10-15 14:55   ` Julia Lawall
2016-10-15 14:55   ` Julia Lawall
2016-10-24 18:01   ` Applied "ASoC: rockchip: constify snd_soc_ops structures" to the asoc tree Mark Brown
2016-10-24 18:01     ` Mark Brown
2016-10-24 18:01     ` Mark Brown
2016-10-24 18:01     ` Mark Brown
2016-10-24 18:01     ` Mark Brown
2016-10-15 14:55 ` [PATCH 4/7] ASoC: qcom: storm: constify snd_soc_ops structures Julia Lawall
2016-10-15 14:55   ` Julia Lawall
2016-10-24 18:01   ` Applied "ASoC: qcom: storm: constify snd_soc_ops structures" to the asoc tree Mark Brown
2016-10-24 18:01     ` Mark Brown
2016-10-24 18:01     ` Mark Brown
2016-10-15 14:55 ` [PATCH 5/7] ASoC: constify snd_soc_ops structures Julia Lawall
2016-10-15 14:55   ` Julia Lawall
2016-10-24 17:34   ` Mark Brown
2016-10-24 17:34     ` Mark Brown
2016-10-24 19:48     ` Julia Lawall
2016-10-24 19:48       ` Julia Lawall
2016-10-25  5:55     ` Julia Lawall
2016-10-25  5:55       ` Julia Lawall
2016-10-25  8:04       ` Joe Perches
2016-10-25  8:04         ` Joe Perches
2016-10-25  8:39         ` Julia Lawall [this message]
2016-10-25  8:39           ` Julia Lawall
2016-10-25 14:08       ` Mark Brown
2016-10-25 14:08         ` Mark Brown
2016-10-15 14:55 ` [PATCH 6/7] " Julia Lawall
2016-10-15 14:55   ` Julia Lawall
2016-10-24 18:01   ` Applied "ASoC: constify snd_soc_ops structures" to the asoc tree Mark Brown
2016-10-24 18:01     ` Mark Brown
2016-10-24 18:01     ` Mark Brown
2016-10-15 14:55 ` [PATCH 7/7] ASoC: tegra: constify snd_soc_ops structures Julia Lawall
2016-10-15 14:55   ` Julia Lawall
     [not found]   ` <1476543351-17858-8-git-send-email-Julia.Lawall-L2FTfq7BK8M@public.gmane.org>
2016-10-24 18:01     ` Applied "ASoC: tegra: constify snd_soc_ops structures" to the asoc tree Mark Brown
2016-10-24 18:01       ` Mark Brown
2016-10-24 18:01       ` Mark Brown
2016-10-24 18:01       ` 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=alpine.DEB.2.10.1610251038570.3039@hadrien \
    --to=julia.lawall@lip6.fr \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=joe@perches.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=tiwai@suse.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.