Re: [RFC v3 09/10] iommu/arm-smmu: Implement reserved region get/put callbacks

Hi Robin, On 07/12/2016 19:24, Robin Murphy wrote: > On 07/12/16 15:02, Auger Eric wrote: >> Hi Robin, >> On 06/12/2016 19:55, Robin Murphy wrote: >>> On 15/11/16 13:09, Eric Auger wrote: The get() populates the list with the PCI host bridge windows and the MSI IOVA range. At

Re: [RFC v3 09/10] iommu/arm-smmu: Implement reserved region get/put callbacks

Hi Robin, On 07/12/2016 19:24, Robin Murphy wrote: > On 07/12/16 15:02, Auger Eric wrote: >> Hi Robin, >> On 06/12/2016 19:55, Robin Murphy wrote: >>> On 15/11/16 13:09, Eric Auger wrote: The get() populates the list with the PCI host bridge windows and the MSI IOVA range. At

[PATCH 0/2] Determine kernel text mapping size at runtime for x86_64

Dave Anderson ever told in Crash utility he makes judgement whether it's a kaslr kernel by size of KERNEL_IMAGE_SIZE. As long as it's 1G, it's recognized as kaslr. Then the current upstream kernel has a wrong behaviour, it sets KERNEL_IMAGE_SIZE as 1G as long as CONFIG_RANDOMIZE_BASE is enabled,

[PATCH 2/2] x86/KASLR/64: Determine kernel text mapping size at runtime

X86 64 kernel takes KERNEL_IMAGE_SIZE as the kernel text mapping size, and it's fixed as compiling time, changing from 512M to 1G as long as CONFIG_RANDOMIZE_BASE is enabled, though people specify kernel option "nokaslr" explicitly. This could be a wrong behaviour. CONFIG_RANDOMIZE_BASE should

[PATCH 1/2] x86/64: Make kernel text mapping always take one whole page table in early boot code

In early boot code level2_kernel_pgt is used to map kernel text. And its size varies according to KERNEL_IMAGE_SIZE and fixed at compiling time. In fact we can make it always takes 512 entries of one whople page table, because later function cleanup_highmap will clean up the unused entries. With

[PATCH 0/2] Determine kernel text mapping size at runtime for x86_64

Dave Anderson ever told in Crash utility he makes judgement whether it's a kaslr kernel by size of KERNEL_IMAGE_SIZE. As long as it's 1G, it's recognized as kaslr. Then the current upstream kernel has a wrong behaviour, it sets KERNEL_IMAGE_SIZE as 1G as long as CONFIG_RANDOMIZE_BASE is enabled,

[PATCH 2/2] x86/KASLR/64: Determine kernel text mapping size at runtime

X86 64 kernel takes KERNEL_IMAGE_SIZE as the kernel text mapping size, and it's fixed as compiling time, changing from 512M to 1G as long as CONFIG_RANDOMIZE_BASE is enabled, though people specify kernel option "nokaslr" explicitly. This could be a wrong behaviour. CONFIG_RANDOMIZE_BASE should

[PATCH 1/2] x86/64: Make kernel text mapping always take one whole page table in early boot code

In early boot code level2_kernel_pgt is used to map kernel text. And its size varies according to KERNEL_IMAGE_SIZE and fixed at compiling time. In fact we can make it always takes 512 entries of one whople page table, because later function cleanup_highmap will clean up the unused entries. With

[PATCH] memremap: Remove unused align_* variables

Commit eb7d78c9e7f6 introduced align_start, align_size and align_end variables in pgmap_radix_release() but did not use them. Compiling with W=1 gives the following harmless warning, fix it to reduce the noise with W=1 in the kernel. kernel/memremap.c: In function ‘pgmap_radix_release’:

[PATCH] memremap: Remove unused align_* variables

Commit eb7d78c9e7f6 introduced align_start, align_size and align_end variables in pgmap_radix_release() but did not use them. Compiling with W=1 gives the following harmless warning, fix it to reduce the noise with W=1 in the kernel. kernel/memremap.c: In function ‘pgmap_radix_release’:

Re: [RFC v3 00/10] KVM PCIe/MSI passthrough on ARM/ARM64 and IOVA reserved regions

Hi Shanker, On 07/12/2016 19:52, Shanker Donthineni wrote: > Hi Eric, > > Is there any reason why you are not supporting SMMUv3 driver? Qualcomm > hardware doesn't not support SMMUv2 hardware, please add support for > SMMUv3 in next patch set. I've ported ' RFC,v3,09/10] iommu/arm-smmu: >

Re: [RFC v3 00/10] KVM PCIe/MSI passthrough on ARM/ARM64 and IOVA reserved regions

Hi Shanker, On 07/12/2016 19:52, Shanker Donthineni wrote: > Hi Eric, > > Is there any reason why you are not supporting SMMUv3 driver? Qualcomm > hardware doesn't not support SMMUv2 hardware, please add support for > SMMUv3 in next patch set. I've ported ' RFC,v3,09/10] iommu/arm-smmu: >

Re: [PATCHv13,1/3] lib/string: add sysfs_match_string helper

On Wed, Dec 07, 2016 at 03:54:45PM -0800, Guenter Roeck wrote: > > +int __sysfs_match_string(const char * const *array, size_t n, const char > > *str) > > +{ > > + const char *item; > > + int index; > > + > > + for (index = 0; index < n; index++) { > > + item = array[index]; > > +

Re: [PATCHv13,1/3] lib/string: add sysfs_match_string helper

On Wed, Dec 07, 2016 at 03:54:45PM -0800, Guenter Roeck wrote: > > +int __sysfs_match_string(const char * const *array, size_t n, const char > > *str) > > +{ > > + const char *item; > > + int index; > > + > > + for (index = 0; index < n; index++) { > > + item = array[index]; > > +

[PATCH v2 2/2] net: rfkill: Add rfkill-any LED trigger

Add a new "global" (i.e. not per-rfkill device) LED trigger, rfkill-any, which may be useful on laptops with a single "radio LED" and multiple radio transmitters. The trigger is meant to turn a LED on whenever there is at least one radio transmitter active and turn it off otherwise.

[PATCH v2 1/2] net: rfkill: Cleanup error handling in rfkill_init()

Use a separate label per error condition in rfkill_init() to make it a bit cleaner and easier to extend. Signed-off-by: Michał Kępień --- No changes from v1. net/rfkill/core.c | 23 --- 1 file changed, 12 insertions(+), 11 deletions(-) diff --git

[PATCH v2 2/2] net: rfkill: Add rfkill-any LED trigger

Add a new "global" (i.e. not per-rfkill device) LED trigger, rfkill-any, which may be useful on laptops with a single "radio LED" and multiple radio transmitters. The trigger is meant to turn a LED on whenever there is at least one radio transmitter active and turn it off otherwise.

[PATCH v2 1/2] net: rfkill: Cleanup error handling in rfkill_init()

Use a separate label per error condition in rfkill_init() to make it a bit cleaner and easier to extend. Signed-off-by: Michał Kępień --- No changes from v1. net/rfkill/core.c | 23 --- 1 file changed, 12 insertions(+), 11 deletions(-) diff --git a/net/rfkill/core.c

Re: [PATCH v2] PCI: designware: add host_init error handling

Hi Srinivas, On Wed, 7 Dec 2016 10:32:49 + Srinivas Kandagatla wrote: > This patch add support to return value from host_init() callback from drivers, > so that the designware libary can handle or pass it to proper place. Issue > with > void return type is that errors or error handling

RE: [RFC v3 00/10] KVM PCIe/MSI passthrough on ARM/ARM64 and IOVA reserved regions

Hi Eric, I have tested this series on NXP platform. Thanks -Bharat > -Original Message- > From: iommu-boun...@lists.linux-foundation.org [mailto:iommu- > boun...@lists.linux-foundation.org] On Behalf Of Eric Auger > Sent: Tuesday, November 15, 2016 6:39 PM > To: eric.au...@redhat.com;

Re: [PATCH v2] PCI: designware: add host_init error handling

Hi Srinivas, On Wed, 7 Dec 2016 10:32:49 + Srinivas Kandagatla wrote: > This patch add support to return value from host_init() callback from drivers, > so that the designware libary can handle or pass it to proper place. Issue > with > void return type is that errors or error handling

RE: [RFC v3 00/10] KVM PCIe/MSI passthrough on ARM/ARM64 and IOVA reserved regions

Hi Eric, I have tested this series on NXP platform. Thanks -Bharat > -Original Message- > From: iommu-boun...@lists.linux-foundation.org [mailto:iommu- > boun...@lists.linux-foundation.org] On Behalf Of Eric Auger > Sent: Tuesday, November 15, 2016 6:39 PM > To: eric.au...@redhat.com;

[PATCH v2 1/2] dt-bindings: display: Add BOE nv101wxmn51 panel binding

The BOE 10.1" NV101WXMN51 panel is an WXGA TFT LCD panel. Signed-off-by: Caesar Wang --- Changes in v2: None .../devicetree/bindings/display/panel/boe,nv101wxmn51.txt | 7 +++ 1 file changed, 7 insertions(+) create mode 100644

[PATCH v2 1/2] dt-bindings: display: Add BOE nv101wxmn51 panel binding

The BOE 10.1" NV101WXMN51 panel is an WXGA TFT LCD panel. Signed-off-by: Caesar Wang --- Changes in v2: None .../devicetree/bindings/display/panel/boe,nv101wxmn51.txt | 7 +++ 1 file changed, 7 insertions(+) create mode 100644

[PATCH v2 2/2] drm/panel: simple: Add support BOE nv101wxmn51

10.1WXGA is a color active matrix TFT LCD module using amorphous silicon TFT's as an active switching devices. It can be supported by the simple-panel driver. Read the panel edid information; EDID MODE DETAILS name = pixel_clock = 71900

[PATCH v2 2/2] drm/panel: simple: Add support BOE nv101wxmn51

10.1WXGA is a color active matrix TFT LCD module using amorphous silicon TFT's as an active switching devices. It can be supported by the simple-panel driver. Read the panel edid information; EDID MODE DETAILS name = pixel_clock = 71900

Re: [PATCH v4 2/2] usb: dwc3: core: Support the dwc3 host suspend/resume

Hi Felipe, On 28 November 2016 at 14:43, Baolin Wang wrote: > For some mobile devices with strict power management, we also want to suspend > the host when the slave is detached for power saving. Thus we add the host > suspend/resume functions to support this requirement.

Re: [PATCH v4 2/2] usb: dwc3: core: Support the dwc3 host suspend/resume

Hi Felipe, On 28 November 2016 at 14:43, Baolin Wang wrote: > For some mobile devices with strict power management, we also want to suspend > the host when the slave is detached for power saving. Thus we add the host > suspend/resume functions to support this requirement. > > Signed-off-by:

Re: [PATCH] Bluetooth: btmrvl: drop duplicate header slab.h

Hi Geliang, > Drop duplicate header slab.h from btmrvl_drv.h. > > Signed-off-by: Geliang Tang > --- > drivers/bluetooth/btmrvl_drv.h | 1 - > 1 file changed, 1 deletion(-) patch has been applied to bluetooth-next tree. Regards Marcel

Re: [PATCH] Bluetooth: btmrvl: drop duplicate header slab.h

Hi Geliang, > Drop duplicate header slab.h from btmrvl_drv.h. > > Signed-off-by: Geliang Tang > --- > drivers/bluetooth/btmrvl_drv.h | 1 - > 1 file changed, 1 deletion(-) patch has been applied to bluetooth-next tree. Regards Marcel

Re: [PATCH v4 1/2] usb: host: plat: Enable xhci plat runtime PM

Hi Mathias and Felipe, On 28 November 2016 at 14:43, Baolin Wang wrote: > Enable the xhci plat runtime PM for parent device to suspend/resume xhci. > Also call pm_runtime_get_noresume() in probe() function in case the parent > device doesn't call suspend/resume callback

Re: [PATCH v4 1/2] usb: host: plat: Enable xhci plat runtime PM

Hi Mathias and Felipe, On 28 November 2016 at 14:43, Baolin Wang wrote: > Enable the xhci plat runtime PM for parent device to suspend/resume xhci. > Also call pm_runtime_get_noresume() in probe() function in case the parent > device doesn't call suspend/resume callback by runtime PM now. > >

Re: [PATCH] xen/pci: Bubble up error and fix description.

On 06/12/16 15:28, Konrad Rzeszutek Wilk wrote: > The function is never called under PV guests, and only shows up > when MSI (or MSI-X) cannot be allocated. Convert the message > to include the error value. > > Signed-off-by: Konrad Rzeszutek Wilk Commited to xen/tip.git

Re: [PATCH] xen/pci: Bubble up error and fix description.

On 06/12/16 15:28, Konrad Rzeszutek Wilk wrote: > The function is never called under PV guests, and only shows up > when MSI (or MSI-X) cannot be allocated. Convert the message > to include the error value. > > Signed-off-by: Konrad Rzeszutek Wilk Commited to xen/tip.git for-linus-4.10

Re: [PATCH v2] inotify: Convert to using per-namespace limits

On 8.12.2016 03:40, Eric W. Biederman wrote: > Nikolay Borisov writes: > >> Gentle ping, now that rc1 has shipped and Jan's sysctl concern hopefully >> resolved. > > After getting slowed down by some fixes I am now taking a hard look at > your patch in the hopes of merging

Re: [PATCH v2] inotify: Convert to using per-namespace limits

On 8.12.2016 03:40, Eric W. Biederman wrote: > Nikolay Borisov writes: > >> Gentle ping, now that rc1 has shipped and Jan's sysctl concern hopefully >> resolved. > > After getting slowed down by some fixes I am now taking a hard look at > your patch in the hopes of merging it. > > Did you

Re: [PATCH 1/1 v2] xen: xenbus: set error code on failure

On 05/12/16 09:22, Pan Bian wrote: > Variable err is initialized with 0. As a result, the return value may > be 0 even if get_zeroed_page() fails to allocate memory. This patch fixes > the bug, initializing err with "-ENOMEM". > > v1 is reviewed by: Juergen Gross > >

Re: [PATCH 1/1 v2] xen: xenbus: set error code on failure

On 05/12/16 09:22, Pan Bian wrote: > Variable err is initialized with 0. As a result, the return value may > be 0 even if get_zeroed_page() fails to allocate memory. This patch fixes > the bug, initializing err with "-ENOMEM". > > v1 is reviewed by: Juergen Gross > > Signed-off-by: Pan Bian

Re: [PATCH 1/1 v2] xen: set error code on failures

On 05/12/16 09:23, Pan Bian wrote: > Variable rc is reset in the loop, and its value will be non-negative > during the second and after repeat of the loop. If it fails to allocate > memory then, it may return a non-negative integer, which indicates no > error. This patch fixes the bug, assigning

Re: [PATCH 1/1 v2] xen: set error code on failures

On 05/12/16 09:23, Pan Bian wrote: > Variable rc is reset in the loop, and its value will be non-negative > during the second and after repeat of the loop. If it fails to allocate > memory then, it may return a non-negative integer, which indicates no > error. This patch fixes the bug, assigning

Re: [PATCH 5/8] efi: Get the secure boot status [ver #5]

On Wed, Dec 07, 2016 at 01:18:39PM +, David Howells wrote: > @@ -226,7 +180,7 @@ unsigned long efi_entry(void *handle, efi_system_table_t > *sys_table, > efi_guid_t loaded_image_proto = LOADED_IMAGE_PROTOCOL_GUID; > unsigned long reserve_addr = 0; > unsigned long

Re: [PATCH 5/8] efi: Get the secure boot status [ver #5]

On Wed, Dec 07, 2016 at 01:18:39PM +, David Howells wrote: > @@ -226,7 +180,7 @@ unsigned long efi_entry(void *handle, efi_system_table_t > *sys_table, > efi_guid_t loaded_image_proto = LOADED_IMAGE_PROTOCOL_GUID; > unsigned long reserve_addr = 0; > unsigned long

[PATCH 3/3] hv_netvsc: Implement VF matching based on serial numbers

From: Haiyang Zhang We currently use MAC address to match VF and synthetic NICs. Hyper-V provides a serial number to both devices for this purpose. This patch implements the matching based on VF serial numbers. This is the way specified by the protocol and more reliable.

[PATCH] fsl/usb: Add USB node in FSL's ls1012a DTS

Add USB node in ls1012a device tree Signed-off-by: Changming Huang --- Dependence on patch "[v3] arm64: Add DTS support for FSL's LS1012A SoC". https://patchwork.kernel.org/patch/9462399/ arch/arm64/boot/dts/freescale/fsl-ls1012a.dtsi | 17 + 1 file

[PATCH 3/3] hv_netvsc: Implement VF matching based on serial numbers

From: Haiyang Zhang We currently use MAC address to match VF and synthetic NICs. Hyper-V provides a serial number to both devices for this purpose. This patch implements the matching based on VF serial numbers. This is the way specified by the protocol and more reliable. Signed-off-by: Haiyang

[PATCH] fsl/usb: Add USB node in FSL's ls1012a DTS

Add USB node in ls1012a device tree Signed-off-by: Changming Huang --- Dependence on patch "[v3] arm64: Add DTS support for FSL's LS1012A SoC". https://patchwork.kernel.org/patch/9462399/ arch/arm64/boot/dts/freescale/fsl-ls1012a.dtsi | 17 + 1 file changed, 17 insertions(+)

[PATCH 2/3] hyperv: Add a function to detect if the device is a vmbus dev

From: Haiyang Zhang On Hyper-V, every VF interface has a corresponding synthetic interface managed by netvsc that share the same MAC address. netvsc registers for netdev events to manage this association. Currently we use the MAC address to manage this association but

Re: [PATCH] linux/types.h: enable endian checks for all sparse builds

On 12/07/16 21:54, Michael S. Tsirkin wrote: > On Thu, Dec 08, 2016 at 05:21:47AM +, Bart Van Assche wrote: >> Additionally, there are notable exceptions to the rule that most drivers >> are endian-clean, e.g. drivers/scsi/qla2xxx. I would appreciate it if it >> would remain possible to check

Re: [PATCH] linux/types.h: enable endian checks for all sparse builds

On 12/07/16 21:54, Michael S. Tsirkin wrote: > On Thu, Dec 08, 2016 at 05:21:47AM +, Bart Van Assche wrote: >> Additionally, there are notable exceptions to the rule that most drivers >> are endian-clean, e.g. drivers/scsi/qla2xxx. I would appreciate it if it >> would remain possible to check

[PATCH 2/3] hyperv: Add a function to detect if the device is a vmbus dev

From: Haiyang Zhang On Hyper-V, every VF interface has a corresponding synthetic interface managed by netvsc that share the same MAC address. netvsc registers for netdev events to manage this association. Currently we use the MAC address to manage this association but going forward, we want to

[PATCH 1/3] hyperv: Move hv_pci_dev and related structs to hyperv.h

From: Haiyang Zhang Move some vPCI data structures to hyperv.h, because we share them with other module. Signed-off-by: Haiyang Zhang Signed-off-by: K. Y. Srinivasan --- drivers/pci/host/pci-hyperv.c | 91

[PATCH 1/3] hyperv: Move hv_pci_dev and related structs to hyperv.h

From: Haiyang Zhang Move some vPCI data structures to hyperv.h, because we share them with other module. Signed-off-by: Haiyang Zhang Signed-off-by: K. Y. Srinivasan --- drivers/pci/host/pci-hyperv.c | 91 -- include/linux/hyperv.h| 98

[PATCH 0/3] Drivers: hv: Implement VF association based on serial number

From: K. Y. Srinivasan Implement VF association based on serial number published by the host. Greg, as promised here is the patchset that would use the API for detecting if the device is a vmbus device. If you can take the first two patches, we can submit the netvsc patch to

[PATCH 0/3] Drivers: hv: Implement VF association based on serial number

From: K. Y. Srinivasan Implement VF association based on serial number published by the host. Greg, as promised here is the patchset that would use the API for detecting if the device is a vmbus device. If you can take the first two patches, we can submit the netvsc patch to the net-next tree.

答复: [PATCH] fuse: freezing abort when use wait_event_killable{,_exclusive}().

Hi Rafael, The fuse we used is without the commit "fuse: don't mess with blocking signals" committed by Al Viro. So we find the issue SIGBUS. In the page fault, trying to read page in fuse is interrupted, which will lead to SIGBUS issue. All Android platforms, include Android N, have the

答复: [PATCH] fuse: freezing abort when use wait_event_killable{,_exclusive}().

Hi Rafael, The fuse we used is without the commit "fuse: don't mess with blocking signals" committed by Al Viro. So we find the issue SIGBUS. In the page fault, trying to read page in fuse is interrupted, which will lead to SIGBUS issue. All Android platforms, include Android N, have the

[PATCH] ASoC: Intel: Skylake: remove unused 'runtime' variable

skl_platform_open() defines and sets 'struct snd_pcm_runtime* runtime' but does not use it. Compiling with W=1 gives the following warning, fix it. sound/soc/intel/skylake/skl-pcm.c: In function ‘skl_platform_open’: sound/soc/intel/skylake/skl-pcm.c:941:26: warning: variable ‘runtime’ set but

[PATCH] ASoC: Intel: Skylake: remove unused 'runtime' variable

skl_platform_open() defines and sets 'struct snd_pcm_runtime* runtime' but does not use it. Compiling with W=1 gives the following warning, fix it. sound/soc/intel/skylake/skl-pcm.c: In function ‘skl_platform_open’: sound/soc/intel/skylake/skl-pcm.c:941:26: warning: variable ‘runtime’ set but

Re: [PATCH 1/7] vfs - merge path_is_mountpoint() and path_is_mountpoint_rcu()

On Thu, 2016-12-08 at 17:28 +1300, Eric W. Biederman wrote: > Ian Kent writes: > > > On Thu, 2016-12-08 at 10:30 +1300, Eric W. Biederman wrote: > > > Ian Kent writes: > > > > > > > On Sat, 2016-12-03 at 05:13 +, Al Viro wrote: > > > > > FWIW, I've

Re: [PATCH 1/7] vfs - merge path_is_mountpoint() and path_is_mountpoint_rcu()

On Thu, 2016-12-08 at 17:28 +1300, Eric W. Biederman wrote: > Ian Kent writes: > > > On Thu, 2016-12-08 at 10:30 +1300, Eric W. Biederman wrote: > > > Ian Kent writes: > > > > > > > On Sat, 2016-12-03 at 05:13 +, Al Viro wrote: > > > > > FWIW, I've folded that pile into

[RESEND PATCH 2/2] drm/panel: simple: Add support BOE nv101wxmn51

10.1WXGA is a color active matrix TFT LCD module using amorphous silicon TFT's as an active switching devices. It can be supported by the simple-panel driver. Signed-off-by: Caesar Wang --- drivers/gpu/drm/panel/panel-simple.c | 31 +++ 1 file

[RESEND PATCH 2/2] drm/panel: simple: Add support BOE nv101wxmn51

10.1WXGA is a color active matrix TFT LCD module using amorphous silicon TFT's as an active switching devices. It can be supported by the simple-panel driver. Signed-off-by: Caesar Wang --- drivers/gpu/drm/panel/panel-simple.c | 31 +++ 1 file changed, 31

[PATCH] ASoC: Intel: Skylake: remove unused 'out_fmt' variable

Commit 4cd9899f0d16 introduced struct skl_module_fmt* out_fmt without using it. Compiling with W=1 gives the below warning, fix it. sound/soc/intel/skylake/skl-topology.c: In function ‘skl_tplg_update_buffer_size’: sound/soc/intel/skylake/skl-topology.c:301:34: warning: variable ‘out_fmt’ set

[PATCH] ASoC: Intel: Skylake: remove unused 'out_fmt' variable

Commit 4cd9899f0d16 introduced struct skl_module_fmt* out_fmt without using it. Compiling with W=1 gives the below warning, fix it. sound/soc/intel/skylake/skl-topology.c: In function ‘skl_tplg_update_buffer_size’: sound/soc/intel/skylake/skl-topology.c:301:34: warning: variable ‘out_fmt’ set

[RESEND PATCH 1/2] dt-bindings: display: Add BOE nv101wxmn51 panel binding

The BOE 10.1" NV101WXMN51 panel is an WXGA TFT LCD panel. Signed-off-by: Caesar Wang --- .../devicetree/bindings/display/panel/boe,nv101wxmn51.txt | 7 +++ 1 file changed, 7 insertions(+) create mode 100644

[RESEND PATCH 1/2] dt-bindings: display: Add BOE nv101wxmn51 panel binding

The BOE 10.1" NV101WXMN51 panel is an WXGA TFT LCD panel. Signed-off-by: Caesar Wang --- .../devicetree/bindings/display/panel/boe,nv101wxmn51.txt | 7 +++ 1 file changed, 7 insertions(+) create mode 100644 Documentation/devicetree/bindings/display/panel/boe,nv101wxmn51.txt

Re: [PATCH] drm/panel: simple: Add support BOE nv101wxmn51

Resend the missing document. Sorry for the noise. 在 2016年12月08日 13:26, Caesar Wang 写道: 10.1WXGA is a color active matrix TFT LCD module using amorphous silicon TFT's as an active switching devices. It can be supported by the simple-panel driver. Signed-off-by: Caesar Wang

Re: [PATCH] drm/panel: simple: Add support BOE nv101wxmn51

Resend the missing document. Sorry for the noise. 在 2016年12月08日 13:26, Caesar Wang 写道: 10.1WXGA is a color active matrix TFT LCD module using amorphous silicon TFT's as an active switching devices. It can be supported by the simple-panel driver. Signed-off-by: Caesar Wang ---

Re: [PATCH] linux/types.h: enable endian checks for all sparse builds

On Thu, Dec 08, 2016 at 05:21:47AM +, Bart Van Assche wrote: > On 12/07/16 18:29, Michael S. Tsirkin wrote: > > By now, linux is mostly endian-clean. Enabling endian-ness > > checks for everyone produces about 200 new sparse warnings for me - > > less than 10% over the 2000 sparse warnings

Re: [PATCH] linux/types.h: enable endian checks for all sparse builds

On Thu, Dec 08, 2016 at 05:21:47AM +, Bart Van Assche wrote: > On 12/07/16 18:29, Michael S. Tsirkin wrote: > > By now, linux is mostly endian-clean. Enabling endian-ness > > checks for everyone produces about 200 new sparse warnings for me - > > less than 10% over the 2000 sparse warnings

Re: [RFC PATCH v3] xen/x86: Increase xen_e820_map to E820_X_MAX possible entries

On 05/12/16 18:49, Alex Thorlton wrote: > This is the third pass at my patchset to fix up our problems with > XENMEM_machine_memory_map on large systems. The only changes on this > pass were to flesh out the comment above the E820_X_MAX definition, and > to add Juergen's Reviewed-by to the second

Re: [RFC PATCH v3] xen/x86: Increase xen_e820_map to E820_X_MAX possible entries

On 05/12/16 18:49, Alex Thorlton wrote: > This is the third pass at my patchset to fix up our problems with > XENMEM_machine_memory_map on large systems. The only changes on this > pass were to flesh out the comment above the E820_X_MAX definition, and > to add Juergen's Reviewed-by to the second

[PATCH] drm/panel: simple: Add support BOE nv101wxmn51

10.1WXGA is a color active matrix TFT LCD module using amorphous silicon TFT's as an active switching devices. It can be supported by the simple-panel driver. Signed-off-by: Caesar Wang --- drivers/gpu/drm/panel/panel-simple.c | 31 +++ 1 file

[PATCH] drm/panel: simple: Add support BOE nv101wxmn51

10.1WXGA is a color active matrix TFT LCD module using amorphous silicon TFT's as an active switching devices. It can be supported by the simple-panel driver. Signed-off-by: Caesar Wang --- drivers/gpu/drm/panel/panel-simple.c | 31 +++ 1 file changed, 31

Re: [PATCH] timekeeping: Remove unused timekeeping_{get,set}_tai_offset()

On Wed, Dec 7, 2016 at 2:33 PM, Stephen Boyd wrote: > The last caller to timekeeping_set_tai_offset() was in commit > 0b5154fb9040 (timekeeping: Simplify tai updating from > do_adjtimex, 2013-03-22) and the last caller to > timekeeping_get_tai_offset() was in commit

Re: [PATCH] timekeeping: Remove unused timekeeping_{get,set}_tai_offset()

On Wed, Dec 7, 2016 at 2:33 PM, Stephen Boyd wrote: > The last caller to timekeeping_set_tai_offset() was in commit > 0b5154fb9040 (timekeeping: Simplify tai updating from > do_adjtimex, 2013-03-22) and the last caller to > timekeeping_get_tai_offset() was in commit 76f4108892d9 (hrtimer: >

Re: [PATCH] linux/types.h: enable endian checks for all sparse builds

On 12/07/16 18:29, Michael S. Tsirkin wrote: > By now, linux is mostly endian-clean. Enabling endian-ness > checks for everyone produces about 200 new sparse warnings for me - > less than 10% over the 2000 sparse warnings already there. > > Not a big deal, OTOH enabling this helps people notice >

Re: [PATCH] linux/types.h: enable endian checks for all sparse builds

On 12/07/16 18:29, Michael S. Tsirkin wrote: > By now, linux is mostly endian-clean. Enabling endian-ness > checks for everyone produces about 200 new sparse warnings for me - > less than 10% over the 2000 sparse warnings already there. > > Not a big deal, OTOH enabling this helps people notice >

Re: [PATCH RFC] user-namespaced file capabilities - now with even more magic

"Serge E. Hallyn" writes: > On Thu, Dec 08, 2016 at 05:43:09PM +1300, Eric W. Biederman wrote: >> "Serge E. Hallyn" writes: >> >> > Root in a user ns cannot be trusted to write a traditional >> > security.capability xattr. If it were allowed to do so, then

Re: [PATCH RFC] user-namespaced file capabilities - now with even more magic

"Serge E. Hallyn" writes: > On Thu, Dec 08, 2016 at 05:43:09PM +1300, Eric W. Biederman wrote: >> "Serge E. Hallyn" writes: >> >> > Root in a user ns cannot be trusted to write a traditional >> > security.capability xattr. If it were allowed to do so, then any >> > unprivileged user on the

Re: linux-next: Tree for Dec 7 (kallsyms failure)

On Thu, 8 Dec 2016 15:29:35 +1100 Stephen Rothwell wrote: > Hi all, > > On Wed, 7 Dec 2016 18:30:57 -0800 Randy Dunlap wrote: > > > > On 12/07/16 15:56, Stephen Rothwell wrote: > > > > > > On Wed, 7 Dec 2016 15:42:32 -0800 Randy Dunlap

Re: linux-next: Tree for Dec 7 (kallsyms failure)

On Thu, 8 Dec 2016 15:29:35 +1100 Stephen Rothwell wrote: > Hi all, > > On Wed, 7 Dec 2016 18:30:57 -0800 Randy Dunlap wrote: > > > > On 12/07/16 15:56, Stephen Rothwell wrote: > > > > > > On Wed, 7 Dec 2016 15:42:32 -0800 Randy Dunlap > > > wrote: > > >> > > >> I started seeing this

Re: Misalignment, MIPS, and ip_hdr(skb)->version

On Wed 2016-12-07 19:30:34 -0500, Hannes Frederic Sowa wrote: > Your custom protocol should be designed in a way you get an aligned ip > header. Most protocols of the IETF follow this mantra and it is always > possible to e.g. pad options so you end up on aligned boundaries for the > next header.

Re: Misalignment, MIPS, and ip_hdr(skb)->version

On Wed 2016-12-07 19:30:34 -0500, Hannes Frederic Sowa wrote: > Your custom protocol should be designed in a way you get an aligned ip > header. Most protocols of the IETF follow this mantra and it is always > possible to e.g. pad options so you end up on aligned boundaries for the > next header.

[PATCH v2 1/5] clk: samsung: exynos5433: Set NoC (Network On Chip) clocks as critical

The ACLK_BUS0/1/2 are used for NoC (Network on Chip). If NoC's clocks are disabled, the system halt happen. Following clock must be always enabled. - CLK_ACLK_BUS0_400 : NoC's bus clock for PERIC/PERIS/FSYS/MSCL - CLK_ACLK_BUS1_400 : NoC's bus clock for MFC/HEVC/G3D - CLK_ACLK_BUS2_400 : NoC's bus

[PATCH v2 1/5] clk: samsung: exynos5433: Set NoC (Network On Chip) clocks as critical

The ACLK_BUS0/1/2 are used for NoC (Network on Chip). If NoC's clocks are disabled, the system halt happen. Following clock must be always enabled. - CLK_ACLK_BUS0_400 : NoC's bus clock for PERIC/PERIS/FSYS/MSCL - CLK_ACLK_BUS1_400 : NoC's bus clock for MFC/HEVC/G3D - CLK_ACLK_BUS2_400 : NoC's bus

[PATCH v2 0/5] arm64: dts: Enable bus frequency scaling on Exynos5433-based TM2 board

This patches add the AMBA bus Device-tree node unsing VDD_INT to enable the bus frequency scaling on Exynos5433-based TM2 board. There are two kind of bus device with devfreq framework. - Parent bus device : Change the frequency/voltage according to bus's utilization. - Passive bus device :

[PATCH v2 4/5] arm64: dts: exynos5433: Add bus dt node using VDD_INT for Exynos5433

This patch adds the bus nodes using VDD_INT for Exynos5433 SoC. Exynos5433 has the following AMBA AXI buses to translate data between DRAM and sub-blocks. Following list specify the detailed correlation between sub-block and clock: - CLK_ACLK_G2D_{400|266} : Bus clock for G2D (2D graphic engine)

[PATCH v2 3/5] arm64: dts: exynos5433: Add PPMU dt node

This patch adds PPMU (Platform Performance Monitoring Unit) Device-tree node to measure the utilization of each IP in Exynos SoC. - PPMU_D{0|1}_CPU are used to measure the utilization of MIF (Memory Interface) block with VDD_MIF power source. - PPMU_D{0|1}_GENERAL are used to measure the

[PATCH v2 0/5] arm64: dts: Enable bus frequency scaling on Exynos5433-based TM2 board

This patches add the AMBA bus Device-tree node unsing VDD_INT to enable the bus frequency scaling on Exynos5433-based TM2 board. There are two kind of bus device with devfreq framework. - Parent bus device : Change the frequency/voltage according to bus's utilization. - Passive bus device :

[PATCH v2 4/5] arm64: dts: exynos5433: Add bus dt node using VDD_INT for Exynos5433

This patch adds the bus nodes using VDD_INT for Exynos5433 SoC. Exynos5433 has the following AMBA AXI buses to translate data between DRAM and sub-blocks. Following list specify the detailed correlation between sub-block and clock: - CLK_ACLK_G2D_{400|266} : Bus clock for G2D (2D graphic engine)

[PATCH v2 3/5] arm64: dts: exynos5433: Add PPMU dt node

This patch adds PPMU (Platform Performance Monitoring Unit) Device-tree node to measure the utilization of each IP in Exynos SoC. - PPMU_D{0|1}_CPU are used to measure the utilization of MIF (Memory Interface) block with VDD_MIF power source. - PPMU_D{0|1}_GENERAL are used to measure the

[PATCH v2 5/5] arm64: dts: exynos5433: Add support of bus frequency using VDD_INT on TM2

This patch adds the bus Device-tree nodes for INT (Internal) block to enable the bus frequency scaling. Signed-off-by: Chanwoo Choi Reviewed-by: Krzysztof Kozlowski --- arch/arm64/boot/dts/exynos/exynos5433-tm2.dts | 70 +++ 1

[PATCH v2 2/5] PM / devfreq: exynos-bus: Add the detailed correlation for Exynos5433

This patch adds the detailed corrleation between sub-blocks and VDD_INT power line for Exynos5433. VDD_INT provided the power source to INT (Internal) block. Cc: MyungJoo Ham Cc: Kyungmin Park Cc: Rob Herring Cc:

[PATCH v2 5/5] arm64: dts: exynos5433: Add support of bus frequency using VDD_INT on TM2

This patch adds the bus Device-tree nodes for INT (Internal) block to enable the bus frequency scaling. Signed-off-by: Chanwoo Choi Reviewed-by: Krzysztof Kozlowski --- arch/arm64/boot/dts/exynos/exynos5433-tm2.dts | 70 +++ 1 file changed, 70 insertions(+) diff --git

[PATCH v2 2/5] PM / devfreq: exynos-bus: Add the detailed correlation for Exynos5433

This patch adds the detailed corrleation between sub-blocks and VDD_INT power line for Exynos5433. VDD_INT provided the power source to INT (Internal) block. Cc: MyungJoo Ham Cc: Kyungmin Park Cc: Rob Herring Cc: devicet...@vger.kernel.org Signed-off-by: Chanwoo Choi ---

Re: [PATCH RFC] user-namespaced file capabilities - now with even more magic

On Thu, Dec 08, 2016 at 05:43:09PM +1300, Eric W. Biederman wrote: > "Serge E. Hallyn" writes: > > > Root in a user ns cannot be trusted to write a traditional > > security.capability xattr. If it were allowed to do so, then any > > unprivileged user on the host could map his

Re: [PATCH RFC] user-namespaced file capabilities - now with even more magic

On Thu, Dec 08, 2016 at 05:43:09PM +1300, Eric W. Biederman wrote: > "Serge E. Hallyn" writes: > > > Root in a user ns cannot be trusted to write a traditional > > security.capability xattr. If it were allowed to do so, then any > > unprivileged user on the host could map his own uid to root in

[PATCH 1/2] arm64:dt:ls1046a: Add TMU device tree support for LS1046A

Also add nodes and properties for thermal management support. Signed-off-by: Jia Hongtao --- arch/arm64/boot/dts/freescale/fsl-ls1046a.dtsi | 79 ++ 1 file changed, 79 insertions(+) diff --git a/arch/arm64/boot/dts/freescale/fsl-ls1046a.dtsi

[PATCH 1/2] arm64:dt:ls1046a: Add TMU device tree support for LS1046A

Also add nodes and properties for thermal management support. Signed-off-by: Jia Hongtao --- arch/arm64/boot/dts/freescale/fsl-ls1046a.dtsi | 79 ++ 1 file changed, 79 insertions(+) diff --git a/arch/arm64/boot/dts/freescale/fsl-ls1046a.dtsi

  1   2   3   4   5   6   7   8   9   10   >