public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: Michal Simek <michal.simek@amd•com>
To: Rosen Penev <rosenp@gmail•com>, linux-kernel@vger•kernel.org
Cc: Arnd Bergmann <arnd@arndb•de>,
	chleroy@kernel•org,
	Greg Kroah-Hartman <gregkh@linuxfoundation•org>,
	"moderated list:ARM/ZYNQ ARCHITECTURE"
	<linux-arm-kernel@lists•infradead.org>
Subject: Re: [PATCH] char: xilinx_hwicap: replace in_be32/out_be32 with ioread32be/iowrite32be
Date: Tue, 2 Jun 2026 08:22:38 +0200	[thread overview]
Message-ID: <878fd338-b4d0-4e46-987c-5a0ee52989dc@amd.com> (raw)
In-Reply-To: <20260602035717.623208-1-rosenp@gmail.com>



On 6/2/26 05:57, Rosen Penev wrote:
> Mechanical conversion of the ppc4xx-specific accessors to the generic
> portable helpers.
> 
> As a result, COMPILE_TEST is added for extra compile coverage.
> 
> Assisted-by: opencode:big-pickle
> Signed-off-by: Rosen Penev <rosenp@gmail•com>
> ---
>   drivers/char/Kconfig                     |  2 +-
>   drivers/char/xilinx_hwicap/buffer_icap.c | 16 +++++------
>   drivers/char/xilinx_hwicap/fifo_icap.c   | 34 +++++++++++-------------
>   3 files changed, 24 insertions(+), 28 deletions(-)

I don't really mind about this because I think that we can also remove the whole 
driver.

Thanks,
Michal


  reply	other threads:[~2026-06-02  6:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-02  3:57 [PATCH] char: xilinx_hwicap: replace in_be32/out_be32 with ioread32be/iowrite32be Rosen Penev
2026-06-02  6:22 ` Michal Simek [this message]
2026-06-03 19:52   ` Rosen Penev
2026-06-04  6:30     ` Michal Simek
2026-06-04  7:13       ` Rosen Penev

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=878fd338-b4d0-4e46-987c-5a0ee52989dc@amd.com \
    --to=michal.simek@amd$(echo .)com \
    --cc=arnd@arndb$(echo .)de \
    --cc=chleroy@kernel$(echo .)org \
    --cc=gregkh@linuxfoundation$(echo .)org \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=rosenp@gmail$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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