From: Brian Norris <computersforpeace@gmail.com>
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: MTD Maling List <linux-mtd@lists.infradead.org>,
Michal Suchanek <hramrach@gmail.com>,
Cyrille Pitchen <cyrille.pitchen@atmel.com>,
Marek Vasut <marex@denx.de>, Han Xu <han.xu@nxp.com>
Subject: Re: [PATCH 2/2] mtd: m25p80: consider max_transfer_size when reading
Date: Tue, 5 Apr 2016 14:07:27 -0700 [thread overview]
Message-ID: <20160405210727.GB5243@localhost> (raw)
In-Reply-To: <57041B43.2000109@gmail.com>
On Tue, Apr 05, 2016 at 10:08:35PM +0200, Heiner Kallweit wrote:
> Am 05.04.2016 um 21:39 schrieb Brian Norris:
> > On Sat, Feb 27, 2016 at 11:50:11PM +0100, Heiner Kallweit wrote:
> >> Some controllers have transfer size limits. To allow to deal with this
> >> max_transfer_size was introduced in the SPI core recently.
> >> Use this new feature to read in chunks if needed.
> >>
> >> Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
> >
> > Michal has been working on a similar series, with some differences (I'll
> > comment below). I think his latest work is here:
> >
> > http://lists.infradead.org/pipermail/linux-mtd/2015-December/063865.html
> >
> > Is there a particular reason you've continued on your series instead of
> > reviewing/fixing his?
> >
> Latest version of Michal's patch set was sent beginning of December and has
> received no comment since then, so I assumed it's dead.
> If that's not the case, totally fine with me and I'll have a further look at it.
There was a comment about the loop bounds changing away from page
alignment. I think otherwise it's about ready to go.
If you or Michal don't take a look at it, I'll rebase and resubmit it.
Brian
next prev parent reply other threads:[~2016-04-05 21:07 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-27 22:50 [PATCH 2/2] mtd: m25p80: consider max_transfer_size when reading Heiner Kallweit
2016-04-05 19:39 ` Brian Norris
2016-04-05 20:08 ` Heiner Kallweit
2016-04-05 21:07 ` Brian Norris [this message]
2016-04-07 19:09 ` Heiner Kallweit
2016-05-05 23:57 ` Brian Norris
2016-05-06 12:14 ` Mark Brown
2016-06-03 22:22 ` Heiner Kallweit
2016-06-06 17:40 ` Mark Brown
2016-06-06 18:28 ` Brian Norris
2016-06-06 18:34 ` Mark Brown
2016-06-06 18:43 ` Brian Norris
2016-06-06 18:48 ` Mark Brown
2016-06-06 18:53 ` Heiner Kallweit
2016-06-06 19:40 ` Michal Suchanek
2016-06-06 21:02 ` Heiner Kallweit
2016-06-06 19:46 ` Geert Uytterhoeven
2016-06-06 21:20 ` Heiner Kallweit
2016-06-06 22:28 ` Marek Vasut
2016-06-07 4:52 ` Heiner Kallweit
2016-06-06 23:07 ` Mark Brown
2016-06-07 6:03 ` Heiner Kallweit
2016-06-07 8:10 ` Michal Suchanek
2016-06-07 20:42 ` Heiner Kallweit
2016-06-08 19:51 ` Heiner Kallweit
2016-06-09 7:12 ` Michal Suchanek
2016-06-17 20:13 ` Heiner Kallweit
2016-04-06 13:55 ` Cyrille Pitchen
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=20160405210727.GB5243@localhost \
--to=computersforpeace@gmail.com \
--cc=cyrille.pitchen@atmel.com \
--cc=han.xu@nxp.com \
--cc=hkallweit1@gmail.com \
--cc=hramrach@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=marex@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).