All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Lee Jones <lee.jones@linaro.org>
Cc: devicetree@vger.kernel.org, alsa-devel@alsa-project.org,
	Samuel Ortiz <sameo@linux.intel.com>,
	Alexander Shiyan <shc_work@mail.ru>, Takashi Iwai <tiwai@suse.de>,
	Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: [PATCH] ASoC: mc13783: Add devicetree support
Date: Fri, 2 May 2014 18:49:34 -0700	[thread overview]
Message-ID: <20140503014934.GB22111@sirena.org.uk> (raw)
In-Reply-To: <20140502080944.GA5206@lee--X1>


[-- Attachment #1.1: Type: text/plain, Size: 988 bytes --]

On Fri, May 02, 2014 at 09:09:44AM +0100, Lee Jones wrote:
> On Thu, 01 May 2014, Mark Brown wrote:

> > Sure, but I didn't see an urgent need for that immediately so I just
> > went ahead - the ack usually means that it's OK to apply.

> Hmm... I'm inclined to disagree.  The Ack is a marker that I'm okay
> with the changes, but the note after makes it pretty clear that the
> preference would be for the patch to be handled via an IB.

Right, and it's sitting on a separate branch which is (as we've seen)
very easy to add a tag to if it turns out to be needed.  This is what
all the small topic branches are there for, it makes it really easy to
cross merge, and obviously applying the patch on a branch is always
going to be the first step in creating an immutable branch.  It
certainly doesn't seem worth getting worried about.

Really, if you're not happy for something to be applied you probably
don't want to be acking it or you at least want to be really explicit
about things.

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



      reply	other threads:[~2014-05-03  1:49 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-26  6:57 [PATCH] ASoC: mc13783: Add devicetree support Alexander Shiyan
     [not found] ` <1398495423-2223-1-git-send-email-shc_work-JGs/UdohzUI@public.gmane.org>
2014-04-28 11:17   ` Lee Jones
2014-04-29 22:25   ` Mark Brown
     [not found]     ` <20140429222522.GS15125-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2014-04-30 14:08       ` Lee Jones
2014-04-30 14:11         ` Alexander Shiyan
     [not found]           ` <1398867073.695596467-rKA3owyty39sdVUOrk1QfQ@public.gmane.org>
2014-04-30 14:17             ` Lee Jones
2014-04-30 14:20               ` Alexander Shiyan
     [not found]                 ` <1398867618.574635813-rKA3owyty39sdVUOrk1QfQ@public.gmane.org>
2014-04-30 14:24                   ` Lee Jones
2014-04-30 14:28                     ` Alexander Shiyan
     [not found]                       ` <1398868130.411182088-rKA3owyty39sdVUOrk1QfQ@public.gmane.org>
2014-04-30 14:33                         ` Lee Jones
2014-04-30 14:40                           ` Alexander Shiyan
     [not found]                             ` <1398868829.456957971-NHsxxyuixOdsdVUOrk1QfQ@public.gmane.org>
2014-04-30 14:46                               ` Lee Jones
2014-04-30 14:58                                 ` Alexander Shiyan
2014-04-30 18:06               ` Mark Brown
     [not found]                 ` <20140430180653.GB3245-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2014-04-30 18:12                   ` Alexander Shiyan
     [not found]                     ` <1398881556.141711961-JZ33oUlt0U9sdVUOrk1QfQ@public.gmane.org>
2014-04-30 18:23                       ` Mark Brown
2014-05-01  7:42                   ` Lee Jones
2014-05-01 15:06                     ` Mark Brown
     [not found]                       ` <20140501150653.GZ3245-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2014-05-02  8:09                         ` Lee Jones
2014-05-03  1:49                           ` Mark Brown [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=20140503014934.GB22111@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=devicetree@vger.kernel.org \
    --cc=lee.jones@linaro.org \
    --cc=lgirdwood@gmail.com \
    --cc=sameo@linux.intel.com \
    --cc=shc_work@mail.ru \
    --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.