linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Noralf Trønnes" <noralf@tronnes.org>
To: Michal Suchanek <hramrach@gmail.com>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	devel@driverdev.osuosl.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] staging: fbtft: do not allocate huge txbuf
Date: Thu, 9 Jun 2016 20:42:27 +0200	[thread overview]
Message-ID: <c47da3b7-5082-4358-5556-7b9fdacadd5d@tronnes.org> (raw)
In-Reply-To: <CAOMqctSzkVFYe1AajiMYu3Lx-jw2_KRHeRukO2tSaCtg8JxO4g@mail.gmail.com>

[resending got rejected on the list for html format]

Den 09.06.2016 19:18, skrev Michal Suchanek:
> Hello,
>
> On 9 June 2016 at 18:20, Noralf Trønnes <noralf@tronnes.org> wrote:
>> Den 09.06.2016 17:08, skrev Michal Suchanek:
>>> txbuflen can be set to arbitrary value by user and it is also set
>>> automagically to the maximum transfer size of the SPI master controller.
>>
>> AFAICT this is a result of your previous patch. Please make a new version of
>> your previous patch with this fix in it. Also make a note in that thread
>> that
> That patch is pretty much independent and just exposes this problem
> under different circumstances. The txbuflen can be also set by the
> user.
>
>> a new version is made so Greg doesn't pull it when he sees my ack. He
>> handles a large volume of patches so let's make it as easy as we can for
>> him.
> Which would be letting in the patches separately imho.


Ok,

Acked-by: Noralf Trønnes <noralf@tronnes.org>

> Thanks
>
> Michal
>

      reply	other threads:[~2016-06-09 18:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1f3abe9aabf3fee9d01b5aa8e93859b0f7ed7142.1465484464.git.hramrach@gmail.com>
2016-06-09 16:20 ` [PATCH] staging: fbtft: do not allocate huge txbuf Noralf Trønnes
2016-06-09 17:18   ` Michal Suchanek
2016-06-09 18:42     ` Noralf Trønnes [this message]

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=c47da3b7-5082-4358-5556-7b9fdacadd5d@tronnes.org \
    --to=noralf@tronnes.org \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hramrach@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thomas.petazzoni@free-electrons.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 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).