From: Greg KH <gregkh@linuxfoundation.org>
To: Jim Lin <jilin@nvidia.com>
Cc: swarren@wwwdotorg.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/1] USB: EHCI: Tegra: Fix wrong register definition
Date: Wed, 19 Sep 2012 07:29:27 +0100 [thread overview]
Message-ID: <20120919062927.GB15492@kroah.com> (raw)
In-Reply-To: <1348026530-17327-1-git-send-email-jilin@nvidia.com>
On Wed, Sep 19, 2012 at 11:48:50AM +0800, Jim Lin wrote:
> Fix the issue that EHCI registers, hostpc[0] and usbmode_ex,
> are not correctly accessed on Tegra3 platform.
>
> Signed-off-by: Jim Lin <jilin@nvidia.com>
> ---
> Changes in v2:
> - Modify array size for reserved4[] only.
> - Note that defining hostpc[0] is for a variable-length object.
Didn't I already apply V1 of this patch? Can you now send me a fixup
given that the first patch had a problem?
thanks,
greg k-h
next prev parent reply other threads:[~2012-09-19 6:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-19 3:48 [PATCH v2 1/1] USB: EHCI: Tegra: Fix wrong register definition Jim Lin
2012-09-19 6:29 ` Greg KH [this message]
2012-09-19 7:53 ` Jim Lin
2012-09-19 8:04 ` Greg KH
2012-09-19 8:32 ` Jim Lin
2012-09-19 8:04 ` Jim Lin
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=20120919062927.GB15492@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=jilin@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=swarren@wwwdotorg.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