mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Engraf <david.engraf@sysgo.com>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: ludovic.desroches@microchip.com, nicolas.ferre@microchip.com,
	alexandre.belloni@bootlin.com, linux-i2c@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] i2c: at91: Read all available bytes at once
Date: Mon, 30 Apr 2018 08:11:05 +0200	[thread overview]
Message-ID: <d728f2ac-5763-48af-03b5-571a75265281@sysgo.com> (raw)
In-Reply-To: <20180428123838.abxiht7k4egv7iel@ninjato>

Am 28.04.2018 um 14:38 schrieb Wolfram Sang:
> On Thu, Apr 26, 2018 at 11:53:14AM +0200, David Engraf wrote:
>> With FIFO enabled it is possible to read multiple bytes
>> at once in the interrupt handler as long as RXRDY is
>> set. This may also reduce the number of interrupts.
>>
>> This patch polls RXRDY and reads all available bytes at
>> once.
>>
>> Signed-off-by: David Engraf <david.engraf@sysgo.com>
> 
> checkpatch said twice:
> 
> WARNING: line over 80 characters
> 
> While I am not super-strict with this limit, it makes sense here IMO.
> The comment stays readable, and we don't even lose a line.

Sorry for that.

> Fixed it this time for you.

Thanks
- David

> Applied to for-next, thanks!
> 

  reply	other threads:[~2018-04-30  6:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-18 12:40 [PATCH] " David Engraf
2018-04-25 15:08 ` Ludovic Desroches
2018-04-25 15:43   ` David Engraf
2018-04-26  8:25     ` Ludovic Desroches
2018-04-26  9:53       ` [PATCH v2] " David Engraf
2018-04-26 12:30         ` Ludovic Desroches
2018-04-28 12:38         ` Wolfram Sang
2018-04-30  6:11           ` David Engraf [this message]
2018-04-26  5:52   ` [PATCH] " David Engraf

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=d728f2ac-5763-48af-03b5-571a75265281@sysgo.com \
    --to=david.engraf@sysgo.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ludovic.desroches@microchip.com \
    --cc=nicolas.ferre@microchip.com \
    --cc=wsa@the-dreams.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
all inboxes | Powered by JetHome®