Received: by 2002:ac0:8845:0:0:0:0:0 with SMTP id g63csp1014345img; Tue, 26 Feb 2019 12:32:28 -0800 (PST) X-Google-Smtp-Source: AHgI3IbuPXC6/0armGZG7ojBrQMdzDk1wrBntSNfxL+QjKJ2UbtATS338XJuw9yPF+ATBiLmMyQl X-Received: by 2002:a65:6491:: with SMTP id e17mr26007194pgv.418.1551213148003; Tue, 26 Feb 2019 12:32:28 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1551213147; cv=none; d=google.com; s=arc-20160816; b=J0LazaDdNvNU7FN+rjdjxg9p3M2ecjov+N7i5+7zZZAh/wJ9AJuuEajBMKLxru2Ckn 5/fapgwOZy/IRBs5YBxjmSS99m6WQ4LIfgJdKweGt9DPQ6nIhwhvf5L+bKbg3XPsYXYS yUdBI37zledL89mq6YB9eMensAfMIT8W7Uolqdpf8hVbmLQ33AkODs5RRKzGLjYsbcOK JxTjnGX03fQyN4Zp8KShf/WFd0Z0sXkijeJE1fZUEXihwRHLuFrF5LnGgcYzAcd3A4aG No1Q3BglUjqHYBk5vSQfGsHPPnOWp8Ptudr3P+bL/02NscmEA9RmovEMgIMFV/X5q2A/ 2DkQ== 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:mime-version :references:in-reply-to:from:subject:cc:to:message-id:date; bh=6cxPU4MtLHlwjzGM/qmi3XxY2i4iNKJyETPslivZRww=; b=vrlOvlQNVeySbKWX+4dUnWDagYvtLJKofY35nOpqoLQ7GEhXMzWRIxG/qHeCmhohhq 4Ttl/Fdv4zpypn2qosd2pBczxVyIWOvsi/GXvTAAsD2Ck2XGvrZfEbMFwA5bvt0r3QrM +al5/zj3LLfteaBkkNJMTsGSnBda4ztEMUK6y3Yskb+rOg6xgW+pPJwNmOojh1or9U/c +yglniGDfkUsdb7gFACptltSUy5ID0qx7qm0LVd862Vh3UXEyIuKc5WbdQObRJRzY0EP SMZixDnE/mF55c1hhhzmINtmlQQD2nbAvyTmwjZ1ewLBT0006rHiDGPRKIFEeHotRWYB d2Og== ARC-Authentication-Results: i=1; mx.google.com; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id x1si13059069plo.58.2019.02.26.12.32.11; Tue, 26 Feb 2019 12:32:27 -0800 (PST) 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; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729022AbfBZUbw (ORCPT + 99 others); Tue, 26 Feb 2019 15:31:52 -0500 Received: from shards.monkeyblade.net ([23.128.96.9]:59466 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727054AbfBZUbv (ORCPT ); Tue, 26 Feb 2019 15:31:51 -0500 Received: from localhost (unknown [IPv6:2601:601:9f80:35cd::bf5]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: davem-davemloft) by shards.monkeyblade.net (Postfix) with ESMTPSA id 0179314F24082; Tue, 26 Feb 2019 12:31:50 -0800 (PST) Date: Tue, 26 Feb 2019 12:31:48 -0800 (PST) Message-Id: <20190226.123148.2025630912555867905.davem@davemloft.net> To: leoyang.li@nxp.com Cc: ioana.ciornei@nxp.com, roy.pledge@nxp.com, ruxandra.radulescu@nxp.com, laurentiu.tudor@nxp.com, horia.geanta@nxp.com, brouer@redhat.com, netdev@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 0/3] soc: fsl: dpio: enable and configure cache stashing From: David Miller In-Reply-To: References: <20190224.220653.256212672271785631.davem@davemloft.net> X-Mailer: Mew version 6.8 on Emacs 26.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.5.12 (shards.monkeyblade.net [149.20.54.216]); Tue, 26 Feb 2019 12:31:51 -0800 (PST) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Li Yang Date: Tue, 26 Feb 2019 13:03:17 -0600 > On Mon, Feb 25, 2019 at 1:01 AM Ioana Ciornei wrote: >> >> > Subject: Re: [PATCH 0/3] soc: fsl: dpio: enable and configure cache stashing >> > >> > From: Ioana Ciornei >> > Date: Sat, 23 Feb 2019 08:48:42 +0000 >> > >> > > The first two patches enable cache stashing and configure the core >> > > cluster destination per software portal while the third patch is the >> > > one configuring the amount of stashing on a queue. >> > >> > Should I merge this series in via my networking tree? >> >> Even though it would be really good to have this on the networking tree as soon as possible, I am afraid that patch 2/3 is not going to apply cleanly because it touches the same areas of code that some other patches on Leo's tree are. > > Hi David, > > What shall we do if we want to get this in the 5.1? Since the change > on the ethernet driver is pretty small, can I get your ACK on that > patch and merge the series through my tree? Sure. Acked-by: David S. Miller