> A handful of boot panics on ARM platforms were bisected to point at
> the version of this commit that's in linux-next (commit
> 64c862a839a8db2c02bbaa88b923d13e1208919d). Reverting this commit
> makes things happy again.
>
> Upon further digging, it seems that users of devres_alloc() are
>
On Fri, 2013-10-18 at 09:57 -0700, Kevin Hilman wrote:
[]
> A handful of boot panics on ARM platforms were bisected to point at
> the version of this commit that's in linux-next (commit
> 64c862a839a8db2c02bbaa88b923d13e1208919d). Reverting this commit
> makes things happy again.
>
> Upon
If implemented properly adcx/adox should give additional speedup... that is the
whole reason for their existence.
Neil Horman wrote:
>On Sat, Oct 12, 2013 at 03:29:24PM -0700, H. Peter Anvin wrote:
>> On 10/11/2013 09:51 AM, Neil Horman wrote:
>> > Sébastien Dugué reported to me that devices
On Fri, Oct 18, 2013 at 10:06 AM, Joe Perches wrote:
> On Fri, 2013-10-18 at 09:57 -0700, Kevin Hilman wrote:
> []
>> A handful of boot panics on ARM platforms were bisected to point at
>> the version of this commit that's in linux-next (commit
>> 64c862a839a8db2c02bbaa88b923d13e1208919d).
Em Fri, Oct 18, 2013 at 10:38:48AM -0400, Waiman Long escreveu:
> When callgraph data was included in the perf data file, it may take a
> long time to scan all those data and merge them together especially
> if the stored callchains are long and the perf data file itself is
> large, like a Gbyte
On Fri, 2013-10-18 at 17:57 +0100, Will Deacon wrote:
> Hi Pablo,
>
> > We also need fixes for net/ipv6/netfilter/ip6_tables.c and
> > net/ipv4/netfilter/arp_tables.c as well. Could you extend this patch
> > and resend?
>
> Sure, I can try, but that's going to require a bit of time to sit down
On Fri, 2013-10-18 at 12:50 -0400, Neil Horman wrote:
> >
> for(i=0;i<10;i++) {
> sum = csum_partial(buf+offset, PAGE_SIZE, sum);
> offset = (offset < BUFSIZ-PAGE_SIZE) ? offset+PAGE_SIZE : 0;
> }
Please replace this by random accesses, and use the
This has been committed.
Thanks
--Rich
commit e64190f8440286a815060524777b435e06a7b364
Author: Namjae Jeon
Date: Sun Oct 6 20:13:38 2013 +
[RESEND, 4/7] xfsprogs: xfsio: add support FALLOC_FL_COLLAPSE_RANGE
for fallocate
--
To unsubscribe from this list: send the line "unsubscribe
On 10/18/2013 06:17 PM, Ezequiel Garcia wrote:
On Fri, Oct 18, 2013 at 10:47:41AM -0400, Jason Cooper wrote:
On Fri, Oct 18, 2013 at 01:54:13PM +0200, Sebastian Hesselbarth wrote:
With legacy devices converted to DT and a proper ethernet MAC
workaround, we can now remove the clk workarounds
On Thu, Oct 17, 2013 at 05:01:14PM +0800, Xiubo Li wrote:
> @@ -883,14 +883,19 @@ static int ldo_regulator_register(struct snd_soc_codec
> *codec,
> struct regulator_init_data *init_data,
> int voltage)
> {
> +#ifdef
From: Viresh Kumar
Date: Fri, 18 Oct 2013 19:29:54 +0530
> This patch converts existing .target() to newly defined light weight
> .target_index() routine for this driver.
>
> CPUFreq core will call cpufreq_frequency_table_target() before calling this
> routine and will pass index to it.
>
>
On 10/18/13 8:38 AM, Waiman Long wrote:
When callgraph data was included in the perf data file, it may take a
long time to scan all those data and merge them together especially
if the stored callchains are long and the perf data file itself is
large, like a Gbyte or so.
The callchain stack is
On 10/18/13 8:38 AM, Waiman Long wrote:
When the callgraph function is enabled (-G), it may take a long time to
scan all the stack data and merge them accordingly.
This patch adds a new --max-stack option to perf-top to limit the depth
of callchain stack data to look at to reduce the time it
On Thu, Oct 17, 2013 at 05:01:17PM +0800, Xiubo Li wrote:
> + -- Power supplies:
> + * Mic Bias
> +
> + -- SGTL5000 pins:
> + * MIC_IN
> + * LINE_IN
> + * HP_OUT
> + * LINE_OUT
Things that are part of the CODEC should be part of the CODEC binding
and this binding should
On Thu, Oct 17, 2013 at 05:01:15PM +0800, Xiubo Li wrote:
> + ret = snd_soc_register_card(_sgt1500_card);
> + if (ret) {
> + dev_err(>dev, "register soc sound card failed :%d\n",
> + ret);
> + return ret;
> + }
Use the newly added
From: Dan Williams
Add a hook for a common dma unmap implementation to enable removal of
the per driver custom unmap code. (A reworked version of Bartlomiej
Zolnierkiewicz's patches to remove the custom callbacks and the size
increase of dma_async_tx_descriptor for drivers that don't care about
[ Original patch series description by Dan. ]
dmaengine from the beginning has placed the burden of unmapping dma
buffers on the individual drivers. The thought being that since the dma
driver already has the descriptor it can use that information for
unmapping. This results in a lot of cruft
From: Dan Williams
Hang a common 'unmap' object off of dma descriptors for the purpose of
providing a unified unmapping interface. The lifetime of a mapping may
span multiple descriptors, so these unmap objects are reference counted
by related descriptor.
Cc: Vinod Koul
Cc: Tomasz Figa
Cc:
From: Dan Williams
Use the generic unmap object to unmap dma buffers.
Cc: Vinod Koul
Cc: Tomasz Figa
Cc: Dave Jiang
Reported-by: Bartlomiej Zolnierkiewicz
Signed-off-by: Dan Williams
Signed-off-by: Bartlomiej Zolnierkiewicz
Signed-off-by: Kyungmin Park
---
crypto/async_tx/async_pq.c |
From: Dan Williams
Use the generic unmap object to unmap dma buffers.
Cc: Vinod Koul
Cc: Tomasz Figa
Cc: Dave Jiang
Reported-by: Bartlomiej Zolnierkiewicz
Signed-off-by: Dan Williams
[bzolnier: minor cleanups]
Signed-off-by: Bartlomiej Zolnierkiewicz
Signed-off-by: Kyungmin Park
---
Remove support for DMA unmapping from drivers as it is no longer
needed (DMA core code is now handling it).
Cc: Vinod Koul
Cc: Tomasz Figa
Cc: Dave Jiang
Signed-off-by: Bartlomiej Zolnierkiewicz
Signed-off-by: Kyungmin Park
Signed-off-by: Dan Williams
---
Use the generic unmap object to unmap dma buffers.
As NTB can be compiled without DMA_ENGINE support add
stub functions to for dma_set_unmap(),
dmaengine_get_unmap_data() and dmaengine_unmap_put().
Cc: Dan Williams
Cc: Vinod Koul
Cc: Tomasz Figa
Cc: Dave Jiang
Cc: Jon Mason
Signed-off-by:
Remove no longer needed DMA unmap flags:
- DMA_COMPL_SKIP_SRC_UNMAP
- DMA_COMPL_SKIP_DEST_UNMAP
- DMA_COMPL_SRC_UNMAP_SINGLE
- DMA_COMPL_DEST_UNMAP_SINGLE
Cc: Vinod Koul
Cc: Tomasz Figa
Cc: Dave Jiang
Signed-off-by: Bartlomiej Zolnierkiewicz
Signed-off-by: Kyungmin Park
Signed-off-by: Dan
On Fri, Oct 18, 2013 at 4:23 AM, Linus Walleij wrote:
> On Thu, Oct 17, 2013 at 7:21 PM, Alexandre Courbot
> wrote:
>
>> Hi Linus,
>>
>> This version should merge as-is in your tree (I hope!). A patch for
>> documentation will follow soon.
>>
>> Changes since v2:
>> - rebased on top of Linus'
From: Dan Williams
Use the generic unmap object to unmap dma buffers.
Cc: Vinod Koul
Cc: Tomasz Figa
Cc: Dave Jiang
Reported-by: Bartlomiej Zolnierkiewicz
Signed-off-by: Dan Williams
[bzolnier: keep temporary dma_dest array in do_async_gen_syndrome()]
Signed-off-by: Bartlomiej
On Wed, Oct 16, 2013 at 10:26:44AM +0900, HATAYAMA Daisuke wrote:
[..]
> >I am wondering if there is any attribute of cpu which we can pass to
> >second kernel on command line. And tell second kernel not to bring up
> >that specific cpu. (Say exclude_cpu=)? If this works, then
> >if ACPI or other
From: Dan Williams
Use the generic unmap object to unmap dma buffers.
Cc: Vinod Koul
Cc: Tomasz Figa
Cc: Dave Jiang
Reported-by: Bartlomiej Zolnierkiewicz
Signed-off-by: Dan Williams
[bzolnier: keep temporary dma_dest array in async_mult()]
Signed-off-by: Bartlomiej Zolnierkiewicz
From: Dan Williams
Use the generic unmap object to unmap dma buffers.
Later we can push this unmap object up to the raid layer and get rid of
the 'scribble' parameter.
Cc: Vinod Koul
Cc: Tomasz Figa
Cc: Dave Jiang
Reported-by: Bartlomiej Zolnierkiewicz
Signed-off-by: Dan Williams
From: Dan Williams
Use the generic unmap object to unmap dma buffers.
Cc: Vinod Koul
Cc: Tomasz Figa
Cc: Dave Jiang
Reported-by: Bartlomiej Zolnierkiewicz
Signed-off-by: Dan Williams
[bzolnier: add missing unmap->len initialization]
[bzolnier: fix whitespace damage]
Signed-off-by:
From: Dan Williams
Copying from page to page (dma_async_memcpy_pg_to_pg) is the superset,
make the other two apis use that one in preparation for providing a
common dma unmap implementation. The common implementation just wants
to assume all buffers are mapped with dma_map_page().
Cc: Vinod
Make the driver DMA unmap also source buffers by itself
(currently it DMA unmaps only destination buffers) as
a preparation for introducing generic 'ummap' data.
Cc: Dan Williams
Cc: Vinod Koul
Cc: Tomasz Figa
Cc: Dave Jiang
Cc: Andy Shevchenko
Signed-off-by: Bartlomiej Zolnierkiewicz
On Friday, October 18, 2013 09:05:13 PM Lan Tianyu wrote:
> On 10/17/2013 07:38 PM, Rafael J. Wysocki wrote:
> >>> Unfortunately, I don't see how we can fix this race in a
> >>> satisfactory way and I'm starting to think that the whole
> >>> resuming of dependent devices may be a bad
On 10/18/2013 07:27 PM, Sebastian Hesselbarth wrote:
On 10/18/2013 06:17 PM, Ezequiel Garcia wrote:
On Fri, Oct 18, 2013 at 10:47:41AM -0400, Jason Cooper wrote:
On Fri, Oct 18, 2013 at 01:54:13PM +0200, Sebastian Hesselbarth wrote:
With legacy devices converted to DT and a proper ethernet
On Fri, Oct 18, 2013 at 07:43:54PM +0200, Sebastian Hesselbarth wrote:
> On 10/18/2013 07:27 PM, Sebastian Hesselbarth wrote:
> >On 10/18/2013 06:17 PM, Ezequiel Garcia wrote:
> >>On Fri, Oct 18, 2013 at 10:47:41AM -0400, Jason Cooper wrote:
> >>>On Fri, Oct 18, 2013 at 01:54:13PM +0200, Sebastian
From: baker.ker...@gmail.com
Date: Sun, 13 Oct 2013 19:50:09 +0800
> From: "baker.zhang"
>
> fib_table_lookup has included the rcu lock protection.
>
> Signed-off-by: baker.zhang
Applied, thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
I'm announcing the release of the 3.10.17 kernel.
All users of the 3.10 kernel series must upgrade.
The updated 3.10.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-3.10.y
and can be browsed at the normal kernel.org git web
On Fri, Oct 18, 2013 at 9:22 AM, Kevin Hilman wrote:
> On Fri, Oct 18, 2013 at 1:22 AM, Thierry Reding
> wrote:
>> On Fri, Oct 18, 2013 at 12:45:26AM -0700, Olof Johansson wrote:
>>> On Fri, Oct 18, 2013 at 01:38:47AM +0100, Mark Brown wrote:
>>> > Hi all,
>>> >
>>> > I've uploaded today's
[I made a mistake with my last change to this patch. I misunderstood
what bdev_io_min() was all about. I needed to stick with
logical_block_size.]
This uses the new kernel aio interface to process loopback IO by
submitting concurrent direct aio. Previously loop's IO was serialized
by synchronous
Add the restart node so we can reboot the device.
Signed-off-by: Stephen Boyd
---
arch/arm/boot/dts/qcom-msm8974.dtsi | 5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm/boot/dts/qcom-msm8974.dtsi
b/arch/arm/boot/dts/qcom-msm8974.dtsi
index 2ebb4f0..df18637 100644
---
This doesn't need to be a def_bool y. Instead we can have every
DT supported platform select ARCH_MSM_DT and we achieve the same
thing with less chance of conflicts.
Signed-off-by: Stephen Boyd
---
arch/arm/mach-msm/Kconfig | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git
Add the mmio architected timer node.
Signed-off-by: Stephen Boyd
---
arch/arm/boot/dts/qcom-msm8974.dtsi | 59 +
1 file changed, 59 insertions(+)
diff --git a/arch/arm/boot/dts/qcom-msm8974.dtsi
b/arch/arm/boot/dts/qcom-msm8974.dtsi
index df18637..6ac9496
This patchset simplifies the ARCH_MSM_DT config and adds some more
nodes for devices that have drivers merged in the upstream kernel.
Changes since v1:
* Moved nodes into soc node
* Enabled restart driver in defconfig
Stephen Boyd (4):
ARM: msm: Simplify ARCH_MSM_DT config
ARM: dts:
Signed-off-by: Stephen Boyd
---
arch/arm/configs/msm_defconfig | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/configs/msm_defconfig b/arch/arm/configs/msm_defconfig
index 0ed32e5..c5698b7 100644
--- a/arch/arm/configs/msm_defconfig
+++ b/arch/arm/configs/msm_defconfig
@@ -89,6
On Mon, Oct 14, 2013 at 08:52:18PM -0300, Gustavo Padovan wrote:
> Hi John,
>
> More patches for 3.12, busy times for Bluetooth. More than a 100 commits since
> the last pull. The bulk of work comes from Johan and Marcel, they are doing
> fixes and improvements all over the Bluetooth subsystem,
On Fri, 2013-10-18 at 19:35 +0200, Bartlomiej Zolnierkiewicz wrote:
> Make the driver DMA unmap also source buffers by itself
> (currently it DMA unmaps only destination buffers) as
> a preparation for introducing generic 'ummap' data.
>
> Cc: Dan Williams
I think you may update Dan's address.
From: Peter A. Felvegi
The UDF driver was not strict enough about checking the IDs in the
VSDs when mounting, which resulted in reading through all the sectors
of the block device in some unfortunate cases. Eg, trying to mount my
uninitialized 200G SSD partition (all 0xFF bytes) took ~350
Put architecture-specific assembly code where it belongs,
allowing for support of additional architectures such as arm64 in
the future.
Signed-off-by: Christopher Covington
---
arch/arm/include/asm/dcc.h | 45 +++
drivers/tty/hvc/hvc_dcc.c | 48
On 10/18/13 6:29 AM, Adrian Hunter wrote:
addr is not displayed by default for hardware events,
however for branch events it is the target of the branch
so for BTS display it by default if it was recorded.
Signed-off-by: Adrian Hunter
---
tools/perf/builtin-script.c | 4 +++-
1 file
I guess this is the last review I have for this around, but not sure
what's the best solution right now.
Kirill, do you think it's OK to just split the huge page when it will
be moved. Will look into how thp anon handle this situation.
Then after this, I probably will post v2.
Thanks!
Best
It's fine for Score. Pass the compiling and other tests.
Thank you.
Acked-by: Lennox Wu
於 2013/10/8 下午 07:34, Richard Weinberger 提到:
> Use the more generic functions get_signal() signal_setup_done()
> for signal delivery.
>
> Signed-off-by: Richard Weinberger
> ---
> arch/score/kernel/signal.c
On 10/18/13 11:14, Christopher Covington wrote:
> Put architecture-specific assembly code where it belongs,
> allowing for support of additional architectures such as arm64 in
> the future.
Do you have that patch too? There was also a patch a year ago to add
armv5/v4 support to this driver. Maybe
On 10/15/13 07:11, Stanimir Varbanov wrote:
> This adds Qualcomm PRNG driver device tree binding documentation
> to use as an example in dts trees.
>
> Signed-off-by: Stanimir Varbanov
> ---
Reviewed-by: Stephen Boyd
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted
On 10/15/13 07:11, Stanimir Varbanov wrote:
> This adds a driver for hardware random number generator present
> on Qualcomm MSM SoC's.
>
> Signed-off-by: Stanimir Varbanov
> ---
Reviewed-by: Stephen Boyd
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux
Hi all,
Guenter, thanks for adding devicetree to Cc.
On Fri, Oct 18, 2013 at 01:44:07AM +0100, Guenter Roeck wrote:
> On 10/17/2013 04:51 PM, Michael Bohan wrote:
> > On Wed, Oct 16, 2013 at 09:54:27PM -0700, Guenter Roeck wrote:
> >> On 10/16/2013 05:27 PM, Michael Bohan wrote:
> >>> My
I'm announcing the release of the 3.11.6 kernel.
All users of the 3.11 kernel series must upgrade.
The updated 3.11.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-3.11.y
and can be browsed at the normal kernel.org git web browser:
* Change the fix for KDB not defined build problem by changing
the kgdb_nmicallin() interface to include the KDB specific
reason code. This removes a dependency on KDB in the debug
core. Also requires a change the call in from UV NMI handler.
* Fix some problems found by the kbuild test
Fix some problems found by the kbuild test robot.
Signed-off-by: Mike Travis
Reviewed-by: Hedi Berriche
---
arch/x86/include/asm/uv/uv.h |2 --
arch/x86/kernel/apic/x2apic_uv_x.c |1 -
arch/x86/platform/uv/uv_nmi.c |9 -
3 files changed, 4 insertions(+), 8
Some code added to the debug_core module had KDB dependencies that it
shouldn't have. Move the KDB dependent REASON back to the caller to
remove the dependence in KGDB code.
Signed-off-by: Mike Travis
Reviewed-by: Hedi Berriche
---
arch/x86/platform/uv/uv_nmi.c |2 +-
include/linux/kgdb.h
Fix UV call into kgdb to depend only on whether KGDB is defined and not
both KGDB and KDB. This allows the power nmi command to use the gdb
remote connection if enabled. Note new action of 'kgdb' needs to be set
as well to indicate user wants to wait for gdb to be connected. If it's
set to
On 10/18/2013 05:13 PM, Keith Busch wrote:
On Fri, 18 Oct 2013, Matias Bjorling wrote:
The nvme driver implements itself as a bio-based driver. This primarily
because of high lock congestion for high-performance nvm devices. To
remove the congestion within the traditional block layer, a
On Mon, 14 Oct 2013 12:29:13 +0400
Andrey Konovalov wrote:
> Testing now with your patch.
> I've seen this report only twice, so it will be difficult to say if
> it's not happening any more or just not triggered.
Can I assume that this is fixed? I'll put it in for 3.12 and mark it
for stable
On 10/18/2013 05:48 PM, Matthew Wilcox wrote:
On Fri, Oct 18, 2013 at 03:14:19PM +0200, Matias Bjorling wrote:
Performance study:
System: HGST Research NVMe prototype, Haswell i7-4770 3.4Ghz, 32GB 1333Mhz
I don't have one of these. Can you provide more details about it,
such as:
- How
Linus,
Please pull the latest x86-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
x86-urgent-for-linus
# HEAD: dd3c9c4b603c664fedc12facf180db0f1794aafe x86: Update UV3 hub
revision ID
Two fixlets:
- fix a (rare-config) build bug
- fix a
On 10/18/2013 05:48 PM, Matthew Wilcox wrote:
On Fri, Oct 18, 2013 at 03:14:19PM +0200, Matias Bjorling wrote:
Performance study:
System: HGST Research NVMe prototype, Haswell i7-4770 3.4Ghz, 32GB 1333Mhz
I don't have one of these. Can you provide more details about it,
such as:
- How
On 10/17/2013 11:07 PM, Myklebust, Trond wrote:
> On Thu, 2013-10-17 at 22:42 퍭, Helge Deller wrote:
>> I'm seeing a regression with current kernel git head when using NFS-mounts.
>> Architecture in my case is parisc, although I don't think that this is
>> relevant.
>> At least kernel 3.10 (and I
Hello Nicolas,
This patch should fix the bug you were seeing with USB device
enumaration after moving to CCF.
Tell me if this solves the issue (it worked for me).
Best Regards,
Boris
On 18/10/2013 21:26, Boris BREZILLON wrote:
The AT91 PMC (Power Management Controller) provides a USB clock
On Fri, Oct 18, 2013 at 09:30:32AM -0700, David Daney wrote:
> On 10/18/2013 08:57 AM, Rob Herring wrote:
> [...]
> >
> >Unflattening is definitely the right
> >direction to go here.
> >
>
> I wonder if that is really true.
>
> The device tree in question is very short lived, and used to control
The AT91 PMC (Power Management Controller) provides a USB clock used by
the different USB controllers (ehci, ohci and udc).
The atmel-ehci driver must configure the usb clock rate to 48Mhz in order
to get a fully functionnal USB host controller.
This configuration was formely done in
On Fri, 2013-10-18 at 21:26 +0200, Helge Deller wrote:
> On 10/17/2013 11:07 PM, Myklebust, Trond wrote:
> > On Thu, 2013-10-17 at 22:42 퍭, Helge Deller wrote:
> >> I'm seeing a regression with current kernel git head when using NFS-mounts.
> >> Architecture in my case is parisc, although I don't
Hi Linus,
Please pull from the git repository at
git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git
pm+acpi-3.12-rc6
to receive ACPI and power management fixes for v3.12-rc6 with
top-most commit 981984cbd09e41c05b4ec6260e3f68591354cd54
Merge branch Merge branch 'acpi-fixes'
On Fri, Oct 18, 2013 at 8:08 PM, Randy Dunlap wrote:
> On 10/17/13 17:38, Mark Brown wrote:
>> Hi all,
>>
>> I've uploaded today's linux-next tree to the master branch of the
>> repository below:
>>
>> git://gitorious.org/thierryreding/linux-next.git
>>
>> A next-20131017 tag is also
NOTE:
This is the LAST 3.0.x stable kernel release that I will be doing.
After this release, 3.0.x is End-Of-Life, please move to the 3.10.x,
or if you must, 3.4.x series. For more information about longterm
stable releases and how long they will be maintained, please see
This is the start of the stable review cycle for the 3.4.67 release.
There are 11 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made by Sun Oct 20 19:50:39 UTC 2013.
Anything
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
commit c16a98ed91597b40b22b540c6517103497ef8e74 upstream.
commit 72a3effaf633bc ([NET]: Size listen hash tables using backlog
hint) added a bug allowing inet6_synq_hash() to
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Helge Deller
commit 59b33f148cc08fb33cbe823fca1e34f7f023765e upstream.
Running an "echo t > /proc/sysrq-trigger" crashes the parisc kernel. The
problem is, that in print_worker_info() we try
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: wojciech kapuscinski
commit 50b8f5aec04ebec7dbdf2adb17220b9148c99e63 upstream.
They have 4 rather than 8.
Fixes:
https://bugs.freedesktop.org/show_bug.cgi?id=63599
Signed-off-by: wojciech
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Dan Carpenter
commit 8612ed0d97abcf1c016d34755b7cf2060de71963 upstream.
Calling the WDIOC_GETSTATUS & WDIOC_GETBOOTSTATUS and twice will cause a
interruptible deadlock.
Signed-off-by: Dan
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Cyril Hrubis
commit e8420a8ece80b3fe810415ecf061d54ca7fab266 upstream.
Fix a corner case for MAP_FIXED when requested mapping length is larger
than rlimit for virtual memory. In such case any
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Helge Deller
commit 59b33f148cc08fb33cbe823fca1e34f7f023765e upstream.
Running an "echo t > /proc/sysrq-trigger" crashes the parisc kernel. The
problem is, that in print_worker_info() we try
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Daniel Mack
commit a9d14bc0b188a822e42787d01e56c06fe9750162 upstream.
The frame check in i_usX2Y_urb_complete() and
i_usX2Y_usbpcm_urb_complete() is bogus and produces false positives as
On 10/18/2013 12:46 AM, Thierry Reding wrote:
> On Sun, Sep 22, 2013 at 09:59:56AM -0700, Mike Dunn wrote:
>> Currently the driver assumes that the values specified in the
>> brightness-levels device tree property increase as they are parsed from
>> left to right. But boards that invert the
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Paul Mackerras
commit cfc860253abd73e1681696c08ea268d33285a2c4 upstream.
This fixes a typo in the code that saves the guest DSCR (Data Stream
Control Register) into the kvm_vcpu_arch struct on
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Dave Jones
commit 6e4ea8e33b2057b85d75175dd89b93f5e26de3bc upstream.
If we take the 2nd retry path in ext4_expand_extra_isize_ea, we
potentionally return from the function without having freed
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Linus Torvalds
commit 09884964335e85e897876d17783c2ad33cf8a2e0 upstream.
The stack vma is designed to grow automatically (marked with VM_GROWSUP
or VM_GROWSDOWN depending on architecture) when
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Linus Torvalds
commit 9d05746e7b16d8565dddbe3200faa1e669d23bbf upstream.
Olga reported that file descriptors opened with O_PATH do not work with
fstatfs(), found during further development of
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
commit c6cc3d58b4042f5cadae653ff8d3df26af1a0169 upstream.
ASUS N56VZ needs a fixup for the bass speaker pin, which was already
provided via model=asus-mode4.
Bugzilla:
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Theodore Ts'o
commit 47d06e532e95b71c0db3839ebdef3fe8812fca2c upstream.
The some platforms (e.g., ARM) initializes their clocks as
late_initcalls for some unknown reason. So make sure
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Dan Carpenter
commit 8612ed0d97abcf1c016d34755b7cf2060de71963 upstream.
Calling the WDIOC_GETSTATUS & WDIOC_GETBOOTSTATUS and twice will cause a
interruptible deadlock.
Signed-off-by: Dan
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Dave Jones
commit 6e4ea8e33b2057b85d75175dd89b93f5e26de3bc upstream.
If we take the 2nd retry path in ext4_expand_extra_isize_ea, we
potentionally return from the function without having freed
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: wojciech kapuscinski
commit 50b8f5aec04ebec7dbdf2adb17220b9148c99e63 upstream.
They have 4 rather than 8.
Fixes:
https://bugs.freedesktop.org/show_bug.cgi?id=63599
Signed-off-by: wojciech
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Linus Torvalds
commit 9d05746e7b16d8565dddbe3200faa1e669d23bbf upstream.
Olga reported that file descriptors opened with O_PATH do not work with
fstatfs(), found during further development of
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Theodore Ts'o
commit 47d06e532e95b71c0db3839ebdef3fe8812fca2c upstream.
The some platforms (e.g., ARM) initializes their clocks as
late_initcalls for some unknown reason. So make sure
On 10/18/2013 09:36 PM, Myklebust, Trond wrote:
> On Fri, 2013-10-18 at 21:26 퍭, Helge Deller wrote:
>> On 10/17/2013 11:07 PM, Myklebust, Trond wrote:
>>> On Thu, 2013-10-17 at 22:42 m, Helge Deller wrote:
I'm seeing a regression with current kernel git head when using NFS-mounts.
Jaehoon,
On Fri, Oct 18, 2013 at 2:42 AM, Jaehoon Chung wrote:
>> - clk_en_a = mci_readl(host, CLKENA);
>> + /*
>> + * Low power mode will stop the card clock when idle. According to the
>> + * description of the CLKENA register we should disable low power mode
>> + * for
Jaehoon / James
On Fri, Oct 18, 2013 at 2:51 AM, Jaehoon Chung wrote:
>> In this case it'd only be a space and code complexity thing I think. I
>> suppose in some cases the benefit of finer-grained locking is probably
>> pretty marginal, but there's a good case for it here. It might be
>> worth
On Fri, Oct 18, 2013 at 10:20:35AM -0700, Eric Dumazet wrote:
> On Fri, 2013-10-18 at 12:50 -0400, Neil Horman wrote:
> > >
>
> > for(i=0;i<10;i++) {
> > sum = csum_partial(buf+offset, PAGE_SIZE, sum);
> > offset = (offset < BUFSIZ-PAGE_SIZE) ? offset+PAGE_SIZE :
On Fri, 2013-10-18 at 22:03 +0200, Helge Deller wrote:
> On 10/18/2013 09:36 PM, Myklebust, Trond wrote:
> > Also, could you please try a sysRQ-t the next time it happens, so that
> > we can get a trace of where the mount program is hanging. Knowing that
> > the mount is stuck in "__schedule()" is
From: Stephen Hemminger
Date: Wed, 16 Oct 2013 17:29:34 -0700
> Randy found that if network namespace not enabled then
> nd_net does not exist and would cause compilation failure.
>
> This is handled correctly by using the dev_net() macro.
>
> Signed-off-by: Stephen Hemminger
> Acked-by:
On Thu, Oct 17, 2013 at 7:06 AM, Mark Rutland wrote:
>> diff --git a/arch/arm/boot/dts/bcm11351.dtsi
>> b/arch/arm/boot/dts/bcm11351.dtsi
>> index 193659c..39c1395 100644
>> --- a/arch/arm/boot/dts/bcm11351.dtsi
>> +++ b/arch/arm/boot/dts/bcm11351.dtsi
>> @@ -95,7 +95,7 @@
>>
From: Hannes Frederic Sowa
Date: Thu, 17 Oct 2013 07:31:54 +0200
> This series implements support for delaying the initialization of secret
> keys, e.g. used for hashing, for as long as possible. This functionality
> is implemented by a new macro, net_get_random_bytes.
>
> I already used it to
901 - 1000 of 1098 matches
Mail list logo