On Mon, 2014-02-10 at 16:54 +0100, Emil Goode wrote:
Since the checks that need to be added in various places are all in
the same subsystem I think it could be done in as little as one patch?
Yes, please definitely. Best for bisectability.
If nobody have any objections I will try removing
Hi Hans,
On 02/07/2014 05:36 PM, Hans de Goede wrote:
Currently ehci-platform is only used in combination with devicetree when used
with some Via socs. By extending it to (optionally) get clks and a phy from
devicetree, and enabling / disabling those on power_on / off, it can be used
more
Hi,
On 02/11/2014 10:12 AM, Roger Quadros wrote:
Hi Hans,
On 02/07/2014 05:36 PM, Hans de Goede wrote:
Currently ehci-platform is only used in combination with devicetree when used
with some Via socs. By extending it to (optionally) get clks and a phy from
devicetree, and enabling /
On 02/11/2014 11:31 AM, Hans de Goede wrote:
Hi,
On 02/11/2014 10:12 AM, Roger Quadros wrote:
Hi Hans,
On 02/07/2014 05:36 PM, Hans de Goede wrote:
Currently ehci-platform is only used in combination with devicetree when
used
with some Via socs. By extending it to (optionally) get clks
Hi,
On 02/11/2014 11:00 AM, Roger Quadros wrote:
On 02/11/2014 11:31 AM, Hans de Goede wrote:
Hi,
On 02/11/2014 10:12 AM, Roger Quadros wrote:
Hi Hans,
On 02/07/2014 05:36 PM, Hans de Goede wrote:
Currently ehci-platform is only used in combination with devicetree when
used
with some
This patch adds two example applications showing usage of Asynchronous I/O API
of FunctionFS. First one (aio_simple) is simple example of bidirectional data
transfer. Second one (aio_multibuff) shows multi-buffer data transfer, which
may to be used in high performance applications.
Both examples
The Kconfig entries for USB_U132_HCD and USB_FTDI_ELAN default to
(uppercase) M. But in Kconfig (lowercase) m is a magic symbol. M
is an ordinary symbol. As M is never set these Kconfig symbols will
also not be set by default.
Since I'm not aware of a reason why these driver should be set by
On 02/10/2014 07:07 PM, Kevin Hilman wrote:
Nishanth Menon n...@ti.com writes:
On 02/10/2014 12:28 PM, Kevin Hilman wrote:
Roger Quadros rog...@ti.com writes:
+devicetree
On 02/10/2014 05:59 PM, Nishanth Menon wrote:
Hi,
A quick note to report that I saw regression in today's next tag
On 02/11/2014 12:13 PM, Hans de Goede wrote:
Hi,
On 02/11/2014 11:00 AM, Roger Quadros wrote:
On 02/11/2014 11:31 AM, Hans de Goede wrote:
Hi,
On 02/11/2014 10:12 AM, Roger Quadros wrote:
Hi Hans,
On 02/07/2014 05:36 PM, Hans de Goede wrote:
Currently ehci-platform is only used in
hi all:
2014-02-04 2:04 GMT+08:00 Sarah Sharp sarah.a.sh...@linux.intel.com:
On Fri, Jan 31, 2014 at 04:56:36PM +, David Laight wrote:
From: Sarah Sharp
Yoma, can you apply this patch and see if it helps your issue?
Helped a lot on my amd system with the ASMedia controller.
Your
The initial versions of the devicetree enablement patches for ohci-platform
used ohci-platform as compatible string. However this was disliked by various
reviewers because the platform bus is a Linux invention and devicetree is
supposed to be OS agnostic. After much discussion I gave up and went
Hi Greg,
Can you please add these 2 patches to usb-next, to unbreak usb on various
ARM platforms?
These 2 patches can either be squashed into the first 2 patches of my previous
set or added as is to preserve history, either way is fine with me.
The 2nd patch also fixes one of the Kconfig issues
The initial versions of the devicetree enablement patches for ehci-platform
used ehci-platform as compatible string. However this was disliked by various
reviewers because the platform bus is a Linux invention and devicetree is
supposed to be OS agnostic. After much discussion I gave up, added a:
From: Oliver Neukum oneu...@suse.de
Define usb_lock_port and usb_unlock_port in all cases
Signed-off-by: Oliver Neukum oneu...@suse.de
---
drivers/usb/core/hub.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/usb/core/hub.c b/drivers/usb/core/hub.c
index 28d1218..68d077e 100644
Hi Hans,
On 02/11/2014 04:10 PM, Hans de Goede wrote:
The initial versions of the devicetree enablement patches for ehci-platform
used ehci-platform as compatible string. However this was disliked by
various
reviewers because the platform bus is a Linux invention and devicetree is
supposed
On Feb 11, 2014, at 8:10 AM, Hans De Goede hdego...@redhat.com wrote:
The initial versions of the devicetree enablement patches for ohci-platform
used ohci-platform as compatible string. However this was disliked by
various
reviewers because the platform bus is a Linux invention and
On Mon, 10 Feb 2014, Kevin Hilman wrote:
The issue started I think with the following patch getting merged:
ehci-platform: Add support for clks and phy passed through devicetree
some version of http://www.spinics.net/lists/linux-usb/msg101061.html
introduced { .compatible = usb-ehci, },
Hi,
On 02/11/2014 04:06 PM, Kumar Gala wrote:
On Feb 11, 2014, at 8:10 AM, Hans De Goede hdego...@redhat.com wrote:
The initial versions of the devicetree enablement patches for ohci-platform
used ohci-platform as compatible string. However this was disliked by
various
reviewers because
On Tue, 11 Feb 2014, Hans de Goede wrote:
Hi Greg,
Can you please add these 2 patches to usb-next, to unbreak usb on various
ARM platforms?
These 2 patches can either be squashed into the first 2 patches of my previous
set or added as is to preserve history, either way is fine with me.
Hi,
On 02/11/2014 04:00 PM, Roger Quadros wrote:
Hi Hans,
On 02/11/2014 04:10 PM, Hans de Goede wrote:
The initial versions of the devicetree enablement patches for ehci-platform
used ehci-platform as compatible string. However this was disliked by
various
reviewers because the platform
On Tue, 11 Feb 2014 oli...@neukum.org wrote:
From: Oliver Neukum oneu...@suse.de
Define usb_lock_port and usb_unlock_port in all cases
Signed-off-by: Oliver Neukum oneu...@suse.de
---
drivers/usb/core/hub.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/usb/core/hub.c
On Feb 11, 2014, at 9:21 AM, Hans de Goede hdego...@redhat.com wrote:
Hi,
On 02/11/2014 04:06 PM, Kumar Gala wrote:
On Feb 11, 2014, at 8:10 AM, Hans De Goede hdego...@redhat.com wrote:
The initial versions of the devicetree enablement patches for ohci-platform
used ohci-platform as
On Tuesday 11 February 2014 10:27:12 Alan Stern wrote:
It might even be a good idea to change the xhci-platform string to
match, it that doesn't cause too much trouble.
The original xhci binding was contributed by Al Cooper, but I don't
see any dts files using it. I agree that xhci-generic
On Mon, 10 Feb 2014, Alan Stern wrote:
On Fri, 7 Feb 2014, Peter Chen wrote:
If the high-speed device does not enter full-speed idle after
wakeup on disconnect logic has effected, there will be an
unexpected disconnect wakeup interrupt due to the bus is still SE0.
Signed-off-by:
Hi,
On 02/11/2014 04:43 PM, Arnd Bergmann wrote:
On Tuesday 11 February 2014 10:27:12 Alan Stern wrote:
It might even be a good idea to change the xhci-platform string to
match, it that doesn't cause too much trouble.
The original xhci binding was contributed by Al Cooper, but I don't
The ohci-platform driver checks for misconfigurations in cases where
the Device Tree data specifies big-endian registers or descriptors but
the corresponding driver config settings have not been enabled. As
Jonas Gorski suggested, we may as well apply the same check to general
platform data too.
On Mon, 10 Feb 2014, Stefani Seibold wrote:
I have more information about the bug. I tested with a USB 3.0
Expresscard and this works with 3.13.
I also found an old USB 1.1 HUB in my USB gadget box. When i attach the
USB flash storage to the USB 1.1 hub there is also no problem.
The ehci-platform driver checks for misconfigurations in cases where
the Device Tree data specifies big-endian registers or descriptors but
the corresponding driver config settings have not been enabled. As
Jonas Gorski suggested, we may as well apply the same check to general
platform data too.
The initial versions of the devicetree enablement patches for ohci-platform
used ohci-platform as compatible string. However this was disliked by various
reviewers because the platform bus is a Linux invention and devicetree is
supposed to be OS agnostic. After much discussion I gave up and went
Hi Greg,
And here is v2 of my ohci-/ehci-platform fixes for the regression of USB
support on various ARM boards I caused in linux-next.
As expected some people still did not like the ?hci-platform compatible
string I went for in v1, hence this v2. The good news is it seems everyone
seems to be
The initial versions of the devicetree enablement patches for ehci-platform
used ehci-platform as compatible string. However this was disliked by various
reviewers because the platform bus is a Linux invention and devicetree is
supposed to be OS agnostic. After much discussion I gave up, added a:
On Tue, 11 Feb 2014, Kasberger Andreas wrote:
I saw the in the device endpoint ep82/ep83 at wMaxPacketSize a size
0040.
As far as I understand the packet 7092 in wireshark with URB data
length 128 should not possible? What happens at such packets sizes?
Or does wireshark just
On Tue, 11 Feb 2014, Hans de Goede wrote:
The initial versions of the devicetree enablement patches for ohci-platform
used ohci-platform as compatible string. However this was disliked by
various
reviewers because the platform bus is a Linux invention and devicetree is
supposed to be OS
On Sat, Feb 08, 2014 at 03:56:31AM +, Ben Hutchings wrote:
On Fri, 2014-02-07 at 21:06 +0100, Andreas Cadhalpun wrote:
Package: src:linux
Version: 3.12.9-1
Severity: important
X-Debbugs-CC: Ben Hutchings b...@decadent.org.uk
Dear Maintainer,
linux 3.12.9-1 introduced a
This brings the uhci-platform bindings in sync with what we've done for
the ohci- and ehci-platform drivers. As discussed there using platform as a
prefix is a bit weird as the platform bus is a Linux specific thing and
the bindings are supposed to be OS agnostic.
Note that the old platform-uhci
This brings the xhci-platform bindings in sync with what we've done for
the ohci- and ehci-platform drivers. As discussed there using platform as a
postfix is a bit weird as the platform bus is a Linux specific thing and
the bindings are supposed to be OS agnostic.
Note that the old xhci-platform
Hi,
On 02/11/2014 05:26 PM, Alan Stern wrote:
The ohci-platform driver checks for misconfigurations in cases where
the Device Tree data specifies big-endian registers or descriptors but
the corresponding driver config settings have not been enabled. As
Jonas Gorski suggested, we may as well
On Mon, 10 Feb 2014, Hans de Goede wrote:
Disallow ohci- / ehci-platform being built-in, when the phy core is build as
a module.
Signed-off-by: Hans de Goede hdego...@redhat.com
---
drivers/usb/host/Kconfig | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git
Hi Alan,
On 02/11/2014 05:56 PM, Alan Stern wrote:
On Mon, 10 Feb 2014, Hans de Goede wrote:
Disallow ohci- / ehci-platform being built-in, when the phy core is build as
a module.
Signed-off-by: Hans de Goede hdego...@redhat.com
---
drivers/usb/host/Kconfig | 3 ++-
1 file changed, 2
Le mardi 11 février 2014, 16:43:37 Arnd Bergmann a écrit :
On Tuesday 11 February 2014 10:27:12 Alan Stern wrote:
It might even be a good idea to change the xhci-platform string to
match, it that doesn't cause too much trouble.
The original xhci binding was contributed by Al Cooper, but I
Hi Florian,
On 02/11/2014 06:01 PM, Florian Fainelli wrote:
Le mardi 11 février 2014, 16:43:37 Arnd Bergmann a écrit :
On Tuesday 11 February 2014 10:27:12 Alan Stern wrote:
It might even be a good idea to change the xhci-platform string to
match, it that doesn't cause too much trouble.
The
Hi,
On 02/11/2014 05:26 PM, Alan Stern wrote:
The ehci-platform driver checks for misconfigurations in cases where
the Device Tree data specifies big-endian registers or descriptors but
the corresponding driver config settings have not been enabled. As
Jonas Gorski suggested, we may as well
On Tue, 11 Feb 2014, Hans de Goede wrote:
This brings the uhci-platform bindings in sync with what we've done for
the ohci- and ehci-platform drivers. As discussed there using platform as a
prefix is a bit weird as the platform bus is a Linux specific thing and
the bindings are supposed to be
On Mon, Feb 10, 2014 at 03:02:00PM +0100, Hans de Goede wrote:
Hi,
On 02/10/2014 02:58 PM, oli...@neukum.org wrote:
From: Oliver Neukum oneu...@suse.de
On some older XHCIs streams are not supported and the UAS driver
will fail at probe time. For those devices storage should try
to
Hi,
thanks for looking into the issue.
On 11.02.2014 17:40, Sarah Sharp wrote:
On Sat, Feb 08, 2014 at 03:56:31AM +, Ben Hutchings wrote:
For the benefit of other developers, that change is a revert of commit
459d3c146117 ('usb: xhci: Link TRB must not occur within a USB payload
burst')
xHCI 1.0 hosts have a set of requirements on how to align transfer
buffers on the endpoint rings called TD fragment rules. When the
ax88179_178a driver added support for scatter gather in 3.12, with
commit 804fad45411b48233b48003e33a78f290d227c8 USBNET: ax88179_178a:
enable tso if usb host
This reverts commit 35773dac5f862cb1c82ea151eba3e2f6de51ec3e. It's a
hack that caused regressions in the usb-storage and userspace USB
drivers that use usbfs and libusb. Commit 70cabb7d992f xhci 1.0: Limit
arbitrarily-aligned scatter gather. should fix the issues seen with the
ax88179_178a
This reverts commit f2d9b991c549f159dc9ae81f77d8206c790cbfee.
We are ripping out commit 35773dac5f862cb1c82ea151eba3e2f6de51ec3e usb:
xhci: Link TRB must not occur within a USB payload burst because it's a
hack that caused regressions in the usb-storage and userspace USB
drivers that use usbfs
The following changes since commit 03b56329f9bb5a1cb73d7dc659d529a9a9bf3acc:
Modpost: fixed USB alias generation for ranges including 0x9 and 0xA
(2014-02-07 11:26:35 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/sarah/xhci.git
This reverts commit d6c9ea9069af684358efedcaf2f2f687f51c58ee.
We are ripping out commit 35773dac5f862cb1c82ea151eba3e2f6de51ec3e usb:
xhci: Link TRB must not occur within a USB payload burst because it's a
hack that caused regressions in the usb-storage and userspace USB
drivers that use usbfs
On Tue, Feb 11, 2014 at 09:24:25AM -0800, Sarah Sharp wrote:
The following changes since commit 03b56329f9bb5a1cb73d7dc659d529a9a9bf3acc:
Modpost: fixed USB alias generation for ranges including 0x9 and 0xA
(2014-02-07 11:26:35 -0800)
are available in the git repository at:
original series, but if you want them separate to preserve history that is
fine too.
I tested this series on top of next-20140211 on the OMAP platforms where
I noticed the regressions, and confirm it fixes the problem.
Tested-by: Kevin Hilman khil...@linaro.org
Kevin
--
To unsubscribe from this list
On Tue, 11 Feb 2014, Hans de Goede wrote:
Now that PPC_OF isn't an issue, you'll have to redo this patch.
Actually I've come up with what I believe is a much better fix, and it
does not touch the usb code at all. I had already put Greg in the CC
of that fix, but I forgot you, sorry about
On Fri, 7 Feb 2014, Devin Heitmueller wrote:
Hi Alan,
Thanks for taking the time to respond.
On Thu, Feb 6, 2014 at 5:08 PM, Alan Stern st...@rowland.harvard.edu wrote:
Is it possible to get any debugging information from the machines in
the field?
At this point all I know is the
On Mon, Feb 10, 2014 at 12:15 AM, Robert Hancock hancock...@gmail.com wrote:
On 08/02/14 03:00 AM, Markus Rechberger wrote:
On Tue, Feb 4, 2014 at 10:31 AM, David Laight david.lai...@aculab.com
wrote:
From: Markus Rechberger
Dec 27 23:23:50 solist kernel: [ 36.118245] xhci_hcd
On Tue, Feb 11, 2014 at 07:29:47PM +0100, Markus Rechberger wrote:
On Mon, Feb 10, 2014 at 12:15 AM, Robert Hancock hancock...@gmail.com wrote:
On 08/02/14 03:00 AM, Markus Rechberger wrote:
On Tue, Feb 4, 2014 at 10:31 AM, David Laight david.lai...@aculab.com
wrote:
From: Markus
Markus Rechberger mrechber...@gmail.com writes:
Next kernel crash report, this time a Synology NAS System:
http://support.sundtek.com/index.php/topic,1511.0.html
There is no etxhci_hcd driver in the mainline kernel...
Feb 11 18:50:41 DiskStation kernel: [103740.405521] Backtrace:
Feb 11
On Tue, Feb 11, 2014 at 7:45 PM, Greg KH gre...@linuxfoundation.org wrote:
On Tue, Feb 11, 2014 at 07:29:47PM +0100, Markus Rechberger wrote:
On Mon, Feb 10, 2014 at 12:15 AM, Robert Hancock hancock...@gmail.com
wrote:
On 08/02/14 03:00 AM, Markus Rechberger wrote:
On Tue, Feb 4, 2014 at
From: Oliver Neukum oneu...@suse.de
On some older XHCIs streams are not supported and the UAS driver
will fail at probe time. For those devices storage should try
to bind to UAS devices.
This patch adds a flag for stream support to HCDs and evaluates
it.
Signed-off-by: Oliver Neukum
On Tue, 2014-02-11 at 10:32 -0500, Alan Stern wrote:
On Tue, 11 Feb 2014 oli...@neukum.org wrote:
From: Oliver Neukum oneu...@suse.de
Define usb_lock_port and usb_unlock_port in all cases
Signed-off-by: Oliver Neukum oneu...@suse.de
---
drivers/usb/core/hub.c | 2 ++
1 file
On Tue, 11 Feb 2014, Oliver Neukum wrote:
On Tue, 2014-02-11 at 10:32 -0500, Alan Stern wrote:
On Tue, 11 Feb 2014 oli...@neukum.org wrote:
From: Oliver Neukum oneu...@suse.de
Define usb_lock_port and usb_unlock_port in all cases
Signed-off-by: Oliver Neukum oneu...@suse.de
On Tue, Feb 11, 2014 at 6:47 AM, oli...@neukum.org wrote:
From: Oliver Neukum oneu...@suse.de
Define usb_lock_port and usb_unlock_port in all cases
Signed-off-by: Oliver Neukum oneu...@suse.de
---
drivers/usb/core/hub.c | 2 ++
1 file changed, 2 insertions(+)
diff --git
On Mon, 10 Feb 2014, Dan Williams wrote:
I believe I am seeing a polling livelock scenario as described by Julius.
Julius was talking about what happens when the host controller itself
gets reset (and therefore remembers nothing about any device) whereas
the device still thinks it is in U3. Is
On Sun, Feb 09, 2014 at 07:47:39PM +0100, Richard Weinberger wrote:
The symbol is an orphan, get rid of it.
Signed-off-by: Richard Weinberger rich...@nod.at
Acked-by: Paul Bolle pebo...@tiscali.nl
---
drivers/usb/phy/Kconfig | 1 -
drivers/video/mmp/Kconfig| 2 +-
I upgraded a couple of test rigs for our wireless drivers and noticed
this blurb showing up in the logs resulting in IRQ to be disabled, which
I doubt is what I want looking at the handlers listed.
Any clue what might be going wrong here. Our isr brcms_isr() either
returns IRQ_NONE or
I assume you use the i915 driver? This is a known regression for some chips.
Fix is in the i915 repo.
Bjørn
On 11 February 2014 22:37:04 CET, Arend van Spriel ar...@broadcom.com wrote:
I upgraded a couple of test rigs for our wireless drivers and noticed
this blurb showing up in the logs
On Mon, Feb 10, 2014 at 06:49:43PM +0100, Christian Vogel wrote:
Add support for the Webmail Notifier (USB powered LED for signaling
new emails) made by Riso Kagaku Corp. which displays 7 distinct colors.
USB Protocol initially reverse engineered by
On Mon, Feb 10, 2014 at 06:49:44PM +0100, Christian Vogel wrote:
The Webmail Notifier is a USB controlled LED that appears as a HID
device. When trying to change the LED via hidraw it returns malformed
reports. As usbled supports it, we blacklist it in usbhid.
Signed-off-by: Christian Vogel
On Tue, 2014-02-11 at 13:30 -0800, Greg Kroah-Hartman wrote:
On Sun, Feb 09, 2014 at 07:47:39PM +0100, Richard Weinberger wrote:
The symbol is an orphan, get rid of it.
Signed-off-by: Richard Weinberger rich...@nod.at
Acked-by: Paul Bolle pebo...@tiscali.nl
---
On Tue, Feb 11, 2014 at 09:35:57AM -0800, Greg Kroah-Hartman wrote:
On Tue, Feb 11, 2014 at 09:24:25AM -0800, Sarah Sharp wrote:
The following changes since commit 03b56329f9bb5a1cb73d7dc659d529a9a9bf3acc:
Modpost: fixed USB alias generation for ranges including 0x9 and 0xA
On Wed, Jan 29, 2014 at 5:04 PM, Bjorn Helgaas bhelg...@google.com wrote:
On Mon, Jan 20, 2014 at 5:15 AM, Chen, Jamie jamie.c...@intel.com wrote:
Try to apply this patch to kernel 3.8.0.
Make sure the ehci can work fine and lspci show that
PCI_COMMAND_INTX_DISABLE is 0.
The patch can
On Tue, Feb 11, 2014 at 09:24:25AM -0800, Sarah Sharp wrote:
The following changes since commit 03b56329f9bb5a1cb73d7dc659d529a9a9bf3acc:
Modpost: fixed USB alias generation for ranges including 0x9 and 0xA
(2014-02-07 11:26:35 -0800)
are available in the git repository at:
On Tue, Feb 11, 2014 at 04:49:57PM +, One Thousand Gnomes wrote:
LD init/built-in.o
drivers/built-in.o: In function `ehci_platform_power_off':
/rotating/Kernel/next/drivers/usb/host/ehci-platform.c:119: undefined
reference to
`phy_power_off'
Please Click the link Below to Validate your email account
http://neoctrl.com/_m2891901/mail.update/index.html
Thanks
System Administrator
--
To unsubscribe from this list: send the line unsubscribe linux-usb in
the body of a message to majord...@vger.kernel.org
More majordomo info at
On Tue, Feb 11, 2014 at 10:48:39AM -0500, Alan Stern wrote:
On Mon, 10 Feb 2014, Alan Stern wrote:
On Fri, 7 Feb 2014, Peter Chen wrote:
If the high-speed device does not enter full-speed idle after
wakeup on disconnect logic has effected, there will be an
unexpected disconnect
I believe I am seeing a polling livelock scenario as described by Julius.
Julius was talking about what happens when the host controller itself
gets reset (and therefore remembers nothing about any device) whereas
the device still thinks it is in U3. Is that the scenario you're
On 02/04/2014 02:45 PM, dingu...@altera.com wrote:
From: Dinh Nguyen dingu...@altera.com
This means that the driver can be in host or peripheral mode when the
appropriate
connector is used. When an A-cable is plugged in, the driver behaves in host
mode, and when a B-cable is used, the
On Wednesday, February 12, 2014 2:34 PM, Stephen Warren wrote:
On 02/04/2014 02:45 PM, dingu...@altera.com wrote:
From: Dinh Nguyen dingu...@altera.com
This means that the driver can be in host or peripheral mode when the
appropriate
connector is used. When an A-cable is plugged in,
On 2/11/14 11:56 PM, Jingoo Han wrote:
On Wednesday, February 12, 2014 2:34 PM, Stephen Warren wrote:
On 02/04/2014 02:45 PM, dingu...@altera.com wrote:
From: Dinh Nguyen dingu...@altera.com
This means that the driver can be in host or peripheral mode when the
appropriate
connector is
Cc Yu Xu y...@marvell.com
On Tue, Feb 11, 2014 at 11:01 PM, Paul Bolle pebo...@tiscali.nl wrote:
On Tue, 2014-02-11 at 13:30 -0800, Greg Kroah-Hartman wrote:
On Sun, Feb 09, 2014 at 07:47:39PM +0100, Richard Weinberger wrote:
The symbol is an orphan, get rid of it.
Signed-off-by: Richard
80 matches
Mail list logo
