All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Vishal Nandanwar <operational.people@gmail.com>
Cc: Alan Stern <stern@rowland.harvard.edu>,
	Linux USB <linux-usb@vger.kernel.org>,
	Linux Docs <linux-doc@vger.kernel.org>,
	Platform driver x86 <platform-driver-x86@vger.kernel.org>
Subject: Re: Need help to understand USB driver mechanism
Date: Fri, 22 Jun 2012 06:42:16 -0700	[thread overview]
Message-ID: <20120622134216.GC3330@kroah.com> (raw)
In-Reply-To: <CAKB833m3sSv4RnrbJN2U1Jh4OiWe5fnCk=HwHEe3UDXtQGkqvA@mail.gmail.com>


A: No.
Q: Should I include quotations after my reply?

http://daringfireball.net/2007/07/on_top

On Fri, Jun 22, 2012 at 08:33:50AM +0530, Vishal Nandanwar wrote:
> Yes, I am reading it simultaneously.
> 
> But to do hands on, which driver one should try as mass storage driver
> (for pen driver) is very difficult.

Yes, the mass-storage driver is one of the most complex, please stay
away from it unless you understand SCSI very well.

As for what one to pick, I do not know, that is your own choice, not
mine.

good luck,

greg k-h

  reply	other threads:[~2012-06-22 13:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-21 10:39 Need help to understand USB driver mechanism Vishal Nandanwar
     [not found] ` <CAKB833mPfX2U6_UA0Fr0CTw623gxCvcYPW3HvfVJWE1Xt7v-UQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-06-21 14:40   ` Alan Stern
     [not found]     ` <Pine.LNX.4.44L0.1206211036540.1164-100000-IYeN2dnnYyZXsRXLowluHWD2FQJk+8+b@public.gmane.org>
2012-06-22  2:05       ` Vishal Nandanwar
     [not found]         ` <CAKB833k1Q7LoJWxDp6AHdq5H=w=LeeeRQ3sRC_1zXcJ_Lp9mNg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-06-22  2:25           ` Greg KH
2012-06-22  3:03             ` Vishal Nandanwar
2012-06-22 13:42               ` Greg KH [this message]
2012-06-22 13:48         ` Alan Stern

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=20120622134216.GC3330@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=operational.people@gmail.com \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    /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.