On 8/5/13 2:09 AM, Xiao Guangrong wrote:
On 08/03/2013 04:05 AM, David Ahern wrote:
Signed-off-by: David Ahern
Cc: Arnaldo Carvalho de Melo
Cc: Ingo Molnar
Cc: Frederic Weisbecker
Cc: Peter Zijlstra
Cc: Jiri Olsa
Cc: Namhyung Kim
Cc: Xiao Guangrong
Cc: Runzhen Wang
---
On 08/05, Felipe Contreras wrote:
>
> On Mon, Aug 5, 2013 at 8:29 AM, Oleg Nesterov wrote:
> >
> > Could you please run wine under strace
> >
> > strace -f -e ptrace -o LOG wine ...
> >
> > and show the result?
>
> Sure.
Thanks.
> Note that the crash might have happened some time before
On 8/5/13 1:53 AM, Xiao Guangrong wrote:
Hi David,
Thanks for your nice job! I got some questions.
On 08/03/2013 04:05 AM, David Ahern wrote:
static int kvm_events_hash_fn(u64 key)
{
return key & (EVENTS_CACHE_SIZE - 1);
@@ -472,7 +501,11 @@ static bool handle_end_event(struct
On Mon, Aug 05, 2013 at 01:25:31PM +0530, Ashish Chavan wrote:
> On Mon, 2013-07-29 at 17:01 +0100, Mark Brown wrote:
> > Well, it's a very unusual hardware design choice to have multiple I2C
> > endpoints in a single physical chip.
> I hope to see more of such devices in near future.
There's
On Mon, Aug 5, 2013 at 9:04 AM, Rafael J. Wysocki wrote:
>> In my machine I think the issue is slightly different, I think _BCM is
>> failing, at least until enabling the _DOS thing, but at the end of the
>> day it's the same thing for the check; _BQC is always returning the
>> same value, and
On Mon, Aug 05, 2013 at 04:27:44PM +0200, Laszlo Ersek wrote:
> I wouldn't call the design of SetVirtualAddressMap() braindead.
Ok, I've always wondered and you could probably shed some light on the
matter: why is SetVirtualAddressMap() a call-once only? Why can't I
simply call it again and
quot;#dma-cells" to "<2>"
Applies to next-20130805
.../devicetree/bindings/dma/moxa,moxart-dma.txt| 21 +
drivers/dma/Kconfig| 7 +
drivers/dma/Makefile | 1 +
drivers/dma/moxart-d
On Mon, Aug 05, 2013 at 11:38:14AM +0800, Jason Wang wrote:
> On 07/25/2013 04:54 PM, Jason Wang wrote:
> > We try to handle the hypervisor compatibility mode by detecting hypervisor
> > through a specific order. This is not robust, since hypervisors may
> > implement
> > each others features.
>
On 08/05/2013 07:35 PM, Paolo Bonzini wrote:
I guess you'd want to carry this in the KVM tree or so - maybe in a
separate branch because it changes Xen as well?
It changes KVM host and guest side, XEN and common x86 spinlock code. I
think it would be best to merge common x86 spinlock bits and
* Steven Rostedt wrote:
> Linus,
>
> Oleg Nesterov has been working hard in closing all the holes that can
> lead to race conditions between deleting an event and accessing an event
> debugfs file. This included a fix to the debugfs system (acked by Greg
> Kroah-Hartman). We think that all
On Sun, Aug 04, 2013 at 08:45:16PM -0700, Linus Torvalds wrote:
> The patch looks right to me - we should pass in similar flags for the
> create case as for tmpfile to the filesystem.
>
> But let's make sure we're all on the same page. Al?
ACK. It used to happen as a side effect of O_CREAT
On Mon, Aug 5, 2013 at 8:29 AM, Oleg Nesterov wrote:
> On 08/04, Felipe Contreras wrote:
>>
>> I found a regression while running all v3.11-rcX kernels; Starcract II
>> through wine crashes.
>
> Thanks... just to clarify, Starcract crashes, wine or kernel?
It's Starcraft. In fact, it detects the
Linus,
Oleg Nesterov has been working hard in closing all the holes that can
lead to race conditions between deleting an event and accessing an event
debugfs file. This included a fix to the debugfs system (acked by
Greg Kroah-Hartman). We think that all the holes have been patched and
hopefully
On Thu, Aug 01, 2013 at 05:49:53PM -0400, Tejun Heo wrote:
> cgroup is currently in the process of transitioning to using css
> (cgroup_subsys_state) as the primary handle instead of cgroup in
> subsystem API. For hierarchy iterators, this is beneficial because
>
> * In most cases, css is the
On 08/05/13 16:03, Borislav Petkov wrote:
> On Mon, Aug 05, 2013 at 03:39:31PM +0200, Laszlo Ersek wrote:
>> My question was: is my understanding correct that you only see this
>> problem with "-enable-kvm"? Because,
>>
>> On 08/01/13 18:49, Borislav Petkov wrote:
>>> so I'm seeing this funny
On Thu, Aug 01, 2013 at 05:49:50PM -0400, Tejun Heo wrote:
> cgroup is currently in the process of transitioning to using struct
> cgroup_subsys_state * as the primary handle instead of struct cgroup.
> Please see the previous commit which converts the subsystem methods
> for rationale.
>
> This
On Fri, Aug 02, 2013 at 02:29:02PM -0700, Roy Franz wrote:
> The ARM kernel also has an EFI stub which works largely the same way
> as the x86 stub, so move the documentation out of x86 directory and
> update to reflect that it is generic, and add ARM specific text.
>
> Signed-off-by: Roy Franz
On Fri, Aug 02, 2013 at 02:29:07PM -0700, Roy Franz wrote:
> This patch adds EFI stub support for the ARM Linux kernel. The EFI stub
> operations similarly to the x86 stub: it is a shim between the EFI firmware
> and the normal zImage entry point, and sets up the environment that the
> zImage is
> > On Mon, Aug 05, 2013 at 11:46:03AM +0200, Ingo Molnar wrote:
> > > Acked-by: Ingo Molnar
> > >
> > > I guess you'd want to carry this in the KVM tree or so - maybe in a
> > > separate branch because it changes Xen as well?
> >
> > It changes KVM host and guest side, XEN and common x86
From: Rafael J. Wysocki
The create_dev label in acpi_create_platform_device() is not
necessary, because the if statement causing the jump to it to
happen may be rearranged to avoid that jump.
Rework the code accordingly (no functional changes should result
from that).
Signed-off-by: Rafael J.
On Mon, Aug 05, 2013 at 03:39:31PM +0200, Laszlo Ersek wrote:
> My question was: is my understanding correct that you only see this
> problem with "-enable-kvm"? Because,
>
> On 08/01/13 18:49, Borislav Petkov wrote:
> > so I'm seeing this funny thing where an EFI region changes when we
> > enter
From: Rafael J. Wysocki
The list of physical devices corresponding to an ACPI device
object is walked by acpi_system_wakeup_device_seq_show() and
physical_device_enable_wakeup() without taking that object's
physical_node_lock mutex. Since each of those functions may be
run at any time as a
Commit-ID: 448ac44d561f0aba5baac54bac62fe40d07230b6
Gitweb: http://git.kernel.org/tip/448ac44d561f0aba5baac54bac62fe40d07230b6
Author: Jason Wang
AuthorDate: Thu, 25 Jul 2013 16:54:33 +0800
Committer: H. Peter Anvin
CommitDate: Mon, 5 Aug 2013 06:34:09 -0700
xen: Switch to use
Commit-ID: 9df56f19a500bea90d160be1bf77e4fbcd204d3f
Gitweb: http://git.kernel.org/tip/9df56f19a500bea90d160be1bf77e4fbcd204d3f
Author: Jason Wang
AuthorDate: Thu, 25 Jul 2013 16:54:35 +0800
Committer: H. Peter Anvin
CommitDate: Mon, 5 Aug 2013 06:35:33 -0700
x86: Correctly detect
Commit-ID: 1085ba7f552d84aa8ac0ae903fa8d0cc2ff9f79d
Gitweb: http://git.kernel.org/tip/1085ba7f552d84aa8ac0ae903fa8d0cc2ff9f79d
Author: Jason Wang
AuthorDate: Thu, 25 Jul 2013 16:54:34 +0800
Committer: H. Peter Anvin
CommitDate: Mon, 5 Aug 2013 06:34:33 -0700
x86, kvm: Switch to use
Commit-ID: 96e39ac0e9d18020c8c5a41b64b8fe86c26575ab
Gitweb: http://git.kernel.org/tip/96e39ac0e9d18020c8c5a41b64b8fe86c26575ab
Author: Jason Wang
AuthorDate: Thu, 25 Jul 2013 16:54:32 +0800
Committer: H. Peter Anvin
CommitDate: Mon, 5 Aug 2013 06:33:54 -0700
x86: Introduce
Hi all,
While fuzzing with trinity inside a KVM tools guest running latest -next kernel,
I've stumbled on the following spew caused by a new BUG() added in "aio: fix
io_destroy() regression by using call_rcu()".
[ 9646.599640] kernel BUG at fs/aio.c:646!
[ 9646.600119] invalid opcode: [#1]
Hi,
wrt to $Subject, I get this with 3.10.5:
[4.342638] i915 :00:02.0: setting latency timer to 64
[4.409045] INFO: trying to register non-static key.
[4.409164] the code is fine but needs lockdep annotation.
[4.409278] turning off the locking correctness validator.
[
On Sunday, August 04, 2013 09:19:56 AM Felipe Contreras wrote:
> On Sun, Aug 4, 2013 at 9:19 AM, Rafael J. Wysocki wrote:
> > On Sunday, August 04, 2013 01:42:49 AM Felipe Contreras wrote:
>
> >> Personally I think there are better ways to fix the code for the
> >> synthetic case than what you
* Gleb Natapov wrote:
> On Mon, Aug 05, 2013 at 11:46:03AM +0200, Ingo Molnar wrote:
> > Acked-by: Ingo Molnar
> >
> > I guess you'd want to carry this in the KVM tree or so - maybe in a
> > separate branch because it changes Xen as well?
>
> It changes KVM host and guest side, XEN and
On Mon, Aug 05, 2013 at 03:27:29PM +0200, Borislav Petkov wrote:
> On Mon, Aug 05, 2013 at 03:23:53PM +0200, Johannes Stezenbach wrote:
> > wrt to $Subject, I get this with 3.10.5:
> >
> > [4.342638] i915 :00:02.0: setting latency timer to 64
> > [4.409045] INFO: trying to register
The error hanling and ret-from-loop look confusing and inconsistent.
- "retval >= 0" simply returns
- "!bprm->file" returns too but with read_unlock() because
binfmt_lock was already re-acquired
- "retval != -ENOEXEC || bprm->mm == NULL" does "break" and
relies on the same check after the
A separate one-liner with the minor fix.
PROC_EVENT_EXEC reports the "exec" event, but this message
is sent at least twice if search_binary_handler() is called
by ->load_binary() recursively, say, load_script().
Move it to exec_binprm(), this is "depth == 0" code too.
Signed-off-by: Oleg
search_binary_handler() checks ->load_binary != NULL for no reason,
this method should be always defined. Turn this check into WARN_ON()
and move it into __register_binfmt().
Also, kill the function pointer. The current code looks confusing,
as if ->load_binary can go away after
A separate one-liner for better documentation.
It doesn't make sense to retry if request_module() fails to exec
/sbin/modprobe, add the additional "request_module() < 0" check.
However, this logic still doesn't look exactly right:
1. It would be better to check "request_module() != 0", the user
search_binary_handler() uses "for (try=0; try<2; try++)" to avoid
"goto" but the code looks too complicated and horrible imho. We
still need to check "try == 0" before request_module() and add the
additional "break" for !CONFIG_MODULES case.
Kill this loop and use a simple "bool need_retry" +
task_pid_nr_ns() and trace/ptrace code in the middle of the
recursive search_binary_handler() looks confusing and imho
annoying. We only need this code if "depth == 0", lets add
a simple helper which calls search_binary_handler() and does
trace_sched_process_exec() + ptrace_event().
The patch
Nobody except search_binary_handler() should touch ->recursion_depth,
"int depth" buys nothing but complicates the code, kill it.
Probably we should also kill "fn" and the !NULL check, ->load_binary
should be always defined. And it can not go away after read_unlock()
or this code is buggy anyway.
When search_binary_handler() succeeds it does allow_write_access()
and fput(), then it clears bprm->file to ensure the caller will not
do the same.
We can simply move this code to exec_binprm() which is called only
once. In fact we could move this to free_bprm() and remove the same
code in
To remind, by discussion with Zach
fs-binfmts-add-a-name-field-to-the-binfmt-struct.patch
fs-binfmts-better-handling-of-binfmt-loops.patch
fs-binfmts-whitespace-fixes-with-scripts-cleanfile.patch
should be dropped. Zach is working on the new version on top of these
On Mon, Aug 05, 2013 at 03:21:57PM +0200, Ralf Baechle wrote:
> On Mon, Aug 05, 2013 at 02:17:01PM +0100, James Hogan wrote:
>
> >
> > On 01/08/13 21:22, David Daney wrote:
> > > From: David Daney
> > >
> > > No code changes, just reflowing some comments and consistently using
> > > tabs and
Hi hpa,
I'm sorry but I don't quite following it.
On 08/05/2013 09:07 PM, H. Peter Anvin wrote:
On 08/01/2013 12:06 AM, Tang Chen wrote:
This patch-set aims to solve some problems at system boot time
to enhance memory hotplug functionality.
[Background]
The Linux kernel cannot migrate
On 08/05/13 15:02, Borislav Petkov wrote:
> On Mon, Aug 05, 2013 at 01:27:16PM +0200, Laszlo Ersek wrote:
>>> --- before 2013-07-31 22:20:52.316039492 +0200
>>> +++ after 2013-07-31 22:21:30.960731706 +0200
>>> @@ -9,7 +9,7 @@ efi: mem07: type=2, attr=0xf, range=[0x0
>>> efi: mem08:
On 08/04, Felipe Contreras wrote:
>
> I found a regression while running all v3.11-rcX kernels; Starcract II
> through wine crashes.
Thanks... just to clarify, Starcract crashes, wine or kernel?
> The culprit is fab840f (ptrace: PTRACE_DETACH
> should do flush_ptrace_hw_breakpoint(child)), I
Hello,
On 8/5/2013 3:09 PM, Bartlomiej Zolnierkiewicz wrote:
On Monday, August 05, 2013 08:16:40 PM Cho KyongHo wrote:
> > -Original Message-
> > From: Bartlomiej Zolnierkiewicz [mailto:b.zolnier...@samsung.com]
> > Sent: Saturday, August 03, 2013 2:14 AM
> >
> > Hi,
> >
> > On Friday,
On Sun, Aug 04, 2013 at 10:45:00AM +0200, Pali Rohár wrote:
> Here is new version (v3) of omap secure part patch:
>
> Other secure functions omap_smc1() and omap_smc2() calling instruction smc #0
> but Nokia RX-51 board needs to call smc #1 for PPA access.
>
> Signed-off-by: Ivaylo Dimitrov
>
On Sun 04-08-13 05:17:21, Kirill A. Shutemov wrote:
> From: "Kirill A. Shutemov"
>
> truncate_inode_pages_range() drops whole huge page at once if it's fully
> inside the range.
>
> If a huge page is only partly in the range we zero out the part,
> exactly like we do for partial small pages.
>
On Mon, Aug 05, 2013 at 03:23:53PM +0200, Johannes Stezenbach wrote:
> wrt to $Subject, I get this with 3.10.5:
>
> [4.342638] i915 :00:02.0: setting latency timer to 64
> [4.409045] INFO: trying to register non-static key.
> [4.409164] the code is fine but needs lockdep
Hi Rafael,
On 08/05/2013 09:26 PM, Rafael J. Wysocki wrote:
..
I think I understand what you're trying to achieve and I don't have objections
agaist the goal, but the matter is *how* to do that.
Why don't you do something like this:
(1) Introduce two new functions that will each do part
On Fri, 2 Aug 2013, Benjamin Tissoires wrote:
> > Could you please elaborate? (and put an elaborate description to revert
> > commit log perhaps?)
>
> Sure, so here is the revert commit log:
>
> --
>
> Commit "HID: hid-logitech-dj, querying_devices was never set" activate
> a flag which
On Mon, Aug 05, 2013 at 02:17:01PM +0100, James Hogan wrote:
>
> On 01/08/13 21:22, David Daney wrote:
> > From: David Daney
> >
> > No code changes, just reflowing some comments and consistently using
> > tabs and spaces. Object code is verified to be unchanged.
> >
> > Signed-off-by: David
Hi David,
On 01/08/13 21:22, David Daney wrote:
> From: David Daney
>
> No code changes, just reflowing some comments and consistently using
> tabs and spaces. Object code is verified to be unchanged.
>
> Signed-off-by: David Daney
> Acked-by: Ralf Baechle
> + /* Put the saved
> -Original Message-
> From: Bartlomiej Zolnierkiewicz [mailto:b.zolnier...@samsung.com]
> Sent: Saturday, August 03, 2013 2:32 AM
>
> Hi,
>
> On Friday, July 26, 2013 08:30:17 PM Cho KyongHo wrote:
> > When a device driver is registered, all constructs to handle System MMU
> > is
On Monday, August 05, 2013 09:33:32 AM Tang Chen wrote:
> Hi Rafael,
>
> On 08/02/2013 09:03 PM, Rafael J. Wysocki wrote:
> > On Friday, August 02, 2013 05:14:26 PM Tang Chen wrote:
> >> Besides the phys addr of the acpi tables, it will be very convenient if
> >> we also have the signature of
On Monday, August 05, 2013 11:21:51 AM Tang Chen wrote:
> Hi Rafael,
>
> On 08/02/2013 09:00 PM, Rafael J. Wysocki wrote:
> ..
> >> This patch splits acpi_boot_table_init() into two steps:
> >> 1. Parse RSDT, which cannot be overrided, and initialize
> >> acpi_gbl_root_table_list. (step 1
On Mon, Aug 05, 2013 at 07:59:01AM -0500, Rob Herring wrote:
> On 08/05/2013 07:40 AM, Sascha Hauer wrote:
> > devicetrees may have a linux,stdout-path property in the chosen
> > node describing the console device. This adds a helper function
> > to match a device against this property so a driver
On 08/05/13 14:26, Jason Cooper wrote:
On Mon, Aug 05, 2013 at 10:53:41AM +0100, Mark Rutland wrote:
I'm not entirely sure on this. The property described is still true for
the device, even if the kernel's not using that information now. My
feeling would be to keep them, unless there's a plan
On Monday, August 05, 2013 08:16:40 PM Cho KyongHo wrote:
> > -Original Message-
> > From: Bartlomiej Zolnierkiewicz [mailto:b.zolnier...@samsung.com]
> > Sent: Saturday, August 03, 2013 2:14 AM
> >
> > Hi,
> >
> > On Friday, July 26, 2013 08:28:19 PM Cho KyongHo wrote:
> > >
On 08/01/2013 12:06 AM, Tang Chen wrote:
> This patch-set aims to solve some problems at system boot time
> to enhance memory hotplug functionality.
>
> [Background]
>
> The Linux kernel cannot migrate pages used by the kernel because
> of the kernel direct mapping. Since va = pa + PAGE_OFFSET,
I seek your consent to present you as the next of kin to the account
of a deceased client for claims valued at Fourteen million, three
hundred thousand Pounds.
Contact me through my private email for details: halawani@ovi.com
Mr. Halawani, Azhar Abdulrahim.
Solicitors Legal Services
On 08/05/2013 06:02 AM, Matt Fleming wrote:
> On Tue, 30 Jul, at 08:52:12PM, Ingo Molnar wrote:
>> Pulled into tip:x86/urgent, thanks Matt!
>
> Thanks Ingo.
>
> Any chance we can get this to Linus for -rc5? The ARM EFI boot stub
> patches depend on the bug fix in this pull request.
>
Yes, we
On 08/05/2013 09:38 AM, Prashant Gaikwad wrote:
> On Thursday 01 August 2013 02:34 AM, Stephen Warren wrote:
>> On 07/31/2013 11:42 AM, Tuomas Tynkkynen wrote:
>>> The lock bit on PLL_U does not seem to be working correctly and
>>> sometimes never gets set when waiting for the PLL to come up.
>>>
On Monday, August 05, 2013 04:59:20 PM Yasuaki Ishimatsu wrote:
> (2013/08/05 13:00), Yasuaki Ishimatsu wrote:
> > (2013/08/04 9:37), Toshi Kani wrote:
> >> On Sat, 2013-08-03 at 03:01 +0200, Rafael J. Wysocki wrote:
> >>> On Friday, August 02, 2013 06:04:40 PM Toshi Kani wrote:
> On Sat,
On Mon, Aug 05, 2013 at 01:27:16PM +0200, Laszlo Ersek wrote:
> > --- before 2013-07-31 22:20:52.316039492 +0200
> > +++ after 2013-07-31 22:21:30.960731706 +0200
> > @@ -9,7 +9,7 @@ efi: mem07: type=2, attr=0xf, range=[0x0
> > efi: mem08: type=7, attr=0xf,
> >
On Tue, 30 Jul, at 08:52:12PM, Ingo Molnar wrote:
> Pulled into tip:x86/urgent, thanks Matt!
Thanks Ingo.
Any chance we can get this to Linus for -rc5? The ARM EFI boot stub
patches depend on the bug fix in this pull request.
--
Matt Fleming, Intel Open Source Technology Center
--
To
On 08/05/2013 07:40 AM, Sascha Hauer wrote:
> devicetrees may have a linux,stdout-path property in the chosen
> node describing the console device. This adds a helper function
> to match a device against this property so a driver can call
> add_preferred_console for a matching device.
>
>
On Thu, Aug 01, 2013 at 05:49:47PM -0400, Tejun Heo wrote:
> cgroup is transitioning to using css (cgroup_subsys_state) instead of
> cgroup as the primary subsystem handle. The cgroupfs file interface
> will be converted to use css's which requires finding out the
> subsystem from cftype so that
Hi Linus,
please pull from the 'for-linus' branch of
git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git for-linus
to receive the following updates:
Enable LZ4 compression for the kernel image, add the machine id for
the new zBC12 model, fix an issue with hanging dasd devices,
On Thu, Aug 01, 2013 at 05:49:46PM -0400, Tejun Heo wrote:
> cgroup is currently in the process of transitioning to using struct
> cgroup_subsys_state * as the primary handle instead of struct cgroup *
> in subsystem implementations for the following reasons.
>
> * With unified hierarchy,
On Sun, 04 Aug 2013 16:40:58 +0100
Nix wrote:
> I just got this panic on 3.10.4, in the middle of a large parallel
> compilation (of Chromium, as it happens) over NFSv3:
>
> [16364.527516] BUG: unable to handle kernel NULL pointer dereference at
> 0008
> [16364.527571] IP: []
devicetrees may have the linux,stdout-path property to specify the
console. This patch adds support to the i.MX serial driver for this.
Signed-off-by: Sascha Hauer
---
drivers/tty/serial/imx.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/tty/serial/imx.c
devicetrees may have a linux,stdout-path property in the chosen
node describing the console device. This adds a helper function
to match a device against this property so a driver can call
add_preferred_console for a matching device.
Signed-off-by: Sascha Hauer
---
drivers/of/base.c | 26
The following adds a helper for matching the linux,stdout-path property
in the chosen node and makes use of it in the i.MX serial
This is a series originally created by me. It was hijacked and then abandoned
by Jean-Christophe for v5. I reverted the changes by Jean-Christophe since
they
On Monday, August 05, 2013 07:29:09 AM Nishanth Menon wrote:
> minor nitpick.
> $subject: PM / OPP:
Those are things I can easily fix up when I'm applying the patch.
> On 08/03/2013 04:25 AM, Viresh Kumar wrote:
> > Export opp_add() so that modules can use it.
> >
> > Signed-off-by: Viresh Kumar
minor nitpick.
$subject: PM / OPP:
On 08/03/2013 04:25 AM, Viresh Kumar wrote:
Export opp_add() so that modules can use it.
Signed-off-by: Viresh Kumar
---
drivers/base/power/opp.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/base/power/opp.c b/drivers/base/power/opp.c
index
On Mon, Aug 05, 2013 at 10:53:41AM +0100, Mark Rutland wrote:
> On Sun, Aug 04, 2013 at 02:09:04AM +0100, Jason Cooper wrote:
> > DT Maintainers,
> >
> > It's been a week with no comment. Shall I assume it's ok to apply
> > this?
>
> Apologies for the delay, still catching up on binding review.
On Fri, 02 Aug, at 05:56:22PM, Leif Lindholm wrote:
> efi_lookup_mapped_addr() is a handy utility for other platforms than
> x86. Move it from arch/x86 to drivers/firmware. Add memmap pointer
> to global efi structure, and initialise it on x86.
>
> Signed-off-by: Leif Lindholm
> ---
>
Since e12d0271 ("nohz: Warn if the machine can not perform nohz_full")
Kernel triggers a WARN() in case sched clock is marked as unstable.
Make it output a proper Kconfig symbol (NO_HZ_FULL) when informing user
about this.
Signed-off-by: Jiri Kosina
---
kernel/time/tick-sched.c |2 +-
1
On Fri, 02 Aug, at 05:56:21PM, Leif Lindholm wrote:
> This patch makes ia64 use the new common code for configuration table
> scanning. It also removes the local definition of the global "efi"
> data structure.
>
> Signed-off-by: Leif Lindholm
> ---
> arch/ia64/kernel/efi.c | 54
>
On Fri, 02 Aug, at 05:56:20PM, Leif Lindholm wrote:
> This patch makes x86 use the new common code for configuration table
> scanning. It also removes the local definition of the global "efi"
> data structure.
>
> Signed-off-by: Leif Lindholm
> ---
> arch/x86/platform/efi/efi.c | 96
>
We must init the delayed_work for codec-codec links
otherwise shutting down the DAI chain will fault when
calling flush_delayed_work_sync() on the linked DAI.
Signed-off-by: Richard Fitzgerald
---
sound/soc/soc-core.c | 12
1 files changed, 12 insertions(+), 0 deletions(-)
diff
On Fri, 02 Aug, at 05:56:19PM, Leif Lindholm wrote:
> Common to (U)EFI support on all platforms is the global "efi" data
> structure, and the code that parses the System Table to locate
> addresses to populate that structure with.
>
> This patch adds both of these to the global EFI driver code.
>
From: Jin Xu
This patch fixes a deadlock bug that occurs quite often when there are
concurrent write and fsync on a same file.
Following is the simplified call trace when tasks get hung.
fsync thread:
- f2fs_sync_file
...
- f2fs_write_data_pages
...
- update_extent_cache
...
-
On Mon, Aug 05, 2013 at 05:58:36AM +, Yadwinder Singh Brar wrote:
> Samsung Enterprise Portal mySingle
>
Please fix your mailer to send plain text mails, or at least provide a
text/plain alternative.
signature.asc
Description: Digital signature
[ Bernhard added to CC ]
On Wed, 3 Jul 2013, Peter De Wachter wrote:
> IBM Scrollpoint have a trackpoint-like gizmo instead of a scroll wheel,
> which allows for two-dimensional scrolling. This driver provides an
> input mapping to make that work.
>
> The scrollpoint is also much more
On Tue, Jul 30, 2013 at 12:35:03AM +0200, Linus Walleij wrote:
> Sorry for taking eternities to look into this.
>
> On Tue, Jun 18, 2013 at 11:29 AM, Christian Ruppert
> wrote:
>
> > The pinmux driver of the Abilis Systems TB10x platform based on ARC700 CPUs.
> > Used to control the pinmux and
(2013/07/30 1:40), Tom Zanussi wrote:
> The original SOFT_DISABLE patches didn't add support for soft disable
> of syscall events; this adds it and paves the way for future patches
> allowing triggers to be added to syscall events, since triggers are
> built on top of SOFT_DISABLE.
>
> Add an
On Mon, Aug 05, 2013 at 06:34:56PM +0800, Wanpeng Li wrote:
> Why round robin allocator don't consume ZONE_DMA?
I guess lowmem reserve reserves it all, 4GB/256(ratio)=16MB.
The only way to relax it would be 1) to account depending on memblock
types and allow only the movable ones to bypass the
This patch fix following issues reported by Dan:-
1) There is no check limiting the size to 32 and it could be up to
253 bytes.
2) Use defines instead of magic numbers.
3) The oz_farewell struct is supposed to be a variable length struct
but the variable part is put in the middle. It
On 08/01/13 18:49, Borislav Petkov wrote:
> On Wed, Jul 31, 2013 at 10:55:27PM +0100, David Woodhouse wrote:
>> On Wed, 2013-07-31 at 22:54 +0200, Borislav Petkov wrote:
>>> so I'm seeing this funny thing where an EFI region changes when we enter
>>> efi_enter_virtual_mode when booting with edk2
On Sun 04-08-13 05:17:10, Kirill A. Shutemov wrote:
> From: "Kirill A. Shutemov"
>
> We're going to add/remove a number of page cache entries at once. This
> patch implements add_bdi_stat() which adjusts bdi stats by arbitrary
> amount. It's required for batched page cache manipulations.
>
>
On 7/11/2013 9:52 AM, Greg KH wrote:
On Thu, Jul 11, 2013 at 09:29:49AM +0530, Akhil Goyal wrote:
On 7/8/2013 3:19 PM, akhil.go...@freescale.com wrote:
From: Akhil Goyal
RF signal path is integral part of any system that transmits/receives RF
(radio frequency) signals. In these systems Data
On Fri, Aug 2, 2013 at 6:28 PM, Zbigniew Jędrzejewski-Szmek
wrote:
> On Fri, Aug 02, 2013 at 09:04:44AM -0700, Andy Lutomirski wrote:
>> CONFIG_FW_LOADER_USER_HELPER=y
> Do you need this? Unsetting this should help.
>
> """This option enables / disables the invocation of user-helper
> (e.g. udev)
On Sun 04-08-13 05:17:03, Kirill A. Shutemov wrote:
> From: "Kirill A. Shutemov"
>
> The radix tree is variable-height, so an insert operation not only has
> to build the branch to its corresponding item, it also has to build the
> branch to existing items if the size has to be increased (by
>
> -Original Message-
> From: Bartlomiej Zolnierkiewicz [mailto:b.zolnier...@samsung.com]
> Sent: Saturday, August 03, 2013 2:14 AM
>
> Hi,
>
> On Friday, July 26, 2013 08:28:19 PM Cho KyongHo wrote:
> > Signed-off-by: Cho KyongHo
> > ---
> >
This patch fixes following build warning.
drivers/built-in.o: In function `oz_hcd_heartbeat':
>> (.text+0x30aadd): undefined reference to `__divdi3'
drivers/built-in.o: In function `oz_hcd_heartbeat':
>> (.text+0x30ac85): undefined reference to `__divdi3'
Signed-off-by: Rupesh Gujare
---
Lines with incorrect spacing around an operator, such as:
bystander, correct,incorrect
would get "fixed" to
bystander,correct, incorrect
as the correct argument as well as the incorrectly-spaced operator
were both being trimmed. The correct argument only needs to be
right trimmed.
Joseph Salisbury writes:
> Hello,
>
> Please consider including upstream commit
> 9eebed7de660c0b5ab129a9de4f89d20b60de68c in the next v3.2.y, v3.5.y and
> v3.8.y releases.
>
> It was included upstream as of v3.11-rc1. It has been tested and
> confirmed to resolve
Li Zefan writes:
> Plese consider adding commit 0231bb5336758426b44ccd798ccd3c5419c95d58
> to stable tree. It fixes a real bug, which was explained here:
>
> http://thread.gmane.org/gmane.linux.kernel.perf.user/1144
>
> and I've managed to reproduce the bug in 3.4 kernel with the test
>
On Fri, 02 Aug, at 05:56:18PM, Leif Lindholm wrote:
> early_ioremap() on IA64 chooses its mapping type based on the EFI
> memory map. This patch adds an alias "early_memremap()" to be used
> where the targeted location is memory rather than an i/o device.
>
> Signed-off-by: Leif Lindholm
> ---
>
501 - 600 of 1482 matches
Mail list logo