From: Felipe Balbi <balbi@ti.com>
To: Skacore Systems <skacore.systems@gmail.com>
Cc: balbi@ti.com, linux-kernel@vger.kernel.org,
Greg KH <gregkh@suse.de>,
linux-usb@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH] s3c2410_udc: udc command always disables pull-up instead of passing the command
Date: Wed, 15 Jun 2011 11:38:12 +0300 [thread overview]
Message-ID: <20110615083811.GD31876@legolas.emea.dhcp.ti.com> (raw)
In-Reply-To: <BANLkTi==s4adWqt0uLhJHmeDe1H2RD_5Bw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 921 bytes --]
Hi,
On Wed, Jun 15, 2011 at 09:30:00AM +0200, Skacore Systems wrote:
> I don't care much about pushing this into mainline. It's a bug and
> it's up to kernel developers to fix that.
> I was aware that kernel devs are bunch of lazy dicks and I'm not going
> to do more work for one line patch.
You are the lazy dick here. All I asked was to follow our standards, do
you have any idea how many patches each kernel maintainer has to go
through ? It doesn't scale if we have to re-format the ugly crap you
send us.
Get over yourself and if you want this fixed, then send a proper patch.
It's just a small set of instructions we are asking you to follow, try
saying the same to your Income Tax office and see if they'll like that
you didn't follow their instructions.
Lazy dicks... hah... the one who can't get a simple set of instructions
right is calling us lazy dicks. What a prick!
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2011-06-15 8:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BANLkTimU+E8Y0_9+H2nsF6CMg66_TDH0LQ@mail.gmail.com>
[not found] ` <BANLkTimL=+vaa7NB5FW192rZd08Gv-Z-OA@mail.gmail.com>
2011-06-14 14:58 ` Skacore Systems
2011-06-14 16:49 ` Felipe Balbi
2011-06-15 7:30 ` Skacore Systems
2011-06-15 8:38 ` Felipe Balbi [this message]
2011-06-15 8:43 ` Skacore Systems
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=20110615083811.GD31876@legolas.emea.dhcp.ti.com \
--to=balbi@ti.com \
--cc=gregkh@suse.de \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=skacore.systems@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®