From: Douglas Gilbert
Signed-off-by: Douglas Gilbert
Signed-off-by: Nicolas Ferre
---
Hi all,
Here is the third revision of this patch. I plan to include it in a
pull-request real-soon-now!
v3: - move to "at91-" prefix for .dts[i] files
- remove the rtc activation code because of the ongo
On Thu, Apr 04, 2013 at 08:57:06AM -0600, Bjorn Helgaas wrote:
> On Thu, Apr 4, 2013 at 8:50 AM, Neil Horman wrote:
> > On Thu, Apr 04, 2013 at 03:27:29PM +0100, David Woodhouse wrote:
> >> On Wed, 2013-04-03 at 17:53 -0600, Bjorn Helgaas wrote:
> >> > );
> >> > > +
> >> > > + if ((revision
Hi Florian,
On 24.03.2013 20:03, Florian Fainelli wrote:
> Your phylib implementation looks good now, just some minor comments below:
Thanks for the review. I'll try to address your new comments in a few
days (currently swamped).
Thanks,
Stefan
--
To unsubscribe from this list: send the line "u
On 04.04.2013, at 15:33, Michael S. Tsirkin wrote:
> On Thu, Apr 04, 2013 at 03:06:42PM +0200, Alexander Graf wrote:
>>
>> On 04.04.2013, at 14:56, Gleb Natapov wrote:
>>
>>> On Thu, Apr 04, 2013 at 02:49:39PM +0200, Alexander Graf wrote:
On 04.04.2013, at 14:45, Gleb Natapov wrote:
On Wed 03-04-13 17:14:11, Li Zefan wrote:
> Now memcg has the same life cycle as the corresponding cgroup.
> Kill the useless refcnt.
>
> Signed-off-by: Li Zefan
Acked-by: Michal Hocko
Thanks!
> ---
> mm/memcontrol.c | 24 +---
> 1 file changed, 1 insertion(+), 23 deletio
On Wed 03-04-13 17:13:21, Li Zefan wrote:
> The cgroup core guarantees it's always safe to access the parent.
>
> Signed-off-by: Li Zefan
I would just prefer if you put a comment into place where we used to
take a reference to parent so that it is more obvious in the code.
See bellow.
Acked-by:
On Wed 03-04-13 17:13:08, Li Zefan wrote:
> Suppose we rmdir a cgroup and there're still css refs, this cgroup won't
> be freed. Then we rmdir the parent cgroup, and the parent is freed due
> to css ref draining to 0. Now it would be a disaster if the child cgroup
> tries to access its parent.
>
>
On Thu 04-04-13 08:22:13, Tejun Heo wrote:
> On Thu, Apr 04, 2013 at 05:20:28PM +0200, Michal Hocko wrote:
> > > But what harm does an additional reference do?
> >
> > No harm at all. I just wanted to be sure that this is not yet another
> > "for memcg" hack. So if this is useful for other control
Hi Linus,
please, pull a single UBIFS fix for v3.9.
The following changes since commit f6161aa153581da4a3867a2d1a7caf4be19b6ec9:
Linux 3.9-rc2 (2013-03-10 16:54:19 -0700)
are available in the git repository at:
git://git.infradead.org/linux-ubifs.git tags/upstream-3.9-rc6
for you to fetch
On 04/03/2013 09:10 PM, Douglas Gilbert :
> On 13-04-02 02:48 PM, Olof Johansson wrote:
>> Hi,
>>
>> I just saw this since it came in through a pull request
>>
>> On Tue, Mar 26, 2013 at 4:39 AM, Nicolas Ferre
>> wrote:
>>> From: Douglas Gilbert
>>>
>>> Signed-off-by: Douglas Gilbert
>>> Signed-
Hi Vineet,
Our stress testing campaign has just successfully completed on this
patch. It seems to solve several issues we have seen in unpatched
versions, amongst others the original timer issue, a crash in hrtimer
rb-tree manipulation etc.
Greetings,
Christian
On Wed, Apr 03, 2013 at 07:41:22
On Thu, Apr 04, 2013 at 04:14:57PM +0300, Gleb Natapov wrote:
> On Thu, Apr 04, 2013 at 03:06:42PM +0200, Alexander Graf wrote:
> >
> > On 04.04.2013, at 14:56, Gleb Natapov wrote:
> >
> > > On Thu, Apr 04, 2013 at 02:49:39PM +0200, Alexander Graf wrote:
> > >>
> > >> On 04.04.2013, at 14:45, Gl
On Thu, 2013-04-04 at 08:12 -0700, K. Y. Srinivasan wrote:
> Here is the code snippet for scanning LUNS (drivers/scsi/scsi_scan.c in
> function
> __scsi_scan_target()):
>
> /*
> * Scan LUN 0, if there is some response, scan further. Ideally, we
> * would not configure L
On Thu, 2013-04-04 at 13:00 +, Sethi Varun-B16395 wrote:
>
> > -Original Message-
> > From: Alex Williamson [mailto:alex.william...@redhat.com]
> > Sent: Wednesday, April 03, 2013 11:32 PM
> > To: Joerg Roedel
> > Cc: Sethi Varun-B16395; Yoder Stuart-B08248; Wood Scott-B07421;
> > io..
On Thu, Apr 04, 2013 at 05:20:28PM +0200, Michal Hocko wrote:
> > But what harm does an additional reference do?
>
> No harm at all. I just wanted to be sure that this is not yet another
> "for memcg" hack. So if this is useful for other controllers then I have
> no objections of course.
I think
On Thu 04-04-13 06:53:53, Tejun Heo wrote:
> Hey,
>
> On Thu, Apr 04, 2013 at 01:37:50PM +0200, Michal Hocko wrote:
> > On Wed 03-04-13 17:13:08, Li Zefan wrote:
> > > Suppose we rmdir a cgroup and there're still css refs, this cgroup won't
> > > be freed. Then we rmdir the parent cgroup, and the
A few years back intel published a spec update:
http://www.intel.com/content/dam/doc/specification-update/5520-and-5500-chipset-ioh-specification-update.pdf
For the 5520 and 5500 chipsets which contained an errata (specificially errata
53), which noted that these chipsets can't properly do interru
On Thu, Apr 4, 2013 at 8:50 AM, Neil Horman wrote:
> On Thu, Apr 04, 2013 at 03:27:29PM +0100, David Woodhouse wrote:
>> On Wed, 2013-04-03 at 17:53 -0600, Bjorn Helgaas wrote:
>> > );
>> > > +
>> > > + if ((revision == 0x13) && irq_remapping_enabled) {
>> > > +pr_warn(HW_ERR
On 15:01 Thu 07 Mar , oskar.and...@sonymobile.com wrote:
> From: Aleksej Makarov
>
> When waking up the platform by pressing a specific key, sending a
> release on that key makes it impossible to react on the event in
> user-space.
>
> Cc: Dmitry Torokhov
> Reviewed-by: Radovan Lekanovic
>
The Linux mutex code has a MUTEX_SPIN_ON_OWNER configuration
option that was enabled by default in major distributions like Red
Hat. Allowing threads waiting on mutex to spin while the mutex owner
is running will theoretically reduce latency on the acquisition of
mutex at the expense of energy effi
This patch set is a collection of 3 different mutex related patches
aimed at improving mutex performance especially for system with large
number of CPUs. This is achieved by doing less atomic operations and
mutex spinning (when the CONFIG_MUTEX_SPIN_ON_OWNER is on).
The first patch reduces the num
>From 5c529597e922c26910fe49b8d5f93aeaca9a2415 Mon Sep 17 00:00:00 2001
From: Lai Jiangshan
Date: Thu, 4 Apr 2013 10:05:38 +0800
destroy_workqueue() performs several sanity checks before proceeding
with destruction of a workqueue. One of the checks verifies that
refcnt of each pwq (pool_workqueu
In the __mutex_lock_common() function, an initial entry into
the lock slow path will cause two atomic_xchg instructions to be
issued. Together with the atomic decrement in the fast path, a total
of three atomic read-modify-write instructions will be issued in
rapid succession. This can cause a lot
The current mutex spinning code allow multiple tasks to spin on a
single mutex concurrently. There are two major problems with this
approach:
1. This is not very energy efficient as the spinning tasks are not
doing useful work. The spinning tasks may also block other more
important or use
We eventually would like to remove the rwlock cpufreq_driver_lock or convert
it back to a spinlock and protect the read sections with RCU. The first step in
that is moving the cpufreq_driver to use the rcu.
I don't see an easy wasy to protect the cpufreq_cpu_data structure with the
RCU, so I am le
On Thu, Apr 04, 2013 at 03:27:29PM +0100, David Woodhouse wrote:
> On Wed, 2013-04-03 at 17:53 -0600, Bjorn Helgaas wrote:
> > );
> > > +
> > > + if ((revision == 0x13) && irq_remapping_enabled) {
> > > +pr_warn(HW_ERR "This system BIOS has enabled interrupt
> > > remapping\n
On Thursday 04 April 2013, Viresh Kumar wrote:
>
> On 4 April 2013 18:32, Arnd Bergmann wrote:
> > Moving the files is good, but I don't see a reason to make the cbe_cpufreq.h
> > header globally visible in include/linux/. Isn't it just used by as the
> > interface between ppc_cbe_cpufreq_pmi.c
On Thu, 4 Apr 2013, Felipe Balbi wrote:
> > >> Some subsystems handle this issue by calling pm_runtime_get_sync()
> > >> before probing a driver and pm_runtime_put_sync() after unbinding the
> > >> driver. If the driver is runtime-PM-enabled, it then does its own
> > >> put_sync near the end of i
Here is the code snippet for scanning LUNS (drivers/scsi/scsi_scan.c in
function
__scsi_scan_target()):
/*
* Scan LUN 0, if there is some response, scan further. Ideally, we
* would not configure LUN 0 until all LUNs are scanned.
*/
res = scsi_probe_and
On Thu, Apr 04, 2013 at 04:02:57PM +0200, Alexander Graf wrote:
>
> On 04.04.2013, at 14:58, Michael S. Tsirkin wrote:
>
> > On Thu, Apr 04, 2013 at 02:22:09PM +0200, Alexander Graf wrote:
> >>
> >> On 04.04.2013, at 14:08, Gleb Natapov wrote:
> >>
> >>> On Thu, Apr 04, 2013 at 01:57:34PM +0200
On 04/04/2013 10:30 AM, Kirill A. Shutemov wrote:
> Sasha Levin wrote:
>> Ping? I'm seeing a whole bunch of these with current -next.
>
> Do you have a way to reproduce?
Not really, trinity just manages to make it happen quite often.
I can add something in the code to spew more debug info when i
Hello,
On Thu, Apr 04, 2013 at 10:05:37AM +0800, Lai Jiangshan wrote:
> calculate the node of the pool earlier, and allocate the pool
> from the node.
>
> Signed-off-by: Lai Jiangshan
> ---
> kernel/workqueue.c | 29 +++--
> 1 files changed, 15 insertions(+), 14 deleti
On Thu, Apr 04, 2013 at 10:05:36AM +0800, Lai Jiangshan wrote:
> When we fail to allocate the node pwq, we can use the default pwq
> for the node.
>
> Thus we can avoid failure after allocated default pwq, and remove
> some code for failure path.
I don't know about this one. The reason why we fa
On Thu, Apr 04, 2013 at 03:06:42PM +0200, Alexander Graf wrote:
>
> On 04.04.2013, at 14:56, Gleb Natapov wrote:
>
> > On Thu, Apr 04, 2013 at 02:49:39PM +0200, Alexander Graf wrote:
> >>
> >> On 04.04.2013, at 14:45, Gleb Natapov wrote:
> >>
> >>> On Thu, Apr 04, 2013 at 02:39:51PM +0200, Alex
2013/4/4 Frederic Weisbecker :
> 2013/4/3 Vincent Guittot :
>> On my smp platform which is made of 5 cores in 2 clusters, I have the
>> nr_busy_cpu field of sched_group_power struct that is not null when the
>> platform is fully idle. The root cause is:
>> During the boot sequence, some CPUs reach
* Oleg Nesterov [2013-03-29 19:15:48]:
> struct uprobe_trace_entry_head has a single member for reporting,
> "unsigned long ip". If we want to support uretprobes we need to
> create another struct which has "func" and "ret_ip" and duplicate
> a lot of functions, like trace_kprobe.c does.
>
> To
* Oleg Nesterov [2013-03-29 19:15:45]:
> uprobe_trace_func() is never called with irqs or preemption
> disabled, no need to ask preempt_count() or local_save_flags().
>
> Signed-off-by: Oleg Nesterov
Acked-by: Srikar Dronamraju
Adding Masami in the Cc.
> ---
> kernel/trace/trace_uprobe.c |
* Oleg Nesterov [2013-03-29 19:15:43]:
> seq_print_ip_sym(ip) in print_uprobe_event() is pointless,
> kallsyms_lookup(ip) can not resolve a user-space address.
>
> Signed-off-by: Oleg Nesterov
Acked-by: Srikar Dronamraju
> ---
> kernel/trace/trace_uprobe.c |8 +---
> 1 files changed
* Oleg Nesterov [2013-03-29 19:15:40]:
> uprobe_trace_func() and uprobe_perf_func() do not need task_pt_regs(),
> we already have "struct pt_regs *regs".
>
> Signed-off-by: Oleg Nesterov
Acked-by: Srikar Dronamraju
Adding Masami in the cc.
> ---
> kernel/trace/trace_uprobe.c |4 ++--
>
Sasha Levin wrote:
> Ping? I'm seeing a whole bunch of these with current -next.
Do you have a way to reproduce?
--
Kirill A. Shutemov
--
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://
On Wed, 2013-04-03 at 17:53 -0600, Bjorn Helgaas wrote:
> );
> > +
> > + if ((revision == 0x13) && irq_remapping_enabled) {
> > +pr_warn(HW_ERR "This system BIOS has enabled interrupt
> > remapping\n"
> > +"on a chipset that contains an errata making
I am not on the list Please forward. It works some times on a openSuSE
12.3 KDE 4 system the kernel is 3.9.0-rc5
donn@m1l-suse:~> /usr/sbin/hwinfo --sound
19: PCI 14.2: 0403 Audio device
[Created at pci.319]
Unique ID: 5Dex.9zCmC9gVD38
SysFS ID: /devices/pci:00/:00:14.2
SysFS Bu
On Thu, 2013-04-04 at 14:48 +0900, Takao Indoh wrote:
>
> - DMAR fault messages floods and second kernel does not boot. Recently I
> saw similar report. https://lkml.org/lkml/2013/3/8/120
Right. So the fix for that is to make the subsequent errors silent,
until/unless we actually get a request
2013/4/3 Vincent Guittot :
> On my smp platform which is made of 5 cores in 2 clusters, I have the
> nr_busy_cpu field of sched_group_power struct that is not null when the
> platform is fully idle. The root cause is:
> During the boot sequence, some CPUs reach the idle loop and set their
> NOHZ_ID
On 04/04/2013 10:20 PM, Tejun Heo wrote:
> Hello,
>
> On Thu, Apr 04, 2013 at 10:16:39PM +0800, Aaron Lu wrote:
>> It probably wouldn't happen for normal user, only for some SCSI driver
>> developers like me, e.g. the sr_mod will normally load during boot, and
>> when I made some changes to the co
It might be a kernel disaster if one sysfs entry is freed but
still referenced by sysfs tree.
Recently Dave and Sasha reported one use-after-free problem on
sysfs entry, and the problem has been troubleshooted with help
of debug message added in this patch.
Given sysfs_get_dirent/sysfs_put are ex
Hello,
On Thu, Apr 04, 2013 at 10:16:39PM +0800, Aaron Lu wrote:
> It probably wouldn't happen for normal user, only for some SCSI driver
> developers like me, e.g. the sr_mod will normally load during boot, and
> when I made some changes to the code, I'll unload the driver and reload
> it. This i
Hi Yaniv, Maya,
On Mon, Mar 11 2013, Luca Porzio (lporzio) wrote:
> In case of Sanitize timeout, the eMMC might go in an unclear state.
> May I suggest to:
> - issue an HPI before leaving thus bring the eMMC back into safe status
> - report the 'sanitize not complete error' and let the user decide
On Thu, 2013-04-04 at 14:48 +0800, Ram Pai wrote:
> On Wed, Apr 03, 2013 at 01:55:05PM -0600, Toshi Kani wrote:
> > On Wed, 2013-04-03 at 13:37 +0800, Ram Pai wrote:
> > > On Tue, Apr 02, 2013 at 10:17:29AM -0600, Toshi Kani wrote:
> > > > + while ((res = *p)) {
>
> ...snip...
>
> > > > +
The current update of the rq's load can be erroneous when RT tasks are
involved
The update of the load of a rq that becomes idle, is done only if the avg_idle
is less than sysctl_sched_migration_cost. If RT tasks and short idle duration
alternate, the runnable_avg will not be updated correctly and
On Wed, Apr 03, 2013 at 05:38:25PM -0700, Yinghai Lu wrote:
> Vivek found old kexec-tools does not work new kernel anymore.
>
> So change back crashkernel= back to old behavoir, and add crashkernel_high=
> to let user decide if buffer could be above 4G, and also new kexec-tools will
> be needed.
>
On 04/04/2013 10:03 PM, Tejun Heo wrote:
> On Thu, Apr 04, 2013 at 10:01:14PM +0800, Aaron Lu wrote:
>> In blk_register_queue, we will end bypass mode for the queue; but in
>> blk_unregister_queue, we didn't start bypass mode for it. This would
>> cause the WARN_ON_ONCE(q->bypass_depth < 0) to trig
On Thu, Apr 04, 2013 at 10:05:34AM +0800, Lai Jiangshan wrote:
> merge the code of clearing POOL_DISASSOCIATED to rebind_workers(), and
> rename rebind_workers() to associate_cpu_pool().
>
> It merges high related code together and simplify
> workqueue_cpu_up_callback().
>
> Signed-off-by: Lai Ji
On Thu, Apr 04, 2013 at 03:56:49PM +0300, Gleb Natapov wrote:
> On Thu, Apr 04, 2013 at 02:49:39PM +0200, Alexander Graf wrote:
> >
> > On 04.04.2013, at 14:45, Gleb Natapov wrote:
> >
> > > On Thu, Apr 04, 2013 at 02:39:51PM +0200, Alexander Graf wrote:
> > >>
> > >> On 04.04.2013, at 14:38, Gl
Hello, Lai.
On Thu, Apr 04, 2013 at 10:05:32AM +0800, Lai Jiangshan wrote:
> @@ -4757,25 +4747,16 @@ void thaw_workqueues(void)
> {
> struct workqueue_struct *wq;
> struct pool_workqueue *pwq;
> - struct worker_pool *pool;
> - int pi;
>
> mutex_lock(&wq_pool_mutex);
>
On Wed, Apr 03, 2013 at 05:38:23PM -0700, Yinghai Lu wrote:
[..]
> + if (ret != 0) {
> + /*
> + * two parts from lib/swiotlb.c:
> + * swiotlb size: user specified with swiotlb= or default.
> + * swiotlb overflow buffer: now is hardco
On Thu, 4 Apr 2013, Joonsoo Kim wrote:
> Pekka alreay applied it.
> Do we need update?
Well I thought the passing of the count via lru.next would be something
worthwhile to pick up.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@v
Le 01/15/13 17:24, Florian Fainelli a écrit :
This patch makes CONFIG_PPS_DEBUG and CONFIG_NTP_PPS be hidden if
CONFIG_PPS is not selected, such that we are not prompted for these
configuration options if CONFIG_PPS is not set.
It seems like this patch has not been merged, yet it is still appli
On Thu, Apr 04, 2013 at 02:39:51PM +0200, Alexander Graf wrote:
>
> On 04.04.2013, at 14:38, Gleb Natapov wrote:
>
> > On Thu, Apr 04, 2013 at 02:32:08PM +0200, Alexander Graf wrote:
> >>
> >> On 04.04.2013, at 14:08, Gleb Natapov wrote:
> >>
> >>> On Thu, Apr 04, 2013 at 01:57:34PM +0200, Alex
Ping? I'm seeing a whole bunch of these with current -next.
Thanks,
Sasha
On 03/29/2013 09:04 AM, Sasha Levin wrote:
> Hi all,
>
> While fuzzing with trinity inside a KVM tools guest running latest -next
> kernel,
> I've stumbled on the following.
>
> It seems that the code in do_huge_pmd_wp_
On Wed, Apr 03, 2013 at 02:55:08PM -0400, J. Bruce Fields wrote:
> On Wed, Apr 03, 2013 at 06:58:43PM +0800, Yanchuan Nian wrote:
> > On Mon, Apr 01, 2013 at 09:50:44PM -0400, J. Bruce Fields wrote:
> > > On Wed, Mar 13, 2013 at 11:04:54PM +0800, Yanchuan Nian wrote:
> > > > 2013/3/11 J. Bruce Fiel
On Thu, Apr 04, 2013 at 02:32:08PM +0200, Alexander Graf wrote:
>
> On 04.04.2013, at 14:08, Gleb Natapov wrote:
>
> > On Thu, Apr 04, 2013 at 01:57:34PM +0200, Alexander Graf wrote:
> >>
> >> On 04.04.2013, at 12:50, Michael S. Tsirkin wrote:
> >>
> >>> With KVM, MMIO is much slower than PIO,
On Thu, Apr 04, 2013 at 10:01:14PM +0800, Aaron Lu wrote:
> In blk_register_queue, we will end bypass mode for the queue; but in
> blk_unregister_queue, we didn't start bypass mode for it. This would
> cause the WARN_ON_ONCE(q->bypass_depth < 0) to trigger if the queue gets
> registered, unregister
On 04.04.2013, at 14:58, Michael S. Tsirkin wrote:
> On Thu, Apr 04, 2013 at 02:22:09PM +0200, Alexander Graf wrote:
>>
>> On 04.04.2013, at 14:08, Gleb Natapov wrote:
>>
>>> On Thu, Apr 04, 2013 at 01:57:34PM +0200, Alexander Graf wrote:
On 04.04.2013, at 12:50, Michael S. Tsirkin w
In blk_register_queue, we will end bypass mode for the queue; but in
blk_unregister_queue, we didn't start bypass mode for it. This would
cause the WARN_ON_ONCE(q->bypass_depth < 0) to trigger if the queue gets
registered, unregistered and then again registered, e.g. unload scsi
cdrom module driver
On Thu, Apr 04, 2013 at 02:22:09PM +0200, Alexander Graf wrote:
>
> On 04.04.2013, at 14:08, Gleb Natapov wrote:
>
> > On Thu, Apr 04, 2013 at 01:57:34PM +0200, Alexander Graf wrote:
> >>
> >> On 04.04.2013, at 12:50, Michael S. Tsirkin wrote:
> >>
> >>> With KVM, MMIO is much slower than PIO,
A few years back intel published a spec update:
http://www.intel.com/content/dam/doc/specification-update/5520-and-5500-chipset-ioh-specification-update.pdf
For the 5520 and 5500 chipsets which contained an errata (specificially errata
53), which noted that these chipsets can't properly do interru
Hey,
On Thu, Apr 04, 2013 at 01:37:50PM +0200, Michal Hocko wrote:
> On Wed 03-04-13 17:13:08, Li Zefan wrote:
> > Suppose we rmdir a cgroup and there're still css refs, this cgroup won't
> > be freed. Then we rmdir the parent cgroup, and the parent is freed due
> > to css ref draining to 0. Now i
On Wed, Apr 03, 2013 at 05:56:00PM -0700, Yinghai Lu wrote:
[..]
>
> One big rang under 4G is working well till second kernel need more than 512M
> on bigger system with more memory.
Currently one range is allocated below 896MB (and not 4G). So if we extend
crashkernel=X to first try below 896MB
On 4 April 2013 18:32, Arnd Bergmann wrote:
> Moving the files is good, but I don't see a reason to make the cbe_cpufreq.h
> header globally visible in include/linux/. Isn't it just used by as the
> interface between ppc_cbe_cpufreq_pmi.c and ppc_cbe_cpufreq.c?
When i moved it initially i though
2013/4/4 Arnd Bergmann :
> Patch 6d0e025 "posix_cpu_timer: consolidate expiry time type" in linux-next
> introduces a new compiler warning:
>
> kernel/posix-cpu-timers.c: In function 'posix_cpu_timer_schedule':
> kernel/posix-cpu-timers.c:1127:19: warning: 'now' may be used uninitialized
> in this
2013/4/4 Stanislaw Gruszka :
> On Thu, Apr 04, 2013 at 02:31:42PM +0200, Frederic Weisbecker wrote:
>> I don't know. I'm not convinced userland is the right place to perform
>> this kind of check. The kernel perhaps doesn't give guarantee about
>> utime/stime precision but now users may have got us
Commit 7517de348663b08a808aff44b5300e817157a568 ("MIPS: Alchemy: Redo
PCI as platform driver") added a reference to CONFIG_DEBUG_PCI. Change
it to CONFIG_PCI_DEBUG, as that is a valid Kconfig macro.
Also add a newline to a debugging printk that this fix enables.
Signed-off-by: Paul Bolle
---
Thi
On Wed, Apr 03, 2013 at 09:14:01AM +0900, Minchan Kim wrote:
> clear_huge_page(page, haddr, HPAGE_PMD_NR);
> + /*
> + * The memory barrier inside __SetPageUptodate makes sure that
> + * clear_huge_page writes become visible after the set_pmd_at()
s/after/before/
> + * wri
Patch 6d0e025 "posix_cpu_timer: consolidate expiry time type" in linux-next
introduces a new compiler warning:
kernel/posix-cpu-timers.c: In function 'posix_cpu_timer_schedule':
kernel/posix-cpu-timers.c:1127:19: warning: 'now' may be used uninitialized in
this function [-Wmaybe-uninitialized]
On Thu, Apr 4, 2013 at 12:02 PM, Lars Poeschel wrote:
> From: Lars Poeschel
>
> This converts the mcp23s08 driver to be able to be used with device
> tree.
> There is a "spi-present-mask" device tree property, that allows to
> use multiple of this spi chips on the same chipselect.
>
> Signed-off
On Wed, Apr 03, 2013 at 05:56:00PM -0700, Yinghai Lu wrote:
> On Wed, Apr 3, 2013 at 2:00 PM, Vivek Goyal wrote:
> > On Wed, Apr 03, 2013 at 01:38:56PM -0700, Yinghai Lu wrote:
> >> On Wed, Apr 3, 2013 at 10:47 AM, Vivek Goyal wrote:
> >> > So what I am saying that all our code is written assumin
On Thu, Apr 04, 2013 at 02:01:48PM +0200, Peter Zijlstra wrote:
>
> I'm sorry, this email ended up quite a bit longer than I had hoped for;
> please bear with me.
>
> On Tue, 2013-04-02 at 18:59 +0200, Peter Zijlstra wrote:
> > struct ww_mutex; /* wound/wait */
> >
> > int mutex_wound_lock(s
On Thu, 4 Apr 2013, Theodore Ts'o wrote:
> Date: Thu, 4 Apr 2013 09:20:48 -0400
> From: Theodore Ts'o
> To: Lukáš Czerner
> Cc: Stephen Rothwell , linux-n...@vger.kernel.org,
> linux-kernel@vger.kernel.org
> Subject: Re: linux-next: build failure after merge of the ext4 tree
>
> On Thu, Apr
On Thu, Apr 04, 2013 at 03:18:32PM +0200, Lukáš Czerner wrote:
> I am afraid I do not understand why this is happening. The commit
> simply replaces ext4_get_group_no_and_offset() with
> ext4_get_group_number() which has the similar definition in the same
> header file. Maybe someone knows what thi
Reserving a large number of 1GB hugetlbfs pages at boot takes a very
long time due to the pages being memset to 0 during the reservation.
This is unneeded as the pages will be zeroed by clear_huge_page() when
being allocated by the user.
Large system sites would at times like to allocate a very la
On Thu, 4 Apr 2013, Stephen Rothwell wrote:
> Date: Thu, 4 Apr 2013 10:43:19 +1100
> From: Stephen Rothwell
> To: Theodore Ts'o
> Cc: linux-n...@vger.kernel.org, linux-kernel@vger.kernel.org,
> Lukas Czerner
> Subject: linux-next: build failure after merge of the ext4 tree
>
> Hi Ted,
>
>
On Thu, Apr 04, 2013 at 03:06:42PM +0200, Alexander Graf wrote:
>
> On 04.04.2013, at 14:56, Gleb Natapov wrote:
>
> > On Thu, Apr 04, 2013 at 02:49:39PM +0200, Alexander Graf wrote:
> >>
> >> On 04.04.2013, at 14:45, Gleb Natapov wrote:
> >>
> >>> On Thu, Apr 04, 2013 at 02:39:51PM +0200, Alex
Hi Sakari,
On Thursday 04 April 2013 01:22:28 Sakari Ailus wrote:
> On Tue, Mar 26, 2013 at 12:07:01AM +0100, Laurent Pinchart wrote:
> > On Sunday 24 March 2013 23:46:01 Sakari Ailus wrote:
> > > Pali Rohár wrote:
> > > > On Thursday 07 March 2013 23:18:27 Sakari Ailus wrote:
> > > >> On Wed, Mar
On Thu, Apr 04, 2013 at 02:31:42PM +0200, Frederic Weisbecker wrote:
> 2013/4/4 Stanislaw Gruszka :
> > This patch series removes cputime scaling from kernel. It can be easily
> > done in user space using floating point if we provide sum_exec_runtime,
> > what patches 2/4 and 3/4 do. I have procps
On 04.04.2013, at 14:56, Gleb Natapov wrote:
> On Thu, Apr 04, 2013 at 02:49:39PM +0200, Alexander Graf wrote:
>>
>> On 04.04.2013, at 14:45, Gleb Natapov wrote:
>>
>>> On Thu, Apr 04, 2013 at 02:39:51PM +0200, Alexander Graf wrote:
On 04.04.2013, at 14:38, Gleb Natapov wrote:
On Thursday 04 April 2013, Viresh Kumar wrote:
> This patch moves cpufreq driver of powerpc platforms/cell to drivers/cpufreq.
>
> Cc: Arnd Bergmann
> Cc: Benjamin Herrenschmidt
> Cc: linuxppc-...@lists.ozlabs.org
> Signed-off-by: Viresh Kumar
> ---
> Compile Tested only.
>
> arch/powerpc/pla
On Thu, 4 Apr 2013 14:30:12 +0400
Pavel Shilovsky wrote:
> 2013/3/12 Jeff Layton :
> > On Mon, 11 Mar 2013 14:54:34 -0400
> > Jeff Layton wrote:
> >
> >> On Thu, 28 Feb 2013 19:25:32 +0400
> >> Pavel Shilovsky wrote:
> >>
> >> > by passing these flags to NFSv4 open request.
> >> >
> >> > Signed
Using this parameter one can disable the storage_size/2 check if
he is really sure that the UEFI does sane gc.
Signed-off-by: Richard Weinberger
---
drivers/firmware/efivars.c | 7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/drivers/firmware/efivars.c b/drivers/firmware/
On Thu, Apr 04, 2013 at 02:59:43PM +0200, Paul Bolle wrote:
> On Thu, 2013-04-04 at 05:07 -0700, Guenter Roeck wrote:
> > On Thu, Apr 04, 2013 at 01:40:03PM +0200, Jean Delvare wrote:
> > > This breakage is telling us something about the weird approach taken in
> > > this file, methinks.
> > >
>
Some (broken?) EFI implementations return always a MaximumVariableSize of 0,
check against max_size only if it is non-zero.
Signed-off-by: Richard Weinberger
---
drivers/firmware/efivars.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/firmware/efivars.c b/drivers/
> -Original Message-
> From: Stephen Warren [mailto:swar...@wwwdotorg.org]
> Sent: Thursday, April 04, 2013 12:47 AM
> To: Venu Byravarasu
> Cc: gre...@linuxfoundation.org; ba...@ti.com;
> st...@rowland.harvard.edu; linux-te...@vger.kernel.org; linux-
> u...@vger.kernel.org; linux-kernel@vg
Normally we keep drivers in alphabetical inside Kconfig and Makefile and over
time this was broken for ARM cpufreq drivers. Fix it.
Cc: linux-arm-ker...@lists.infradead.org
Signed-off-by: Viresh Kumar
Acked-by: Stephen Warren
Tested-by: Stephen Warren
Acked-by: Arnd Bergmann
---
drivers/cpufr
On Thu, 2013-04-04 at 05:07 -0700, Guenter Roeck wrote:
> On Thu, Apr 04, 2013 at 01:40:03PM +0200, Jean Delvare wrote:
> > This breakage is telling us something about the weird approach taken in
> > this file, methinks.
> >
> Yes, they have persistent problems with renamed or moved drivers. I so
> -Original Message-
> From: Alex Williamson [mailto:alex.william...@redhat.com]
> Sent: Wednesday, April 03, 2013 11:32 PM
> To: Joerg Roedel
> Cc: Sethi Varun-B16395; Yoder Stuart-B08248; Wood Scott-B07421;
> io...@lists.linux-foundation.org; linuxppc-...@lists.ozlabs.org; linux-
> ker.
This patch moves cpufreq drivers of CRIS architecture to drivers/cpufreq.
Cc: Jesper Nilsson
Cc: Mikael Starvik
Cc: linux-cris-ker...@axis.com
Signed-off-by: Viresh Kumar
Acked-by: Jesper Nilsson
---
arch/cris/arch-v32/mach-a3/Makefile | 1 -
arch/cris/arch
This patch moves cpufreq driver of BLACKFIN architecture to drivers/cpufreq.
Cc: Mike Frysinger
Cc: uclinux-dist-de...@blackfin.uclinux.org
Signed-off-by: Viresh Kumar
Acked-by: Steven Miao
---
arch/blackfin/mach-common/Makefile | 1 -
drivers/cpufreq/Make
On Thu, Apr 04, 2013 at 02:49:39PM +0200, Alexander Graf wrote:
>
> On 04.04.2013, at 14:45, Gleb Natapov wrote:
>
> > On Thu, Apr 04, 2013 at 02:39:51PM +0200, Alexander Graf wrote:
> >>
> >> On 04.04.2013, at 14:38, Gleb Natapov wrote:
> >>
> >>> On Thu, Apr 04, 2013 at 02:32:08PM +0200, Alex
This patch moves cpufreq driver of powerpc platform to drivers/cpufreq.
Cc: Benjamin Herrenschmidt
Cc: Paul Mackerras
Cc: Olof Johansson
Cc: linuxppc-...@lists.ozlabs.org
Signed-off-by: Viresh Kumar
---
Compile Tested only.
arch/powerpc/platforms/Kconfig | 31
This patch moves cpufreq driver of powerpc platforms/cell to drivers/cpufreq.
Cc: Arnd Bergmann
Cc: Benjamin Herrenschmidt
Cc: linuxppc-...@lists.ozlabs.org
Signed-off-by: Viresh Kumar
---
Compile Tested only.
arch/powerpc/platforms/cell/Kconfig| 26 +-
arc
401 - 500 of 709 matches
Mail list logo