Received: by 2002:ac0:de83:0:0:0:0:0 with SMTP id b3csp1445246imk; Mon, 4 Jul 2022 03:17:00 -0700 (PDT) X-Google-Smtp-Source: AGRyM1tHP0VqvhFdSXD/qnpZF9BeHLWa7aLy0xVk3ROQg99e4n4jHTjL2mHdNB+Z4suN828gLrmW X-Received: by 2002:a50:fb13:0:b0:435:90d1:19ca with SMTP id d19-20020a50fb13000000b0043590d119camr38270399edq.159.1656929820176; Mon, 04 Jul 2022 03:17:00 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1656929820; cv=none; d=google.com; s=arc-20160816; b=iW+Oiiqu7Bp+/6fO69l/ssbxzzBsPadZ3UfCHZc3ulSA0U4ksWkNERBLjCg1Mm7vOu ykvZYw5zb32hT+SHjNpb7GpyPo7rkYxV9O4/5kWbp4shGxHiQ5vexruj1s8BHJKebKLx +w4AqhHcPl2DdPV+Ic3mc0YnejnbrI2IBAppjnpwsGwilE1x0hk+a2+0TZzp0TLC9RaU 75xvRA7UWsJpGvGmyDb460piOQdz8OH67lYR5no3oLPjiXgBMR4dCMCAzY7iOqA4jTUw Q3EpzzRIh01/EqXlZUBoa/3VulA+n2U0JFC8S563NT1O/u/7mCFrqXukVDpM9FhJpPw2 IAAg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:references:message-id:in-reply-to :subject:cc:to:from:date:dkim-signature; bh=i/0dk0TW4mf5ohdzl9CDn7qKisy60D6tOokASh6xscE=; b=v5I4lIsbf5ggE/moDbQI8Kx5C/HKCwpXEU2zoHhw8bAo9pY6VO1OphP6eM2Jg91RaI VNWx8BrOQKI7lYXKBMsagTUdbpxsHKn81l/dtdw2IhMeN8pwXUXq506/kN4hdJXyYcSX mdHbzOOVTbigX4qJqGKaUSm6kfEwlEQHz9T4zIVn5VMylDY9iFHXddmYQlKxNwK5HFo4 XOHJS5ueI0GIw8xkTI9QLt0xmNgD3mbT9QxvZu1OwLChCbfBjeXlx/fGhHFu62XEI/1O UpPxFw808LX1P8fPwdl0NoGv9CUcPAcAsc30IqQNi87Ncz/xOeanhoLQFugRAWyVLCWz 997w== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=etdLVxMj; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id q20-20020a170906b29400b0072a63159448si9097383ejz.572.2022.07.04.03.16.35; Mon, 04 Jul 2022 03:17:00 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=etdLVxMj; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233849AbiGDJyJ (ORCPT + 99 others); Mon, 4 Jul 2022 05:54:09 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:47120 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229961AbiGDJyI (ORCPT ); Mon, 4 Jul 2022 05:54:08 -0400 Received: from mga17.intel.com (mga17.intel.com [192.55.52.151]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 411ABD12F; Mon, 4 Jul 2022 02:54:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1656928447; x=1688464447; h=date:from:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=lSh2EbbxhUgUat8Nrxc/d9fNoMjhwQg9R6qR3jGL+Ug=; b=etdLVxMjDFb/UKPjtQGcTIFJFAjSwOPkNzXL8uLd++krQc0HvSKUpAVL WaSf//U9/U223LyZcJ0gMTpv6au4MAdy2wgxb0SQbya7bKqrNR9l82DKO Ae5ZyD02T1Bq6IOXT7C5ZLND3zBgs6bxnu/WOkHad1Gh6ltRnx59I8xHt eSFb1XwNwW0YGJtqHRof36MocKARPSJcoLsIbzg1mCIQWh4PpUSW9NPTW rjS3+So51Dv+0UUT0OKKboYPO0CCSY7kajBmoJQJfQE0WKD+DLleUHSqY dgYc0c9hh+h/NjVr1+MBPDIzZKHy3EeX+pNHj7fxnyf/fsKxNjDB1LXw4 A==; X-IronPort-AV: E=McAfee;i="6400,9594,10397"; a="263511023" X-IronPort-AV: E=Sophos;i="5.92,243,1650956400"; d="scan'208";a="263511023" Received: from fmsmga008.fm.intel.com ([10.253.24.58]) by fmsmga107.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 04 Jul 2022 02:54:07 -0700 X-IronPort-AV: E=Sophos;i="5.92,243,1650956400"; d="scan'208";a="649512912" Received: from bclindho-mobl.ger.corp.intel.com ([10.252.49.27]) by fmsmga008-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 04 Jul 2022 02:54:01 -0700 Date: Mon, 4 Jul 2022 12:53:58 +0300 (EEST) From: =?ISO-8859-15?Q?Ilpo_J=E4rvinen?= To: Lino Sanfilippo cc: Andy Shevchenko , Greg Kroah-Hartman , Jiri Slaby , Rob Herring , Krzysztof Kozlowski , Andy Shevchenko , Vladimir Zapolskiy , linux-arm Mailing List , devicetree , "open list:SERIAL DRIVERS" , Linux Kernel Mailing List , Lukas Wunner , p.rosenberger@kunbus.com, Lino Sanfilippo Subject: Re: [PATCH v2 7/9] serial: ar933x: Fix check for RS485 support In-Reply-To: Message-ID: References: <20220703170039.2058202-1-LinoSanfilippo@gmx.de> <20220703170039.2058202-8-LinoSanfilippo@gmx.de> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Spam-Status: No, score=-5.0 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_EF,RCVD_IN_DNSWL_MED,SPF_HELO_NONE, SPF_NONE,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 4 Jul 2022, Lino Sanfilippo wrote: > On 03.07.22 20:39, Andy Shevchenko wrote: > > On Sun, Jul 3, 2022 at 7:02 PM Lino Sanfilippo wrote: > >> > >> From: Lino Sanfilippo > >> > >> Without an RTS GPIO RS485 is not possible so disable the support > >> regardless of whether RS485 is enabled at boottime or not. Also remove the > > > > boot time > > > >> now superfluous check for the RTS GPIO in ar933x_config_rs485(). > >> > >> Fixes: e849145e1fdd ("serial: ar933x: Fill in rs485_supported") > > > > Is it an independent fix? If so, it should be the first patch in the > > series, otherwise if it's dependent on something from previous patches > > you need to mark all of them as a fix. > > > > The fix is independent, patch 8 depends on the fix however. I was not > aware of this fixes-first rule for series with patches that are independent > from each other. I will change the order accordingly in the next version of the series. While at it, you could separate just the fix to own patch and the ->rs485_config() cleanup to own patch (or move it all to patch 8). Not that this fix is expected to go anywhere else besides tty-next. -- i.