ARM is moving to stricter checks on readl/write functions,
so we need to use the correct types everywhere.
Cc: David Brown
Cc: Daniel Walker
Cc: Bryan Huntsman
Signed-off-by: Arnd Bergmann
---
arch/arm/mach-msm/smd.c | 19 ++-
1 file changed, 10 insertions(+), 9
ARM is moving to stricter checks on readl/write functions,
so we need to use the correct types everywhere.
Cc: Nicolas Ferre
Cc: Jean-Christophe Plagniol-Villard
Signed-off-by: Arnd Bergmann
---
arch/arm/mach-at91/at91x40.c |2 +-
arch/arm/mach-at91/at91x40_time.c
ARM is moving to stricter checks on readl/write functions,
so we need to use the correct types everywhere.
Cc: Krzysztof Halasa
Signed-off-by: Arnd Bergmann
---
arch/arm/mach-ks8695/cpu.c |2 +-
arch/arm/mach-ks8695/include/mach/hardware.h |2 +-
ARM is moving to stricter checks on readl/write functions,
so we need to use the correct types everywhere.
Cc: "James E.J. Bottomley"
Cc: linux-s...@vger.kernel.org
Signed-off-by: Arnd Bergmann
---
drivers/scsi/arm/eesox.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
ARM is moving to stricter checks on readl/write functions,
so we need to use the correct types everywhere.
At the moment, this patch conflicts with other patches in linux-next,
need to sort this out.
Cc: Imre Kaloz
Cc: Krzysztof Halasa
Signed-off-by: Arnd Bergmann
---
ARM is moving to stricter checks on readl/write functions,
so we need to use the correct types everywhere.
I'm not completely sure about this patch, and it will
probably require some arch/sh changes to go along with it,
but it's clear that something has to be done to avoid
getting hundreds of new
ARM is moving to stricter checks on readl/write functions,
so we need to use the correct types everywhere.
Cc: Viresh Kumar
Cc: Shiraz Hashim
Cc: spear-de...@list.st.com
Signed-off-by: Arnd Bergmann
---
arch/arm/mach-spear13xx/include/mach/spear.h | 14 +++---
ARM is moving to stricter checks on readl/write functions,
so we need to use the correct types everywhere.
This found a bug in mach-armadillo5x0.c, where we attempt mmio
on the MXC_CCM_RCSR address that is currently defined to 0xc
and consequently causes an illegal address access.
Signed-off-by:
ARM is moving to stricter checks on readl/write functions,
so we need to use the correct types everywhere.
Cc: Jochen Friedrich
Cc: Dominik Brodowski
Signed-off-by: Arnd Bergmann
---
arch/arm/mach-sa1100/include/mach/simpad.h |2 +-
arch/arm/mach-sa1100/simpad.c |2 +-
2
ARM is moving to stricter checks on readl/write functions,
so we need to use the correct types everywhere.
Cc: Alan Cox
Cc: Greg Kroah-Hartman
Signed-off-by: Arnd Bergmann
---
drivers/tty/serial/serial_ks8695.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
ARM is moving to stricter checks on readl/write functions,
so we need to use the correct types everywhere.
Cc: Kukjin Kim
Cc: Ben Dooks
Signed-off-by: Arnd Bergmann
---
arch/arm/plat-samsung/s5p-irq-gpioint.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
ARM is moving to stricter checks on readl/write functions,
so we need to use the correct types everywhere.
Cc: Tony Lindgren
Signed-off-by: Arnd Bergmann
---
arch/arm/plat-omap/include/plat/hardware.h | 18 +-
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git
ARM is moving to stricter checks on readl/write functions,
so we need to use the correct types everywhere.
Cc: Hartley Sweeten
Cc: Ryan Mallon
Signed-off-by: Arnd Bergmann
---
arch/arm/mach-ep93xx/include/mach/ts72xx.h | 10 +-
arch/arm/mach-ep93xx/ts72xx.c | 10
From: Stephen M. Cameron
If a command completes with a status of CMD_PROTOCOL_ERR, this
information should be conveyed to the SCSI mid layer, not dropped
on the floor. Unlike a similar bug in the hpsa driver, this bug
only affects tape drives and CD and DVD ROM drives in the cciss
driver, and
From: Stephen M. Cameron
If a command status of CMD_PROTOCOL_ERR is received, this
information should be conveyed to the SCSI mid layer, not
dropped on the floor. CMD_PROTOCOL_ERR may be received
from the Smart Array for any commands destined for an external
RAID controller such as a P2000, or
On Fri, Sep 14, 2012 at 02:14:57PM -0700, Linus Torvalds wrote:
> On Thu, Sep 13, 2012 at 11:23 PM, tip-bot for Jan Beulich
> wrote:
> >
> > x86: Prefer TZCNT over BFS
>
> This patch is insane.
>
> > For the moment, only do this when the respective generic-CPU
> > option is selected (as there
tty_port_tty_get() can return NULL after port hangup that may happen anytime.
The patch adds checks that tty_port_tty_get() returns nonNULL around places
where tty is actually used.
I have no actual hardware to test the patch, so I have updated rx side
processing from common sense only.
v2: rx
(Adding everybody to CC and leaving the below for reference.)
Guys,
as Nikolay says below, we have a regression in 3.6 with pgbench's
benchmark in postgresql.
I was able to reproduce it on another box here and did a bisection run.
It pointed to the commit below.
And yes, reverting that commit
On Fri, 2012-09-14 at 22:11 +0200, Ingo Molnar wrote:
> return -EPERF_CPU_PRECISE_EV_NOTSUPP;
I just don't like having to enumerate all possible fails, I'm too lazy.
Can't we be smarter about that? Could we do a {reason}x{bit-offset} like
thing?
Where we limit reason to a few simple things
Introduces new sysfs boolean knob /sys/kernel/mm/ksm/merge_nodes
which control merging pages across different numa nodes.
When it is set to zero only pages from the same node are merged,
otherwise pages from all nodes can be merged together (default behavior).
Typical use-case could be a lot of
On Thu, Sep 13, 2012 at 11:23 PM, tip-bot for Jan Beulich
wrote:
>
> x86: Prefer TZCNT over BFS
This patch is insane.
> For the moment, only do this when the respective generic-CPU
> option is selected (as there are no specific-CPU options
> covering the CPUs supporting TZCNT), and don't do
Hi Russell,
These are two patches I've been carrying in a larger series that
converts the Tegra PCIe controller driver to a proper platform driver.
Since the complete series didn't get much feedback, I've begun to post
smaller subsets in an effort to get them merged more easily.
The first patch
When using deferred driver probing, PCI host controller drivers may
actually require this function after the init stage.
Signed-off-by: Thierry Reding
---
arch/arm/kernel/bios32.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm/kernel/bios32.c
In order to allow drivers to specify private data for each controller,
this commit adds a private_data field to the struct hw_pci. This field
is an array of nr_controllers pointers that will be used to initialize
the private_data field of the corresponding controller's pci_sys_data
structure.
On Thu, 13 Sep 2012 20:15:26 -0700
Vikram Mulukutla wrote:
> The logic in do_raw_spin_lock attempts to acquire a spinlock
> by invoking arch_spin_trylock in a loop with a delay between
> each attempt. Now consider the following situation in a 2
> CPU system:
>
> 1. CPU-0 continually acquires
On Fri, Sep 14, 2012 at 01:55:55PM -0700, Tejun Heo wrote:
> On Fri, Sep 14, 2012 at 01:54:34PM -0700, Tejun Heo wrote:
> > On Fri, Sep 14, 2012 at 09:35:54PM +0200, Sasha Levin wrote:
> > > Prevent warnings generated by smatch due to unchecked dereference of
> > > 'new_xattr' in
On Fri, Sep 14, 2012 at 01:54:34PM -0700, Tejun Heo wrote:
> On Fri, Sep 14, 2012 at 09:35:54PM +0200, Sasha Levin wrote:
> > Prevent warnings generated by smatch due to unchecked dereference of
> > 'new_xattr' in __simple_xattr_set().
>
> Isn't this an actual bug w/ or w/o smatch? Remove
On Fri, Sep 14, 2012 at 09:35:54PM +0200, Sasha Levin wrote:
> Prevent warnings generated by smatch due to unchecked dereference of
> 'new_xattr' in __simple_xattr_set().
Isn't this an actual bug w/ or w/o smatch? Remove request (NULL
@value) w/o XATTR_REPLACE for an non-existent node would end
+cc Greg KH
On Fri, Sep 14, 2012 at 2:44 PM, Thierry Reding
wrote:
> In order to keep pci_fixup_irqs() around after init (e.g. for hotplug),
> mark it __devinit instead of __init. This requires the same change for
> the implementation of the pcibios_update_irq() function on all
> architectures.
Most architectures implement this in exactly the same way. Instead of
having each architecture duplicate this function, provide a single
implementation in the core and make it a weak symbol so that it can be
overridden on architectures where it is required.
Signed-off-by: Thierry Reding
---
In order to keep pci_fixup_irqs() around after init (e.g. for hotplug),
mark it __devinit instead of __init. This requires the same change for
the implementation of the pcibios_update_irq() function on all
architectures.
Signed-off-by: Thierry Reding
---
Note: Ideally these annotations should go
Hello, again.
On Fri, Sep 14, 2012 at 12:49:50PM -0700, Tejun Heo wrote:
> That said, if someone can think of a better solution, I'm all ears.
> One thing that *has* to be maintained is that it should be able to tag
> a resource in such way that its associated controllers are
> identifiable
> The concern I have is that even though we have gone through changes to
> help reduce the candidate vcpus we yield to, we still have a very poor
> idea of which vcpu really needs to run. The result is high cpu usage in
> the get_pid_task and still some contention in the double runqueue lock.
>
On Fri, 14 Sep 2012 20:00:09 +0900
Yasuaki Ishimatsu wrote:
> > @@ -187,9 +184,10 @@ void register_page_bootmem_info_node(struct
> > pglist_data *pgdat)
> > end_pfn = pfn + pgdat->node_spanned_pages;
> >
> > /* register_section info */
> > - for (; pfn < end_pfn; pfn +=
> As to the boot parameter to enable this function, you suggested using
> reset_devices. I found that on a certain platform resetting devices
> caused PCIe error due to a hardware bug. Therefore I think we need
> new parameter apart from reset_devices to disable this function on
> such a machine.
* Ingo Molnar wrote:
> * Peter Zijlstra wrote:
>
> > On Fri, 2012-09-14 at 11:00 -0700, Arnaldo Carvalho de Melo wrote:
> > > > Understood and there have been suggestions on how to definitely state
> > > > what the kernel side did not like. I like Peter's last suggestion --
> > > > something
Sasha,
On Fri, Sep 14, 2012 at 09:35:53PM +0200, Sasha Levin wrote:
> This reverts commit 0142145ddb1d6c841be4eae2c7a32dd18ad34b24.
>
> Short version:
>
> Not initializing 'new_xattr' at the beginning of __simple_xattr_set() may
> lead to
> dereferencing it later on in the function.
>
>
>
* Peter Zijlstra wrote:
> On Fri, 2012-09-14 at 11:00 -0700, Arnaldo Carvalho de Melo wrote:
> > > Understood and there have been suggestions on how to definitely state
> > > what the kernel side did not like. I like Peter's last suggestion --
> > > something along the lines of clearing attr on
When dump_one_policy() returns an error, e.g. because of a too small
buffer to dump the whole xfrm policy, xfrm_policy_netlink() returns
NULL instead of an error pointer. But its caller expects an error
pointer and therefore continues to operate on a NULL skbuff.
Cc: sta...@vger.kernel.org
Hi
2012/9/14 Daniel Vetter :
> On Fri, Sep 14, 2012 at 09:55:58AM -0400, Bobby Powers wrote:
>> This tree gives me recursive dependency problems, which ends up
>> removing a big (& important) part of my .config:
>>
>> [bpowers@fina linux]$ git reset --hard drm-intel-next-2012-09-09
>> HEAD is now
On Fri, Sep 14, 2012 at 12:44:39PM -0700, Tejun Heo wrote:
> I think there currently is too much (broken) flexibility and intent to
> remove it. That doesn't mean that removeing all flexibility is the
> right direction. It inherently is a balancing act and I think the
> proposed solution is a
Hello, Vivek.
On Fri, Sep 14, 2012 at 03:28:40PM -0400, Vivek Goyal wrote:
> Hmm.., In that case how libvirt will make use of blkio in the proposed
> scheme. We can't disable blkio nesting at "system" level. So We will
> have to disable it at each service level except "libvirtd" so that
>
Prevent warnings generated by smatch due to unchecked dereference of
'new_xattr' in __simple_xattr_set().
Signed-off-by: Sasha Levin
---
fs/xattr.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/xattr.c b/fs/xattr.c
index 508ec1d..f24e5d5 100644
--- a/fs/xattr.c
+++
PMD 0
[ 19.398034] Oops: [#1] PREEMPT SMP DEBUG_PAGEALLOC
[ 19.398034] Dumping ftrace buffer:
[ 19.398034](ftrace buffer empty)
[ 19.398034] CPU 0
[ 19.410800] Pid: 5913, comm: nomnom Tainted: G W
3.6.0-rc5-next-20120914-sasha-1-ge76e16e-dirty #332
[ 19.410853] RIP: 0
Hello,
(cc'ing Lennart and Kay)
On Fri, Sep 14, 2012 at 09:58:30AM -0400, Vivek Goyal wrote:
> I am little concerned about above and wondering how systemd and libvirt
> will interact and behave out of the box.
>
> Currently systemd does not create its own hierarchy under blkio and
> libvirt
On Fri, Sep 14, 2012 at 11:53:24AM -0700, Tejun Heo wrote:
[..]
> In addition, for some resources, granularity beyond certain point
> simply doesn't work. Per-service granularity might make sense for cpu
> but applying it by default would be silly for blkio.
Hmm.., In that case how libvirt will
On 09/14/2012 12:46 AM, Michel Lespinasse wrote:
> On Thu, Sep 13, 2012 at 11:14 AM, Jiri Slaby wrote:
>> Hi,
>>
>> I've just get the following BUG with today's -next. It happens every
>> time I try to update packages.
>>
>> kernel BUG at mm/huge_memory.c:1428!
>
> That is very likely my bug.
>
On Friday, September 14, 2012, Aaron Lu wrote:
> commit a606dac368eed5696fb38e16b1394f1d049c09e9 adds support to link
> devices which have _PRx, if a device does not have _PRx, a warning
> message will be printed.
>
> This commit is for ZPODD on Intel ZPODD capable platforms, on other
>
Hi folks,
I just upgraded an NFSv3 client machine to Linux 3.5.3 and am seeing the
following BUG. It occurs reproducibly a short time after the first
login in to the machine after boot (within one minute). There's a lot
of nfs4-looking functions in backtrace, which is weird as there are
> > > I went ahead and pushed the (updated) branch to my for-next, to get
> > > some integration coverage. It is that time. Jiri, I added your
> > > Acked-by on the hid patches for now, hope that is alright.
> >
> > Yes, it is, thanks Henrik.
> >
> > Dmitry, I can pull the whole lot into my tree
On Fri, Sep 14, 2012 at 12:19:06PM +0400, Glauber Costa wrote:
> I want oppose it as well, but I believe part of this exercise is to make
> the need to have hierarchy widespread. Warning on the case
> 1st-level-only case helps with that, even if we make more noise than we
> should.
>
> The reason
On Sep 14, 2012, at 1:38 PM, Myklebust, Trond wrote:
> On Fri, 2012-09-14 at 13:01 -0400, Chuck Lever wrote:
>> What happens if statd is restarted?
>
> Nothing unusual. Why?
The NSM upcall transport is a potential application for TCP + softconn, now
that a persistent rpc_clnt is used. It
Hi-
On Sep 14, 2012, at 10:25 AM, Stanislav Kinsbursky wrote:
> Taking hostname from uts namespace if not safe, because this cuold be
> performind during umount operation on child reaper death. And in this case
> current->nsproxy is NULL already.
>
> Signed-off-by: Stanislav Kinsbursky
> Cc:
On Fri, Sep 07, 2012 at 01:44:01PM -0700, Kent Overstreet wrote:
> Previously, dm_rq_clone_bio_info needed to be freed by the bio's
> destructor to avoid a memory leak in the blk_rq_prep_clone() error path.
> This gets rid of a memory allocation and means we can kill
> dm_rq_bio_destructor.
>
>
On Fri, Sep 14, 2012 at 12:22:09PM +0400, Glauber Costa wrote:
> This is not about being interested anymore
> This thing is more pressing than global warming.
Heh, yeah, let's save the polar bears. :)
--
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the
Hello,
On Fri, Sep 14, 2012 at 02:36:41PM -0400, Aristeu Rozanski wrote:
> if Serge is not planning to do it already, I can take a look in device_cgroup.
Yes please. :)
Thanks.
--
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Hello, Vivek.
On Fri, Sep 14, 2012 at 02:07:54PM -0400, Vivek Goyal wrote:
> I am curious that why are you planning to provide capability of controller
> specific view of hierarchy. To me it sounds pretty close to having
> separate hierarchies per controller. Just that it is a little more
>
On Fri, Sep 14, 2012 at 08:40:32PM +0200, Borislav Petkov wrote:
> I'll try a coarse bisection of the -rcs first, to see where the
> regression appeared.
Ok, 3.6-rc1 already shows the regression so I have to do the normal
bisection now to see which patch caused it.
Stay tuned.
--
Here are the networking fixes that have accumulated over the past few
weeks, most notably:
1) Use after free and new device IDs in bluetooth from Andre Guedes,
Yevgeniy Melnichuk, Gustavo Padovan, and Henrik Rydberg.
2) Fix crashes with short packet lengths and VLAN in pktgen, from
From: Lad, Prabhakar
channel_first_int[][] variable is used as a flag for the ISR,
This flag was being set after enabling the interrupts, There
where situations when the isr occurred even before the flag was set
due to which it was causing the application hang.
This patch sets
On Fri, Sep 14, 2012 at 10:47:44AM +0300, Nikolay Ulyanitsky wrote:
> Hi
> I compiled the 3.6-rc5 kernel with the same config from 3.5.3 and got
> the 15-20% performance drop of PostgreSQL 9.2 on AMD chipsets (880G,
> 990X).
>
> CentOS 6.3 x86_64
> PostgreSQL 9.2
> cpufreq scaling_governor -
Hi Ferruh,
> This driver is for Cypress TrueTouch(tm) Standard Product controllers,
> Generation4 devices.
>
> This is second version of driver, code re-structured to match with
> existing Generation3 driver code.
To integrate with the existing gen3 driver is clearly not the same as
creating a
Tejun,
On Thu, Sep 13, 2012 at 01:58:27PM -0700, Tejun Heo wrote:
> memcg can be handled by memcg people and I can handle cgroup_freezer
> and others with help from the authors. The problematic one is
> blkio. If anyone is interested in working on blkio, please be my
> guest. Vivek?
On Thu, Sep 06, 2012 at 03:34:55PM -0700, Kent Overstreet wrote:
> With the old code, when you allocate a bio from a bio pool you have to
> implement your own destructor that knows how to find the bio pool the
> bio was originally allocated from.
> This adds a new field to struct bio (bi_pool) and
On Fri, Sep 14, 2012 at 08:32:28PM +0200, Sedat Dilek wrote:
> Did you pushed this to [1] already?
Was still building. Pushed out now.
Thanks.
--
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More
Hi Jon,
On Thu, Sep 13, 2012 at 2:54 PM, Jonathan Corbet wrote:
>
> Well, there is some documentation here:
>
> https://lwn.net/Articles/447435/
>
I thank you for this. It really helped me getting started on videobuf2.
> This reminds me that I've always meant to turn it into something
Hello,
On Fri, Sep 14, 2012 at 08:23:41PM +0200, Peter Zijlstra wrote:
> Its hotplug, all hotplug stuff is synchronous, the last thing hotplug
> needs is the added complexity of async callbacks. Also pushing stuff out
> into worklets just to work around locking issues is vile.
I was asking
On Fri, Sep 14, 2012 at 7:00 PM, Tejun Heo wrote:
> Hello,
>
> On Fri, Sep 14, 2012 at 08:56:29AM +0200, Daniel Wagner wrote:
>> On 14.09.2012 05:17, Stephen Rothwell wrote:
>> >After merging the cgroup tree, today's linux-next build (powerpc
>> >ppc64_defconfig) failed like this:
>> >
>>
On Thu, Sep 13, 2012 at 06:55:29PM +0800, Shaohui Xie wrote:
> Error handle in case of DDR ECC off is wrong, sysfs entries have not been
> created, so edac_mc_free which frees a mci instance should not be called.
> Also, free mci's memory in this case.
Jus FYI: I ran into the same error in
On Thu, Sep 06, 2012 at 03:34:55PM -0700, Kent Overstreet wrote:
> With the old code, when you allocate a bio from a bio pool you have to
> implement your own destructor that knows how to find the bio pool the
> bio was originally allocated from.
>
> This adds a new field to struct bio (bi_pool)
On Fri, 2012-09-14 at 10:59 -0700, Tejun Heo wrote:
> Hello,
>
> On Fri, Sep 14, 2012 at 05:12:31PM +0800, Li Zefan wrote:
> > Agreed. The biggest issue in cpuset is if hotplug makes a cpuset's cpulist
> > empty the tasks in it will be moved to an ancestor cgroup, which requires
> > holding
Hello.
On 09/14/2012 03:13 PM, Stefano Stabellini wrote:
> Changes in v2:
> - mark Xen guest support on ARM as EXPERIMENTAL.
> Signed-off-by: Stefano Stabellini
> Acked-by: Konrad Rzeszutek Wilk
> ---
> arch/arm/Kconfig | 10 ++
> 1 files changed, 10 insertions(+), 0 deletions(-)
On Thu, Aug 23, 2012 at 3:35 PM, Tejun Heo wrote:
> pci_call_probe() uses work_on_cpu(), which creates and tears down a
> full kthread on each call, to invoke ->probe() on node local CPU for
> allocation affinity.
>
> The same goal can easily be achieved using a work item. This patch
> rewrites
On Fri, Sep 14, 2012 at 10:05:03AM -0600, David Ahern wrote:
> On 9/14/12 9:39 AM, Andrew Jones wrote:
> >
> >I recently tried 'perf script rwtop', and it immediately failed with
> >'failed to read event header'. Running it through strace I found that the
> >when rwtop.pl is reading from the pipe,
Hello.
On 09/14/2012 08:23 PM, Davide Ciminaghi wrote:
> From: Alessandro Rubini
> Patch dece904d itroduced chained_irq_enter/exit, which is only
Rather commit dece904d. And you need to also specify its summary in parens.
> available for arch/arm and the driver won't compile elsewhere.
>
thanks, propably works, will not test
On 12.09.2012 at 3:05 PM, Joe Perches wrote:
>
>auto75914...@hushmail.com reports that iptables does not correctly
>output the KERN_.
>
>$IPTABLES -A RULE_0_in -j LOG --log-level notice --log-prefix
>"DENY in: "
>
>result with linux 3.6-rc5
>Sep 12
On Thu, Sep 13, 2012 at 01:58:27PM -0700, Tejun Heo wrote:
[..]
> 6. Multiple hierarchies
>
> Apart from the apparent whness of it (I think I talked about
> that enough the last time[1]), there's a basic problem when more
> than one controllers interact - it's impossible to define
On Fri, Sep 14, 2012 at 12:58:16PM -0500, Shaun Ruffell wrote:
> From: Fengguang Wu
>
> From: Fengguang Wu
Darn it. If you push this through, mind fixing the above?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
On Fri, 2012-09-14 at 11:00 -0700, Arnaldo Carvalho de Melo wrote:
> > Understood and there have been suggestions on how to definitely state
> > what the kernel side did not like. I like Peter's last suggestion --
> > something along the lines of clearing attr on a failure except the
> > offending
There are no more embedded kobjects in struct mem_ctl_info. Remove a header and
a comment that does not reflect the code anymore.
Signed-off-by: Shaun Ruffell
---
drivers/edac/edac_mc.c | 7 ---
include/linux/edac.h | 1 -
2 files changed, 8 deletions(-)
diff --git
v2:
Use '!device_is_registered(>dev)' instead of 'if (!mci->bus.name)' to
check if mem_ctl_info has been registered with sysfs.
v1:
With kernel version 3.6-rc2 on a Dell Poweredge 2600 I experienced a NULL
pointer dereference that did not occur with on 3.5. I believe the error is
related to
edac_mc_free() may need to deallocate any memory associated with struct
mem_ctl_info directly if the structure was never registered with sysfs in
edac_mc_add_mc(). This moves the error handling code from edac_mc_alloc() into a
dedicated function to be called by edac_mc_free() as well if necessary.
From: Fengguang Wu
From: Fengguang Wu
We need to free up memory in this order:
free csrows[i]->channels[j]
free csrows[i]->channels
free csrows[i]
free csrows
Signed-off-by: Fengguang Wu
---
drivers/edac/edac_mc.c | 12 +++-
1 file changed, 7 insertions(+), 5 deletions(-)
commit 7a253c2954dad9d70fa2e07b45b55ea4bee6c6c7
Dave,
This is a batch of fixes intended for the 3.6 stream.
Arend van Spriel sends a simple thinko fix to correct a constant,
preventing the setting of an invalid power level.
Colin Ian King gives us a simple allocation failure check to avoid a
Em Fri, Sep 14, 2012 at 05:43:42AM -0600, David Ahern escreveu:
> On 9/14/12 5:36 AM, Ingo Molnar wrote:
> >Well, then that is useful information we *lost*, and that situation
> >needs to be improved on the ABI side: an expanded error code present
> >in the event structure, copied back to
Hello,
On Fri, Sep 14, 2012 at 05:12:31PM +0800, Li Zefan wrote:
> Agreed. The biggest issue in cpuset is if hotplug makes a cpuset's cpulist
> empty the tasks in it will be moved to an ancestor cgroup, which requires
> holding cgroup lock. We have to either change cpuset's behavior or eliminate
On Fri, Sep 14, 2012 at 09:27:32AM +0200, Linus Walleij wrote:
> On Thu, Sep 13, 2012 at 6:58 PM, Paul E. McKenney
> wrote:
> > On Thu, Sep 13, 2012 at 09:49:14AM -0700, John Stultz wrote:
> >> I saw this once as well testing the fix to Daniel's deep idle hang
> >> issue (also on 32 bit).
>
>
Hello, Peter.
On Fri, Sep 14, 2012 at 01:15:02PM +0200, Peter Zijlstra wrote:
> On Thu, 2012-09-13 at 13:58 -0700, Tejun Heo wrote:
> > The cpu ones handle nesting correctly - parent's accounting includes
> > children's, parent's configuration affects children's unless
> > explicitly
PDE/PTE update code uses CP ring for memory writes.
All page table entries are preallocated for now in alloc_pt().
It is made as whole because it's hard to divide it to several patches
that compile and doesn't break anything being applied separately.
Tested on cayman card.
v2 changes:
* rebased
From: Christian König
Cleanup the interface in preparation for hierarchical page tables.
v2: * add incr parameter to set_page for simple scattered PTs uptates
* added PDE-specific flags to r600_flags and radeon_drm.h
* removed superflous value masking with 0x
Signed-off-by:
Cypress TrueTouch(tm) Standard Product controllers, Generation4
devices, SPI adapter module.
This driver adds communication support with TTSP controller
using SPI bus.
Signed-off-by: Ferruh Yigit
---
drivers/input/touchscreen/Kconfig | 12 ++
drivers/input/touchscreen/Makefile |
Cypress TrueTouch(tm) Standard Product controllers, Generation4
devices, I2C adapter module.
This driver adds communication support with TTSP controller
using I2C bus.
Signed-off-by: Ferruh Yigit
---
drivers/input/touchscreen/Kconfig | 12 ++
drivers/input/touchscreen/Makefile |
This driver is for Cypress TrueTouch(tm) Standard Product controllers,
Generation4 devices.
This is second version of driver, code re-structured to match with
existing Generation3 driver code.
Driver consist of three modules:
- Core module: Main module, gets data from TTSP controller,
sent MT
Hello, Glauber.
On Fri, Sep 14, 2012 at 12:16:31PM +0400, Glauber Costa wrote:
> Can we please keep some key userspace guys CCd?
Yeap, thanks for adding the ccs.
> > 1. cpu and cpuacct
...
> > Me, working on it.
> I can work on it as well if you want. I dealt with it many times in
> the past,
On Fri, Sep 14, 2012 at 06:31:59PM +0100, Arnd Bergmann wrote:
> On Friday 14 September 2012, Catalin Marinas wrote:
> > (revisiting unanswered emails :))
> >
> > On Wed, Aug 15, 2012 at 01:33:55AM +0100, Olof Johansson wrote:
> > > On Tue, Aug 14, 2012 at 06:52:14PM +0100, Catalin Marinas wrote:
On Wed, Aug 15, 2012 at 01:10:43AM +0100, Olof Johansson wrote:
> On Tue, Aug 14, 2012 at 06:52:09PM +0100, Catalin Marinas wrote:
> > +#ifndef __ASM_CPUTYPE_H
> > +#define __ASM_CPUTYPE_H
> > +
> > +#define ID_MIDR_EL1"midr_el1"
> > +#define ID_CTR_EL0 "ctr_el0"
> > +
> >
On Fri, 2012-09-14 at 13:01 -0400, Chuck Lever wrote:
> What happens if statd is restarted?
Nothing unusual. Why?
> Sent from my iPhone
>
> On Sep 14, 2012, at 10:25 AM, Stanislav Kinsbursky
> wrote:
>
> > This is a bug fix for https://bugzilla.redhat.com/show_bug.cgi?id=830862.
> >
> > The
On Wed, Aug 15, 2012 at 12:50:13AM +0100, Olof Johansson wrote:
> On Tue, Aug 14, 2012 at 06:52:08PM +0100, Catalin Marinas wrote:
>
> > diff --git a/arch/arm64/kernel/process.c b/arch/arm64/kernel/process.c
> > new file mode 100644
> > index 000..c4a4e1c
> > --- /dev/null
> > +++
(additional note to simplify the review)
On 09/14, Oleg Nesterov wrote:
>
> Note
> that we do this unconditionally, see the next patch(es).
IOW, we could move it under "if (!uprobe)" branch, but we do not.
This is mostly needed for 2/5, which in turn is needed for 3/5.
If can_skip_sstep()
On Friday 14 September 2012, Catalin Marinas wrote:
> (revisiting unanswered emails :))
>
> On Wed, Aug 15, 2012 at 01:33:55AM +0100, Olof Johansson wrote:
> > On Tue, Aug 14, 2012 at 06:52:14PM +0100, Catalin Marinas wrote:
> > > +/*
> > > + * I/O port access primitives.
> > > + */
> > >
101 - 200 of 1246 matches
Mail list logo
