On 1 February 2013 09:54, Stephen Warren wrote:
>>
>> The entire series is merged in Greg's driver-core tree [1] and I
>> presume all other associated patches would also be picked up by him.
>> Isn't it Greg?
>>
>> [1] git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git
>
> The
On 02/01/2013 07:54 AM, Bart Van Assche wrote:
* proc_scsi_write - handle writes to /proc/scsi/scsi
* @file: not used
* @buf: buffer to write
* @length: length of buf, at most PAGE_SIZE
* @ppos: not used
*
* Description: this provides a legacy mechanism to add or remove
* devices
On Tue, Jan 29, 2013 at 11:54 PM, Maxime Ripard
wrote:
> Le 29/01/2013 23:41, Linus Walleij a écrit :
>> On Sun, Jan 27, 2013 at 8:02 PM, Maxime Ripard
>> wrote:
>>
>>> Since the pin controller of sunxi chips is represented as a single bank
>>> in the driver.
>>> Since this is neither convenient
On 02/01/2013 05:24 PM, Jack Wang wrote:
>
> On 02/01/2013 04:50 PM, Jack Wang wrote:
>> Hi All,
>> In our product system, we have several sata disks attached to one
>> machine. So when one of the disk fails, the jbd2(yes, we use ext4)
>> will hang forever and we will get something in
* Sasha Levin wrote:
> These headers provide the same API as their pthread mutex counterparts.
>
> The design here is to allow to easily switch to liblock lock validation
> just by adding a "liblock_" to pthread_mutex_*() calls, which means that
> it's easy to integrate liblock into existing
On Wed, Jan 30, 2013 at 12:27 PM, Thierry Reding
wrote:
> __devinit, __devexit and __devexit_p have been removed and should no
> longer be used.
>
> Signed-off-by: Thierry Reding
Hm I think I removed these just the other day ... may have been
around the time you sent this patch. Anyway,
On 02/01/2013 05:52 PM, Bryn M. Reeves wrote:
> On 02/01/2013 07:54 AM, Bart Van Assche wrote:
>> * proc_scsi_write - handle writes to /proc/scsi/scsi
>> * @file: not used
>> * @buf: buffer to write
>> * @length: length of buf, at most PAGE_SIZE
>> * @ppos: not used
>> *
>> *
On Fri, Feb 01, 2013 at 10:14:20AM +0900, Yasuaki Ishimatsu wrote:
> 2013/02/01 9:53, Yasuaki Ishimatsu wrote:
> >2013/02/01 9:50, Yasuaki Ishimatsu wrote:
> >>2013/01/31 19:03, Daniel Vetter wrote:
> >>>On Thu, Jan 31, 2013 at 12:27:26PM +0900, Yasuaki Ishimatsu wrote:
> I forgot to change
On 02/01/2013 09:59 AM, Tao Ma wrote:
yes, but the result is the same. It will do some IO first which will
cause this command hang.
You seem to have a problem with either the device/adapter or in the
driver. The backtrace you posted shows that jbd2 (ext4) is still waiting
on IO that's been
On Tue, Jan 29, 2013 at 11:56:01AM -0500, Vince Weaver wrote:
> On Tue, 29 Jan 2013, Jiri Olsa wrote:
>
> > ok, there's been perf fixies wrt enable events groups, but they
> > landed in 3.8-rc1.. until that point all the group members are
> > specifically enabled, so that's why your perf is
* Andi Kleen wrote:
> From: Andi Kleen
>
> Implement the TSX transaction and checkpointed transaction qualifiers for
> Haswell. This allows e.g. to profile the number of cycles in transactions.
>
> The checkpointed qualifier requires forcing the event to
> counter 2, implement this with a
Use the newly introduced devm_ioremap_resource() instead of
devm_request_and_ioremap() which provides more consistent error handling.
devm_ioremap_resource() provides its own error messages; so all explicit
error messages can be removed from the failure code paths.
Signed-off-by: Sachin Kamat
Use the newly introduced devm_ioremap_resource() instead of
devm_request_and_ioremap() which provides more consistent error handling.
devm_ioremap_resource() provides its own error messages; so all explicit
error messages can be removed from the failure code paths.
Signed-off-by: Sachin Kamat
This is the fifth version of the Tegra114 clockframework. It is based on the
for-next branch of
git://git.kernel.org/pub/scm/linux/kernel/git/swarren/linux-tegra.git and
http://www.spinics.net/lists/arm-kernel/msg220452.html.
It has been boottested on Pluto.
Changes from v4:
* Split the new PLL
* Arnaldo Carvalho de Melo wrote:
> Hi Ingo,
>
> Please consider pulling,
>
> - Arnaldo
>
> The following changes since commit 152fefa921535665f95840c08062844ab2f5593e:
>
> Merge tag 'perf-core-for-mingo' of
> git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux into perf/core
On Fri, Feb 01, 2013 at 02:32:03PM +0800, zergmk2 wrote:
> I've verified your patch and spi bus worked properly on PXA910 platform.
> I used a debug tool to send data on spi bus, and I connected spi out pin
> and spi in pin.
> So when I read data from spi bus, it should be what I sent from spi
This is the fifth version of the Tegra114 clockframework. It is based on the
for-next branch of
git://git.kernel.org/pub/scm/linux/kernel/git/swarren/linux-tegra.git and
http://www.spinics.net/lists/arm-kernel/msg220452.html.
It has been boottested on Pluto.
Changes from v4:
* Split the new PLL
Refactor the PLL programming code to make it useable by the new PLL types
introduced by Tegra114.
The following changes were done:
* Split programming the PLL into updating m,n,p and updating cpcon
* Move locking from _update_pll_cpcon() to clk_pll_set_rate()
* Introduce _get_pll_mnp() helper
*
On Thu 2013-01-31 23:38:27, Phil Turmel wrote:
> On 01/31/2013 10:13 PM, paul.sz...@sydney.edu.au wrote:
> > [trim /] Does not that prove that PAE is broken?
>
> Please, Paul, take *yes* for an answer. It is broken. You've received
> multiple dissertations on why it is going to stay that way.
Not all PLLs in Tegra114 have a bypass bit. Adapt the common code to only use
this bit when available.
Signed-off-by: Peter De Schrijver
---
drivers/clk/tegra/clk-pll.c | 15 ++-
drivers/clk/tegra/clk.h |8 +---
2 files changed, 15 insertions(+), 8 deletions(-)
diff
Some PLLs in Tegra114 don't use a power of 2 mapping for the post divider.
Introduce a table based approach and switch PLLU to it.
Signed-off-by: Peter De Schrijver
---
drivers/clk/tegra/clk-pll.c | 38 --
drivers/clk/tegra/clk-tegra20.c |7 +++
Tegra114 introduces new PLL types. This requires new clocktypes as well
as some new fields in the pll structure.
Signed-off-by: Peter De Schrijver
---
drivers/clk/tegra/clk-pll.c | 719 +++
drivers/clk/tegra/clk.h | 47 +++
2 files changed, 766
We will need some tegra peripheral clocks with the CLK_IGNORE_UNUSED flag,
most notably mselect, which is a bridge between AXI and most peripherals.
Signed-off-by: Peter De Schrijver
---
drivers/clk/tegra/clk-periph.c | 11 ++-
drivers/clk/tegra/clk-tegra20.c |2 +-
hi,
this fix is related to following discussion:
http://thread.gmane.org/gmane.linux.kernel.perf.user/1144
The fix is straightforward, but I think we could have
same issue in perf_pmu_migrate_context function as well,
which is used so far only by uncore bits.
I think the perf_pmu_migrate_context
Workaround a hardware bug in MSENC during clock enable.
Signed-off-by: Peter De Schrijver
---
drivers/clk/tegra/clk-periph-gate.c |9 +
drivers/clk/tegra/clk.h |1 +
2 files changed, 10 insertions(+), 0 deletions(-)
diff --git a/drivers/clk/tegra/clk-periph-gate.c
The device tree binding models Tegra114 CAR (Clock And Reset) as a single
monolithic clock provider.
Signed-off-by: Peter De Schrijver
---
.../bindings/clock/nvidia,tegra114-car.txt | 311
1 files changed, 311 insertions(+), 0 deletions(-)
create mode 100644
On Fri 2013-02-01 11:20:44, Pavel Machek wrote:
> On Thu 2013-01-31 23:38:27, Phil Turmel wrote:
> > On 01/31/2013 10:13 PM, paul.sz...@sydney.edu.au wrote:
> > > [trim /] Does not that prove that PAE is broken?
> >
> > Please, Paul, take *yes* for an answer. It is broken. You've received
> >
Add references to tegra_car clocks for the basic device nodes.
Signed-off-by: Peter De Schrijver
---
arch/arm/boot/dts/tegra114.dtsi |7 ++-
1 files changed, 6 insertions(+), 1 deletions(-)
diff --git a/arch/arm/boot/dts/tegra114.dtsi b/arch/arm/boot/dts/tegra114.dtsi
index
* Arnaldo Carvalho de Melo wrote:
> From: Sukadev Bhattiprolu
>
> Rename EVENT_ATTR() to PMU_EVENT_ATTR() and make it global so it is
> available to all architectures.
>
> Further to allow architectures flexibility, have PMU_EVENT_ATTR() pass
> in the variable name as a parameter.
>
>
Signed-off-by: Peter De Schrijver
---
drivers/clk/tegra/clk.c |1 +
drivers/clk/tegra/clk.h |7 +++
2 files changed, 8 insertions(+), 0 deletions(-)
diff --git a/drivers/clk/tegra/clk.c b/drivers/clk/tegra/clk.c
index a603b9a..a328365 100644
--- a/drivers/clk/tegra/clk.c
+++
These patches try to support context tracking for Power arch, beginning with
64-bit pSeries. The codes are ported from that of the x86_64, and in each
patch, I listed the corresponding patch for x86.
Would you please help review and give your comments?
Thanks, Zhong
Li Zhong (5):
powerpc:
This patch allows RCU usage in do_notify_resume, e.g. signal handling.
It corresponds to
[PATCH] x86: Exit RCU extended QS on notify resume
commit edf55fda35c7dc7f2d9241c3abaddaf759b457c6
Signed-off-by: Li Zhong
---
arch/powerpc/kernel/signal.c |5 +
1 file changed, 5 insertions(+)
Start context tracking support from pSeries.
Signed-off-by: Li Zhong
---
arch/powerpc/platforms/pseries/Kconfig |1 +
1 file changed, 1 insertion(+)
diff --git a/arch/powerpc/platforms/pseries/Kconfig
b/arch/powerpc/platforms/pseries/Kconfig
index 837cf49..a9570fe 100644
---
This is the exception hooks for context tracking subsystem, including
data access, program check, single step, instruction breakpoint, machine check,
alignment, fp unavailable, altivec assist, unknown exception, whose handlers
might use RCU.
This patch corresponds to
[PATCH] x86: Exception hooks
This patch corresponds to
[PATCH] x86: Use the new schedule_user API on userspace preemption
commit 0430499ce9d78691f3985962021b16bf8f8a8048
Signed-off-by: Li Zhong
---
arch/powerpc/include/asm/context_tracking.h | 11 +++
arch/powerpc/kernel/entry_64.S |3 ++-
2
This is the syscall slow path hooks for context tracking subsystem,
corresponding to
[PATCH] x86: Syscall hooks for userspace RCU extended QS
commit bf5a3c13b939813d28ce26c01425054c740d6731
TIF_MEMDIE is moved to the second 16-bits (with value 17), as it seems there
is no asm code using it.
Commit-ID: 11859e821761e9738c4d8a0e7d6ca1cc2e0d37e8
Gitweb: http://git.kernel.org/tip/11859e821761e9738c4d8a0e7d6ca1cc2e0d37e8
Author: Arnaldo Carvalho de Melo
AuthorDate: Wed, 30 Jan 2013 13:25:53 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 31 Jan 2013 13:07:42 -0300
Hello Nicolas,
thanks for your review!
Cheers,
Bernd
--
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
Commit-ID: 0de233b9c4f8c83b2cb655bfdbec306c8da81199
Gitweb: http://git.kernel.org/tip/0de233b9c4f8c83b2cb655bfdbec306c8da81199
Author: Arnaldo Carvalho de Melo
AuthorDate: Wed, 30 Jan 2013 14:01:20 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 31 Jan 2013 13:07:43 -0300
Commit-ID: 97f63e4a2cf88e9d7bc086a1c3f10fa41c9174df
Gitweb: http://git.kernel.org/tip/97f63e4a2cf88e9d7bc086a1c3f10fa41c9174df
Author: Namhyung Kim
AuthorDate: Tue, 22 Jan 2013 18:09:29 +0900
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 31 Jan 2013 13:07:43 -0300
perf tools:
Commit-ID: 8d7d8474d7b04dc89aa653d67425b61d3ff5c6f0
Gitweb: http://git.kernel.org/tip/8d7d8474d7b04dc89aa653d67425b61d3ff5c6f0
Author: Namhyung Kim
AuthorDate: Tue, 22 Jan 2013 18:09:30 +0900
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 31 Jan 2013 13:07:44 -0300
perf tests:
Commit-ID: a8bb559bd4eff5c71601e2e61a4bd1deef44a03c
Gitweb: http://git.kernel.org/tip/a8bb559bd4eff5c71601e2e61a4bd1deef44a03c
Author: Namhyung Kim
AuthorDate: Tue, 22 Jan 2013 18:09:31 +0900
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 31 Jan 2013 13:07:44 -0300
perf header:
Commit-ID: 6e1f601a10cbaa5cda869f844292dd81c519a8e7
Gitweb: http://git.kernel.org/tip/6e1f601a10cbaa5cda869f844292dd81c519a8e7
Author: Namhyung Kim
AuthorDate: Tue, 22 Jan 2013 18:09:32 +0900
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 31 Jan 2013 13:07:44 -0300
perf report:
Commit-ID: 29d720ed5f897d7e26f6b36c12c7704dc200d107
Gitweb: http://git.kernel.org/tip/29d720ed5f897d7e26f6b36c12c7704dc200d107
Author: Namhyung Kim
AuthorDate: Tue, 22 Jan 2013 18:09:33 +0900
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 31 Jan 2013 13:07:45 -0300
perf hists:
Hi,
This set of patches are aimed to allow truncate_inode_pages_range() handle
ranges which are not aligned at the end of the page. Currently it will
hit BUG_ON() when the end of the range is not aligned. Punch hole feature
however can benefit from this ability saving file systems some work not
->invalidatepage() aop now accepts range to invalidate so we can make
use of it in all ext4 invalidatepage routines.
Signed-off-by: Lukas Czerner
---
fs/ext4/inode.c | 47 ++
include/trace/events/ext4.h | 22 +++-
2 files
The discard_partial_page_buffers is no longer used anywhere so we can
simply remove it including the *_no_lock variant and
EXT4_DISCARD_PARTIAL_PG_ZERO_UNMAPPED define.
Signed-off-by: Lukas Czerner
---
fs/ext4/ext4.h |8 --
fs/ext4/inode.c | 206
Currently punch hole is disabled in file systems with bigalloc
feature enabled. However the recent changes in punch hole patch should
make it easier to support punching holes on bigalloc enabled file
systems.
This commit changes partial_cluster handling in ext4_remove_blocks(),
ext4_ext_rm_leaf()
In commits 5f95d21fb6f2aaa52830e5b7fb405f6c71d3ab85 and
30bc2ec9598a1b156ad75217f2e7d4560efdeeab we've reworked punch_hole
implementation and there is noting holding us back from using punch hole
on file system with bigalloc feature enabled.
This has been tested with fsx and xfstests.
Add "end" variable.
Signed-off-by: Lukas Czerner
---
fs/ext4/extents.c |6 +++---
include/trace/events/ext4.h | 21 ++---
2 files changed, 17 insertions(+), 10 deletions(-)
diff --git a/fs/ext4/extents.c b/fs/ext4/extents.c
index 966a09e..2b7e521 100644
---
Commit-ID: 5aed9d24934be5b7fec1b66cc2a5f29fab4ec11e
Gitweb: http://git.kernel.org/tip/5aed9d24934be5b7fec1b66cc2a5f29fab4ec11e
Author: Namhyung Kim
AuthorDate: Tue, 22 Jan 2013 18:09:35 +0900
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 31 Jan 2013 13:07:46 -0300
perf hists
->invalidatepage() aop now accepts range to invalidate so we can make
use of it in reiserfs_invalidatepage()
Signed-off-by: Lukas Czerner
---
fs/reiserfs/inode.c |9 +++--
1 files changed, 7 insertions(+), 2 deletions(-)
diff --git a/fs/reiserfs/inode.c b/fs/reiserfs/inode.c
index
This commit changes truncate_inode_pages_range() so it can handle non
page aligned regions of the truncate. Currently we can hit BUG_ON when
the end of the range is not page aligned, but we can handle unaligned
start of the range.
Being able to handle non page aligned regions of the page can help
> -Original Message-
> From: Alex Williamson [mailto:alex.william...@redhat.com]
> Sent: Tuesday, January 29, 2013 5:25 AM
> To: Pandarathil, Vijaymohan R
> Cc: Gleb Natapov; Bjorn Helgaas; Blue Swirl; Ortiz, Lance E;
> k...@vger.kernel.org; qemu-de...@nongnu.org;
The "head removal" branch in the condition is never used in any code
path in ext4 since the function only caller ext4_ext_rm_leaf() will make
sure that the extent is properly split before removing blocks. Note that
there is a bug in this branch anyway.
This commit removes the unused code
We're doing to get rid of ext4_discard_partial_page_buffers() since it is
duplicating some code and also partially duplicating work of
truncate_pagecache_range(), moreover the old implementation was much
clearer.
Now when the truncate_inode_pages_range() can handle truncating non page
aligned
Commit-ID: 843985e953ddcc3d57a62641b377c8d3222859e2
Gitweb: http://git.kernel.org/tip/843985e953ddcc3d57a62641b377c8d3222859e2
Author: Namhyung Kim
AuthorDate: Tue, 22 Jan 2013 18:09:36 +0900
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 31 Jan 2013 13:07:46 -0300
perf
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Olivier Sobrie
commit 6ea45886865c1abb01bb861f7f6bdd5d0f398cb3 upstream.
Errors in CAN protocol (location) are reported in data[3] of the can
frame instead of data[2].
Signed-off-by: Olivier
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Olivier Sobrie
commit 71088c4bd9b8f8cbffb0e66f2abc14297e4b2ca8 upstream.
Errors in CAN protocol (location) are reported in data[3] of the can
frame instead of data[2].
Signed-off-by: Olivier
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Cong Ding
commit 10b8c7dff5d3633b69e77f57d404dab54ead3787 upstream.
When it goes to error through line 144, the memory allocated to *devname is
not freed, and the caller doesn't free it either
Commit-ID: 5b9e2146ec4f8c6d436f9f7043a0409a4296a705
Gitweb: http://git.kernel.org/tip/5b9e2146ec4f8c6d436f9f7043a0409a4296a705
Author: Namhyung Kim
AuthorDate: Tue, 22 Jan 2013 18:09:37 +0900
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 31 Jan 2013 13:07:46 -0300
perf ui/hist:
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Szymon Janc
commit dbccd791a3fbbdac12c33834b73beff3984988e9 upstream.
After sending reset command wait for its command complete event before
sending next command. Some chips sends CC event for
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Felix Fietkau
commit 1adb2e2b5f85023d17eb4f95386a57029df27c88 upstream.
When the next beacon is sent, the ath_buf from the previous run is reused.
If getting a new beacon from mac80211 fails,
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Clemens Ladisch
commit d56268fb108c7c21e19933588ca4d94652585183 upstream.
Commit 23caaf19b11e (ALSA: usb-mixer: Add support for Audio Class v2.0)
forgot to adjust the length check for UAC 2.0
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Dan Carpenter
commit 8024c4c0b1057d1cd811fc9c3f88f81de9729fcd upstream.
We're testing for ->show but calling ->store().
Signed-off-by: Dan Carpenter
Signed-off-by: Borislav Petkov
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Anderson Lizardo
commit 0a9ab9bdb3e891762553f667066190c1d22ad62b upstream.
The length parameter should be sizeof(req->name) - 1 because there is no
guarantee that string provided by userspace
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Olivier Sobrie
commit ee50e135aeb048b90fab662e661c58b67341830b upstream.
Errors in CAN protocol (location) are reported in data[3] of the can
frame instead of data[2].
Signed-off-by: Olivier
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Alan Cox
commit c903f0456bc69176912dee6dd25c6a66ee1aed00 upstream.
At the moment the MSR driver only relies upon file system
checks. This means that anything as root with any capability set
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Nathan Zimmer
commit b8f2c21db390273c3eaf0e5308faeaeb1e233840 upstream.
Update efi_call_phys_prelog to install an identity mapping of all available
memory. This corrects a bug on very large
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: "H. Peter Anvin"
commit e43b3cec711a61edf047adf6204d542f3a659ef8 upstream.
early_pci_allowed() and read_pci_config_16() are only available if
CONFIG_PCI is defined.
Signed-off-by: H. Peter
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Wang YanQing
commit f44310b98ddb7f0d06550d73ed67df5865e3eda5 upstream.
I get the following warning every day with v3.7, once or
twice a day:
[ 2235.186027] WARNING: at
This is the start of the stable review cycle for the 3.4.29 release.
There are 33 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 Feb 3 10:47:08 UTC 2013.
Anything
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Olivier Sobrie
commit 71088c4bd9b8f8cbffb0e66f2abc14297e4b2ca8 upstream.
Errors in CAN protocol (location) are reported in data[3] of the can
frame instead of data[2].
Signed-off-by: Olivier
Commit-ID: 897014603c4786ef33450e675e02a5e74dc63785
Gitweb: http://git.kernel.org/tip/897014603c4786ef33450e675e02a5e74dc63785
Author: Namhyung Kim
AuthorDate: Tue, 22 Jan 2013 18:09:38 +0900
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 31 Jan 2013 13:07:47 -0300
perf hists
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Olivier Sobrie
commit 6ea45886865c1abb01bb861f7f6bdd5d0f398cb3 upstream.
Errors in CAN protocol (location) are reported in data[3] of the can
frame instead of data[2].
Signed-off-by: Olivier
On Thu, Jan 31, 2013 at 06:37:47PM -0600, Kim Phillips wrote:
> +#if GCC_VERSION >= 40600
> +#define __HAVE_BUILTIN_BSWAP32__
> +#define __HAVE_BUILTIN_BSWAP64__
You really aren't listening to anything that's been said to you.
--
To unsubscribe from this list: send the line "unsubscribe
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Russell King
commit 15653371c67c3fbe359ae37b720639dd4c7b42c5 upstream.
Subhash Jadavani reported this partial backtrace:
Now consider this call stack from MMC block driver (this is on the
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Jean-Christophe PLAGNIOL-VILLARD
commit 36224d0fe0f34cdde66a381708853ebadeac799c upstream.
Make BGA as the default version as we are supposed to just have
to specify when we use the PQFP
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Szymon Janc
commit dbccd791a3fbbdac12c33834b73beff3984988e9 upstream.
After sending reset command wait for its command complete event before
sending next command. Some chips sends CC event for
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Jerome Glisse
commit e521a29014794d139cca46396d1af8faf1295a26 upstream.
Aruba and newer gpu does not need the avivo cursor work around,
quite the opposite this work around lead to corruption.
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: xueminsu
commit b2f4b03f8a378cd626d2ea67d19e7470c050a098 upstream.
drm_mode_addfb() expects fb_create return error code
instead of NULL.
Signed-off-by: xueminsu
Signed-off-by: Alex Deucher
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Suravee Suthikulpanit
commit 318fe782539c4150d1b8e4e6c9dc3a896512cb8a upstream.
The IOMMU may stop processing page translations due to a perceived lack
of credits for writing upstream
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Olivier Sobrie
commit ee50e135aeb048b90fab662e661c58b67341830b upstream.
Errors in CAN protocol (location) are reported in data[3] of the can
frame instead of data[2].
Signed-off-by: Olivier
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Stanislaw Gruszka
commit fa4cffcba9e13798ed7c6b8526b91b1631ecb53e upstream.
We do not correctly change interface type when switching from
IBSS mode to STA mode, that results in microcode
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Johannes Berg
commit 1626e0fa740dec8665a973cf2349405cdfeb46dc upstream.
During FT roaming, wpa_supplicant attempts to set the
key before association. This used to be rejected, but
as a side
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Sujith Manoharan
commit 0981c3b24ef664f5611008a6e6d0622fac6d892b upstream.
SKBs that are allocated in the HTC layer do not have callbacks
registered and hence ended up not being freed, Fix
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Felix Fietkau
commit a3dc48e82bb146ef11cf75676c8410c1df29b0c4 upstream.
On AR9300 the rx FIFO needs to be empty during reset to ensure that no
further DMA activity is generated, otherwise it
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Felix Fietkau
commit 1adb2e2b5f85023d17eb4f95386a57029df27c88 upstream.
When the next beacon is sent, the ath_buf from the previous run is reused.
If getting a new beacon from mac80211 fails,
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Jan Kara
commit 4b05d09c18d9aa62d2e7fb4b057f54e5a38963f5 upstream.
Running AIO is pinning inode in memory using file reference. Once AIO
is completed using aio_complete(), file reference is
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Dan Carpenter
commit 8024c4c0b1057d1cd811fc9c3f88f81de9729fcd upstream.
We're testing for ->show but calling ->store().
Signed-off-by: Dan Carpenter
Signed-off-by: Borislav Petkov
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Chris Rattray
commit a80cc734282805e15b5e023751a4d02f7ffbcc91 upstream.
Signed-off-by: Chris Rattray
Signed-off-by: Mark Brown
Signed-off-by: Greg Kroah-Hartman
---
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Anderson Lizardo
commit 0a9ab9bdb3e891762553f667066190c1d22ad62b upstream.
The length parameter should be sizeof(req->name) - 1 because there is no
guarantee that string provided by userspace
On Fri, 1 Feb 2013, Linus Torvalds wrote:
> On Fri, Feb 1, 2013 at 9:44 AM, Thomas Gleixner wrote:
> >
> > Just face it. The current hotplug maze has 100+ states which are
> > completely undocumented. They are asymetric vs. startup and
> > teardown. They just exists and work somehow aside of the
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Trond Myklebust
commit ab225417825963b6dc66be7ea80f94ac1378dfdf upstream.
Ensure that any setattr and getattr requests for junctions and/or
mountpoints are sent to the server. Ever since
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Alan Cox
commit c903f0456bc69176912dee6dd25c6a66ee1aed00 upstream.
At the moment the MSR driver only relies upon file system
checks. This means that anything as root with any capability set
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
commit 0712eea349d8e2b6d0e44b94a752d999319027fb upstream.
A Packard-Bell desktop machine gives no proper pin configuration from
BIOS. It's almost equivalent with the 6stack+fp
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: "H. Peter Anvin"
commit e43b3cec711a61edf047adf6204d542f3a659ef8 upstream.
early_pci_allowed() and read_pci_config_16() are only available if
CONFIG_PCI is defined.
Signed-off-by: H. Peter
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Matt Fleming
commit 712ba9e9afc4b3d3d6fa81565ca36fe518915c01 upstream.
efi.runtime_version is erroneously being set to the value of the
vendor's firmware revision instead of that of the
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Nathan Zimmer
commit b8f2c21db390273c3eaf0e5308faeaeb1e233840 upstream.
Update efi_call_phys_prelog to install an identity mapping of all available
memory. This corrects a bug on very large
On Thu, Jan 31, 2013 at 12:22:52PM +0100, Ingo Molnar wrote:
>
> * Yuanhan Liu wrote:
>
> > > or whether the lock hold times could be reduced drastically
> >
> > I also found one, but it doesn't sound like the one will
> > reduce lock hold times drastically:
> >
> >vma_lock_anon_vma()
701 - 800 of 1300 matches
Mail list logo