From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: nick <yocto6@gmail.com>
Cc: Peter Chen <Peter.Chen@freescale.com>,
"julia.lawall@lip6.fr" <julia.lawall@lip6.fr>,
"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 19:24:42 -0700 [thread overview]
Message-ID: <20140922022442.GA1710@kroah.com> (raw)
In-Reply-To: <541F86C2.80306@gmail.com>
On Sun, Sep 21, 2014 at 10:17:38PM -0400, nick wrote:
>
>
> On 14-09-21 10:11 PM, gregkh@linuxfoundation.org wrote:
> > On Sun, Sep 21, 2014 at 10:03:28PM -0400, nick wrote:
> >>
> >>
> >> On 14-09-21 07:53 PM, Peter Chen wrote:
> >>>
> >>>
> >>>> Subject: Re: FIX ME in oxu210p-hcd.c
> >>>>
> >>>>
> >>>> I found a unfixed FIX ME in the file stated in my above message. I am
> >>>> wondering what to set hcd->self.comtroller->dma_mask to as it's now been
> >>>> defined to NULL and clearly even as a newbie this seem incorrect.
> >>>> Regards Nick
> >>>
> >>> Usually, it is set at its controller driver or pass through through device tree or
> >>> platform data.
> >>>
> >>> Peter
> >>>
> >> Sorry Peter,
> >> I apologize for asking for more help here but I will paste the function below and with my changes.
> >> Please let me known if I am wrong and how to fix it as I new here.
> >> Sorry for Wasting Your Time,
> >
> > Then please do not. Just because your other email addresses were banned
> > from lkml, don't keep popping up and bothering people, it's rude, and
> > will cause this address to be banned as well.
> >
> 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
next prev parent reply other threads:[~2014-09-22 2:24 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 [this message]
2014-09-22 2:36 ` nick
2014-09-22 3:05 ` gregkh
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=20140922022442.GA1710@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Peter.Chen@freescale.com \
--cc=himangi774@gmail.com \
--cc=julia.lawall@lip6.fr \
--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.