On Sat, Dec 9, 2017 at 7:45 AM, Greg Kroah-Hartman
wrote:
> On Sat, Dec 09, 2017 at 03:34:24AM +, Ivan Kozik wrote:
>> I saw no problems on 8 of 9 machines, but the last one had a problem
>> because it used NVIDIA drivers (387); DKMS reported:
>>
>> FATAL: modpost:
On Sat, Dec 9, 2017 at 7:45 AM, Greg Kroah-Hartman
wrote:
> On Sat, Dec 09, 2017 at 03:34:24AM +, Ivan Kozik wrote:
>> I saw no problems on 8 of 9 machines, but the last one had a problem
>> because it used NVIDIA drivers (387); DKMS reported:
>>
>> FATAL: modpost: GPL-incompatible module
> On 27. Nov 2017, at 14:09, Steve Rutherford wrote:
>
> On Mon, Nov 27, 2017 at 3:58 AM, Paolo Bonzini wrote:
>> On 26/11/2017 17:41, Filippo Sironi wrote:
>>> ... that the guest should see.
>>> Guest operating systems may check the microcode
> On 27. Nov 2017, at 14:09, Steve Rutherford wrote:
>
> On Mon, Nov 27, 2017 at 3:58 AM, Paolo Bonzini wrote:
>> On 26/11/2017 17:41, Filippo Sironi wrote:
>>> ... that the guest should see.
>>> Guest operating systems may check the microcode version to decide whether
>>> to disable certain
On Sat, Dec 09, 2017 at 03:34:24AM +, Ivan Kozik wrote:
> On Thu, Dec 7, 2017 at 1:07 PM, Greg Kroah-Hartman
> wrote:
> > This is the start of the stable review cycle for the 4.14.5 release.
> > There are 75 patches in this series, all will be posted as a response
On Sat, Dec 09, 2017 at 03:34:24AM +, Ivan Kozik wrote:
> On Thu, Dec 7, 2017 at 1:07 PM, Greg Kroah-Hartman
> wrote:
> > This is the start of the stable review cycle for the 4.14.5 release.
> > There are 75 patches in this series, all will be posted as a response
> > to this one. If anyone
> On 27. Nov 2017, at 03:58, Paolo Bonzini wrote:
>
> On 26/11/2017 17:41, Filippo Sironi wrote:
>> ... that the guest should see.
>> Guest operating systems may check the microcode version to decide whether
>> to disable certain features that are known to be buggy up to
> On 27. Nov 2017, at 03:58, Paolo Bonzini wrote:
>
> On 26/11/2017 17:41, Filippo Sironi wrote:
>> ... that the guest should see.
>> Guest operating systems may check the microcode version to decide whether
>> to disable certain features that are known to be buggy up to certain
>> microcode
On Sat, Dec 09, 2017 at 06:16:04AM +, alexander.le...@verizon.com wrote:
> On Fri, Dec 08, 2017 at 03:56:40AM +, Ben Hutchings wrote:
> >On Thu, 2017-12-07 at 14:07 +0100, Greg Kroah-Hartman wrote:
> >> 4.4-stable review patch. If anyone has any objections, please let me know.
> >>
> >>
On Sat, Dec 09, 2017 at 06:16:04AM +, alexander.le...@verizon.com wrote:
> On Fri, Dec 08, 2017 at 03:56:40AM +, Ben Hutchings wrote:
> >On Thu, 2017-12-07 at 14:07 +0100, Greg Kroah-Hartman wrote:
> >> 4.4-stable review patch. If anyone has any objections, please let me know.
> >>
> >>
> On 27. Nov 2017, at 02:40, Paolo Bonzini wrote:
>
> On 26/11/2017 17:41, Filippo Sironi wrote:
>> ... that the guest should see.
>> Guest operating systems may check the microcode version to decide whether
>> to disable certain features that are known to be buggy up to
> On 27. Nov 2017, at 02:40, Paolo Bonzini wrote:
>
> On 26/11/2017 17:41, Filippo Sironi wrote:
>> ... that the guest should see.
>> Guest operating systems may check the microcode version to decide whether
>> to disable certain features that are known to be buggy up to certain
>> microcode
On Fri, Dec 08, 2017 at 03:42:10PM +, John Garry wrote:
> On 08/12/2017 12:29, Jiri Olsa wrote:
> > On Wed, Dec 06, 2017 at 03:20:14PM +, John Garry wrote:
> > > On 06/12/2017 13:36, Jiri Olsa wrote:
> > > > On Wed, Dec 06, 2017 at 12:13:16AM +0800, John Garry wrote:
> > > > > For some
On Fri, Dec 08, 2017 at 03:42:10PM +, John Garry wrote:
> On 08/12/2017 12:29, Jiri Olsa wrote:
> > On Wed, Dec 06, 2017 at 03:20:14PM +, John Garry wrote:
> > > On 06/12/2017 13:36, Jiri Olsa wrote:
> > > > On Wed, Dec 06, 2017 at 12:13:16AM +0800, John Garry wrote:
> > > > > For some
Acked-by: Sudarsana Kalluru
-Original Message-
From: Arnd Bergmann [mailto:a...@arndb.de]
Sent: 04 December 2017 20:17
To: Gurumurthy, Anil ; Kalluru, Sudarsana
; James E.J. Bottomley
Acked-by: Sudarsana Kalluru
-Original Message-
From: Arnd Bergmann [mailto:a...@arndb.de]
Sent: 04 December 2017 20:17
To: Gurumurthy, Anil ; Kalluru, Sudarsana
; James E.J. Bottomley ;
Martin K. Petersen
Cc: Arnd Bergmann ; Hannes Reinecke ; Kees Cook
; Benjamin Poirier ; Mody,
ARM v8.4 extensions include support for new floating point
multiplication variant instructions to the AArch64 SIMD
instructions set. Let the userspace know about it via a
HWCAP bit and MRS emulation.
Cc: Suzuki K Poulose
Signed-off-by: Dongjiu Geng
ARM v8.4 extensions include support for new floating point
multiplication variant instructions to the AArch64 SIMD
instructions set. Let the userspace know about it via a
HWCAP bit and MRS emulation.
Cc: Suzuki K Poulose
Signed-off-by: Dongjiu Geng
---
My platform supports this feature, so I
On Fri, Dec 08, 2017 at 03:38:06PM +, John Garry wrote:
SNIP
> > >
> > > Hi jirka,
> > >
>
> Hi jirka,
>
> > > The linux kernel headers are not used for jevents tool. I would rather use
> > > them if possible...
> >
> > should be as easy as adding #include ;-)
> >
>
> Hi jirka,
>
>
On Fri, Dec 08, 2017 at 03:38:06PM +, John Garry wrote:
SNIP
> > >
> > > Hi jirka,
> > >
>
> Hi jirka,
>
> > > The linux kernel headers are not used for jevents tool. I would rather use
> > > them if possible...
> >
> > should be as easy as adding #include ;-)
> >
>
> Hi jirka,
>
>
If 'mtd_device_parse_register()' fails, we still return 0 which mean
success.
Return the error code instead, as done in all the other error handling
paths.
Signed-off-by: Christophe JAILLET
---
Compile tested-only
v2: call 'onenand_release()' to undo
If 'mtd_device_parse_register()' fails, we still return 0 which mean
success.
Return the error code instead, as done in all the other error handling
paths.
Signed-off-by: Christophe JAILLET
---
Compile tested-only
v2: call 'onenand_release()' to undo 'onenand_scan()'
---
Convert all error handling code in 's3c_onenand_probe()' to
resource-managed alternatives in order to simplify code.
This fixes a resource leak if 'platform_get_resource()' fails at line 872.
The 'request_irq()' at line 971 was also un-balanced. It is now
resource-managed.
Signed-off-by:
Convert all error handling code in 's3c_onenand_probe()' to
resource-managed alternatives in order to simplify code.
This fixes a resource leak if 'platform_get_resource()' fails at line 872.
The 'request_irq()' at line 971 was also un-balanced. It is now
resource-managed.
Signed-off-by:
The first patch converts 's3c_onenand_probe()' to devm_ functions.
This fixes a leak in one path (line 872).
This also free_irq which was not handled at all. (I hope I'm correct :) )
The 2nd patch is about an un-handled error code which looks spurious.
Not sure if I'm right.
While
The first patch converts 's3c_onenand_probe()' to devm_ functions.
This fixes a leak in one path (line 872).
This also free_irq which was not handled at all. (I hope I'm correct :) )
The 2nd patch is about an un-handled error code which looks spurious.
Not sure if I'm right.
While
> On 26. Nov 2017, at 17:02, Wanpeng Li wrote:
>
> 2017-11-27 0:41 GMT+08:00 Filippo Sironi :
>> ... that the guest should see.
>> Guest operating systems may check the microcode version to decide whether
>> to disable certain features that are known to be
> On 26. Nov 2017, at 17:02, Wanpeng Li wrote:
>
> 2017-11-27 0:41 GMT+08:00 Filippo Sironi :
>> ... that the guest should see.
>> Guest operating systems may check the microcode version to decide whether
>> to disable certain features that are known to be buggy up to certain
>> microcode
A semaphore is acquired before this check, so we must release it before
leaving.
Fixes: b7f0554a56f2 ("mm: fail get_vaddr_frames() for filesystem-dax mappings")
Signed-off-by: Christophe JAILLET
---
-- Untested --
The wording of the commit entry and log
A semaphore is acquired before this check, so we must release it before
leaving.
Fixes: b7f0554a56f2 ("mm: fail get_vaddr_frames() for filesystem-dax mappings")
Signed-off-by: Christophe JAILLET
---
-- Untested --
The wording of the commit entry and log description could be improved
but I
ARM v8.4 extensions include support for new floating point
multiplication variant instructions to the AArch64 SIMD
instructions set. Let the userspace know about it via a
HWCAP bit and MRS emulation.
Cc: Suzuki K Poulose
Signed-off-by: Dongjiu Geng
ARM v8.4 extensions include support for new floating point
multiplication variant instructions to the AArch64 SIMD
instructions set. Let the userspace know about it via a
HWCAP bit and MRS emulation.
Cc: Suzuki K Poulose
Signed-off-by: Dongjiu Geng
---
My platform supports this feature, so I
Yeeloong is a laptop with a MIPS Loongson 2F processor, AMD CS5536
chipset, and KB3310B controller.
This yeeloong_laptop module enables access to sensors, battery,
video camera switch, external video connector event, and some
additional buttons.
This driver was orginally from
Yeeloong is a laptop with a MIPS Loongson 2F processor, AMD CS5536
chipset, and KB3310B controller.
This yeeloong_laptop module enables access to sensors, battery,
video camera switch, external video connector event, and some
additional buttons.
This driver was orginally from
This patch just add pdev during boot to load the platform driver
Signed-off-by: Jiaxun Yang
---
arch/mips/loongson64/lemote-2f/Makefile | 2 +-
arch/mips/loongson64/lemote-2f/platform.c | 29 +
2 files changed, 30 insertions(+), 1
To operate EC from platform driver, this head file need able to be include
from anywhere. This patch just move ec_kb3310b.h to include dir and
clean up ec_kb3310b.h.
Signed-off-by: Jiaxun Yang
---
arch/mips/include/asm/mach-loongson64/ec_kb3310b.h | 170
Since lemote-2f/marchtype.c need to get cmdline from loongson.h
this patch simply copy kernel command line from arcs_cmdline
to fix that issue
Signed-off-by: Jiaxun Yang
---
arch/mips/include/asm/mach-loongson64/loongson.h | 6 ++
Add myself as a maintainer of Lemote YeeLoong Extra driver
Signed-off-by: Jiaxun Yang
---
MAINTAINERS | 6 ++
1 file changed, 6 insertions(+)
mode change 100644 => 100755 MAINTAINERS
diff --git a/MAINTAINERS b/MAINTAINERS
old mode 100644
new mode 100755
index
This patch just add pdev during boot to load the platform driver
Signed-off-by: Jiaxun Yang
---
arch/mips/loongson64/lemote-2f/Makefile | 2 +-
arch/mips/loongson64/lemote-2f/platform.c | 29 +
2 files changed, 30 insertions(+), 1 deletion(-)
create mode 100755
To operate EC from platform driver, this head file need able to be include
from anywhere. This patch just move ec_kb3310b.h to include dir and
clean up ec_kb3310b.h.
Signed-off-by: Jiaxun Yang
---
arch/mips/include/asm/mach-loongson64/ec_kb3310b.h | 170 +++
Since lemote-2f/marchtype.c need to get cmdline from loongson.h
this patch simply copy kernel command line from arcs_cmdline
to fix that issue
Signed-off-by: Jiaxun Yang
---
arch/mips/include/asm/mach-loongson64/loongson.h | 6 ++
arch/mips/loongson64/common/cmdline.c| 7 +++
Add myself as a maintainer of Lemote YeeLoong Extra driver
Signed-off-by: Jiaxun Yang
---
MAINTAINERS | 6 ++
1 file changed, 6 insertions(+)
mode change 100644 => 100755 MAINTAINERS
diff --git a/MAINTAINERS b/MAINTAINERS
old mode 100644
new mode 100755
index 1c3feffb1c1c..f576db163986
Change since v3:
Fix build error in platform.c
Change since v3:
Fix build error in platform.c
In case function skl_format_to_drm returns -EINVAL, fmt turns into a huge
number as fmt is of type u32, hence there is an out-of-bounds read when
using fmt as an index for array skl_pixel_formats at line 225:
plane->bpp = skl_pixel_formats[fmt].bpp;
Fix this by comparing the value returned by
In case function skl_format_to_drm returns -EINVAL, fmt turns into a huge
number as fmt is of type u32, hence there is an out-of-bounds read when
using fmt as an index for array skl_pixel_formats at line 225:
plane->bpp = skl_pixel_formats[fmt].bpp;
Fix this by comparing the value returned by
[Adding Laura]
On Fri, Dec 08, 2017 at 06:18:45PM -0800, Joe Perches wrote:
> On Sat, 2017-12-09 at 12:27 +1100, Tobin C. Harding wrote:
> > On Fri, Dec 08, 2017 at 01:22:37PM -0800, Joe Perches wrote:
>
> > > Outside of the documentation, what could be useful is for
> > > someone to add a tool
[Adding Laura]
On Fri, Dec 08, 2017 at 06:18:45PM -0800, Joe Perches wrote:
> On Sat, 2017-12-09 at 12:27 +1100, Tobin C. Harding wrote:
> > On Fri, Dec 08, 2017 at 01:22:37PM -0800, Joe Perches wrote:
>
> > > Outside of the documentation, what could be useful is for
> > > someone to add a tool
Use 'seq_printf(m, "...%*phN...")' instead of duplicating its
implementation.
Signed-off-by: Christophe JAILLET
---
drivers/s390/block/dasd_eckd.c | 7 ++-
1 file changed, 2 insertions(+), 5 deletions(-)
diff --git a/drivers/s390/block/dasd_eckd.c
Use 'seq_printf(m, "...%*phN...")' instead of duplicating its
implementation.
Signed-off-by: Christophe JAILLET
---
drivers/s390/block/dasd_eckd.c | 7 ++-
1 file changed, 2 insertions(+), 5 deletions(-)
diff --git a/drivers/s390/block/dasd_eckd.c b/drivers/s390/block/dasd_eckd.c
index
On Fri, Dec 08, 2017 at 03:56:40AM +, Ben Hutchings wrote:
>On Thu, 2017-12-07 at 14:07 +0100, Greg Kroah-Hartman wrote:
>> 4.4-stable review patch. If anyone has any objections, please let me know.
>>
>> --
>>
>> From: Ben Hutchings
>>
>>
>> [ Upstream
On Fri, Dec 08, 2017 at 03:56:40AM +, Ben Hutchings wrote:
>On Thu, 2017-12-07 at 14:07 +0100, Greg Kroah-Hartman wrote:
>> 4.4-stable review patch. If anyone has any objections, please let me know.
>>
>> --
>>
>> From: Ben Hutchings
>>
>>
>> [ Upstream commit
On 12/08/17 05:13, Geert Uytterhoeven wrote:
> Hi Pantelis, Rob, Frank,
>
> This patch series fixes memory corruption when applying overlays.
>
> I first noticed this when using OF configfs. After lots of failed
> debugging attempts, I bisected it to "of: overlay: add per overlay sysfs
>
On 12/08/17 05:13, Geert Uytterhoeven wrote:
> Hi Pantelis, Rob, Frank,
>
> This patch series fixes memory corruption when applying overlays.
>
> I first noticed this when using OF configfs. After lots of failed
> debugging attempts, I bisected it to "of: overlay: add per overlay sysfs
>
the result of cgroup_file_name will be used by kernfs_remove_name,
and then by kernfs_remove_by_name_ns().
If reached the max length, may have problem printed by WARN() in
kernfs_remove_by_name_ns().
Signed-off-by: Ma Shimiao
---
kernel/cgroup/cgroup.c | 2 +-
1
the result of cgroup_file_name will be used by kernfs_remove_name,
and then by kernfs_remove_by_name_ns().
If reached the max length, may have problem printed by WARN() in
kernfs_remove_by_name_ns().
Signed-off-by: Ma Shimiao
---
kernel/cgroup/cgroup.c | 2 +-
1 file changed, 1 insertion(+), 1
On 12/8/2017 5:27 PM, Wanpeng Li wrote:
2017-12-08 16:28 GMT+08:00 Tianyu Lan :
Hi Jim:
Thanks for your help.
2017-12-08 5:25 GMT+08:00 Jim Mattson :
Try disabling the module parameter, "unrestricted_guest." Make sure
that the module
On 12/8/2017 5:27 PM, Wanpeng Li wrote:
2017-12-08 16:28 GMT+08:00 Tianyu Lan :
Hi Jim:
Thanks for your help.
2017-12-08 5:25 GMT+08:00 Jim Mattson :
Try disabling the module parameter, "unrestricted_guest." Make sure
that the module parameter, "emulate_invalid_guest_state" is
On Thu, Dec 07, 2017 at 08:41:14PM +, Ben Hutchings wrote:
>On Tue, 2017-11-28 at 11:23 +0100, Greg Kroah-Hartman wrote:
>> 4.4-stable review patch. If anyone has any objections, please let me know.
>>
>> --
>>
>> From: Geert Uytterhoeven
>>
>>
>> [
On Thu, Dec 07, 2017 at 08:16:05PM +, Ben Hutchings wrote:
>On Tue, 2017-11-28 at 11:23 +0100, Greg Kroah-Hartman wrote:
>> 4.4-stable review patch. If anyone has any objections, please let me
>> know.
>>
>> --
>>
>> From: Daniel Vetter
>>
>>
>> [
On Thu, Dec 07, 2017 at 09:21:10PM +, Ben Hutchings wrote:
>On Tue, 2017-11-28 at 11:23 +0100, Greg Kroah-Hartman wrote:
>> 4.4-stable review patch. If anyone has any objections, please let me know.
>>
>> --
>>
>> From: Heiko Carstens
>>
>>
>> [
On Thu, Dec 07, 2017 at 08:41:14PM +, Ben Hutchings wrote:
>On Tue, 2017-11-28 at 11:23 +0100, Greg Kroah-Hartman wrote:
>> 4.4-stable review patch. If anyone has any objections, please let me know.
>>
>> --
>>
>> From: Geert Uytterhoeven
>>
>>
>> [ Upstream commit
On Thu, Dec 07, 2017 at 08:16:05PM +, Ben Hutchings wrote:
>On Tue, 2017-11-28 at 11:23 +0100, Greg Kroah-Hartman wrote:
>> 4.4-stable review patch. If anyone has any objections, please let me
>> know.
>>
>> --
>>
>> From: Daniel Vetter
>>
>>
>> [ Upstream commit
On Thu, Dec 07, 2017 at 09:21:10PM +, Ben Hutchings wrote:
>On Tue, 2017-11-28 at 11:23 +0100, Greg Kroah-Hartman wrote:
>> 4.4-stable review patch. If anyone has any objections, please let me know.
>>
>> --
>>
>> From: Heiko Carstens
>>
>>
>> [ Upstream commit
/linux/kernel/git/jmorris/linux-security.git
keys-for-linus
for you to fetch changes up to 4ded3bec65a07343258ed8fd9d46483f032d866f:
Merge tag 'keys-fixes-20171208' of
git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs into
keys-for-linus (2017-12-09 14:39:48 +1100
/linux/kernel/git/jmorris/linux-security.git
keys-for-linus
for you to fetch changes up to 4ded3bec65a07343258ed8fd9d46483f032d866f:
Merge tag 'keys-fixes-20171208' of
git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs into
keys-for-linus (2017-12-09 14:39:48 +1100
Hi Mark,
On Dec 9 2017 03:52, Mark Brown wrote:
The patch
ASoC: rsnd: ssi: fix race condition in rsnd_ssi_pointer_update
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
The applied patches are in v1 patchset, but we have v2
Hi Mark,
On Dec 9 2017 03:52, Mark Brown wrote:
The patch
ASoC: rsnd: ssi: fix race condition in rsnd_ssi_pointer_update
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
The applied patches are in v1 patchset, but we have v2
earlyprintk=efi,keep does not work any more with a warning
in mm/early_ioremap.c: WARN_ON(system_state != SYSTEM_BOOTING):
Boot just hangs because of the earlyprintk within earlyprintk
implementation code.
This is caused by a new introduced middle state in below commit:
commit 69a78ff226fe
earlyprintk=efi,keep does not work any more with a warning
in mm/early_ioremap.c: WARN_ON(system_state != SYSTEM_BOOTING):
Boot just hangs because of the earlyprintk within earlyprintk
implementation code.
This is caused by a new introduced middle state in below commit:
commit 69a78ff226fe
On Fri 08 Dec 09:22 PST 2017, Charles Keepax wrote:
> On Fri, Dec 08, 2017 at 03:40:49PM +0100, Linus Walleij wrote:
> > On Fri, Dec 8, 2017 at 3:29 PM, Charles Keepax
> > wrote:
> >
> > > (...) I have finally
> > > managed to get some time to look over the
On Fri 08 Dec 09:22 PST 2017, Charles Keepax wrote:
> On Fri, Dec 08, 2017 at 03:40:49PM +0100, Linus Walleij wrote:
> > On Fri, Dec 8, 2017 at 3:29 PM, Charles Keepax
> > wrote:
> >
> > > (...) I have finally
> > > managed to get some time to look over the pinctrl-single stuff.
> > >
> > >
Hello,
I'm Mr. Hazim, A banker working in a bank in my country; there is a certain
deceased customer of my bank who left behind her fund.
I seek your partnership in receiving this fund. If interested, reply
immediately for detailed information.
My sincere regards, Mr. Hazim Issa.
Hello,
I'm Mr. Hazim, A banker working in a bank in my country; there is a certain
deceased customer of my bank who left behind her fund.
I seek your partnership in receiving this fund. If interested, reply
immediately for detailed information.
My sincere regards, Mr. Hazim Issa.
>> On Dec 8, 2017, at 6:34 PM, Mario Limonciello
>> wrote:
>>
>> It's possible for the same GUID to show up on as system twice.
>> This means using solely the GUID for identify the file will not
>> be sufficient.
>
>Isn't the file already in a per-bus directory?
Yep,
>> On Dec 8, 2017, at 6:34 PM, Mario Limonciello
>> wrote:
>>
>> It's possible for the same GUID to show up on as system twice.
>> This means using solely the GUID for identify the file will not
>> be sufficient.
>
>Isn't the file already in a per-bus directory?
Yep, but the symlink created in
On Thu, Dec 7, 2017 at 1:07 PM, Greg Kroah-Hartman
wrote:
> This is the start of the stable review cycle for the 4.14.5 release.
> There are 75 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied,
On Thu, Dec 7, 2017 at 1:07 PM, Greg Kroah-Hartman
wrote:
> This is the start of the stable review cycle for the 4.14.5 release.
> There are 75 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
>
On Fri, Dec 08, 2017 at 09:27:37AM +0100, Michal Hocko wrote:
> On Fri 08-12-17 12:42:55, changbin...@intel.com wrote:
> > From: Changbin Du
> >
> > This patch introduced 4 new interfaces to allocate a prepared transparent
> > huge page. These interfaces merge distributed
On Fri, Dec 08, 2017 at 09:27:37AM +0100, Michal Hocko wrote:
> On Fri 08-12-17 12:42:55, changbin...@intel.com wrote:
> > From: Changbin Du
> >
> > This patch introduced 4 new interfaces to allocate a prepared transparent
> > huge page. These interfaces merge distributed two-step allocation as
On Fri, Dec 8, 2017 at 1:02 PM, David Rientjes wrote:
> On Thu, 7 Dec 2017, Suren Baghdasaryan wrote:
>
>> Slab shrinkers can be quite time consuming and when signal
>> is pending they can delay handling of the signal. If fatal
>> signal is pending there is no point in
On Fri, Dec 8, 2017 at 1:02 PM, David Rientjes wrote:
> On Thu, 7 Dec 2017, Suren Baghdasaryan wrote:
>
>> Slab shrinkers can be quite time consuming and when signal
>> is pending they can delay handling of the signal. If fatal
>> signal is pending there is no point in shrinking that process
>>
From: Andrew Waterman
RISC-V systems perform TLB shootdows via the SBI, which currently
performs an IPI to each of the remote harts which then performs a local
TLB flush. This process is a bit on the slow side, but we can at least
speed it up for some common cases by
From: Andrew Waterman
RISC-V systems perform TLB shootdows via the SBI, which currently
performs an IPI to each of the remote harts which then performs a local
TLB flush. This process is a bit on the slow side, but we can at least
speed it up for some common cases by restricting the set of
--Andy
> On Dec 8, 2017, at 6:34 PM, Mario Limonciello
> wrote:
>
> It's possible for the same GUID to show up on as system twice.
> This means using solely the GUID for identify the file will not
> be sufficient.
Isn't the file already in a per-bus directory?
--Andy
> On Dec 8, 2017, at 6:34 PM, Mario Limonciello
> wrote:
>
> It's possible for the same GUID to show up on as system twice.
> This means using solely the GUID for identify the file will not
> be sufficient.
Isn't the file already in a per-bus directory?
In: commit d1f9e4970742 ("ACPI: WMI: Survive BIOS with duplicate GUIDs")
parsing two of the same GUID was prevented in the WMI bus driver.
At the time no one understood why GUID 05901221-D566-11D1-B2F0-00A0C9062910
was being duplicated. It's now known that GUID is used for the binary
MOF file of
In: commit d1f9e4970742 ("ACPI: WMI: Survive BIOS with duplicate GUIDs")
parsing two of the same GUID was prevented in the WMI bus driver.
At the time no one understood why GUID 05901221-D566-11D1-B2F0-00A0C9062910
was being duplicated. It's now known that GUID is used for the binary
MOF file of
It's possible for the same GUID to show up on as system twice.
This means using solely the GUID for identify the file will not
be sufficient.
Signed-off-by: Mario Limonciello
---
drivers/platform/x86/wmi.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff
I recently discovered that multiple instances of the WMI BMOF
GUID are present on some machines with more advanced WMI implementations.
Only the first found instance is parsed today with the rest ignored.
The rest of the instances should be readable by the wmi-bmof driver
(and userspace) to
It's possible for the same GUID to show up on as system twice.
This means using solely the GUID for identify the file will not
be sufficient.
Signed-off-by: Mario Limonciello
---
drivers/platform/x86/wmi.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git
I recently discovered that multiple instances of the WMI BMOF
GUID are present on some machines with more advanced WMI implementations.
Only the first found instance is parsed today with the rest ignored.
The rest of the instances should be readable by the wmi-bmof driver
(and userspace) to
On Sat, 2017-12-09 at 12:27 +1100, Tobin C. Harding wrote:
> On Fri, Dec 08, 2017 at 01:22:37PM -0800, Joe Perches wrote:
> > Outside of the documentation, what could be useful is for
> > someone to add a tool to verify %p extension to
> > the typeof address actually passed as an argument.
>
>
On Sat, 2017-12-09 at 12:27 +1100, Tobin C. Harding wrote:
> On Fri, Dec 08, 2017 at 01:22:37PM -0800, Joe Perches wrote:
> > Outside of the documentation, what could be useful is for
> > someone to add a tool to verify %p extension to
> > the typeof address actually passed as an argument.
>
>
This makes davinci_clk_reset() static. It is not used anywhere else.
Signed-off-by: David Lechner
---
arch/arm/mach-davinci/clock.c | 3 +--
arch/arm/mach-davinci/clock.h | 1 -
2 files changed, 1 insertion(+), 3 deletions(-)
diff --git a/arch/arm/mach-davinci/clock.c
This makes davinci_clk_reset() static. It is not used anywhere else.
Signed-off-by: David Lechner
---
arch/arm/mach-davinci/clock.c | 3 +--
arch/arm/mach-davinci/clock.h | 1 -
2 files changed, 1 insertion(+), 3 deletions(-)
diff --git a/arch/arm/mach-davinci/clock.c
This moves the call of davinci_clk_init() from map_io to init_time for all
boards.
This is the proper place to init clocks. This is also done in preparation
for moving to the common clock framework.
Signed-off-by: David Lechner
---
arch/arm/mach-davinci/board-da830-evm.c
This converts the clocks in mach-davinci to the common clock framework.
Most of the patch just involves renaming struct clk to struct davinci_clk.
There is also a struct clk_hw added to provide the bridge between the
existing clock implementation and the common clock framework.
The
This moves the call of davinci_clk_init() from map_io to init_time for all
boards.
This is the proper place to init clocks. This is also done in preparation
for moving to the common clock framework.
Signed-off-by: David Lechner
---
arch/arm/mach-davinci/board-da830-evm.c | 2 +-
This converts the clocks in mach-davinci to the common clock framework.
Most of the patch just involves renaming struct clk to struct davinci_clk.
There is also a struct clk_hw added to provide the bridge between the
existing clock implementation and the common clock framework.
The
1 - 100 of 1870 matches
Mail list logo