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

[-- Attachment #1: Type: text/plain, Size: 471 bytes --]


> >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. And we don't have two patches yet, just the revert. So, the
result is broken anyhow.

Can you elaborate?


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2014-09-02 17:18 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 [this message]
2014-09-02 17:28                   ` Sergei Shtylyov
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=20140902171835.GA10355@katana \
    --to=wsa@the-dreams.de \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=sergei.shtylyov@cogentembedded.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).