Thanks.
Acked-by: Xuetao Guan g...@mprc.pku.edu.cn
- Andrew Morton a...@linux-foundation.org 写道：
On Mon, 27 Jan 2014 19:10:24 +0100 xypron.g...@gmx.de wrote:
From: Heinrich Schuchardt xypron.g...@gmx.de
If is based on uninitialized value keep_early.
This leads to unpredictable
On 2014-01-27 21:22, Andi Kleen wrote:
On Mon, Jan 27, 2014 at 08:14:06PM +0100, Jan Kiszka wrote:
apic_icr_write and its users in smpboot.c were apparently written under
the assumption that this code would only run during early boot. But
nowadays we also execute it when onlining a CPU later
Am 28.01.2014 07:28, schrieb Ingo Molnar:
* Kees Cook keesc...@chromium.org wrote:
On Mon, Jan 27, 2014 at 9:20 AM, Richard Weinberger rich...@nod.at wrote:
Am 27.01.2014 18:05, schrieb Kees Cook:
I would argue that decoding a non-panic oops on a running system is
entirely possible as-is,
An OTP write shall write as much data as possible to the OTP memory
and return the number of bytes that have actually been written.
If no data could be written at all due to lack of OTP memory,
return -ENOSPC.
Signed-off-by: Christian Riesch christian.rie...@omicron.at
Cc: Artem Bityutskiy
Hi all,
In the discussion on my patchset for the OTP support for
drivers/mtd/chips/cfi_cmdset_0002.c [1-5], Artem requested two changes in the
current code of the OTP write functions and the _get_{fact,user}_prot_info
code.
These two patches are an attempt to make the requested changes.
The
Signed-off-by: Alexander Gordeev agord...@redhat.com
---
drivers/block/nvme-core.c |6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/block/nvme-core.c b/drivers/block/nvme-core.c
index f03f123..e004c09 100644
--- a/drivers/block/nvme-core.c
+++
Signed-off-by: Alexander Gordeev agord...@redhat.com
---
drivers/block/nvme-core.c | 33 ++---
1 files changed, 26 insertions(+), 7 deletions(-)
diff --git a/drivers/block/nvme-core.c b/drivers/block/nvme-core.c
index 39868be..83d57b3 100644
---
This update partially reverts commit c5dc919 (NVMe: Disable
admin queue on init failure) to roll back easy readable
nvme_free_queues() function. Commit's c5dc919 functionality
aimed to free admin queue IRQ on init failure is preserved.
Signed-off-by: Alexander Gordeev agord...@redhat.com
---
IRQ affinity hints are attempted to setup for some or all
queues which have not yet been allocated: either on device
probe or resume. This update moves the setup after all
queues are successfully created.
Signed-off-by: Alexander Gordeev agord...@redhat.com
---
drivers/block/nvme-core.c | 12
Signed-off-by: Alexander Gordeev agord...@redhat.com
---
drivers/block/nvme-core.c | 22 --
1 files changed, 16 insertions(+), 6 deletions(-)
diff --git a/drivers/block/nvme-core.c b/drivers/block/nvme-core.c
index 1e30c42..39868be 100644
--- a/drivers/block/nvme-core.c
+++
Minimize a poissible error when accessing dev-entry[] array
entries using an arbitrary index rather than the legitimate
nvme_queue::cq_vector value. This update also makes affinity
hint setup conform to the rest of the code around.
Signed-off-by: Alexander Gordeev agord...@redhat.com
---
On Sun, Jan 26, 2014 at 9:25 PM, Ingo Molnar mi...@kernel.org wrote:
* Ingo Molnar mi...@kernel.org wrote:
* Linus Torvalds torva...@linux-foundation.org wrote:
On Sun, Jan 26, 2014 at 4:27 AM, David Howells dhowe...@redhat.com wrote:
- p = proc_create(cells, 0, proc_afs,
A queue structure contains both a pointer to the device it
belongs to and the queue ID - there is no need to drag these
parameters around.
Signed-off-by: Alexander Gordeev agord...@redhat.com
---
drivers/block/nvme-core.c | 20 +++-
1 files changed, 11 insertions(+), 9
While nvme_alloc_queue() and nvme_free_queue() are logically
counterparts, they are inconsistent with regard to how device
queue_count is updated - it is increased within the former,
but decreased outside of the latter. This update fixes the
described inconsistency and also makes further
A queue structure contains both a pointer to the device it
belongs to and the queue ID - there is no need to drag these
parameters around.
Signed-off-by: Alexander Gordeev agord...@redhat.com
---
drivers/block/nvme-core.c | 34 +++---
1 files changed, 19
Hi Keith, Matthew,
Here are few fixes to the code that caught my eye.
These are unrelated to the patch nvme: Use pci_enable_msi_range()
and pci_enable_msix_range() I sent earlier, which still waits for
your review.
Thanks!
Alexander Gordeev (14):
NVMe: Fix setup of affinity hint for
Parameter qid is not only superfluous, but also confusing -
it suggests nvme_init_queue() could reinit the queue with an
ID other than index into device queues[] array.
Signed-off-by: Alexander Gordeev agord...@redhat.com
---
drivers/block/nvme-core.c |8
1 files changed, 4
Signed-off-by: Alexander Gordeev agord...@redhat.com
---
drivers/block/nvme-core.c | 12 ++--
1 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/drivers/block/nvme-core.c b/drivers/block/nvme-core.c
index 661277d..f03f123 100644
--- a/drivers/block/nvme-core.c
+++
From: Liu Junliang liujunliang_...@163.com
Signed-off-by: Liu Junliang liujunliang_...@163.com
---
drivers/net/usb/Kconfig | 16 +
drivers/net/usb/Makefile |1 +
drivers/net/usb/sr9800.c | 874 ++
drivers/net/usb/sr9800.h | 202 +++
4
Hi Heiko
Thank you for your reply.
On Tue, Jan 28, 2014 at 1:08 PM, Heiko Stübner he...@sntech.de wrote:
On Tuesday, 28. January 2014 12:46:01 Manish Badarkhe wrote:
Hi Dmitry,
Thank you for your review.
On Tue, Jan 28, 2014 at 12:03 PM, Dmitry Torokhov
dmitry.torok...@gmail.com wrote:
Hi Mike, Russell,
On 2013-11-06 18:19, Russell King - ARM Linux wrote:
On Wed, Nov 06, 2013 at 01:48:44PM +0200, Tomi Valkeinen wrote:
On 2013-11-06 13:15, Russell King - ARM Linux wrote:
On Wed, Nov 06, 2013 at 01:06:48PM +0200, Tomi Valkeinen wrote:
This means that the following code works
On 01/24/2014 11:21 AM, Preeti U Murthy wrote:
On 01/24/2014 02:38 PM, Daniel Lezcano wrote:
On 01/23/2014 12:15 PM, Preeti U Murthy wrote:
Hi Daniel,
Thank you for the review.
[ ... ]
---
drivers/cpuidle/cpuidle.c | 15 +
drivers/cpuidle/governors/ladder.c | 101
Patch (clk: si5351: remove variant from platform_data) changed parameters
passed to si5351_dt_parse. While it builds fine with CONFIG_OF, the non-DT
stub of si5351_dt_parse has not been updated and fails to build there.
Signed-off-by: Sebastian Hesselbarth sebastian.hesselba...@gmail.com
On 2014-01-28 09:50, Tomi Valkeinen wrote:
On 2014-01-27 19:30, Ivaylo Dimitrov wrote:
Hi Tomi,
linux-next-20140124 DSS is broken on N900 - display stays black (there
is some noise though). I booted the kernel with qemu and it gives the
following warning:
[0.623779] DSS: set fck to
On Mon, Jan 27, 2014 at 02:43:36PM -0800, Andrew Morton wrote:
On Mon, 27 Jan 2014 15:51:27 + Mel Gorman mgor...@suse.de wrote:
The command line parsing takes place before jump labels are initialised
which
generates a warning if numa_balancing= is specified and CONFIG_JUMP_LABEL
is
Signed-off-by: Christian Riesch christian.rie...@omicron.at
Cc: Artem Bityutskiy artem.bityuts...@linux.intel.com
Cc: Brian Norris computersforpe...@gmail.com
---
drivers/mtd/chips/cfi_cmdset_0001.c | 31 +--
drivers/mtd/devices/mtd_dataflash.c |7 ---
From: xinhui.pan xinhuix@intel.com
intel_gpio_runtime_idle should return correct error code if it do fail.
make it more correct even though -EBUSY is the most possible return value.
Signed-off-by: bo.he bo...@intel.com
Signed-off-by: xinhui.pan xinhuix@intel.com
---
Hi,
-Original Message-
From: Jaegeuk Kim [mailto:jaegeuk@samsung.com]
Sent: Tuesday, January 28, 2014 2:00 PM
To: Chao Yu
Cc: linux-fsde...@vger.kernel.org; linux-kernel@vger.kernel.org;
linux-f2fs-de...@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: use inode
On Tuesday, 28. January 2014 14:16:39 Manish Badarkhe wrote:
Hi Heiko
Thank you for your reply.
On Tue, Jan 28, 2014 at 1:08 PM, Heiko Stübner he...@sntech.de wrote:
On Tuesday, 28. January 2014 12:46:01 Manish Badarkhe wrote:
Hi Dmitry,
Thank you for your review.
On Tue, Jan
On Mon, Jan 27, 2014 at 03:31:32PM -0800, David Rientjes wrote:
On Mon, 27 Jan 2014, Mel Gorman wrote:
diff --git a/mm/mempolicy.c b/mm/mempolicy.c
index c2ccec0..c1a2573 100644
--- a/mm/mempolicy.c
+++ b/mm/mempolicy.c
@@ -120,6 +120,14 @@ static struct mempolicy default_policy = {
Signed-off-by: Alexander Gordeev agord...@redhat.com
---
drivers/block/nvme-core.c | 16 ++--
1 files changed, 14 insertions(+), 2 deletions(-)
diff --git a/drivers/block/nvme-core.c b/drivers/block/nvme-core.c
index d81b4c4..1e30c42 100644
--- a/drivers/block/nvme-core.c
+++
On Tue, 2014-01-28 at 16:36 +0800, liujunliang_...@163.com wrote:
From: Liu Junliang liujunliang_...@163.com
trivial comments...
diff --git a/drivers/net/usb/sr9800.c b/drivers/net/usb/sr9800.c
[]
+static int sr_rx_fixup(struct usbnet *dev, struct sk_buff *skb)
+{
[]
+ if
On Tue, Jan 28, 2014 at 2:25 PM, Heiko Stübner he...@sntech.de wrote:
On Tuesday, 28. January 2014 14:16:39 Manish Badarkhe wrote:
Hi Heiko
Thank you for your reply.
On Tue, Jan 28, 2014 at 1:08 PM, Heiko Stübner he...@sntech.de wrote:
On Tuesday, 28. January 2014 12:46:01 Manish Badarkhe
On-stack variable numa_kernel_nodes in numa_clear_kernel_node_hotplug()
was not initialized. So we need to initialize it.
Signed-off-by: Tang Chen tangc...@cn.fujitsu.com
Tested-by: Gu Zheng guz.f...@cn.fujitsu.com
---
arch/x86/mm/numa.c | 2 ++
1 file changed, 2 insertions(+)
diff --git
Dave found a kernel crash problem during boot. This is a problem of array out
of boundary.
These two patches fix this problem.
Since I am in a hurry, if the changelog is not good enough, I'll resend a new
version tomorrow.
Tang Chen (2):
numa, mem-hotplug: Initialize numa_kernel_nodes in
The following path will cause array out of bound.
memblock_add_region() will always set nid in memblock.reserved to MAX_NUMNODES.
In numa_register_memblks(), after we set all nid to correct valus in
memblock.reserved,
we called setup_node_data(), and used memblock_alloc_nid() to allocate memory,
Network Nut wrote:
5. I can simulate system-global named mutex using shared-memory for
underlying state of mutex (POCO NamedMutex)
6. I can get named semaphore using POSIX sem_create
It seems that the remaining problem is to get named mutex and named
semaphore to be accessible by
On 2014-01-27 20:41, Christoph Fritz wrote:
On Mon, 2014-01-27 at 19:30 +0200, Ivaylo Dimitrov wrote:
linux-next-20140124 DSS is broken on N900 - display stays black (there
is some noise though). I booted the kernel with qemu and it gives the
following warning:
[0.623779] DSS: set fck
On 01/28/2014 07:27 AM, Andy Gross wrote:
Add device tree binding support for the QCOM BAM DMA driver.
Signed-off-by: Andy Gross agr...@codeaurora.org
---
.../devicetree/bindings/dma/qcom_bam_dma.txt | 52
1 file changed, 52 insertions(+)
create mode 100644
On Mon, Jan 27, 2014 at 10:36:25PM -0500, Benjamin Tissoires wrote:
On Tue, Jan 14, 2014 at 5:13 AM, Mika Westerberg
mika.westerb...@linux.intel.com wrote:
This patch adds runtime PM support for the HID over I2C driver. When the
i2c-hid device is first opened we power it on and on the last
Hi Daniel,
On Tue, Jan 28, 2014 at 03:55:57PM +0900, Daniel Jeong wrote:
Add additional FLASH Fault bits to dectect faults from chip.
Some Flash drivers support UVLO, IVFM, NTC Trip faults.
UVLO :Under Voltage Lock Out Threshold crossed
IVFM :IVFM block reported and/or
On Tue, 28 Jan 2014, Tang Chen wrote:
On-stack variable numa_kernel_nodes in numa_clear_kernel_node_hotplug()
was not initialized. So we need to initialize it.
Signed-off-by: Tang Chen tangc...@cn.fujitsu.com
Tested-by: Gu Zheng guz.f...@cn.fujitsu.com
Reported-by: David Rientjes
On Tue, Jan 28, Benjamin Herrenschmidt wrote:
So here's my next branch for powerpc. A bit late as I was on vacation
This breaks booting on G5 11,2, the nouveau driver prints errors and as
result the kernel hangs, fans kick in. This is what I did:
# Rebase 54c0a4b..b2e448e onto 54c0a4b
I will
On Tuesday 28 January 2014 10:05:35 Lars-Peter Clausen wrote:
+
+Clients must use the format described in the dma.txt file, using a three
cell
+specifier for each channel.
+
+The three cells in order are:
+ 1. A phandle pointing to the DMA controller
+ 2. The channel number
+
From: Geert Uytterhoeven geert+rene...@linux-m68k.org
Signed-off-by: Geert Uytterhoeven geert+rene...@linux-m68k.org
---
v5:
- Define interrupts in terms of interrupt-names in bindings
- No code changes
v4:
- Clarify SoCtype and interrupts
- Add clock property
- Add QSPI example
- Add
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:
A new binary interface to be able to query and modify the LPAR scheduler
weight and cap settings. Some improvements for the hvc
At Mon, 27 Jan 2014 20:54:37 +,
Mark Brown wrote:
On Mon, Jan 27, 2014 at 08:49:15PM +, Russell King - ARM Linux wrote:
On Mon, Jan 27, 2014 at 08:44:41PM +, Mark Brown wrote:
Can this parsing code be factored out - it (or large parts of it) should
be usable by other HDMI
Initialization of the admin queue interrupt number within
nvme_dev_map() is confusing. Just keep nvme_dev_map() and
nvme_dev_unmap() counterparts simple and let deal function
nvme_configure_admin_queue() with the admin queue in full.
Signed-off-by: Alexander Gordeev agord...@redhat.com
---
On Fri, Jan 24, 2014 at 10:08:35AM +, Tommaso Cucinotta wrote:
We should also again talk about what it would take to allow
unprivileged access to SCHED_DEADLINE. The things I can remember are the
obvious cap on utilization and a minimum period -- the latter so that we
don't DoS the
From: Geert Uytterhoeven geert+rene...@linux-m68k.org
This reverts commit e120cc0dcf2880a4c5c0a6cb27b655600a1cfa1d.
It causes a NULL pointer dereference with drivers using the generic
spi_transfer_one_message(), which always calls
spi_finalize_current_message(), which zeroes master-cur_msg.
On Tue, 2014-01-28 at 01:03 +, Julien Grall wrote:
On ARM, address size can be 32 bits or 64 bits (if
CONFIG_ARCH_PHYS_ADDR_T_64BIT
is enabled).
We can't assume that the grant frame base address will always fits in an
unsigned long. Use phys_addr_t instead of unsigned long as argument
On Tue, 2014-01-28 at 11:04 +0200, Tomi Valkeinen wrote:
On 2014-01-27 20:41, Christoph Fritz wrote:
On Mon, 2014-01-27 at 19:30 +0200, Ivaylo Dimitrov wrote:
linux-next-20140124 DSS is broken on N900 - display stays black (there
is some noise though). I booted the kernel with qemu and it
On Mon, Jan 27, 2014 at 10:33:40PM -0800, David Rientjes wrote:
It seems like Tejun would obviously be a maintainer as well?
No, I'm not. Li has final say on what goes in for cpuset and they may
even go through other trees.
Thanks.
--
tejun
--
To unsubscribe from this list: send the line
[CCing Ralf for MIPS.]
On Mon 27-01-14 17:45:44, Borislav Petkov wrote:
On Mon, Jan 27, 2014 at 08:41:09AM -0800, H. Peter Anvin wrote:
I don't think it'd hurt... although I think the above pretty much
requires that the code contain actual floating-point types to ever be
generated.
Yes,
Diploma?
http://ow.ly/t16ME
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Hi Konrad,
If cpufreq_register_driver() fails we would free the acpi driver
related structures but not free the ones allocated
by acpi_cpufreq_boost_init() function. This meant that as
the driver error-ed out and a CPU online/offline event came
we would crash and burn as one of the CPU
Function nvme_setup_io_queues() is quite big - make it more
readable by moving out a code with clearly distinguishable
functionality. This update is the first in a series.
Signed-off-by: Alexander Gordeev agord...@redhat.com
---
drivers/block/nvme-core.c | 28 +---
1
On 2014-01-28 11:35, Christoph Fritz wrote:
On Tue, 2014-01-28 at 11:04 +0200, Tomi Valkeinen wrote:
On 2014-01-27 20:41, Christoph Fritz wrote:
On Mon, 2014-01-27 at 19:30 +0200, Ivaylo Dimitrov wrote:
linux-next-20140124 DSS is broken on N900 - display stays black (there
is some noise
On Fri, Jan 17, 2014 at 05:02:18PM +0100, Alexander Gordeev wrote:
As result deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range() and pci_enable_msix_range()
On Mon, Jan 27, 2014 at 05:03:44PM -0500, r...@redhat.com wrote:
From: Rik van Riel r...@redhat.com
Use the active_nodes nodemask to make smarter decisions on NUMA migrations.
In order to maximize performance of workloads that do not fit in one NUMA
node, we want to satisfy the following
On Mon, Jan 27, 2014 at 05:03:45PM -0500, r...@redhat.com wrote:
From: Rik van Riel r...@redhat.com
Tracing the code that decides the active nodes has made it abundantly clear
that the naive implementation of the faults_from code has issues.
Specifically, the garbage collector in some
Hi Linus,
please pull these Microblaze patches to your tree.
Thanks,
Michal
The following changes since commit d8ec26d7f8287f5788a494f56e8814210f0e64be:
Linux 3.13 (2014-01-19 18:40:07 -0800)
are available in the git repository at:
git://git.monstr.eu/linux-2.6-microblaze.git
On 01/27/2014 11:29 PM, Luca Abeni wrote:
Hi Steven,
On Mon, 27 Jan 2014 12:09:38 -0500
Steven Rostedt rost...@goodmis.org wrote:
[...]
Lets take a case where deadline == period. It seems that the above
would be true any time there was any delay to starting the task
or the task was
On 01/28/2014 03:39 PM, zhuyj wrote:
On 01/28/2014 03:32 PM, zhuyj wrote:
On 01/27/2014 08:59 PM, Nicolas Dichtel wrote:
Le 27/01/2014 11:39, zhuyj a écrit :
Hi, Maintainers
In our scene, we will create the 6in4/6to4 tunnel firstly and need
to check the
tunnel type, secondly, we will
2014년 01월 28일 18:08, Sakari Ailus 쓴 글:
Hi Daniel,
On Tue, Jan 28, 2014 at 03:55:57PM +0900, Daniel Jeong wrote:
Add additional FLASH Fault bits to dectect faults from chip.
Some Flash drivers support UVLO, IVFM, NTC Trip faults.
UVLO : Under Voltage Lock Out Threshold crossed
IVFM : IVFM
If that is intentional it needs a big huge freaking comment recording why it is
not a bug. I would expect that to generate a FP multiply.
On January 28, 2014 1:37:01 AM PST, Michal Hocko mho...@suse.cz wrote:
[CCing Ralf for MIPS.]
On Mon 27-01-14 17:45:44, Borislav Petkov wrote:
On Mon, Jan
On Mon, Jan 27, 2014 at 06:33:44PM -0800, Guenter Roeck wrote:
I confirmed that your two patches (regulator: core: Correct default
return value for full constraints and ACPI: Flag use of ACPI and ACPI
idioms for power supplies to regulator API) together fix the problem
with the lm90 driver,
On Sat, 25 Jan 2014, Andi Kleen wrote:
On Sat, Jan 25, 2014 at 02:35:58PM -0200, Henrique de Moraes Holschuh wrote:
On Fri, 24 Jan 2014, Andi Kleen wrote:
For testing purposes it can be useful to downgrade microcode.
Normally the driver only allows upgrading.
The code is not prepared
On Tue, Jan 28, 2014 at 10:45:46AM +0200, Tomi Valkeinen wrote:
Russell, I'd like to understand why you think the original example is bad:
rate = clk_round_rate(clk, rate);
clk_set_rate(clk, rate);
It's needlessly wasteful. All the processing for setting the rate is
repeated.
On Tue 28-01-14 02:25:09, H. Peter Anvin wrote:
If that is intentional it needs a big huge freaking comment recording
why it is not a bug.
Agreed.
I would expect that to generate a FP multiply.
Exactly! And actually the very same construct in a module provided to
reproduce an issue was a
On 28/01/14 00:34, Julien Grall wrote:
On ARM, xen_init_IRQ (which calls xen_evtchn_fifo_init) is called after
all CPUs are online. It would mean that the notifier will never be called.
Why does ARM call xen_init_IRQ() so late? Is it possible to call it
earlier when only the boot CPU is
On 01/28/2014 08:26 AM, Kirill Tkhai wrote:
v2: Changed comment
When p is current and it's not of dl class, then there are no other
dl taks in the rq. If we had had pushable tasks in some other rq,
^ tasks
they would have been pushed earlier. So, skip p == rq-curr case.
[This is
On 28.01.14 at 03:18, Mukesh Rathor mukesh.rat...@oracle.com wrote:
Until now, xen did not expose PSE to pvh guest, but a patch was submitted
to xen list to enable bunch of features for a pvh guest. PSE has not been
looked into for PVH, so until we can do that and test it to make sure it
On 2014-01-28 12:32, Russell King - ARM Linux wrote:
Why I'm asking this is that for me (and probably for others also if
you've seen it used in the kernel code) it feels natural to have code like:
rate = clk_round_rate(clk, rate);
/* Verify the rounded rate here to see it's
On Tue, Jan 28, 2014 at 02:31:32PM +0530, Manish Badarkhe wrote:
On Tue, Jan 28, 2014 at 2:25 PM, Heiko Stübner he...@sntech.de wrote:
I don't have a strong opinion on this and others are most likely more
qualified
to have a definitive answer, I just found it strange to exchange one
On 28/01/14 01:03, Julien Grall wrote:
On ARM, address size can be 32 bits or 64 bits (if
CONFIG_ARCH_PHYS_ADDR_T_64BIT
is enabled).
We can't assume that the grant frame base address will always fits in an
unsigned long. Use phys_addr_t instead of unsigned long as argument for
When switching the signal voltage from 3.3V to 1.8V, there should be only
one SD Clock gating and un-gating operation. Between them the SD host
controller should switch signal level to 1.8V.
However, sometimes there is an additional gating and un-gating operation
immediately after CMD11. This
Hi Thomas,
I realized that the below patch is also required for this patchset.
This patch apart, I noticed that there is also one corner case which we will
need to handle. The BROADCAST_ON notifications in periodic mode
(oneshot mode is a nop).
We will need to fail the BROADCAST_ON
On Tue, 28 Jan 2014, Jan Kara wrote:
Hum, still no luck with reproduction (either on physical machine or with
KVM). Anyway, I've looked at the code again and the previous patch had a
stupid bug (passing different pointer to fsnotify_destroy_event() than we
should have), plus also the
On Tue, Jan 28, 2014 at 10:23:57AM +0100, Takashi Iwai wrote:
Mark Brown wrote:
On Mon, Jan 27, 2014 at 08:49:15PM +, Russell King - ARM Linux wrote:
Yes, preferably as a generic ALSA helper rather than an ASoC helper -
I don't see any need for this to be ASoC specific (I have a pure
On Tue, 28 Jan 2014, Jan Kara wrote:
2b:* 4d 8b 64 c6 08 mov0x8(%r14,%rax,8),%r12 --
trapping instruction
R14 is 0x6b6b6b6b6b6b6c03, which looks like a use-after-free.
Yup. But I'm somewhat puzzled by the trace. We crash when calling
fsnotify_destroy_event()
clock-specifier to DT binding description
2. remove local variable rate
3. add local variable parent_name
4. use clk_register_fixed_factor() instead of clk_register_fixed_rate()
5. remove flag CLK_IS_ROOT
Applies to next-20140128
.../bindings/clock/moxa,moxart-clock.txt
Hi Daniel,
On 01/28/2014 02:16 PM, Daniel Lezcano wrote:
On 01/24/2014 11:21 AM, Preeti U Murthy wrote:
On 01/24/2014 02:38 PM, Daniel Lezcano wrote:
On 01/23/2014 12:15 PM, Preeti U Murthy wrote:
Hi Daniel,
Thank you for the review.
[ ... ]
---
drivers/cpuidle/cpuidle.c
At Tue, 28 Jan 2014 11:00:51 +,
Mark Brown wrote:
On Tue, Jan 28, 2014 at 10:23:57AM +0100, Takashi Iwai wrote:
Mark Brown wrote:
On Mon, Jan 27, 2014 at 08:49:15PM +, Russell King - ARM Linux wrote:
Yes, preferably as a generic ALSA helper rather than an ASoC helper -
I
On 28 January 2014 11:50, Vincent Yang vincent.yang.fuji...@gmail.com wrote:
When switching the signal voltage from 3.3V to 1.8V, there should be only
one SD Clock gating and un-gating operation. Between them the SD host
controller should switch signal level to 1.8V.
However, sometimes there
Commit 63d0f0a3c7e1 (mm/readahead.c:do_readhead(): don't check for
-readpage) unintentionally made do_readahead return 0 for all valid
files regardless of whether readahead was supported, rather than the
expected -EINVAL. This gets forwarded on to userspace, and results in
sys_readahead appearing
On Tue, Jan 28, 2014 at 10:16:53AM +0100, Arnd Bergmann wrote:
On Tuesday 28 January 2014 10:05:35 Lars-Peter Clausen wrote:
Why does the direction needs to be specified in specifier? I see two
options, either the direction per is fixed in hardware. In that case the DMA
controller node
On Tue, Jan 28, 2014 at 11:17:57AM +, Russell King - ARM Linux wrote:
On Tue, Jan 28, 2014 at 10:16:53AM +0100, Arnd Bergmann wrote:
On Tuesday 28 January 2014 10:05:35 Lars-Peter Clausen wrote:
Why does the direction needs to be specified in specifier? I see two
options, either the
* David Rientjes rient...@google.com wrote:
On Tue, 28 Jan 2014, Tang Chen wrote:
On-stack variable numa_kernel_nodes in numa_clear_kernel_node_hotplug()
was not initialized. So we need to initialize it.
Signed-off-by: Tang Chen tangc...@cn.fujitsu.com
Tested-by: Gu Zheng
Hi,
On 27.01.2014 19:37, Manish Badarkhe wrote:
Instead of #ifdef CONFIG_OF use IS_ENABLED(CONFIG_OF)
option for DT code to avoid if-deffery in code.
Signed-off-by: Manish Badarkhe badarkhe.man...@gmail.com
---
:100644 100644 b4513f2... 3e54476... M drivers/power/max8925_power.c
On Tue, Jan 28, 2014 at 11:14:19AM +, Mark Rutland wrote:
Commit 63d0f0a3c7e1 (mm/readahead.c:do_readhead(): don't check for
-readpage) unintentionally made do_readahead return 0 for all valid
files regardless of whether readahead was supported, rather than the
expected -EINVAL. This gets
* Jan Kiszka jan.kis...@siemens.com wrote:
On 2014-01-27 21:22, Andi Kleen wrote:
On Mon, Jan 27, 2014 at 08:14:06PM +0100, Jan Kiszka wrote:
apic_icr_write and its users in smpboot.c were apparently written under
the assumption that this code would only run during early boot. But
On Mon, Jan 27, 2014 at 12:20:02PM +0200, Mika Westerberg wrote:
On Sat, Jan 25, 2014 at 01:09:23AM -0800, Bin Gao wrote:
diff --git a/arch/x86/kernel/tsc.c b/arch/x86/kernel/tsc.c index
a3acbac2ee72$
--- a/arch/x86/kernel/tsc.c
+++ b/arch/x86/kernel/tsc.c
@@ -655,10 +655,11 @@
On Sun, Jan 26, 2014 at 08:54:18AM -0200, Jose Alonso wrote:
I observed that there are for_each macros that do an extra memory access
beyond the defined area.
Normally this does not cause problems.
But, this can cause exceptions. For example: if the area is allocated at
the end of a page
Hi!
How is this different from the unpatched kernel?
In the unpatched kernel, if you happen on reader side
to enable icanon while n_tty received all but VEOF (is this
possible at all?),
then the buffer will be flushed, and the remaining VEOF
will get you a nice EOF.
So, in the unpatched
* Geert Uytterhoeven ge...@linux-m68k.org wrote:
On Sun, Jan 26, 2014 at 9:25 PM, Ingo Molnar mi...@kernel.org wrote:
* Ingo Molnar mi...@kernel.org wrote:
* Linus Torvalds torva...@linux-foundation.org wrote:
On Sun, Jan 26, 2014 at 4:27 AM, David Howells dhowe...@redhat.com
wrote:
On Tuesday 28 January 2014 17:02:42 Vinod Koul wrote:
On Tue, Jan 28, 2014 at 11:17:57AM +, Russell King - ARM Linux wrote:
On Tue, Jan 28, 2014 at 10:16:53AM +0100, Arnd Bergmann wrote:
On Tuesday 28 January 2014 10:05:35 Lars-Peter Clausen wrote:
Why does the direction needs to be
On Tuesday 28 January 2014 13:05:10 Arnd Bergmann wrote:
On Tuesday 28 January 2014 17:02:42 Vinod Koul wrote:
On Tue, Jan 28, 2014 at 11:17:57AM +, Russell King - ARM Linux wrote:
On Tue, Jan 28, 2014 at 10:16:53AM +0100, Arnd Bergmann wrote:
On Tuesday 28 January 2014 10:05:35
On 2014-01-28 12:55, Ingo Molnar wrote:
* Jan Kiszka jan.kis...@siemens.com wrote:
On 2014-01-27 21:22, Andi Kleen wrote:
On Mon, Jan 27, 2014 at 08:14:06PM +0100, Jan Kiszka wrote:
apic_icr_write and its users in smpboot.c were apparently written under
the assumption that this code would
Em Mon, Jan 27, 2014 at 08:12:42PM -0800, Davidlohr Bueso escreveu:
On Fri, 2014-01-24 at 10:13 -0800, Darren Hart wrote:
I agree that we should take whatever makes sense for perf out of
futex-test and merge it with perf. It will see greater use and receive
more review and improvements than
601 - 700 of 1194 matches
Mail list logo
