From: marek.vasut@gmail.com (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] MXS: Convert mutexes in clock.c to spinlocks
Date: Tue, 20 Dec 2011 00:35:52 +0100 [thread overview]
Message-ID: <201112200035.52802.marek.vasut@gmail.com> (raw)
In-Reply-To: <20111219232325.GA5683@S2100-06.ap.freescale.net>
> On Mon, Dec 19, 2011 at 09:54:25PM +0100, Marek Vasut wrote:
> > > So, in summary, you have everything you require to fix it outside the
> > > driver. You just have to decide which of the two options you want to
> > > proceed with, and actually (and finally) do it instead of endlessly
> > > procrastinating and waiting for more and more bug reports (which is
> > > exactly what has happened so far.)
>
> Marek, the 'you' here really means me rather than you.
Sure, I figured as much after Russells reply.
>
> Russell, sorry for leaving the issue here for long time, and I'm working
> on the patches you suggested right now.
I see ... shall I back off from this issue then? Can I somehow help you on this?
M
WARNING: multiple messages have this Message-ID (diff)
From: Marek Vasut <marek.vasut@gmail.com>
To: Shawn Guo <shawn.guo@freescale.com>
Cc: "Russell King - ARM Linux" <linux@arm.linux.org.uk>,
Wolfgang Denk <wd@denx.de>, Sascha Hauer <s.hauer@pengutronix.de>,
linux-kernel@vger.kernel.org, Huang Shijie <b32955@freescale.com>,
linux-arm-kernel@lists.infradead.org,
Shawn Guo <shawn.guo@linaro.org>, Stefano Babic <sbabic@denx.de>
Subject: Re: [PATCH] MXS: Convert mutexes in clock.c to spinlocks
Date: Tue, 20 Dec 2011 00:35:52 +0100 [thread overview]
Message-ID: <201112200035.52802.marek.vasut@gmail.com> (raw)
In-Reply-To: <20111219232325.GA5683@S2100-06.ap.freescale.net>
> On Mon, Dec 19, 2011 at 09:54:25PM +0100, Marek Vasut wrote:
> > > So, in summary, you have everything you require to fix it outside the
> > > driver. You just have to decide which of the two options you want to
> > > proceed with, and actually (and finally) do it instead of endlessly
> > > procrastinating and waiting for more and more bug reports (which is
> > > exactly what has happened so far.)
>
> Marek, the 'you' here really means me rather than you.
Sure, I figured as much after Russells reply.
>
> Russell, sorry for leaving the issue here for long time, and I'm working
> on the patches you suggested right now.
I see ... shall I back off from this issue then? Can I somehow help you on this?
M
next prev parent reply other threads:[~2011-12-19 23:35 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-18 14:06 [PATCH] MXS: Convert mutexes in clock.c to spinlocks Marek Vasut
2011-12-18 14:06 ` Marek Vasut
2011-12-19 3:27 ` Shawn Guo
2011-12-19 3:27 ` Shawn Guo
2011-12-19 4:03 ` Marek Vasut
2011-12-19 4:03 ` Marek Vasut
2011-12-19 8:22 ` Russell King - ARM Linux
2011-12-19 8:22 ` Russell King - ARM Linux
2011-12-19 11:57 ` Marek Vasut
2011-12-19 11:57 ` Marek Vasut
2011-12-19 12:15 ` Russell King - ARM Linux
2011-12-19 12:15 ` Russell King - ARM Linux
2011-12-19 20:54 ` Marek Vasut
2011-12-19 20:54 ` Marek Vasut
2011-12-19 21:03 ` Russell King - ARM Linux
2011-12-19 21:03 ` Russell King - ARM Linux
2011-12-19 21:05 ` Marek Vasut
2011-12-19 21:05 ` Marek Vasut
2011-12-19 21:28 ` Russell King - ARM Linux
2011-12-19 21:28 ` Russell King - ARM Linux
2011-12-19 21:37 ` Marek Vasut
2011-12-19 21:37 ` Marek Vasut
2011-12-19 21:43 ` Marek Vasut
2011-12-19 21:43 ` Marek Vasut
2011-12-19 23:23 ` Shawn Guo
2011-12-19 23:23 ` Shawn Guo
2011-12-19 23:35 ` Marek Vasut [this message]
2011-12-19 23:35 ` Marek Vasut
2011-12-20 0:19 ` Shawn Guo
2011-12-20 0:19 ` Shawn Guo
2011-12-20 3:09 ` Marek Vasut
2011-12-20 3:09 ` Marek Vasut
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=201112200035.52802.marek.vasut@gmail.com \
--to=marek.vasut@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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.