From: Tirumala Marri <tmarri@apm.com>
To: Alexander Gordeev <lasaine@lvk.cs.msu.su>
Cc: greg@kroah.com, linux-usb@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, Fushen Chen <fchen@apm.com>,
Mark Miesfeld <mmiesfeld@apm.com>
Subject: RE: [PATCH V8 04/10] USB/ppc4xx: Add Synopsys DWC OTG HCD function
Date: Mon, 7 Feb 2011 10:53:47 -0800 [thread overview]
Message-ID: <b1ca0e7cedbf942783fedb44fea7ee52@mail.gmail.com> (raw)
In-Reply-To: <20110126192743.646af6d2@desktopvm.lvknet>
}
dev_set_drvdata(_dev, dwc_otg_device);
hcd->regs = otg_dev->base;
+ hcd->rsrc_start = otg_dev->phys_addr;
+ hcd->rsrc_len = otg_dev->base_len;
hcd->self.otg_port = 1;
[Marri] Sure
prev parent reply other threads:[~2011-02-07 18:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-19 22:57 [PATCH V8 04/10] USB/ppc4xx: Add Synopsys DWC OTG HCD function tmarri
2011-01-26 16:27 ` Alexander Gordeev
2011-02-07 18:53 ` Tirumala Marri [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=b1ca0e7cedbf942783fedb44fea7ee52@mail.gmail.com \
--to=tmarri@apm.com \
--cc=fchen@apm.com \
--cc=greg@kroah.com \
--cc=lasaine@lvk.cs.msu.su \
--cc=linux-usb@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mmiesfeld@apm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).