All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: tiwai@suse.de, vinod.koul@intel.com, alsa-devel@alsa-project.org
Subject: Re: [PATCH RESEND 0/3] Intel-rt5670 updates
Date: Wed, 20 Sep 2017 16:08:33 +0100	[thread overview]
Message-ID: <20170920150833.u72i3rqrjq3xwseu@sirena.co.uk> (raw)
In-Reply-To: <1d9e0181-edeb-e3e3-0094-9f66083a223c@linux.intel.com>


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

On Wed, Sep 20, 2017 at 08:17:09AM -0500, Pierre-Louis Bossart wrote:
> On 9/20/17 5:41 AM, Mark Brown wrote:

> > Please allow a reasonable time for review.  People get busy, go on
> > holiday, attend conferences and so on so unless there is some reason for
> > urgency (like critical bug fixes) please allow at least a couple of
> > weeks for review.  It's been less than two weeks, including both the
> > merge window and LPC...

> Sure. it's just that you already merged a number of patches sent *after*
> this batch and they aren't queued in your topic/intel branch either.

You really shouldn't expect things to be handled FIFO.

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

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



      reply	other threads:[~2017-09-20 15:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-20  0:34 [PATCH RESEND 0/3] Intel-rt5670 updates Pierre-Louis Bossart
2017-09-20  0:34 ` [PATCH RESEND 1/3] ASoC: rt5670: refactor DMI quirks and fix Dell Venue settings Pierre-Louis Bossart
2017-09-20  0:34 ` [PATCH RESEND 2/3] ASoC: Intel: cht_bsw_rt5672: use actual HID in suspend/resume Pierre-Louis Bossart
2017-09-20  0:34 ` [PATCH RESEND 3/3] ASoC: Intel: cht_bsw_rt5672: fix card name Pierre-Louis Bossart
2017-09-20 10:41 ` [PATCH RESEND 0/3] Intel-rt5670 updates Mark Brown
2017-09-20 13:17   ` Pierre-Louis Bossart
2017-09-20 15:08     ` 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=20170920150833.u72i3rqrjq3xwseu@sirena.co.uk \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=tiwai@suse.de \
    --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 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.