From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 2FEB7C433EF for ; Mon, 20 Jun 2022 10:40:01 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S240956AbiFTKj7 (ORCPT ); Mon, 20 Jun 2022 06:39:59 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:35764 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S240321AbiFTKj6 (ORCPT ); Mon, 20 Jun 2022 06:39:58 -0400 Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id DF7771403F; Mon, 20 Jun 2022 03:39:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1655721597; x=1687257597; h=date:from:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=LeRkSVDTT0Yb76jEsTjO7SM/+tjqpDRALlVCJn6AsZE=; b=hlWiyWIijUeKbsV1iMXUWXvcN9YykSsTY/qm/ufJKU5ByYHjLRVwO1Qb IsZhIh5xOpW9yOhM5Is6bp7gCVAQQbcS3BnU9iuzjQFzUN699hzWiyB50 eypIhhH1EoR/0mbWwVr6KMJlTv1FYmuc7AmNbKe7tX9hUDqvBUS7QTt1b oIW6WFmFCTdGzGMKKG55XjXkEt0PgLQ85mHnsNRfHMbK1FtAq02FpLe7V k1JWNlJrmFP+L+o0R5SmufE+Tpkju94wyHDDs5SzoeTc0wXSGjWTNQtEy hFKviBZyHdY+n58kW1eJITefCVTuM2ghY/IlmE067unjshJjS1LCahXzA A==; X-IronPort-AV: E=McAfee;i="6400,9594,10380"; a="279911587" X-IronPort-AV: E=Sophos;i="5.92,306,1650956400"; d="scan'208";a="279911587" Received: from fmsmga008.fm.intel.com ([10.253.24.58]) by fmsmga103.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 20 Jun 2022 03:39:57 -0700 X-IronPort-AV: E=Sophos;i="5.92,306,1650956400"; d="scan'208";a="643056879" Received: from lspinell-mobl1.ger.corp.intel.com ([10.251.215.169]) by fmsmga008-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 20 Jun 2022 03:39:54 -0700 Date: Mon, 20 Jun 2022 13:39:52 +0300 (EEST) From: =?ISO-8859-15?Q?Ilpo_J=E4rvinen?= To: linux-serial cc: Greg KH , Jiri Slaby , Neil Armstrong , Kevin Hilman , Jerome Brunet , Martin Blumenstingl , =?ISO-8859-15?Q?Andreas_F=E4rber?= , Manivannan Sadhasivam , LKML , linux-arm-kernel@lists.infradead.org, linux-amlogic@lists.infradead.org, linux-actions@lists.infradead.org, linux-unisoc@lists.infradead.org Subject: Re: [PATCH 5/6] cleanup: Use UART_XMIT_SIZE In-Reply-To: <20220620103408.37454-6-ilpo.jarvinen@linux.intel.com> Message-ID: References: <20220620103408.37454-1-ilpo.jarvinen@linux.intel.com> <20220620103408.37454-6-ilpo.jarvinen@linux.intel.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="8323329-1889180693-1655721597=:2433" Precedence: bulk List-ID: X-Mailing-List: linux-serial@vger.kernel.org This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --8323329-1889180693-1655721597=:2433 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT On Mon, 20 Jun 2022, Ilpo Järvinen wrote: > Both UART_XMIT_SIZE and SERIAL_XMIT_SIZE are defined. Make them all > UART_XMIT_SIZE. > > Signed-off-by: Ilpo Järvinen Grr, it seems that my internal naming to organize patches managed to leak into that summary on subject line. It should have been serial: obviously and I only noticed while git send-email was sending the bits out. :-( -- i. --8323329-1889180693-1655721597=:2433--