From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932710AbcAYMCF (ORCPT ); Mon, 25 Jan 2016 07:02:05 -0500 Received: from mga02.intel.com ([134.134.136.20]:62565 "EHLO mga02.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932219AbcAYMB5 (ORCPT ); Mon, 25 Jan 2016 07:01:57 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.22,344,1449561600"; d="scan'208";a="900616720" Date: Mon, 25 Jan 2016 17:35:41 +0530 From: Vinod Koul To: =?iso-8859-1?Q?M=E5ns_Rullg=E5rd?= Cc: Mark Brown , Viresh Kumar , Andy Shevchenko , linux-kernel@vger.kernel.org, dmaengine@vger.kernel.org, Rob Herring , Pawel Moll , Mark Rutland , Ian Campbell , Kumar Gala , Haavard Skinnemoen , Hans-Christian Egtvedt , Tejun Heo , Dan Williams , Daniel Mack , Haojian Zhuang , Robert Jarzmik , Greg Kroah-Hartman , Jiri Slaby , devicetree@vger.kernel.org, linux-ide@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-spi@vger.kernel.org, linux-serial@vger.kernel.org Subject: Re: [PATCH 03/15] dmaengine: dw: rename masters to reflect actual topology Message-ID: <20160125120541.GH11130@localhost> References: <1453663322-14474-1-git-send-email-mans@mansr.com> <1453663322-14474-4-git-send-email-mans@mansr.com> <20160124223629.GI6588@sirena.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Jan 24, 2016 at 10:38:57PM +0000, Måns Rullgård wrote: > Mark Brown writes: > > > On Sun, Jan 24, 2016 at 07:21:50PM +0000, Mans Rullgard wrote: > >> From: Andy Shevchenko > >> > >> The source and destination masters are reflecting buses or their layers to > >> where the different devices can be connected. The patch changes the master > >> names to reflect which one is related to which independently on the transfer > >> direction. > > > > This is patch 3 of a series but I don't have anything else in the > > series. What is going on with the rest of the series - what are the > > dependencies and so on? > > I give up. Seriously, this is impossible. If I don't include everybody > in the slightest way related to any patch in the series, I get > complaints that patches are missing. If I do, the lists reject it all > due to too many recipients. What the hell am I supposed to do? Right practice is to CC everyone in cover-letter and mention which subsystem this is intended to be merged thru and CC relevant folks on the patches. That gives everyone context and right attention and lesser noise on patches -- ~Vinod