[PATCH v4 11/11] [media] vimc: sca: Add scaler

Implement scaler and integrated with the core Signed-off-by: Helen Koike --- Changes in v4: [media] vimc: sca: Add scaler - use vimc_colorimetry_clamp - replace V4L2_COLORSPACE_SRGB by V4L2_COLORSPACE_DEFAULT in the default format struct

[PATCH v4 11/11] [media] vimc: sca: Add scaler

Implement scaler and integrated with the core Signed-off-by: Helen Koike --- Changes in v4: [media] vimc: sca: Add scaler - use vimc_colorimetry_clamp - replace V4L2_COLORSPACE_SRGB by V4L2_COLORSPACE_DEFAULT in the default format struct - use struct

[PATCH v4 06/11] [media] vimc: common: Add vimc_colorimetry_clamp

Colorimetry value will always be checked in the same way. Adding a helper macro for that Signed-off-by: Helen Koike --- Changes in v4: [media] vimc: common: Add vimc_colorimetry_clamp - this is a new patch in the series Changes in v3: None Changes in v2:

[PATCH v4 08/11] [media] vimc: cap: Support several image formats

Allow user space to change the image format as the frame size, the pixel format, colorspace, quantization, field YCbCr encoding and the transfer function Signed-off-by: Helen Koike --- Changes in v4: [media] vimc: cap: Support several image formats - add

[PATCH v4 06/11] [media] vimc: common: Add vimc_colorimetry_clamp

Colorimetry value will always be checked in the same way. Adding a helper macro for that Signed-off-by: Helen Koike --- Changes in v4: [media] vimc: common: Add vimc_colorimetry_clamp - this is a new patch in the series Changes in v3: None Changes in v2: None ---

[PATCH v4 08/11] [media] vimc: cap: Support several image formats

Allow user space to change the image format as the frame size, the pixel format, colorspace, quantization, field YCbCr encoding and the transfer function Signed-off-by: Helen Koike --- Changes in v4: [media] vimc: cap: Support several image formats - add vimc_colorimetry_clamp macro

[PATCH v4 07/11] [media] vimc: sen: Support several image formats

Allow user space to change the image format as the frame size, the media bus pixel format, colorspace, quantization, field YCbCr encoding and the transfer function Signed-off-by: Helen Koike --- Changes in v4: [media] vimc: sen: Support several image formats

[PATCH v4 07/11] [media] vimc: sen: Support several image formats

Allow user space to change the image format as the frame size, the media bus pixel format, colorspace, quantization, field YCbCr encoding and the transfer function Signed-off-by: Helen Koike --- Changes in v4: [media] vimc: sen: Support several image formats - use

[PATCH v4 09/11] [media] vimc: Subdevices as modules

Change the core structure for adding subdevices in the topology. Instead of calling the specific create function for each subdevice, inject a child platform_device with the driver's name. Each type of node in the topology (sensor, capture, debayer, scaler) will register a platform_driver with the

[PATCH v4 09/11] [media] vimc: Subdevices as modules

Change the core structure for adding subdevices in the topology. Instead of calling the specific create function for each subdevice, inject a child platform_device with the driver's name. Each type of node in the topology (sensor, capture, debayer, scaler) will register a platform_driver with the

[PATCH v4 04/11] [media] vimc: common: Add vimc_pipeline_s_stream helper

Move the vimc_cap_pipeline_s_stream from the vimc-cap.c to vimc-common.c as this core will be reused by other subdevices to activate the stream in their directly connected nodes Signed-off-by: Helen Koike --- Changes in v4: None Changes in v3: [media] vimc: Add

[PATCH v4 04/11] [media] vimc: common: Add vimc_pipeline_s_stream helper

Move the vimc_cap_pipeline_s_stream from the vimc-cap.c to vimc-common.c as this core will be reused by other subdevices to activate the stream in their directly connected nodes Signed-off-by: Helen Koike --- Changes in v4: None Changes in v3: [media] vimc: Add vimc_pipeline_s_stream in the

[PATCH v4 03/11] [media] vimc: common: Add vimc_ent_sd_* helper

As all the subdevices in the topology will be initialized in the same way, to avoid code repetition the vimc_ent_sd_{register, unregister} helper functions were created Signed-off-by: Helen Koike --- Changes in v4: None Changes in v3: [media] vimc: common: Add

[PATCH v4 02/11] [media] vimc: Move common code from the core

Remove helper functions from vimc-core and add it in vimc-common to clean up the core. Signed-off-by: Helen Koike --- Changes in v4: None Changes in v3: [media] vimc: Move common code from the core - This is a new patch in the series Changes in v2: None

[PATCH v4 02/11] [media] vimc: Move common code from the core

Remove helper functions from vimc-core and add it in vimc-common to clean up the core. Signed-off-by: Helen Koike --- Changes in v4: None Changes in v3: [media] vimc: Move common code from the core - This is a new patch in the series Changes in v2: None ---

[PATCH v4 03/11] [media] vimc: common: Add vimc_ent_sd_* helper

As all the subdevices in the topology will be initialized in the same way, to avoid code repetition the vimc_ent_sd_{register, unregister} helper functions were created Signed-off-by: Helen Koike --- Changes in v4: None Changes in v3: [media] vimc: common: Add vimc_ent_sd_* helper -

[PATCH v4 01/11] [media] vimc: sen: Integrate the tpg on the sensor

Initialize the test pattern generator on the sensor Generate a colored bar image instead of a grey one Signed-off-by: Helen Koike --- Changes in v4: None Changes in v3: [media] vimc: sen: Integrate the tpg on the sensor - Declare frame_size as a local

[PATCH v4 01/11] [media] vimc: sen: Integrate the tpg on the sensor

Initialize the test pattern generator on the sensor Generate a colored bar image instead of a grey one Signed-off-by: Helen Koike --- Changes in v4: None Changes in v3: [media] vimc: sen: Integrate the tpg on the sensor - Declare frame_size as a local variable - Set tpg frame

Re: [PATCH v2] xen/mce: don't issue error message for failed /dev/mcelog registration

On Tue, 2017-06-13 at 21:27 +0200, Juergen Gross wrote: > On 13/06/17 18:31, Joe Perches wrote: > > On Tue, 2017-06-13 at 18:13 +0200, Juergen Gross wrote: > > > On 13/06/17 17:20, Ingo Molnar wrote: > > > > * Juergen Gross wrote: > > > > > > > > > When running under Xen as dom0

Re: [PATCH v2] xen/mce: don't issue error message for failed /dev/mcelog registration

On Tue, 2017-06-13 at 21:27 +0200, Juergen Gross wrote: > On 13/06/17 18:31, Joe Perches wrote: > > On Tue, 2017-06-13 at 18:13 +0200, Juergen Gross wrote: > > > On 13/06/17 17:20, Ingo Molnar wrote: > > > > * Juergen Gross wrote: > > > > > > > > > When running under Xen as dom0 /dev/mcelog is

RE: RE: GRSecurity goes full commercial, no more free testing patches, threatens programmer trying to port. - Contemplation

Here is a song recorded in contemplation of the current GRSecurity situation (And the violation of the terms under-which the linux kernel is licensed for modification and distribution (that is: their implicit (or perhaps even explicit but by another channel other than the writing) addition of

RE: RE: GRSecurity goes full commercial, no more free testing patches, threatens programmer trying to port. - Contemplation

Here is a song recorded in contemplation of the current GRSecurity situation (And the violation of the terms under-which the linux kernel is licensed for modification and distribution (that is: their implicit (or perhaps even explicit but by another channel other than the writing) addition of

Re: [PATCH v2] xen/mce: don't issue error message for failed /dev/mcelog registration

On 13/06/17 18:31, Joe Perches wrote: > On Tue, 2017-06-13 at 18:13 +0200, Juergen Gross wrote: >> On 13/06/17 17:20, Ingo Molnar wrote: >>> * Juergen Gross wrote: >>> When running under Xen as dom0 /dev/mcelog is being registered by Xen instead of the normal mcelog

Re: [PATCH v2] xen/mce: don't issue error message for failed /dev/mcelog registration

On 13/06/17 18:31, Joe Perches wrote: > On Tue, 2017-06-13 at 18:13 +0200, Juergen Gross wrote: >> On 13/06/17 17:20, Ingo Molnar wrote: >>> * Juergen Gross wrote: >>> When running under Xen as dom0 /dev/mcelog is being registered by Xen instead of the normal mcelog driver. Avoid an

GRSecurity goes full commercial, no more free testing patches, threatens programmer trying to port.

GRSecurity goes full commercial, no more free testing patches, threatens programmer trying to port. (*1) https://lwn.net/Articles/723169/ (*2) https://www.phoronix.com/forums/forum/software/general-linux-open-source/948623-grsecurity-kernel-patches-will-no-longer-be-free-to-the-public?page=1

GRSecurity goes full commercial, no more free testing patches, threatens programmer trying to port.

GRSecurity goes full commercial, no more free testing patches, threatens programmer trying to port. (*1) https://lwn.net/Articles/723169/ (*2) https://www.phoronix.com/forums/forum/software/general-linux-open-source/948623-grsecurity-kernel-patches-will-no-longer-be-free-to-the-public?page=1

Re: [PATCH][netdev-next] net: hns: make guid hns_dsaf_acpi_dsm_guid static

On Tue, Jun 13, 2017 at 8:56 PM, David Miller wrote: > From: Colin King > Date: Tue, 13 Jun 2017 14:03:21 +0100 > >> From: Colin Ian King >> >> The guid hns_dsaf_acpi_dsm_guid does not need to be in global >> scope, so

Re: [PATCH][netdev-next] net: hns: make guid hns_dsaf_acpi_dsm_guid static

On Tue, Jun 13, 2017 at 8:56 PM, David Miller wrote: > From: Colin King > Date: Tue, 13 Jun 2017 14:03:21 +0100 > >> From: Colin Ian King >> >> The guid hns_dsaf_acpi_dsm_guid does not need to be in global >> scope, so make it static. >> >> Cleans up sparse warning: >> "symbol

Re: [Merge tag 'pci-v4.12-changes' of git] 857f864014: BUG: unable to handle kernel NULL pointer dereference at 00000000000000a8

On Tue, 13 Jun 2017, Greg Kroah-Hartman wrote: > On Tue, Jun 13, 2017 at 10:25:40AM -0600, Logan Gunthorpe wrote: > > > > On 12/06/17 10:35 PM, Greg Kroah-Hartman wrote: > > > Or better yet, just turn all char major allocations into dynamic, which > > > would be really good for test systems. I

Re: [Merge tag 'pci-v4.12-changes' of git] 857f864014: BUG: unable to handle kernel NULL pointer dereference at 00000000000000a8

On Tue, 13 Jun 2017, Greg Kroah-Hartman wrote: > On Tue, Jun 13, 2017 at 10:25:40AM -0600, Logan Gunthorpe wrote: > > > > On 12/06/17 10:35 PM, Greg Kroah-Hartman wrote: > > > Or better yet, just turn all char major allocations into dynamic, which > > > would be really good for test systems. I

RE: [Possible Phish Fraud][PATCH] storvsc: use default I/O timeout handler for FC devices

> -Original Message- > From: Bart Van Assche [mailto:bart.vanass...@sandisk.com] > Sent: Tuesday, June 13, 2017 8:38 AM > To: linux-kernel@vger.kernel.org; KY Srinivasan ; > martin.peter...@oracle.com; linux-s...@vger.kernel.org; Stephen Hemminger >

RE: [Possible Phish Fraud][PATCH] storvsc: use default I/O timeout handler for FC devices

> -Original Message- > From: Bart Van Assche [mailto:bart.vanass...@sandisk.com] > Sent: Tuesday, June 13, 2017 8:38 AM > To: linux-kernel@vger.kernel.org; KY Srinivasan ; > martin.peter...@oracle.com; linux-s...@vger.kernel.org; Stephen Hemminger > ; Long Li ; > j...@linux.vnet.ibm.com;

Re: [PATCH 03/12] coresight: Extend the PIDR mask to cover relevant bits in PIDR2

On 13 June 2017 at 11:55, Suzuki K Poulose wrote: > On 13/06/17 18:53, Mathieu Poirier wrote: >> >> On Mon, Jun 12, 2017 at 03:36:42PM +0100, Suzuki K Poulose wrote: >>> >>> As per coresight standards, PIDR2 register has the following format : >>> >>> [2-0] -

Re: [PATCH 03/12] coresight: Extend the PIDR mask to cover relevant bits in PIDR2

On 13 June 2017 at 11:55, Suzuki K Poulose wrote: > On 13/06/17 18:53, Mathieu Poirier wrote: >> >> On Mon, Jun 12, 2017 at 03:36:42PM +0100, Suzuki K Poulose wrote: >>> >>> As per coresight standards, PIDR2 register has the following format : >>> >>> [2-0] - JEP106_bits6to4 >>> [3]-

RE: [PATCH v9 5/7] ACPI: Translate the I/O range of non-MMIO devices before scanning

Hi Mika > -Original Message- > From: Mika Westerberg [mailto:mika.westerb...@linux.intel.com] > Sent: 13 June 2017 16:10 > To: Gabriele Paoloni > Cc: Lorenzo Pieralisi; raf...@kernel.org; Rafael J. Wysocki; > catalin.mari...@arm.com; will.dea...@arm.com; robh...@kernel.org; >

RE: [PATCH v9 5/7] ACPI: Translate the I/O range of non-MMIO devices before scanning

Hi Mika > -Original Message- > From: Mika Westerberg [mailto:mika.westerb...@linux.intel.com] > Sent: 13 June 2017 16:10 > To: Gabriele Paoloni > Cc: Lorenzo Pieralisi; raf...@kernel.org; Rafael J. Wysocki; > catalin.mari...@arm.com; will.dea...@arm.com; robh...@kernel.org; >

Re: [PATCH 11/11] Staging: rtl8712: ieee80211: fixed coding style issue

Greg is never going to merge your patches until you fix your numbering so you may as well do that before anything else. This patch fixes a bug in a patch which is never going to be merged so it's not needed. Google "how to send a v2 patch". regards, dan carpenter

Re: [PATCH 11/11] Staging: rtl8712: ieee80211: fixed coding style issue

Greg is never going to merge your patches until you fix your numbering so you may as well do that before anything else. This patch fixes a bug in a patch which is never going to be merged so it's not needed. Google "how to send a v2 patch". regards, dan carpenter

Re: [PATCH v4 14/16] perf tool: add show_feature_header to perf_tool

On Mon, Jun 12, 2017 at 09:29:30PM -0700, David Carrillo-Cisneros wrote: > Add show_feat_hdr to control level of printed information > of feature headers. > > Signed-off-by: David Carrillo-Cisneros > --- > tools/perf/builtin-report.c | 11 --- >

Re: [PATCH v4 14/16] perf tool: add show_feature_header to perf_tool

On Mon, Jun 12, 2017 at 09:29:30PM -0700, David Carrillo-Cisneros wrote: > Add show_feat_hdr to control level of printed information > of feature headers. > > Signed-off-by: David Carrillo-Cisneros > --- > tools/perf/builtin-report.c | 11 --- > tools/perf/builtin-script.c | 3 +++ >

Re: [PATCH 3/4] KVM: async_pf: Force a nested vmexit if the injected #PF is async_pf

2017-06-12 23:08-0700, Wanpeng Li: > From: Wanpeng Li > > Add an async_page_fault field to vcpu->arch.exception to identify an async > page fault, and constructs the expected vm-exit information fields. Force > a nested VM exit from nested_vmx_check_exception() if the

Re: [PATCH 3/4] KVM: async_pf: Force a nested vmexit if the injected #PF is async_pf

2017-06-12 23:08-0700, Wanpeng Li: > From: Wanpeng Li > > Add an async_page_fault field to vcpu->arch.exception to identify an async > page fault, and constructs the expected vm-exit information fields. Force > a nested VM exit from nested_vmx_check_exception() if the injected #PF > is async

Re: [PATCH v4 00/16] perf tool: add meta-data header support for pipe-mode

On Mon, Jun 12, 2017 at 09:29:16PM -0700, David Carrillo-Cisneros wrote: > v4: - Limit write_* functions to page_size. > - Fixed bugs spotted by Jiri. > - Add information about pipe-mode to some error messages. looks like this version breaks the normal report [jolsa@krava perf]$ ./perf

Re: [PATCH v11 3/6] virtio-balloon: VIRTIO_BALLOON_F_PAGE_CHUNKS

On Tue, Jun 13, 2017 at 10:59:07AM -0700, Dave Hansen wrote: > On 06/13/2017 10:56 AM, Michael S. Tsirkin wrote: > >> +/* The size of one page_bmap used to record inflated/deflated pages. */ > >> +#define VIRTIO_BALLOON_PAGE_BMAP_SIZE (8 * PAGE_SIZE) > > At this size, you probably want

Re: [PATCH v4 15/16] perf tools: add feature header record to pipe-mode

On Mon, Jun 12, 2017 at 09:29:31PM -0700, David Carrillo-Cisneros wrote: SNIP > > void perf_event__print_totals(void); > diff --git a/tools/perf/util/header.c b/tools/perf/util/header.c > index ddfaf157913d..6f6a54c15cb0 100644 > --- a/tools/perf/util/header.c > +++ b/tools/perf/util/header.c

Re: [PATCH v4 00/16] perf tool: add meta-data header support for pipe-mode

On Mon, Jun 12, 2017 at 09:29:16PM -0700, David Carrillo-Cisneros wrote: > v4: - Limit write_* functions to page_size. > - Fixed bugs spotted by Jiri. > - Add information about pipe-mode to some error messages. looks like this version breaks the normal report [jolsa@krava perf]$ ./perf

Re: [PATCH v11 3/6] virtio-balloon: VIRTIO_BALLOON_F_PAGE_CHUNKS

On Tue, Jun 13, 2017 at 10:59:07AM -0700, Dave Hansen wrote: > On 06/13/2017 10:56 AM, Michael S. Tsirkin wrote: > >> +/* The size of one page_bmap used to record inflated/deflated pages. */ > >> +#define VIRTIO_BALLOON_PAGE_BMAP_SIZE (8 * PAGE_SIZE) > > At this size, you probably want

Re: [PATCH v4 15/16] perf tools: add feature header record to pipe-mode

On Mon, Jun 12, 2017 at 09:29:31PM -0700, David Carrillo-Cisneros wrote: SNIP > > void perf_event__print_totals(void); > diff --git a/tools/perf/util/header.c b/tools/perf/util/header.c > index ddfaf157913d..6f6a54c15cb0 100644 > --- a/tools/perf/util/header.c > +++ b/tools/perf/util/header.c

Re: [PATCH v4 00/16] perf tool: add meta-data header support for pipe-mode

On Mon, Jun 12, 2017 at 09:29:16PM -0700, David Carrillo-Cisneros wrote: > v4: - Limit write_* functions to page_size. > - Fixed bugs spotted by Jiri. > - Add information about pipe-mode to some error messages. hum, looks like we have pipe report broken.. on arnaldo's perf/core branch:

Re: [PATCH v4 00/16] perf tool: add meta-data header support for pipe-mode

On Mon, Jun 12, 2017 at 09:29:16PM -0700, David Carrillo-Cisneros wrote: > v4: - Limit write_* functions to page_size. > - Fixed bugs spotted by Jiri. > - Add information about pipe-mode to some error messages. hum, looks like we have pipe report broken.. on arnaldo's perf/core branch:

Re: [PATCH v4 15/16] perf tools: add feature header record to pipe-mode

On Mon, Jun 12, 2017 at 09:29:31PM -0700, David Carrillo-Cisneros wrote: SNIP > + > + for_each_set_bit(feat, header->adds_features, HEADER_FEAT_BITS) { > + if (!feat_ops[feat].synthesize) { > + pr_debug("No record header feature for header :%d\n", > feat); >

Re: [PATCH v4 15/16] perf tools: add feature header record to pipe-mode

On Mon, Jun 12, 2017 at 09:29:31PM -0700, David Carrillo-Cisneros wrote: SNIP > + > + for_each_set_bit(feat, header->adds_features, HEADER_FEAT_BITS) { > + if (!feat_ops[feat].synthesize) { > + pr_debug("No record header feature for header :%d\n", > feat); >

Re: [PATCH v4 12/16] perf header: add a buffer to struct feat_fd

On Mon, Jun 12, 2017 at 09:29:28PM -0700, David Carrillo-Cisneros wrote: SNIP > /* Return: 0 if succeded, -ERR if failed. */ > int write_padded(struct feat_fd *ff, const void *bf, >size_t count, size_t count_aligned) > @@ -125,13 +151,32 @@ static int do_write_string(struct

Re: [PATCH v4 09/16] perf header: don't pass struct perf_file_section to process_##_feat

On Mon, Jun 12, 2017 at 09:29:25PM -0700, David Carrillo-Cisneros wrote: SNIP > struct cpu_cache_level *caches; > u32 cnt, i, version; > @@ -2084,8 +2073,7 @@ static int process_cache(struct perf_file_section > *section __maybe_unused, > struct feature_ops { > int

Re: [PATCH v4 12/16] perf header: add a buffer to struct feat_fd

On Mon, Jun 12, 2017 at 09:29:28PM -0700, David Carrillo-Cisneros wrote: SNIP > /* Return: 0 if succeded, -ERR if failed. */ > int write_padded(struct feat_fd *ff, const void *bf, >size_t count, size_t count_aligned) > @@ -125,13 +151,32 @@ static int do_write_string(struct

Re: [PATCH v4 09/16] perf header: don't pass struct perf_file_section to process_##_feat

On Mon, Jun 12, 2017 at 09:29:25PM -0700, David Carrillo-Cisneros wrote: SNIP > struct cpu_cache_level *caches; > u32 cnt, i, version; > @@ -2084,8 +2073,7 @@ static int process_cache(struct perf_file_section > *section __maybe_unused, > struct feature_ops { > int

Re: [PATCH RFC v3 2/4] tracing: Add support for recording tgid of tasks

On Thu, 8 Jun 2017 19:53:25 -0700 Joel Fernandes wrote: > Inorder to support recording of tgid, the following changes are made: > > * Introduce a new API (tracing_record_taskinfo) to additionally record the > tgid > along with the task's comm at the same time. The API is

Re: [PATCH RFC v3 2/4] tracing: Add support for recording tgid of tasks

On Thu, 8 Jun 2017 19:53:25 -0700 Joel Fernandes wrote: > Inorder to support recording of tgid, the following changes are made: > > * Introduce a new API (tracing_record_taskinfo) to additionally record the > tgid > along with the task's comm at the same time. The API is flexible to >

Re: [PATCH 1/9] [media] s5p-jpeg: Reset the Codec before doing a soft reset

Hi Thierry, On 06/07/2017 02:34 PM, Thierry Escande wrote: > Hi Jacek, > > On 02/06/2017 21:50, Jacek Anaszewski wrote: >> Hi Thierry, >> >> On 06/02/2017 06:02 PM, Thierry Escande wrote: >>> From: Abhilash Kesavan >>> >>> This patch resets the encoding and decoding

Re: [PATCH 1/9] [media] s5p-jpeg: Reset the Codec before doing a soft reset

Hi Thierry, On 06/07/2017 02:34 PM, Thierry Escande wrote: > Hi Jacek, > > On 02/06/2017 21:50, Jacek Anaszewski wrote: >> Hi Thierry, >> >> On 06/02/2017 06:02 PM, Thierry Escande wrote: >>> From: Abhilash Kesavan >>> >>> This patch resets the encoding and decoding register bits before doing a

Re: [PATCH] goldfish_pipe: use GFP_ATOMIC under spin lock

I meant that the patch needs Cc: sta...@vger.kernel.org. Thanks, jin On Mon, Jun 12, 2017 at 11:02 PM, Greg Kroah-Hartman wrote: > On Fri, Jun 09, 2017 at 12:15:42PM -0700, Jin Qian wrote: >> Reviewed-by: Jin Qian >> >> Can we merge this to

Re: [PATCH] goldfish_pipe: use GFP_ATOMIC under spin lock

I meant that the patch needs Cc: sta...@vger.kernel.org. Thanks, jin On Mon, Jun 12, 2017 at 11:02 PM, Greg Kroah-Hartman wrote: > On Fri, Jun 09, 2017 at 12:15:42PM -0700, Jin Qian wrote: >> Reviewed-by: Jin Qian >> >> Can we merge this to stable? > > I don't understand the question, what

Re: [PATCH] RFC: platform/x86: wmi: Fix check for method instance number

On Tue, Jun 13, 2017 at 08:04:57PM +0200, Pali Rohár wrote: > On Tuesday 13 June 2017 18:49:51 Darren Hart wrote: > > On Sat, Jun 10, 2017 at 09:15:57PM +0200, Pali Rohár wrote: > > > On Saturday 27 May 2017 13:55:34 Pali Rohár wrote: > > > > instance_count defines number of instances of data

Re: [PATCH] RFC: platform/x86: wmi: Fix check for method instance number

On Tue, Jun 13, 2017 at 08:04:57PM +0200, Pali Rohár wrote: > On Tuesday 13 June 2017 18:49:51 Darren Hart wrote: > > On Sat, Jun 10, 2017 at 09:15:57PM +0200, Pali Rohár wrote: > > > On Saturday 27 May 2017 13:55:34 Pali Rohár wrote: > > > > instance_count defines number of instances of data

Re: [PATCH v3] PCI: Workaround wrong flags completions for IDT switch

On 6/13/2017 1:00 PM, Yinghai Lu wrote: On Mon, Jun 12, 2017 at 2:48 PM, Bjorn Helgaas wrote: On Fri, Jun 09, 2017 at 04:16:17PM -0700, Yinghai Lu wrote: From: James Puthukattukaran The IDT switch incorrectly flags an ACS source

Re: [PATCH v3] PCI: Workaround wrong flags completions for IDT switch

On 6/13/2017 1:00 PM, Yinghai Lu wrote: On Mon, Jun 12, 2017 at 2:48 PM, Bjorn Helgaas wrote: On Fri, Jun 09, 2017 at 04:16:17PM -0700, Yinghai Lu wrote: From: James Puthukattukaran The IDT switch incorrectly flags an ACS source violation on a read config request to an end point device on

Re: [PATCH v2 4/4] arm64: dts: rockchip: use cs-gpios for cros_ec_spi

On Tue, Jun 13, 2017 at 10:50:44AM -0700, Brian Norris wrote: > On Tue, Jun 13, 2017 at 01:25:43PM +0800, Jeffy Chen wrote: > > The cros_ec requires CS line to be active after last message. But the CS > > would be toggled when powering off/on rockchip spi, which breaks ec xfer. > > Use GPIO CS to

Re: [PATCH v2 4/4] arm64: dts: rockchip: use cs-gpios for cros_ec_spi

On Tue, Jun 13, 2017 at 10:50:44AM -0700, Brian Norris wrote: > On Tue, Jun 13, 2017 at 01:25:43PM +0800, Jeffy Chen wrote: > > The cros_ec requires CS line to be active after last message. But the CS > > would be toggled when powering off/on rockchip spi, which breaks ec xfer. > > Use GPIO CS to

Re: [PATCH 4/4] KVM: async_pf: Let host know whether the guest support delivery async_pf as #PF vmexit

2017-06-12 23:08-0700, Wanpeng Li: > From: Wanpeng Li > > Adds another flag bit (bit 2) to MSR_KVM_ASYNC_PF_EN. If bit 2 is 1, async > page faults are delivered to L1 as #PF vmexits; if bit 2 is 0, > kvm_can_do_async_pf > returns 0 if in guest mode. > > Cc: Paolo

Re: [PATCH 4/4] KVM: async_pf: Let host know whether the guest support delivery async_pf as #PF vmexit

2017-06-12 23:08-0700, Wanpeng Li: > From: Wanpeng Li > > Adds another flag bit (bit 2) to MSR_KVM_ASYNC_PF_EN. If bit 2 is 1, async > page faults are delivered to L1 as #PF vmexits; if bit 2 is 0, > kvm_can_do_async_pf > returns 0 if in guest mode. > > Cc: Paolo Bonzini > Cc: Radim Krčmář

Re: [PATCH RFC v3 1/4] tracing: Remove unused declaration of trace_stop_cmdline_recording

On Thu, 8 Jun 2017 19:53:24 -0700 Joel Fernandes wrote: > trace_stop_cmdline_recording declaration isn't in use, remove it. OK, I just pulled this one in. No need to send it out again. -- Steve > > Cc: kernel-t...@android.com > Cc: Ingo Molnar > Cc:

Re: [PATCH RFC v3 1/4] tracing: Remove unused declaration of trace_stop_cmdline_recording

On Thu, 8 Jun 2017 19:53:24 -0700 Joel Fernandes wrote: > trace_stop_cmdline_recording declaration isn't in use, remove it. OK, I just pulled this one in. No need to send it out again. -- Steve > > Cc: kernel-t...@android.com > Cc: Ingo Molnar > Cc: Steven Rostedt > Signed-off-by: Joel

Re: [PATCH 2/2] power: supply: sbs-battery: Don't needlessly set CAPACITY_MODE

On Tue, Jun 13, 2017 at 10:53 AM, Shawn Nematbakhsh wrote: > According to the smart battery spec (1), the CAPACITY_MODE bit does not > influence the value read from RelativeStateOfCharge(), so don't bother > changing CAPACITY_MODE when doing such a read. > > (1) - Smart

Re: [PATCH 2/2] power: supply: sbs-battery: Don't needlessly set CAPACITY_MODE

On Tue, Jun 13, 2017 at 10:53 AM, Shawn Nematbakhsh wrote: > According to the smart battery spec (1), the CAPACITY_MODE bit does not > influence the value read from RelativeStateOfCharge(), so don't bother > changing CAPACITY_MODE when doing such a read. > > (1) - Smart Battery Data

Re: [PATCH] staging: android: uapi: drop definitions of removed ION_IOC_{FREE,SHARE} ioctls

On Tue, May 30, 2017 at 04:33:57PM -0700, Laura Abbott wrote: > On 05/30/2017 07:11 AM, Gleb Fotengauer-Malinovskiy wrote: > > This problem was found by strace ioctl list generator. > > > > Fixes: 15c6098cfec5 ("staging: android: ion: Remove ion_handle and > > ion_client") As this commit fixes

Re: [PATCH] staging: android: uapi: drop definitions of removed ION_IOC_{FREE,SHARE} ioctls

On Tue, May 30, 2017 at 04:33:57PM -0700, Laura Abbott wrote: > On 05/30/2017 07:11 AM, Gleb Fotengauer-Malinovskiy wrote: > > This problem was found by strace ioctl list generator. > > > > Fixes: 15c6098cfec5 ("staging: android: ion: Remove ion_handle and > > ion_client") As this commit fixes

Re: [PATCH 1/2] power: supply: sbs-battery: Prevent CAPACITY_MODE races

On Tue, Jun 13, 2017 at 10:53 AM, Shawn Nematbakhsh wrote: > A subset of smart battery commands return charge or energy depending on > the CAPACITY_MODE bit setting of BatteryMode(). In order to > unambiguously read a charge or energy value, it is necessary to ensure > that

Re: [PATCH 1/2] power: supply: sbs-battery: Prevent CAPACITY_MODE races

On Tue, Jun 13, 2017 at 10:53 AM, Shawn Nematbakhsh wrote: > A subset of smart battery commands return charge or energy depending on > the CAPACITY_MODE bit setting of BatteryMode(). In order to > unambiguously read a charge or energy value, it is necessary to ensure > that CAPACITY_MODE is set

Re: [PATCH v4] Introduce v3 namespaced file capabilities

On 06/13/2017 01:18 PM, Serge E. Hallyn wrote: Quoting Stefan Berger (stef...@linux.vnet.ibm.com): On 05/08/2017 02:11 PM, Serge E. Hallyn wrote: Root in a non-initial user ns cannot be trusted to write a traditional security.capability xattr. If it were allowed to do so, then any

Re: [PATCH v4] Introduce v3 namespaced file capabilities

On 06/13/2017 01:18 PM, Serge E. Hallyn wrote: Quoting Stefan Berger (stef...@linux.vnet.ibm.com): On 05/08/2017 02:11 PM, Serge E. Hallyn wrote: Root in a non-initial user ns cannot be trusted to write a traditional security.capability xattr. If it were allowed to do so, then any

Re: [PATCH] security: smack: smack.h - style fix

On 6/9/2017 5:28 PM, Derek Robson wrote: > Fixed checkpatch.pl warnings of "function definition argument FOO should > also have an identifier name" > Found using checkpatch > > Signed-off-by: Derek Robson Can you please update this to apply to:

Re: [PATCH] security: smack: smack.h - style fix

On 6/9/2017 5:28 PM, Derek Robson wrote: > Fixed checkpatch.pl warnings of "function definition argument FOO should > also have an identifier name" > Found using checkpatch > > Signed-off-by: Derek Robson Can you please update this to apply to:

Re: WMI and Kernel:User interface

On Tue, Jun 13, 2017 at 08:00:30PM +0200, Pali Rohár wrote: > > I just tried to show that proposed proxy has above problem and looks > like anti-pattern for linux kernel. As this should be evaluated when > going to accept or reject it. OK, I think at this point we need to follow Greg's advice

Re: WMI and Kernel:User interface

On Tue, Jun 13, 2017 at 08:00:30PM +0200, Pali Rohár wrote: > > I just tried to show that proposed proxy has above problem and looks > like anti-pattern for linux kernel. As this should be evaluated when > going to accept or reject it. OK, I think at this point we need to follow Greg's advice

Re: gadgetfs: how to wait for USB device initialization?

On Tue, Jun 13, 2017 at 6:22 PM, Tal Shorer wrote: > On Tue, Jun 13, 2017 at 7:02 PM, Tal Shorer wrote: >> On Tue, Jun 13, 2017 at 3:21 PM, Andrey Konovalov >> wrote: >>> Hi! >>> >>> I'm trying to use gadgetfs to fuzz USB

Re: gadgetfs: how to wait for USB device initialization?

On Tue, Jun 13, 2017 at 6:22 PM, Tal Shorer wrote: > On Tue, Jun 13, 2017 at 7:02 PM, Tal Shorer wrote: >> On Tue, Jun 13, 2017 at 3:21 PM, Andrey Konovalov >> wrote: >>> Hi! >>> >>> I'm trying to use gadgetfs to fuzz USB device drivers by simply >>> connecting random devices for now. >>> >>>

Re: usb/gadget: potential deadlock in gadgetfs_suspend

On Tue, Jun 13, 2017 at 7:44 PM, Alan Stern wrote: > On Tue, 13 Jun 2017, Andrey Konovalov wrote: > >> Hi Alan, >> >> Thanks for the patch! >> >> I've been testing with your patch applied and the "bad spinlock magic" >> crashes seem to be gone. However I got another

Re: usb/gadget: potential deadlock in gadgetfs_suspend

On Tue, Jun 13, 2017 at 7:44 PM, Alan Stern wrote: > On Tue, 13 Jun 2017, Andrey Konovalov wrote: > >> Hi Alan, >> >> Thanks for the patch! >> >> I've been testing with your patch applied and the "bad spinlock magic" >> crashes seem to be gone. However I got another crash (happened only >> once

[PATCH] caif: Add sockaddr length check before accessing sa_family in connect handler

Verify that the caller-provided sockaddr structure is large enough to contain the sa_family field, before accessing it in the connect() handler of the AF_CAIF socket. Since the syscall doesn't enforce a minimum size of the corresponding memory region, very short sockaddrs (zero or one byte long)

[PATCH] caif: Add sockaddr length check before accessing sa_family in connect handler

Verify that the caller-provided sockaddr structure is large enough to contain the sa_family field, before accessing it in the connect() handler of the AF_CAIF socket. Since the syscall doesn't enforce a minimum size of the corresponding memory region, very short sockaddrs (zero or one byte long)

Re: [PATCH] RFC: platform/x86: wmi: Fix check for method instance number

On Tuesday 13 June 2017 18:49:51 Darren Hart wrote: > On Sat, Jun 10, 2017 at 09:15:57PM +0200, Pali Rohár wrote: > > On Saturday 27 May 2017 13:55:34 Pali Rohár wrote: > > > instance_count defines number of instances of data block and > > > instance itself is indexed from zero, which means first

Re: [PATCH] RFC: platform/x86: wmi: Fix check for method instance number

On Tuesday 13 June 2017 18:49:51 Darren Hart wrote: > On Sat, Jun 10, 2017 at 09:15:57PM +0200, Pali Rohár wrote: > > On Saturday 27 May 2017 13:55:34 Pali Rohár wrote: > > > instance_count defines number of instances of data block and > > > instance itself is indexed from zero, which means first

Re: [PATCH] char: tmp: fix potential null pointer dereference

On Mon, Jun 12, 2017 at 05:25:44PM -0500, Gustavo A. R. Silva wrote: > Hi Jarkko, > > Please, see my comments below > > Quoting Jarkko Sakkinen : > > > On Tue, May 30, 2017 at 04:51:23PM -0500, Gustavo A. R. Silva wrote: > > > NULL check at line 147: if (chip)

Re: [PATCH] char: tmp: fix potential null pointer dereference

On Mon, Jun 12, 2017 at 05:25:44PM -0500, Gustavo A. R. Silva wrote: > Hi Jarkko, > > Please, see my comments below > > Quoting Jarkko Sakkinen : > > > On Tue, May 30, 2017 at 04:51:23PM -0500, Gustavo A. R. Silva wrote: > > > NULL check at line 147: if (chip) {, implies chip might be NULL. > >

Re: Ftrace vs perf user page fault statistics differences

On Tue, Jun 13, 2017 at 9:06 AM, Steven Rostedt wrote: > On Mon, 12 Jun 2017 22:05:05 -0400 > Will Hawkins wrote: > >> > Can you supply this program. So I can see exactly what it does? >> >> I have attached the binary to this email. I also provided the

Re: Ftrace vs perf user page fault statistics differences

On Tue, Jun 13, 2017 at 9:06 AM, Steven Rostedt wrote: > On Mon, 12 Jun 2017 22:05:05 -0400 > Will Hawkins wrote: > >> > Can you supply this program. So I can see exactly what it does? >> >> I have attached the binary to this email. I also provided the source >> so you can reproduce the

[PATCH] virtio_balloon: disable VIOMMU support

virtio balloon bypasses the DMA API entirely so does not support the VIOMMU right now. It's not clear we need that support, for now let's just make sure we don't pretend to support it. Cc: sta...@vger.kernel.org Cc: Wei Wang Fixes: 1a937693993f ("virtio: new feature to

[PATCH] virtio_balloon: disable VIOMMU support

virtio balloon bypasses the DMA API entirely so does not support the VIOMMU right now. It's not clear we need that support, for now let's just make sure we don't pretend to support it. Cc: sta...@vger.kernel.org Cc: Wei Wang Fixes: 1a937693993f ("virtio: new feature to detect IOMMU device

Re: [PATCH net-next] of_mdio: move of_mdio_parse_addr to header file

From: Jon Mason Date: Tue, 13 Jun 2017 10:56:08 -0400 > The of_mdio_parse_addr() helper function is useful to other code, but > the module dependency chain causes issues. To work around this, we can > move of_mdio_parse_addr() to be an inline function in the header file.

Re: [PATCH net-next] of_mdio: move of_mdio_parse_addr to header file

From: Jon Mason Date: Tue, 13 Jun 2017 10:56:08 -0400 > The of_mdio_parse_addr() helper function is useful to other code, but > the module dependency chain causes issues. To work around this, we can > move of_mdio_parse_addr() to be an inline function in the header file. > This gets rid of the

<    3   4   5   6   7   8   9   10   11   12   >