Hi,
On 04-05-15 23:35, Simon Glass wrote:
On 4 May 2015 at 15:35, Simon Glass s...@chromium.org wrote:
Hi Hans,
On 4 May 2015 at 14:28, Simon Glass s...@chromium.org wrote:
On 4 May 2015 at 11:19, Hans de Goede hdego...@redhat.com wrote:
Currently we copy over a number of usb_device values
Currently we copy over a number of usb_device values stored in the on stack
struct usb_device probed in usb_scan_device() to the final driver-model managed
struct usb_device in usb_child_pre_probe() through usb_device_platdata, and
then call usb_select_config() to fill in the rest.
There are 3
Hi Hans,
On 4 May 2015 at 14:28, Simon Glass s...@chromium.org wrote:
On 4 May 2015 at 11:19, Hans de Goede hdego...@redhat.com wrote:
Currently we copy over a number of usb_device values stored in the on stack
struct usb_device probed in usb_scan_device() to the final driver-model
managed
On 4 May 2015 at 15:35, Simon Glass s...@chromium.org wrote:
Hi Hans,
On 4 May 2015 at 14:28, Simon Glass s...@chromium.org wrote:
On 4 May 2015 at 11:19, Hans de Goede hdego...@redhat.com wrote:
Currently we copy over a number of usb_device values stored in the on stack
struct usb_device
On 4 May 2015 at 11:19, Hans de Goede hdego...@redhat.com wrote:
Currently we copy over a number of usb_device values stored in the on stack
struct usb_device probed in usb_scan_device() to the final driver-model
managed
struct usb_device in usb_child_pre_probe() through usb_device_platdata,
5 matches
Mail list logo
