From: viliam.mateicka@gmail.com (Viliam Mateicka)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] s3c2410_udc: fix custom UDC command handling
Date: Mon, 20 Jun 2011 19:27:18 +0200 [thread overview]
Message-ID: <BANLkTinc-9hxLQ1Epf5=PoHvxtapfO7Vvg@mail.gmail.com> (raw)
In-Reply-To: <20110620170551.GE26623@legolas.emea.dhcp.ti.com>
I wonder then, who applies the patch first. One ass can't stop
progress (was there some progress afterall ?) because of one
line-break (which git produces by default afterall) and several
non-conforming whitespace conversions. I think you should stop
replying to me, because I'm kinda starting to like trolling afterall.
Vilo
On Mon, Jun 20, 2011 at 7:05 PM, Felipe Balbi <balbi@ti.com> wrote:
> Hi,
>
> On Mon, Jun 20, 2011 at 06:41:59PM +0200, Skacore Systems wrote:
>> Yeah I think that one line break and tabs are sabotaging your work.
>> So stop being an 8====O - hole. No wonder if you are paid by TI that
>> one line patch into the upstream takes you so long to comprehend.
>
> you are this close for me to drop your fix and add you to the shitlist.
>
> --
> balbi
>
next prev parent reply other threads:[~2011-06-20 17:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-16 8:04 [PATCH] s3c2410_udc: fix custom UDC command handling Viliam Mateicka
2011-06-20 8:25 ` Viliam Mateicka
2011-06-20 15:07 ` Alan Stern
2011-06-20 15:15 ` Felipe Balbi
2011-06-20 15:20 ` Skacore Systems
2011-06-20 15:36 ` Felipe Balbi
2011-06-20 15:48 ` Skacore Systems
2011-06-20 15:57 ` Skacore Systems
2011-06-20 16:06 ` Felipe Balbi
2011-06-20 16:41 ` Skacore Systems
2011-06-20 17:05 ` Felipe Balbi
2011-06-20 17:27 ` Viliam Mateicka [this message]
2011-06-20 17:34 ` Felipe Balbi
2011-06-20 19:05 ` Viliam Mateicka
2011-06-20 16:07 ` Jassi Brar
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='BANLkTinc-9hxLQ1Epf5=PoHvxtapfO7Vvg@mail.gmail.com' \
--to=viliam.mateicka@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 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).