linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Heiner Kallweit <hkallweit1@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: Brian Norris <computersforpeace@gmail.com>,
	Michal Suchanek <hramrach@gmail.com>,
	Martin Sperl <martin@sperl.org>,
	MTD Maling List <linux-mtd@lists.infradead.org>,
	"linux-spi@vger.kernel.org" <linux-spi@vger.kernel.org>
Subject: Re: [PATCH resubmit 2/2] spi: fsl-espi: make use of max_msg_size in spi_master to handle HW restrictions
Date: Tue, 1 Dec 2015 19:53:56 +0100	[thread overview]
Message-ID: <565DECC4.2030507@gmail.com> (raw)
In-Reply-To: <20151201141923.GJ1929@sirena.org.uk>

Am 01.12.2015 um 15:19 schrieb Mark Brown:
> On Mon, Nov 30, 2015 at 09:25:36PM +0100, Heiner Kallweit wrote:
>> Propagate the 64K message size limitation allowing client drivers
>> to deal properly with this limitation.
> 
> Please don't submit patches into the middle of existing threads, it
> makes it very confusing trying to work out what the currently proposed
> patches are:
> 
>    8592 N T 11/22 Heiner Kallweit (2.1K) │                   │ ├─>[PATCH 2/3] mt
>    8593 N C 11/22 Michal Suchanek (0.5K) │                   │ │ └─>
> -> 8594 N T 11/22 Heiner Kallweit (0.9K) │                   │ ├─>[PATCH 3/3] sp
>    8595 N T 11/30 Heiner Kallweit (1.7K) │                   │ ├─>[PATCH v2 1/2]
>    8596 N T 11/30 Heiner Kallweit (0.9K) │                   │ └─>[PATCH resubmi
>    8597 NsF 11/22 To Heiner Kallw (1.4K) │                   └─>Re: RfC: Handle
> 
> I *think* the two messages from yesterday are supposed to be a single
> patch series but they're buried in the middle of a huge thread at the
> same level as some older patches and for soem reason have different tags
> (one of which is "resubmit" which is really just adding noise).
> 
Sorry, my mail template referred to the discussion thread.
I'll resubmit.

  reply	other threads:[~2015-12-01 18:58 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-18 21:19 RfC: Handle SPI controller limitations like maximum message length Heiner Kallweit
2015-11-18 21:57 ` Mark Brown
2015-11-18 22:50   ` Heiner Kallweit
2015-11-19 11:40     ` Mark Brown
2015-11-19 15:00       ` Martin Sperl
2015-11-19 17:15         ` Mark Brown
2015-11-20  0:07           ` Brian Norris
2015-11-20 11:06             ` Mark Brown
2015-11-20 11:16               ` Martin Sperl
2015-11-20 10:18           ` Martin Sperl
2015-11-20 12:05             ` Mark Brown
2015-11-20 12:56               ` Martin Sperl
2015-11-21 13:49                 ` Mark Brown
2015-11-21 14:10                   ` Heiner Kallweit
2015-11-21 15:57                     ` Michal Suchanek
2015-11-21 22:59                       ` [PATCH 0/3] spi: mtd: Handle HW message length restrictions Heiner Kallweit
2015-11-21 23:01                       ` [PATCH 1/3] spi: core: add max_msg_size to spi_master Heiner Kallweit
2015-11-22 13:16                         ` Mark Brown
2015-11-22 16:15                           ` Heiner Kallweit
2015-11-23 11:38                             ` Mark Brown
2015-11-27 19:26                               ` Heiner Kallweit
2015-11-30 16:42                                 ` Mark Brown
2015-11-30 20:15                                   ` Heiner Kallweit
2015-11-21 23:08                       ` [PATCH 2/3] mtd: m25p80: handle HW message size restrictions Heiner Kallweit
2015-11-22 12:51                         ` Michal Suchanek
2015-11-21 23:11                       ` [PATCH 3/3] spi: fsl-espi: make use of max_msg_size in spi_master to handle HW restrictions Heiner Kallweit
2015-11-30 20:24                       ` [PATCH v2 1/2] spi: core: add max_msg_size to spi_master Heiner Kallweit
2015-11-30 20:25                       ` [PATCH resubmit 2/2] spi: fsl-espi: make use of max_msg_size in spi_master to handle HW restrictions Heiner Kallweit
2015-12-01 14:19                         ` Mark Brown
2015-12-01 18:53                           ` Heiner Kallweit [this message]
2015-11-22 13:19                     ` RfC: Handle SPI controller limitations like maximum message length Mark Brown
2015-11-20  0:02 ` Brian Norris
2015-11-20  6:59   ` Heiner Kallweit
2015-11-20 10:06     ` Heiner Kallweit
2015-11-20 12:35       ` Mark Brown
2015-11-20 18:59         ` Heiner Kallweit
2015-11-20 19:05           ` Michal Suchanek
2015-11-20 19:21             ` Mark Brown
2015-11-20 19:44               ` Michal Suchanek
2015-11-20 23:22             ` Brian Norris
2015-11-21 22:53               ` Heiner Kallweit
2015-11-20 19:18           ` Mark Brown
2015-11-20 19:37             ` Heiner Kallweit
2015-11-20 12:31   ` Mark Brown
2015-11-20 12:56 ` Michal Suchanek
2015-11-20 23:07   ` Brian Norris

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=565DECC4.2030507@gmail.com \
    --to=hkallweit1@gmail.com \
    --cc=broonie@kernel.org \
    --cc=computersforpeace@gmail.com \
    --cc=hramrach@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=martin@sperl.org \
    /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).