Received: by 10.223.176.46 with SMTP id f43csp4425099wra; Tue, 23 Jan 2018 09:14:38 -0800 (PST) X-Google-Smtp-Source: AH8x227sP4ACMsWPHimdEN6Vj4LM3bgIDyNHOhPYAWGocjgjWidvHf+k6JBNWqVCaIubOJ8qM1O3 X-Received: by 10.107.128.154 with SMTP id k26mr4745016ioi.291.1516727678537; Tue, 23 Jan 2018 09:14:38 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1516727678; cv=none; d=google.com; s=arc-20160816; b=yc82SI8+KlzvDYYczTAD4JfirtmR+w+BodF02xg18D2GC9EVM1M1WOFPzQE8qED6bi ly5rbdbsC+dVocccV2W/zhJNa7a9Im2aEoJuBPVAXJ51u/xnbkF0vgnekqpkJMfuFHwZ 7wDROOccF1LjWZHl2BqK0tC+WereddYC4UYsji9/rEdH/DyKf0pqEZ6iiGQhnBZgLRdn xCf8iCzdCjtymCl0rY0Rg6PcRKJWpFuSp2x7mc3T/FCwxj/z6prysZn3bjEZbJGAxfpM NNDevLovSO1MPrwZlG0HEwTpQZq14EYZcsl8aFXQ6ITHA75rdVGyMg1Cz5VXdj8oojfU N7/A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-transfer-encoding:content-disposition:mime-version :references:message-id:subject:cc:to:from:date :arc-authentication-results; bh=RSQstBHkv8tk6V/yC6quzoXE6I3cd9fW3a8HU22Gbkw=; b=Cj+THi7XWoM2jHstZOrgyh9IYiBZ/4cFrgmpexMmh8d615H3JAyiHjoe8vlFWBAEcd qzLYEfElbPwz9B8kAJqxTH0Ne4c/WquZaQTiF5G9iwAzY+K/SyxAutxPH3vp4UZUKu4S UQ/ZZiyXkpEfTSRmyfZmj/nanKR7kqp2sYLD2IRQMf53oFVblt14bjWGIMePOuFEaSZ0 63Pl5X2qbKyiiusiHi6nCwXuEI8PDEkHMAvfv6/07T44jTKJzCL32y6agBW3CCh3nQXk TsxGgl41JduojSgMSD4R8hnyX+nk1FA8D0aji2KFcoQCG9DhRTZWrzvJ7TsSf7+aFmLi xSWw== 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 w129si8878787itd.71.2018.01.23.09.14.25; Tue, 23 Jan 2018 09:14:38 -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 S1751547AbeAWROB (ORCPT + 99 others); Tue, 23 Jan 2018 12:14:01 -0500 Received: from eddie.linux-mips.org ([148.251.95.138]:49322 "EHLO cvs.linux-mips.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751259AbeAWRN6 (ORCPT ); Tue, 23 Jan 2018 12:13:58 -0500 Received: (from localhost user: 'ladis' uid#1021 fake: STDIN (ladis@eddie.linux-mips.org)) by eddie.linux-mips.org id S23992391AbeAWRNy3bCdl (ORCPT + 2 others); Tue, 23 Jan 2018 18:13:54 +0100 Date: Tue, 23 Jan 2018 18:13:47 +0100 From: Ladislav Michl To: Lee Jones Cc: SF Markus Elfring , linux-omap@vger.kernel.org, LKML , kernel-janitors@vger.kernel.org, Tony Lindgren Subject: Re: [3/3] mfd/omap-usb-tll: Return an error code only as a constant in usbtll_omap_probe() Message-ID: <20180123171346.GA5296@lenoch> References: <367e77d8-3a65-2c12-5e79-75a626b65f41@users.sourceforge.net> <20180122155057.7eiu53l6xjls6uga@dell> <20180123130440.lgfoeq4rzsa2e4gk@dell> <20180123150408.tljqon24yhbartkw@dell> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20180123150408.tljqon24yhbartkw@dell> User-Agent: Mutt/1.9.2 (2017-12-15) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Lee, On Tue, Jan 23, 2018 at 03:04:08PM +0000, Lee Jones wrote: > On Tue, 23 Jan 2018, SF Markus Elfring wrote: > > > >> Applied, thanks. > > > > > > This patch does not apply. > > > > > > Please rebase and resend. > > > > Did you notice that this update suggestion could eventually be superseded > > by the software change “[PATCH v2] mfd: omap-usb-tll: Allocate driver data at once”? > > How would I? It looks like a completely different patch. > > In future, please either reply to the original patch with the > follow-up patch OR reply to the original patch to say it's been > superseded, and provide an indication of which patch superseded it. this is my fault. I should point out that v2 superseded also other patches in the serie (see previous discussion, how that happened). I'm sorry for this. > > https://lkml.org/lkml/2018/1/23/277 > > https://patchwork.kernel.org/patch/10165339/ > > https://lkml.kernel.org/r/<20180115202505.GA2628@lenoch> > > -- > Lee Jones > Linaro Services Technical Lead > Linaro.org │ Open source software for ARM SoCs > Follow Linaro: Facebook | Twitter | Blog