linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: linux-spi@vger.kernel.org,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	linux-kernel@vger.kernel.org
Cc: Jon Hunter <jonathanh@nvidia.com>
Subject: Re: (subset) [PATCH v3 1/3] spi: Fix condition in the __spi_register_driver()
Date: Wed, 24 Nov 2021 17:37:03 +0000	[thread overview]
Message-ID: <163777542313.2712295.15442415383053073135.b4-ty@kernel.org> (raw)
In-Reply-To: <20211123170034.41253-1-andriy.shevchenko@linux.intel.com>

On Tue, 23 Nov 2021 19:00:32 +0200, Andy Shevchenko wrote:
> The recent commit 3f07657506df ("spi: deduplicate spi_match_id()
> in __spi_register_driver()") inadvertently inverted a condition
> that provokes a (harmless) warning:
> 
>   WARNING KERN SPI driver mtd_dataflash has no spi_device_id for atmel,at45
> 
> Restore logic to avoid such warning to be issued.
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next

Thanks!

[1/3] spi: Fix condition in the __spi_register_driver()
      commit: b79332ef9d61513d0ccda74a5161bb7c31851e9c

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

      parent reply	other threads:[~2021-11-24 17:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-23 17:00 [PATCH v3 1/3] spi: Fix condition in the __spi_register_driver() Andy Shevchenko
2021-11-23 17:00 ` [PATCH v3 2/3] spi: Replace memset() with __GFP_ZERO Andy Shevchenko
2021-11-23 17:02   ` Andy Shevchenko
2021-11-23 17:00 ` [PATCH v3 3/3] spi: Fix multi-line comment style Andy Shevchenko
2021-11-23 17:02   ` Andy Shevchenko
2021-11-23 17:34 ` [PATCH v3 1/3] spi: Fix condition in the __spi_register_driver() Jon Hunter
2021-11-24 17:37 ` Mark Brown [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=163777542313.2712295.15442415383053073135.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=jonathanh@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).