On Thu, Oct 25, 2012 at 04:58:39PM +0200, Oleg Nesterov wrote:
> On 10/16, Rabin Vincent wrote:
> >
> > 2012/10/15 Oleg Nesterov :
> > > On 10/14, Rabin Vincent wrote:
> > >> Flush the cache so that the instructions written to the XOL area are
> > >> visible.
> > >>
> > >> Signed-off-by: Rabin
On Fri, 19 Oct 2012 17:56:24 +0100, David Howells wrote:
> Make perf build for x86 once the UAPI disintegration patches for that arch
> have been applied by adding the appropriate -I flags - in the right order -
> and then converting some #includes that use ../.. notation to find main kernel
>
Am Freitag, den 26.10.2012, 06:36 +0800 schrieb Richard Yang:
> >
> >And holy cow that code is hard to read :( Why was kfifo_in()
> >implemented as a macro, anyway? AFAICT all its args have a known type,
> >so we could have used a proper C interface, which would have fixed all
> >this nicely.
>
Hi Toshi,
On 10/26/2012 01:20 AM, Toshi Kani wrote:
...
Why do you need to call acpi_bus_trim(device,0) to stop the container
device first?
This issue was introduced by Lu Yinghai, I think he could give a better
answer than me. :)
Please refer to the following url:
Am Freitag, den 26.10.2012, 09:46 +0800 schrieb Yuanhan Liu:
> From: Yuanhan Liu
>
> Firstly, this kind of type check doesn't work. It does something similay
> like following:
> void * __dummy = NULL;
> __buf = __dummy;
>
> __dummy is defined as void *. Thus it will not trigger
On Fri, 19 Oct 2012 17:56:16 +0100, David Howells wrote:
> Honour the O= flag that was passed to a higher level Makefile and then passed
> down as part of a tool build.
>
> To make this work, the top-level Makefile passes the original O= flag and
> subdir=tools to the tools/Makefile, and that in
On Thu, Oct 25, 2012 at 9:28 PM, Paul Mundt wrote:
> On Tue, Oct 23, 2012 at 01:01:40PM -0700, Kees Cook wrote:
>> This config item has not carried much meaning for a while now and is
>> almost always enabled by default. As agreed during the Linux kernel
>> summit, remove it.
>>
>> CC: Paul Mundt
There are comments on why PME poll support is necessary for PCI
devices, but not for PCIe devices. That may lead to misunderstanding
that PME poll is only necessary for PCI devices. So add comments
related to PCIe PME poll to make it more clear.
The content of comments comes from the changelog
On Fri, Oct 26, 2012 at 11:55 AM, Fengguang Wu wrote:
> On Fri, Oct 26, 2012 at 11:38:11AM +0800, YingHang Zhu wrote:
>> On Fri, Oct 26, 2012 at 8:25 AM, Dave Chinner wrote:
>> > On Thu, Oct 25, 2012 at 10:58:26AM +0800, Fengguang Wu wrote:
>> >> Hi Chen,
>> >>
>> >> > But how can bdi related
From: Robin Dong
Currently, if the IO is throttled by io-throttle, the system admin has no idea
of the situation and can't report it to the real application user about that
he/she has to do something.
So this patch adds a new interface named blkio.throttle.io_submitted which
exposes the number
From: Robin Dong
We don't need to convert tg to blkg and then convert it back in
throtl_update_dispatch_stats().
Signed-off-by: Robin Dong
---
block/blk-throttle.c |7 +++
1 files changed, 3 insertions(+), 4 deletions(-)
diff --git a/block/blk-throttle.c b/block/blk-throttle.c
index
My guess is that Windows explicitly enables A20 on resume. We should do that
too, really... with the current heavily unified realmode code it should be easy
- let me hack up a patch in the morning.
Robert Hancock wrote:
>On 10/24/2012 02:09 PM, Alan Cox wrote:
>> On Wed, 24 Oct 2012 12:36:04
On 10/25/2012 01:47 AM, Chris Wilson wrote:
On Thu, 25 Oct 2012 10:16:08 +0200, Daniel Vetter wrote:
On Thu, Oct 25, 2012 at 7:22 AM, Justin P. Mattock
wrote:
here is a link to the file..: intel_error_decode
http://www.filefactory.com/file/22bypyjhs4mx
I haven't figured out how to access
Hi all,
Changes since 201201025:
The arm -soc tree gained conflicts against the gpio-lw and pinctrl trees.
The akpm tree a couple of patches that turned up elsewhere.
I have created today's linux-next tree at
On Fri, Oct 26, 2012 at 11:51 AM, Ni zhan Chen wrote:
> On 10/26/2012 11:28 AM, YingHang Zhu wrote:
>>
>> On Fri, Oct 26, 2012 at 10:30 AM, Ni zhan Chen
>> wrote:
>>>
>>> On 10/26/2012 09:27 AM, Fengguang Wu wrote:
On Fri, Oct 26, 2012 at 11:25:44AM +1100, Dave Chinner wrote:
>
Hi David,
On Thu, 25 Oct 2012 08:57:20 +0100, David Howells wrote:
> Borislav Petkov wrote:
>
>> David, where can get that x86 UAPI disintegration patch?
>
> The tip tree has it in branch x86/uapi or you can get it from:
>
> git://git.infradead.org/users/dhowells/linux-headers.git
>
>
On 10/24/2012 02:09 PM, Alan Cox wrote:
On Wed, 24 Oct 2012 12:36:04 -0700
"H. Peter Anvin" wrote:
Minor concern: it should do the wait for ready before sending each command.
Can we get a command line to do this quirk too - it strikes me that if
the MSIs rely upon it then it may be
This patch adds missing device.h header to fix build warnings as below:
drivers/cpuidle/cpuidle.h:26:41: warning: 'struct device' declared inside
parameter list [enabled by default]
drivers/cpuidle/cpuidle.h:26:41: warning: its scope is only this definition or
declaration, which is probably not
On Tue, Oct 23, 2012 at 01:01:40PM -0700, Kees Cook wrote:
> This config item has not carried much meaning for a while now and is
> almost always enabled by default. As agreed during the Linux kernel
> summit, remove it.
>
> CC: Paul Mundt
> CC: Tejun Heo
> Signed-off-by: Kees Cook
While
Linus,
Please pull the latest ktest-v3.7-rc2 tree, which can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-ktest.git
ktest-v3.7-rc2
Head SHA1: 0979976ee53697f4308578c56abedb9766fea231
Steven Rostedt (1):
ktest: Fix ktest confusion with
On Thu, Oct 25, 2012 at 8:57 PM, Rik van Riel wrote:
>
> That may not even be needed. Apparently Intel chips
> automatically flush an entry from the TLB when it
> causes a page fault. I assume AMD chips do the same,
> because flush_tlb_fix_spurious_fault evaluates to
> nothing on x86.
Yes.
This adds following helper routines:
- of_property_read_u8_array()
- of_property_read_u16_array()
- of_property_read_u8()
- of_property_read_u16()
First two actually share most of the code with of_property_read_u32_array(), so
the common part is taken out into a macro, which can be used by all
Driver anchors the tx urbs and defers the urb submission if
a transmit request comes when the interface is suspended.
Anchoring urb increments the urb reference count. These
deferred urbs are later accessed by calling usb_get_from_anchor()
for submission during interface resume.
On 25 October 2012 19:48, Viresh Kumar wrote:
> The problem i see here is:
>
> The data passed via DT comes as Little Endian in the kernel.
>
> For a little endian system, byte zero will contain the data and so
> (u8) val
>
> look to be the correct thing.
>
> For a big endian system, byte 3 will
HATAYAMA Daisuke writes:
> From: "H. Peter Anvin"
> Subject: Re: [PATCH v1 2/2] x86, apic: Disable BSP if boot cpu is AP
> Date: Mon, 22 Oct 2012 17:35:47 -0700
>
>> On 10/22/2012 02:29 PM, Eric W. Biederman wrote:
As I said, I thought Fenghua tried that but it didn't work,
On 10/24/2012 11:11:36 AM, Catalin Marinas wrote:
> 2012/10/24 Tekkaman Ninja :
> > This is a Chinese translated version of
> > Documentation/arm64/booting.txt
> >
> > Signed-off-by: Fu Wei
>
> Same as my comment on the memory.txt patch, I don't understand what
> it
> says, so you need to keep
On Fri, Oct 26, 2012 at 11:38:11AM +0800, YingHang Zhu wrote:
> On Fri, Oct 26, 2012 at 8:25 AM, Dave Chinner wrote:
> > On Thu, Oct 25, 2012 at 10:58:26AM +0800, Fengguang Wu wrote:
> >> Hi Chen,
> >>
> >> > But how can bdi related ra_pages reflect different files' readahead
> >> > window? Maybe
On 10/25/2012 10:56 PM, Linus Torvalds wrote:
Guess what? If you want to optimize the function to not do remote TLB
flushes, then just do that! None of the garbage. Just change the
flush_tlb_page(vma, address);
line to
__flush_tlb_one(address);
That may not even be needed.
On Thu, Oct 25, 2012 at 08:38:25PM -0700, Linus Torvalds wrote:
> It's valid to cast a non-const pointer to a const one. It's the
> *other* way around that is invalid.
>
> So marking fw_path[] as having 'const char *' elements just means that
> we won't be changing those elements through the
On 10/26/2012 11:28 AM, YingHang Zhu wrote:
On Fri, Oct 26, 2012 at 10:30 AM, Ni zhan Chen wrote:
On 10/26/2012 09:27 AM, Fengguang Wu wrote:
On Fri, Oct 26, 2012 at 11:25:44AM +1100, Dave Chinner wrote:
On Thu, Oct 25, 2012 at 10:58:26AM +0800, Fengguang Wu wrote:
Hi Chen,
But how can
On Thu, Oct 25, 2012 at 8:12 PM, Ming Lei wrote:
>
> Yes, it should be the cleanest, I don't do it because I thought that might
> have caused one compile warning('const char *' points to memory
> without 'const', like below)
You can just keep the const.
In fact, you could even add one, and make
On Fri, Oct 26, 2012 at 8:25 AM, Dave Chinner wrote:
> On Thu, Oct 25, 2012 at 10:58:26AM +0800, Fengguang Wu wrote:
>> Hi Chen,
>>
>> > But how can bdi related ra_pages reflect different files' readahead
>> > window? Maybe these different files are sequential read, random read
>> > and so on.
>>
[snip]
> > +#define F2FS_SUPER_MAGIC 0xF2F52010
> > +#define F2FS_SUPER_OFFSET 0 /* start sector # for sb */
>
> Does f2fs superblock really haven't any offset from the volume begin?
The reason that I changed this from 1 to 0 is due to the failure during android
recovery. I
Matthew Garrett writes:
> On Thu, Oct 25, 2012 at 09:15:58PM -0400, Mimi Zohar wrote:
>
>> On a running system, the package installer, after verifying the package
>> integrity, would install each file with the associated 'security.ima'
>> extended attribute. The 'security.evm' digital signature
On 26 October 2012 05:43, Rafael J. Wysocki wrote:
> I have applied this patch only because of the fixes on top of it. It broke
> kernel compliation due to some missing EXPORT_SYMBOL_GPLs in
> cpufreq_governor.c,
> so I woulnd't have applied it otherwise.
Hi Rafael,
So sorry for this. I am
On Fri, Oct 26, 2012 at 10:30 AM, Ni zhan Chen wrote:
> On 10/26/2012 09:27 AM, Fengguang Wu wrote:
>>
>> On Fri, Oct 26, 2012 at 11:25:44AM +1100, Dave Chinner wrote:
>>>
>>> On Thu, Oct 25, 2012 at 10:58:26AM +0800, Fengguang Wu wrote:
Hi Chen,
> But how can bdi related
On 10/23/2012 07:53 PM, Josh Cartwright wrote:
> The list of attributes above details the use of the 'filter-ranges'
> property, but the example improperly used 'filter-latency'. Make these
> consistent by fixing up the example.
>
> Signed-off-by: Josh Cartwright
Applied for 3.8 (unless I get
Hi all,
Today's linux-next merge of the arm-soc tree got a conflict in
arch/arm/mach-ux500/cpu-db8500.c between commit 63c53906312f
("pinctrl/nomadik: move the platform data header") from the pinctrl tree
and commit 4040d10a3d44 ("ARM: ux500: add DB serial number to entropy
pool") from the
From: "H. Peter Anvin"
Subject: Re: [PATCH v1 2/2] x86, apic: Disable BSP if boot cpu is AP
Date: Mon, 22 Oct 2012 17:35:47 -0700
> On 10/22/2012 02:29 PM, Eric W. Biederman wrote:
>>>
>>> As I said, I thought Fenghua tried that but it didn't work,
>>> experimentally.
>>
>> Fair enough. You
Hi all,
Today's linux-next merge of the arm-soc tree got a conflict in
arch/arm/Kconfig between commit a3b8d4a51357 ("GPIO: Add support for GPIO
on CLPS711X-target platform") from the gpio-lw tree and commit
4a8355c4c34f ("ARM: clps711x: convert to clockevents") from the arm-soc
tree.
I fixed it
On 10/26/2012 10:27 AM, Charles Wang wrote:
> Yes, it's a new way to do scheduler test. But why use kernel
> threads? The info, total time, run time, wait time, preempt number, all
> can be collected from tasks' sched info from /proc/pid/sched and
> /proc/pid/stat.
That's right, next version's
Fixes some minor issues in the x86 boot documentation.
Signed-off-by: Kees Cook
---
Documentation/x86/boot.txt |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/x86/boot.txt b/Documentation/x86/boot.txt
index 9efceff..f15cb74 100644
---
Thank you for comment.
I will make and send patch again.
Thanks and Regards.
SeongJae Park.
On Fri, Oct 26, 2012 at 4:16 AM, Greg KH wrote:
> On Thu, Oct 25, 2012 at 02:51:10PM +0900, SeongJae Park wrote:
>> Nobody use CsrEventHandle, Nobody call function using it as parameter.
>> So, remove
On Fri, Oct 26, 2012 at 10:32 AM, Linus Torvalds
wrote:
>
> Please just make "fw_path[0]" just be the pointer to fw_path_para[]
> (which sounds like the cleanest fix) and get rid of the negative 'i'
> and conditional entirely.
Yes, it should be the cleanest, I don't do it because I thought that
On 10/26/2012 03:51 AM, Johannes Weiner wrote:
On Thu, Oct 25, 2012 at 05:44:31PM +0100, Will Deacon wrote:
On x86 memory accesses to pages without the ACCESSED flag set result in the
ACCESSED flag being set automatically. With the ARM architecture a page access
fault is raised instead (and it
On 26 October 2012 03:14, Francesco Lavra wrote:
> Hi,
> Hongbo Zhang wrote:
>> Problem of using this list is that the cpufreq_get_max_state callback will be
>> called when register cooling device by thermal_cooling_device_register, but
>> this list isn't ready at this moment. What's more, there
On Thu, Oct 25, 2012 at 7:30 PM, Rik van Riel wrote:
>>
>> LOOK at the code, for chrissake. Just look at it. And if you don't see
>> why the above is stupid and retarded, you damn well shouldn't be
>> touching VM code.
>
> I agree it is pretty ugly. However, the above patch
> did get rid of a
From: Yanmin Zhang
We hit a kernel panic at __run_hrtimer=>BUG_ON(timer->state !=
HRTIMER_STATE_CALLBACK).
<2>[ 10.226053, 3] kernel BUG at
/home/android/xiaobing/ymz/r4/hardware/intel/linux-2.6/kernel/hrtimer.c:1228!
<0>[ 10.235682, 3] invalid opcode: [#1] PREEMPT SMP
<4>[
于 2012年10月26日 10:45, Greg KH 写道:
On Fri, Oct 26, 2012 at 09:10:45AM +0800, wwang wrote:
于 2012年10月26日 02:50, Greg KH 写道:
On Sat, Oct 20, 2012 at 06:46:15AM +0300, Dan Carpenter wrote:
On Sat, Oct 06, 2012 at 03:23:56PM +0800, wwang wrote:
We are still maintaining the SCSI driver for Realtek
On Fri, Oct 26, 2012 at 09:10:45AM +0800, wwang wrote:
> 于 2012年10月26日 02:50, Greg KH 写道:
> > On Sat, Oct 20, 2012 at 06:46:15AM +0300, Dan Carpenter wrote:
> >> On Sat, Oct 06, 2012 at 03:23:56PM +0800, wwang wrote:
> >>> We are still maintaining the SCSI driver for Realtek card reader,
> >>> and
On Thu, Oct 25, 2012 at 5:57 PM, Michal Hocko wrote:
> On Wed 24-10-12 11:44:17, Qiang Gao wrote:
>> On Wed, Oct 24, 2012 at 1:43 AM, Balbir Singh wrote:
>> > On Tue, Oct 23, 2012 at 3:45 PM, Michal Hocko wrote:
>> >> On Tue 23-10-12 18:10:33, Qiang Gao wrote:
>> >>> On Tue, Oct 23, 2012 at
On Thu, Oct 25, 2012 at 09:15:58PM -0400, Mimi Zohar wrote:
> On a running system, the package installer, after verifying the package
> integrity, would install each file with the associated 'security.ima'
> extended attribute. The 'security.evm' digital signature would be
> installed with an
The benchmark:
/*
* test.c - Simulate workloads that load the CPU differently
*
* This program is free software; you can redistribute it and/or
* modify it under the terms of the GNU General Public License as
* published by the Free Software Foundation; version 2 of the License.
*
* This
On Thu, Oct 25, 2012 at 5:46 PM, Ming Lei wrote:
> struct file *file;
> - snprintf(path, PATH_MAX, "%s/%s", fw_path[i], buf->fw_id);
> +
> + if (i < 0) {
> + if (!fw_path_para[0]) /* No customized path */
> +
On Thu, Oct 25, 2012 at 02:08:14AM -0700, Anton Vorontsov wrote:
> Hello Minchan,
>
> Thanks a lot for the email!
>
> On Thu, Oct 25, 2012 at 03:40:09PM +0900, Minchan Kim wrote:
> [...]
> > > What applications (well, activity managers) are really interested in is
> > > this:
> > >
> > > 1. Do
On 10/26/2012 09:27 AM, Fengguang Wu wrote:
On Fri, Oct 26, 2012 at 11:25:44AM +1100, Dave Chinner wrote:
On Thu, Oct 25, 2012 at 10:58:26AM +0800, Fengguang Wu wrote:
Hi Chen,
But how can bdi related ra_pages reflect different files' readahead
window? Maybe these different files are
On 10/25/2012 04:17 PM, Linus Torvalds wrote:
On Thu, Oct 25, 2012 at 5:16 AM, Peter Zijlstra wrote:
From: Rik van Riel
@@ -306,11 +306,26 @@ int ptep_set_access_flags(struct vm_area
pte_t entry, int dirty)
{
int changed = !pte_same(*ptep, entry);
+
Yes, it's a new way to do scheduler test. But why use kernel
threads? The info, total time, run time, wait time, preempt number,
all can be collected from tasks' sched info from /proc/pid/sched and
/proc/pid/stat.
I don't understand clearly about "pure scheduler performance" here. In
order to
On Thu, Oct 25, 2012 at 05:11:19PM -0700, Jonathan Nieder wrote:
> Hi,
>
> Greg Kroah-Hartman wrote:
>
> > commit 31fd84b95eb211d5db460a1dda85e004800a7b52 upstream.
> >
> > The min/max call needed to have explicit types on some architectures
> > (e.g. mn10300). Use clamp_t instead to avoid the
On 10/26/2012 08:25 AM, Dave Chinner wrote:
On Thu, Oct 25, 2012 at 10:58:26AM +0800, Fengguang Wu wrote:
Hi Chen,
But how can bdi related ra_pages reflect different files' readahead
window? Maybe these different files are sequential read, random read
and so on.
It's simple: sequential reads
On 10/26/2012 05:48 AM, Hugh Dickins wrote:
On Thu, 25 Oct 2012, Johannes Weiner wrote:
On Wed, Oct 24, 2012 at 09:36:27PM -0700, Hugh Dickins wrote:
On Wed, 24 Oct 2012, Dave Jones wrote:
Machine under significant load (4gb memory used, swap usage fluctuating)
triggered this...
WARNING: at
On 10/25/2012 12:17 PM, KOSAKI Motohiro wrote:
> On Wed, Oct 24, 2012 at 5:43 AM, Lai Jiangshan wrote:
>> Currently memory_hotplug only manages the node_states[N_HIGH_MEMORY],
>> it forgets to manage node_states[N_NORMAL_MEMORY]. it may cause
>> node_states[N_NORMAL_MEMORY] becomes incorrect.
>>
From: Yuanhan Liu
Firstly, this kind of type check doesn't work. It does something similay
like following:
void * __dummy = NULL;
__buf = __dummy;
__dummy is defined as void *. Thus it will not trigger warnings as
expected.
Second, we don't need that kind of check. Since the
On 10/26/2012 05:27 AM, Hugh Dickins wrote:
On Thu, 25 Oct 2012, Ni zhan Chen wrote:
On 10/25/2012 02:59 PM, Hugh Dickins wrote:
On Thu, 25 Oct 2012, Ni zhan Chen wrote:
I think it maybe caused by your commit [d189922862e03ce: shmem: fix
negative
rss in memcg memory.stat], one question:
On 10/25/12 18:41, Jun'ichi Nomura wrote:
> With 749fefe677 ("block: lift the initial queue bypass mode on
> blk_register_queue() instead of blk_init_allocated_queue()"),
> add_disk() eventually calls blk_queue_bypass_end().
> This change invokes the following warning when multipath is used.
...
>
On Thu, 25 Oct 2012 08:46:59 +0100
Ian Campbell wrote:
> On Thu, 2012-10-25 at 01:07 +0100, Mukesh Rathor wrote:
> > On Wed, 24 Oct 2012 16:44:11 -0700
> > Mukesh Rathor wrote:
> >
> > > >
> > > > +/* Indexes into space being mapped. */
> > > > +GUEST_HANDLE(xen_ulong_t) idxs;
> > >
On Wed, 24 Oct 2012 14:19:37 +0100
Ian Campbell wrote:
> Squeezing the necessary fields into the existing XENMEM_add_to_physmap
> interface was proving to be a bit tricky so we have decided to go with
> a new interface upstream (the XENMAPSPACE_gmfn_foreign interface using
>
On Fri, Oct 26, 2012 at 11:25:44AM +1100, Dave Chinner wrote:
> On Thu, Oct 25, 2012 at 10:58:26AM +0800, Fengguang Wu wrote:
> > Hi Chen,
> >
> > > But how can bdi related ra_pages reflect different files' readahead
> > > window? Maybe these different files are sequential read, random read
> > >
Hi, KOSAKI
On 09/28/2012 06:03 AM, KOSAKI Motohiro wrote:
> (9/27/12 2:47 AM), Lai Jiangshan wrote:
>> Currently memory_hotplug only manages the node_states[N_HIGH_MEMORY],
>> it forgets to manage node_states[N_NORMAL_MEMORY]. it causes
>> node_states[N_NORMAL_MEMORY] becomes stale.
>
> What's
Hi Jiri,
On Sat, 20 Oct 2012 16:33:08 +0200, Jiri Olsa wrote:
> hi,
> adding support to read sample values through the PERF_SAMPLE_READ
> sample type. It's now possible to specify 'S' modifier for an event
> and get its sample value by PERF_SAMPLE_READ.
I have a question. What's an actual
On Thu, 2012-10-25 at 14:55 -0400, Vivek Goyal wrote:
> On Thu, Oct 25, 2012 at 02:40:21PM -0400, Mimi Zohar wrote:
> > On Thu, 2012-10-25 at 10:10 -0400, Vivek Goyal wrote:
> > > On Thu, Oct 25, 2012 at 02:10:01AM -0400, Mimi Zohar wrote:
> > >
> > > [..]
> > > > IMA-appraisal verifies the
Hi Linus,
This pull fixes a fairly urgent issue with the NFSv2/v3 statd code that
is causing Oopses, as well as some long standing races with the SUNRPC
tcp code.
The following changes since commit 0e9e3e306c7e472bdcffa34c4c4584301eda03b3:
Merge tag 'stable/for-linus-3.7-rc2-tag' of
于 2012年10月26日 02:50, Greg KH 写道:
> On Sat, Oct 20, 2012 at 06:46:15AM +0300, Dan Carpenter wrote:
>> On Sat, Oct 06, 2012 at 03:23:56PM +0800, wwang wrote:
>>> We are still maintaining the SCSI driver for Realtek card reader,
>>> and will release the latest source code in the Github in the future.
On Thu, Oct 25, 2012 at 06:41:08PM -0400, Nick Bowler wrote:
> On 2012-10-25 16:29 -0500, Josh Cartwright wrote:
> > On Thu, Oct 25, 2012 at 04:17:01PM -0400, Nick Bowler wrote:
> > > Did you test this on any real hardware? I can't get the ZC702 to work
> > > with the UART mapped at this address
Hi Linus,
Just radeon fixes in this one,
some new PCI IDs,
ATPX regression fix,
async VM regression fixes
some module options fixes.
Dave.
The following changes since commit b8e902f24fdd16c4373ddc37a4e150c4afe9c6db:
drm/ttm: Fix a theoretical race in ttm_bo_cleanup_refs() (2012-10-23
Hi Christoph,
On Thu, Oct 25, 2012 at 03:19:27PM +, Christoph Lameter wrote:
> On Thu, 25 Oct 2012, Minchan Kim wrote:
>
> > #endif
> > + /*
> > +* True if page in this vma is reclaimed.
>
> What does that mean? All pages in the vma have been cleared out?
It means at least, more
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Bjørn Mork
commit 1452df6f1b7e396d89c2a1fdbdc0e0e839f97671 upstream.
Based on information from the ZTE Windows drivers.
Signed-off-by: Bjørn Mork
Signed-off-by: Greg Kroah-Hartman
---
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Bjørn Mork
commit 4b35f1c52943851b310afb09047bfe991ac8f5ae upstream.
Signed-off-by: Bjørn Mork
Signed-off-by: Greg Kroah-Hartman
---
drivers/usb/serial/option.c | 18 ++
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Daisuke Nishimura
commit 1f5320d5972aa50d3e8d2b227b636b370e608359 upstream.
notify_on_release must be triggered when the last process in a cgroup is
move to another. But if the first(and only)
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Trond Myklebust
commit cd0b16c1c3cda12dbed1f8de8f1a9b0591990724 upstream.
If the filehandle is stale, or open access is denied for some reason,
nlm_fopen() may return one of the NLMv4-specific
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Devin Heitmueller
commit a595c1ce4c9d572cf53513570b9f1a263d7867f2 upstream.
We weren't checking whether the resource was in use before calling
res_free(), so applications which called
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Jesse Barnes
commit 3bcf603f6d5d18bd9d076dc280de71f48add4101 upstream.
On CougarPoint and PantherPoint PCH chips, the timing generator may fail
to start after DP training completes. This is
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Greg Kroah-Hartman
This reverts 12d63702c53bc2230dfc997e91ca891f39cb6446 which was commit
303a7ce92064c285a04c870f2dc0192fdb2968cb upstream.
Taking hostname from uts namespace if not safe,
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Andrew Morton
commit 168bfeef7bba3f9784f7540b053e4ac72b769ce9 upstream.
If none of the elements in scrubrates[] matches, this loop will cause
__amd64_set_scrub_rate() to incorrectly use the
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Kees Cook
commit 2702b1526c7278c4d65d78de209a465d4de2885e upstream.
Calling uname() with the UNAME26 personality set allows a leak of kernel
stack contents. This fixes it by defensively
devfreq governors such as ondemand are controlled by a min and
max frequency, while governors like userspace governor allow us
to set a specific frequency.
However, for the same specific device, depending on the SoC, the
available frequencies can vary.
So expose the available frequencies as a
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Jacob Shin
commit 1e779aabe1f0768c2bf8f8c0a5583679b54a upstream.
On systems with very large memory (1 TB in our case), BIOS may report a
reserved region or a hole in the E820 map, even
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Ming Lei
commit c5211187f7ff8e8dbff4ebf7c011ac4c0ffe319c upstream.
If the write endpoint is interrupt type, usb_sndintpipe() should
be passed to usb_fill_int_urb() instead of
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Nicolas Boullis
commit 301a29da6e891e7eb95c843af0ecdbe86d01f723 upstream.
The current code assumes that CSIZE is 060, which appears to be
wrong on some arches (such as powerpc).
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Kees Cook
commit 31fd84b95eb211d5db460a1dda85e004800a7b52 upstream.
The min/max call needed to have explicit types on some architectures
(e.g. mn10300). Use clamp_t instead to avoid the
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Arnd Bergmann
commit fdc858a466b738d35d3492bc7cf77b1dac98bf7c upstream.
The sharpsl_pcmcia_ops structure gets passed into
sa11xx_drv_pcmcia_probe, where it gets accessed at run-time,
unlike
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Elric Fu
commit b92cc66c047ff7cf587b318fe377061a353c120f upstream.
Software have to abort command ring and cancel command
when a command is failed or hang. Otherwise, the command
ring will
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Elric Fu
commit 6e4468b9a0793dfb53eb80d9fe52c739b13b27fd upstream.
The patch is used to cancel command when the command isn't
acknowledged and a timeout occurs.
This patch should be
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: "jeff.liu"
[ Upstream commit 5175a5e76bbdf20a614fb47ce7a38f0f39e70226 ]
This is the revised patch for fixing rds-ping spinlock recursion
according to Venkat's suggestions.
RDS ping/pong over
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Elric Fu
commit b63f4053cc8aa22a98e3f9a97845afe6c15d0a0d upstream.
According to xHCI spec section 4.6.1.1 and section 4.6.1.2,
after aborting a command on the command ring, xHC will
generate a
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Dan Carpenter
commit 44009105081b51417f311f4c3be0061870b6b8ed upstream.
The "event" variable is a u16 so the shift will always wrap to zero
making the line a no-op.
Signed-off-by: Dan
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: "ramesh.naga...@gmail.com"
[ Upstream commit e1f165032c8bade3a6bdf546f8faf61fda4dd01c ]
The retry loop in neigh_resolve_output() and neigh_connected_output()
call dev_hard_header() with out
This patch introduces one module parameter of 'path' in firmware_class
to support customizing firmware image search path, so that people can
use its own firmware path if the default built-in paths can't meet their
demand[1], and the typical usage is passing the below from kernel command
parameter
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Alexey Kuznetsov
[ Upstream commit 4c67525849e0b7f4bd4fab2487ec9e43ea52ef29 ]
After commit e2446eaa ("tcp_v4_send_reset: binding oif to iif in no
sock case").. tcp resets are always lost,
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Jiri Kosina
[ Upstream commit a27032eee8cb6e16516f13c8a9752e9d5d4cc430 ]
There are multiple errors in how sys_sparc64_personality() handles
personality flags stored in top three bytes.
-
1 - 100 of 1720 matches
Mail list logo
