Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp1343309ybl; Sat, 10 Aug 2019 01:47:40 -0700 (PDT) X-Google-Smtp-Source: APXvYqxiaMf1JU/2FXSfrKXIjgWRMueo52jWiVg0dFxgFDuxenlkFCynb+KPwAbiEXVT/H68g1df X-Received: by 2002:a63:4c46:: with SMTP id m6mr21908940pgl.59.1565426860678; Sat, 10 Aug 2019 01:47:40 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1565426860; cv=none; d=google.com; s=arc-20160816; b=ifkGSqZZHYiF3bmjVllhWecYHGLxXsLpIGl1Eni9dxRgEWjJpBR5mfCqAqmtXhWE1S Zum31d0DIyG5O8l717cfi2XsOFCnoXKj4tSn5/0tKlzUPpwnlIjVQ0S7adyR0q7HVoia 9nnQjYf3mGYBFlitkexSpCCkbVJHOHGXG2OhqkiQejaVA9HqnGAZOub0JMKEZ83Swmcb J/2+Nv/len0Won9aT6NLVQ+usK2hD7HcWLpSULpVsbbN6Q+50gRkyqt6Qji8R4UMTwYV B6jjz/xi0ylh39DN+5y9Sin5ccnLtipe4/xwTLok+hrZfY1wmZPHYyccwvqspWrR4NWD brTA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:cc:to:subject :message-id:date:from:in-reply-to:references:mime-version :dkim-signature; bh=4N2DP4l2LpXR0ja9/QlgTCxk89cb9ApRuW6Y7KL7/QM=; b=HEtPgjVwchuphGSzJtqseSpb4A2UsDKuouYFKXp3GZcIOrV1ELz0UDfpiK2+8ufv+5 GC08ajDSXjRF7ydRGZ5hzNzVDApnWUq8c7fBEKGIbjJCDwLfe03W1KAobvkzvhR4tsGX 3LmrBCtWOPdwe+HzQf24G/jOMyAQtaGaoPrMXl/32kyHJdb9nglnxngbxCYV+Sfz2ITX /EbnV8js95Qyzc0TyjLIzVce/1/qYU/+DJCXVxjlocNp3bBXv0uhI0xWRMU0dY7PIOVK LRWiI9Cy7W+/UwsuCeyr+so7B0uzjLmczBpp9jNM2giz60rSZaVLEng8vW5EQj1tfq+X kVUg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=tFjHxYGs; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id y22si51364695plp.192.2019.08.10.01.47.25; Sat, 10 Aug 2019 01:47:40 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=tFjHxYGs; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726167AbfHJIpg (ORCPT + 99 others); Sat, 10 Aug 2019 04:45:36 -0400 Received: from mail-yb1-f194.google.com ([209.85.219.194]:46718 "EHLO mail-yb1-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725763AbfHJIpg (ORCPT ); Sat, 10 Aug 2019 04:45:36 -0400 Received: by mail-yb1-f194.google.com with SMTP id w196so8776570ybe.13; Sat, 10 Aug 2019 01:45:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=4N2DP4l2LpXR0ja9/QlgTCxk89cb9ApRuW6Y7KL7/QM=; b=tFjHxYGsshA6uhC4ZyO8gQA5CGqOklLRWWxRbDw74L/pi+b9ttnCV0SxJXzM1GWIvS F9rYQq1hBhIsaxKOI08ZyaGxkadwK312OhWil5n/UwwkKSmadnu/olRJh1TePylAFF1P 4ktVi+A2LsntpLrg+0r5GSjYQS6MoaBf5QcbFDhiWv7xJnDJnGAAFTUKJLcAwhajChY9 OyZKinHBA6UhYKPjOgT2ZHjTfw/jp+Njsc09CGDN2oGgyuMarC1b8lJbRsvnx9Il0N93 Q2aGmNoPzI8TmYFqu0vVtm5p9ZXDTei6QktQwpM52ZY7q5UI24kSvWdBmw3r3ttiWOfn PRfg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=4N2DP4l2LpXR0ja9/QlgTCxk89cb9ApRuW6Y7KL7/QM=; b=e0jFvHJrt/Ei0HgtWqj5//2isnrkp+vyAXTitNstIFCReo/eYytWQlBOU+Qh3Eapj2 6dDvh3A1IjSzqsiQYeloC6Ryo3QimUeNiQOTBiTiOBsOUIfg+bzhrWKr6Xyym3vIcmuT Pze5YCJ/shKbWejTHE8o5PGJm3TEPI7Sh5UVBP5t152VDcEubxTDjoyJRF5PIyW0Owq2 pouUXcKgac/psoQ6mYFfgcDg97iLyVgzebtkqf5BG68JHD/xaU6RfRst67p6yr4fSEtx gYrzcRD6lF3tS+aibUmHP7neV7IzCmvHllivGgNvRNXHXVtDbDSu0QyJYsnXKFe3eILj f7gg== X-Gm-Message-State: APjAAAULcyvAW4L7qXx95o9aAJXVAKaDBia8rDbMUM+mi2t30pbRlpur QwaAWjTCvj2X4zwt+RxT73+8vY74dQrJ9mkIbUc= X-Received: by 2002:a25:9109:: with SMTP id v9mr17429940ybl.396.1565426734980; Sat, 10 Aug 2019 01:45:34 -0700 (PDT) MIME-Version: 1.0 References: <20190527200627.8635-1-peron.clem@gmail.com> <20190715193842.GC4503@sirena.org.uk> In-Reply-To: <20190715193842.GC4503@sirena.org.uk> From: =?UTF-8?B?Q2zDqW1lbnQgUMOpcm9u?= Date: Sat, 10 Aug 2019 10:45:23 +0200 Message-ID: Subject: Re: [PATCH v4 0/7] Allwinner H6 SPDIF support To: Mark Brown , Maxime Ripard Cc: Liam Girdwood , Jaroslav Kysela , Takashi Iwai , Linux-ALSA , devicetree , linux-arm-kernel , Mark Rutland , Rob Herring , Chen-Yu Tsai , linux-kernel , linux-sunxi , Jagan Teki Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, Sorry, I just discovered that the ASoC patches have been merged into the broonie and linus tree in 5.3. I'm still quite new in the sending of patches to the Kernel but souldn't be a ack or a mail sent to warn the sender when the series are accepted? Should 5/6/7 patches be picked by Sunxi maintainer? Thanks, Cl=C3=A9ment On Mon, 15 Jul 2019 at 21:38, Mark Brown wrote: > > On Mon, Jul 15, 2019 at 09:21:01PM +0200, Cl=C3=A9ment P=C3=A9ron wrote: > > Hi, > > > > I'm missing ACK from ASoC Maintainers patch 2-3-4. > > > > It's really small paches, if you could have a look at it. > > Please don't send content free pings and 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. If there have been > review comments then people may be waiting for those to be addressed. > > Sending content free pings adds to the mail volume (if they are seen at > all) which is often the problem and since they can't be reviewed > directly if something has gone wrong you'll have to resend the patches > anyway, so sending again is generally a better approach though there are > some other maintainers who like them - if in doubt look at how patches > for the subsystem are normally handled.