Message ID | 20230714091748.89681-1-andriy.shevchenko@linux.intel.com |
---|---|
Headers |
Return-Path: <linux-kernel-owner@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:a59:a6b2:0:b0:3e4:2afc:c1 with SMTP id c18csp2386827vqm; Fri, 14 Jul 2023 02:51:39 -0700 (PDT) X-Google-Smtp-Source: APBJJlExpo14NfaTJlKHQddqQPDA+Ql98K+5IQWsYcmgzho+TvhKenT8I9lY1tQ0421gVm4dPu0z X-Received: by 2002:a17:90a:2d8d:b0:262:e598:6046 with SMTP id p13-20020a17090a2d8d00b00262e5986046mr3884317pjd.28.1689328298816; Fri, 14 Jul 2023 02:51:38 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1689328298; cv=none; d=google.com; s=arc-20160816; b=zWa9/CekHfGi70U1E5vzZCJP6lGw6Eh7nVABjSYbStOtc+ukcRq8EIGElsrmo8LF2u zQ4It24FPHoFEkmFT+iQ+Xmol+ZyomVoklw2MACYEoZ8M0udFm9rMLoaauzzPZJulhB6 tlo7und6kZwErEpmYnv8UAwkMTkvffQF2sCr/P25v7IBnRI49+GzbwQbkBysySyUW6OF 64sSAxbxffgevDjkvq6m+CmZmX5+JCVqJAI9IJrK+lVcRl1x/UKlnyf2L77UXi/9ZCrd gOhJNm+FDRScuhUACpWcXwVSzaXbY9zSo3xdlsEr8saOkGREkldjMloNIzUkqE2LaAlj nefQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :message-id:date:subject:cc:to:from:dkim-signature; bh=zNBGhHqOmxXbijvoX99fAEAt3PEP+UKeadZ5LvCegWo=; fh=Qdz9kbAdPAfvhj/swQYvX2BMbB6C1mb3M8cD7Q9tvzc=; b=yFXc79L725wOQZ9iJPmC41MXLUa94TnIG8FziZQJuO4TCsTj9uNu0yPrEdb/mmzXaf HMaiStNEk+oG3iQ1JHOKpTA+9GYgERLILDefjGxL47LXh1Sz3Pr+iMU8wAdYI8bXvvM+ D5tbGRDmg3qPeTo9a0pEmFdgHDFXHhU4UcfTBzdRmOExH/r4zpcL3KdfJsaCrkvckHxY FTBEEbANnpydVYREWh8nsouDkMKCErJNCa7ht2kJxDNTGhVjmRAldI9CQUIIkm2dtz5k fU/GuqLKQMrl0IJN1/zm7VlE4RTDg0AcIeCn2L30lA+egvVMhpkLYcV8QCcE5dO2PTBp Hc/g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=ko0lO94N; 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: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id hv9-20020a17090ae40900b00263cfc97546si992256pjb.88.2023.07.14.02.51.25; Fri, 14 Jul 2023 02:51:38 -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=ko0lO94N; 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 S235685AbjGNJRx (ORCPT <rfc822;tebrre53rla2o@gmail.com> + 99 others); Fri, 14 Jul 2023 05:17:53 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:46868 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235043AbjGNJRt (ORCPT <rfc822;linux-kernel@vger.kernel.org>); Fri, 14 Jul 2023 05:17:49 -0400 Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 3B7C01FC9; Fri, 14 Jul 2023 02:17:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1689326269; x=1720862269; h=from:to:cc:subject:date:message-id:mime-version: content-transfer-encoding; bh=q4kBfKspO7sFkiacFnREqVjDod6DUMgGpY8AF3efGsw=; b=ko0lO94N4D06e07HpiXC+7ya2TFCPK7o5T1hN977B7wanHD0oZzsRRws tVvVX76pTeznZXISLXecTP0aqCvlsoOCYWsFXRG95rkLxUkPLmc4AwIjM PABd5Zb3i+nOFxFoU2epF4+yycBrjFns9LkEwVSTesfiJl7GXa2j7ACA8 E49YW44gRr3duRS5rIqB4xuNDHcsHdqnrb+TBSV5+KJrxEnrF+2F43CjB O4MOTjvO4qjrXANH5Hu8cjESEl3yu1j8x7iVOgD6SqPEkfDBbHTVMPpHU HFZKz+Y6zzdrUi7oYYjrPGB5AyJ8icsHk8o396gLxUP7y57QMANpKZeXr w==; X-IronPort-AV: E=McAfee;i="6600,9927,10770"; a="362897871" X-IronPort-AV: E=Sophos;i="6.01,204,1684825200"; d="scan'208";a="362897871" Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by fmsmga102.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 14 Jul 2023 02:17:46 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10770"; a="812357259" X-IronPort-AV: E=Sophos;i="6.01,204,1684825200"; d="scan'208";a="812357259" Received: from black.fi.intel.com ([10.237.72.28]) by FMSMGA003.fm.intel.com with ESMTP; 14 Jul 2023 02:17:44 -0700 Received: by black.fi.intel.com (Postfix, from userid 1003) id 74CA5379; Fri, 14 Jul 2023 12:17:50 +0300 (EEST) From: Andy Shevchenko <andriy.shevchenko@linux.intel.com> To: Mark Brown <broonie@kernel.org>, Andy Shevchenko <andriy.shevchenko@linux.intel.com>, linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org Cc: Sebastian Reichel <sebastian.reichel@collabora.com> Subject: [PATCH v4 0/4] spi: Header and core clean up and refactoring Date: Fri, 14 Jul 2023 12:17:44 +0300 Message-Id: <20230714091748.89681-1-andriy.shevchenko@linux.intel.com> X-Mailer: git-send-email 2.40.0.1.gaa8946217a0b MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-4.3 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,URIBL_BLOCKED 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: <linux-kernel.vger.kernel.org> X-Mailing-List: linux-kernel@vger.kernel.org X-getmail-retrieved-from-mailbox: INBOX X-GMAIL-THRID: 1771389110291188593 X-GMAIL-MSGID: 1771389110291188593 |
Series |
spi: Header and core clean up and refactoring
|
|
Message
Andy Shevchenko
July 14, 2023, 9:17 a.m. UTC
Various cleanups and refactorings of the SPI header and core parts united in a single series. It also touches drivers under SPI subsystem folder on the pure renaming purposes of some constants. No functional change intended (with some subtle shortcuts which are explained in the respective commit messages). Changelog v4: - dropped applied patches - added tag to patch 1 (Sebastian) v3: 20230711171756.86736-1-andriy.shevchenko@linux.intel.com Changelog v3: - dropped controversial used to be patches 3,4,8,10 (Mark) - amended many commit messages (Mark) - added tag to patch 1 (AngeloGioacchino) - split used to be patch 2 to patches 2 & 3 for better review (Mark) - rewritten used to be patch 5 to patches 4 & 5 (Mark, Sebastian) - added new patch 7 - fixed typos and added tag to patch 12 (Serge) v2: 20230710154932.68377-1-andriy.shevchenko@linux.intel.com Changelog v2: - added new patches 3,4,5,10,13,14 - massaged comment and kernel doc in patch 9 - split used to be patch 4 to patches 11,12 - covered a few things in SPI core in patch 15 - amended commit message for above (Mark) - reshuffled patches in the series for better logical grouping Andy Shevchenko (4): spi: Remove code duplication in spi_add_device*() spi: Kill spi_add_device_locked() spi: Use BITS_TO_BYTES() spi: Use struct_size() helper drivers/spi/spi.c | 51 +++++++++++++---------------------------- include/linux/spi/spi.h | 15 +++++++----- 2 files changed, 25 insertions(+), 41 deletions(-)
Comments
On Fri, 14 Jul 2023 12:17:44 +0300, Andy Shevchenko wrote: > Various cleanups and refactorings of the SPI header and core parts > united in a single series. It also touches drivers under SPI subsystem > folder on the pure renaming purposes of some constants. > > No functional change intended (with some subtle shortcuts which are > explained in the respective commit messages). > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next Thanks! [1/4] spi: Remove code duplication in spi_add_device*() commit: 36124dea164cf684869e856b2ada23e8adab5f03 [2/4] spi: Kill spi_add_device_locked() commit: 7b5c6a545b3491fb785c75cee60e6b0c35a4de1b [3/4] spi: Use BITS_TO_BYTES() commit: 169f5312dc46deb986e368b6828bedbedd297f6e [4/4] spi: Use struct_size() helper commit: 75e308ffc4f0d36b895f1110ece8b77d4116fdb1 All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus during the next merge window (or sooner if it is a bug fix), however if problems are discovered then the patch may be dropped or reverted. You may get further e-mails resulting from automated or manual testing and review of the tree, please engage with people reporting problems and send followup patches addressing any issues that are reported if needed. If any updates are required or you are submitting further changes they should be sent as incremental updates against current git, existing patches will not be replaced. Please add any relevant lists and maintainers to the CCs when replying to this mail. Thanks, Mark