All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luis de Arquer <ldearquer@gmail.com>
To: linux-spi@vger.kernel.org, linux-rockchip@lists.infradead.org
Cc: broonie@kernel.org, heiko@sntech.de,
	linux-arm-kernel@lists.infradead.org,
	 Robin Murphy <robin.murphy@arm.com>,
	luis.dearquer@inertim.com
Subject: [PATCH 0/3] spi: spi-rockchip: Fix of chip select lines handling
Date: Fri, 26 Jan 2024 20:46:05 +0100	[thread overview]
Message-ID: <08e518f54f94b78a3985a3c9247bced5b275433b.camel@gmail.com> (raw)

This patch series has several fixes concerning spi-rockchip handling of chip select lines.

Probably the more important issue is an out of bounds access to an array, fixed on
the first commit of the series. The issue was found and reproduced on a downstream
kernel (orange pi 5 plus), but it seems to still be present on mainline

The patch has been made and built on linux-rockchip tree.
It will take me a few days to complete proper testing, but any comments at this point
are welcome.

Also, this is my first patch, so let me know of any side issues with patch or email
format :)

Luis de Arquer
Inertim Research

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

WARNING: multiple messages have this Message-ID (diff)
From: Luis de Arquer <ldearquer@gmail.com>
To: linux-spi@vger.kernel.org, linux-rockchip@lists.infradead.org
Cc: broonie@kernel.org, heiko@sntech.de,
	linux-arm-kernel@lists.infradead.org,
	 Robin Murphy <robin.murphy@arm.com>,
	luis.dearquer@inertim.com
Subject: [PATCH 0/3] spi: spi-rockchip: Fix of chip select lines handling
Date: Fri, 26 Jan 2024 20:46:05 +0100	[thread overview]
Message-ID: <08e518f54f94b78a3985a3c9247bced5b275433b.camel@gmail.com> (raw)

This patch series has several fixes concerning spi-rockchip handling of chip select lines.

Probably the more important issue is an out of bounds access to an array, fixed on
the first commit of the series. The issue was found and reproduced on a downstream
kernel (orange pi 5 plus), but it seems to still be present on mainline

The patch has been made and built on linux-rockchip tree.
It will take me a few days to complete proper testing, but any comments at this point
are welcome.

Also, this is my first patch, so let me know of any side issues with patch or email
format :)

Luis de Arquer
Inertim Research

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

WARNING: multiple messages have this Message-ID (diff)
From: Luis de Arquer <ldearquer@gmail.com>
To: linux-spi@vger.kernel.org, linux-rockchip@lists.infradead.org
Cc: broonie@kernel.org, heiko@sntech.de,
	linux-arm-kernel@lists.infradead.org,
	 Robin Murphy <robin.murphy@arm.com>,
	luis.dearquer@inertim.com
Subject: [PATCH 0/3] spi: spi-rockchip: Fix of chip select lines handling
Date: Fri, 26 Jan 2024 20:46:05 +0100	[thread overview]
Message-ID: <08e518f54f94b78a3985a3c9247bced5b275433b.camel@gmail.com> (raw)

This patch series has several fixes concerning spi-rockchip handling of chip select lines.

Probably the more important issue is an out of bounds access to an array, fixed on
the first commit of the series. The issue was found and reproduced on a downstream
kernel (orange pi 5 plus), but it seems to still be present on mainline

The patch has been made and built on linux-rockchip tree.
It will take me a few days to complete proper testing, but any comments at this point
are welcome.

Also, this is my first patch, so let me know of any side issues with patch or email
format :)

Luis de Arquer
Inertim Research

             reply	other threads:[~2024-01-26 19:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-26 19:46 Luis de Arquer [this message]
2024-01-26 19:46 ` [PATCH 0/3] spi: spi-rockchip: Fix of chip select lines handling Luis de Arquer
2024-01-26 19:46 ` Luis de Arquer

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=08e518f54f94b78a3985a3c9247bced5b275433b.camel@gmail.com \
    --to=ldearquer@gmail.com \
    --cc=broonie@kernel.org \
    --cc=heiko@sntech.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=luis.dearquer@inertim.com \
    --cc=robin.murphy@arm.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.