Commit-ID: fb74fbda42dc5bcbd9bae5d75bfb6755948db21d
Gitweb: http://git.kernel.org/tip/fb74fbda42dc5bcbd9bae5d75bfb6755948db21d
Author: Masami Hiramatsu masami.hiramatsu...@hitachi.com
AuthorDate: Thu, 14 Aug 2014 02:22:47 +
Committer: Arnaldo Carvalho de Melo a...@redhat.com
On Mon, 2014-08-18 at 16:33 +1000, NeilBrown wrote:
Hi Ian,
Have you had a chance to run your tests in these patches yet?
I've done what testing I can think of and cannot fault them.
I haven't, I've been plagued with illness so I'm not getting nearly
enough done. I'll try to put a kernel
Commit-ID: 35550da389ba8752f024a44ef14b74001c4fc4d3
Gitweb: http://git.kernel.org/tip/35550da389ba8752f024a44ef14b74001c4fc4d3
Author: Masami Hiramatsu masami.hiramatsu...@hitachi.com
AuthorDate: Thu, 14 Aug 2014 02:22:43 +
Committer: Arnaldo Carvalho de Melo a...@redhat.com
Commit-ID: 6e81c74cbf4b64620170da14844f1dc8a9a5950f
Gitweb: http://git.kernel.org/tip/6e81c74cbf4b64620170da14844f1dc8a9a5950f
Author: Masami Hiramatsu masami.hiramatsu...@hitachi.com
AuthorDate: Thu, 14 Aug 2014 02:22:36 +
Committer: Arnaldo Carvalho de Melo a...@redhat.com
Commit-ID: 5f03cba41590b5e7db5b66d2b2aa3e146ff8a84f
Gitweb: http://git.kernel.org/tip/5f03cba41590b5e7db5b66d2b2aa3e146ff8a84f
Author: Masami Hiramatsu masami.hiramatsu...@hitachi.com
AuthorDate: Thu, 14 Aug 2014 02:22:34 +
Committer: Arnaldo Carvalho de Melo a...@redhat.com
Commit-ID: 942a91ed30267944ed3161ae292d0960fd44
Gitweb: http://git.kernel.org/tip/942a91ed30267944ed3161ae292d0960fd44
Author: Masami Hiramatsu masami.hiramatsu...@hitachi.com
AuthorDate: Thu, 14 Aug 2014 02:22:41 +
Committer: Arnaldo Carvalho de Melo a...@redhat.com
Commit-ID: f9f33fdba159a9c163ecf1dc0106ebd4c2498130
Gitweb: http://git.kernel.org/tip/f9f33fdba159a9c163ecf1dc0106ebd4c2498130
Author: Masami Hiramatsu masami.hiramatsu...@hitachi.com
AuthorDate: Thu, 14 Aug 2014 02:22:51 +
Committer: Arnaldo Carvalho de Melo a...@redhat.com
Commit-ID: 809adea685f7dbc9bdcc38b27d24801c461d8413
Gitweb: http://git.kernel.org/tip/809adea685f7dbc9bdcc38b27d24801c461d8413
Author: Masami Hiramatsu masami.hiramatsu...@hitachi.com
AuthorDate: Thu, 14 Aug 2014 02:22:38 +
Committer: Arnaldo Carvalho de Melo a...@redhat.com
Add Device Tree binding documentation for the clocks
outputs in the Maxim 77802 Power Management IC.
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
Acked-by: Mike Turquette mturque...@linaro.org
---
Changes since v6: None
Changes since v5:
- Fix typo error in DT
The max77686 mfd driver adds a regmap IRQ chip which creates an
IRQ domain that is used to map the virtual RTC alarm1 interrupt.
The RTC driver assumes that this will always be true since the
PMIC IRQ is a required property according to the max77686 DT
binding doc. If an interrupts property is
for the max77686 rtc.
The series were tested on an Exynos5250 Snow (max77686) and
Exynos5420 Peach Pit (max77802) machines and applies cleanly
to both 3.17-rc1 and today's linux-next (20140818).
Doug Anderson (1):
rtc: max77686: Allow the max77686 rtc to wakeup the system
Javier Martinez Canillas (4
From: Doug Anderson diand...@chromium.org
The max77686 includes an RTC that keeps power during suspend. It's
convenient to be able to use it as a wakeup source.
NOTE: due to wakeup ordering problems this patch alone doesn't work so
well on exynos5250-snow. You also need something that brings
Add Device Tree binding documentation for the regulators
present in the Maxim 77802 Power Management IC.
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
---
.../devicetree/bindings/regulator/max77802.txt | 53 ++
1 file changed, 53 insertions(+)
Maxim Integrated Power Management ICs are very similar with
regard to their clock outputs. Most of the clock drivers for
these chips are duplicating code and are simpler enough that
can be converted to use a generic driver to consolidate code
and avoid duplication.
Signed-off-by: Javier Martinez
This patch adds a dt-binding include for Maxim 77686
PMIC clock IDs that can be used by both the max77686
clock driver and Device Tree source files.
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
Reviewed-by: Krzysztof Kozlowski k.kozlow...@samsung.com
Reviewed-by: Mike
The MAX77686 RTC chip has two features called SMPL (Sudden Momentary
Power Loss) and WTSR (Watchdog Timeout and Software Resets).
Support for these features seems to be implemented in the driver but
compilation is disabled using a C pre-processor conditional.
This code has been disabled since the
Build kernel with SND_SOC_IMC_PCM_DMA=m SND_IMX_SOC=n leads the following
error:
sound/built-in.o: In function `fsl_sai_probe':
fsl_sai.c:(.text+0x5f662): undefined reference to `imx_pcm_dma_init'
sound/built-in.o: In function `fsl_esai_probe':
fsl_esai.c:(.text+0x6044b): undefined
If devm_rtc_device_register() fails a dev_err() is already
reported so there is no need to do an additional dev_info().
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
---
drivers/rtc/rtc-max77686.c | 2 --
1 file changed, 2 deletions(-)
diff --git
The MAX77802 PMIC has 10 high-efficiency Buck and 32 Low-dropout
(LDO) regulators. This patch adds support for all these regulators
found on the MAX77802 PMIC and is based on a driver added by Simon
Glass to the Chrome OS kernel 3.8 tree.
Signed-off-by: Javier Martinez Canillas
Like most clock drivers, the Maxim 77686 PMIC clock binding
follows the convention that the #clock-cells property is
used to specify the number of cells in a clock provider.
But the binding document is not clear enough that it shall
be set to 1 since the PMIC support multiple clocks outputs.
Clocks drivers for Maxim PMIC are very similar so they can
be converted to use the generic Maxim clock driver.
Also, while being there use module_platform_driver() helper
macro to eliminate more boilerplate code.
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
on the max77802 driver
since v7 of the old series.
The series were tested on an Exynos5420 based Peach Pit board
and applies cleanly to both 3.17-rc1 and today's next-20140818.
Javier Martinez Canillas (2):
regulator: Add driver for max77802 PMIC PMIC regulators
regulator: Add DT bindings
Building kernel with SND_SOC_IMX_AUDMUX=n leads to the following error:
sound/built-in.o: In function `fsl_asoc_card_probe':
fsl-asoc-card.c:(.text+0x1467b5): undefined reference to
`imx_audmux_v2_configure_port'
fsl-asoc-card.c:(.text+0x1467d0): undefined reference to
The MAX7802 PMIC has a Real-Time-Clock (RTC) with two alarms.
This patch adds support for the RTC and is based on a driver
added by Simon Glass to the Chrome OS kernel 3.8 tree.
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
Reviewed-by: Krzysztof Kozlowski
the patches had been
already acked by you so I hope there won't be issues to get
them merged.
The series were tested on an Exynos5250 Snow (max77686) and
Exynos5420 Peach Pit (max77802) machines and applies cleanly
to both 3.17-rc1 and today's linux-next (20140818).
Javier Martinez Canillas (6):
clk
Il 13/08/2014 16:21, Nadav Amit ha scritto:
Correction: the word “never” in the message is too harsh.
Nonetheless, there is a regression bug. I encountered it with “wrfsbase”
instruction.
So KVM is emulating wrfsbase even if the host doesn't support it?
I'm swapping the order of the two
The MAX77802 PMIC has two 32.768kHz Buffered Clock Outputs with
Low Jitter Mode. This patch adds support for these two clocks.
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
Reviewed-by: Krzysztof Kozlowski k.kozlow...@samsung.com
Acked-by: Mike Turquette
On Thu, 14 Aug 2014, Brian Norris wrote:
On Wed, Aug 13, 2014 at 10:11:59AM +0100, Lee Jones wrote:
Hi Brian, Pekon,
I believe all of your queries have either been answered or addressed
and I am hoping this will be the last submission. :)
/me crosses fingers!
Kind regards,
When build fsl-asoc-card as module, there is following error:
sound/soc/fsl/fsl-asoc-card.c: In function 'fsl_asoc_card_probe':
sound/soc/fsl/fsl-asoc-card.c:547:13: warning: 'asrc_np' may be used
uninitialized in this function [-Wmaybe-uninitialized]
of_node_put(asrc_np);
This series patch is for fixing build error/waring in sound/soc/fsl
Shengjiu Wang (3):
ASoC: fsl: Kconfig: remove dependence of SND_IMX_SOC for
SND_SOC_IMX_PCM_DMA
ASoC: fsl-asoc-card: Fix build warning for maybe-uninitialized
ASoC: fsl: fsl-asoc-card: Select SND_SOC_IMX_AUDMUX
Hi Thierry,
On Mon, Aug 18, 2014 at 10:20 AM, Thierry Reding
thierry.red...@gmail.com wrote:
Could we achieve the same by storing a pointer to the best match and
then use that instead of p? Perhaps something like this:
struct pwm_lookup *entry;
...
if
On Sun, 17 Aug 2014 12:45:31 -0600, Jens Axboe ax...@fb.com wrote:
On 2014-08-16 09:55, Dmitry Monakhov wrote:
Signed-off-by: Dmitry Monakhov dmonak...@openvz.org
You forgot a commit message justifying this change?
I've assumed that one line comment is enough :(
Please take a look at the
Currently kick_all_cpus_sync() or smp_call_function() can not
break the polling idle cpu immediately.
Here using wake_up_all_cpus() which can wake up the polling idle
cpu quickly is much helpful for power.
Signed-off-by: Chuansheng Liu chuansheng@intel.com
---
drivers/cpuidle/cpuidle.c |
On 2014-08-18 04:43, Chase Southwood wrote:
We initialize 'irqbit' to 0, only to properly set it immediately
afterwards. Just remove the zero-initialization.
Signed-off-by: Chase Southwood chase.southw...@gmail.com
Cc: Ian Abbott abbo...@mev.co.uk
Cc: H Hartley Sweeten
On 2014-08-18 04:43, Chase Southwood wrote:
cppcheck was complaining that the variable 'stat' is being reassigned
before the old value is used. Upon inspection, I found that
dt2801_writecmd() cannot fail, always returns 0, and most callers already
do not bother with assigning its return value
Dear Randy,
thanks for you reply.
* Randy Dunlap rdun...@infradead.org [140818 09:37]:
On 08/17/14 11:30, Markus Osterhoff wrote:
diff --git a/Documentation/HOWTO b/Documentation/HOWTO
-gcc`) for some information on them.
+gcc') for some information on them.
Backquotes imply that the
Currently kick_all_cpus_sync() can break non-polling idle cpus
thru IPI interrupts.
But sometimes we need to break the polling idle cpus immediately
to reselect the suitable c-state, also for non-idle cpus, we need
to do nothing if we try to wake up them.
Here adding one new function
At Sun, 17 Aug 2014 20:21:38 +0200,
Oleg Nesterov wrote:
On 08/17, Luis R. Rodriguez wrote:
In the last iteration that I have stress tested for corner cases I just
get_task_struct() on the init and then put_task_struct() at the exit, is
that
fine too or are there reasons to prefer
Signed-off-by: Alexander Gordeev agord...@redhat.com
Cc: Anil Ravindranath anil_ravindran...@pmc-sierra.com
Cc: linux-s...@vger.kernel.org
Cc: linux-...@vger.kernel.org
---
drivers/scsi/pmcraid.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/scsi/pmcraid.c b/drivers/scsi/pmcraid.c
* Don Zickus dzic...@redhat.com wrote:
From: Ulrich Obergfell uober...@redhat.com
This patch avoids printing the message 'enabled on all CPUs, ...'
multiple times. For example, the issue can occur in the following
scenario:
1) watchdog_nmi_enable() fails to enable PMU counters and sets
As result of 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() or pci_enable_msi_exact()
and pci_enable_msix_range() or pci_enable_msix_exact()
interfaces.
* Don Zickus dzic...@redhat.com wrote:
From: chai wen chaiw.f...@cn.fujitsu.com
For now, soft lockup detector warns once for each case of process softlockup.
But the thread 'watchdog/n' may not always get the cpu at the time slot
between
the task switch of two processes hogging that cpu
Currently the driver fails to analize MSI-X re-enablement
status on resuming and always assumes the success. This
update checks the MSI-X initialization result and fails
to resume if MSI-Xs re-enablement failed.
Signed-off-by: Alexander Gordeev agord...@redhat.com
Acked-by: Kashyap Desai
On Sat, Aug 16, 2014 at 05:38:30PM +0200, Philippe Reynes wrote:
Hi all,
i.MX27's usb needs three clocks (usb_ipg_gate, usb_ahb_gate and usb_div)
but the current chipidea driver implementation, and devicetree, provides
only ipg and ahb. Consequently, if the bootloader don't enable the last
As result of 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() or pci_enable_msi_exact()
and pci_enable_msix_range() or pci_enable_msix_exact()
interfaces.
If intel_iommu is enabled, when kdump kernel boots, the old root entry
should be cleared, otherwise it may cause DMAR error.
To make it works for more enviroments, this patch does not use
is_kdump_kernel() to check it, but reads the register to check whether
hardware is using old root entry.
On 2014-8-18 16:27, Mika Westerberg wrote:
On Mon, Aug 18, 2014 at 04:13:29PM +0800, Hanjun Guo wrote:
Hi,
Some minor comments below.
On 2014-8-17 14:04, Mika Westerberg wrote:
Device Tree is used in many embedded systems to describe the system
configuration to the OS. It supports
Currently the driver falls back to INTx mode when MSI-X
initialization failed. This is a suboptimal behaviour
for chips that also support MSI. This update changes that
behaviour and falls back to MSI mode in case MSI-X mode
initialization failed.
Signed-off-by: Alexander Gordeev
Implementing one new API wake_up_if_idle(), which is used to
wake up the idle CPU.
Suggested-by: Andy Lutomirski l...@amacapital.net
Signed-off-by: Chuansheng Liu chuansheng@intel.com
---
include/linux/sched.h |1 +
kernel/sched/core.c | 16
2 files changed, 17
As result of 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() or pci_enable_msi_exact()
and pci_enable_msix_range() or pci_enable_msix_exact()
interfaces.
Hello,
This series is against 3.17-rc1. Patches 0-7 have been acked.
Patches 8-13 still need reviews and are resent without changes
except 'lpfc' which concerns latest James comments.
Thanks!
As result of deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block()
As result of 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() or pci_enable_msi_exact()
and pci_enable_msix_range() or pci_enable_msix_exact()
interfaces.
On Mon, Aug 18, 2014 at 10:38:00AM +0200, Geert Uytterhoeven wrote:
Hi Thierry,
On Mon, Aug 18, 2014 at 10:20 AM, Thierry Reding
thierry.red...@gmail.com wrote:
Could we achieve the same by storing a pointer to the best match and
then use that instead of p? Perhaps something like this:
As result of 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() or pci_enable_msi_exact()
and pci_enable_msix_range() or pci_enable_msix_exact()
interfaces.
Log
As result of 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() or pci_enable_msi_exact()
and pci_enable_msix_range() or pci_enable_msix_exact()
interfaces.
There is no need to call pci_disable_msix() in case
the previous call to pci_enable_msix() failed
Signed-off-by: Alexander Gordeev agord...@redhat.com
Cc: Naresh Kumar Inna nar...@chelsio.com
Cc: Arvind Bhushan arvi...@chelsio.com
Cc: linux-s...@vger.kernel.org
Cc: linux-...@vger.kernel.org
---
As result of 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() or pci_enable_msi_exact()
and pci_enable_msix_range() or pci_enable_msix_exact()
interfaces.
As result of 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()
interfaces.
Signed-off-by: Alexander Gordeev agord...@redhat.com
Cc:
As result of 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() or pci_enable_msi_exact()
and pci_enable_msix_range() or pci_enable_msix_exact()
interfaces.
On 08.08.2014 14:36, Linus Walleij wrote:
On Thu, Jul 24, 2014 at 5:51 PM, Tomasz Nowicki
tomasz.nowi...@linaro.org wrote:
GPIO signaled events is quite new thing in Linux kernel.
AFAIK, there are not many board which can take advantage of it.
However, GPIO events are very useful feature
* Don Zickus dzic...@redhat.com wrote:
From: Ulrich Obergfell uober...@redhat.com
In some cases we don't want hard lockup detection enabled by default.
An example is when running as a guest. Introduce
watchdog_enable_hardlockup_detector(bool)
So, the name
On 13 August 2014 17:13, Doug Anderson diand...@chromium.org wrote:
If we happened to get a data error at just the wrong time the dw_mmc
driver could get into a state where it would never complete its
request. That would leave the caller just hanging there.
We fix this two ways and both of
Hi Michal,
On Tue, Aug 12, 2014 at 3:07 PM, Michal Simek mon...@monstr.eu wrote:
Hi Bjorn,
On 07/30/2014 01:24 PM, Srikanth Thokala wrote:
Hi Arnd,
On Mon, Jul 28, 2014 at 6:32 PM, Arnd Bergmann a...@arndb.de wrote:
On Monday 28 July 2014 18:04:34 Srikanth Thokala wrote:
Hi Arnd and Rob,
* Don Zickus dzic...@redhat.com wrote:
The running kernel still has the ability to enable/disable at any
time with /proc/sys/kernel/nmi_watchdog us usual. However even
when the default has been overridden /proc/sys/kernel/nmi_watchdog
will initially show '1'. To truly turn it on one must
Le Fri, 8 Aug 2014 13:50:52 -0600,
David Ahern dsah...@gmail.com a écrit :
On 8/8/14, 10:40 AM, Matthieu CASTET wrote:
Hi,
I have a 64 bits kernel running with 32 bits binaries.
If I run 32 bits perf on this 64 bits kernel 3.14, I got weird result :
- perf trace doesn't work [1]
I
* Don Zickus dzic...@redhat.com wrote:
--- a/kernel/watchdog.c
+++ b/kernel/watchdog.c
@@ -522,6 +522,9 @@ static void watchdog_nmi_disable(unsigned int cpu)
/* should be in cleanup, but blocks oprofile */
perf_event_release_kernel(event);
}
+ if (cpu
On Mon, Aug 18, 2014 at 05:00:59PM +0800, Peter Chen wrote:
On Sat, Aug 16, 2014 at 05:38:30PM +0200, Philippe Reynes wrote:
Hi all,
i.MX27's usb needs three clocks (usb_ipg_gate, usb_ahb_gate and usb_div)
but the current chipidea driver implementation, and devicetree, provides
only
On 12.08.2014 12:01, Mika Westerberg wrote:
On Fri, Aug 08, 2014 at 02:36:02PM +0200, Linus Walleij wrote:
On Thu, Jul 24, 2014 at 5:51 PM, Tomasz Nowicki
tomasz.nowi...@linaro.org wrote:
GPIO signaled events is quite new thing in Linux kernel.
AFAIK, there are not many board which can take
On Sun, Aug 17, 2014 at 01:54:16PM +0100, Grant Likely wrote:
On Sun, 17 Aug 2014 09:04:14 +0300, Mika Westerberg
mika.westerb...@linux.intel.com wrote:
From: Aaron Lu aaron...@intel.com
With the unified device properties interface in place, add device tree
support.
By adding the
On 2014-8-15 18:01, Catalin Marinas wrote:
Hanjun,
Hi Catalin,
On Fri, Aug 15, 2014 at 10:09:42AM +0100, Hanjun Guo wrote:
On 2014-8-14 18:27, Catalin Marinas wrote:
On Thu, Aug 14, 2014 at 04:21:25AM +0100, Hanjun Guo wrote:
On 2014-8-14 7:41, Rafael J. Wysocki wrote:
On Tuesday, August
On 12.08.2014 16:15, Alexandre Courbot wrote:
On Tue, Aug 12, 2014 at 3:01 AM, Mika Westerberg
mika.westerb...@linux.intel.com wrote:
On Fri, Aug 08, 2014 at 02:36:02PM +0200, Linus Walleij wrote:
On Thu, Jul 24, 2014 at 5:51 PM, Tomasz Nowicki
tomasz.nowi...@linaro.org wrote:
GPIO signaled
3.11.10.15 -stable review patch. If anyone has any objections, please let me
know.
--
From: John David Anglin dave.ang...@bell.net
commit 20dbea494543aefaace874cc3ec93a39b94b1ec4 upstream.
The sa_restorer field in struct sigaction is obsolete and no longer in
the parisc
3.11.10.15 -stable review patch. If anyone has any objections, please let me
know.
--
From: Mikulas Patocka mpato...@redhat.com
commit 3b3a1814d1703027f9867d0f5cbbfaf6c7482474 upstream.
This patch provides the compat BLKZEROOUT ioctl. The argument is a pointer
to two uint64_t
3.11.10.15 -stable review patch. If anyone has any objections, please let me
know.
--
From: David S. Miller da...@davemloft.net
commit aa3449ee9c87d9b7660dd1493248abcc57769e31 upstream.
Only the second argument, 'op', is signed.
Signed-off-by: David S. Miller
3.11.10.15 -stable review patch. If anyone has any objections, please let me
know.
--
From: Sasha Levin sasha.le...@oracle.com
commit 06ebb06d49486676272a3c030bfeef4bd969a8e6 upstream.
Check for cases when the caller requests 0 bytes instead of running off
and dereferencing
3.11.10.15 -stable review patch. If anyone has any objections, please let me
know.
--
From: zhangwei(Jovi) jovi.zhang...@huawei.com
commit 8abfb8727f4a724d31f9ccfd8013fbd16d539445 upstream.
Currently trace option stacktrace is not applicable for
trace_printk with constant
3.11.10.15 -stable review patch. If anyone has any objections, please let me
know.
--
From: Andrey Utkin andrey.krieger.ut...@gmail.com
commit 093758e3daede29cb4ce6aedb111becf9d4bfc57 upstream.
This commit is a guesswork, but it seems to make sense to drop this
break, as
3.11.10.15 -stable review patch. If anyone has any objections, please let me
know.
--
From: Christoph Lameter c...@linux.com
commit 3e374919b314f20e2a04f641ebc1093d758f66a4 upstream.
SLUB can alias multiple slab kmem_create_requests to one slab cache to save
memory and
3.11.10.15 -stable review patch. If anyone has any objections, please let me
know.
--
From: Christoph Paasch christoph.paa...@uclouvain.be
commit 1f74e613ded11517db90b2bd57e9464d9e0fb161 upstream.
In vegas we do a multiplication of the cwnd and the rtt. This
may overflow and
3.11.10.15 -stable review patch. If anyone has any objections, please let me
know.
--
From: Konstantin Khlebnikov k.khlebni...@samsung.com
commit 811a2407a3cf7bbd027fbe92d73416f17485a3d8 upstream.
On LPAE, each level 1 (pgd) page table entry maps 1GiB, and the level 2
(pmd)
3.11.10.15 -stable review patch. If anyone has any objections, please let me
know.
--
From: Li RongQing roy.qing...@gmail.com
commit 916c1689a09bc1ca81f2d7a34876f8d35aadd11b upstream.
skb_cow called in vlan_reorder_header does not free the skb when it failed,
and
3.11.10.15 -stable review patch. If anyone has any objections, please let me
know.
--
From: Eric Dumazet eduma...@google.com
commit 73f156a6e8c1074ac6327e0abd1169e95eb66463 upstream.
Ideally, we would need to generate IP ID using a per destination IP
generator.
linux kernels
3.11.10.15 -stable review patch. If anyone has any objections, please let me
know.
--
From: Martin Lau ka...@fb.com
commit 97b8ee845393701edc06e27ccec2876ff9596019 upstream.
ring_buffer_poll_wait() should always put the poll_table to its wait_queue
even there is immediate
3.11.10.15 -stable review patch. If anyone has any objections, please let me
know.
--
From: Thomas Petazzoni thomas.petazz...@free-electrons.com
commit 4d12bc63ab5e48c1d78fa13883cf6fefcea3afb1 upstream.
As reported by Maggie Mae Roxas, the mvneta driver doesn't behave
3.11.10.15 -stable review patch. If anyone has any objections, please let me
know.
--
From: Thomas Fitzsimmons fitz...@fitzsim.org
commit 0a1985879437d14bda8c90d0dae3455c467d7642 upstream.
This commit fixes the command value generated for CSUM calculation
when running in big
This is the start of the review cycle for the Linux 3.11.10.15 stable kernel.
PLEASE NOTE:
This will be the LAST 3.11.y.z extended stable kernel release.
This version contains 137 new patches, summarized below. The new patches are
posted as replies to this message and also available in this
3.11.10.15 -stable review patch. If anyone has any objections, please let me
know.
--
From: David Rientjes rient...@google.com
commit b104a35d32025ca740539db2808aa3385d0f30eb upstream.
The page allocator relies on __GFP_WAIT to determine if ALLOC_CPUSET
should be set in
3.11.10.15 -stable review patch. If anyone has any objections, please let me
know.
--
From: HATAYAMA Daisuke d.hatay...@jp.fujitsu.com
commit b292d7a10487aee6e74b1c18b8d95b92f40d4a4f upstream.
Currently, any NMI is falsely handled by a NMI handler of NMI watchdog
if CondChgd
3.11.10.15 -stable review patch. If anyone has any objections, please let me
know.
--
From: Eric Dumazet eduma...@google.com
commit 04ca6973f7c1a0d8537f2d9906a0cf8e69886d75 upstream.
In Counting Packets Sent Between Arbitrary Internet Hosts, Jeffrey and
Jedidiah describe ways
Hi Varka Bhadram,
On Tue, Aug 5, 2014 at 5:29 PM, Varka Bhadram varkabhad...@gmail.com wrote:
On 08/05/2014 05:09 PM, Srikanth Thokala wrote:
Device-tree binding documentation of Xilinx Central DMA Engine
Signed-off-by: Srikanth Thokala stho...@xilinx.com
---
Changes in v2:
- Change
3.11.10.15 -stable review patch. If anyone has any objections, please let me
know.
--
From: Eric Dumazet eduma...@google.com
commit 757efd32d5ce31f67193cc0e6a56e4dffcc42fb1 upstream.
Dave reported following splat, caused by improper use of
IP_INC_STATS_BH() in process
3.11.10.15 -stable review patch. If anyone has any objections, please let me
know.
--
From: willy tarreau w...@1wt.eu
commit 290213667ab53a95456397763205e4b1e30f46b5 upstream.
If a queue timeout is reported, we can oops because of some
schedules while the caller is atomic, as
3.11.10.15 -stable review patch. If anyone has any objections, please let me
know.
--
From: Vlad Yasevich vyase...@redhat.com
commit 081e83a78db9b0ae1f5eabc2dedecc865f509b98 upstream.
Macvlan devices do not initialize vlan_features. As a result,
any vlan devices configured
3.11.10.15 -stable review patch. If anyone has any objections, please let me
know.
--
From: Mateusz Guzik mgu...@redhat.com
commit b0ab99e7736af88b8ac1b7ae50ea287fffa2badc upstream.
proc_sched_show_task() does:
if (nr_switches)
do_div(avg_atom, nr_switches);
3.11.10.15 -stable review patch. If anyone has any objections, please let me
know.
--
From: Christoph Paasch christoph.paa...@uclouvain.be
commit 45a07695bc64b3ab5d6d2215f9677e5b8c05a7d0 upstream.
In veno we do a multiplication of the cwnd and the rtt. This
may overflow and
3.11.10.15 -stable review patch. If anyone has any objections, please let me
know.
--
From: Vlad Yasevich vyase...@redhat.com
commit fcdfe3a7fa4cb74391d42b6a26dc07c20dab1d82 upstream.
When performing segmentation, the mac_len value is copied right
out of the original skb.
On 15 August 2014 08:06, rogera...@realtek.com wrote:
From: Roger Tseng rogera...@realtek.com
Current code erroneously fill the last byte of R2 response with an undefined
value. In addition, the controller actually 'offloads' the last byte
(CRC7, end bit) while receiving R2 response and thus
On 15 August 2014 08:06, rogera...@realtek.com wrote:
From: Roger Tseng rogera...@realtek.com
Current code erroneously fill the last byte of R2 response with an undefined
value. In addition, the controller actually 'offloads' the last byte
(CRC7, end bit) while receiving R2 response and thus
3.11.10.15 -stable review patch. If anyone has any objections, please let me
know.
--
From: Tejun Heo t...@kernel.org
commit 1a112d10f03e83fb3a2fdc4c9165865dec8a3ca6 upstream.
1871ee134b73 (libata: support the ata host which implements a queue
depth less than 32) directly
3.11.10.15 -stable review patch. If anyone has any objections, please let me
know.
--
From: James Bottomley jbottom...@parallels.com
commit 89fb4cd1f717a871ef79fa7debbe840e3225cd54 upstream.
Flush commands don't transfer data and thus need to be special cased
in the I/O
801 - 900 of 1499 matches
Mail list logo
