linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: linux-i2c@vger.kernel.org, linux-sh@vger.kernel.org
Subject: Re: [PATCH v2] Revert "i2c: rcar: remove spinlock"
Date: Tue, 02 Sep 2014 21:28:07 +0400	[thread overview]
Message-ID: <5405FE27.4050909@cogentembedded.com> (raw)
In-Reply-To: <20140902171835.GA10355@katana>

On 09/02/2014 09:18 PM, Wolfram Sang wrote:

>>> As I understood from your previous mail, a plain revert is less broken
>>> but still broken. Applying a correct fix is my preferred way.

>>     Actually, from the -stable kernel perspective, a single patch would
>> complicate backporting. So could you please reconsider?

> I don't see why. If we have two patches, the state inbetween them is
> broken.

    Even so, it has always been broken, we don't make it more broken by 
reverting your change.

> And we don't have two patches yet, just the revert. So, the

    I'm going to consider the spinlock issue ASAP, after I check whether the 
I2C clock frequency really has any influence on the unexpected read NACK issue 
I've been chasing for several days.

> result is broken anyhow.

> Can you elaborate?

    Your patch removing the spinlock went into 3.16 only but we'd have to 
backport the assumed single patch to the -stable kernels older than that. This 
means that I'd have to provide the "delta" patch (i.e. the separate patch that 
I'd like to provide now atop of the revert) for these kernels instead since 
the original single patch wouldn't apply anyway.

WBR, Sergei


  reply	other threads:[~2014-09-02 17:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-23 20:44 [PATCH v2] Revert "i2c: rcar: remove spinlock" Sergei Shtylyov
2014-08-24  6:45 ` Wolfram Sang
2014-08-24 11:30   ` Sergei Shtylyov
     [not found]     ` <53F9CCE7.3010006-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org>
2014-08-25  3:40       ` Wolfram Sang
2014-08-25 11:35         ` Sergei Shtylyov
     [not found]           ` <53FB1F90.6080704-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org>
2014-08-25 14:33             ` Wolfram Sang
2014-09-02 17:13               ` Sergei Shtylyov
2014-09-02 17:18                 ` Wolfram Sang
2014-09-02 17:28                   ` Sergei Shtylyov [this message]
2014-09-02 17:45                     ` Wolfram Sang
2014-09-02 18:10                       ` Sergei Shtylyov
2014-09-04 18:05 ` 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=5405FE27.4050909@cogentembedded.com \
    --to=sergei.shtylyov@cogentembedded.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).