From: marek.vasut@gmail.com (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] sa1111: Prevent deadlock in resume path
Date: Thu, 27 May 2010 00:35:54 +0200 [thread overview]
Message-ID: <201005270035.54509.marek.vasut@gmail.com> (raw)
In-Reply-To: <20100526222530.GD16418@n2100.arm.linux.org.uk>
Dne ?t 27. kv?tna 2010 00:25:30 Russell King - ARM Linux napsal(a):
> On Wed, May 26, 2010 at 11:52:33PM +0200, Marek Vasut wrote:
> > You don't want the patch? Fine by me ... Anyway, please, open your eyes,
> > look around, noone in the whole community does such complications. Why
> > do you do that? What does it help? Why can't you just pick patches as
> > everyone else does -- from email. That's why git supports it.
>
> What you're saying is that *everyone* has to conform to your way of
> working.
Come on, you know it's not what I said.
> Sorry, the human race isn't like that. Humans are individuals,
> and each one has their own quirks.
Fine by me, there aren't many people I have problems with.
>
> Mine is that I'm dreadful at dealing with patches in email. Unless I
> deal with a message at the point I've read it, it basically doesn't
> exist.
Why don't you set up a mailbox for that ? You read the emails anyway and you can
drop the patches you Ack into that mailbox ... then run git am on that once in a
while.
> So I created the patch system 10 years ago to solve that problem
> - to keep patches around and visible, *and* to make them easier for me
> to merge.
Things changed ever since then ...
>
> So your choice is:
>
> 1. send patches by email, but have to repeatedly send them to get them
> applied.
>
> 2. send the patch to the patch system so that it's easily visible and
> doesn't get buried beneath a mountain of email.
>
> Lastly, I don't do kernel work 7 days a week.
Neither do I, nor am I paid for it. I do it in my free time.
> I do have time off when I
> don't look at the kernel tree, but I still read email. Maybe you'd
> prefer me to ignore all email on those days I'm not working instead?
See above please.
>
> The patch system is there to _solve_ a problem.
And it's there to create another one.
> If you don't want to use it, the fine, don't expect that problem to be solved
> for your patches.
The problem should be solved already. This discussion was here already, it
repeats and people complain.
>
> And now, at this point I really don't have any more time for you and
> these stupid, idiotic and childish politics.
I'm just trying to solve a real problem here.
next prev parent reply other threads:[~2010-05-26 22:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-26 19:11 [PATCH] sa1111: Prevent deadlock in resume path Marek Vasut
2010-05-26 19:14 ` Russell King - ARM Linux
2010-05-26 19:15 ` Marek Vasut
2010-05-26 20:18 ` Russell King - ARM Linux
2010-05-26 21:33 ` Marek Vasut
2010-05-26 21:42 ` Russell King - ARM Linux
2010-05-26 21:52 ` Marek Vasut
2010-05-26 22:25 ` Russell King - ARM Linux
2010-05-26 22:35 ` Marek Vasut [this message]
2010-05-27 3:49 ` Nicolas Pitre
2010-06-10 13:56 ` Pavel Machek
2010-06-10 13:56 ` Pavel Machek
2010-06-10 21:49 ` Marek Vasut
2010-06-10 21:49 ` Marek Vasut
2010-06-10 23:05 ` Russell King - ARM Linux
2010-06-10 23:05 ` Russell King - ARM Linux
2010-06-11 12:22 ` Catalin Marinas
2010-06-11 12:22 ` Catalin Marinas
2010-06-12 5:36 ` Eric Miao
2010-06-12 5:36 ` Eric Miao
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=201005270035.54509.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.