-Original Message-
From: Shawn Guo [mailto:shawn@freescale.com]
Sent: Tuesday, July 22, 2014 10:32 AM
To: Stefan Agner; Lu Jingchang-B35083
Cc: Chen Peter-B29397; s.ha...@pengutronix.de; linux-arm-
ker...@lists.infradead.org; linux-usb@vger.kernel.org; linux-
ker...@vger.kernel.org
On 09/23/13 22:23, Paul Zimmerman wrote:
Here is the third version of the microframe scheduler patch. This
version removes the NAK holdoff patch from the series, since it
was effectively a no-op as pointed out by Matthijs.
I think there was a misunderstanding here - Matthijs was pointing out
Hi,
Felipe Balbi wrote:
On Fri, Jul 18, 2014 at 11:31:30AM +0200, Lothar Waßmann wrote:
There is no need to throw the baby out with the bath due to a bad
failure analysis. The commit:
7adb5c876e9c usb: musb: Fix panic upon musb_am335x module removal
came to a wrong conclusion about the
Hi,
Felipe Balbi wrote:
Hi,,
On Mon, Jul 21, 2014 at 10:03:07AM +0200, Lothar Waßmann wrote:
Hi,
On Fri, Jul 18, 2014 at 11:31:29AM +0200, Lothar Waßmann wrote:
This patch makes it possible to use the musb driver with HW that
requires external regulators or clocks.
can
Hello Jim Baxter,
This is a semi-automatic email about new static checker warnings.
The patch 6d3865f9d41f: usb: gadget: NCM: Add transmit multi-frame.
from Jul 7, 2014, leads to the following Smatch complaint:
drivers/usb/gadget/function/u_ether.c:570 eth_start_xmit()
error: we
Add devicetree bindings for Xilinx udc driver.
Signed-off-by: Subbaraya Sundeep Bhatta sbha...@xilinx.com
---
Changes for v4:
- renamed xlnx,axi-usb2-device-4.00.a to xlnx,usb2-device-4.00.a
Changes for v3:
- None
Changes for v2:
- replaced xlnx,include-dma with
Hi Lee,
Thanks for reviewing, see my comments inline below: -
On Mon, 07 Jul 2014, Lee Jones wrote:
On Sat, 05 Jul 2014, Peter Griffin wrote:
This patch adds the ST glue logic to manage the DWC3 HC
on STiH407 SoC family. It manages the powerdown signal,
and configures the internal glue
Hi Jingoo,
Sorry for the delay in replying. Thanks for reviewing,
see my comments inline below: -
snip
+#include linux/module.h
+#include linux/kernel.h
+#include linux/slab.h
+#include linux/interrupt.h
+#include linux/platform_device.h
+#include linux/ioport.h
+#include
Am 2014-07-22 04:22, schrieb Shawn Guo:
On Fri, Jul 18, 2014 at 07:01:37PM +0200, Stefan Agner wrote:
This adds USB PHY and USB controller nodes. Vybrid SoCs have two
independent USB cores which each supports DR (dual role). However,
real OTG is not supported since the OTG ID pin is not
On 07/22/2014 02:38 PM, Subbaraya Sundeep Bhatta wrote:
+#include linux/delay.h
+#include linux/device.h
+#include linux/dma-mapping.h
+#include gadget_chips.h
+#include linux/interrupt.h
+#include linux/io.h
+#include linux/module.h
+#include linux/of_address.h
+#include linux/of_device.h
Thanks for reviewing, see my comments inline below: -
In future, it's best to only reply to questions, or review comments
that you disagree with. Anything that you will action or agree with
can be snipped along with any irrelevant code from your reply and
replaced with snip or [...]. If you
Hello Sarah,
I would like to draw attention to another potential problem which concerns
combination of USB ethernet and xHCI driver in Linux kernel. I have serious
problem with D-Link USB 3.0 Gigabit Ethernet Adapter DUB-1312. I am not
able to assign the IPv4 address through DHCP client
I would like to draw attention to another potential problem which concerns
combination of USB ethernet and xHCI driver in Linux kernel. I have serious
problem with D-Link USB 3.0 Gigabit Ethernet Adapter DUB-1312. I am not
able to assign the IPv4 address through DHCP client or even manually
On Tue, Jul 22, 2014 at 11:57:31AM +0200, Stefan Agner wrote:
Am 2014-07-22 04:22, schrieb Shawn Guo:
On Fri, Jul 18, 2014 at 07:01:37PM +0200, Stefan Agner wrote:
This adds USB PHY and USB controller nodes. Vybrid SoCs have two
independent USB cores which each supports DR (dual role).
Hi David,
thank you very much for your explanation. My answers to your questions
follow:
* Yes, I have ASMedia ASM1042 SuperSpeed USB Host (XHCI) Controller
in my computer.
* Yes, D-Link DUB-1312 is using asix88179_178a linux kernel driver.
Based on information from you it seems that my
From: Marek Uher
Hi David,
thank you very much for your explanation. My answers to your questions
follow:
* Yes, I have ASMedia ASM1042 SuperSpeed USB Host (XHCI) Controller
in my computer.
* Yes, D-Link DUB-1312 is using asix88179_178a linux kernel driver.
Based on information
Hi Felipe,
Sorry for the delay in replying. I've been trying to get to the root cause
of this problem so I could reply which took longer than I had hoped.
The problem manifested itself as a hang on register read/write access if
dwc3-st
probed before the usb3 phy. Even though dwc3 core would
Hi Alan,
Most platform drivers have already been moved.
Okay, I grant the point. Objections withdrawn. Fix up the spelling
error and the other stuff in the Kconfig help text, and this will be
acceptable.
Thanks, I intend to send a new version shortly.
regards,
Peter.
--
To
Hi David,
that's not good news. I have three same computers with ASMedia USB
Host XHCI Controller. I have also three same D-Link DUB-1312 adapters.
Now I can throw them out of the window. I am afraid that these bugs anyone
will fixed soon. It looks like another never ending story. In any case
Hello,
This device works perfectly with usbserial generic, loaded with forced
vendor/product parameters. Can you please add it to the proper driver?
T: Bus=02 Lev=01 Prnt=01 Port=05 Cnt=02 Dev#= 7 Spd=480 MxCh= 0
D: Ver= 2.00 Cls=ff(vend.) Sub=02 Prot=01 MxPS=64 #Cfgs= 2
P: Vendor=03f0
On 07/18/2014 05:09 PM, Hans de Goede wrote:
When using a Renesas uPD720231 chipset usb-3 uas to sata bridge with a 120G
Crucial M500 ssd, model string: Crucial_ CT120M500SSD1, together with a
the integrated Intel xhci controller on a Haswell laptop:
00:14.0 USB controller [0c03]: Intel
On Tue, Jul 22, 2014 at 10:06:13AM +0200, Lothar Waßmann wrote:
Hi,
Felipe Balbi wrote:
Hi,,
On Mon, Jul 21, 2014 at 10:03:07AM +0200, Lothar Waßmann wrote:
Hi,
On Fri, Jul 18, 2014 at 11:31:29AM +0200, Lothar Waßmann wrote:
This patch makes it possible to use the musb
Hi,
On Tue, Jul 22, 2014 at 10:18:00AM +0100, Peter Griffin wrote:
+static inline u32 st_dwc3_readl(void __iomem *base, u32 offset)
+{
+ return readl_relaxed(base + offset);
+}
+
+static inline void st_dwc3_writel(void __iomem *base, u32 offset, u32
value)
+{
+
On Tue, Jul 22, 2014 at 09:49:30AM +0200, Lothar Waßmann wrote:
Hi,
Felipe Balbi wrote:
On Fri, Jul 18, 2014 at 11:31:30AM +0200, Lothar Waßmann wrote:
There is no need to throw the baby out with the bath due to a bad
failure analysis. The commit:
7adb5c876e9c usb: musb: Fix panic
Hi Marek,
I'm Ccing Mathias Nyman, who is the new xHCI driver maintainer. He can
help you look into the issue with the AsMedia host controller. Is there
any chance these are desktop systems? If so, you could get a Rensas
PCIe add-in card that will better than the AsMedia host under Linux.
The
On Tue, Jul 22, 2014 at 02:55:34PM +0100, Peter Griffin wrote:
Hi Felipe,
Sorry for the delay in replying. I've been trying to get to the root cause
of this problem so I could reply which took longer than I had hoped.
The problem manifested itself as a hang on register read/write access if
+static void st_dwc3_init(struct st_dwc3 *dwc3_data)
+{
+ u32 reg = st_dwc3_readl(dwc3_data-glue_base, USB2_CLKRST_CTRL);
+
+ reg |= aux_clk_en(1) | ext_cfg_reset_n(1) | xhci_revision(1);
+ reg = ~sw_pipew_reset_n(1);
1? Better to add defines for
On Tue, Jul 22, 2014 at 04:45:03PM +0100, Lee Jones wrote:
+static void st_dwc3_init(struct st_dwc3 *dwc3_data)
+{
+ u32 reg = st_dwc3_readl(dwc3_data-glue_base, USB2_CLKRST_CTRL);
+
+ reg |= aux_clk_en(1) | ext_cfg_reset_n(1) | xhci_revision(1);
+ reg =
On Tue, 22 Jul 2014, Felipe Balbi wrote:
On Tue, Jul 22, 2014 at 04:45:03PM +0100, Lee Jones wrote:
+static void st_dwc3_init(struct st_dwc3 *dwc3_data)
+{
+ u32 reg = st_dwc3_readl(dwc3_data-glue_base, USB2_CLKRST_CTRL);
+
+ reg |= aux_clk_en(1) |
hi Paul
My questions are
1. The xhci controller seems not handle the normal TRB for short package.
as you can see the length of event package for normal package is 0.
am I correct?
2. if above #1 is correct, how xhci controller get the left 0x6f8 data
in original normal package?
On 07/04/2014 07:43 AM, Takashi Iwai wrote:
At Thu, 3 Jul 2014 20:15:28 +0200,
Sebastian Reimers wrote:
The pcm playback and capture sample size format was fixed
SNDRV_PCM_FMTBIT_S16_LE.
This patch respects also 16, 24 and 32 bit p_ssize and c_ssize values.
Signed-off-by: Sebastian
On Tue, Jul 22, 2014 at 07:09:51PM +0200, Daniel Mack wrote:
On 07/04/2014 07:43 AM, Takashi Iwai wrote:
At Thu, 3 Jul 2014 20:15:28 +0200,
Sebastian Reimers wrote:
The pcm playback and capture sample size format was fixed
SNDRV_PCM_FMTBIT_S16_LE.
This patch respects also 16, 24
From: Nick Hudson [mailto:sk...@netbsd.org]
Sent: Tuesday, July 22, 2014 12:19 AM
On 09/23/13 22:23, Paul Zimmerman wrote:
Here is the third version of the microframe scheduler patch. This
version removes the NAK holdoff patch from the series, since it
was effectively a no-op as pointed
uac1 function is missing strings. Add them.
Signed-off-by: Andrzej Pietrasiewicz andrze...@samsung.com
---
drivers/usb/gadget/function/f_uac1.c | 51 +++-
1 file changed, 50 insertions(+), 1 deletion(-)
diff --git a/drivers/usb/gadget/function/f_uac1.c
Integrating configfs requires converting f_uac1 to new function interface,
which in turn requires converting it to the new function interface,
which involves separate compilation of f_uac1.c into usb_f_uac1.ko.
u_uac1.c contains some module parameters. After this patch is applied
they are still a
There are no users of the old interface left, so it can be removed.
Signed-off-by: Andrzej Pietrasiewicz andrze...@samsung.com
---
drivers/usb/gadget/function/f_uac2.c | 124 ---
1 file changed, 124 deletions(-)
diff --git a/drivers/usb/gadget/function/f_uac2.c
Eliminate static struct *agdev_g from f_uac2.c.
It is used for freeing its memory, but the same address can be found
by calling container_of in afunc_unbind(). This implies eliminating
uac2_unbind_config(). The audio_config_driver in audio.c does not have
its unbind method any more. It has been
Use the new interface so that the old one can be removed.
Signed-off-by: Andrzej Pietrasiewicz andrze...@samsung.com
---
drivers/usb/gadget/legacy/Kconfig | 1 +
drivers/usb/gadget/legacy/audio.c | 69 +++
2 files changed, 64 insertions(+), 6 deletions(-)
There are no users of the old interface left, so it can be removed.
Signed-off-by: Andrzej Pietrasiewicz andrze...@samsung.com
---
drivers/usb/gadget/function/f_uac1.c | 102 +--
drivers/usb/gadget/function/u_uac1.c | 33
Converting uac1 to the new function interface requires converting
the USB uac1's function code and its users.
This patch converts the f_uac1.c to the new function interface.
The file is now compiled into a separate usb_f_uac1.ko module.
The old function interface is provided by means of a
This series aims at integrating configfs into the audio gadget, the way
it has been done for acm, ncm, ecm, eem, ecm subset, rndis, obex, phonet,
mass_storage, FunctionFS, loopback, sourcesink; rfc for uvc has also been
sent. It contains everything that is required to provide the
equivalent of
Use the new interface so that the old one can be removed.
Signed-off-by: Andrzej Pietrasiewicz andrze...@samsung.com
---
drivers/usb/gadget/legacy/Kconfig | 1 +
drivers/usb/gadget/legacy/audio.c | 85 ++-
2 files changed, 84 insertions(+), 2 deletions(-)
Use the new usb_gstring_attach interface.
Signed-off-by: Andrzej Pietrasiewicz andrze...@samsung.com
---
drivers/usb/gadget/function/f_uac1.c | 30 --
1 file changed, 12 insertions(+), 18 deletions(-)
diff --git a/drivers/usb/gadget/function/f_uac1.c
Converting uac2 to the new function interface requires converting
the USB uac2's function code and its users.
This patch converts the f_uac2.c to the new function interface.
The file is now compiled into a separate usb_f_uac2.ko module.
The old function interface is provided by means of a
Add support for using f_uac1 function as a component of a gadget
composed with configfs.
Signed-off-by: Andrzej Pietrasiewicz andrze...@samsung.com
---
Documentation/ABI/testing/configfs-usb-gadget-uac1 | 12 ++
drivers/usb/gadget/function/f_uac1.c | 158 +
When configfs is integrated the same values will have to be used
as defaults. Use symbolic names in order not to duplicate magic numbers.
Signed-off-by: Andrzej Pietrasiewicz andrze...@samsung.com
---
drivers/usb/gadget/function/u_uac2.h | 7 +++
drivers/usb/gadget/legacy/audio.c| 16
When configfs support is added the values in question will have to be
used in two different places. Substitute them with defined constants
to avoid duplicating magic numbers.
Signed-off-by: Andrzej Pietrasiewicz andrze...@samsung.com
---
drivers/usb/gadget/function/f_uac1.c | 4 +---
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/22/2014 07:44 PM, Felipe Balbi wrote:
On Tue, Jul 22, 2014 at 07:09:51PM +0200, Daniel Mack wrote:
On 07/04/2014 07:43 AM, Takashi Iwai wrote:
At Thu, 3 Jul 2014 20:15:28 +0200, Sebastian Reimers wrote:
The pcm playback and capture sample
Use the new usb_gstring_attach interface.
Signed-off-by: Andrzej Pietrasiewicz andrze...@samsung.com
---
drivers/usb/gadget/function/f_uac2.c | 33 +
1 file changed, 17 insertions(+), 16 deletions(-)
diff --git a/drivers/usb/gadget/function/f_uac2.c
Add support for using f_uac2 function as a component of a gadget
composed with configfs.
Signed-off-by: Andrzej Pietrasiewicz andrze...@samsung.com
---
Documentation/ABI/testing/configfs-usb-gadget-uac2 | 12 +++
drivers/usb/gadget/function/f_uac2.c | 105 +
On Tue, 22 Jul 2014 18:46:27 +0100, Paul Zimmerman
paul.zimmer...@synopsys.com wrote:
From: Nick Hudson [mailto:sk...@netbsd.org]
Sent: Tuesday, July 22, 2014 12:19 AM
On 09/23/13 22:23, Paul Zimmerman wrote:
Here is the third version of the microframe scheduler patch. This
version removes
From: vichy [mailto:vichy@gmail.com]
Sent: Tuesday, July 22, 2014 9:27 AM
My questions are
1. The xhci controller seems not handle the normal TRB for short package.
as you can see the length of event package for normal package is 0.
am I correct?
2. if above #1 is correct, how
This PHY, though formally being a part of Renesas USBHS controller, contains the
UGCTRL2 register that controls multiplexing of the USB ports (Renesas calls them
channels) to the different USB controllers: channel 0 can be connected to either
PCI EHCI/OHCI or USBHS controllers, channel 2 can be
On Sun, 22 Jun 2014, Toralf Förster wrote:
On 06/20/2014 10:53 PM, Alan Stern wrote:
You mean 3.15 plus the patch I sent?
tfoerste@n22 ~/tmp $ sudo su -
n22 ~ # cat /sys/kernel/debug/usb/usbmon/2u /tmp/right
^C
n22 ~ # cat /sys/kernel/debug/usb/usbmon/2u /tmp/wrong
^C
Hello.
Here's the set of 2 patches against Simon Horman's 'renesas.git' repo,
'renesas-devel-v3.16-rc5-20140722' tag. Here we add the USB PHY device tree
support on the R8A7790/Lager reference board. The patchset requires the USB PHY
driver (just re-posted) in order to work.
[1/2] ARM
Define the R8A7790 generic part of the USB PHY device node. It is up to the
board file to enable the device.
Signed-off-by: Sergei Shtylyov sergei.shtyl...@cogentembedded.com
---
Changes in version 3:
- changed subnodes of the USB PHY node to be per-channel;
- changed renesas,phy-select property
Enable USB PHY device for the Lager board.
Signed-off-by: Sergei Shtylyov sergei.shtyl...@cogentembedded.com
---
Changes in version 3:
- refreshed the patch.
Changes in version 2:
- refreshed the patch.
arch/arm/boot/dts/r8a7790-lager.dts |4
1 file changed, 4 insertions(+)
Index:
Hello.
Here's the set of 3 patches against Simon Horman's 'renesas.git' repo,
'renesas-devel-v3.16-rc5-20140722' tag. Here we add the USB PHY device tree
support on the R8A7791/Koelsch/Henninger boards. The patchset requires the USB
PHY driver (just re-posted) in order to work.
[1/3] ARM
Define the R8A7791 generic part of the USB PHY device node. It is up to the
board file to enable the device.
Signed-off-by: Sergei Shtylyov sergei.shtyl...@cogentembedded.com
---
Changes in version 3:
- changed subnodes of the USB PHY node to be per-channel;
- changed renesas,phy-select property
Enable USB PHY device for the Koelsch board.
Signed-off-by: Sergei Shtylyov sergei.shtyl...@cogentembedded.com
---
Changes in version 3:
- refreshed the patch.
Changes in version 2:
- fixed the wrong board name in the changelog;
- refreshed the patch.
arch/arm/boot/dts/r8a7791-koelsch.dts |
On 07/22/14 18:46, Paul Zimmerman wrote:
The nak_frame handling would have added some benefit, but wouldn't handle all
cases.
I'm seeing problems with devices NAKing to the point of confusing dwc2
completely,
so I'd like to investigate a NAK holdoff scheme that's acceptable for dwc2. I
Enable USB PHY device for the Henninger board.
Signed-off-by: Sergei Shtylyov sergei.shtyl...@cogentembedded.com
---
Changes in version 3:
- refreshed the patch.
arch/arm/boot/dts/r8a7791-henninger.dts |4
1 file changed, 4 insertions(+)
Index:
Hi,
On Wed, Jul 9, 2014 at 5:17 AM, Antoine Ténart
antoine.ten...@free-electrons.com wrote:
Before using the PHY framework instead of the USB PHY one, we need to
move the OTG state into another place, since it won't be available when
USB PHY isn't used. This patch moves the OTG state into the
Add the generic PHY support, analogous to the USB PHY support. Intended it to be
used with the PCI EHCI/OHCI drivers and the xHCI platform driver.
Signed-off-by: Sergei Shtylyov sergei.shtyl...@cogentembedded.com
Signed-off-by: Yoshihiro Shimoda yoshihiro.shimoda...@renesas.com
---
This patch is
Describe the PCI USB devices that are behind the PCI bridges, adding necessary
links to the USB PHY device.
Signed-off-by: Sergei Shtylyov sergei.shtyl...@cogentembedded.com
---
This patch is against 'renesas-devel-v3.16-rc5-20140722' tag of Simon Horman's
'renesas.git' repo plus R8A7791/Koelsch
Hello,
I'm experiencing the following issue which I'd like to help resolve.
I have no previous experience with linux usb or input systems but I'm
a competent C / C++ developer. I'll split the info over a couple of
mails.
Please let me know if there's any other information or action that I
can
-20140722' tag of Simon Horman's
'renesas.git' repo plus R8A7790/Lager USB PHY support patches posted before.
The patch requires the USB PHY driver, and USB HCD generic PHY support (also
already posted) in order to work.
Changes in version 3:
- adjusted phys properties in the PCI OHCI/EHCI device nodes
On Wed, Jul 23, 2014 at 08:39:56AM +1000, Daniel Heckenberg wrote:
Hello,
I'm experiencing the following issue which I'd like to help resolve.
I have no previous experience with linux usb or input systems but I'm
a competent C / C++ developer. I'll split the info over a couple of
mails.
xinput -list
⎡ Virtual core pointerid=2[master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)]
⎜ ↳ Wacom ISDv4 EC Pen stylus id=9[slave pointer (2)]
⎜ ↳ Atmel Atmel maXTouch Digitizer
Try sending this to the linux-in...@vger.kernel.org mailing list.
Hi Greg,
Thanks for the response. As I mentioned in the summary, I have sent
this to linux-input but haven't received any reponses there. I'm
happy to dig into this myself but would appreciate any pointers for
where to start.
On Wed, Jul 23, 2014 at 08:54:46AM +1000, Daniel Heckenberg wrote:
Try sending this to the linux-in...@vger.kernel.org mailing list.
Hi Greg,
Thanks for the response. As I mentioned in the summary, I have sent
this to linux-input but haven't received any reponses there. I'm
happy to
On Wed, Jul 23, 2014 at 9:06 AM, Greg KH g...@kroah.com wrote:
On Wed, Jul 23, 2014 at 08:54:46AM +1000, Daniel Heckenberg wrote:
Try sending this to the linux-in...@vger.kernel.org mailing list.
Hi Greg,
Thanks for the response. As I mentioned in the summary, I have sent
this to
This patch adds usb quirks to improve support for devices
with non standard bInterval values. Quirks are added to support devices with
bInterval values expressed as microframes or frames. The quirks cause the
parse endpoint function to modify the reported bInterval to the standards
conforming
Hi,
I am not familiar with git or code writting, I have no idea where to
start.
I was reporting the issue so hopefully someone with a clue who had one
of these dongles might look to see if they experience this and know how
to resolve it, if I cant figure it out, might have to go back to 3.12,
On Wed, Jul 23, 2014 at 10:05:23AM +1000, ress...@ausics.net wrote:
Hi,
I am not familiar with git or code writting, I have no idea where to start.
You installed your own kernels from kernel.org, right?
If so, you have git, and you can read the documentation on 'git bisect'
for how to do this
On Tue, Jul 22, 2014 at 08:02:10PM -0400, James P Michels III wrote:
This patch adds usb quirks to improve support for devices
with non standard bInterval values. Quirks are added to support devices with
bInterval values expressed as microframes or frames. The quirks cause the
parse
I do believe that I did.
+ /* Razer - Razer Blade Keyboard */
+ { USB_DEVICE(0x1532, 0x0116), .driver_info =
+ USB_QUIRK_INTERVAL_AS_MICROFRAMES },
+
Am I missing something still?
Regards
Jim
On Tue, Jul 22, 2014 at 8:17 PM, Greg KH g...@kroah.com wrote:
On
On 07/18/2014 10:52 PM, Nick Krause wrote:
On Fri, Jul 18, 2014 at 10:45 PM, Nick Krause xerofo...@gmail.com wrote:
Sorry didn't run spell check. I will resend this patch with the
correct information
as needed. Thanks for the advice, Sasha.
Cheers Nick
On Fri, Jul 18, 2014 at 10:36 PM,
I think I understand your concern now. You mean that I am only adding
a quirk for the devices with their interval reported as microframes.
After reading the code comments about many other vendors having
similar issues, I thought it was more complete, and potentially less
confusing, for the
On 2014-07-23 04:17, Dan Williams wrote:
On Tue, 2014-07-22 at 14:02 +, Stanescu Victor wrote:
Hello,
This device works perfectly with usbserial generic, loaded with forced
vendor/product parameters. Can you please add it to the proper driver?
T: Bus=02 Lev=01 Prnt=01 Port=05 Cnt=02
On Tue, Jul 22, 2014 at 8:44 PM, Sasha Levin sas...@kernel.org wrote:
On 07/18/2014 10:52 PM, Nick Krause wrote:
On Fri, Jul 18, 2014 at 10:45 PM, Nick Krause xerofo...@gmail.com wrote:
Sorry didn't run spell check. I will resend this patch with the
correct information
as needed. Thanks for
81 matches
Mail list logo
