From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] MXS: Convert mutexes in clock.c to spinlocks
Date: Mon, 19 Dec 2011 21:03:17 +0000 [thread overview]
Message-ID: <20111219210317.GI14542@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <201112192154.25310.marek.vasut@gmail.com>
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.)
>
> What the hell, I just recently found this bug and I submitted a patch right
> away! What are you complaining about?!
If you want to take that attitude to my attempt to help you understand
the problem and see solutions, I'll ignore you permanently for being an
absolute twit. I'm not going to spend time giving a detailed explaination
about the background and options over something to only then have it
immediately shoved back in my face with such a response.
next prev parent reply other threads:[~2011-12-19 21:03 UTC|newest]
Thread overview: 16+ 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-19 3:27 ` Shawn Guo
2011-12-19 4:03 ` Marek Vasut
2011-12-19 8:22 ` Russell King - ARM Linux
2011-12-19 11:57 ` Marek Vasut
2011-12-19 12:15 ` Russell King - ARM Linux
2011-12-19 20:54 ` Marek Vasut
2011-12-19 21:03 ` Russell King - ARM Linux [this message]
2011-12-19 21:05 ` Marek Vasut
2011-12-19 21:28 ` Russell King - ARM Linux
2011-12-19 21:37 ` Marek Vasut
2011-12-19 21:43 ` Marek Vasut
2011-12-19 23:23 ` Shawn Guo
2011-12-19 23:35 ` Marek Vasut
2011-12-20 0:19 ` Shawn Guo
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=20111219210317.GI14542@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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 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).