From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: nick <yocto6@gmail.com>
Cc: "oneukum@suse.de" <oneukum@suse.de>,
"himangi774@gmail.com" <himangi774@gmail.com>,
"stern@rowland.harvard.edu" <stern@rowland.harvard.edu>,
"paul.gortmaker@windriver.com" <paul.gortmaker@windriver.com>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: FIX ME in oxu210p-hcd.c
Date: Sun, 21 Sep 2014 20:05:50 -0700 [thread overview]
Message-ID: <20140922030550.GA20013@kroah.com> (raw)
In-Reply-To: <541F8B22.9010006@gmail.com>
Damm, didn't configure my kill-file correctly, and this snuck in, so
might as well respond...
On Sun, Sep 21, 2014 at 10:36:18PM -0400, nick wrote:
> On 14-09-21 10:24 PM, gregkh@linuxfoundation.org wrote:
> >> Sorry Greg,
> >> I don't want to get banned again. I was trying to help out and learn, I was apologizing not
> >> for wasting time as much as for making sure I wasn't wasting maintainer time again. I also
> >> am coming to the conclusion that my terrible patches were a waste of time and I am trying
> >> to get back into helping out.
> >
> > You were asked to finish the Eudyptula challenge before bothering any
> > other kernel developers with questions / patches. Until that happens,
> > you are in my killfile, now with yet-another-email-address.
> >
> Greg K-H,
> I really don't want you to get any more upset with me then you already are. The reason I gave up on the
> challenge was it was mostly driver based and I wanted to learn more in other areas. If you would like to
> discuss with me your concerns about my work on this list and how I can aid more please let me known.
You stopped so early in the challenge, you really have no idea what it
is "mostly" about, so don't make rash statements like that.
Again, unless you finish it, you will be ignored by me, and probably by
everyone else as well.
greg k-h
prev parent reply other threads:[~2014-09-22 3:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <541DB6BF.7090909@gmail.com>
2014-09-20 17:26 ` FIX ME in oxu210p-hcd.c nick
2014-09-21 23:53 ` Peter Chen
2014-09-22 2:03 ` nick
2014-09-22 2:11 ` Peter Chen
2014-09-22 2:33 ` nick
2014-09-22 2:11 ` gregkh
2014-09-22 2:17 ` nick
2014-09-22 2:24 ` gregkh
2014-09-22 2:36 ` nick
2014-09-22 3:05 ` gregkh [this message]
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=20140922030550.GA20013@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=himangi774@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=oneukum@suse.de \
--cc=paul.gortmaker@windriver.com \
--cc=stern@rowland.harvard.edu \
--cc=yocto6@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 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.