Re: [PATCH] HID: redragon: fix num lock and caps lock LEDs

5455dd906d. I have fixed that, added Fixes: tag, and applied. -- Jiri Kosina SUSE Labs

Re: [PATCH] Patch enabling Fn function keys for Laptop Asus G730 (keyboard 0x1869)

; AsusGL703-Keyboard-Fn-keys.patch Neither does any of this. What is OTOH missing is your signoff. Could you please fix these up and resubmit (ideally with Subject: line also tailored to fit the subsystem customs, IOW something like "HID: asus: add support for "). Thanks, -- Jiri Kosina SUSE Labs

Re: [PATCH] Patch enabling Fn function keys for Laptop Asus G730 (keyboard 0x1869)

; AsusGL703-Keyboard-Fn-keys.patch Neither does any of this. What is OTOH missing is your signoff. Could you please fix these up and resubmit (ideally with Subject: line also tailored to fit the subsystem customs, IOW something like "HID: asus: add support for "). Thanks, -- Jiri Kosina SUSE Labs

Re: [PATCH v2] HID: hid-ntrig: add error handling for sysfs_create_group

: > - Remove goto statement. Applied, thanks. -- Jiri Kosina SUSE Labs

Re: [PATCH v2] HID: hid-ntrig: add error handling for sysfs_create_group

: > - Remove goto statement. Applied, thanks. -- Jiri Kosina SUSE Labs

Re: [PATCH v3 0/2] Add another regulator to i2c-hid

Applied both to for-4.19/i2c-hid. Thanks, -- Jiri Kosina SUSE Labs

Re: [PATCH v3 0/2] Add another regulator to i2c-hid

Applied both to for-4.19/i2c-hid. Thanks, -- Jiri Kosina SUSE Labs

[tip:x86/pti] x86/pti: Don't report XenPV as vulnerable

Commit-ID: 6cb2b08ff92460290979de4be91363e5d1b6cec1 Gitweb: https://git.kernel.org/tip/6cb2b08ff92460290979de4be91363e5d1b6cec1 Author: Jiri Kosina AuthorDate: Mon, 18 Jun 2018 09:59:54 +0200 Committer: Ingo Molnar CommitDate: Thu, 21 Jun 2018 14:14:52 +0200 x86/pti: Don't report

[tip:x86/pti] x86/pti: Don't report XenPV as vulnerable

Commit-ID: 6cb2b08ff92460290979de4be91363e5d1b6cec1 Gitweb: https://git.kernel.org/tip/6cb2b08ff92460290979de4be91363e5d1b6cec1 Author: Jiri Kosina AuthorDate: Mon, 18 Jun 2018 09:59:54 +0200 Committer: Ingo Molnar CommitDate: Thu, 21 Jun 2018 14:14:52 +0200 x86/pti: Don't report

Re: [git pull] Please pull powerpc.git next branch

> them. > > I didn't send this. It's an ancient (8 years old) email... I have no > idea how it got resent while I was asleep... I got a few mails from 2010 this morning as well. From the headers it looks like Mauro (CCed) re-bounced them for some reason. -- Jiri Kosina SUSE Labs

Re: [git pull] Please pull powerpc.git next branch

> them. > > I didn't send this. It's an ancient (8 years old) email... I have no > idea how it got resent while I was asleep... I got a few mails from 2010 this morning as well. From the headers it looks like Mauro (CCed) re-bounced them for some reason. -- Jiri Kosina SUSE Labs

Re: [GIT PULL] HID fixes

ten from scratch. It's not really a firmware / code, it's just a description of the data in the reports, so that HID parser can interpret it properly. -- Jiri Kosina SUSE Labs

Re: [GIT PULL] HID fixes

ten from scratch. It's not really a firmware / code, it's just a description of the data in the reports, so that HID parser can interpret it properly. -- Jiri Kosina SUSE Labs

[GIT PULL v2] HID fixes

changed, 23 insertions(+), 20 deletions(-) -- Jiri Kosina SUSE Labs

[GIT PULL v2] HID fixes

changed, 23 insertions(+), 20 deletions(-) -- Jiri Kosina SUSE Labs

Re: [GIT PULL] HID fixes

uld go in). The plan eventually is to offload all this crazy rdesc replacing to userspace, but that is still WIP. Thanks, -- Jiri Kosina SUSE Labs

Re: [GIT PULL] HID fixes

uld go in). The plan eventually is to offload all this crazy rdesc replacing to userspace, but that is still WIP. Thanks, -- Jiri Kosina SUSE Labs

[GIT PULL] HID fixes

-hid.h -- Jiri Kosina SUSE Labs

[GIT PULL] HID fixes

-hid.h -- Jiri Kosina SUSE Labs

[tip:x86/pti] x86/pti: Don't report XenPV as vulnerable

Commit-ID: 66aa6b5cbc359331fc054e96bb49e9502bc0b1d9 Gitweb: https://git.kernel.org/tip/66aa6b5cbc359331fc054e96bb49e9502bc0b1d9 Author: Jiri Kosina AuthorDate: Mon, 18 Jun 2018 09:59:54 +0200 Committer: Thomas Gleixner CommitDate: Tue, 19 Jun 2018 09:58:22 +0200 x86/pti: Don't report

[tip:x86/pti] x86/pti: Don't report XenPV as vulnerable

Commit-ID: 66aa6b5cbc359331fc054e96bb49e9502bc0b1d9 Gitweb: https://git.kernel.org/tip/66aa6b5cbc359331fc054e96bb49e9502bc0b1d9 Author: Jiri Kosina AuthorDate: Mon, 18 Jun 2018 09:59:54 +0200 Committer: Thomas Gleixner CommitDate: Tue, 19 Jun 2018 09:58:22 +0200 x86/pti: Don't report

[PATCH v2] x86/pti: don't report XenPV as vulnerable

From: Jiri Kosina Xen PV domain kernel is not by design affected by meltdown as it's enforcing split CR3 itself. Let's not report such systems as "Vulnerable" in sysfs (we're also already forcing PTI to off in X86_HYPER_XEN_PV cases); the security of the system ultimately depends o

[PATCH v2] x86/pti: don't report XenPV as vulnerable

From: Jiri Kosina Xen PV domain kernel is not by design affected by meltdown as it's enforcing split CR3 itself. Let's not report such systems as "Vulnerable" in sysfs (we're also already forcing PTI to off in X86_HYPER_XEN_PV cases); the security of the system ultimately depends o

Re: [PATCH] x86/pti: don't report XenPV as vulnerable

return sprintf(buf, "Unknown (XEN PV detected, hypervisor mitigation required\n"); perhaps? Thanks, -- Jiri Kosina SUSE Labs

Re: [PATCH] x86/pti: don't report XenPV as vulnerable

return sprintf(buf, "Unknown (XEN PV detected, hypervisor mitigation required\n"); perhaps? Thanks, -- Jiri Kosina SUSE Labs

Re: [PATCH] x86/pti: don't report XenPV as vulnerable

what you meant by this in your first reply: "This is wrong for [ ... ] for 64-bit, too, in case the mitigation is disabled at hypervisor level." -- Jiri Kosina SUSE Labs

Re: [PATCH] x86/pti: don't report XenPV as vulnerable

what you meant by this in your first reply: "This is wrong for [ ... ] for 64-bit, too, in case the mitigation is disabled at hypervisor level." -- Jiri Kosina SUSE Labs

Re: [PATCH] x86/pti: don't report XenPV as vulnerable

> No, it isn't. PTI for 32-bit kernels isn't paravirtualized, so it has to > be disabled. I was talking about this "mitigation disabled at Xen hypervisor level for 64-bit" situation though. -- Jiri Kosina SUSE Labs

Re: [PATCH] x86/pti: don't report XenPV as vulnerable

> No, it isn't. PTI for 32-bit kernels isn't paravirtualized, so it has to > be disabled. I was talking about this "mitigation disabled at Xen hypervisor level for 64-bit" situation though. -- Jiri Kosina SUSE Labs

Re: [PATCH] x86/pti: don't report XenPV as vulnerable

64 Fair enough. > and the returned string should be e.g. "Mitigation: XEN". Well, perhaps; it'd confuse all the scripts that are checking whether system is fully secured or not by parsing sysfs files ... but that's mostly their problem. Thanks, -- Jiri Kosina SUSE Labs

Re: [PATCH] x86/pti: don't report XenPV as vulnerable

64 Fair enough. > and the returned string should be e.g. "Mitigation: XEN". Well, perhaps; it'd confuse all the scripts that are checking whether system is fully secured or not by parsing sysfs files ... but that's mostly their problem. Thanks, -- Jiri Kosina SUSE Labs

[PATCH] x86/pti: don't report XenPV as vulnerable

From: Jiri Kosina Xen PV domain is not by design affected by meltdown as it's enforcing split CR3 itself. Let's not report such systems as "Vulnerable" in sysfs (we're also already forcing PTI to off in X86_HYPER_XEN_PV cases) Reported-and-tested-by: Mike Latimer Signed-off-by: J

[PATCH] x86/pti: don't report XenPV as vulnerable

From: Jiri Kosina Xen PV domain is not by design affected by meltdown as it's enforcing split CR3 itself. Let's not report such systems as "Vulnerable" in sysfs (we're also already forcing PTI to off in X86_HYPER_XEN_PV cases) Reported-and-tested-by: Mike Latimer Signed-off-by: J

Re: [PATCH] hid: intel_ish-hid: ipc: register more pm callbacks to support hibernation

e used, so mark them as __maybe_unused to > clarify that this is the intended behavior, and remove #ifdefs for power > management. > > Cc: sta...@vger.kernel.org > Signed-off-by: Even Xu > Acked-by: Srinivas Pandruvada Applied to hid.git#for-4.18/upstream-fixes. Thanks, -- Jiri Kosina SUSE Labs

Re: [PATCH] hid: intel_ish-hid: ipc: register more pm callbacks to support hibernation

e used, so mark them as __maybe_unused to > clarify that this is the intended behavior, and remove #ifdefs for power > management. > > Cc: sta...@vger.kernel.org > Signed-off-by: Even Xu > Acked-by: Srinivas Pandruvada Applied to hid.git#for-4.18/upstream-fixes. Thanks, -- Jiri Kosina SUSE Labs

Re: [PATCH] hid: intel_ish-hid: ipc: register more pm callbacks to support hibernation

r, and > remove #ifdefs for power management. This describes details the patch does on code level, but what are the user observable effects? Hibernation resume doesn't fail any more? Hibernation is possible (and wasn't before)? Did kernel crash while trying to hibernate and this is the fix? Or

Re: [PATCH] hid: intel_ish-hid: ipc: register more pm callbacks to support hibernation

r, and > remove #ifdefs for power management. This describes details the patch does on code level, but what are the user observable effects? Hibernation resume doesn't fail any more? Hibernation is possible (and wasn't before)? Did kernel crash while trying to hibernate and this is the fix? Or

Re: [PATCH] HID: hid-ntrig: add error handling for sysfs_create_group

eally necessarily to bail out completely here and render the device dysfunctional? Issuing a warning about sysfs knobs being unavailable might be more appropriate. Thanks, -- Jiri Kosina SUSE Labs

Re: [PATCH] HID: hid-ntrig: add error handling for sysfs_create_group

eally necessarily to bail out completely here and render the device dysfunctional? Issuing a warning about sysfs knobs being unavailable might be more appropriate. Thanks, -- Jiri Kosina SUSE Labs

Re: [PATCH] HID: google: Add support for whiskers

On Fri, 8 Jun 2018, Nicolas Boichat wrote: > Another device in the hammer class, with USB id 0x5030. > > Signed-off-by: Nicolas Boichat Applied, thanks. -- Jiri Kosina SUSE Labs

Re: [PATCH] HID: google: Add support for whiskers

On Fri, 8 Jun 2018, Nicolas Boichat wrote: > Another device in the hammer class, with USB id 0x5030. > > Signed-off-by: Nicolas Boichat Applied, thanks. -- Jiri Kosina SUSE Labs

[PATCH] MAINTAINERS: Acpi4asus-user is moderated for non-subscribers

Make that clear in the MAINTAINERS file. Signed-off-by: Jiri Kosina --- MAINTAINERS | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/MAINTAINERS b/MAINTAINERS index 2c7069037a15..a297a2bf8100 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -2286,7 +2286,7 @@ F:drivers

[PATCH] MAINTAINERS: Acpi4asus-user is moderated for non-subscribers

Make that clear in the MAINTAINERS file. Signed-off-by: Jiri Kosina --- MAINTAINERS | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/MAINTAINERS b/MAINTAINERS index 2c7069037a15..a297a2bf8100 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -2286,7 +2286,7 @@ F:drivers

Re: [PATCH] HID: steam: use hid_device.driver_data instead of hid_set_drvdata()

'll stage this for 2nd wave so that it still goes in for 4.18. -- Jiri Kosina SUSE Labs

Re: [PATCH] HID: steam: use hid_device.driver_data instead of hid_set_drvdata()

'll stage this for 2nd wave so that it still goes in for 4.18. -- Jiri Kosina SUSE Labs

[GIT PULL] HID

() comment Jason Gerecke (1): HID: wacom: Support "in range" for Intuos/Bamboo tablets where possible Jiri Kosina (2): HID: steam: add missing fields in client initialization HID: multitouch: fix types returned from mt_need_to_apply_feature() Robert Munteanu (1):

[GIT PULL] HID

() comment Jason Gerecke (1): HID: wacom: Support "in range" for Intuos/Bamboo tablets where possible Jiri Kosina (2): HID: steam: add missing fields in client initialization HID: multitouch: fix types returned from mt_need_to_apply_feature() Robert Munteanu (1):

[GIT] livepatching

not longer valid limitations from the documentation Documentation/livepatch/livepatch.txt | 24 1 file changed, 24 deletions(-) -- Jiri Kosina SUSE Labs

[GIT] livepatching

not longer valid limitations from the documentation Documentation/livepatch/livepatch.txt | 24 1 file changed, 24 deletions(-) -- Jiri Kosina SUSE Labs

Re: [PATCH] HID: rmi: use HID_QUIRK_NO_INPUT_SYNC

can you check for any sides effects please? I have now added Oscar's Tested-by: line and queued in for-4.18/rmi. In case any sideeffects are discovered, I'll either not include for-4.18/rmi in the push to Linus, or we'll do incremental fixups on top (depending on the nature of the side-effects :) ). Thanks, -- Jiri Kosina SUSE Labs

Re: [PATCH] HID: rmi: use HID_QUIRK_NO_INPUT_SYNC

can you check for any sides effects please? I have now added Oscar's Tested-by: line and queued in for-4.18/rmi. In case any sideeffects are discovered, I'll either not include for-4.18/rmi in the push to Linus, or we'll do incremental fixups on top (depending on the nature of the side-effects :) ). Thanks, -- Jiri Kosina SUSE Labs

Re: [PATCH] HID: multitouch: fix calculation of last slot field in multi-touch reports

ows-precision-touchpad-input-reports > [2] https://patchwork.kernel.org/patch/1742181/ > > Fixes: 29cc309d8bf19 ("HID: hid-multitouch: forward MSC_TIMESTAMP") > Signed-off-by: Ben Chan Applied, thanks Ben. -- Jiri Kosina SUSE Labs

Re: [PATCH] HID: multitouch: fix calculation of last slot field in multi-touch reports

ows-precision-touchpad-input-reports > [2] https://patchwork.kernel.org/patch/1742181/ > > Fixes: 29cc309d8bf19 ("HID: hid-multitouch: forward MSC_TIMESTAMP") > Signed-off-by: Ben Chan Applied, thanks Ben. -- Jiri Kosina SUSE Labs

Re: [PATCH] HID: steam: select CONFIG_POWER_SUPPLY

ice.") > Signed-off-by: Arnd Bergmann Applied, thanks. -- Jiri Kosina SUSE Labs

Re: [PATCH] HID: steam: select CONFIG_POWER_SUPPLY

ice.") > Signed-off-by: Arnd Bergmann Applied, thanks. -- Jiri Kosina SUSE Labs

Re: [PATCH] livepatch: Remove not longer valid limitations from the documentation

introduce shadow variable API"). > > It is a high time we removed these limitations from the documentation. > > Signed-off-by: Petr Mladek <pmla...@suse.com> > --- > I have found this when working on v12 of the atomic replace. It looks > like a no-brainer and does not conf

Re: [PATCH] livepatch: Remove not longer valid limitations from the documentation

introduce shadow variable API"). > > It is a high time we removed these limitations from the documentation. > > Signed-off-by: Petr Mladek > --- > I have found this when working on v12 of the atomic replace. It looks > like a no-brainer and does not conflict with the patchset, so ... ;-) Applied, thanks. -- Jiri Kosina SUSE Labs

Re: rtc: fix chardev initialization races

On Tue, 22 May 2018, Uwe Kleine-König wrote: > [adding linux-rtc ML and Alexandre to Cc:] > > Hello, > > On Tue, May 22, 2018 at 02:09:36PM +0200, Jiri Kosina wrote: > > On Mon, 21 May 2018, Uwe Kleine-König wrote: > > > > > > The race looks like th

Re: rtc: fix chardev initialization races

On Tue, 22 May 2018, Uwe Kleine-König wrote: > [adding linux-rtc ML and Alexandre to Cc:] > > Hello, > > On Tue, May 22, 2018 at 02:09:36PM +0200, Jiri Kosina wrote: > > On Mon, 21 May 2018, Uwe Kleine-König wrote: > > > > > > The race looks like th

Re: rtc: fix chardev initialization races

tanding, when rtc_device_unregister returned, the cdev is gone and > so chrdev_open is supposed to fail. Oh wow, hello back to 4 years ago! Looking at the current code, I don't think there is no such race any more, as the last thing cmos_do_probe() -> __rtc_register_device() does that can potentiall

Re: rtc: fix chardev initialization races

tanding, when rtc_device_unregister returned, the cdev is gone and > so chrdev_open is supposed to fail. Oh wow, hello back to 4 years ago! Looking at the current code, I don't think there is no such race any more, as the last thing cmos_do_probe() -> __rtc_register_device() does that can potentiall

Re: [PATCH] HID: i2c-hid: check if device is there before really probing

. > > To avoid bunch of scary messages when device is not actually present in the > system let's try testing basic communication with it and if there is no > response terminate probe early with -ENXIO. > > Signed-off-by: Dmitry Torokhov <d...@chromium.org> Applied, thanks. -- Jiri Kosina SUSE Labs

Re: [PATCH] HID: i2c-hid: check if device is there before really probing

nch of scary messages when device is not actually present in the > system let's try testing basic communication with it and if there is no > response terminate probe early with -ENXIO. > > Signed-off-by: Dmitry Torokhov Applied, thanks. -- Jiri Kosina SUSE Labs

Re: [PATCH v9 0/2] hid-steam driver with user mode client dection

nt but who uses that? > > Anyway, this would be the change, I don't know if it is worth a whole > reroll... I've put this on top of your patches and queued in for-4.18/hid-steam. Thanks, -- Jiri Kosina SUSE Labs

Re: [PATCH v9 0/2] hid-steam driver with user mode client dection

nt but who uses that? > > Anyway, this would be the change, I don't know if it is worth a whole > reroll... I've put this on top of your patches and queued in for-4.18/hid-steam. Thanks, -- Jiri Kosina SUSE Labs

Re: [Ksummit-discuss] bug-introducing patches

r consumption by test bots. What I do for my trees is that I actually merge the '-fixes' branch (that is scheduled to go to Linus in the 'current' cycle) into my for-next branch as well. This has the advantage of (a) getting all the coverage linux-next does (b) seeing any potential merge conflicts early Is this not feasible for other trees? -- Jiri Kosina SUSE Labs

Re: [Ksummit-discuss] bug-introducing patches

r consumption by test bots. What I do for my trees is that I actually merge the '-fixes' branch (that is scheduled to go to Linus in the 'current' cycle) into my for-next branch as well. This has the advantage of (a) getting all the coverage linux-next does (b) seeing any potential merge conflicts early Is this not feasible for other trees? -- Jiri Kosina SUSE Labs

[GIT PULL] HID fixes for 4.17

(-) -- Jiri Kosina SUSE Labs

[GIT PULL] HID fixes for 4.17

(-) -- Jiri Kosina SUSE Labs

Re: [PATCH v9 0/2] hid-steam driver with user mode client dection

g/disabling lizard mode are the same. If noone has any objections (last chance to raise them), I'll be queuing this for 4.18. Thanks, -- Jiri Kosina SUSE Labs

Re: [PATCH v9 0/2] hid-steam driver with user mode client dection

g/disabling lizard mode are the same. If noone has any objections (last chance to raise them), I'll be queuing this for 4.18. Thanks, -- Jiri Kosina SUSE Labs

[tip:x86/urgent] x86/mm: Make vmemmap and vmalloc base address constants unsigned long

Commit-ID: 14d12bb8582e158006c35cce0f8ae1706094f9a4 Gitweb: https://git.kernel.org/tip/14d12bb8582e158006c35cce0f8ae1706094f9a4 Author: Jiri Kosina <jkos...@suse.cz> AuthorDate: Thu, 12 Apr 2018 14:39:10 +0200 Committer: Thomas Gleixner <t...@linutronix.de> CommitDate: Thu,

[tip:x86/urgent] x86/mm: Make vmemmap and vmalloc base address constants unsigned long

Commit-ID: 14d12bb8582e158006c35cce0f8ae1706094f9a4 Gitweb: https://git.kernel.org/tip/14d12bb8582e158006c35cce0f8ae1706094f9a4 Author: Jiri Kosina AuthorDate: Thu, 12 Apr 2018 14:39:10 +0200 Committer: Thomas Gleixner CommitDate: Thu, 26 Apr 2018 14:56:24 +0200 x86/mm: Make vmemmap

Re: [PATCH] hid: intel-ish-hid: use put_device() instead of kfree()

On Fri, 30 Mar 2018, Arvind Yadav wrote: > Never directly free @dev after calling device_register(), even > if it returned an error. Always use put_device() to give up the > reference initialized. > > Signed-off-by: Arvind Yadav <arvind.yadav...@gmail.com> Applied, thank

Re: [PATCH] hid: intel-ish-hid: use put_device() instead of kfree()

On Fri, 30 Mar 2018, Arvind Yadav wrote: > Never directly free @dev after calling device_register(), even > if it returned an error. Always use put_device() to give up the > reference initialized. > > Signed-off-by: Arvind Yadav Applied, thank you. -- Jiri Kosina SUSE Labs

Re: [PATCH 0/4] HID: alps: Fix some bugs and improve code around 't4_read_write_register()'

ter()' > HID: alps: Fix some style in 't4_read_write_register()' > > drivers/hid/hid-alps.c | 27 ++- > 1 file changed, 22 insertions(+), 5 deletions(-) Queued for 4.18, thanks. -- Jiri Kosina SUSE Labs

Re: [PATCH 0/4] HID: alps: Fix some bugs and improve code around 't4_read_write_register()'

ter()' > HID: alps: Fix some style in 't4_read_write_register()' > > drivers/hid/hid-alps.c | 27 ++- > 1 file changed, 22 insertions(+), 5 deletions(-) Queued for 4.18, thanks. -- Jiri Kosina SUSE Labs

Re: [PATCH v2 0/6] HID: input cleanups and mt additions

On Tue, 24 Apr 2018, Benjamin Tissoires wrote: > following the thread about the 'not incrementing ABS_MISC', here is the > actual submission of the series. Thanks Benjamin, this looks nice. I've queued it for 4.18. -- Jiri Kosina SUSE Labs

Re: [PATCH v2 0/6] HID: input cleanups and mt additions

On Tue, 24 Apr 2018, Benjamin Tissoires wrote: > following the thread about the 'not incrementing ABS_MISC', here is the > actual submission of the series. Thanks Benjamin, this looks nice. I've queued it for 4.18. -- Jiri Kosina SUSE Labs

Re: [PATCH] x86/mm: vmemmap and vmalloc base addressess are usngined longs

e more > > tricky. > > I don't have a problem with the patch: > > Acked-by: Kirill A. Shutemov <kirill.shute...@linux.intel.com> ping, please? sparse build is still noisy like hell :/ Thanks, -- Jiri Kosina SUSE Labs

Re: [PATCH] x86/mm: vmemmap and vmalloc base addressess are usngined longs

ch treats this as > > a generic case (where the missing UL might be a problem), and totally > > pollutes the build output. > > > > Either we put the 'UL' there, or teach sparse about figuring out the > > 'closer bigger fitting type' for hexadecimal literals, which might be more > > tricky. > > I don't have a problem with the patch: > > Acked-by: Kirill A. Shutemov ping, please? sparse build is still noisy like hell :/ Thanks, -- Jiri Kosina SUSE Labs

Re: [PATCH 07/24] hibernate: Disable when the kernel is locked down

On Thu, 26 Apr 2018, Pavel Machek wrote: > That's not how the crypto needs to work. Talk to Jiri Kosina, ok? Yeah, Joey Lee (adding to CC) implemented it here: https://lkml.org/lkml/2015/8/11/47 I think there have been more respins, Joey definitely knows more details and status

Re: [PATCH 07/24] hibernate: Disable when the kernel is locked down

On Thu, 26 Apr 2018, Pavel Machek wrote: > That's not how the crypto needs to work. Talk to Jiri Kosina, ok? Yeah, Joey Lee (adding to CC) implemented it here: https://lkml.org/lkml/2015/8/11/47 I think there have been more respins, Joey definitely knows more details and status

Re: [PATCH] HID: wacom: Release device resource data obtained by devres_alloc()

On Tue, 24 Apr 2018, Arvind Yadav wrote: > Free device resource data, if __wacom_devm_sysfs_create_group > is not successful. Applied, thanks. -- Jiri Kosina SUSE Labs

Re: [PATCH] HID: wacom: Release device resource data obtained by devres_alloc()

On Tue, 24 Apr 2018, Arvind Yadav wrote: > Free device resource data, if __wacom_devm_sysfs_create_group > is not successful. Applied, thanks. -- Jiri Kosina SUSE Labs

[GIT PULL] HID fixes

Bluetooth devices Aaron Ma (1): HID: i2c-hid: Fix resume issue on Raydium touchscreen device Dmitry Torokhov (1): HID: input: fix battery level reporting on BT mice Jiri Kosina (1): HID: i2c-hid: fix inverted return value from i2c_hid_command() Rodrigo Rivas Costa (1

[GIT PULL] HID fixes

Bluetooth devices Aaron Ma (1): HID: i2c-hid: Fix resume issue on Raydium touchscreen device Dmitry Torokhov (1): HID: input: fix battery level reporting on BT mice Jiri Kosina (1): HID: i2c-hid: fix inverted return value from i2c_hid_command() Rodrigo Rivas Costa (1

[GIT PULL] livepatching fix

/livepatch/shadow.c | 108 -- samples/livepatch/livepatch-shadow-fix1.c | 43 +--- samples/livepatch/livepatch-shadow-fix2.c | 33 - 5 files changed, 163 insertions(+), 81 deletions(-) -- Jiri Kosina SUSE Labs

[GIT PULL] livepatching fix

/livepatch/shadow.c | 108 -- samples/livepatch/livepatch-shadow-fix1.c | 43 +--- samples/livepatch/livepatch-shadow-fix2.c | 33 - 5 files changed, 163 insertions(+), 81 deletions(-) -- Jiri Kosina SUSE Labs

Re: [PATCH] x86/mm: vmemmap and vmalloc base addressess are usngined longs

be more > > tricky. > > I don't have a problem with the patch: > > Acked-by: Kirill A. Shutemov <kirill.shute...@linux.intel.com> x86 folks, any objections to merging this? Without it, the sparse build is currently totally unreadable mess. Thanks, -- Jiri Kosina SUSE Labs

Re: [PATCH] x86/mm: vmemmap and vmalloc base addressess are usngined longs

> > tricky. > > I don't have a problem with the patch: > > Acked-by: Kirill A. Shutemov x86 folks, any objections to merging this? Without it, the sparse build is currently totally unreadable mess. Thanks, -- Jiri Kosina SUSE Labs

Re: [PATCH AUTOSEL for 4.14 015/161] printk: Add console owner and waiter logic to load balance console writes

stable, the proper solution (and contribution) would be just bringing more people into the XFS community. To put it simply -- I don't think the simple lack of actual human brainpower can be reasonably resolved in other way than bringing more of it in. Thanks, -- Jiri Kosina SUSE Labs

Re: [PATCH AUTOSEL for 4.14 015/161] printk: Add console owner and waiter logic to load balance console writes

stable, the proper solution (and contribution) would be just bringing more people into the XFS community. To put it simply -- I don't think the simple lack of actual human brainpower can be reasonably resolved in other way than bringing more of it in. Thanks, -- Jiri Kosina SUSE Labs

Re: [PATCH v2 2/2] HID: input: do not increment usages when a duplicate is found

orokhov <dmitry.torok...@gmail.com> Sorry, I somehow lost this one. Now queued for 4.18. Thanks, -- Jiri Kosina SUSE Labs

Re: [PATCH v2 2/2] HID: input: do not increment usages when a duplicate is found

y Torokhov Sorry, I somehow lost this one. Now queued for 4.18. Thanks, -- Jiri Kosina SUSE Labs

Re: [PATCH v6] Fix modifier keys for Redragon Asura Keyboard

not working, keyboard device. > > Signed-off-by: Robert Munteanu <romb...@apache.org> Applied, thanks. -- Jiri Kosina SUSE Labs

Re: [PATCH v6] Fix modifier keys for Redragon Asura Keyboard

not working, keyboard device. > > Signed-off-by: Robert Munteanu Applied, thanks. -- Jiri Kosina SUSE Labs

Re: [PATCH v3 0/2] livepatch: Allocate and free shadow variables more safely

nother location. Queued in for-4.17/upstream-fixes. Thanks, -- Jiri Kosina SUSE Labs

Re: [PATCH v3 0/2] livepatch: Allocate and free shadow variables more safely

nother location. Queued in for-4.17/upstream-fixes. Thanks, -- Jiri Kosina SUSE Labs

Re: [PATCH AUTOSEL for 4.14 015/161] printk: Add console owner and waiter logic to load balance console writes

re simply was no other way, and I took it for given that this is seen by everybody involved as an absolute exception, due to the nature of the issue and of the massive changes that were needed. Thanks, -- Jiri Kosina SUSE Labs

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