On Thu, 2014-01-23 at 14:45 -0800, David Rientjes wrote:
> On Thu, 23 Jan 2014, Andrew Morton wrote:
>
> > > $ ./scripts/get_maintainer.pl -f drivers/firmware/google/Kconfig
> > > linux-kernel@vger.kernel.org (open list)
> > >
> > > I wonder why he's not listed as a recipient for patches from
>
On 01/21/2014 11:16 AM, Linus Torvalds wrote:
> On Mon, Nov 25, 2013 at 4:39 PM, Mark Brown wrote:
>>
>> If you're OK with octopus merges for things like this I'll definitely
>> take another look at using them, the enormous stack of merge commits
>> always looks noisy to me in the logs and pull re
Hi Linus,
Sorry for the late reply.
On 2014年01月22日 16:26, Linus Walleij wrote:
On Fri, Jan 17, 2014 at 1:25 PM, Hanjun Guo wrote:
From: Amit Daniel Kachhap
This macro does the same job as CLOCKSOURCE_OF_DECLARE. The device
name from the ACPI timer table is matched with all the registered
t
On Thursday, January 23, 2014 11:21:01 AM Bjorn Helgaas wrote:
> On Wed, Jan 22, 2014 at 8:42 PM, Yijing Wang wrote:
> > Since acpi_evaluate_object() returns acpi_status and not plain int,
> > ACPI_FAILURE() should be used for checking its return value. Also
> > add some detailed debug info when a
On 2014年01月22日 19:45, Mark Rutland wrote:
On Wed, Jan 22, 2014 at 08:26:50AM +, Linus Walleij wrote:
On Fri, Jan 17, 2014 at 1:25 PM, Hanjun Guo wrote:
From: Amit Daniel Kachhap
This macro does the same job as CLOCKSOURCE_OF_DECLARE. The device
name from the ACPI timer table is matched
I've got a second failure mode, too, also memblock related with the same
system but a different config. In this one, the memblock code looks to
have returned an address for which there is no virtual mapping. The PMD
is clear.
> [0.00] memblock_find_in_range_node():239
> [0.00] __
On 2014年01月22日 19:46, Mark Rutland wrote:
On Mon, Jan 20, 2014 at 09:08:32AM +, Hanjun Guo wrote:
On 2014-1-17 22:21, Arnd Bergmann wrote:
On Friday 17 January 2014, Hanjun Guo wrote:
From: Amit Daniel Kachhap
This macro does the same job as CLOCKSOURCE_OF_DECLARE. The device
name from t
Hi Linus,
just a few bugfixes for md.
The following changes since commit 8313b8e57f55b15e5b7f7fc5d1630bbf686a9a97:
md: fix problem when adding device to read-only array with bitmap.
(2014-01-14 16:44:08 +1100)
are available in the git repository at:
git://neil.brown.name/md tags/md/3.14
On 01/17/2014 06:03 PM, Bjorn Andersson wrote:
> From: "Ivan T. Ivanov"
>
> This bus driver supports the QUP i2c hardware controller in the Qualcomm
> MSM SOCs. The Qualcomm Universal Peripheral Engine (QUP) is a general
> purpose data path engine with input/output FIFOs and an embedded i2c
> mi
(2014/01/24 1:12), Steven Rostedt wrote:
> On Thu, 23 Jan 2014 11:52:11 -0300
> Arnaldo Carvalho de Melo wrote:
>
>> Em Thu, Jan 23, 2014 at 02:29:55AM +, Masami Hiramatsu escreveu:
>>> Since several local symbols can have same name (e.g. t_show),
>>> we need to use the actual address instead
Hi
Here I'm sending some ia64 patches to make it work in the ski emulator.
This has been broken for a long time.
Mikulas
--
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
This patch fixes the following bugs:
* Lockup when out of memory: If we are out of memory, we must actually
read the data and drop it. If we don't read the data, the interrupt is
still pending and the data are still in the emulator's queue. The guest
system locks up, processing the interrupt
The ski emulator can't spawn any process with larger stack than
0x7.
Signed-off-by: Mikulas Patocka
---
arch/ia64/include/asm/resource.h |6 ++
1 file changed, 6 insertions(+)
Index: linux-2.6-ia64/arch/ia64/include/asm/resource.h
===
The simscsi driver processes the requests in the request routine and then
offloads the completion callback to a tasklet. This is buggy because there
is parallel unsynchronized access to the completion queue from the request
routine and from the tasklet.
With current SCSI architecture, requests can
Fix some warnings in ia64:
arch/ia64/kernel/sys_ia64.c:29:20: warning: unused variable 'mm'
[-Wunused-variable]
arch/ia64/sn/kernel/setup.c:582:23: warning: argument to 'sizeof' in
'memset' call is the same pointer type 'struct pda_s *' as the
destination; expected 'struct pda_s' or an explicit l
Fix sleeping with interrupts disabled warning in simserial.c:
BUG: sleeping function called from invalid context at mm/slub.c:925
in_atomic(): 0, irqs_disabled(): 1, pid: 1, name: init
Call Trace:
[] show_stack+0x40/0x90
sp=e70b7b40 bsp=e70b12c8
[
Hi All,
I'm hitting an XFS lockdep error with Linus' tree today after the XFS
merge. I wasn't hitting this with v3.13-3995-g0dc3fd0, which seems
to backup the "before XFS merge" claim. Full text below:
[ 132.638044] ==
[ 132.638045] [ INFO:
Cc: Tejun
On 2014/1/24 5:31, David Rientjes wrote:
> On Thu, 23 Jan 2014, Viresh Kumar wrote:
>
>> update_flag() routine uses heap only when spread_flag_changed is true.
>> Otherwise
>> heap isn't used, but is allocated and freed unnecessarily.
>>
but harmless
>> Fix this by allocating heap on
Hi Greg,
After merging the staging tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/staging/rtl8821ae/regd.c: In function '_rtl_reg_apply_beaconing_flags':
drivers/staging/rtl8821ae/regd.c:200:20: error: 'IEEE80211_CHAN_NO_IBSS'
undeclared (first use in this functio
On Thu, Jan 16, 2014 at 04:39:06PM +0100, Jonas Jensen wrote:
> When a skeleton "clocks { .. }" remain in .dtsi, the child node can
> be moved to .dts, "ref12" is then found by of_clk_get().
>
> Signed-off-by: Jonas Jensen
Applied to late/misc branch, will likely be included in 3.14-rc1
-Olof
ia64: validate user arguments in csum_partial_copy_from_user
csum_partial_copy_from_user needs to validate that the argument points to
userspace and not kernelspace (see for example commit
3ddc5b46a8e90f3c9251338b60191d0a804b0d92). Consequently, we need to use
copy_from_user instead of __copy_from
On Tue, Jan 21, 2014 at 04:26:13PM +0100, Jonas Jensen wrote:
> Change DT files to remain coherent with changes in
> accompanying drivers.
>
> 1. replace "sdhci" with "mmc"
> 2. add bus-width property to mmc node
> 3. drop device_type property
> 4. replace "mac@" with "ethernet@"
> 5. replace CONF
[Re: [PATCH 59/73] drivers/gpio: delete non-required instances of include
] On 24/01/2014 (Fri 09:58) Stephen Rothwell wrote:
> Hi Linus,
>
> On Thu, 23 Jan 2014 09:12:43 +0100 Linus Walleij
> wrote:
> >
> > On Tue, Jan 21, 2014 at 10:23 PM, Paul Gortmaker
> > wrote:
> >
> > > None of these
On Fri, 2014-01-24 at 13:05 +1100, Stephen Rothwell wrote:
> Hi James,
>
> Today's linux-next merge of the scsi tree got conflicts in
> drivers/scsi/hpsa.c and drivers/scsi/hpsa.h between commits from Linus'
> tree and commits from the scsi tree.
>
> This has happened because what you submitted t
On 01/23/2014 12:17 PM, Mark Brown wrote:
On Thu, Jan 23, 2014 at 05:47:02PM +0100, Geert Uytterhoeven wrote:
Probably your transfer_one_message() forgot to call
spi_finalize_current_message()? Is this allowed in case of failure?
Probably not, or at least we should be consistent about requirin
On Thursday, January 23, 2014 6:28 PM, Liu Ying wrote:
> On 01/23/2014 01:44 PM, Jingoo Han wrote:
> > On Wednesday, January 22, 2014 6:36 PM, Jani Nikula wrote:
> >> On Mon, 20 Jan 2014, Liu Ying wrote:
> >>> We don't have to turn backlight on/off everytime a blanking
> >>> or unblanking event co
On Thu, Jan 23, 2014 at 08:58:56PM -0500, Josh Boyer wrote:
> Hi All,
>
> I'm hitting an XFS lockdep error with Linus' tree today after the XFS
> merge. I wasn't hitting this with v3.13-3995-g0dc3fd0, which seems
> to backup the "before XFS merge" claim. Full text below:
Ugh. mmap_sem/inode loc
On Fri, Jan 24, 2014 at 01:01:22PM +1100, Stephen Rothwell wrote:
> Hi Greg,
>
> After merging the staging tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/staging/rtl8821ae/regd.c: In function
> '_rtl_reg_apply_beaconing_flags':
> drivers/staging/rtl8821ae/re
From: Kuninori Morimoto
Add support Audio DMAC peri peri driver
for Renesas R-Car Gen2 SoC, using 'shdma-base'
DMA driver framework.
Signed-off-by: Kuninori Morimoto
---
drivers/dma/sh/Kconfig |6 +
drivers/dma/sh/Makefile|1 +
drivers/dm
> > +static struct snd_soc_dapm_widget simple_widgets[] = {
> > + SND_SOC_DAPM_MIC("Mic", NULL),
> > + SND_SOC_DAPM_LINE("Line", NULL),
> > + SND_SOC_DAPM_HP("Hp", NULL),
> > + SND_SOC_DAPM_SPK("Spk", NULL),
> > +};
>
This is the templates for "Microphone XXX", "Line XXX", "Headphone XXX
On Thu, Jan 23, 2014 at 9:29 PM, Dave Chinner wrote:
> On Thu, Jan 23, 2014 at 08:58:56PM -0500, Josh Boyer wrote:
>> Hi All,
>>
>> I'm hitting an XFS lockdep error with Linus' tree today after the XFS
>> merge. I wasn't hitting this with v3.13-3995-g0dc3fd0, which seems
>> to backup the "before
On Thu, Jan 23, 2014 at 09:51:05PM -0500, Josh Boyer wrote:
> On Thu, Jan 23, 2014 at 9:29 PM, Dave Chinner wrote:
> > On Thu, Jan 23, 2014 at 08:58:56PM -0500, Josh Boyer wrote:
> >> the existing dependency chain (in reverse order) is:
> >> [ 132.638078]
> >> -> #1 (&(&ip->i_lock)->mr_lock){
On 24 January 2014 02:53, Andrew Morton wrote:
> On Thu, 23 Jan 2014 15:51:31 +0530 Prabhakar Lad
> wrote:
>
>> Hi Sachin,
>>
>> On Thu, Jan 23, 2014 at 3:38 PM, Sachin Kamat
>> wrote:
>> > Hi Prabhakar,
>> >
>> > On 23 January 2014 15:26, Prabhakar Lad wrote:
>> >> From: "Lad, Prabhakar"
>>
On 01/23/14 at 05:56pm, Peter Zijlstra wrote:
> On Thu, Jan 23, 2014 at 10:10:28AM +0800, Dave Young wrote:
> > Hmm, seems the my physical machine is booting fine with this patch. kvm
> > guest problem still exist, but that kvm thing might be other problem.
>
> Dave, could you try with tip/master,
Hi Linus,
Please pull from the git repository at
git://git.kernel.org/pub/scm/linux/kernel/git/rzhang/linux.git next
to receive Thermal management updates for v3.14-rc1 with
top-most commit c698a4492f01127ca90fc28cd5157f3d616fe4ff:
Merge branch 'misc' of .git into next (2014-01-06 22:48:19
Dave,
On Thursday 23 January 2014 05:49 PM, Dave Hansen wrote:
> Linus's current tree doesn't boot on an 8-node/1TB NUMA system that I
> have. Its reboots are *LONG*, so I haven't fully bisected it, but it's
> down to a just a few commits, most of which are changes to the memblock
> code. Since
On Fri, Jan 24, 2014 at 01:01:22PM +1100, Stephen Rothwell wrote:
> Hi Greg,
>
> After merging the staging tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/staging/rtl8821ae/regd.c: In function
> '_rtl_reg_apply_beaconing_flags':
> drivers/staging/rtl8821ae/re
Hi Greg,
On Thu, 23 Jan 2014 19:53:12 -0800 Greg KH wrote:
>
> On Fri, Jan 24, 2014 at 01:01:22PM +1100, Stephen Rothwell wrote:
> >
> > After merging the staging tree, today's linux-next build (x86_64
> > allmodconfig) failed like this:
> >
> > drivers/staging/rtl8821ae/regd.c: In function
>
On Tue, Jan 21, 2014 at 08:53:07PM -0800, David Rientjes wrote:
> On Thu, 16 Jan 2014, Johannes Weiner wrote:
>
> > > Unfortunately, I think this could potentially be too much of a bonus. On
> > > your same 32GB machine, if a root process is using 18GB and a user
> > > process
> > > is using 1
On Fri, Jan 24, 2014 at 03:04:01PM +1100, Stephen Rothwell wrote:
> Hi Greg,
>
> On Thu, 23 Jan 2014 19:53:12 -0800 Greg KH wrote:
> >
> > On Fri, Jan 24, 2014 at 01:01:22PM +1100, Stephen Rothwell wrote:
> > >
> > > After merging the staging tree, today's linux-next build (x86_64
> > > allmodco
On Thu, Jan 23, 2014 at 03:20:30PM -0800, Guenter Roeck wrote:
> On Thu, Jan 23, 2014 at 11:06:37AM -0800, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 3.12.9 release.
> > There are 27 patches in this series, all will be posted as a response
> > to this one. I
On Thu, Jan 23, 2014 at 03:35:45PM -0800, Guenter Roeck wrote:
> On Thu, Jan 23, 2014 at 10:39:33AM -0800, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 3.10.28 release.
> > There are 23 patches in this series, all will be posted as a response
> > to this one.
On Thu, Jan 23, 2014 at 6:20 PM, Steven Noonan wrote:
> On Thu, Jan 23, 2014 at 11:23:37AM -0500, Elena Ufimtseva wrote:
>> On Wed, Jan 22, 2014 at 3:33 PM, Steven Noonan wrote:
>> > On Wed, Jan 22, 2014 at 03:18:50PM -0500, Elena Ufimtseva wrote:
>> >> On Wed, Jan 22, 2014 at 9:29 AM, Daniel Bor
The generic __native_word() macro defined in include/linux/compiler.h
only allows "int" and "long" data types to be treated as native and
atomic. The x86 architecture, however, allow the use of char and short
data types as atomic as well.
This patch extends the data type allowed in the __native_wo
This patch introduces a new read/write lock implementation that put
waiting readers and writers into a queue instead of actively contending
the lock like the current read/write lock implementation. This will
improve performance in highly contended situation by reducing the
cache line bouncing effec
There is a pending MCS lock patch series that adds generic MCS lock
helper functions to do MCS-style locking. This patch will enable
the queue rwlock to use that generic MCS lock/unlock primitives for
internal queuing. This patch should only be merged after the merging
of that generic MCS locking p
v10->v11:
- Insert appropriate smp_mb__{before,after}_atomic_* calls to make sure
that the lock and unlock functions provide the proper memory barrier.
v9->v10:
- Eliminate the temporary smp_load_acquire()/smp_store_release() macros
by merging v9 patch 4 into patch 1.
- Include & remove
This patch makes the necessary changes at the x86 architecture specific
layer to enable the presence of the CONFIG_QUEUE_RWLOCK kernel option
to replace the read/write lock by the queue read/write lock.
It also enables the CONFIG_QUEUE_RWLOCK option by default for x86 which
will force the use of q
Hi all,
There will be no tree on Monday (26/1) as it is a public holiday.
Please do *not* add material destined for v3.15 to your linux-next
included trees until after v3.14-rc1 is released.
This tree fails (more than usual) the powerpc allyesconfig build.
Changes since 20140123:
Dropped
On 24 January 2014 07:28, Li Zefan wrote:
>> Acked-by: David Rientjes
>
> Acked-by: Li Zefan
Thanks..
> I would like this patch be picked up by Tejun. I'll send out a patchset
> for cpuset which may have confliction with this one.
Its already applied by Andrew Morton..
--
To unsubscribe from
On 23 January 2014 20:28, Frederic Weisbecker wrote:
> On Tue, Jan 21, 2014 at 04:03:53PM +0530, Viresh Kumar wrote:
>> So, the main problem in my case was caused by this:
>>
>><...>-2147 [001] d..2 302.573881: hrtimer_start:
>> hrtimer=c172aa50 function=tick_sched_timer expires=60
On 01/23/2014 08:11 PM, Greg Kroah-Hartman wrote:
On Thu, Jan 23, 2014 at 03:20:30PM -0800, Guenter Roeck wrote:
On Thu, Jan 23, 2014 at 11:06:37AM -0800, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.12.9 release.
There are 27 patches in this series, all will
CR_MAXSIZE needs to account for an llog_changelog_rec that actually
contains a changelog_ext_rec structure rather than a changelog_rec.
With out doing so, a file size approaching the Linux kernel NAME_MAX
length that is renamed to a size also close to, or at, NAME_MAX will
exceed CR_MAXSIZE and tri
Call to ksocknal_launch_packet might schedule a callback that
might free the just sent message, and so subsequent access to it
via lntmsg->msg_vmflush goes to freed memory.
Instead we'll just remember if we are in the vmflush thread and
only restore if we happened to set mempressure flag.
Signed-
The kernel to userspace communication routines (KUC) allocate
and limit the maximum cs_buf size to CR_MAXSIZE. However this
fails to account for the fact that the buffer is assumed to begin
with a struct kuc_hdr. To allocate and account for that space,
we introduce a new define, KUC_CHANGELOG_MSG
I just deployed a mainline lustre client in my test system.
These patches below are for stuff that causes crashes or other issues
in my (so far) very basic sanity testing (more to come).
The patches mostly originate from our main tree, but I decided to
prioritize these as they disrupt my testing,
Recent commit 175f5475fb9c5800319da4e3c4204413d7280f5c
introduced this compile warning (because vaddr is unsigned long),
so add a cast:
drivers/staging/lustre/lnet/klnds/o2iblnd/o2iblnd_cb.c: In function
‘kiblnd_kvaddr_to_page’:
drivers/staging/lustre/lnet/klnds/o2iblnd/o2iblnd_cb.c:532:2: warning
Signed-off-by: Oleg Drokin
---
drivers/staging/lustre/TODO | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/lustre/TODO b/drivers/staging/lustre/TODO
index 22742d6..0a2b6cb 100644
--- a/drivers/staging/lustre/TODO
+++ b/drivers/staging/lustre/TODO
@@ -9,5 +
Add a MAINTAINERS entry too?
---
MAINTAINERS | 8
1 file changed, 8 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 5c5d554..9ca5de8 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -8284,6 +8284,14 @@ W: http://www.lirc.org/
S: Odd Fixes
F: drivers/staging/media/
Hi,
Russell King - ARM Linux wrote:
> On Thu, Jan 23, 2014 at 04:53:50PM +, Russell King - ARM Linux wrote:
> > On Thu, Jan 23, 2014 at 12:04:44PM +0100, Sascha Hauer wrote:
> > > On Thu, Jan 23, 2014 at 11:56:32AM +0100, Lothar Waßmann wrote:
> > > > Hi,
> > > >
> > > > Sascha Hauer wrote:
>
On Thu, Jan 23, 2014 at 09:23:44PM +, Zoltan Kiss wrote:
> The grant mapping API does m2p_override unnecessarily: only gntdev needs it,
> for blkback and future netback patches it just cause a lock contention, as
> those pages never go to userspace. Therefore this series does the following:
> -
Hello!
> +STAGING - LUSTRE
> +M: Andreas Dilger
> +M: Oleg Drokin
> +M: Peng Tao .
> +L: hpdd-discuss
> +S: Odd Fixes
Actually we are at least Maintained here, if not outright Supported.
Bye,
Oleg
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the
On Thu, Jan 23, 2014 at 2:49 PM, Dave Hansen wrote:
> Linus's current tree doesn't boot on an 8-node/1TB NUMA system that I
> have. Its reboots are *LONG*, so I haven't fully bisected it, but it's
> down to a just a few commits, most of which are changes to the memblock
> code. Since the panic i
This patch bypass the timer_irq_works() check for hyperv guest since:
- It was guaranteed to work.
- timer_irq_works() may fail sometime due to the lpj calibration were inaccurate
in a hyperv guest or a buggy host.
In the future, we should get the tsc frequency from hypervisor and use preset
lp
On Thu, Jan 23, 2014 at 9:55 PM, Mikulas Patocka wrote:
>> BTW, good to see you still have a working TGA. My PPC and Alpha gear
>> died a decade ago.
>
> With the patches that I sent, I can switch it to 1920x1080 and let it
> drive my monitor in native resolution. I was wondering how such an old
>
We don't have to update the state and fb_blank properties of
a backlight device every time a blanking or unblanking event
comes because they may have already been what we want. Another
thought is that one backlight device may be shared by multiple
framebuffers. The backlight driver should take the
We don't have to turn backlight on/off every time a blanking
or unblanking event comes because the backlight status may
have already been what we want. Another thought is that one
backlight device may be shared by multiple framebuffers. We
don't hope blanking one of the framebuffers may turn the
ba
We don't have to update a backlight status every time a
blanking or unblanking event comes because the backlight
status may have already been what we want. Another thought
is that one backlight device may be shared by multiple
framebuffers. We don't hope blanking one of the framebuffers
may turn th
On 14/01/23, Peter Zijlstra wrote:
> On Thu, Jan 23, 2014 at 02:32:33PM -0500, Richard Guy Briggs wrote:
> > These are a number of patches inspired by ebiederman's container work that
> > were
> > included by me 2013-08-20 as the patchset:
> > RFC: steps to make audit pid namespace-safe
> >
>
Yinghai,
On Friday 24 January 2014 12:55 AM, Yinghai Lu wrote:
> On Thu, Jan 23, 2014 at 2:49 PM, Dave Hansen wrote:
>> > Linus's current tree doesn't boot on an 8-node/1TB NUMA system that I
>> > have. Its reboots are *LONG*, so I haven't fully bisected it, but it's
>> > down to a just a few co
Hi Andrew
On Fri, Jan 24, 2014 at 2:49 AM, Andrew Morton
wrote:
> On Thu, 23 Jan 2014 20:27:29 +0400 (MSK) malc wrote:
>
>> Sep 17 00:00:00 2001
>> From: Vladimir Murzin
>> Date: Thu, 23 Jan 2014 14:54:20 +0400
>> Subject: [PATCH] Revert "mm/vmalloc: interchage the implementation of
>> vmalloc
On Friday 24 January 2014 01:38 AM, Santosh Shilimkar wrote:
> Yinghai,
>
> On Friday 24 January 2014 12:55 AM, Yinghai Lu wrote:
>> On Thu, Jan 23, 2014 at 2:49 PM, Dave Hansen wrote:
Linus's current tree doesn't boot on an 8-node/1TB NUMA system that I
have. Its reboots are *LONG*, s
On Thu, Jan 23, 2014 at 10:38 PM, Santosh Shilimkar
wrote:
> Yinghai,
>
> On Friday 24 January 2014 12:55 AM, Yinghai Lu wrote:
>> On Thu, Jan 23, 2014 at 2:49 PM, Dave Hansen wrote:
>>> > Linus's current tree doesn't boot on an 8-node/1TB NUMA system that I
>>> > have. Its reboots are *LONG*, s
Hi Thomas,
The below patch works pretty much as is. I tried this out with deep idle
states on our system. Looking through the code and analysing corner
cases also did not bring out any issues to me. I will send out a patch
V2 of this.
Regards
Preeti U Murthy
On 01/22/2014 06:57 PM, Thomas Gleixn
On Thu, 23 Jan 2014 22:57:08 -0800 Yinghai Lu wrote:
> On Thu, Jan 23, 2014 at 10:38 PM, Santosh Shilimkar
> wrote:
> > Yinghai,
> >
> > On Friday 24 January 2014 12:55 AM, Yinghai Lu wrote:
> >> On Thu, Jan 23, 2014 at 2:49 PM, Dave Hansen wrote:
> >>> > Linus's current tree doesn't boot on an
This earlier version of this patchset can be found here:
https://lkml.org/lkml/2013/12/12/687. This version has been based on the
discussion in http://www.kernelhub.org/?p=2&msg=399516.
This patchset provides the hooks that the architectures without an external
clock device and deep idle states wh
From: Thomas Gleixner
On some architectures, in certain CPU deep idle states the local timers stop.
An external clock device is used to wakeup these CPUs. The kernel support for
the
wakeup of these CPUs is provided by the tick broadcast framework by using the
external clock device as the wakeup
The broadcast framework can potentially be made use of by archs which do not
have an
external clock device as well. Then, it is required that one of the CPUs need
to handle the broadcasting of wakeup IPIs to the CPUs in deep idle. As a
result its local timers should remain functional all the time.
On Thu, Jan 23, 2014 at 10:56 PM, Santosh Shilimkar
wrote:
> On Friday 24 January 2014 01:38 AM, Santosh Shilimkar wrote:
> The patch which is now commit 457ff1d {lib/swiotlb.c: use
> memblock apis for early memory allocations} was the breaking the
> boot on Andrew's machine. Now if I look back t
N�Р骒r��yb�X�肚�v�^�)藓{.n�+�伐�{��赙zXФ�≤�}��财�z�&j:+v�����赙zZ+��+zf＂�h���~i���z� �wア�?�ㄨ��&�)撷f��^j谦y�m��@A�a囤�
0鹅h���i
On Friday 24 January 2014 02:04 AM, Yinghai Lu wrote:
> On Thu, Jan 23, 2014 at 10:56 PM, Santosh Shilimkar
> wrote:
>> On Friday 24 January 2014 01:38 AM, Santosh Shilimkar wrote:
>
>> The patch which is now commit 457ff1d {lib/swiotlb.c: use
>> memblock apis for early memory allocations} was th
On Fri, 24 Jan 2014, Jan Kara wrote:
> Strange. I've installed systemd system (openSUSE 13.1) and it boots
> with the latest Linus' kernel just fine (and I have at least FANOTIFY
> and SLAB debugging set the same way as you). But it was only a KVM
> guest. I'll try tomorrow with a physical ma
> Subject: Re: [PATCH Resend 3/8] ASoC: simple-card: simplify the daifmt code
>
> On Thu, Jan 23, 2014 at 01:02:45PM +0800, Xiubo Li wrote:
> > In the asoc_simple_card_parse_of() will parse the device node's CPU/CODEC
> > DAI commone fmts, and then in asoc_simple_card_sub_parse_of() will parse
>
Any more comments for this idea? :)
On 01/22/2014 03:40 PM, Alex Shi wrote:
> On 01/21/2014 10:57 PM, Peter Zijlstra wrote:
>> On Tue, Jan 21, 2014 at 10:04:26PM +0800, Alex Shi wrote:
>>>
>>> Current scheduler load balance is bottom-up mode, each CPU need
>>> initiate the balance by self.
>>>
>>
Hi Morimoto-san,
On Fri, Jan 24, 2014 at 3:32 AM, Kuninori Morimoto
wrote:
> --- a/drivers/dma/sh/Kconfig
> +++ b/drivers/dma/sh/Kconfig
> @@ -29,6 +29,12 @@ config RCAR_HPB_DMAE
> help
> Enable support for the Renesas R-Car series DMA controllers.
>
> +config RCAR_AUDMAC_PP
> +
On Fri, Jan 24, 2014 at 06:42:54AM +0100, Lothar Waßmann wrote:
> Hi,
>
> > Okay, this works, but there's a problem with pwm-leds.
> >
> > When the duty cycle is set to zero (when you set the brightness to zero)
> > pwm-leds decides to disable the PWM after configuring it. This causes
> > the PW
On Thu, Jan 23, 2014 at 11:22 PM, Santosh Shilimkar
wrote:
> On Friday 24 January 2014 02:04 AM, Yinghai Lu wrote:
>> On Thu, Jan 23, 2014 at 10:56 PM, Santosh Shilimkar
>> wrote:
>>> On Friday 24 January 2014 01:38 AM, Santosh Shilimkar wrote:
>>
>>> The patch which is now commit 457ff1d {lib/sw
> Subject: Re: [alsa-devel] [PATCH] ASoC: simple-card: fix simple card widgets
> routing property name usage
>
> On Thu, Jan 23, 2014 at 11:00:16AM +, li.xi...@freescale.com wrote:
> > Hi,
> >
> > I'd like to know the status about this patch.
>
> Please send upstream mail to kernel.org if yo
Before we had the PWM framework we used to have a barebone PWM api. The
HAVE_PWM Kconfig symbol used to be selected by the PWM drivers to specify
the PWM API is present in the kernel. Since the last legacy driver is gone
the HAVE_PWM symbol can go aswell.
Signed-off-by: Sascha Hauer
Cc: Dmitry To
On Friday 24 January 2014 02:46 AM, Yinghai Lu wrote:
>> OK. So we need '__alloc_bootmem_low()' equivalent memblock API. We will try
>> > to come up with a patch for the same. Thanks for inputs.
> Yes,
>
> Andrew, can you try attached two patches in your setup?
>
> Assume your system does not hav
* Dave Young wrote:
> On 01/23/14 at 05:56pm, Peter Zijlstra wrote:
> > On Thu, Jan 23, 2014 at 10:10:28AM +0800, Dave Young wrote:
> > > Hmm, seems the my physical machine is booting fine with this patch. kvm
> > > guest problem still exist, but that kvm thing might be other problem.
> >
> > D
601 - 691 of 691 matches
Mail list logo
