All of lore.kernel.org
 help / color / mirror / Atom feed
From: Federico Vaga <federico.vaga@cern.ch>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: Peter Korsgaard <peter@korsgaard.com>,
	linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2 0/5] i2c:ocores: improvements
Date: Tue, 15 Jan 2019 17:37:07 +0100	[thread overview]
Message-ID: <14601911.GrvbWtgO0l@pcbe13614> (raw)
In-Reply-To: <20181127113821.GB1107@kunai>

Hi there,

I just want to ask if there has been any update about this patchset that I'm 
not aware off. Thanks

On Tuesday, November 27, 2018 12:38:22 PM CET Wolfram Sang wrote:
> > This patch set provides improvements to the i2c-ocore driver.
> > 
> > [V1 -> V2]
> > - replaced usleep_range() with udelay() so that the polling version can be
> > 
> >   used in atomic context.
> > 
> > - added dedicated patch for minor style issues
> > - fixed delay computation
> > - use spin_lock_irqsave(), instead of spin_trylock_irqsave(). IACK is
> > always> 
> >   necessary and a trylock would generate an extra interrupt for nothing
> > 
> > - make the driver ready for an eventual master_xfer_irqless()
> 
> Peter, do you have a time slot to review this?

WARNING: multiple messages have this Message-ID (diff)
From: Federico Vaga <federico.vaga@cern.ch>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: Peter Korsgaard <peter@korsgaard.com>,
	<linux-i2c@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V2 0/5] i2c:ocores: improvements
Date: Tue, 15 Jan 2019 17:37:07 +0100	[thread overview]
Message-ID: <14601911.GrvbWtgO0l@pcbe13614> (raw)
In-Reply-To: <20181127113821.GB1107@kunai>

Hi there,

I just want to ask if there has been any update about this patchset that I'm 
not aware off. Thanks

On Tuesday, November 27, 2018 12:38:22 PM CET Wolfram Sang wrote:
> > This patch set provides improvements to the i2c-ocore driver.
> > 
> > [V1 -> V2]
> > - replaced usleep_range() with udelay() so that the polling version can be
> > 
> >   used in atomic context.
> > 
> > - added dedicated patch for minor style issues
> > - fixed delay computation
> > - use spin_lock_irqsave(), instead of spin_trylock_irqsave(). IACK is
> > always> 
> >   necessary and a trylock would generate an extra interrupt for nothing
> > 
> > - make the driver ready for an eventual master_xfer_irqless()
> 
> Peter, do you have a time slot to review this?





  reply	other threads:[~2019-01-15 16:37 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-29 14:50 [PATCH V2 0/5] i2c:ocores: improvements Federico Vaga
2018-10-29 14:50 ` Federico Vaga
2018-10-29 14:50 ` [PATCH V2 1/5] i2c:ocores: stop transfer on timeout Federico Vaga
2018-10-29 14:50   ` Federico Vaga
2018-10-29 14:50 ` [PATCH V2 2/5] i2c:ocores: do not handle IRQ if IF is not set Federico Vaga
2018-10-29 14:50   ` Federico Vaga
2018-10-29 14:50 ` [PATCH V2 3/5] i2c:ocores: add polling interface Federico Vaga
2018-10-29 14:50   ` Federico Vaga
2018-10-29 14:50 ` [PATCH V2 4/5] i2c:ocores: add SPDX tag Federico Vaga
2018-10-29 14:50   ` Federico Vaga
2018-10-29 14:50 ` [PATCH V2 5/5] i2c:ocores: checkpatch fixes Federico Vaga
2018-10-29 14:50   ` Federico Vaga
2018-11-27 11:38 ` [PATCH V2 0/5] i2c:ocores: improvements Wolfram Sang
2019-01-15 16:37   ` Federico Vaga [this message]
2019-01-15 16:37     ` Federico Vaga
2019-01-15 22:49     ` Wolfram Sang

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=14601911.GrvbWtgO0l@pcbe13614 \
    --to=federico.vaga@cern.ch \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peter@korsgaard.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 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.