On Wed, Jul 31, 2013 at 05:11:14PM +0200, Jan Kara wrote:
On Wed 31-07-13 14:15:45, Dave Chinner wrote:
/*
+ * mark an inode as under writeback on the given bdi
+ */
+void bdi_mark_inode_writeback(struct backing_dev_info *bdi, struct inode
*inode)
+{
+ WARN_ON_ONCE(bdi !=
Naoya Horiguchi n-horigu...@ah.jp.nec.com writes:
On Wed, Jul 31, 2013 at 12:02:30AM +0530, Aneesh Kumar K.V wrote:
Naoya Horiguchi n-horigu...@ah.jp.nec.com writes:
Now hugepages are definitely movable. So allocating hugepages from
ZONE_MOVABLE is natural and we have no reason to keep
On Wed, Jul 31, 2013 at 11:25:04PM +0800, Hillf Danton wrote:
On Wed, Jul 31, 2013 at 2:37 PM, Joonsoo Kim iamjoonsoo@lge.com wrote:
On Wed, Jul 31, 2013 at 02:21:38PM +0800, Hillf Danton wrote:
On Wed, Jul 31, 2013 at 12:41 PM, Joonsoo Kim iamjoonsoo@lge.com
wrote:
On Wed, Jul
This patch adds code to handle the misplaced TRIMINFO register
incase of Exynos5420.
On Exynos5420 we have a TRIMINFO register being misplaced for
TMU channels 2, 3 and 4
TRIMINFO at 0x1006c000 contains data for TMU channel 3
TRIMINFO at 0x100a contains data for TMU channel 4
TRIMINFO at
On Thursday 01 August 2013 07:57 AM, Joel Fernandes wrote:
On 07/31/2013 04:18 AM, Sekhar Nori wrote:
On Wednesday 31 July 2013 10:19 AM, Joel Fernandes wrote:
Hi Sekhar,
On 07/30/2013 02:05 AM, Sekhar Nori wrote:
On Monday 29 July 2013 06:59 PM, Joel Fernandes wrote:
In an effort to move
On Thu, Aug 01, 2013 at 09:53:03AM +0400, Cyrill Gorcunov wrote:
On Thu, Aug 01, 2013 at 09:51:32AM +0900, Minchan Kim wrote:
Index: linux-2.6.git/include/linux/swapops.h
===
--- linux-2.6.git.orig/include/linux/swapops.h
On Wed, Jul 31, 2013 at 05:15:42PM +0200, Jan Kara wrote:
On Wed 31-07-13 14:15:46, Dave Chinner wrote:
From: Dave Chinner dchin...@redhat.com
Inodes are removed lazily from the bdi writeback list, so in the
absence of sync(2) work inodes will build up on the bdi writback
list even
On Wed, Jul 31, 2013 at 08:48:40AM +0200, Sedat Dilek wrote:
On Wed, Jul 31, 2013 at 6:15 AM, Dave Chinner da...@fromorbit.com wrote:
Hi folks,
This series of patches is against the curent mmotm tree here:
http://git.cmpxchg.org/cgit/linux-mmotm.git/
Current is not precise
On Wed, 2013-07-10 at 13:57 -0600, Bjorn Helgaas wrote:
[+cc Jeff, Jesse, et al, e1000-devel]
Holy cow, you guys have a lot of folks listed in MAINTAINERS for Intel
drivers :) This is an ASPM question, if that helps narrow down the
folks interested.
Bruce Allan is the e1000e maintainer, I
2013/8/1, Ben Myers b...@sgi.com:
Hey Namjae,
On Wed, Jul 31, 2013 at 11:42:14PM +0900, Namjae Jeon wrote:
From: Namjae Jeon namjae.j...@samsung.com
New fallocate flag FALLOC_FL_COLLAPSE_RANGE implementation for XFS.
Signed-off-by: Namjae Jeon namjae.j...@samsung.com
Signed-off-by: Ashish
2013/8/1, Dave Chinner da...@fromorbit.com:
On Wed, Jul 31, 2013 at 11:42:26PM +0900, Namjae Jeon wrote:
From: Namjae Jeon namjae.j...@samsung.com
New fallocate flag FALLOC_FL_COLLAPSE_RANGE implementation for Ext4
.
+
+punch_start = offset EXT4_BLOCK_SIZE_BITS(sb);
+
Subject: [PATCH,RFC] numa,sched: use group fault statistics in numa placement
Here is a quick strawman on how the group fault stuff could be used
to help pick the best node for a task. This is likely to be quite
suboptimal and in need of tweaking. My main goal is to get this to
Peter Mel before
The AT91 PMC (Power Management Controller) provides an USB clock used by
USB Full Speed host (ohci) and USB Full Speed device (udc).
The usb drivers (ohci and udc) must configure this clock to 48Mhz.
This configuration was formely done in mach-at91/clock.c, but this
implementation will be removed
On Thu, Aug 01, 2013 at 03:16:32PM +0900, Minchan Kim wrote:
I don't get it. Could you correct me with below example?
Process A context
try_to_unmap
swp_pte = swp_entry_to_pte /* change generic swp into arch
swap */
swp_pte =
On 2013/8/1 13:38, Gao feng wrote:
On 08/01/2013 11:10 AM, Rui Xiang wrote:
On 2013/8/1 9:36, Gao feng wrote:
On 07/29/2013 10:31 AM, Rui Xiang wrote:
This patch makes syslog buf and other fields per
namespace.
Here use ns-log_buf(log_buf_len, logbuf_lock,
log_first_seq, logbuf_lock, and
On Thu, Aug 1, 2013 at 8:19 AM, Dave Chinner da...@fromorbit.com wrote:
On Wed, Jul 31, 2013 at 08:48:40AM +0200, Sedat Dilek wrote:
On Wed, Jul 31, 2013 at 6:15 AM, Dave Chinner da...@fromorbit.com wrote:
Hi folks,
This series of patches is against the curent mmotm tree here:
(2013/08/01 6:23), Rafael J. Wysocki wrote:
On Wednesday, July 31, 2013 03:08:03 PM Bjorn Helgaas wrote:
[+cc Rafael, linux-acpi]
On Tue, Jul 30, 2013 at 6:35 PM, Takao Indoh indou.ta...@jp.fujitsu.com
wrote:
On x86, currently IOMMU initialization run *after* PCI enumeration, but
what you
On Wed, Jul 31, 2013 at 05:00:44PM +0200, Roger Pau Monne wrote:
There's no need to keep the foreign access in a grant if it is not
persistently mapped by the backend. This allows us to free grants that
are not mapped by the backend, thus preventing blkfront from hoarding
all grants.
The
On Thu, Aug 01, 2013 at 10:28:14AM +0400, Cyrill Gorcunov wrote:
On Thu, Aug 01, 2013 at 03:16:32PM +0900, Minchan Kim wrote:
I don't get it. Could you correct me with below example?
Process A context
try_to_unmap
swp_pte = swp_entry_to_pte /* change generic
On Thu, Aug 01, 2013 at 03:37:06PM +0900, Minchan Kim wrote:
Reviewed-by: Minchan Kim minc...@kernel.org
Thanks a lot for review, Minchan!
--
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
The AT91 PMC (Power Management Controller) provides an USB clock used by
USB Full Speed host (ohci) and USB Full Speed device (udc).
The usb drivers (ohci and udc) must configure this clock to 48Mhz.
This configuration was formely done in mach-at91/clock.c, but this
implementation will be removed
This patch moves peripheral id definitions from machine specific include
dir (arch/arm/mach-at91/include/mach/'soc-name'.h) to dt-bindinds include
dir (include/dt-bindings/at91/'soc-name'/peripherals.h).
These definitions will be used inside dt to define interrupt ids and
peripheral clk ids.
This patch make use of the peripheral id macros defined in
dt-bindings/at91/at91sam9260/peripherals.h to register peripheral
interrupts.
Signed-off-by: Boris BREZILLON b.brezil...@overkiz.com
---
arch/arm/boot/dts/at91sam9260.dtsi | 57 +++-
1 file changed, 30
This patch make use of the peripheral id macros defined in
dt-bindings/at91/at91sam9g45/peripherals.h to register peripheral
interrupts.
Signed-off-by: Boris BREZILLON b.brezil...@overkiz.com
---
arch/arm/boot/dts/at91sam9g45.dtsi| 57 +
This patch make use of the peripheral id macros defined in
dt-bindings/at91/at91sam9n12/peripherals.h to register peripheral
interrupts.
Signed-off-by: Boris BREZILLON b.brezil...@overkiz.com
---
arch/arm/boot/dts/at91sam9n12.dtsi | 43 ++--
1 file changed, 22
This patch make use of the peripheral id macros defined in
dt-bindings/at91/at91sam9x5/peripherals.h to register peripheral
interrupts.
Signed-off-by: Boris BREZILLON b.brezil...@overkiz.com
---
arch/arm/boot/dts/at91sam9x5.dtsi | 63 +++--
1 file changed, 32
This patch make use of the peripheral id macros defined in
dt-bindings/at91/sama5d3/peripherals.h to register peripheral
interrupts.
Signed-off-by: Boris BREZILLON b.brezil...@overkiz.com
---
arch/arm/boot/dts/sama5d3.dtsi | 83
1 file changed, 42
This patch make use of the peripheral id macros defined in
dt-bindings/at91/at91sam9263/peripherals.h to register peripheral
interrupts.
Signed-off-by: Boris BREZILLON b.brezil...@overkiz.com
---
arch/arm/boot/dts/at91sam9263.dtsi | 46 +++-
1 file changed, 24
This patch make use of the peripheral id macros defined in
dt-bindings/at91/at91rm9200/peripherals.h to register peripheral
interrupts.
Signed-off-by: Boris BREZILLON b.brezil...@overkiz.com
---
arch/arm/boot/dts/at91rm9200.dtsi | 59 +
1 file changed, 33
* Linus Torvalds torva...@linux-foundation.org wrote:
On Wed, Jul 31, 2013 at 7:14 PM, Rik van Riel r...@redhat.com wrote:
Is this better? Not that I really care which version gets applied :)
I'm ok with this.
That said, I'm assuming this goes in through Ingo, since it is both
x86
Hello,
This patch series move at91 SoCs peripheral id definitions from machine
specific include dir to dt-bindings include dir.
These macros are used to reference interrupts instead of peripheral numbers.
This makes dt definitions cleaner and easier to debug (one can easily tell if
the
Linux cannot migrate pages used by the kernel due to the direct mapping
(va = pa + PAGE_OFFSET), any memory used by the kernel cannot be hot-removed.
So when using memory hotplug, we have to prevent the kernel from using
hotpluggable memory.
The ACPI table SRAT (System Resource Affinity Table)
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, if the
physical address is changed, we cannot simply
In the following patches, we need to call get_ramdisk_{image|size}()
to get initrd file's address and size. So make these two functions
global.
v1 - v2:
As tj suggested, make these two function static inline in
arch/x86/include/asm/setup.h.
Signed-off-by: Tang Chen tangc...@cn.fujitsu.com
In find_hotpluggable_memory, once we find out a memory region which is
hotpluggable, we want to mark them in memblock.memory. So that we could
control memblock allocator not to allocte hotpluggable memory for the kernel
later.
To achieve this goal, we introduce MEMBLOCK_HOTPLUG flag to indicate
The Hot-Pluggable fired in SRAT specifies which memory is hotpluggable.
As we mentioned before, if hotpluggable memory is used by the kernel,
it cannot be hot-removed. So memory hotplug users may want to set all
hotpluggable memory in ZONE_MOVABLE so that the kernel won't use it.
Memory hotplug
At early time, memblock will reserve some memory for the kernel,
such as the kernel code and data segments, initrd file, and so on，
which means the kernel resides in these memory regions.
Even if these memory regions are hotpluggable, we should not
mark them as hotpluggable. Otherwise the kernel
In ACPI SRAT(System Resource Affinity Table), there is a memory affinity for
each
memory range in the system. In each memory affinity, there is a field indicating
that if the memory range is hotpluggable.
This patch parses all the memory affinities in SRAT only, and find out all the
hotpluggable
Linux kernel cannot migrate pages used by the kernel. As a result, hotpluggable
memory used by the kernel won't be able to be hot-removed. To solve this
problem, the basic idea is to prevent memblock from allocating hotpluggable
memory for the kernel at early time, and arrange all hotpluggable
+static int task_numa_find_cpu(struct task_struct *p, int nid)
+{
+ int node_cpu = cpumask_first(cpumask_of_node(nid));
+ int cpu, src_cpu = task_cpu(p), dst_cpu = src_cpu;
+ unsigned long src_load, dst_load;
+ unsigned long min_load = ULONG_MAX;
+ struct task_group *tg
There is no flag in memblock to describe what type the memory is.
Sometimes, we may use memblock to reserve some memory for special usage.
And we want to know what kind of memory it is. So we need a way to
differentiate memory for different usage.
In hotplug environment, we want to reserve
This patch introduce early_acpi_firmware_srat() to find the
phys addr of SRAT provided by firmware. And call it in
find_hotpluggable_memory().
Since we have initialized acpi_gbl_root_table_list earlier,
and store all the tables' phys addrs and signatures in it,
it is easy to find the SRAT.
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
Besides the phys addr of the acpi tables, it will be very convenient if
we also have the signature of each table in acpi_gbl_root_table_list at
early time. We can find SRAT easily by comparing the signature.
This patch alse record signature and some other info in
acpi_gbl_root_table_list at early
In ACPI, SRAT(System Resource Affinity Table) contains NUMA info.
The memory affinities in SRAT record every memory range in the
system, and also, flags specifying if the memory range is
hotpluggable.
(Please refer to ACPI spec 5.0 5.2.16)
memblock starts to work at very early time, and SRAT has
The comments of find_cpio_data() says:
* @offset: When a matching file is found, this is the offset to the
* beginning of the cpio. ..
But according to the code,
dptr = PTR_ALIGN(p + ch[C_NAMESIZE], 4);
nptr = PTR_ALIGN(dptr + ch[C_FILESIZE], 4);
*offset =
The Hot-Pluggable field in SRAT suggests if the memory could be
hotplugged while the system is running. Print it as well when
parsing SRAT will help users to know which memory is hotpluggable.
Signed-off-by: Tang Chen tangc...@cn.fujitsu.com
Reviewed-by: Wanpeng Li liw...@linux.vnet.ibm.com
In acpi_initrd_override(), it checks several things to ensure the
table it found is valid. In later patches, we need to do these check
somewhere else. So this patch introduces a common function
acpi_invalid_table() to do all these checks, and reuse it in different
places. The function will be used
We have split acpi_table_init() into two steps:
1. Pares RSDT or XSDT, and initialize acpi_gbl_root_table_list.
This step will record all tables' physical address in memory.
2. Check acpi initrd table override and install all tables into
acpi_gbl_root_table_list.
This patch does step 1
The macro INVALID_TABLE() is defined like this:
#define INVALID_TABLE(x, path, name)\
{ pr_err(ACPI OVERRIDE: x [%s%s]\n, path, name); continue; }
And it is used like this:
for (...) {
...
if (...)
Arrange hotpluggable memory as ZONE_MOVABLE will cause NUMA performance down
because the kernel cannot use movable memory. For users who don't use memory
hotplug and who don't want to lose their NUMA performance, they need a way to
disable this functionality. So we improved movablecore boot
On Wed, Jul 31, 2013 at 6:31 PM, Borislav Petkov b...@alien8.de wrote:
On Wed, Jul 31, 2013 at 12:39:23PM +0300, Mike Rapoport wrote:
There are plenty virtual machines in EC2, Rackspace, HP and other
clouds that do not have hardware virtualization. I believe that
running a hypervisor on them
On Mon, Jul 29, 2013 at 11:08:52PM +, Winkler, Tomas wrote:
How do I add new device specific sysfs in non-race way if my entry
point is the pci probe function.
You do it in the device creation for the device you add below the PCI device
in sysfs, by setting the groups field in the
Hi all,
Changes since 20130731:
Removed trees: xen-arm (merged into the xen-tip tree)
The ext4 tree still has its build failure so I used the version from
next-20130726.
The driver-core tree gained a conflict against the net-next tree.
The usb-gadget tree lost its build failure but gained
On Wed, Jul 31, 2013 at 10:30:41AM +0800, Xiong Zhou wrote:
From: Xiong Zhou jencce.ker...@gmail.com
First version of this patch makes LUSTRE_FS depends on BLOCK. Second
version makes only lloop depends on BLOCK with a config option for this
dependence, and remove unnecessary jdb header
On Thu, 2013-07-25 at 12:00 +0200, Fabio Baltieri wrote:
Change mac80211 LED trigger code to use the generic
led_trigger_blink_oneshot() API for transmit and receive activity
indication.
This gives a better feedback to the user, as with the new API each
activity event results in a visible
On Wed, Jul 31, 2013 at 10:36:48AM +0100, Srinivas KANDAGATLA wrote:
From: Srinivas Kandagatla srinivas.kandaga...@st.com
This patch adds support to ASC (asynchronous serial controller)
driver, which is basically a standard serial driver. This IP is common
across all the ST parts for settop
On Wed, Jul 24, 2013 at 08:31:32PM -0700, Sudeep Dutt wrote:
--- /dev/null
+++ b/drivers/misc/mic/common/mic_device.h
@@ -0,0 +1,81 @@
+/*
+ * Intel MIC Platform Software Stack (MPSS)
+ *
+ * Copyright(c) 2013 Intel Corporation.
+ *
+ * This program is free software; you can redistribute
On Fri, Jul 26, 2013 at 06:19:16PM +0530, Kishon Vijay Abraham I wrote:
+static int phy_get_id(void)
+{
+ int ret;
+ int id;
+
+ ret = ida_pre_get(phy_ida, GFP_KERNEL);
+ if (!ret)
+ return -ENOMEM;
+
+ ret = ida_get_new(phy_ida, id);
+ if (ret 0)
+
On Thu, Jul 18, 2013 at 06:50:55PM -0700, Greg KH wrote:
On Thu, Jul 18, 2013 at 06:36:07PM -0700, Kees Cook wrote:
On Thu, Jul 18, 2013 at 6:30 PM, Greg KH gre...@linuxfoundation.org wrote:
On Fri, Jul 19, 2013 at 01:15:26AM +, Linux Kernel Mailing List wrote:
Gitweb:
On Wed, Jul 24, 2013 at 08:31:31PM -0700, Sudeep Dutt wrote:
An Intel MIC X100 device is a PCIe form factor add-in coprocessor
card based on the Intel Many Integrated Core (MIC) architecture
that runs a Linux OS. It is a PCIe endpoint in a platform and therefore
implements the three required
On Wed, Jul 24, 2013 at 08:31:32PM -0700, Sudeep Dutt wrote:
This patch enables the following:
a) Initializes the Intel MIC X100 PCIe devices.
b) Boots and shuts down the card via sysfs entries.
c) Allocates and maps a device page for communication with the
card driver and updates the device
Hi Linus,
On Tue, Jul 30, 2013 at 12:47 AM, Linus Walleij
linus.wall...@linaro.org wrote:
On Fri, Jul 26, 2013 at 6:57 AM, Sonic Zhang sonic@gmail.com wrote:
Could you please comment on this patch set? It is based on your former
comments.
I'll get to it. I'm pretty choked right now and
On Wed, Jul 24, 2013 at 08:31:32PM -0700, Sudeep Dutt wrote:
This patch enables the following:
a) Initializes the Intel MIC X100 PCIe devices.
b) Boots and shuts down the card via sysfs entries.
c) Allocates and maps a device page for communication with the
card driver and updates the device
On 07/31/2013 11:54 AM, Gleb Natapov wrote:
On Tue, Jul 30, 2013 at 10:13:12PM +0530, Raghavendra K T wrote:
On 07/25/2013 03:08 PM, Raghavendra K T wrote:
On 07/25/2013 02:45 PM, Gleb Natapov wrote:
On Thu, Jul 25, 2013 at 02:47:37PM +0530, Raghavendra K T wrote:
On 07/24/2013 06:06 PM,
I wonder if we could get even more conservative values
of avg_idle by clamping delta to max, before calling
update_avg...
Or rather, I wonder if that would matter enough to make
a difference, and in what direction that difference would
be.
In other words:
if (rq-idle_stamp) {
On Thu, Aug 01, 2013 at 07:21:30AM +, Winkler, Tomas wrote:
On Mon, Jul 29, 2013 at 11:08:52PM +, Winkler, Tomas wrote:
How do I add new device specific sysfs in non-race way if my entry
point is the pci probe function.
You do it in the device creation for the device you
2013/8/1 Boris BREZILLON b.brezil...@overkiz.com:
Hello,
This patch series move at91 SoCs peripheral id definitions from machine
specific include dir to dt-bindings include dir.
These macros are used to reference interrupts instead of peripheral numbers.
This makes dt definitions cleaner
Ulf,
I got confirmation from Broadcom that all cell phone reference designs
have card insert/removal configured as a wakeup IRQ. Unless our
customers change that - which I doubt - this results in a considerable
number of products implementing this feature.
Please let me know how you wish to
Hello Sudeep Dutt,
On Wed, Jul 31, 2013 at 06:46:08PM -0700, Greg Kroah-Hartman wrote:
On Wed, Jul 24, 2013 at 08:31:31PM -0700, Sudeep Dutt wrote:
An Intel MIC X100 device is a PCIe form factor add-in coprocessor
card based on the Intel Many Integrated Core (MIC) architecture
that runs a
On Thu, Aug 01, 2013 at 01:08:47PM +0530, Raghavendra K T wrote:
On 07/31/2013 11:54 AM, Gleb Natapov wrote:
On Tue, Jul 30, 2013 at 10:13:12PM +0530, Raghavendra K T wrote:
On 07/25/2013 03:08 PM, Raghavendra K T wrote:
On 07/25/2013 02:45 PM, Gleb Natapov wrote:
On Thu, Jul 25, 2013 at
There are several drivers in drivers/net/usb/ that
do not have specific MAINTAINERS that should have
emails forwarded to the linux-usb mailing list.
Add a section for those drivers.
Signed-off-by: Joe Perches j...@perches.com
---
In the future, you do not need to send drivers/net/usb/ patches
On Thu, Aug 01, 2013 at 12:36:41AM -0700, Jason Low wrote:
So how acceptable is setting a limit of 2*migration cost or less on the
delta rather than on the avg?
Its fine with me as we're already doing that. But since you asked last
time around if those two things weren't unrelated etc..
--
To
On Thu, Aug 1, 2013 at 9:25 AM, Stephen Rothwell s...@canb.auug.org.au wrote:
Hi all,
Changes since 20130731:
Removed trees: xen-arm (merged into the xen-tip tree)
The ext4 tree still has its build failure so I used the version from
next-20130726.
The driver-core tree gained a conflict
On Thu, Aug 01, 2013 at 12:48:48AM -0700, Joe Perches wrote:
There are several drivers in drivers/net/usb/ that
do not have specific MAINTAINERS that should have
emails forwarded to the linux-usb mailing list.
Add a section for those drivers.
Signed-off-by: Joe Perches j...@perches.com
By slightly reorganizing the code, the number of registers
used in the tlb miss handlers can be reduced by two,
thus removing the need to save them to memory.
Also, some dead and commented out code is removed.
No functional change.
Signed-off-by: Stefan Kristiansson
Fix inadvertent breakage in the clone syscall ABI for Microblaze
that was introduced in this patch:
microblaze: switch to generic fork/vfork/clone
(sha1: f3268edbe6fe0ce56e62c6d6b14640aeb04864b7)
The Microblaze syscall ABI for clone takes the parent tid address in
the 4th argument; the third
On 07/31/2013 10:10 PM, Andrew Morton wrote:
On Mon, 29 Jul 2013 09:01:48 +0200 Michal Simek michal.si...@xilinx.com
wrote:
Fix inadvertent breakage in the clone syscall ABI for Microblaze
that was introduced in this patch:
microblaze: switch to generic fork/vfork/clone
(sha1:
This patch fixes mishandling of the sbi-n_orphans variable.
If users request lots of f2fs_unlink(), check_orphan_space() could be contended.
In such the case, sbi-n_orphans can be read incorrectly so that f2fs_unlink()
would fall into the wrong state which results in the failure of
On Thu 01-08-13 08:42:17, Wu Fengguang wrote:
tree: git://git.cmpxchg.org/linux-mmotm.git master
head: 01db8fe7b3c8461274e4c9257789514987e7abc8
commit: 5701031ddea61c051fb8309cbf372dd94e540f22 [69/312] watchdog: update
watchdog_tresh properly
config: i386-randconfig-c00-0801 (attached as
On Wed, 31 Jul 2013, Kim, Milo wrote:
Thanks for the review, please see my comments.
snip * looks good up to me up to here *
Although, I think the 0 = 1, 1 = 2 ... stuff is really confusing. Is
there nothing we can do about that?
OK, enum value of lp3943_pwm_output can be changed
Hi,
Le Wed, 31 Jul 2013 18:41:57 +0100,
Tuomas Tynkkynen ttynkky...@nvidia.com a écrit :
The has_hostpc capability bit indicates that the host controller has
the HOSTPC register extensions, but at the same time enables clock
disabling power saving features with the PHY Low Power Clock Disable
On Wed, Jul 31, 2013 at 11:16:52PM +0200, Rafael J. Wysocki wrote:
Does reverting efaa14c help?
Nope.
But see my other reply to Aaron.
Thanks.
--
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
On Thu, 2013-08-01 at 15:56 +0800, Greg KH wrote:
On Thu, Aug 01, 2013 at 12:48:48AM -0700, Joe Perches wrote:
There are several drivers in drivers/net/usb/ that
do not have specific MAINTAINERS that should have
emails forwarded to the linux-usb mailing list.
diff --git a/MAINTAINERS
On Wed, Jul 31, 2013 at 02:15:41PM +1000, Dave Chinner wrote:
From: Dave Chinner dchin...@redhat.com
Some filesystems don't use the VFS inode hash and fake the fact they
are hashed so that all the writeback code works correctly. However,
this means the evict() path still tries to remove the
On Thu, Aug 01, 2013 at 09:13:35AM +0800, Aaron Lu wrote:
Can you please run acpi_listen and then press the Fn-Fx key, see if the
events are correctly sent out?
Like this?
# acpi_listen
video/brightnessdown BRTDN 0087
video/brightnessup BRTUP 0086
video/brightnessdown
Which algorithm (apart from crc* which I know and will fix) uses the
same driver name as its algorithm name? Doing this will cause issues
when an alternative implementation for that algorithm gets added.
Fixing names resolves double calls only for the thread cryptomgr_test-alg_test
where the
On 08/01/2013 05:38 AM, Rafael J. Wysocki wrote:
From: Rafael J. Wysocki rafael.j.wyso...@intel.com
The cpufreq core is a little inconsistent in the way it uses the
driver module refcount.
Namely, if __cpufreq_add_dev() is called for a CPU without siblings
or generally a CPU for which a
On Thu, Aug 01, 2013 at 11:55:35AM +0900, Namhyung Kim wrote:
Hello,
This patchset tries to fix and enhance current srcline behavior.
Firstly it doesn't actually sort by srcline info but by ip. I suspect
it was because of a performance reason to run external addr2line
utility. It showed
At this point the list_lru name really becomes confusing. Given that
it's not really LRU specific maybe just rename it to pernode_list
or similar?
--
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
Instead of adding more mess to change_file_space it might be a good idea
to pull my
refactor the preallocation and hole punching code
series from December in first.
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
On Wed, Jul 31, 2013 at 08:48:27PM -0700, Felipe Ferreri Tonello wrote:
I did that but I'm not happy with the control name. Usually drivers
add jacks like: Headset for a headset, Headphone for a headphone
and so on.
I did the following: control name is jack name + (jack type) + Jack.
If jack
I am Capt. Jon Hutchins from Multinational Base Tarin Kot, Afghanistan. I found
your contact particulars in an address journals and i summoned up courage to
contact you. With a very despirate need for help, i am seeking your assistance
in evacuating the sum of $5,200,000.00 to you for safe
Btw, FreeBSD has an extension to shm_open to create unnamed but fd
passable segments. From their man page:
As a FreeBSD extension, the constant SHM_ANON may be used for the path
argument to shm_open(). In this case, an anonymous, unnamed shared
memory object is created. Since the
On Thu, Aug 01, 2013 at 02:31:17AM +0200, Frederic Weisbecker wrote:
Hi,
So none of the patches from the previous v2 posting have changed.
I've just added two more in order to fix build crashes reported
by Wu Fengguang:
hardirq: Split preempt count mask definitions
m68k:
Hi Naveen,
Can you rebase these patches against
https://git.kernel.org/cgit/linux/kernel/git/evalenti/linux-soc-thermal.git/log/?h=next.
All these patches have been queued for 3.12 merge and contains the new
re-structured TMU driver.
Thanks,
Amit Daniel
On Thu, Aug 1, 2013 at 11:32 AM, Naveen
On Thu 01-08-13 15:48:05, Dave Chinner wrote:
On Wed, Jul 31, 2013 at 04:40:19PM +0200, Jan Kara wrote:
On Wed 31-07-13 14:15:40, Dave Chinner wrote:
From: Dave Chinner dchin...@redhat.com
Doing writeback on lots of little files causes terrible IOPS storms
because of the
On Thu, Aug 01, 2013 at 01:29:51AM -0700, Christoph Hellwig wrote:
Btw, FreeBSD has an extension to shm_open to create unnamed but fd
passable segments. From their man page:
As a FreeBSD extension, the constant SHM_ANON may be used for the path
argument to shm_open(). In this case,
By following commit, I cannot hot remove a memory device.
ACPI / memhotplug: Bind removable memory blocks to ACPI device nodes
commit e2ff39400d81233374e780b133496a2296643d7d
Details are follows:
When I add a memory device, acpi_memory_enable_device() always fails
as follows:
...
[ 1271.114116]
Hi Jianpeng Ma,
On 8/1/2013 10:18 AM, majianpeng wrote:
We found a problem when we removed a working sd card that the irqaction
of omap_hsmmc can sleep to 3.6s. This cause our watchdog to work.
In func omap_hsmmc_reset_controller_fsm, it should watch a 0-1
transition.It used loops_per_jiffy
1 - 100 of 1664 matches
Mail list logo
