From: Sarah Sharp <sarah.a.sharp@linux.intel.com>
To: Aman Deep <amandeep3986@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@suse.de>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] xHCI: Adding #define values used for hub descriptor
Date: Wed, 23 Nov 2011 09:00:06 -0800 [thread overview]
Message-ID: <20111123170006.GB5792@xanatos> (raw)
In-Reply-To: <CAJ54Ua4HgcDkWrcgVHNtNBmwgHh+Swn_Q2kKGLKS5+d94g07kQ@mail.gmail.com>
On Wed, Nov 23, 2011 at 10:20:10AM +0530, Aman Deep wrote:
> Hi Sarah,
>
>
> > >
> > > Also use some #defines in places where magic numbers are being used.
> >
> > Looks fine to me for the xHCI changes. I copied most of the hub
> > descriptor code from EHCI, so it will need the same treatment.
>
> Okay, thanks. I will try to make some of these changes into other host
> controller drivers also as
> soon as I can.
>
> >
> > Acked-by: Sarah Sharp <sarah.a.sharp@linux.intel.com>
>
> Thanks for the ACK, Sarah.
>
> >
> > The #defines look a bit odd to me, like you're using spaces instead of
> > tabs to separate the name and value, or your mail program is converting
> > tabs to spaces. Do the numbers line up for you?
>
> Actually, both the HUB_CHAR_TTTT and HUB_CHAR_PORTIND were already using
> spaces instead of tabs. I just copied them to the lines below, thats
> why they still have
> spaces between define and value.
>
> But thanks for info. I will take more care about this in future.
>
> Do you want me to make any changes in this patch ?
Fixing them up to have tabs instead of spaces would be nice, but is not
required. :)
Sarah Sharp
next prev parent reply other threads:[~2011-11-23 17:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-22 14:03 [PATCH 1/1] xHCI: Adding #define values used for hub descriptor Aman Deep
2011-11-22 16:26 ` Alan Stern
2011-11-23 5:02 ` Aman Deep
2011-11-22 19:57 ` Sarah Sharp
2011-11-23 4:50 ` Aman Deep
2011-11-23 17:00 ` Sarah Sharp [this message]
2011-11-27 3:49 ` Greg KH
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=20111123170006.GB5792@xanatos \
--to=sarah.a.sharp@linux.intel.com \
--cc=amandeep3986@gmail.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.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