On Thu, Feb 21, 2013 at 7:15 PM, sjur.brandel...@stericsson.com wrote:
From: Sjur Brændeland sjur.brandel...@stericsson.com
This patch-set adds support for shared resource table between
Linux kernel and remote devices.
- dynamically-allocated address of the vrings can be communicated
- vdev
On Thu, Apr 04, 2013 at 03:30:01PM -0600, Stephen Warren wrote:
On 04/04/2013 03:28 PM, Stephen Warren wrote:
On 04/03/2013 08:45 AM, Thierry Reding wrote:
Move the PCIe driver from arch/arm/mach-tegra into the drivers/pci/host
directory. The motivation is to collect various host controller
On Thu, Apr 04, 2013 at 11:21:46PM -0500, Nishanth Menon wrote:
Nishanth Menon (2):
regulator: core: return err value for regulator_get if there is no DT
binding
cpufreq: cpufreq-cpu0: defer probe when regulator is not ready
For both,
Acked-by: Shawn Guo shawn@linaro.org
--
To
Hi Ohad,
On Fri, Mar 15, 2013 at 10:29 AM, Erwan Yvin erwan.y...@stericsson.com wrote:
From: Erwan Yvin erwan.y...@stericsson.com
Implement the vringh callback functions in order
to manage host virtio rings and handle kicks.
This allows virtio device to request host-virtio-rings.
Hi Li,
On Thu, Feb 28, 2013 at 10:02 AM, Li Fei fei...@intel.com wrote:
Even in failed case of pm_runtime_get_sync, the usage_count
is incremented. In order to keep the usage_count with correct
value and runtime power management to behave correctly, call
pm_runtime_put(_sync) in such case.
Hi Sjur,
On Fri, Apr 5, 2013 at 9:15 AM, Sjur Brændeland sjurb...@gmail.com wrote:
Any chance that you could review this in time for 3.10 merge window?
Sure, I'm getting to this early next week. Monday at the latest.
Thanks,
Ohad.
--
To unsubscribe from this list: send the line unsubscribe
Hi Michal,
On 03/21/2013 04:19 PM, Michal Hocko wrote:
On Thu 21-03-13 10:33:07, Simon Jeons wrote:
Hi Mel,
On 03/21/2013 02:19 AM, Mel Gorman wrote:
The following problem was reported against a distribution kernel when
zone_reclaim was enabled but the same problem applies to the mainline
On Tue, Apr 02, 2013 at 09:02:02AM +, Zhanghaoyu (A) wrote:
I start a kvm VM with vnc(using the zrle protocol) connect, sometimes qemu
program crashed during starting period, received signal SIGABRT.
Trying about 20 times, this crash may be reproduced.
I guess the cause memory corruption
Dear Alexandre Pereira da Silva,
Some boards and card slots doesn't have card detect feature available.
In that case allow to mark the cards as non-removable, via devicetree.
Signed-off-by: Alexandre Pereira da Silva aletes@gmail.com
Looks good,
Reviewed-by: Marek Vasut ma...@denx.de
Dear Alexandre Pereira da Silva,
The imx23-olinuxino sdcard doesn't support card detect.
Signed-off-by: Alexandre Pereira da Silva aletes@gmail.com
---
arch/arm/boot/dts/imx23-olinuxino.dts |1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/boot/dts/imx23-olinuxino.dts
On Fri, Mar 29, 2013 at 12:34 AM, Robert Tivy rt...@ti.com wrote:
rproc_alloc_vring() was modified to call idr_alloc() instead of
idr_get_new(), but the return value was still handled as before.
Signed-off-by: Robert Tivy rt...@ti.com
Thanks Rob. This was submitted by Suman some time ago and
On 4 April 2013 18:24, Viresh Kumar viresh.ku...@linaro.org wrote:
This patch moves cpufreq driver of powerpc platform to drivers/cpufreq.
Cc: Benjamin Herrenschmidt b...@kernel.crashing.org
Cc: Paul Mackerras pau...@samba.org
Cc: Olof Johansson o...@lixom.net
Cc:
* Andi Kleen a...@firstfloor.org wrote:
This is based on v7 of the full Haswell PMU support,
This series looks mostly good - I've got two requests:
- please rename intx - in_tx, INTX - IN_TX, as 'intx' is confusing
- please port to the latest tip:master (or perf/core), as the underlying
Hi Minchan,
On 04/03/2013 09:11 AM, Minchan Kim wrote:
On Tue, Apr 02, 2013 at 03:15:23PM -0700, Hugh Dickins wrote:
On Tue, 2 Apr 2013, Kirill A. Shutemov wrote:
Kirill A. Shutemov wrote:
From: Kirill A. Shutemov kirill.shute...@linux.intel.com
ramfs is the most simple fs from page cache
Viresh Kumar wrote:
This patch moves cpufreq driver of Samsung's ARM based s3c24xx platform to
drivers/cpufreq.
Cc: Ben Dooks ben-li...@fluff.org
Cc: Kukjin Kim kgene@samsung.com
Cc: linux-samsung-...@vger.kernel.org
Cc: linux-arm-ker...@lists.infradead.org
Signed-off-by: Viresh
On 5 April 2013 10:19, Viresh Kumar viresh.ku...@linaro.org wrote:
For the latest versions sent by you (including {get|put}_online_cpus()):
Acked-by: Viresh Kumar viresh.ku...@linaro.org
Hi Rafael,
I see that you have applied this patchset to bleeding-edge, but in
wrong order. You have
Stephen Rothwell wrote:
Hi Kukjin,
Hi,
Today's linux-next merge of the samsung tree got a conflict in
drivers/irqchip/irq-s3c24xx.c between commit de88cbb7b244 (arm: Move
chained_irq_(enter|exit) to a generic file) from the arm-soc tree (where
it is called arch/arm/mach-s3c24xx/irq.c)
Hi all,
After upgrading to the latest stable kernel I found my x230 (with the
latest, v2.52 BIOS) no longer boots.
Using an EFI only boot scheme with gummiboot v29, I get a blank
backlit screen when attempting to boot up my distro. There isn't any
indication from the hard drive it has attempted
Hi,
On 2013-03-29 03:40, Jingoo Han wrote:
VESA_DMT_VSYNC_HIGH should be used instead of VESA_DMT_HSYNC_HIGH,
because FB_SYNC_VERT_HIGH_ACT is related to vsync, not to hsync.
Signed-off-by: Jingoo Han jg1@samsung.com
Cc: Steffen Trumtrar s.trumt...@pengutronix.de
Cc: Tomi Valkeinen
* Julien Tinnes j...@google.com wrote:
On Thu, Apr 4, 2013 at 1:27 PM, H. Peter Anvin h...@zytor.com wrote:
On 04/04/2013 01:23 PM, Julien Tinnes wrote:
On Thu, Apr 4, 2013 at 1:19 PM, Julien Tinnes j...@google.com wrote:
On Thu, Apr 4, 2013 at 1:12 PM, H. Peter Anvin h...@zytor.com
Hi guys,
Added some folks to CC, blame scripts/get_maintainer.pl.
Comment below ..
On Tue, Apr 02, 2013 at 02:22:05PM -0700, Nishanth Aravamudan wrote:
From: Michael Neuling michael.neul...@au1.ibm.com
We are currently out of free bits in AT_HWCAP. With POWER8, we have
several hardware
On 5 April 2013 12:18, Kukjin Kim kgene@samsung.com wrote:
Basically, this moving looks good to me, but should be re-worked based on
for-next of samsung tree because this touches too many samsung stuff so this
should be sent to upstream via samsung tree.
Hmm... Its already applied in
Hi Kevin,
On Wednesday 03 April 2013 11:18 PM, Kevin Hilman wrote:
Sourav Poddarsourav.pod...@ti.com writes:
Hi Kevin,
On Wednesday 20 March 2013 05:36 PM, Sourav Poddar wrote:
Realised the list to whom the patch was send got dropped. Ccing
them all..
On Wednesday 20 March 2013 05:18 PM,
* Kees Cook keesc...@chromium.org wrote:
This creates CONFIG_RANDOMIZE_BASE, so that the base offset of the kernel
can be randomized at boot.
This makes kernel vulnerabilities harder to reliably exploit, especially
from remote attacks and local processes in seccomp containers. Keeping
the
* Kees Cook keesc...@chromium.org wrote:
Add logic for 64-bit kernel relocations. Since there is no need to
handle 32 and 64 bit at the same time, refactor away most of the 32/64
bit ELF differences and split the build into producing two separate
binaries. Additionally switches to using
On Friday 05 April 2013 12:38 PM, Sourav Poddar wrote:
Hi Kevin,
On Wednesday 03 April 2013 11:18 PM, Kevin Hilman wrote:
Sourav Poddarsourav.pod...@ti.com writes:
Hi Kevin,
On Wednesday 20 March 2013 05:36 PM, Sourav Poddar wrote:
Realised the list to whom the patch was send got dropped.
On 03/19/2013 10:16 PM, Sebastian Andrzej Siewior wrote:
DEFINE_SRCU() and DEFINE_STATIC_SRCU() does the same thing except for
the static attribute. This patch moves the common pieces into
_DEFINE_SRCU() which is used by the the former macros either adding the
static attribute or not.
On 03/19/2013 10:16 PM, Sebastian Andrzej Siewior wrote:
There are macros for static initializer for the three out of four
possible notifier types, that are:
ATOMIC_NOTIFIER_HEAD()
BLOCKING_NOTIFIER_HEAD()
RAW_NOTIFIER_HEAD()
This patch provides a static initilizer for
On 04/05/2013 01:51 AM, Julian Calaby wrote:
Hi Wang,
On Fri, Apr 5, 2013 at 3:01 AM, Wang YanQing udkni...@gmail.com wrote:
Current we can only enable lib80211 by enable a driver
in tree use it which will select it, but some out tree's
drivers also use it, so I think it has sense to make
* Kees Cook keesc...@chromium.org wrote:
This provides routines for selecting a randomized kernel base offset,
bounded by e820 details. It tries to use RDRAND and falls back to RDTSC.
If noaslr is on the kernel command line, no offset will be used.
Would it make sense to also add three
On 04/05/2013 06:01 AM, Randy Dunlap wrote:
On 04/04/13 16:51, Julian Calaby wrote:
Hi Wang,
On Fri, Apr 5, 2013 at 3:01 AM, Wang YanQing udkni...@gmail.com wrote:
Current we can only enable lib80211 by enable a driver
in tree use it which will select it, but some out tree's
drivers also use
On 04/04/2013 09:03 PM, Eric Valette wrote:
I fixed this already.
https://git.kernel.org/cgit/linux/kernel/git/jgarzik/libata-dev.git/commit/?h=upstream-fixesid=8e725c7f8a60feaa88edacd4dee2c754d5ae7706
Thanks for the support. I will apply the patch manually and wait for 3.8.6
Just to
[Ping]
Hi, Eric Paris
Could you review this patch?
Thanks,
Lai
On 03/16/2013 12:50 AM, Lai Jiangshan wrote:
fsnotify implements its own call_srcu() by:
dedicated thread + synchronize_srcu()
But srcu provides call_srcu() now, so we should convert them to use
existed call_srcu() and
* Kees Cook keesc...@chromium.org wrote:
+config RANDOMIZE_BASE_MAX_OFFSET
+ hex Maximum ASLR offset allowed
+ depends on RANDOMIZE_BASE
+ default 0x1000
+ range 0x0 0x1000
+ ---help---
+ Determines the maximal offset in bytes that will be applied to the
On 04/04/2013 10:55 PM, Tejun Heo wrote:
From 5c529597e922c26910fe49b8d5f93aeaca9a2415 Mon Sep 17 00:00:00 2001
From: Lai Jiangshan la...@cn.fujitsu.com
Date: Thu, 4 Apr 2013 10:05:38 +0800
destroy_workqueue() performs several sanity checks before proceeding
with destruction of a workqueue.
* Ingo Molnar mi...@kernel.org wrote:
* Kees Cook keesc...@chromium.org wrote:
This provides routines for selecting a randomized kernel base offset,
bounded by e820 details. It tries to use RDRAND and falls back to RDTSC.
If noaslr is on the kernel command line, no offset will be
On Thu, Apr 04, 2013 at 03:28:54PM -0600, Stephen Warren wrote:
[...]
diff --git a/Documentation/devicetree/bindings/pci/nvidia,tegra20-pcie.txt
b/Documentation/devicetree/bindings/pci/nvidia,tegra20-pcie.txt
+Required properties:
+- interrupts: the interrupt outputs of the controller
Linus,
please pull sound fixes for v3.9-rc6 from:
git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git for-linus
The topmost commit is fed61fb5275cf1fa4915d6415b4e376c87089d83
Sound fixes for 3.9-rc6
This contains
Donn Washburn wrote:
I am not on the list
Indeed you are not on the alsa-devel list.
It works some times
What works? And why would that be a problem?
Regards,
Clemens
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to
On 01/19/2013 03:23 AM, Craig Hada wrote:
This patch sets the coherent DMA mask to 64-bit after the be2net driver
has been acknowledged that the system is 64-bit DMA capable. The coherent
DMA mask is examined by the Intel IOMMU driver to determine whether to
allow pass through context mapping
For reference, here's the new binding document with all your comments
addressed (I think).
Thierry
NVIDIA Tegra PCIe controller
Required properties:
- compatible: nvidia,tegra20-pcie
- device_type: Must be pci
- reg: A list of physical base address and length for each set of controller
On 04/03/2013 07:06 PM, Doug Anderson wrote:
Lars,
On Sat, Mar 16, 2013 at 7:41 AM, Lars-Peter Clausen l...@metafoo.de wrote:
I think you still need the mutex for serialization, otherwise the requests
would just cancel each other out. Btw. what happens if you start a conversion
while
Hi John,
On Thu, Apr 04, 2013 at 10:37:52AM -0700, John Stultz wrote:
On 04/03/2013 11:55 PM, Minchan Kim wrote:
On Wed, Apr 03, 2013 at 04:52:19PM -0700, John Stultz wrote:
Next we introduce a parallel fvrange() syscall for creating
volatile ranges directly against files.
Okay. It seems you
* Eric Northup digitale...@google.com wrote:
On Thu, Apr 4, 2013 at 1:58 PM, H. Peter Anvin h...@zytor.com wrote:
It seems to me that you are assuming that the attacker is targeting a
specific system, but a bot might as well target 256 different systems and
see what sticks...
The
Hi. Max.
I have a question.
Your mmc host driver set to host-max_discard_to by some value instead
of not zero ?
Thanks.
2013/4/5, Max Filippov jcmvb...@gmail.com:
On Fri, Apr 5, 2013 at 5:53 AM, Shaohua Li s...@kernel.org wrote:
On Thu, Apr 04, 2013 at 06:00:18AM +0400, Max Filippov wrote:
Il 04/04/2013 12:27, Michael S. Tsirkin ha scritto:
PIO and MMIO are separate address spaces, but
ioeventfd registration code mistakenly detected
two eventfds as duplicate if they use the same address,
even if one is PIO and another one MMIO.
Signed-off-by: Michael S. Tsirkin
On Fri, Apr 05, 2013 at 02:47:25PM +0800, Simon Jeons wrote:
Hi Minchan,
On 04/03/2013 09:11 AM, Minchan Kim wrote:
On Tue, Apr 02, 2013 at 03:15:23PM -0700, Hugh Dickins wrote:
On Tue, 2 Apr 2013, Kirill A. Shutemov wrote:
Kirill A. Shutemov wrote:
From: Kirill A. Shutemov
On Friday, April 05, 2013 3:57 PM, Tomi Valkeinen wrote:
Hi,
On 2013-03-29 03:40, Jingoo Han wrote:
VESA_DMT_VSYNC_HIGH should be used instead of VESA_DMT_HSYNC_HIGH,
because FB_SYNC_VERT_HIGH_ACT is related to vsync, not to hsync.
Signed-off-by: Jingoo Han jg1@samsung.com
Cc:
* H. Peter Anvin h...@zytor.com wrote:
I have to admit to being somewhat skeptical toward KASLR with only 8
bits of randomness. There are at least two potential ways of
dramatically increasing the available randomness:
1. actually compose the kernel of multiple independently relocatable
On 04/04/2013 06:21 PM, Oskar Andero wrote:
Some blackpoints are only valid for specific architectures. To let each
architecture specify its own blackpoints the list has been split in two
lists: common and arch. The common list is kept in kernel/kprobes.c and
the arch list is kept in the arch/
On 04/03/2013 07:29 PM, Michal Hocko wrote:
On Wed 03-04-13 16:58:48, Glauber Costa wrote:
On 04/03/2013 01:11 PM, Li Zefan wrote:
Use css_get/css_put instead of mem_cgroup_get/put.
Note, if at the same time someone is moving @current to a different
cgroup and removing the old cgroup,
On Fri 05-04-13 09:14:58, Simon Jeons wrote:
Hi Michal,
On 03/22/2013 04:15 PM, Michal Hocko wrote:
[getting off-list]
On Fri 22-03-13 07:46:32, Simon Jeons wrote:
Hi Michal,
On 03/21/2013 08:56 PM, Michal Hocko wrote:
On Thu 21-03-13 07:49:48, Simon Jeons wrote:
[...]
When I hacking
On 04/04/2013 07:22 PM, Tejun Heo wrote:
On Thu, Apr 04, 2013 at 05:20:28PM +0200, Michal Hocko wrote:
But what harm does an additional reference do?
No harm at all. I just wanted to be sure that this is not yet another
for memcg hack. So if this is useful for other controllers then I have
On Fri 05-04-13 07:41:23, Wanpeng Li wrote:
On Thu, Apr 04, 2013 at 06:17:46PM +0200, Michal Hocko wrote:
On Thu 04-04-13 17:09:08, Wanpeng Li wrote:
order = MAX_ORDER pages are only allocated at boot stage using the
bootmem allocator with the hugepages=xxx option. These pages are never
Now, memory barrier in __do_huge_pmd_anonymous_page doesn't work.
Because lru_cache_add_lru uses pagevec so it could miss spinlock
easily so above rule was broken so user might see inconsistent data.
I was not first person who pointed out the problem. Mel and Peter
pointed out a few months ago
Hi Doug,
You're right..it's something wrong.
Actually i didn't test with your patch, but your commit message is reasonable.
I will check until next week after test.
Best Regards,
Jaehoon Chung
On 03/27/2013 03:06 AM, Doug Anderson wrote:
Jaehoon,
On Mon, Mar 18, 2013 at 3:21 AM, Jaehoon
On Thu, Apr 4, 2013 at 11:27 AM, Adrian Chadd adr...@freebsd.org wrote:
Hi,
Here's my first take on the version number policy:
https://github.com/qca/open-ath9k-htc-firmware/wiki/VersionPolicy
The summary:
* major version number changes are for firmware API / behaviour
changes that
(2013/04/05 11:39), Namhyung Kim wrote:
From: Namhyung Kim namhyung@lge.com
Some of kernel functions are not allowed to be used by kprobes for
some reason, so they're marked as __kprobe on the source code and
reside on .kprobes.text section.
However normal users which only see
On 5 April 2013 01:19, Luis R. Rodriguez mcg...@do-not-panic.com wrote:
This is better than anything we had drafted before for 802.11 open
firmware design rules. Cc'ing a few lists for wider review given that
what we had written before for rules was for 802.11 and Bluetooth [0]
and it was
From: Ivan Vecera ivec...@redhat.com
Date: Fri, 05 Apr 2013 09:51:24 +0200
Dave, I'd like to ask when do you plan to apply this patch?
I'm waiting for the be2net driver maintainers to integrate it and
resend it to me, they're usually very good about that.
--
To unsubscribe from this list: send
Hi Roger,
On 03/20/2013 04:44 PM, Roger Quadros wrote:
Hi Tony,
These patches provide the SoC side code required to support
the changes in the OMAP USB Host drivers done in [1], [2] [3].
Device tree support is added for Beagleboard only. I've removed
Panda device tree support till we
Hi Wanpeng,
On Fri, Apr 05, 2013 at 04:22:17PM +0800, Wanpeng Li wrote:
On Fri, Apr 05, 2013 at 05:01:06PM +0900, Minchan Kim wrote:
On Fri, Apr 05, 2013 at 02:47:25PM +0800, Simon Jeons wrote:
Hi Minchan,
On 04/03/2013 09:11 AM, Minchan Kim wrote:
On Tue, Apr 02, 2013 at 03:15:23PM
-Original Message-
From: David Miller [mailto:da...@davemloft.net]
From: Ivan Vecera ivec...@redhat.com
Date: Fri, 05 Apr 2013 09:51:24 +0200
Dave, I'd like to ask when do you plan to apply this patch?
I'm waiting for the be2net driver maintainers to integrate it and resend it
On 04/02/2013 11:23 AM, Roger Quadros wrote:
+ Paul
On 03/26/2013 12:23 PM, Roger Quadros wrote:
Register a device tree clock provider for the clocks
on the OMAP4 SoC. Also provide the binding information.
For now we only provide AUXCLKs.
NOTE: this patch depends on
From: KOSAKI Motohiro kosaki.motoh...@jp.fujitsu.com
Currently glibc rt/cpuclock2 test(*) sporadically fail. The
pseudo test code is here.
t0 = clock_gettime()
abs = t0 + sleeptime;
clock_nanosleep(TIMER_ABSTIME, abs)
t1 = clock_gettime()
assert(t1-t0 sleeptime)
assert(t1 abs)
Because
On 11:47-20130405, Roger Quadros wrote:
On 04/02/2013 11:23 AM, Roger Quadros wrote:
+ Paul
On 03/26/2013 12:23 PM, Roger Quadros wrote:
Register a device tree clock provider for the clocks
on the OMAP4 SoC. Also provide the binding information.
For now we only provide AUXCLKs
On 04/05/2013 11:48 AM, Nishanth Menon wrote:
On 11:47-20130405, Roger Quadros wrote:
On 04/02/2013 11:23 AM, Roger Quadros wrote:
+ Paul
On 03/26/2013 12:23 PM, Roger Quadros wrote:
Register a device tree clock provider for the clocks
on the OMAP4 SoC. Also provide the binding information
Hi Michal,
On 04/05/2013 04:12 PM, Michal Hocko wrote:
On Fri 05-04-13 07:41:23, Wanpeng Li wrote:
On Thu, Apr 04, 2013 at 06:17:46PM +0200, Michal Hocko wrote:
On Thu 04-04-13 17:09:08, Wanpeng Li wrote:
order = MAX_ORDER pages are only allocated at boot stage using the
bootmem allocator
On 03/28/2013 10:22 AM, Wanlong Gao wrote:
On 03/23/2013 07:28 PM, Wanlong Gao wrote:
This series implements virtio-scsi queue steering, which gives
performance improvements of up to 50% (measured both with QEMU and
tcm_vhost backends).
This version rebased on Rusty's virtio ring rework
On 18:33 Thu 04 Apr , Dmitry Torokhov wrote:
Hi Oskar,
On Thu, Mar 07, 2013 at 03:01:22PM +0100, oskar.and...@sonymobile.com wrote:
From: Aleksej Makarov aleksej.maka...@sonymobile.com
When waking up the platform by pressing a specific key, sending a
release on that key makes it
Hi Michal,
On 04/05/2013 04:08 PM, Michal Hocko wrote:
On Fri 05-04-13 09:14:58, Simon Jeons wrote:
Hi Michal,
On 03/22/2013 04:15 PM, Michal Hocko wrote:
[getting off-list]
On Fri 22-03-13 07:46:32, Simon Jeons wrote:
Hi Michal,
On 03/21/2013 08:56 PM, Michal Hocko wrote:
On Thu 21-03-13
When looking through some mm code I stumbled over one part in
arch/x86/mm/pageattr.c that looks somewhat bogus to me. Cannot
say what exactly the effects are, but maybe you do (or you could
explain to me why I am wrong :)).
commit a8aed3e0752b4beb2e37cbed6df69faae88268da
Author: Andrea Arcangeli
On Fri, Apr 05, 2013 at 01:18:38AM -0300, Alexandre Pereira da Silva wrote:
Some boards and card slots doesn't have card detect feature available.
In that case allow to mark the cards as non-removable, via devicetree.
Signed-off-by: Alexandre Pereira da Silva aletes@gmail.com
Marc
On Fri, Apr 05, 2013 at 01:16:53AM -0300, Alexandre Pereira da Silva wrote:
The imx23-olinuxino sdcard doesn't support card detect.
So it sounds more like a broken-cd rather than non-removable?
Shawn
Signed-off-by: Alexandre Pereira da Silva aletes@gmail.com
---
Commit 57084ede395bb3c9da7905701d34a3b7d33c9356 (blackfin: bf537:
stamp: update board file for 193x) changed two references to
CONFIG_SND_BF5XX_SOC_AD193X (and CONFIG_SND_BF5XX_SOC_AD193X_MODULE).
One was changed to CONFIG_SND_SOC_AD193X_SPI, the other to
CONFIG_SND_SOC_AD193X_I2C. The commit
(2013/04/03 18:13), Li Zefan wrote:
The cgroup core guarantees it's always safe to access the parent.
Signed-off-by: Li Zefan lize...@huawei.com
Acked-by: KAMEZAWA Hiroyuki kamezawa.hir...@jp.fujitsu.com
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of
(2013/04/03 18:14), Li Zefan wrote:
Now memcg has the same life cycle as the corresponding cgroup.
Kill the useless refcnt.
Signed-off-by: Li Zefan lize...@huawei.com
very very very nice. Thank you.
Acked-by: KAMEZAWA Hiroyuki kamezawa.hir...@jp.fujitsu.com
--
To unsubscribe from this
On Fri 05-04-13 16:27:59, Wanpeng Li wrote:
On Fri, Apr 05, 2013 at 10:12:39AM +0200, Michal Hocko wrote:
On Fri 05-04-13 07:41:23, Wanpeng Li wrote:
On Thu, Apr 04, 2013 at 06:17:46PM +0200, Michal Hocko wrote:
On Thu 04-04-13 17:09:08, Wanpeng Li wrote:
order = MAX_ORDER pages are only
On Fri 05-04-13 17:00:58, Simon Jeons wrote:
Hi Michal,
On 04/05/2013 04:08 PM, Michal Hocko wrote:
On Fri 05-04-13 09:14:58, Simon Jeons wrote:
Hi Michal,
On 03/22/2013 04:15 PM, Michal Hocko wrote:
[getting off-list]
On Fri 22-03-13 07:46:32, Simon Jeons wrote:
Hi Michal,
On
From: Yasuaki Ishimatsu isimatu.yasu...@jp.fujitsu.com
If system can create movable node which all memory of the
node is allocated as ZONE_MOVABLE, setup_node_data() cannot
allocate memory for the node's pg_data_t.
So, use memblock_alloc_try_nid() instead of memblock_alloc_nid()
to retry when the
The Hot Pluggable field in SRAT points out if the memory could be
hotplugged while the system is running. It is useful to print out
this info when parsing SRAT.
Signed-off-by: Tang Chen tangc...@cn.fujitsu.com
---
arch/x86/mm/srat.c |9 ++---
1 files changed, 6 insertions(+), 3
As mentioned by Liu Jiang and Wu Jiangguo, users could specify DMA,
DMA32, and HIGHMEM as movable. In order to ensure the kernel will
work correctly, we should exclude these memory ranges out from
zone_movable_limit[].
NOTE: Do find_usable_zone_for_movable() to initialize movable_zone
so
If kernelcore or movablecore is specified at the same time with
movablemem_map, movablemem_map will have higher priority to be
satisfied. This patch will make find_zone_movable_pfns_for_nodes()
calculate zone_movable_pfn[] with the limit from zone_movable_limit[].
Signed-off-by: Tang Chen
Before this patch-set, we introduced movablemem_map boot option which allowed
users to specify physical address ranges to set memory as movable. This is not
user friendly enough for normal users.
So now, we introduce just movablemem_map=acpi to allow users to enable/disable
the kernel to use Hot
Before parsing SRAT, memblock has already reserved some memory ranges
for other purposes, such as for kernel image. We cannot prevent
kernel from using these memory. Furthermore, if all the memory is
hotpluggable, then the system won't have enough memory to boot if we set
all of them as movable.
Since node info in SRAT may not be in increasing order, we may meet
a lower range after we handled a higher range. So we need to keep
the lowest movable pfn each time we parse a SRAT memory entry, and
update it when we get a lower one.
This patch introduces a new array zone_movable_limit[], which
Ensure memblock will not allocate memory from areas that may be
ZONE_MOVABLE. The map info is from movablemem_map boot option.
The following problem was reported by Stephen Rothwell:
The definition of struct movablecore_map is protected by
CONFIG_HAVE_MEMBLOCK_NODE_MAP but its use in
Since we are using struct numa_meminfo to store SRAT info, and sanitize
movablemem_map.map[], we need hotplug info in struct numa_meminfo.
This patch introduces a bool hotpluggable member into struct
numa_meminfo.
And modifies the following APIs' prototypes to support it:
- numa_add_memblk()
Since we have introduced hotplug info into struct numa_meminfo, we need
to consider it when cleanup numa_meminfo.
The original logic in numa_cleanup_meminfo() is:
Merge blocks on the same node, holes between which don't overlap with
memory on other nodes.
This patch modifies
When parsing SRAT, we are able to know which memory ranges are hotpluggable,
and we add them to movablemem_map. So movablemem_map could be used to prevent
memblock from allocating memory in area which will be set as ZONE_MOVABLE later.
Signed-off-by: Tang Chen tangc...@cn.fujitsu.com
---
Since the kernel pages cannot be migrated, if we want a memory device
hotpluggable, we have to set all the memory on it as ZONE_MOVABLE.
This patch adds a boot option movablemem_map=acpi to inform the kernel
to use Hot Pluggable bit in SRAT to determine which memory device is
hotpluggable.
On 04/05/13 06:00, Rusty Russell wrote:
Exactly. Don't workaround it here, revert it and put the
duplicate-section-name fixup in parisc where it belongs.
Assuming parisc still produces these dup sections: that patch is 4 years
old now.
Untested:
diff --git a/arch/parisc/kernel/module.c
On Fri, 05 Apr 2013 11:20:46 +0200, Paul Bolle wrote:
1) Added Jean and Guenter because they seem to take in interest in
Blackfin's stamp files.
Doh, no, I only express my disgust and I'd rather stay away from them
as much as I can ;)
--
Jean Delvare
--
To unsubscribe from this list: send the
On Fri, Apr 05, 2013 at 12:09:42AM -0500, Nishanth Menon wrote:
If we ignore the details of the class 1.5 implementation, we will notice
a) regulator set_voltage equivalent set_voltage() is required.
b) this set_voltage does some 'magic stuff' depending on the SoC and AVS class
and calls the
On 4 April 2013 03:24, Tejun Heo t...@kernel.org wrote:
Not a call, probably a module_param() so that it can be switched
on/off during boot. You can make the param writable so that it can be
flipped run-time but updating existing workqueues would be non-trivial
and I don't think it's gonna be
(2013/04/05 17:16), Minchan Kim wrote:
Now, memory barrier in __do_huge_pmd_anonymous_page doesn't work.
Because lru_cache_add_lru uses pagevec so it could miss spinlock
easily so above rule was broken so user might see inconsistent data.
I was not first person who pointed out the problem.
On Fri 05-04-13 16:54:44, Simon Jeons wrote:
Hi Michal,
On 04/05/2013 04:12 PM, Michal Hocko wrote:
On Fri 05-04-13 07:41:23, Wanpeng Li wrote:
On Thu, Apr 04, 2013 at 06:17:46PM +0200, Michal Hocko wrote:
On Thu 04-04-13 17:09:08, Wanpeng Li wrote:
order = MAX_ORDER pages are only allocated
On Thu, Apr 04, 2013 at 03:27:47PM -0700, Andrew Bresticker wrote:
Regulator drivers may specify regulator_desc-supply_name which
regulator_register() will use to find the supply node for a regulator.
If no supply was specified in the device tree or the supply has yet
to be registered
Hi Roger,
On 04/05/2013 10:30 AM, Benoit Cousson wrote:
...
ARM: dts: OMAP4: Add HS USB Host IP nodes
ARM: dts: OMAP3: Add HS USB Host IP nodes
ARM: dts: omap3-beagle: Add USB Host support
These 3 DTS patches are good to me, but I cannot applied them on top of
the already existing
On Fri, Apr 05, 2013 at 08:37:39AM +0200, Marek Vasut wrote:
btw. did you know you can let git send-email automatically handle CC for you
so
you don't have to type it into the command line by simply sticking
Cc: Us Er e...@ma.il
in the commit message? Preferably under the SoB line.
1 - 100 of 1014 matches
Mail list logo
