[PATCH] cifs: escape spaces in share names

ned-off-by: Maciek Borzecki --- fs/cifs/cifsfs.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/fs/cifs/cifsfs.c b/fs/cifs/cifsfs.c index 099ad9f3660bb28db1b6a9aea9538282b41c6455..3c6cb85b95e207df48f10cc9df937cdda24e 100644 --- a/fs/cifs/cifsfs.c +++ b/fs/cifs/cifsfs.c

[PATCH] staging wlan-ng: fix type mismatch warnings in mkpdrlist()

ast to restricted __le16 drivers/staging/wlan-ng/prism2fw.c:625:21: warning: cast to restricted __le16 Signed-off-by: Maciek Borzecki --- drivers/staging/wlan-ng/hfa384x.h | 4 ++-- drivers/staging/wlan-ng/prism2fw.c | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/driv

Re: [PATCH] staging wlan-ng: mark PDA buf as __le16

On Sat, Apr 8, 2017 at 3:18 PM, Maciek Borzecki wrote: > On Sat, Apr 8, 2017 at 1:01 PM, Greg Kroah-Hartman > wrote: >> On Fri, Apr 07, 2017 at 02:47:55PM +0200, Maciek Borzecki wrote: >>> PDA buffer contains little-endian data, clearly mark it as such. >>

Re: [PATCH] staging wlan-ng: mark PDA buf as __le16

On Sat, Apr 8, 2017 at 1:01 PM, Greg Kroah-Hartman wrote: > On Fri, Apr 07, 2017 at 02:47:55PM +0200, Maciek Borzecki wrote: >> PDA buffer contains little-endian data, clearly mark it as such. >> >> Fixes sparse warnings: >> drivers/staging/wlan-ng/hfa384x_usb.

[PATCH] staging wlan-ng: mark PDA buf as __le16

:2382:44: warning: cast to restricted __le16 Signed-off-by: Maciek Borzecki --- drivers/staging/wlan-ng/hfa384x_usb.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/wlan-ng/hfa384x_usb.c b/drivers/staging/wlan-ng/hfa384x_usb.c index

[PATCH] staging: wlan-ng: prism2sta: replace memcmp with ether_addr_equal

() Signed-off-by: Maciek Borzecki --- drivers/staging/wlan-ng/prism2sta.c | 14 +++--- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/drivers/staging/wlan-ng/prism2sta.c b/drivers/staging/wlan-ng/prism2sta.c index 0329c521d17c5c0ee5baa237c81383021daefe24

Re: [PATCH v2 1/3] leds: add device activity LED triggers

so as long as > > there's no collision in numbering things should be fine. > > Ensuring no collision will be difficult, especially given that it's most > common that the dynamic allocator is used. In order to guarantee no > collisions, a user who doesn't expose any

Re: [PATCH v2 0/3] leds: add device trigger

linux/video7/name:s5p-jpeg-enc > #/sys/class/video4linux/video8/name:s5p-jpeg-dec > #ls -l /dev/video7 > #crw-rw---T 1 root video 81, 8 Jan 1 03:32 /dev/video8 > #echo "81:7" > /sys/kernel/debug/ledtrig-dev/register > #cd /sys/class/leds/aat1290 > #cat trigg

Re: [PATCH v2 1/3] leds: add device activity LED triggers

On 10/01 09:47, Josh Cartwright wrote: > Hello Maciek- > > Some architectural questions below: > > On Thu, Oct 01, 2015 at 04:04:31PM +0200, Maciek Borzecki wrote: > > The patch adds LED triggers for indicating an activity on a selected > > device. The drivers that int

[PATCH v2 3/3] Documentation: leds: document ledtrig-device trigger

This patch adds documentation for ledtrig-device trigger. Signed-off-by: Maciek Borzecki --- Documentation/leds/00-INDEX | 3 +++ Documentation/leds/ledtrig-device.txt | 35 +++ 2 files changed, 38 insertions(+) create mode 100644 Documentation/leds

[PATCH v2 0/3] leds: add device trigger

ister debugfs attribute - documentation update Maciek Borzecki (3): leds: add device activity LED triggers leds: add debugfs to device trigger Documentation: leds: document ledtrig-device trigger Documentation/leds/00-INDEX | 3 + Documentation/leds/ledtrig-device.txt | 35 dr

[PATCH v2 2/3] leds: add debugfs to device trigger

o'ing : will create a trigger for this device unregister - echo'ing : will delete a trigger for this device trigger - echo'ing : will fire a trigger for this device Signed-off-by: Maciek Borzecki --- drivers/leds/trigger/le

[PATCH v2 1/3] leds: add device activity LED triggers

The patch adds LED triggers for indicating an activity on a selected device. The drivers that intend to use triggers need to register respective devices using ledtrig_dev_add(). Triggers are generated by explicitly calling ledtrig_dev_activity(). Signed-off-by: Maciek Borzecki --- drivers/leds

Re: [PATCH 2/3] leds: add debugfs to device trigger

comment. Indeed, I noticed the problem just after sending the patch. Surprisingly this didn't fail on iMX6 for some reason. Aside from the __user access problem, is the approach, in general, ok for you or would you suggest that I changed something? Regards, -- Maciek Borzecki -- To unsubscri

Re: [PATCH 2/3] leds: add debugfs to device trigger

tatic ssize_t ledtrig_dev_register_write(struct file *filp, > > --- > 0-DAY kernel test infrastructureOpen Source Technology Center > https://lists.01.org/pipermail/kbuild-all Intel Corporation -- Maciek Borzecki -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

[PATCH 2/3] leds: add debugfs to device trigger

o'ing : will create a trigger for this device trigger - echo'ing : will fire a trigger for this device Signed-off-by: Maciek Borzecki --- drivers/leds/trigger/ledtrig-device.c | 113 +- 1 file changed, 111 insertions(+), 2 deletions(-) diff

[PATCH 0/3] leds: add device trigger

le of debugfs helpers. The third patch adds documentation and notes on debugfs interface. Maciek Borzecki (3): leds: add device activity LED triggers leds: add debugfs to device trigger Documentation: leds: document ledtrig-device trigger Documentation/leds/00-INDEX | 3 + Document

[PATCH 3/3] Documentation: leds: document ledtrig-device trigger

This patch adds documentation for ledtrig-device trigger. Signed-off-by: Maciek Borzecki --- Documentation/leds/00-INDEX | 3 +++ Documentation/leds/ledtrig-device.txt | 32 2 files changed, 35 insertions(+) create mode 100644 Documentation/leds

[PATCH 1/3] leds: add device activity LED triggers

The patch adds LED triggers for indicating an activity on a selected device. The drivers that intend to use triggers need to register respective devices using ledtrig_dev_add(). Triggers are generated by explicitly calling ledtrig_dev_activity(). Signed-off-by: Maciek Borzecki --- drivers/leds

Re: [PATCH] perf: allow user to indicate path to objdump in command line

On Wed, 2012-09-05 at 12:11 +1000, Michael Ellerman wrote: > On Tue, 2012-09-04 at 10:05 -0600, David Ahern wrote: > > On 9/4/12 4:32 AM, Maciek Borzecki wrote: > > > When analyzing perf data from hosts of other architecture than one of the > > > local > > > h

[PATCH] perf: allow user to indicate path to objdump in command line

When analyzing perf data from hosts of other architecture than one of the local host it's useful to call objdump that is part of a toolchain for that architecture. Instead of calling regular objdump, call one that user specified in command line. Signed-off-by: Maciek Borzecki --- tools