Signed-off-by: Artem Savkov
---
drivers/firmware/dmi_scan.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/firmware/dmi_scan.c b/drivers/firmware/dmi_scan.c
index 3439f59..40e940d 100644
--- a/drivers/firmware/dmi_scan.c
+++ b/drivers/firmware/dmi_scan.c
@@ -410,7 +410,7 @@ s
or invalid.
Introduced in dmi_scan: refactor dmi_scan_machine(), {smbios,dmi}_present()
Signed-off-by: Artem Savkov artem.sav...@gmail.com
---
drivers/firmware/dmi_scan.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/firmware/dmi_scan.c b/drivers/firmware/dmi_scan.c
index
On Wed, Mar 06, 2013 at 04:50:39PM +0100, Oleg Nesterov wrote:
> On 03/05, Andrew Morton wrote:
> >
> > Basically the same as
> > http://ozlabs.org/~akpm/mmots/broken-out/drivers-platform-x86-thinkpad_acpic-move-hotkey_thread_mutex-lock-after-set_freezable.patch.
> > I think Artem's patch is a
On Wed, Mar 06, 2013 at 04:50:39PM +0100, Oleg Nesterov wrote:
On 03/05, Andrew Morton wrote:
Basically the same as
http://ozlabs.org/~akpm/mmots/broken-out/drivers-platform-x86-thinkpad_acpic-move-hotkey_thread_mutex-lock-after-set_freezable.patch.
I think Artem's patch is a little
On Mon, Feb 25, 2013 at 03:54:45PM -0800, Andrew Morton wrote:
> On Sun, 24 Feb 2013 13:22:02 +0400
> Artem Savkov wrote:
>
> > set_freezable() checks freezing during which no locks should be held.
> > hotkey_thread_mutex lock should be moved closer to where it is
On Mon, Feb 25, 2013 at 03:54:45PM -0800, Andrew Morton wrote:
On Sun, 24 Feb 2013 13:22:02 +0400
Artem Savkov artem.sav...@gmail.com wrote:
set_freezable() checks freezing during which no locks should be held.
hotkey_thread_mutex lock should be moved closer to where it is actually
set_freezable() checks freezing during which no locks should be held.
hotkey_thread_mutex lock should be moved closer to where it is actually needed.
Signed-off-by: Artem Savkov
---
drivers/platform/x86/thinkpad_acpi.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git
set_freezable() checks freezing during which no locks should be held.
hotkey_thread_mutex lock should be moved closer to where it is actually needed.
Signed-off-by: Artem Savkov artem.sav...@gmail.com
---
drivers/platform/x86/thinkpad_acpi.c | 6 +++---
1 file changed, 3 insertions(+), 3
intel_pstate.c won't compile on i686 because of a linking error:
drivers/cpufreq/intel_pstate.c:459: undefined reference to `__udivdi3'
Signed-off-by: Artem Savkov
---
drivers/cpufreq/intel_pstate.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/cpufreq
intel_pstate.c won't compile on i686 because of a linking error:
drivers/cpufreq/intel_pstate.c:459: undefined reference to `__udivdi3'
Signed-off-by: Artem Savkov artem.sav...@gmail.com
---
drivers/cpufreq/intel_pstate.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git
Added missing idr_preload_end calls in drm_gem_flink_ioctl().
Without those preemption stays disabled resulting in lots of "scheduling while
atomic" BUGs.
Introduced in 4e486fae707d9a79c76f1be6dcacffc4a721cc1b (linux-next.git)
Signed-off-by: Artem Savkov
---
drivers/gpu/drm/drm_gem.c
Added missing idr_preload_end calls in drm_gem_flink_ioctl().
Without those preemption stays disabled resulting in lots of scheduling while
atomic BUGs.
Introduced in 4e486fae707d9a79c76f1be6dcacffc4a721cc1b (linux-next.git)
Signed-off-by: Artem Savkov artem.sav...@gmail.com
---
drivers/gpu/drm
irqsave(_driver_lock, flags);
> if (driver->exit)
> driver->exit(data);
> - spin_unlock_irqrestore(_driver_lock, flags);
>
> free_cpumask_var(data->related_cpus);
> free_cpumask_var(data->cpus);
Tested-by: Artem Savkov
--
Kind regards,
Artem
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
On Thu, Feb 07, 2013 at 03:57:42PM +0530, Viresh Kumar wrote:
> Hi Rafael,
>
> This is another unplanned patchset for all the platforms that i broke. :)
>
> Okay, there are two important fixes (1 & 4) and two general cleanups (2 & 3).
> I
> hope most of the issues would be resolved by these and
On Thu, Feb 07, 2013 at 03:57:42PM +0530, Viresh Kumar wrote:
Hi Rafael,
This is another unplanned patchset for all the platforms that i broke. :)
Okay, there are two important fixes (1 4) and two general cleanups (2 3).
I
hope most of the issues would be resolved by these and we would
(data-cpus);
Tested-by: Artem Savkov artem.sav...@gmail.com
--
Kind regards,
Artem
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ
On Thu, Feb 07, 2013 at 01:41:57AM +0100, Rafael J. Wysocki wrote:
> On Wednesday, February 06, 2013 10:11:25 PM Rafael J. Wysocki wrote:
> > On Thursday, February 07, 2013 12:25:13 AM Artem Savkov wrote:
> > > I get the following BUG on suspend using systemd-sleep(this do
I get the following BUG on suspend using systemd-sleep(this doesn't
happen with pm-suspend). This seems to be introduced by some of the
Viresh's patches.
[ 94.908046] Disabling non-boot CPUs ...
[ 94.908416] BUG: sleeping function called from invalid context at
kernel/workqueue.c:2811
[
I get the following BUG on suspend using systemd-sleep(this doesn't
happen with pm-suspend). This seems to be introduced by some of the
Viresh's patches.
[ 94.908046] Disabling non-boot CPUs ...
[ 94.908416] BUG: sleeping function called from invalid context at
kernel/workqueue.c:2811
[
On Thu, Feb 07, 2013 at 01:41:57AM +0100, Rafael J. Wysocki wrote:
On Wednesday, February 06, 2013 10:11:25 PM Rafael J. Wysocki wrote:
On Thursday, February 07, 2013 12:25:13 AM Artem Savkov wrote:
I get the following BUG on suspend using systemd-sleep(this doesn't
happen with pm-suspend
On Sun, Feb 03, 2013 at 07:04:35PM +, Al Viro wrote:
> On Sun, Feb 03, 2013 at 07:59:12PM +0100, Ingo Molnar wrote:
> >
> > * Artem Savkov wrote:
> >
> > > asmlinkage tag seems to be missing from sys_iopl prototype rendering iopl
> > > syscalls un
asmlinkage tag seems to be missing from sys_iopl prototype rendering iopl
syscalls unusable, i.e. every call returns -EINVAL. Most likely introduced in
9e0b2428bc6a6c6df90bb701ca843820727cadf0.
Signed-off-by: Artem Savkov
---
arch/x86/include/asm/syscalls.h | 2 +-
arch/x86/kernel/ioport.c
asmlinkage tag seems to be missing from sys_iopl prototype rendering iopl
syscalls unusable, i.e. every call returns -EINVAL. Most likely introduced in
9e0b2428bc6a6c6df90bb701ca843820727cadf0.
Signed-off-by: Artem Savkov artem.sav...@gmail.com
---
arch/x86/include/asm/syscalls.h | 2 +-
arch
On Sun, Feb 03, 2013 at 07:04:35PM +, Al Viro wrote:
On Sun, Feb 03, 2013 at 07:59:12PM +0100, Ingo Molnar wrote:
* Artem Savkov artem.sav...@gmail.com wrote:
asmlinkage tag seems to be missing from sys_iopl prototype rendering iopl
syscalls unusable, i.e. every call returns
On Sat, Aug 18, 2012 at 11:25:43PM -0500, Shaun Ruffell wrote:
> Adding linux-net to the CC list.
>
> On Fri, Aug 17, 2012 at 11:57:56PM +0100, Dave Haywood wrote:
> > [1.] One line summary of the problem:
> > BUG: unable to handle kernel paging request at 00010016
> >
> > System boots then
On Sat, Aug 18, 2012 at 11:25:43PM -0500, Shaun Ruffell wrote:
Adding linux-net to the CC list.
On Fri, Aug 17, 2012 at 11:57:56PM +0100, Dave Haywood wrote:
[1.] One line summary of the problem:
BUG: unable to handle kernel paging request at 00010016
System boots then crashes a
201 - 226 of 226 matches
Mail list logo
