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:45:48 +0200 [thread overview]
Message-ID: <20140902174548.GB10355@katana> (raw)
In-Reply-To: <5405FE27.4050909@cogentembedded.com>
[-- Attachment #1: Type: text/plain, Size: 1313 bytes --]
> >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.
Yes. Still, if I send something to *stable*, less broken is not an
option for me, if I know there is a fix possible. And we are at -rc3
now, so there is still time for that.
> >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.
Good luck with that! Such bugs are truly annoying :(
> 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.
With all my changes in 3.16, I wonder if the patch with your addition to
the revert will apply anyhow. But, okay, you send two patches, and I
will decide how I apply them and deal with delta-patches. Okay?
All the best,
Wolfram
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
WARNING: multiple messages have this Message-ID (diff)
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, 02 Sep 2014 17:45:48 +0000 [thread overview]
Message-ID: <20140902174548.GB10355@katana> (raw)
In-Reply-To: <5405FE27.4050909@cogentembedded.com>
[-- Attachment #1: Type: text/plain, Size: 1313 bytes --]
> >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.
Yes. Still, if I send something to *stable*, less broken is not an
option for me, if I know there is a fix possible. And we are at -rc3
now, so there is still time for that.
> >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.
Good luck with that! Such bugs are truly annoying :(
> 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.
With all my changes in 3.16, I wonder if the patch with your addition to
the revert will apply anyhow. But, okay, you send two patches, and I
will decide how I apply them and deal with delta-patches. Okay?
All the best,
Wolfram
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-09-02 17:45 UTC|newest]
Thread overview: 24+ 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-23 20:44 ` Sergei Shtylyov
2014-08-24 6:45 ` Wolfram Sang
2014-08-24 6:45 ` Wolfram Sang
2014-08-24 11:30 ` Sergei Shtylyov
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 3:40 ` Wolfram Sang
2014-08-25 11:35 ` Sergei Shtylyov
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-08-25 14:33 ` Wolfram Sang
2014-09-02 17:13 ` Sergei Shtylyov
2014-09-02 17:13 ` Sergei Shtylyov
2014-09-02 17:18 ` Wolfram Sang
2014-09-02 17:18 ` Wolfram Sang
2014-09-02 17:28 ` Sergei Shtylyov
2014-09-02 17:28 ` Sergei Shtylyov
2014-09-02 17:45 ` Wolfram Sang [this message]
2014-09-02 17:45 ` Wolfram Sang
2014-09-02 18:10 ` Sergei Shtylyov
2014-09-02 18:10 ` Sergei Shtylyov
2014-09-04 18:05 ` Wolfram Sang
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=20140902174548.GB10355@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 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.