Re: [PATCH 04/15] mm/hmm: unregister mmu_notifier when last HMM client quit v2

On 03/22/2018 05:50 PM, Jerome Glisse wrote: > On Thu, Mar 22, 2018 at 05:13:14PM -0700, John Hubbard wrote: >> On 03/22/2018 04:37 PM, Jerome Glisse wrote: >>> On Thu, Mar 22, 2018 at 03:47:16PM -0700, John Hubbard wrote: On 03/21/2018 04:41 PM, Jerome Glisse wrote: > On Wed, Mar 21,

Re: [PATCH 04/15] mm/hmm: unregister mmu_notifier when last HMM client quit v2

On 03/22/2018 05:50 PM, Jerome Glisse wrote: > On Thu, Mar 22, 2018 at 05:13:14PM -0700, John Hubbard wrote: >> On 03/22/2018 04:37 PM, Jerome Glisse wrote: >>> On Thu, Mar 22, 2018 at 03:47:16PM -0700, John Hubbard wrote: On 03/21/2018 04:41 PM, Jerome Glisse wrote: > On Wed, Mar 21,

Re: linux-next: manual merge of the drm-intel tree with Linus' tree

Hi all, On Thu, 22 Mar 2018 13:21:29 +1100 Stephen Rothwell wrote: > > Today's linux-next merge of the drm-intel tree got a conflict in: > > drivers/gpu/drm/i915/gvt/scheduler.c > > between commit: > > fa3dd623e559 ("drm/i915/gvt: keep oa config in shadow ctx") >

Re: linux-next: manual merge of the drm-intel tree with Linus' tree

Hi all, On Thu, 22 Mar 2018 13:21:29 +1100 Stephen Rothwell wrote: > > Today's linux-next merge of the drm-intel tree got a conflict in: > > drivers/gpu/drm/i915/gvt/scheduler.c > > between commit: > > fa3dd623e559 ("drm/i915/gvt: keep oa config in shadow ctx") > > from Linus' tree and

Re: [PATCH 04/15] mm/hmm: unregister mmu_notifier when last HMM client quit v2

On Thu, Mar 22, 2018 at 05:13:14PM -0700, John Hubbard wrote: > On 03/22/2018 04:37 PM, Jerome Glisse wrote: > > On Thu, Mar 22, 2018 at 03:47:16PM -0700, John Hubbard wrote: > >> On 03/21/2018 04:41 PM, Jerome Glisse wrote: > >>> On Wed, Mar 21, 2018 at 04:22:49PM -0700, John Hubbard wrote: >

Re: [PATCH 04/15] mm/hmm: unregister mmu_notifier when last HMM client quit v2

On Thu, Mar 22, 2018 at 05:13:14PM -0700, John Hubbard wrote: > On 03/22/2018 04:37 PM, Jerome Glisse wrote: > > On Thu, Mar 22, 2018 at 03:47:16PM -0700, John Hubbard wrote: > >> On 03/21/2018 04:41 PM, Jerome Glisse wrote: > >>> On Wed, Mar 21, 2018 at 04:22:49PM -0700, John Hubbard wrote: >

Re: [PATCH] USB:fix USB3 devices behind USB3 hubs not resuming at hibernate thaw

On 3/22/2018 8:03 PM, Greg KH wrote: On Wed, Mar 21, 2018 at 01:29:42PM +0800, Zhengjun Xing wrote: USB3 hubs don't support global suspend. USB3 specification 10.10, Enhanced SuperSpeed hubs only support selective suspend and resume, they do not support global suspend/resume where the hub

Re: [PATCH] USB:fix USB3 devices behind USB3 hubs not resuming at hibernate thaw

On 3/22/2018 8:03 PM, Greg KH wrote: On Wed, Mar 21, 2018 at 01:29:42PM +0800, Zhengjun Xing wrote: USB3 hubs don't support global suspend. USB3 specification 10.10, Enhanced SuperSpeed hubs only support selective suspend and resume, they do not support global suspend/resume where the hub

Re: linux-next: manual merge of the drm-misc tree with Linus' tree

Hi all, On Thu, 15 Mar 2018 14:14:25 +1100 Stephen Rothwell wrote: > > Today's linux-next merge of the drm-misc tree got a conflict in: > > sound/pci/hda/hda_intel.c > > between commits: > > 1ba8f9d30817 ("ALSA: hda: Add a power_save blacklist") > 40088dc4e1ea

Re: linux-next: manual merge of the drm-misc tree with Linus' tree

Hi all, On Thu, 15 Mar 2018 14:14:25 +1100 Stephen Rothwell wrote: > > Today's linux-next merge of the drm-misc tree got a conflict in: > > sound/pci/hda/hda_intel.c > > between commits: > > 1ba8f9d30817 ("ALSA: hda: Add a power_save blacklist") > 40088dc4e1ea ("ALSA: hda - Revert

Re: linux-next: manual merge of the drm-misc tree with Linus' tree

Hi all, On Tue, 20 Mar 2018 12:08:41 +1100 Stephen Rothwell wrote: > > Today's linux-next merge of the drm-misc tree got a conflict in: > > drivers/gpu/drm/sun4i/sun4i_tcon.h > > between commit: > > e742a17cd360 ("drm/sun4i: tcon: Reduce the scope of the LVDS error

Re: linux-next: manual merge of the drm-misc tree with Linus' tree

Hi all, On Tue, 20 Mar 2018 12:08:41 +1100 Stephen Rothwell wrote: > > Today's linux-next merge of the drm-misc tree got a conflict in: > > drivers/gpu/drm/sun4i/sun4i_tcon.h > > between commit: > > e742a17cd360 ("drm/sun4i: tcon: Reduce the scope of the LVDS error a bit") > > from

Re: [PATCH v2] x86,sched: allow topologies where NUMA nodes share an LLC

On 03/22/2018 01:49 PM, Alison Schofield wrote: > > + */ > + if (!topology_same_node(c, o) && > + (c->x86_vendor == X86_VENDOR_INTEL && > + c->x86_model == INTEL_FAM6_SKYLAKE_X)) { > + /* Use NUMA instead of coregroups for scheduling: */ > +

Re: [PATCH v2] x86,sched: allow topologies where NUMA nodes share an LLC

On 03/22/2018 01:49 PM, Alison Schofield wrote: > > + */ > + if (!topology_same_node(c, o) && > + (c->x86_vendor == X86_VENDOR_INTEL && > + c->x86_model == INTEL_FAM6_SKYLAKE_X)) { > + /* Use NUMA instead of coregroups for scheduling: */ > +

[GIT PULL] libnvdimm fixes for 4.16-rc7

Hi Linus, please pull from: git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm libnvdimm-fixes ...to receive 2 regression fixes, 2 bug fixes for older issues, 2 fixes for new functionality added this cycle that have userspace ABI concerns, and a small cleanup. These have appeared in a

[GIT PULL] libnvdimm fixes for 4.16-rc7

Hi Linus, please pull from: git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm libnvdimm-fixes ...to receive 2 regression fixes, 2 bug fixes for older issues, 2 fixes for new functionality added this cycle that have userspace ABI concerns, and a small cleanup. These have appeared in a

[PATCH] trace: instrument security and console initcall

Hi Steve,  This is the patch for security & console initcall's instrumentation Signed-off-by: Abderrahmane Benbachir Cc: Steven Rostedt Cc: Ingo Molnar Cc: Peter Zijlstra Cc:

[PATCH] trace: instrument security and console initcall

Hi Steve,  This is the patch for security & console initcall's instrumentation Signed-off-by: Abderrahmane Benbachir Cc: Steven Rostedt Cc: Ingo Molnar Cc: Peter Zijlstra Cc: linux-kernel@vger.kernel.org --- kernel/printk/printk.c | 7 ++- security/security.c| 8 +++- 2 files

Re: [RFC v2 83/83] Sysfs support.

On Thu, Mar 22, 2018 at 8:00 AM, David Sterba wrote: > On Sat, Mar 10, 2018 at 10:19:04AM -0800, Andiry Xu wrote: >> From: Andiry Xu >> >> Sysfs support allows user to get/post information of running NOVA instance. >> After mount, NOVA creates four entries

Re: [RFC v2 83/83] Sysfs support.

On Thu, Mar 22, 2018 at 8:00 AM, David Sterba wrote: > On Sat, Mar 10, 2018 at 10:19:04AM -0800, Andiry Xu wrote: >> From: Andiry Xu >> >> Sysfs support allows user to get/post information of running NOVA instance. >> After mount, NOVA creates four entries under proc directory >>

Re: [PATCH v3 3/3] pinctrl: qcom: Don't allow protected pins to be requested

On 03/22/2018 07:16 PM, Timur Tabi wrote: This needs to be ret <= max_gpios, otherwise it will fail if every GPIO is available. And it should print an error message and return an error code if ret > max_gpios. Also, you don't allocate chip->valid_mask anywhere. -- Qualcomm Datacenter

Re: [PATCH v3 3/3] pinctrl: qcom: Don't allow protected pins to be requested

On 03/22/2018 07:16 PM, Timur Tabi wrote: This needs to be ret <= max_gpios, otherwise it will fail if every GPIO is available. And it should print an error message and return an error code if ret > max_gpios. Also, you don't allocate chip->valid_mask anywhere. -- Qualcomm Datacenter

RE: [PATCH v2 0/8] Decode IA32/X64 CPER

> -Original Message- > From: Borislav Petkov > Sent: Thursday, March 1, 2018 7:00 AM > To: Ghannam, Yazen > Cc: Tony Luck ; linux-...@vger.kernel.org; linux- > ker...@vger.kernel.org; ard.biesheu...@linaro.org; x...@kernel.org >

RE: [PATCH v2 0/8] Decode IA32/X64 CPER

> -Original Message- > From: Borislav Petkov > Sent: Thursday, March 1, 2018 7:00 AM > To: Ghannam, Yazen > Cc: Tony Luck ; linux-...@vger.kernel.org; linux- > ker...@vger.kernel.org; ard.biesheu...@linaro.org; x...@kernel.org > Subject: Re: [PATCH v2 0/8] Decode IA32/X64 CPER > > On

[PATCH 3/3] Storvsc: Select channel based on available percentage of ring buffer to write

From: Long Li This is a best effort for estimating on how busy the ring buffer is for that channel, based on available buffer to write in percentage. It is still possible that at the time of actual ring buffer write, the space may not be available due to other processes may

[PATCH 3/3] Storvsc: Select channel based on available percentage of ring buffer to write

From: Long Li This is a best effort for estimating on how busy the ring buffer is for that channel, based on available buffer to write in percentage. It is still possible that at the time of actual ring buffer write, the space may not be available due to other processes may be writing at the

[PATCH 1/3] Vmbus: Add function to report available ring buffer to write in total ring size percentage

From: Long Li Netvsc has a similar function to calculate how much ring buffer in percentage is available to write. This function is useful for storvsc and other vmbus devices. Define a similar function in vmbus to be used by storvsc. Signed-off-by: Long Li

[PATCH 1/3] Vmbus: Add function to report available ring buffer to write in total ring size percentage

From: Long Li Netvsc has a similar function to calculate how much ring buffer in percentage is available to write. This function is useful for storvsc and other vmbus devices. Define a similar function in vmbus to be used by storvsc. Signed-off-by: Long Li --- drivers/hv/ring_buffer.c | 2

[PATCH 2/3] Netvsc: Use the vmbus functiton to calculate ring buffer percentage

From: Long Li In Vmbus, we have defined a function to calculate available ring buffer percentage to write. Use that function and remove duplicate netvsc code. Signed-off-by: Long Li --- drivers/net/hyperv/netvsc.c | 17 +++--

[PATCH 2/3] Netvsc: Use the vmbus functiton to calculate ring buffer percentage

From: Long Li In Vmbus, we have defined a function to calculate available ring buffer percentage to write. Use that function and remove duplicate netvsc code. Signed-off-by: Long Li --- drivers/net/hyperv/netvsc.c | 17 +++-- drivers/net/hyperv/netvsc_drv.c | 3 --- 2 files

Re: [PATCH v3 3/3] pinctrl: qcom: Don't allow protected pins to be requested

On 03/21/2018 11:58 AM, Stephen Boyd wrote: +static int msm_gpio_init_valid_mask(struct gpio_chip *chip, + struct msm_pinctrl *pctrl) +{ + int ret; + unsigned int len, i; + unsigned int max_gpios = pctrl->soc->ngpios; + + /* The number of

Re: [PATCH v3 3/3] pinctrl: qcom: Don't allow protected pins to be requested

On 03/21/2018 11:58 AM, Stephen Boyd wrote: +static int msm_gpio_init_valid_mask(struct gpio_chip *chip, + struct msm_pinctrl *pctrl) +{ + int ret; + unsigned int len, i; + unsigned int max_gpios = pctrl->soc->ngpios; + + /* The number of

Re: [PATCH 04/15] mm/hmm: unregister mmu_notifier when last HMM client quit v2

On 03/22/2018 04:37 PM, Jerome Glisse wrote: > On Thu, Mar 22, 2018 at 03:47:16PM -0700, John Hubbard wrote: >> On 03/21/2018 04:41 PM, Jerome Glisse wrote: >>> On Wed, Mar 21, 2018 at 04:22:49PM -0700, John Hubbard wrote: On 03/21/2018 11:16 AM, jgli...@redhat.com wrote: > From: Jérôme

Re: [PATCH 04/15] mm/hmm: unregister mmu_notifier when last HMM client quit v2

On 03/22/2018 04:37 PM, Jerome Glisse wrote: > On Thu, Mar 22, 2018 at 03:47:16PM -0700, John Hubbard wrote: >> On 03/21/2018 04:41 PM, Jerome Glisse wrote: >>> On Wed, Mar 21, 2018 at 04:22:49PM -0700, John Hubbard wrote: On 03/21/2018 11:16 AM, jgli...@redhat.com wrote: > From: Jérôme

[git pull] drm fixes for 4.16-rc7

Hi Linus, A bunch of fixes all over the place, nothing too serious or worrying at this stage. One uapi fix to stop multi-planar images with getfb, Sun4i error path and clock fixes udl driver mmap offset fix i915 DP MST and GPU reset fixes vmwgfx mutex and black screen fixes imx array underflow

[git pull] drm fixes for 4.16-rc7

Hi Linus, A bunch of fixes all over the place, nothing too serious or worrying at this stage. One uapi fix to stop multi-planar images with getfb, Sun4i error path and clock fixes udl driver mmap offset fix i915 DP MST and GPU reset fixes vmwgfx mutex and black screen fixes imx array underflow

Re: [PATCH] arm/arm64: smccc: Use xN for arm64 register constraints with clang

El Thu, Mar 22, 2018 at 04:19:42PM -0700 Greg Hackmann ha dit: > On 03/22/2018 03:44 PM, Matthias Kaehlcke wrote: > > El Thu, Mar 22, 2018 at 10:26:18PM + Nick Desaulniers ha dit: > > > >> Note that a patch in this form has previously been implemented by: > >> > >> Andrey Konovalov

Re: [PATCH] arm/arm64: smccc: Use xN for arm64 register constraints with clang

El Thu, Mar 22, 2018 at 04:19:42PM -0700 Greg Hackmann ha dit: > On 03/22/2018 03:44 PM, Matthias Kaehlcke wrote: > > El Thu, Mar 22, 2018 at 10:26:18PM + Nick Desaulniers ha dit: > > > >> Note that a patch in this form has previously been implemented by: > >> > >> Andrey Konovalov : > >>

Re: [PATCH v2] x86,sched: allow topologies where NUMA nodes share an LLC

On 03/22/2018 04:20 PM, Peter Zijlstra wrote: >> +/* >> + * Return value doesn't actually matter because we >> + * are throwing away coregroups for scheduling anyway. >> + * Return false to bypass topology broken bug messages >> + * and

Re: [PATCH v1 0/4] platform/x86: mlx-platform: Add bus differed and auto detection functionalities

On Tue, Feb 13, 2018 at 10:09:32PM +, Vadim Pasternak wrote: > This patchset: > - Adds define for the channels number for mux device. > - Adds differed bus functionality. > - Changes input for device create routine in mlxreg-hotplug driver. > - Adds physical bus number auto detection. > >

Re: [PATCH v2] x86,sched: allow topologies where NUMA nodes share an LLC

On 03/22/2018 04:20 PM, Peter Zijlstra wrote: >> +/* >> + * Return value doesn't actually matter because we >> + * are throwing away coregroups for scheduling anyway. >> + * Return false to bypass topology broken bug messages >> + * and

Re: [PATCH v1 0/4] platform/x86: mlx-platform: Add bus differed and auto detection functionalities

On Tue, Feb 13, 2018 at 10:09:32PM +, Vadim Pasternak wrote: > This patchset: > - Adds define for the channels number for mux device. > - Adds differed bus functionality. > - Changes input for device create routine in mlxreg-hotplug driver. > - Adds physical bus number auto detection. > >

Re: [PATCH v9 12/12] extcon: axp288: Set USB role where necessary

On 2018년 03월 20일 21:57, Heikki Krogerus wrote: > From: Hans de Goede > > The AXP288 BC1.2 charger detection / extcon code may seem like a strange > place to add code to control the USB role-switch on devices with an AXP288, > but there are 2 reasons to do this inside the

Re: [PATCH v9 12/12] extcon: axp288: Set USB role where necessary

On 2018년 03월 20일 21:57, Heikki Krogerus wrote: > From: Hans de Goede > > The AXP288 BC1.2 charger detection / extcon code may seem like a strange > place to add code to control the USB role-switch on devices with an AXP288, > but there are 2 reasons to do this inside the axp288 extcon code: > >

Re: [PATCHv5,5/5] ARM: dts: omap4-droid4: add soundcard

Hi Pavel, On Thu, Mar 22, 2018 at 09:48:05PM +0100, Pavel Machek wrote: > Hi! > > > Add sound support to Motorola Droid 4 using simple-soundcard > > and CPCAP's audio codec. This does not yet correctly represent > > the whole audio routing, since McBSP3 is also connected to > > Bluetooth and

Re: [PATCHv5,5/5] ARM: dts: omap4-droid4: add soundcard

Hi Pavel, On Thu, Mar 22, 2018 at 09:48:05PM +0100, Pavel Machek wrote: > Hi! > > > Add sound support to Motorola Droid 4 using simple-soundcard > > and CPCAP's audio codec. This does not yet correctly represent > > the whole audio routing, since McBSP3 is also connected to > > Bluetooth and

Re: [PATCH RFC] xfs, memcg: Call xfs_fs_nr_cached_objects() only in case of global reclaim

On Thu, Mar 22, 2018 at 07:52:37PM +0300, Kirill Tkhai wrote: > Here is the problem I'm solving: https://lkml.org/lkml/2018/3/21/365. Oh, finally you tell me what the problem is that you're trying to solve. I *asked this several times* and got no response. Thank you for wasting so much of my

Re: [PATCH RFC] xfs, memcg: Call xfs_fs_nr_cached_objects() only in case of global reclaim

On Thu, Mar 22, 2018 at 07:52:37PM +0300, Kirill Tkhai wrote: > Here is the problem I'm solving: https://lkml.org/lkml/2018/3/21/365. Oh, finally you tell me what the problem is that you're trying to solve. I *asked this several times* and got no response. Thank you for wasting so much of my

Re: [PATCH 04/15] mm/hmm: unregister mmu_notifier when last HMM client quit v2

On Thu, Mar 22, 2018 at 03:47:16PM -0700, John Hubbard wrote: > On 03/21/2018 04:41 PM, Jerome Glisse wrote: > > On Wed, Mar 21, 2018 at 04:22:49PM -0700, John Hubbard wrote: > >> On 03/21/2018 11:16 AM, jgli...@redhat.com wrote: > >>> From: Jérôme Glisse > >>> > >>> This code

Re: [PATCH 04/15] mm/hmm: unregister mmu_notifier when last HMM client quit v2

On Thu, Mar 22, 2018 at 03:47:16PM -0700, John Hubbard wrote: > On 03/21/2018 04:41 PM, Jerome Glisse wrote: > > On Wed, Mar 21, 2018 at 04:22:49PM -0700, John Hubbard wrote: > >> On 03/21/2018 11:16 AM, jgli...@redhat.com wrote: > >>> From: Jérôme Glisse > >>> > >>> This code was lost in

Re: [PATCH v2 05/14] platform/chrome: chromeos_laptop - stop setting suspend mode for Atmel devices

Hi Dmitry, On Tue, Mar 20, 2018 at 03:31:29PM -0700, Dmitry Torokhov wrote: > Atmel touch controller driver no longer respects suspend mode specified in > platform data, so let's stop setting it. > > Signed-off-by: Dmitry Torokhov Applied to my working branch for

Re: [PATCH v2 05/14] platform/chrome: chromeos_laptop - stop setting suspend mode for Atmel devices

Hi Dmitry, On Tue, Mar 20, 2018 at 03:31:29PM -0700, Dmitry Torokhov wrote: > Atmel touch controller driver no longer respects suspend mode specified in > platform data, so let's stop setting it. > > Signed-off-by: Dmitry Torokhov Applied to my working branch for atmel_mxt_ts +

Re: [PATCH 1/1] lz4: Implement lz4 with dynamic offset length.

Hi Maninder, Thank you for the patch! Yet something to improve: [auto build test ERROR on linus/master] [also build test ERROR on v4.16-rc6] [cannot apply to next-20180322] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https

Re: [PATCH 1/1] lz4: Implement lz4 with dynamic offset length.

Hi Maninder, Thank you for the patch! Yet something to improve: [auto build test ERROR on linus/master] [also build test ERROR on v4.16-rc6] [cannot apply to next-20180322] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https

[PATCH] drm/amd/display: don't pass large struct stream_res by value

From: Colin Ian King Passing stream_res by value is inefficient as it requires a large copy of 320 bytes. Instead, pass it by reference and also use a pointer to stream_res->tg and also stream_res->abm to clean up the code a little. Detected by CoverityScan,

[PATCH] drm/amd/display: don't pass large struct stream_res by value

From: Colin Ian King Passing stream_res by value is inefficient as it requires a large copy of 320 bytes. Instead, pass it by reference and also use a pointer to stream_res->tg and also stream_res->abm to clean up the code a little. Detected by CoverityScan, CID#1466432 ("Big parameter passed

Re: [PATCH v2] x86,sched: allow topologies where NUMA nodes share an LLC

On Thu, Mar 22, 2018 at 01:49:22PM -0700, Alison Schofield wrote: > + if (!topology_same_node(c, o) && > + (c->x86_vendor == X86_VENDOR_INTEL && > + c->x86_model == INTEL_FAM6_SKYLAKE_X)) { Maybe make life easier in the future to add more models to the list by using

Re: [PATCH v2] x86,sched: allow topologies where NUMA nodes share an LLC

On Thu, Mar 22, 2018 at 01:49:22PM -0700, Alison Schofield wrote: > + if (!topology_same_node(c, o) && > + (c->x86_vendor == X86_VENDOR_INTEL && > + c->x86_model == INTEL_FAM6_SKYLAKE_X)) { Maybe make life easier in the future to add more models to the list by using

Re: [GIT PULL] ACPI fixes for v4.16-rc7

On Fri, Mar 23, 2018 at 12:21 AM, Linus Torvalds wrote: > On Thu, Mar 22, 2018 at 4:05 PM, Rafael J. Wysocki wrote: >> >> git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \ >> acpi-4.16-rc4 > > I get > > fatal: Couldn't find

Re: [GIT PULL] ACPI fixes for v4.16-rc7

On Fri, Mar 23, 2018 at 12:21 AM, Linus Torvalds wrote: > On Thu, Mar 22, 2018 at 4:05 PM, Rafael J. Wysocki wrote: >> >> git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \ >> acpi-4.16-rc4 > > I get > > fatal: Couldn't find remote ref acpi-4.16-rc4 > > Forgot to push out? >

Business Proposal

Good day! I seek your consent to present you as the beneficiary of an unclaimed financial estate belonging to my late client. I am contacting you because you share a similar name as his. Get back to me so I give you comprehensive details if interested. Regards Albrecht.

Business Proposal

Good day! I seek your consent to present you as the beneficiary of an unclaimed financial estate belonging to my late client. I am contacting you because you share a similar name as his. Get back to me so I give you comprehensive details if interested. Regards Albrecht.

Re: [PATCH 1/2] cpufreq: scpi: add thermal dependency

On Wednesday, March 14, 2018 6:09:54 AM CET Viresh Kumar wrote: > On 13-03-18, 12:45, Arnd Bergmann wrote: > > A built-in scpi cpufreq driver cannot link against a modular > > thermal framework: > > > > drivers/cpufreq/scpi-cpufreq.o: In function `scpi_cpufreq_ready': > >

Re: [PATCH 1/2] cpufreq: scpi: add thermal dependency

On Wednesday, March 14, 2018 6:09:54 AM CET Viresh Kumar wrote: > On 13-03-18, 12:45, Arnd Bergmann wrote: > > A built-in scpi cpufreq driver cannot link against a modular > > thermal framework: > > > > drivers/cpufreq/scpi-cpufreq.o: In function `scpi_cpufreq_ready': > >

Re: [RFC PATCH] ftrace: support boot level tracing

On Tue, 20 Mar 2018 23:35:46 + Abderrahmane Benbachir wrote: > Steven Rostedt a écrit : > > > On Tue, 20 Mar 2018 14:22:56 -0400 > > Abderrahmane Benbachir wrote: > > > > Would something like this

Re: [RFC PATCH] ftrace: support boot level tracing

On Tue, 20 Mar 2018 23:35:46 + Abderrahmane Benbachir wrote: > Steven Rostedt a écrit : > > > On Tue, 20 Mar 2018 14:22:56 -0400 > > Abderrahmane Benbachir wrote: > > > > Would something like this work for you? > > Yes this is working great. I have also instrumented console and

Re: [PATCH v2] ACPI / scan: Send the change uevent with offine environmental data

On Tuesday, March 20, 2018 6:51:26 AM CET Lee, Chun-Yi wrote: > In current design of ACPI container offline, Kernel emits > KOBJ_CHANGE uevent to user space to indidate that the ejection of > the container was triggered by platform. (caa73ea15 patch) > > A pure KOBJ_CHANGE uevent is not enough

Re: [PATCH v2] ACPI / scan: Send the change uevent with offine environmental data

On Tuesday, March 20, 2018 6:51:26 AM CET Lee, Chun-Yi wrote: > In current design of ACPI container offline, Kernel emits > KOBJ_CHANGE uevent to user space to indidate that the ejection of > the container was triggered by platform. (caa73ea15 patch) > > A pure KOBJ_CHANGE uevent is not enough

Re: [PATCH v2] ACPI / PM: allow deeper wakeup power states with no _SxD nor _SxW

On Tuesday, March 20, 2018 5:07:35 AM CET Daniel Drake wrote: > acpi_dev_pm_get_state() is used to determine the range of allowable > device power states when going into S3 suspend. This is implemented > by executing the _S3D and _S3W ACPI methods. > > Linux follows the ACPI spec behaviour in

Re: [PATCH v2] ACPI / PM: allow deeper wakeup power states with no _SxD nor _SxW

On Tuesday, March 20, 2018 5:07:35 AM CET Daniel Drake wrote: > acpi_dev_pm_get_state() is used to determine the range of allowable > device power states when going into S3 suspend. This is implemented > by executing the _S3D and _S3W ACPI methods. > > Linux follows the ACPI spec behaviour in

Re: [PATCH] acpi: edit ACPI_PROCFS_POWER help text

On Saturday, March 3, 2018 1:55:54 AM CET Randy Dunlap wrote: > From: Randy Dunlap > > Fix grammar and punctuation (end sentences with a period) in the > Kconfig help text for ACPI_PROCFS_POWER. > > I was looking at this since it appears to be going away (again, > some

Re: [PATCH] acpi: edit ACPI_PROCFS_POWER help text

On Saturday, March 3, 2018 1:55:54 AM CET Randy Dunlap wrote: > From: Randy Dunlap > > Fix grammar and punctuation (end sentences with a period) in the > Kconfig help text for ACPI_PROCFS_POWER. > > I was looking at this since it appears to be going away (again, > some day) and I have a working

Re: [GIT PULL] ACPI fixes for v4.16-rc7

On Thu, Mar 22, 2018 at 4:05 PM, Rafael J. Wysocki wrote: > > git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \ > acpi-4.16-rc4 I get fatal: Couldn't find remote ref acpi-4.16-rc4 Forgot to push out? Oh. No, I see what happened. You meant "rc7".

Re: [GIT PULL] ACPI fixes for v4.16-rc7

On Thu, Mar 22, 2018 at 4:05 PM, Rafael J. Wysocki wrote: > > git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \ > acpi-4.16-rc4 I get fatal: Couldn't find remote ref acpi-4.16-rc4 Forgot to push out? Oh. No, I see what happened. You meant "rc7". Didn't your script warn

Re: [PATCH v2] x86,sched: allow topologies where NUMA nodes share an LLC

On Thu, Mar 22, 2018 at 01:49:22PM -0700, Alison Schofield wrote: > + /* > + * Some Intel CPUs enumerate an LLC that is shared by > + * multiple NUMA nodes. The LLC on these systems is > + * shared for off-package data access but private to the > + * NUMA node (half of the

Re: [PATCH v2] x86,sched: allow topologies where NUMA nodes share an LLC

On Thu, Mar 22, 2018 at 01:49:22PM -0700, Alison Schofield wrote: > + /* > + * Some Intel CPUs enumerate an LLC that is shared by > + * multiple NUMA nodes. The LLC on these systems is > + * shared for off-package data access but private to the > + * NUMA node (half of the

Re: [PATCH] arm/arm64: smccc: Use xN for arm64 register constraints with clang

On 03/22/2018 03:44 PM, Matthias Kaehlcke wrote: > El Thu, Mar 22, 2018 at 10:26:18PM + Nick Desaulniers ha dit: > >> Note that a patch in this form has previously been implemented by: >> >> Andrey Konovalov : >>

Re: [PATCH] arm/arm64: smccc: Use xN for arm64 register constraints with clang

On 03/22/2018 03:44 PM, Matthias Kaehlcke wrote: > El Thu, Mar 22, 2018 at 10:26:18PM + Nick Desaulniers ha dit: > >> Note that a patch in this form has previously been implemented by: >> >> Andrey Konovalov : >> https://gist.github.com/xairy/ee11682ea86044a45c0291c528cd936f >> >> and another

mmotm 2018-03-22-16-18 uploaded

The mm-of-the-moment snapshot 2018-03-22-16-18 has been uploaded to http://www.ozlabs.org/~akpm/mmotm/ mmotm-readme.txt says README for mm-of-the-moment: http://www.ozlabs.org/~akpm/mmotm/ This is a snapshot of my -mm patch queue. Uploaded at random hopefully more than once a week. You

mmotm 2018-03-22-16-18 uploaded

The mm-of-the-moment snapshot 2018-03-22-16-18 has been uploaded to http://www.ozlabs.org/~akpm/mmotm/ mmotm-readme.txt says README for mm-of-the-moment: http://www.ozlabs.org/~akpm/mmotm/ This is a snapshot of my -mm patch queue. Uploaded at random hopefully more than once a week. You

Re: [PATCH 2/2] trace-cmd: Change the way of getting python ldflags.

On Sun, 4 Feb 2018 11:20:14 +0800 szts...@gmail.com wrote: > From: Zamir SUN > > Prior than this patch, Makefile detects python ldflags using a hardcoded > python command. It will cause problems if we are building against > python3 in the future when ldflags for python2 and

Re: [PATCH 2/2] trace-cmd: Change the way of getting python ldflags.

On Sun, 4 Feb 2018 11:20:14 +0800 szts...@gmail.com wrote: > From: Zamir SUN > > Prior than this patch, Makefile detects python ldflags using a hardcoded > python command. It will cause problems if we are building against > python3 in the future when ldflags for python2 and python3 are >

[PATCH][next] drm/amd/pp: don't dereference hwmgr until after it is null checked

From: Colin Ian King Pointer hwmgr is dereferenced before it is null checked, hence there is a possibility of a null pointer dereference. Fix this by only dereferencing hwmgr once it is null checked. Detected by CoverityScan, CID#1466428 ("Dereference before null

[PATCH][next] drm/amd/pp: don't dereference hwmgr until after it is null checked

From: Colin Ian King Pointer hwmgr is dereferenced before it is null checked, hence there is a possibility of a null pointer dereference. Fix this by only dereferencing hwmgr once it is null checked. Detected by CoverityScan, CID#1466428 ("Dereference before null check") Fixes: 59156faf810e

Re: [PATCH 1/1] lz4: Implement lz4 with dynamic offset length.

Hi Maninder, Thank you for the patch! Yet something to improve: [auto build test ERROR on linus/master] [also build test ERROR on v4.16-rc6] [cannot apply to next-20180322] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https

Re: [PATCH 1/1] lz4: Implement lz4 with dynamic offset length.

Hi Maninder, Thank you for the patch! Yet something to improve: [auto build test ERROR on linus/master] [also build test ERROR on v4.16-rc6] [cannot apply to next-20180322] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https

Re: [PATCH v6 03/12] PKCS#7: Introduce pkcs7_get_digest()

On Fri, 2018-03-16 at 17:38 -0300, Thiago Jung Bauermann wrote: > IMA will need to access the digest of the PKCS7 message (as calculated by > the kernel) before the signature is verified, so introduce > pkcs7_get_digest() for that purpose. > > Also, modify pkcs7_digest() to detect when the digest

Re: [PATCH v6 03/12] PKCS#7: Introduce pkcs7_get_digest()

On Fri, 2018-03-16 at 17:38 -0300, Thiago Jung Bauermann wrote: > IMA will need to access the digest of the PKCS7 message (as calculated by > the kernel) before the signature is verified, so introduce > pkcs7_get_digest() for that purpose. > > Also, modify pkcs7_digest() to detect when the digest

[GIT PULL] ACPI fixes for v4.16-rc7

Hi Linus, Please pull from the tag git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \ acpi-4.16-rc4 with top-most commit 594fdbaab739f82b3a712b88beb483ca1ca250ee Merge branch 'acpi-wdat' on top of commit c698ca5278934c0ae32297a8725ced2e27585d7f Linux 4.16-rc6 to receive

[GIT PULL] ACPI fixes for v4.16-rc7

Hi Linus, Please pull from the tag git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \ acpi-4.16-rc4 with top-most commit 594fdbaab739f82b3a712b88beb483ca1ca250ee Merge branch 'acpi-wdat' on top of commit c698ca5278934c0ae32297a8725ced2e27585d7f Linux 4.16-rc6 to receive

[PATCH] kvm_config: add CONFIG_VIRTIO_MENU

Make sure that make kvmconfig enables all the virtio drivers even if it is preceded by a make allnoconfig. Signed-off-by: Lénaïc Huard --- kernel/configs/kvm_guest.config | 1 + 1 file changed, 1 insertion(+) diff --git a/kernel/configs/kvm_guest.config

[PATCH] kvm_config: add CONFIG_VIRTIO_MENU

Make sure that make kvmconfig enables all the virtio drivers even if it is preceded by a make allnoconfig. Signed-off-by: Lénaïc Huard --- kernel/configs/kvm_guest.config | 1 + 1 file changed, 1 insertion(+) diff --git a/kernel/configs/kvm_guest.config b/kernel/configs/kvm_guest.config index

Re: [PATCH v3 01/11] PCI/P2PDMA: Support peer-to-peer memory

> I've seen the response that peers directly below a Root Port could not > DMA to each other through the Root Port because of the "route to self" > issue, and I'm not disputing that. Bjorn You asked me for a reference to RTS in the PCIe specification. As luck would have it I ended up in an

Re: [PATCH v3 01/11] PCI/P2PDMA: Support peer-to-peer memory

> I've seen the response that peers directly below a Root Port could not > DMA to each other through the Root Port because of the "route to self" > issue, and I'm not disputing that. Bjorn You asked me for a reference to RTS in the PCIe specification. As luck would have it I ended up in an

Business Proposal

Good day! I seek your consent to present you as the beneficiary of an unclaimed financial estate belonging to my late client. I am contacting you because you share a similar name as his. Get back to me so I give you comprehensive details if interested. Regards Albrecht.

Business Proposal

Good day! I seek your consent to present you as the beneficiary of an unclaimed financial estate belonging to my late client. I am contacting you because you share a similar name as his. Get back to me so I give you comprehensive details if interested. Regards Albrecht.

Re: [PATCH 04/15] mm/hmm: unregister mmu_notifier when last HMM client quit v2

On 03/21/2018 04:41 PM, Jerome Glisse wrote: > On Wed, Mar 21, 2018 at 04:22:49PM -0700, John Hubbard wrote: >> On 03/21/2018 11:16 AM, jgli...@redhat.com wrote: >>> From: Jérôme Glisse >>> >>> This code was lost in translation at one point. This properly call >>>

Re: [PATCH 04/15] mm/hmm: unregister mmu_notifier when last HMM client quit v2

On 03/21/2018 04:41 PM, Jerome Glisse wrote: > On Wed, Mar 21, 2018 at 04:22:49PM -0700, John Hubbard wrote: >> On 03/21/2018 11:16 AM, jgli...@redhat.com wrote: >>> From: Jérôme Glisse >>> >>> This code was lost in translation at one point. This properly call >>>

Re: [PATCH] arm/arm64: smccc: Use xN for arm64 register constraints with clang

El Thu, Mar 22, 2018 at 10:26:18PM + Nick Desaulniers ha dit: > Note that a patch in this form has previously been implemented by: > > Andrey Konovalov : > https://gist.github.com/xairy/ee11682ea86044a45c0291c528cd936f > > and another by: > > Greg Hackmann

Re: [PATCH] arm/arm64: smccc: Use xN for arm64 register constraints with clang

El Thu, Mar 22, 2018 at 10:26:18PM + Nick Desaulniers ha dit: > Note that a patch in this form has previously been implemented by: > > Andrey Konovalov : > https://gist.github.com/xairy/ee11682ea86044a45c0291c528cd936f > > and another by: > > Greg Hackmann : >

<    1   2   3   4   5   6   7   8   9   10   >