From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andy Shevchenko Subject: Re: Designware patches Date: Sun, 19 Jun 2016 20:16:31 +0300 Message-ID: <1466356591.30123.167.camel@linux.intel.com> References: <20160619170800.GB2933@tetsubishi> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Return-path: Received: from mga01.intel.com ([192.55.52.88]:41810 "EHLO mga01.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751454AbcFSRQu (ORCPT ); Sun, 19 Jun 2016 13:16:50 -0400 In-Reply-To: <20160619170800.GB2933@tetsubishi> Sender: linux-i2c-owner@vger.kernel.org List-Id: linux-i2c@vger.kernel.org To: Wolfram Sang , linux-i2c@vger.kernel.org, Jarkko Nikula Cc: Mika Westerberg , Ulf Hansson On Sun, 2016-06-19 at 19:08 +0200, Wolfram Sang wrote: > Hi Jarkko and everyone, > > there are a bunch of patches pending for the designware driver and I > am > a bit lost e.g. if a series is superseding another series by taking a > different approach, if there are contradicting series, or what would > be > a good order to pick them. May I ask for some assistance here? The > list > of patches can be seen here: > > http://patchwork.ozlabs.org/project/linux- > i2c/list/?submitter=&state=&q=design&archive=&delegate= Wow, there is a couple from ancient times! > > I'd suggest I apply patches whenever they get acked- or rev-by tags. > Or > drop them when someone says so in a reply to the patch. Does that > sound > like a plan? My patches can't be applied since it touches PCI part. -- Andy Shevchenko Intel Finland Oy