All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jagan Teki <jagan@amarulasolutions.com>
To: Simon Glass <sjg@chromium.org>,
	Kever Yang <kever.yang@rock-chips.com>,
	Philipp Tomsich <philipp.tomsich@theobroma-systems.com>
Cc: u-boot@lists.denx.de,
	linux-amarula <linux-amarula@amarulasolutions.com>,
	linux-rockchip@lists.infradead.org
Subject: [PATCH 0/2] spi: rk_spi: Fix transfer size overflow
Date: Wed, 11 Dec 2019 18:56:21 +0530	[thread overview]
Message-ID: <20191211132623.430-1-jagan@amarulasolutions.com> (raw)

These two patches are fixing flash read with > 64K size and
spi flash read during SPI boot.

Any inputs?
Jagan.

Jagan Teki (2):
  Revert "rockchip: spi: fix off-by-one in chunk size computation"
  spi: rk_spi: Fix overflow max chunk size

 drivers/spi/rk_spi.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

-- 
2.18.0.321.gffc6fa0e3

WARNING: multiple messages have this Message-ID (diff)
From: Jagan Teki <jagan@amarulasolutions.com>
To: u-boot@lists.denx.de
Subject: [PATCH 0/2] spi: rk_spi: Fix transfer size overflow
Date: Wed, 11 Dec 2019 18:56:21 +0530	[thread overview]
Message-ID: <20191211132623.430-1-jagan@amarulasolutions.com> (raw)

These two patches are fixing flash read with > 64K size and
spi flash read during SPI boot.

Any inputs?
Jagan.

Jagan Teki (2):
  Revert "rockchip: spi: fix off-by-one in chunk size computation"
  spi: rk_spi: Fix overflow max chunk size

 drivers/spi/rk_spi.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

-- 
2.18.0.321.gffc6fa0e3

             reply	other threads:[~2019-12-11 13:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-11 13:26 Jagan Teki [this message]
2019-12-11 13:26 ` [PATCH 0/2] spi: rk_spi: Fix transfer size overflow Jagan Teki
     [not found] ` <20191211132623.430-1-jagan-dyjBcgdgk7Pe9wHmmfpqLFaTQe2KTcn/@public.gmane.org>
2019-12-11 13:26   ` [PATCH 1/2] Revert "rockchip: spi: fix off-by-one in chunk size computation" Jagan Teki
2019-12-11 13:26     ` Jagan Teki
2019-12-11 13:40     ` Philipp Tomsich
2019-12-11 13:40       ` Philipp Tomsich
2019-12-11 14:10       ` Jagan Teki
2019-12-11 14:10         ` Jagan Teki
     [not found]       ` <1E12E6D7-5401-4EF5-9D74-DFC6F8216799-SN7IsUiht6C/RdPyistoZJqQE7yCjDx5@public.gmane.org>
2019-12-21  7:32         ` Jagan Teki
2019-12-21  7:32           ` Jagan Teki
2019-12-23  2:28           ` Kever Yang
2019-12-23  2:28             ` Kever Yang
2019-12-11 13:26   ` [PATCH 2/2] spi: rk_spi: Fix overflow max chunk size Jagan Teki
2019-12-11 13:26     ` Jagan Teki

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=20191211132623.430-1-jagan@amarulasolutions.com \
    --to=jagan@amarulasolutions.com \
    --cc=kever.yang@rock-chips.com \
    --cc=linux-amarula@amarulasolutions.com \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=philipp.tomsich@theobroma-systems.com \
    --cc=sjg@chromium.org \
    --cc=u-boot@lists.denx.de \
    /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.