All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Geert Uytterhoeven <geert+renesas@glider.be>,
	Fabrizio Castro <fabrizio.castro.jz@renesas.com>
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>,
	linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org,
	Chris Paterson <Chris.Paterson2@renesas.com>,
	Biju Das <biju.das@bp.renesas.com>,
	Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>,
	linux-renesas-soc@vger.kernel.org
Subject: Re: (subset) [PATCH 00/10] spi: rzv2m-csi: Code refactoring
Date: Tue, 18 Jul 2023 19:46:49 +0100	[thread overview]
Message-ID: <168970600997.94192.11376983705102685200.b4-ty@kernel.org> (raw)
In-Reply-To: <20230715010407.1751715-1-fabrizio.castro.jz@renesas.com>

On Sat, 15 Jul 2023 02:03:57 +0100, Fabrizio Castro wrote:
> this series is to follow up on Geert and Andy feedback:
> https://patchwork.kernel.org/project/linux-renesas-soc/patch/20230622113341.657842-4-fabrizio.castro.jz@renesas.com/
> 
> Thanks,
> Fab
> 
> Fabrizio Castro (10):
>   spi: rzv2m-csi: Add missing include
>   spi: rzv2m-csi: Adopt HZ_PER_MHZ for max spi clock
>   spi: rzv2m-csi: Rework CSI_CKS_MAX definition
>   spi: rzv2m-csi: Leave readl_poll_timeout calls for last
>   spi: rzv2m-csi: Replace unnecessary ternary operators
>   spi: rzv2m-csi: Squash timing settings into one statement
>   spi: rzv2m-csi: Switch to using {read,write}s{b,w}
>   spi: rzv2m-csi: Improve data types and alignment
>   spi: rzv2m-csi: Get rid of the x_trg{_words} tables
>   spi: rzv2m-csi: Make use of device_set_node
> 
> [...]

Applied to

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

Thanks!

[01/10] spi: rzv2m-csi: Add missing include
        commit: f572ba797c639c9b1705908d3f5d71ed7c3f53e0
[02/10] spi: rzv2m-csi: Adopt HZ_PER_MHZ for max spi clock
        commit: 74e27ce8d23c3aeb1a9fdcaf6261462506bbbfc3
[03/10] spi: rzv2m-csi: Rework CSI_CKS_MAX definition
        commit: aecf9fbdb7a4dc6d83e8d9984c8d9dc074d8ea2e
[04/10] spi: rzv2m-csi: Leave readl_poll_timeout calls for last
        commit: 2ed2699f58891c72fcd462129345d09424f986c5
[05/10] spi: rzv2m-csi: Replace unnecessary ternary operators
        commit: 9f5ac599801c0f7c0969fa94c638265ed988b9bc

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:[~2023-07-18 18:46 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-15  1:03 [PATCH 00/10] spi: rzv2m-csi: Code refactoring Fabrizio Castro
2023-07-15  1:03 ` [PATCH 01/10] spi: rzv2m-csi: Add missing include Fabrizio Castro
2023-07-15  1:03 ` [PATCH 02/10] spi: rzv2m-csi: Adopt HZ_PER_MHZ for max spi clock Fabrizio Castro
2023-07-17  9:24   ` Geert Uytterhoeven
2023-07-15  1:04 ` [PATCH 03/10] spi: rzv2m-csi: Rework CSI_CKS_MAX definition Fabrizio Castro
2023-07-17  9:27   ` Geert Uytterhoeven
2023-07-15  1:04 ` [PATCH 04/10] spi: rzv2m-csi: Leave readl_poll_timeout calls for last Fabrizio Castro
2023-07-17  9:29   ` Geert Uytterhoeven
2023-07-15  1:04 ` [PATCH 05/10] spi: rzv2m-csi: Replace unnecessary ternary operators Fabrizio Castro
2023-07-17  9:30   ` Geert Uytterhoeven
2023-07-15  1:04 ` [PATCH 06/10] spi: rzv2m-csi: Squash timing settings into one statement Fabrizio Castro
2023-07-15  7:54   ` Andy Shevchenko
2023-07-17 10:44     ` Fabrizio Castro
2023-07-17 11:15       ` Andy Shevchenko
2023-07-15  1:04 ` [PATCH 07/10] spi: rzv2m-csi: Switch to using {read,write}s{b,w} Fabrizio Castro
2023-07-17  9:37   ` Geert Uytterhoeven
2023-07-17 10:36     ` Fabrizio Castro
2023-07-17 11:18       ` Andy Shevchenko
2023-07-17 13:00         ` Fabrizio Castro
2023-07-17 16:31           ` Fabrizio Castro
2023-07-15  1:04 ` [PATCH 08/10] spi: rzv2m-csi: Improve data types and alignment Fabrizio Castro
2023-07-17  9:44   ` Geert Uytterhoeven
2023-07-15  1:04 ` [PATCH 09/10] spi: rzv2m-csi: Get rid of the x_trg{_words} tables Fabrizio Castro
2023-07-15  7:57   ` Andy Shevchenko
2023-07-17  9:49   ` Geert Uytterhoeven
2023-07-15  1:04 ` [PATCH 10/10] spi: rzv2m-csi: Make use of device_set_node Fabrizio Castro
2023-07-15  7:58   ` Andy Shevchenko
2023-07-17 15:05     ` Fabrizio Castro
2023-07-15  8:00 ` [PATCH 00/10] spi: rzv2m-csi: Code refactoring Andy Shevchenko
2023-07-18 18:46 ` 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=168970600997.94192.11376983705102685200.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=Chris.Paterson2@renesas.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=biju.das@bp.renesas.com \
    --cc=fabrizio.castro.jz@renesas.com \
    --cc=geert+renesas@glider.be \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=prabhakar.mahadev-lad.rj@bp.renesas.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.