All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Colin Ian King <colin.i.king@gmail.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"Rafael J . Wysocki" <rafael@kernel.org>
Cc: linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] regmap: mmio: replace return 0 with break in switch statement
Date: Thu, 22 Sep 2022 18:54:02 +0100	[thread overview]
Message-ID: <166386924264.727940.17683368538547591702.b4-ty@kernel.org> (raw)
In-Reply-To: <20220922080445.818020-1-colin.i.king@gmail.com>

On Thu, 22 Sep 2022 09:04:45 +0100, Colin Ian King wrote:
> Variable min_stride is assigned a value that is never read, fix this by
> replacing the return 0 with a break statement. This also makes the case
> statement consistent with the other cases in the switch statement.
> 
> 

Applied to

   broonie/regmap.git for-next

Thanks!

[1/1] regmap: mmio: replace return 0 with break in switch statement
      commit: 01ed230761e51f0403b3f3845c11cb67014487e2

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

      reply	other threads:[~2022-09-22 17:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-22  8:04 [PATCH] regmap: mmio: replace return 0 with break in switch statement Colin Ian King
2022-09-22 17:54 ` 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=166386924264.727940.17683368538547591702.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=colin.i.king@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael@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 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.