All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: yang.lee@linux.alibaba.com
Cc: abaci@linux.alibaba.com, lewis.hanly@microchip.com,
	linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org,
	conor.dooley@microchip.com, linux-riscv@lists.infradead.org
Subject: Re: (subset) [PATCH -next 1/2] spi: Remove unnecessary print function dev_err()
Date: Thu, 09 Jun 2022 15:13:18 +0100	[thread overview]
Message-ID: <165478399889.1092145.5682711038335760840.b4-ty@kernel.org> (raw)
In-Reply-To: <20220609055533.95866-2-yang.lee@linux.alibaba.com>

On Thu, 9 Jun 2022 13:55:33 +0800, Yang Li wrote:
> The function platform_get_irq() never returns 0, and the print function
> dev_err() is redundant because platform_get_irq() already prints an error.
> 
> Eliminate the follow coccicheck warning:
> ./drivers/spi/spi-microchip-core.c:543:2-9: line 543 is redundant
> because platform_get_irq() already prints an error
> 
> [...]

Applied to

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

Thanks!

[2/2] spi: fix platform_no_drv_owner.cocci warning
      commit: a4f26ba2608c9ff736a9ad1348aa8078f0b03f81

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

WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org>
To: yang.lee@linux.alibaba.com
Cc: abaci@linux.alibaba.com, lewis.hanly@microchip.com,
	linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org,
	conor.dooley@microchip.com, linux-riscv@lists.infradead.org
Subject: Re: (subset) [PATCH -next 1/2] spi: Remove unnecessary print function dev_err()
Date: Thu, 09 Jun 2022 15:13:18 +0100	[thread overview]
Message-ID: <165478399889.1092145.5682711038335760840.b4-ty@kernel.org> (raw)
In-Reply-To: <20220609055533.95866-2-yang.lee@linux.alibaba.com>

On Thu, 9 Jun 2022 13:55:33 +0800, Yang Li wrote:
> The function platform_get_irq() never returns 0, and the print function
> dev_err() is redundant because platform_get_irq() already prints an error.
> 
> Eliminate the follow coccicheck warning:
> ./drivers/spi/spi-microchip-core.c:543:2-9: line 543 is redundant
> because platform_get_irq() already prints an error
> 
> [...]

Applied to

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

Thanks!

[2/2] spi: fix platform_no_drv_owner.cocci warning
      commit: a4f26ba2608c9ff736a9ad1348aa8078f0b03f81

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

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  parent reply	other threads:[~2022-06-09 14:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-09  5:55 [PATCH -next 2/2] spi: fix platform_no_drv_owner.cocci warning Yang Li
2022-06-09  5:55 ` Yang Li
2022-06-09  5:55 ` [PATCH -next 1/2] spi: Remove unnecessary print function dev_err() Yang Li
2022-06-09  5:55   ` Yang Li
2022-06-09 10:55   ` Mark Brown
2022-06-09 10:55     ` Mark Brown
2022-06-09 15:15     ` Conor.Dooley
2022-06-09 15:15       ` Conor.Dooley
2022-06-09 14:13   ` Mark Brown [this message]
2022-06-09 14:13     ` (subset) " Mark Brown

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=165478399889.1092145.5682711038335760840.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=abaci@linux.alibaba.com \
    --cc=conor.dooley@microchip.com \
    --cc=lewis.hanly@microchip.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=yang.lee@linux.alibaba.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.