Re: [RFC][PATCH] printk: Add option to append kernel version to the dict

Hello, On (05/13/16 13:58), Calvin Owens wrote: [..] > +#if defined(CONFIG_PRINTK_APPEND_UNAME) > +static ssize_t msg_print_ext_uname(char *buf, size_t size) > +{ > + return scnprintf(buf, size, " UNAME=%s\n", init_utsname()->release); > +} > +#else > +static ssize_t msg_print_ext_uname(char

Re: [RFC][PATCH] printk: Add option to append kernel version to the dict

Hello, On (05/13/16 13:58), Calvin Owens wrote: [..] > +#if defined(CONFIG_PRINTK_APPEND_UNAME) > +static ssize_t msg_print_ext_uname(char *buf, size_t size) > +{ > + return scnprintf(buf, size, " UNAME=%s\n", init_utsname()->release); > +} > +#else > +static ssize_t msg_print_ext_uname(char

Re: [PATCH] dwc3: gadget: Defer starting the gadget device until gadget is power on

On 13 May 2016 at 20:46, Felipe Balbi wrote: > > Hi, > > Baolin Wang writes: > why does it need restart? Why is dwc3 powered off? Who powers it off? Because when the dwc3 Vbus is off (no cable pluging in now), especially for some

Re: [PATCH] dwc3: gadget: Defer starting the gadget device until gadget is power on

On 13 May 2016 at 20:46, Felipe Balbi wrote: > > Hi, > > Baolin Wang writes: > why does it need restart? Why is dwc3 powered off? Who powers it off? Because when the dwc3 Vbus is off (no cable pluging in now), especially for some mobile device, the system need to power off the

[PATCH v6 4/6] crypto: algif_akcipher - enable compilation

From: Stephan Mueller Add the Makefile and Kconfig updates to allow algif_akcipher to be compiled. Signed-off-by: Stephan Mueller Signed-off-by: Tadeusz Struk --- crypto/Kconfig |9 + crypto/Makefile |1 + 2

[PATCH v6 3/6] crypto: AF_ALG -- add asymmetric cipher interface

From: Stephan Mueller This patch adds the user space interface for asymmetric ciphers. The interface allows the use of sendmsg as well as vmsplice to provide data. This version has been rebased on top of 4.6 and a few chackpatch issues have been fixed. Signed-off-by:

[PATCH v6 5/6] crypto: algif_akcipher - add ops_nokey

Similar to algif_skcipher and algif_hash, algif_akcipher needs to prevent user space from using the interface in an improper way. This patch adds nokey ops handlers, which do just that. Signed-off-by: Tadeusz Struk --- crypto/algif_akcipher.c | 159

[PATCH v6 4/6] crypto: algif_akcipher - enable compilation

From: Stephan Mueller Add the Makefile and Kconfig updates to allow algif_akcipher to be compiled. Signed-off-by: Stephan Mueller Signed-off-by: Tadeusz Struk --- crypto/Kconfig |9 + crypto/Makefile |1 + 2 files changed, 10 insertions(+) diff --git a/crypto/Kconfig

[PATCH v6 3/6] crypto: AF_ALG -- add asymmetric cipher interface

From: Stephan Mueller This patch adds the user space interface for asymmetric ciphers. The interface allows the use of sendmsg as well as vmsplice to provide data. This version has been rebased on top of 4.6 and a few chackpatch issues have been fixed. Signed-off-by: Stephan Mueller

[PATCH v6 5/6] crypto: algif_akcipher - add ops_nokey

Similar to algif_skcipher and algif_hash, algif_akcipher needs to prevent user space from using the interface in an improper way. This patch adds nokey ops handlers, which do just that. Signed-off-by: Tadeusz Struk --- crypto/algif_akcipher.c | 159

[PATCH v6 2/6] crypto: AF_ALG -- add setpubkey setsockopt call

From: Stephan Mueller For supporting asymmetric ciphers, user space must be able to set the public key. The patch adds a new setsockopt call for setting the public key. Signed-off-by: Stephan Mueller --- crypto/af_alg.c | 18

[PATCH v6 6/6] crypto: AF_ALG - add support for key_id

This patch adds support for asymmetric key type to AF_ALG. It will work as follows: A new PF_ALG socket options are added on top of existing ALG_SET_KEY and ALG_SET_PUBKEY, namely ALG_SET_KEY_ID and ALG_SET_PUBKEY_ID for setting public and private keys respectively. When these new options will be

[PATCH v6 2/6] crypto: AF_ALG -- add setpubkey setsockopt call

From: Stephan Mueller For supporting asymmetric ciphers, user space must be able to set the public key. The patch adds a new setsockopt call for setting the public key. Signed-off-by: Stephan Mueller --- crypto/af_alg.c | 18 +- include/crypto/if_alg.h |1 + 2

[PATCH v6 6/6] crypto: AF_ALG - add support for key_id

This patch adds support for asymmetric key type to AF_ALG. It will work as follows: A new PF_ALG socket options are added on top of existing ALG_SET_KEY and ALG_SET_PUBKEY, namely ALG_SET_KEY_ID and ALG_SET_PUBKEY_ID for setting public and private keys respectively. When these new options will be

[PATCH v6 1/6] crypto: AF_ALG -- add sign/verify API

From: Stephan Mueller Add the flags for handling signature generation and signature verification. Also, the patch adds the interface for setting a public key. Signed-off-by: Stephan Mueller Signed-off-by: Tadeusz Struk ---

[PATCH v6 0/6] crypto: algif - add akcipher

First four patches are a resend of the v3 algif_akcipher from Stephan Mueller, with minor changes after rebase on top of 4.6-rc1. The next three patches add support for keys stored in system keyring subsystem. First patch adds algif_akcipher nokey hadlers. Second patch adds generic sign,

[PATCH v6 1/6] crypto: AF_ALG -- add sign/verify API

From: Stephan Mueller Add the flags for handling signature generation and signature verification. Also, the patch adds the interface for setting a public key. Signed-off-by: Stephan Mueller Signed-off-by: Tadeusz Struk --- include/uapi/linux/if_alg.h |3 +++ 1 file changed, 3

[PATCH v6 0/6] crypto: algif - add akcipher

First four patches are a resend of the v3 algif_akcipher from Stephan Mueller, with minor changes after rebase on top of 4.6-rc1. The next three patches add support for keys stored in system keyring subsystem. First patch adds algif_akcipher nokey hadlers. Second patch adds generic sign,

[PATCH perf/core v8 11/16] perf probe: Accept %sdt and %cached event name

From: Masami Hiramatsu To improbe usability, support %[PROVIDER:]SDTEVENT format to add new probes on SDT and cached events. e.g. # perf probe -x /lib/libc-2.17.so %lll_lock_wait_private Added new event: sdt_libc:lll_lock_wait_private (on

[PATCH perf/core v8 16/16] perf probe: Support a special SDT probe format

Support a special SDT probe format which can omit the '%' prefix only if the SDT group name starts with "sdt_". So, for example both of "%sdt_libc:setjump" and "sdt_libc:setjump" are acceptable for perf probe --add. Suggested-by: Brendan Gregg Signed-off-by: Masami

[PATCH perf/core v8 12/16] perf-list: Show SDT and pre-cached events

From: Masami Hiramatsu Show SDT and pre-cached events by perf-list with "sdt". This also shows the binary and build-id where the events are placed only when there are same name events on different binaries. e.g. # perf list sdt List of pre-defined

[PATCH perf/core v8 14/16] perf probe: Allow wildcard for cached events

Allo glob wildcard for reusing cached/SDT events. This also automatically find the target binaries, e.g. # perf probe -a %sdt_libc:\* This example adds probes for all SDT in libc. Note that the SDTs must have been scanned by perf buildid-cache. Signed-off-by: Masami Hiramatsu

[PATCH perf/core v8 10/16] perf buildid-cache: Scan and import user SDT events to probe cache

From: Masami Hiramatsu perf buildid-cache --add scans given binary and add the SDT events to probe cache. "sdt_" prefix is appended for all SDT providers to avoid event-name clash with other pre-defined events. It is possible to use the cached SDT events as

[PATCH perf/core v8 11/16] perf probe: Accept %sdt and %cached event name

From: Masami Hiramatsu To improbe usability, support %[PROVIDER:]SDTEVENT format to add new probes on SDT and cached events. e.g. # perf probe -x /lib/libc-2.17.so %lll_lock_wait_private Added new event: sdt_libc:lll_lock_wait_private (on %lll_lock_wait_private in

[PATCH perf/core v8 16/16] perf probe: Support a special SDT probe format

Support a special SDT probe format which can omit the '%' prefix only if the SDT group name starts with "sdt_". So, for example both of "%sdt_libc:setjump" and "sdt_libc:setjump" are acceptable for perf probe --add. Suggested-by: Brendan Gregg Signed-off-by: Masami Hiramatsu ---

[PATCH perf/core v8 12/16] perf-list: Show SDT and pre-cached events

From: Masami Hiramatsu Show SDT and pre-cached events by perf-list with "sdt". This also shows the binary and build-id where the events are placed only when there are same name events on different binaries. e.g. # perf list sdt List of pre-defined events (to be used in -e):

[PATCH perf/core v8 14/16] perf probe: Allow wildcard for cached events

Allo glob wildcard for reusing cached/SDT events. This also automatically find the target binaries, e.g. # perf probe -a %sdt_libc:\* This example adds probes for all SDT in libc. Note that the SDTs must have been scanned by perf buildid-cache. Signed-off-by: Masami Hiramatsu --- Changes in

[PATCH perf/core v8 10/16] perf buildid-cache: Scan and import user SDT events to probe cache

From: Masami Hiramatsu perf buildid-cache --add scans given binary and add the SDT events to probe cache. "sdt_" prefix is appended for all SDT providers to avoid event-name clash with other pre-defined events. It is possible to use the cached SDT events as other cached events, via perf probe

[PATCH perf/core v8 13/16] perf-list: Skip SDTs placed in invalid binaries

From: Masami Hiramatsu Skip SDTs placed in invalid (non-exist, or older version) binaries. Note that perf-probe --cache --list and perf-probe --cache --del still handle all the caches including invalid binaries. Signed-off-by: Masami Hiramatsu

[PATCH perf/core v8 15/16] perf probe: Support @BUILDID or @FILE suffix for SDT events

Support @BUILDID or @FILE suffix for SDT events. This allows perf to add probes on SDTs/pre-cached events on given FILE or the file which has given BUILDID (also, this complements BUILDID.) For example, both gcc and libstdc++ has same SDTs as below. If you would like to add a probe on

[PATCH perf/core v8 13/16] perf-list: Skip SDTs placed in invalid binaries

From: Masami Hiramatsu Skip SDTs placed in invalid (non-exist, or older version) binaries. Note that perf-probe --cache --list and perf-probe --cache --del still handle all the caches including invalid binaries. Signed-off-by: Masami Hiramatsu Signed-off-by: Masami Hiramatsu --- Changes in

[PATCH perf/core v8 15/16] perf probe: Support @BUILDID or @FILE suffix for SDT events

Support @BUILDID or @FILE suffix for SDT events. This allows perf to add probes on SDTs/pre-cached events on given FILE or the file which has given BUILDID (also, this complements BUILDID.) For example, both gcc and libstdc++ has same SDTs as below. If you would like to add a probe on

[PATCH perf/core v8 05/16] perf probe: Use cache entry if possible

From: Masami Hiramatsu Before analyzing debuginfo, try to find a corresponding entry from probe cache always. This does not depend on --cache, the --cache enables to store/update cache, but looking up the cache is always enabled. Signed-off-by: Masami Hiramatsu

[PATCH perf/core v8 05/16] perf probe: Use cache entry if possible

From: Masami Hiramatsu Before analyzing debuginfo, try to find a corresponding entry from probe cache always. This does not depend on --cache, the --cache enables to store/update cache, but looking up the cache is always enabled. Signed-off-by: Masami Hiramatsu Signed-off-by: Masami Hiramatsu

[PATCH perf/core v8 03/16] perf-buildid-cache: Use path/to/bin/buildid/elf instead of path/to/bin/buildid

From: Masami Hiramatsu Use path/to/bin/buildid/elf instead of path/to/bin/buildid to store corresponding elf binary. This also stores vdso in buildid/vdso, kallsyms in buildid/kallsyms. Note that the existing caches are not updated until user adds or updates the

[PATCH perf/core v8 07/16] perf probe: Remove caches when --cache is given

From: Masami Hiramatsu perf-probe --del removes caches when --cache is given. Note that the delete pattern is not same as normal events. If you cached probes with event name, --del "eventname" works as expected. However, if you skipped it, the cached probes

[PATCH perf/core v8 08/16] perf/sdt: ELF support for SDT

From: Hemant Kumar This patch serves the initial support to identify and list SDT events in binaries. When programs containing SDT markers are compiled, gcc with the help of assembler directives identifies them and places them in the section ".note.stapsdt". To find

[PATCH perf/core v8 03/16] perf-buildid-cache: Use path/to/bin/buildid/elf instead of path/to/bin/buildid

From: Masami Hiramatsu Use path/to/bin/buildid/elf instead of path/to/bin/buildid to store corresponding elf binary. This also stores vdso in buildid/vdso, kallsyms in buildid/kallsyms. Note that the existing caches are not updated until user adds or updates the cache. Anyway, if there is the

[PATCH perf/core v8 07/16] perf probe: Remove caches when --cache is given

From: Masami Hiramatsu perf-probe --del removes caches when --cache is given. Note that the delete pattern is not same as normal events. If you cached probes with event name, --del "eventname" works as expected. However, if you skipped it, the cached probes doesn't have actual event name. In

[PATCH perf/core v8 08/16] perf/sdt: ELF support for SDT

From: Hemant Kumar This patch serves the initial support to identify and list SDT events in binaries. When programs containing SDT markers are compiled, gcc with the help of assembler directives identifies them and places them in the section ".note.stapsdt". To find these markers from the

[PATCH perf/core v8 09/16] perf probe: Add group name support

From: Masami Hiramatsu Allow user to set group name for adding new event. Note that user must ensure that the group name doesn't conflict with existing group name carefully. E.g. Existing group name can conflict with other events. Especially, using the group name

[PATCH perf/core v8 04/16] perf probe: Add --cache option to cache the probe definitions

From: Masami Hiramatsu Add --cache option to cache the probe definitions. This just saves the result of the dwarf analysis to probe cache. Signed-off-by: Masami Hiramatsu Signed-off-by: Masami Hiramatsu ---

[PATCH perf/core v8 06/16] perf probe: Show all cached probes

From: Masami Hiramatsu perf probe --list shows all cached probes when --cache is given. Each caches are shown with on which binary that probed. e.g. - # perf probe --cache vfs_read \$params # perf probe --cache -x /lib64/libc-2.17.so getaddrinfo

[PATCH perf/core v8 04/16] perf probe: Add --cache option to cache the probe definitions

From: Masami Hiramatsu Add --cache option to cache the probe definitions. This just saves the result of the dwarf analysis to probe cache. Signed-off-by: Masami Hiramatsu Signed-off-by: Masami Hiramatsu --- Changes in v6: - Remove unneeded O_APPEND from open(). (Thanks Namhyung!) - Fix

[PATCH perf/core v8 06/16] perf probe: Show all cached probes

From: Masami Hiramatsu perf probe --list shows all cached probes when --cache is given. Each caches are shown with on which binary that probed. e.g. - # perf probe --cache vfs_read \$params # perf probe --cache -x /lib64/libc-2.17.so getaddrinfo \$params # perf probe --cache --list

[PATCH perf/core v8 09/16] perf probe: Add group name support

From: Masami Hiramatsu Allow user to set group name for adding new event. Note that user must ensure that the group name doesn't conflict with existing group name carefully. E.g. Existing group name can conflict with other events. Especially, using the group name reserved for kernel modules can

[PATCH perf/core v8 02/16] perf symbol: Cleanup the code flow of dso__find_kallsyms

Cleanup the code flow of dso__find_kallsyms() to remove redundant checking code and add some comment for readability. Signed-off-by: Masami Hiramatsu --- Changes in v8: - Add comments why we can't use access(R_OK) for /proc/kcore access. --- tools/perf/util/symbol.c |

[PATCH perf/core v8 02/16] perf symbol: Cleanup the code flow of dso__find_kallsyms

Cleanup the code flow of dso__find_kallsyms() to remove redundant checking code and add some comment for readability. Signed-off-by: Masami Hiramatsu --- Changes in v8: - Add comments why we can't use access(R_OK) for /proc/kcore access. --- tools/perf/util/symbol.c | 68

[PATCH perf/core v8 01/16] perf buildid: Introduce DSO__NAME_KALLSYMS and DSO__NAME_KCORE

Instead of using raw string, use DSO__NAME_KALLSYMS and DSO__NAME_KCORE macros for kallsyms and kcore. Signed-off-by: Masami Hiramatsu --- tools/perf/builtin-buildid-cache.c |8 tools/perf/util/annotate.c |2 +- tools/perf/util/machine.c |

[PATCH perf/core v8 00/16] perf-probe --cache and SDT support

Hi, Here is the 8th version of the patchset for probe-cache and initial SDT support. The previous version is here; https://lkml.org/lkml/2016/5/11/446 This version I droped the second patch in v7 because it may involves unintended behavior change and we'd better discuss it out of this series.

[PATCH perf/core v8 01/16] perf buildid: Introduce DSO__NAME_KALLSYMS and DSO__NAME_KCORE

Instead of using raw string, use DSO__NAME_KALLSYMS and DSO__NAME_KCORE macros for kallsyms and kcore. Signed-off-by: Masami Hiramatsu --- tools/perf/builtin-buildid-cache.c |8 tools/perf/util/annotate.c |2 +- tools/perf/util/machine.c |2 +-

[PATCH perf/core v8 00/16] perf-probe --cache and SDT support

Hi, Here is the 8th version of the patchset for probe-cache and initial SDT support. The previous version is here; https://lkml.org/lkml/2016/5/11/446 This version I droped the second patch in v7 because it may involves unintended behavior change and we'd better discuss it out of this series.

[PATCH] scripts/package/Makefile: rpmbuild add support of RPMOPTS

After commit 21a59991ce0c ("scripts/package/Makefile: rpmbuild is needed for rpm targets"), it is no longer possible to specify RPMOPTS. For example, we can no longer able to control _topdir using the following make command. make RPMOPTS="--define '_topdir /home/xyz/workspace/'" binrpm-pkg Fixes:

[PATCH] scripts/package/Makefile: rpmbuild add support of RPMOPTS

After commit 21a59991ce0c ("scripts/package/Makefile: rpmbuild is needed for rpm targets"), it is no longer possible to specify RPMOPTS. For example, we can no longer able to control _topdir using the following make command. make RPMOPTS="--define '_topdir /home/xyz/workspace/'" binrpm-pkg Fixes:

Re: Unclear BSD licensing (headers, MODULE_LICENSE, versions)

On Sun, May 15, 2016 at 12:44:35AM +0200, Rafał Miłecki wrote: > > I recently received a hint that it would be nice/expected to have DTS > files licensed under BSD. I had no experience with BSD, so I started > looking at this and the way kernel parts use it. There is a lot of sloppiness in some

Re: Unclear BSD licensing (headers, MODULE_LICENSE, versions)

On Sun, May 15, 2016 at 12:44:35AM +0200, Rafał Miłecki wrote: > > I recently received a hint that it would be nice/expected to have DTS > files licensed under BSD. I had no experience with BSD, so I started > looking at this and the way kernel parts use it. There is a lot of sloppiness in some

Re: [RFC v2 PATCH 0/8] VFS:userns: support portable root filesystems

James Bottomley writes: > On Sat, 2016-05-14 at 10:53 +0100, Djalal Harouni wrote: Just a couple of quick comments from a very high level design point. - I think a shiftfs is valuable in the same way that overlayfs is valuable. Esepcially in the

Re: [RFC v2 PATCH 0/8] VFS:userns: support portable root filesystems

James Bottomley writes: > On Sat, 2016-05-14 at 10:53 +0100, Djalal Harouni wrote: Just a couple of quick comments from a very high level design point. - I think a shiftfs is valuable in the same way that overlayfs is valuable. Esepcially in the Docker case where a lot of containers want

Re: [PATCH 1/1 v2] hwmon: add support for Sensirion SHT3x sensors

On 04/25/2016 01:42 AM, Pascal Sachs wrote: From: David Frey This driver implements support for the Sensirion SHT3x-DIS chip, a humidity and temperature sensor. Temperature is measured in degrees celsius, relative humidity is expressed as a percentage. In the sysfs

Re: [PATCH 1/1 v2] hwmon: add support for Sensirion SHT3x sensors

On 04/25/2016 01:42 AM, Pascal Sachs wrote: From: David Frey This driver implements support for the Sensirion SHT3x-DIS chip, a humidity and temperature sensor. Temperature is measured in degrees celsius, relative humidity is expressed as a percentage. In the sysfs interface, all values are

[PATCH] Staging: android: ion: fixed a kzalloc coding style issue.

Fixed a coding style issue. Issue reported by checkpatch.pl. Signed-off-by: Shubham Bansal --- drivers/staging/android/ion/ion.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/android/ion/ion.c b/drivers/staging/android/ion/ion.c

[PATCH] Staging: android: ion: fixed a kzalloc coding style issue.

Fixed a coding style issue. Issue reported by checkpatch.pl. Signed-off-by: Shubham Bansal --- drivers/staging/android/ion/ion.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/android/ion/ion.c b/drivers/staging/android/ion/ion.c index 8536567..2217ccb

Re: [PATCH] ftrace/x86: Fix function graph tracer reset path

Hi Namhyung, I'm interested in this problem, and it seems compiling environment related or kconfig related problem. If you can reproduce this kernel, would you share what the "AS" commandline shows? That can be done as below; $ make V=1 arch/x86/kernel/mcount_64.o | grep mcount_64 Thank you,

Re: [PATCH] ftrace/x86: Fix function graph tracer reset path

Hi Namhyung, I'm interested in this problem, and it seems compiling environment related or kconfig related problem. If you can reproduce this kernel, would you share what the "AS" commandline shows? That can be done as below; $ make V=1 arch/x86/kernel/mcount_64.o | grep mcount_64 Thank you,

Re: [PATCH 3.14 01/23] compiler-gcc: integrate the various compiler-gcc[345].h files

On Wed, May 11, 2016 at 11:27:10AM +0200, Jiri Slaby wrote: > On 05/09/2016, 09:17 AM, Greg Kroah-Hartman wrote: > > 3.14-stable review patch. If anyone has any objections, please let me know. > > > > -- > > > > From: Joe Perches > > > > commit

Re: [PATCH 3.14 01/23] compiler-gcc: integrate the various compiler-gcc[345].h files

On Wed, May 11, 2016 at 11:27:10AM +0200, Jiri Slaby wrote: > On 05/09/2016, 09:17 AM, Greg Kroah-Hartman wrote: > > 3.14-stable review patch. If anyone has any objections, please let me know. > > > > -- > > > > From: Joe Perches > > > > commit

Unclear BSD licensing (headers, MODULE_LICENSE, versions)

Hi, I recently received a hint that it would be nice/expected to have DTS files licensed under BSD. I had no experience with BSD, so I started looking at this and the way kernel parts use it. Obviously Linux kernel is licensed under GPLv2, so all its code has to use GPLv2 compatible license. I

Unclear BSD licensing (headers, MODULE_LICENSE, versions)

Hi, I recently received a hint that it would be nice/expected to have DTS files licensed under BSD. I had no experience with BSD, so I started looking at this and the way kernel parts use it. Obviously Linux kernel is licensed under GPLv2, so all its code has to use GPLv2 compatible license. I

Re: [RFC][PATCH] printk: Add option to append kernel version to the dict

On Fri, May 13, 2016 at 10:58 PM, Calvin Owens wrote: > We use netconsole to collect kernel logs from all the servers at > Facebook. We use this patch internally so each logline has a record of > which kernel version emitted it. > > At first glance, this might seem lazy: as

Re: [RFC][PATCH] printk: Add option to append kernel version to the dict

On Fri, May 13, 2016 at 10:58 PM, Calvin Owens wrote: > We use netconsole to collect kernel logs from all the servers at > Facebook. We use this patch internally so each logline has a record of > which kernel version emitted it. > > At first glance, this might seem lazy: as you would expect, we

Re: [PATCH RFT 1/2] phylib: add device reset GPIO support

Hello. On 05/14/2016 10:50 PM, Andrew Lunn wrote: Another issue is that on some boards we have one reset line tied to multiple PHYs.How do we prevent multiple resets being taking place when each of the PHYs are registered? My patch just doesn't address this case -- it's about the individual

Re: [PATCH RFT 1/2] phylib: add device reset GPIO support

Hello. On 05/14/2016 10:50 PM, Andrew Lunn wrote: Another issue is that on some boards we have one reset line tied to multiple PHYs.How do we prevent multiple resets being taking place when each of the PHYs are registered? My patch just doesn't address this case -- it's about the individual

[PATCH v4 2/4] ASoC: MAX9860: new driver

This is a driver for the MAX9860 Mono Audio Voice Codec. https://datasheets.maximintegrated.com/en/ds/MAX9860.pdf This driver does not support sidetone since the DVST register field is backwards with the mute near the maximum level instead of the minimum. Signed-off-by: Peter Rosin

[PATCH v4 2/4] ASoC: MAX9860: new driver

This is a driver for the MAX9860 Mono Audio Voice Codec. https://datasheets.maximintegrated.com/en/ds/MAX9860.pdf This driver does not support sidetone since the DVST register field is backwards with the mute near the maximum level instead of the minimum. Signed-off-by: Peter Rosin ---

[PATCH v4 3/4] ASoC: dapm: support mixer controls with mute at non-zero value

The max9860 codec has a mixer control field that has its mute/disable at the wrong end of the scale. I.e. you turn the volume up and up, and then as the final step the volume is off. This does not sit well with DAPM, which assumes the mute/off is at the minimum value. Add support for such

[PATCH v4 0/4] ASoC: MAX9860: new driver

Hi! I kept the sidetone changes in separate patches since I don't know if I solved the DAPM-off issue cleanly enough. Also, a new driver may still have a chance to make 4.7, but maybe it's too late for the DAPM changes? Finally, I wonder if the device tree crowd prefers seeing the whole of a

[PATCH v4 3/4] ASoC: dapm: support mixer controls with mute at non-zero value

The max9860 codec has a mixer control field that has its mute/disable at the wrong end of the scale. I.e. you turn the volume up and up, and then as the final step the volume is off. This does not sit well with DAPM, which assumes the mute/off is at the minimum value. Add support for such

[PATCH v4 0/4] ASoC: MAX9860: new driver

Hi! I kept the sidetone changes in separate patches since I don't know if I solved the DAPM-off issue cleanly enough. Also, a new driver may still have a chance to make 4.7, but maybe it's too late for the DAPM changes? Finally, I wonder if the device tree crowd prefers seeing the whole of a

Re: [PATCH net-next] net: switchdev: Drop EXPERIMENTAL from description

From: Florian Fainelli Date: Sat, 14 May 2016 12:49:54 -0700 > Switchdev has been around for quite a while now, putting "EXPERIMENTAL" > in the description is no longer accurate, drop it. > > Signed-off-by: Florian Fainelli Yeah this is long

Re: [PATCH net-next] net: switchdev: Drop EXPERIMENTAL from description

From: Florian Fainelli Date: Sat, 14 May 2016 12:49:54 -0700 > Switchdev has been around for quite a while now, putting "EXPERIMENTAL" > in the description is no longer accurate, drop it. > > Signed-off-by: Florian Fainelli Yeah this is long overdue, applied, thanks.

Re: [PATCH RFT 1/2] phylib: add device reset GPIO support

Hello. On 05/13/2016 10:18 PM, Sergei Shtylyov wrote: [we already talked about this patch in #armlinux, I'm now just forwarding my comments on the list. Background was that I sent an easier and less complete patch with the same idea. See http://patchwork.ozlabs.org/patch/621418/] [added Linus

[PATCH v4 4/4] ASoC: MAX9860: add sidetone mixer control

Signed-off-by: Peter Rosin --- sound/soc/codecs/max9860.c | 22 +- 1 file changed, 17 insertions(+), 5 deletions(-) diff --git a/sound/soc/codecs/max9860.c b/sound/soc/codecs/max9860.c index 2b0dd6a18dad..8d257cc20ef7 100644 --- a/sound/soc/codecs/max9860.c

[PATCH v4 1/4] dt-bindings: sound: add bindings for the max9860 codec

This adds the device tree binding documentation for the Maxim Integrated MAX9860 mono audio voice codec. Acked-by: Rob Herring Signed-off-by: Peter Rosin --- .../devicetree/bindings/sound/max9860.txt | 28 ++ 1 file changed, 28

Re: [PATCH RFT 1/2] phylib: add device reset GPIO support

Hello. On 05/13/2016 10:18 PM, Sergei Shtylyov wrote: [we already talked about this patch in #armlinux, I'm now just forwarding my comments on the list. Background was that I sent an easier and less complete patch with the same idea. See http://patchwork.ozlabs.org/patch/621418/] [added Linus

[PATCH v4 4/4] ASoC: MAX9860: add sidetone mixer control

Signed-off-by: Peter Rosin --- sound/soc/codecs/max9860.c | 22 +- 1 file changed, 17 insertions(+), 5 deletions(-) diff --git a/sound/soc/codecs/max9860.c b/sound/soc/codecs/max9860.c index 2b0dd6a18dad..8d257cc20ef7 100644 --- a/sound/soc/codecs/max9860.c +++

[PATCH v4 1/4] dt-bindings: sound: add bindings for the max9860 codec

This adds the device tree binding documentation for the Maxim Integrated MAX9860 mono audio voice codec. Acked-by: Rob Herring Signed-off-by: Peter Rosin --- .../devicetree/bindings/sound/max9860.txt | 28 ++ 1 file changed, 28 insertions(+) create mode 100644

Re: [PATCH] usb: gadget: f_fs: report error if excess data received

On Fri, May 13 2016, Alan Stern wrote: > The point is that you don't know whether the host sent more data than > expected. All you know is that the host sent more data than the user > asked the kernel for -- but maybe the user didn't ask for all the data > that he expected. Maybe the user wanted

Re: [PATCH] usb: gadget: f_fs: report error if excess data received

On Fri, May 13 2016, Alan Stern wrote: > The point is that you don't know whether the host sent more data than > expected. All you know is that the host sent more data than the user > asked the kernel for -- but maybe the user didn't ask for all the data > that he expected. Maybe the user wanted

Re: [PATCH net-next] net: switchdev: Drop EXPERIMENTAL from description

Sat, May 14, 2016 at 09:49:54PM CEST, f.faine...@gmail.com wrote: >Switchdev has been around for quite a while now, putting "EXPERIMENTAL" >in the description is no longer accurate, drop it. > >Signed-off-by: Florian Fainelli Acked-by: Jiri Pirko

Re: [PATCH net-next] net: switchdev: Drop EXPERIMENTAL from description

Sat, May 14, 2016 at 09:49:54PM CEST, f.faine...@gmail.com wrote: >Switchdev has been around for quite a while now, putting "EXPERIMENTAL" >in the description is no longer accurate, drop it. > >Signed-off-by: Florian Fainelli Acked-by: Jiri Pirko

Re: [PATCH] iommu/rockchip: fix zap cache during device attach

Am Dienstag, 10. Mai 2016, 16:50:46 schrieb John Keeping: > rk_iommu_command() takes a struct rk_iommu and iterates over the slave > MMUs, so this is doubly wrong in that we're passing in the wrong pointer > and talking to MMUs that we shouldn't be. > > Fixes: cd6438c5f844 ("iommu/rockchip:

Re: [PATCH] iommu/rockchip: fix zap cache during device attach

Am Dienstag, 10. Mai 2016, 16:50:46 schrieb John Keeping: > rk_iommu_command() takes a struct rk_iommu and iterates over the slave > MMUs, so this is doubly wrong in that we're passing in the wrong pointer > and talking to MMUs that we shouldn't be. > > Fixes: cd6438c5f844 ("iommu/rockchip:

[GIT] Networking

1) Fix mvneta/bm dependencies, from Arnd Bergmann. 2) RX completion hw bug workaround in bnxt_en, from Michael Chan. 3) Kernel pointer leak in nf_conntrack, from Linus. 4) Hoplimit route attribute limits not enforced properly, from Paolo Abeni. 5) qlcnic driver NULL deref fix from Dan

[GIT] Networking

1) Fix mvneta/bm dependencies, from Arnd Bergmann. 2) RX completion hw bug workaround in bnxt_en, from Michael Chan. 3) Kernel pointer leak in nf_conntrack, from Linus. 4) Hoplimit route attribute limits not enforced properly, from Paolo Abeni. 5) qlcnic driver NULL deref fix from Dan

Re: [PATCH v2] drm/amd/powerplay: use ARRAY_SIZE() to calculate array size.

Am 13.05.2016 um 19:36 schrieb Muhammad Falak R Wani: It is preferred to use ARRAY_SIZE() for size calculation, instead using sizeof(array)/sizeof(*array). It makes the code more readable. Signed-off-by: Muhammad Falak R Wani Reviewed-by: Christian König

Re: [PATCH v2] drm/amd/powerplay: use ARRAY_SIZE() to calculate array size.

Am 13.05.2016 um 19:36 schrieb Muhammad Falak R Wani: It is preferred to use ARRAY_SIZE() for size calculation, instead using sizeof(array)/sizeof(*array). It makes the code more readable. Signed-off-by: Muhammad Falak R Wani Reviewed-by: Christian König Thanks for the cleanup, Christian.

Re: [PATCH RFT 1/2] phylib: add device reset GPIO support

On Sat, May 14, 2016 at 10:36:38PM +0300, Sergei Shtylyov wrote: > Hello. > > On 05/14/2016 02:44 AM, Andrew Lunn wrote: > > >Another issue is that on some boards we have one reset line tied to > >multiple PHYs.How do we prevent multiple resets being taking place when > >each of >

Re: [PATCH RFT 1/2] phylib: add device reset GPIO support

On Sat, May 14, 2016 at 10:36:38PM +0300, Sergei Shtylyov wrote: > Hello. > > On 05/14/2016 02:44 AM, Andrew Lunn wrote: > > >Another issue is that on some boards we have one reset line tied to > >multiple PHYs.How do we prevent multiple resets being taking place when > >each of >

[PATCH net-next] net: switchdev: Drop EXPERIMENTAL from description

Switchdev has been around for quite a while now, putting "EXPERIMENTAL" in the description is no longer accurate, drop it. Signed-off-by: Florian Fainelli --- net/switchdev/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/net/switchdev/Kconfig

[PATCH net-next] net: switchdev: Drop EXPERIMENTAL from description

Switchdev has been around for quite a while now, putting "EXPERIMENTAL" in the description is no longer accurate, drop it. Signed-off-by: Florian Fainelli --- net/switchdev/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/net/switchdev/Kconfig b/net/switchdev/Kconfig

  1   2   3   >