On Fri, May 31, 2013 at 10:47:20AM +0200, Robert Richter wrote:
> Patches base on Boris' patches which I have rebased to latest
> tip/perf/core. All patches can be found here:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/rric/oprofile.git persistent
Right, we should merge the fixes/changes
From: Robert Richter
This patch set contains userland changes necessary for out-of-the-box
support of persistent events. These patches are follow on patches of
the kernel patches I sent out today:
[PATCH 00/16] perf, persistent: Kernel updates for perf tool integration
Persistent events are
From: Robert Richter
These define's may cause conflicts with other definitions:
#define INITIAL 0
#define mem 1
#define config 2
#define event 3
Prefix them with cond_* to avoid this.
Signed-off-by: Robert Richter
---
tools/perf/util/parse-events.l | 24
1 file
From: Robert Richter
In a later patch we want to introduce a syntax that allows updating
attribute fields by an index pointing to a certain u64 entry of struct
perf_event_attr. We need this to expose any event via sysfs that is
available in the system where especially flag fields need to be set.
From: Robert Richter
The event parser is limited to update only a subset of all fields in
struct perf_event_attr (config*, period, branch_type). We are not able
to set other attr fields, esp. flags.
Introducing a new syntax to set any field of the event attribute by
using an index to the u64
From: Robert Richter
Persistent event buffers may only be mmapped readonly. Thus, retry
mapping it readonly if mmap returns EACCES after trying to mmap
writable.
Signed-off-by: Robert Richter
---
tools/perf/builtin-record.c | 7 ++-
tools/perf/builtin-top.c| 8 ++--
* KOSAKI Motohiro wrote:
> >> I'm unhappy you guys uses offensive word so much. Please cool down all
> >> you guys. :-/ In fact, _BOTH_ the behavior before and after Cristoph's
> >> patch doesn't have cleaner semantics.
> >
> > Erm, this feature _regressed_ after the patch. All other concerns
This patch adds a basic clock driver for the TI-Nspire calculator series.
Changes from v1:
* Removed filename in header comment
* Removed unnecessary #undef EXTRACT statement
Signed-off-by: Daniel Tang
---
.../devicetree/bindings/clock/nspire-clock.txt | 24
drivers/clk/Makefile
To support some (legacy) firmwares and platforms let's make life easier for
their customers.
This patch extracts SFI GPIO API from arch/x86/platform/mrst/mrst.c.
Signed-off-by: Andy Shevchenko
Acked-by: Len Brown
Cc: Grant Likely
Cc: Linus Walleij
---
Since v1:
- address Linus' comments:
Hi Linus,
On Thu, May 23, 2013 at 5:58 PM, Prabhakar Lad
wrote:
> Hi Rob/Grant,
>
> On Tue, May 7, 2013 at 11:34 AM, Prabhakar Lad
> wrote:
>> From: Lad, Prabhakar
>>
>> the function of_property_read_u8/16/32_array() has a parameter
>> out_values, but the description mentioned it as out_value.
On 31.05.13 11:15:40, Borislav Petkov wrote:
> On Fri, May 31, 2013 at 10:47:20AM +0200, Robert Richter wrote:
> > Patches base on Boris' patches which I have rebased to latest
> > tip/perf/core. All patches can be found here:
> >
> >
From: Sebastian Hesselbarth
Date: Fri, 31 May 2013 08:28:58 +0200
> thanks for pulling these in. I finally found how to check if a patch
> already went into -stable. As Jason already said, the mdio patch that
> #1 fixes did not yet went into -stable. Can you unqueue it? Sorry for
> the
On Fri, May 31, 2013 at 11:30 AM, Prabhakar Lad
wrote:
> Hi Linus,
(...)
> Can you pick this patch ?
No. I'm not a maintainer of drivers/of.
Only Grant and Rob can take changes to drivers/of.
(Check MAINTAINERS.)
Yours,
Linus Walleij
--
To unsubscribe from this list: send the line
Hi Guenter,
On Fri, May 31, 2013 at 3:32 AM, Guenter Roeck wrote:
> On Thu, May 30, 2013 at 11:59:28PM +0200, Wim Van Sebroeck wrote:
>> Hi Guenter,
>>
>> > On Tue, May 28, 2013 at 10:10:53AM +0200, Johannes Thumshirn wrote:
>> > > On Mon, May 27, 2013 at 08:25:54PM +0200, Wim Van Sebroeck
On Thu, May 30, 2013 at 11:21:21AM +0200, Jan Kara wrote:
> On Wed 29-05-13 21:49:38, Haicheng Li wrote:
> > Functions not used globally should be static.
> I agree for wb_do_writeback().
Ok, thanks.
> You definitely shouldn't make
> writeback_inodes_sb_nr() static, that it part of generic
From: "John W. Linville"
Date: Wed, 29 May 2013 11:28:53 -0400
> Please pull this batch of fixes intended for the 3.10 stream...
Pulled, thanks John.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo
2013/5/31 Wenyou Yang :
> Hello,
>
> The patches is to add watchdog device tree node for at91 SoC and board dts
> files.
>
> Since the watchdog is disabled in the at91bootstrap with default
> configuration,
> if you want to use the watchdog in the kernel, you must make sure the watchdog
>
arch/blackfin/mach-bf533/boards/stamp.c:545:2: error: operator '||' has no
right operand
arch/blackfin/mach-bf533/boards/stamp.c:662:3: error: 'bfin_snd_resources'
undeclared here (not in a function)
arch/blackfin/mach-bf533/boards/stamp.c:662:3: error: negative width in
bit-field ''
On 31/05/13 01:30, John Stultz wrote:
> On 05/30/2013 07:25 AM, David Vrabel wrote:
>> From: David Vrabel
>>
>> Currently the Xen wallclock is only updated every 11 minutes if NTP is
>> synchronized to its clock source. If a guest is started before NTP is
>> synchronized it may see an incorrect
From: Srinivas Kandagatla
This patch moves sirfsoc_of_rstc_init from early_initcall to .init_early
in machine descriptor, doing this way a multi_v7 kernel will not crash
on non-prima2 SOCs.
Without this patch the multi_v7 kernel panics if we boot it on any non
prima2 parts with below log:
From: Srinivas Kandagatla
This patch moves all postcore_initcalls to very first calls in
init_machine. This should achieve the same sequencing as done via
postcore_initcalls.
Without this patch a multi_v7 kernel panics if we boot it on any
non prima2 parts with below log:
Kernel panic - not
From: Srinivas Kandagatla
If we try to boot a multi_v7_defconfig kernel on any ARM parts other than
prima2, you will hit kernel panics. This is because some of the code is still
using explicit early_initcall and postcore_initcalls.
Moving these calls to machine descriptor level is the right
On 31/05/13 00:55, John Stultz wrote:
> On 05/30/2013 07:25 AM, David Vrabel wrote:
>>
>> These series fixes the above limitations and depends on "x86: increase
>> precision of x86_platform.get/set_wallclock()" which was previously
>> posted.
>
> This is the only area that will need some
* Frederic Weisbecker wrote:
> On Wed, May 29, 2013 at 06:39:39PM +0200, Frederic Weisbecker wrote:
> > Ingo,
> >
> > Please pull the timers/urgent-for-tip branch that can be found at:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks.git
> >
Hi all:
This series implements a v2 of fully tuntap compatiable API which could be used
by userspace to manage multiple macvtap queues. The main parts is to add
TUNSETQUEUE ioctl support for macvtap.
Patch 1 - 4 was some tuntap compatibility and misc cleanups.
Patch 5 removes the linear search
Macvtap should be at least compatible with tap, so change the max number to 16.
Signed-off-by: Jason Wang
---
include/linux/if_macvlan.h |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/include/linux/if_macvlan.h b/include/linux/if_macvlan.h
index e47ad46..62d8bda
Acked-by: Michael S. Tsirkin
Signed-off-by: Jason Wang
---
include/linux/if_macvlan.h |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/include/linux/if_macvlan.h b/include/linux/if_macvlan.h
index 84dde1d..e47ad46 100644
--- a/include/linux/if_macvlan.h
+++
This patch adds TUNSETQUEUE ioctl to let userspace can temporarily disable or
enable a queue of macvtap. This is used to be compatible at API layer of tuntap
to simplify the userspace to manage the queues.
This is done by split the taps array into three different areas:
- [0, numvtaps) : enabled
Factor out the device holding logic to a macvtap_get_vlan(), this will be also
used by multiqueue API.
Signed-off-by: Jason Wang
---
drivers/net/macvtap.c | 27 ---
1 files changed, 20 insertions(+), 7 deletions(-)
diff --git a/drivers/net/macvtap.c
There's no need to add self to waitqueue if doing a nonblock read. This could
help to avoid the spinlock contention.
Signed-off-by: Jason Wang
---
drivers/net/macvtap.c |7 +--
1 files changed, 5 insertions(+), 2 deletions(-)
diff --git a/drivers/net/macvtap.c b/drivers/net/macvtap.c
* Russ Anderson wrote:
> On Thu, May 30, 2013 at 10:32:09PM +, Matthew Garrett wrote:
> > On Thu, 2013-05-30 at 17:28 -0500, Russ Anderson wrote:
> > > On Thu, May 30, 2013 at 10:21:53PM +, Matthew Garrett wrote:
> > > > On Thu, 2013-05-30 at 17:17 -0500, Russ Anderson wrote:
> > > >
>
Linear search were used in both get_slot() and macvtap_get_queue(), this is
because:
- macvtap didn't reshuffle the array of taps when create or destroy a queue, so
when adding a new queue, macvtap must do linear search to find a location for
the new queue. This will also complicate the
Signed-off-by: Jason Wang
---
drivers/net/macvtap.c |7 ++-
1 files changed, 2 insertions(+), 5 deletions(-)
diff --git a/drivers/net/macvtap.c b/drivers/net/macvtap.c
index 03b781c..fac9dbf 100644
--- a/drivers/net/macvtap.c
+++ b/drivers/net/macvtap.c
@@ -31,10 +31,6 @@
*
Though the queue were in fact created by open(), we still need to add this check
to be compatible with tuntap which can let mgmt software use a single API to
manage queues. This patch only validates the device name and moves the TUNSETIFF
to a helper.
Signed-off-by: Jason Wang
---
On Fri, May 31, 2013 at 03:05:50PM +0530, anish singh wrote:
> Hi Guenter,
>
> On Fri, May 31, 2013 at 3:32 AM, Guenter Roeck wrote:
> > On Thu, May 30, 2013 at 11:59:28PM +0200, Wim Van Sebroeck wrote:
> >> Hi Guenter,
> >>
> >> > On Tue, May 28, 2013 at 10:10:53AM +0200, Johannes Thumshirn
From: Srinivas Kandagatla
This patch adds "Clocksource drivers" menu to clocksource drivers.
The reason to add this is because, some of the clocksource Kconfig
options like *SHED_CLK ones are selectable and they appear at random
places in the device drivers menu.
These options can be more than
Make pinctrl-single able to handle suspend/resume events and change
hogged pins states accordingly.
Signed-off-by: Hebbar Gururaja
Cc: Linus Walleij
---
:100644 100644 b9fa046... bfd4f6a... M drivers/pinctrl/pinctrl-single.c
drivers/pinctrl/pinctrl-single.c | 27 +++
* Jiri Kosina wrote:
> On Thu, 30 May 2013, Russ Anderson wrote:
>
> > > > > > Yes, but this call is clearly happening way before
> > > > > > ExitBootServices() --
> > > > > > see the surrounding code, see for example this in efi_main():
> > > > > >
> > > > > > [ ... snip ... ]
> > > > > >
Amend the spi omap controller to optionally take a pin control
handle and set the state of the pins to:
- "default" on boot, resume and before performing an spi transfer
- "idle" after initial default, after resume default, and after each
spi xfer
- "sleep" on suspend()
By optionally putting the
Amend TI ecap controller to optionally take a pin control handle and
set the state of the pins to:
- "default" on boot, resume
- "sleep" on suspend()
By optionally putting the pins into sleep state in the suspend callback
we can accomplish two things.
- One is to minimize current leakage from
Amend the musb controller to optionally take a pin control handle and
set the state of the pins to:
- "default" on boot, resume
- "sleep" on suspend()
By optionally putting the pins into sleep state in the suspend callback
we can accomplish two things.
- One is to minimize current leakage from
Amend matrix-keypad driver to optionally take a pin control handle and
set the state of the pins to:
- "default" on boot, resume
- "sleep" on suspend()
By optionally putting the pins into sleep state in the suspend callback
we can accomplish two things.
- One is to minimize current leakage from
By optionally putting the pins into sleep state in the suspend [or in
runtime_suspend] callback we can accomplish two things.
- One is to minimize current leakage from pins and thus save power,
- second, we can prevent the IP from driving pins output in an
uncontrolled manner, which may happen if
Amend gpio-keys driver to optionally take a pin control handle and set
the state of the pins to:
- "default" on boot, resume
- "sleep" on suspend()
By Optionally putting the pins into sleep state in the suspend callback
we can accomplish two things.
- One is to minimize current leakage from pins
Amend the I2C omap pin controller to optionally take a pin control
handle and set the state of the pins to:
- "default" on boot, resume and before performing an i2c transfer
- "idle" after initial default, after resume default, and after each
i2c xfer
- "sleep" on suspend()
By optionally putting
Amend the da8xx-fb controller to optionally take a pin control handle
and set the state of the pins to:
- "default" on boot, resume
- "sleep" on suspend()
By optionally putting the pins into sleep state in the suspend callback
we can accomplish two things.
- One is to minimize current leakage
Amend the hsmmc controller to optionally take a pin control handle and
set the state of the pins to:
- "default" on boot, resume and before performing a mmc transfer
- "idle" after initial default, after resume default, and after each
mmc/sd card access
- "sleep" on suspend()
By optionally
Amend leds-gpio driver to optionally take a pin control handle and set
the state of the pins to:
- "default" on boot, resume
- "sleep" on suspend()
By optionally putting the pins into sleep state in the suspend callback
we can accomplish two things.
- One is to minimize current leakage from pins
Various temporary files used when building DTB files were not suffixed with
.tmp and therefore were not cleaned up by "make clean".
Signed-off-by: Ian Campbell
Cc: Michal Marek
Cc: Stephen Warren
Cc: Rob Herring
Cc: Grant Likely
Cc: linux-kbu...@vger.kernel.org
Cc:
Amend the ti ehrpwm controller to optionally take a pin control handle
and set the state of the pins to:
- "default" on boot, resume
- "sleep" on suspend()
By optionally putting the pins into sleep state in the suspend callback
we can accomplish two things.
- One is to minimize current leakage
This file is a common include for B4860 and B4420 but is not a valid DTS itself:
DTC arch/powerpc/boot/b4qds.dtb
Error: arch/powerpc/boot/dts/b4qds.dts:35.1-2 syntax error
FATAL ERROR: Unable to parse input tree
make[1]: *** [arch/powerpc/boot/b4qds.dtb] Error
On Thu, May 30, 2013 at 08:02:03AM +0100, Alex Shi wrote:
> Except using runnable load average in background, move_tasks is also
> the key functions in load balance. We need consider the runnable load
> average in it in order to the apple to apple load comparison.
>
> Signed-off-by: Alex Shi
>
Hello Daniel,
Thanks for your comment.
On 2013년 05월 31일 18:14, Daniel Vetter wrote:
> On Fri, May 31, 2013 at 10:54 AM, Seung-Woo Kim
> wrote:
>> importer private data in dma-buf attachment can be used by importer to
>> reimport same dma-buf.
>>
>> Seung-Woo Kim (2):
>> dma-buf: add importer
On Fri, 31 May 2013, Michal Hocko wrote:
> I have always discouraged people from running oom handler in the same
> memcg (or even in the same hierarchy).
>
We allow users to control their own memcgs by chowning them, so they must
be run in the same hierarchy if they want to run their own
This affects arch/powerpc/boot/dts/virtex440-ml510.dts but I think it is
actually a more general issue:
$ make ARCH=powerpc CROSS_COMPILE=powerpc-linux- virtex440-ml510.dtb
CC scripts/mod/devicetable-offsets.s
GEN scripts/mod/devicetable-offsets.h
On 05/30/2013 05:21 AM, Laurent Pinchart wrote:
> Hi Sylwester,
>
> On Saturday 25 May 2013 16:11:52 Sylwester Nawrocki wrote:
>> On 05/25/2013 11:17 AM, Prabhakar Lad wrote:
[...]
> And for synchronisation method on the analog part we could perhaps
> define 'component-sync' or similar
On Wed, May 29, 2013 at 5:42 PM, Takashi Iwai wrote:
> At Fri, 24 May 2013 23:32:14 +0200, Alex Riesen wrote:
>> I'm sorry to say that I will not be able to test it in the next
>> 8 or so days: I'll be traveling and without this particular laptop
>> with me. I hope someone with similar model
On Fri, May 31, 2013 at 10:58:48AM +0200, Johannes Thumshirn wrote:
> This patch adds the driver for the watchdog devices found on MEN Mikro
> Elektronik A21 VMEbus CPU Carrier Boards. It has DT-support and uses the
> watchdog framework.
>
> Revision 2:
> * Removed unneeded open flag in struct
On Thu, May 30, 2013 at 05:18:28PM +0100, Stefano Stabellini wrote:
> Most of Xen support for ARM is common between ARMv7 and ARMv8.
> Create links to the code under arch/arm (bleah).
>
> Other, probably better alternatives:
>
> - move the code to a different location, maybe the header files to
On Thu, May 30, 2013 at 05:18:29PM +0100, Stefano Stabellini wrote:
> Signed-off-by: Stefano Stabellini
> ---
> arch/arm/include/asm/xen/events.h |4
> arch/arm/include/asm/xen/page.h |2 ++
> 2 files changed, 6 insertions(+), 0 deletions(-)
>
> diff --git
On 22 May 2013 14:04, Viresh Kumar wrote:
> Sorry for being late in replying to your queries.
>
> On 13 May 2013 16:05, Thomas Gleixner wrote:
>> Which mechanism is migrating the timer away?
>
> It will be the same: get_nohz_timer_target() which will decide target
> cpu for migration.
>
>> I
On 20 May 2013 10:10, Viresh Kumar wrote:
> On 13 May 2013 11:34, Viresh Kumar wrote:
>> On 22 April 2013 12:19, Viresh Kumar wrote:
>>> On 9 April 2013 14:05, Viresh Kumar wrote:
On 5 April 2013 12:16, Viresh Kumar wrote:
> On 4 April 2013 18:24, Viresh Kumar wrote:
>> This
On Fri, May 31, 2013 at 03:36:54AM -0700, Guenter Roeck wrote:
> On Fri, May 31, 2013 at 10:58:48AM +0200, Johannes Thumshirn wrote:
> > This patch adds the driver for the watchdog devices found on MEN Mikro
> > Elektronik A21 VMEbus CPU Carrier Boards. It has DT-support and uses the
> > watchdog
* Morten Rasmussen wrote:
> Hi,
>
> A number of patch sets related to power-efficient scheduling have been
> posted over the last couple of months. Most of them do not have much
> data to back them up, so I decided to do some testing.
Thanks, numbers are always welcome!
> Measurement
Hi Andrew,
Max Filippov reported a generic MM issue with PTE/TLB coherency
@ http://www.spinics.net/lists/linux-arch/msg21736.html
While the fix for issue is still being discussed, sending over a bunch
mm fixlets which we found in due course.
Infact, 1/2 looks like stable material as orig code
This removes some unused generated code for tlb_fast_mode() == true
Signed-off-by: Vineet Gupta
Acked-by: Peter Zijlstra
Cc: Andrew Morton
Cc: Mel Gorman
Cc: Hugh Dickins
Cc: Rik van Riel
Cc: David Rientjes
Cc: Peter Zijlstra
Cc: linux...@kvack.org
Cc: linux-a...@vger.kernel.org
---
zap_pte_range loops from @addr to @end. In the middle, if it runs out of
batching slots, TLB entries needs to be flushed for @start to @interim,
NOT @interim to @end.
Since ARC port doesn't use page free batching I can't test it myself but
this seems like the right thing to do.
Observed this when
On Thu, May 30, 2013 at 05:18:32PM +0100, Stefano Stabellini wrote:
> --- a/arch/arm/include/asm/xen/page.h
> +++ b/arch/arm/include/asm/xen/page.h
> @@ -90,6 +90,10 @@ static inline bool set_phys_to_machine(unsigned long pfn,
> unsigned long mfn)
> return __set_phys_to_machine(pfn, mfn);
>
On Fri 31-05-13 03:22:59, David Rientjes wrote:
> On Fri, 31 May 2013, Michal Hocko wrote:
[...]
> > > If the oom notifier is in the oom cgroup, it may not be able to
> > > successfully read the memcg "tasks" file to even determine the set of
> > > eligible processes.
> >
> > It would
Hi Will,
I have merge your code ,
But there is a different ,
+
+ ct_user_exit
+
+#ifdef CONFIG_ALIGNMENT_TRAP
+ ldr ip, __cr_alignment
+ ldr ip, [ip]
+ mcr p15, 0, ip, c1, c0 @ update control register
+#endif
+ enable_irq
+
On Thu, May 30, 2013 at 05:18:33PM +0100, Stefano Stabellini wrote:
> Introduce CONFIG_XEN and the implementation of hypercall.S (that is
> the only ARMv8 specific code in Xen support for ARM).
>
> Signed-off-by: Stefano Stabellini
> ---
> arch/arm64/Kconfig | 11 +
>
* Arnaldo Carvalho de Melo wrote:
> From: Arnaldo Carvalho de Melo
>
> Hi Ingo,
>
> Please consider pulling,
>
> - Arnaldo
>
> The following changes since commit c0ffaf3655fab1909a920c8f30ba1722932d01bb:
>
> watchdog: Remove softlockup_thresh from Documentation (2013-05-28
On Fri, 31 May 2013, Ingo Molnar wrote:
> So this change needs to be reverted or fixed.
I don't think anyone is arguing against that.
My remark was purely to describe the current status quo and help to
understand what exactly is happening, i.e.:
- QueryVariableInfo() should be a valid thing
This patch adds the driver for the watchdog devices found on MEN Mikro
Elektronik A21 VMEbus CPU Carrier Boards. It has DT-support and uses the
watchdog framework.
Revision 2:
* Removed unneeded open flag in struct a21_wdt_drv
* Corrected 3bit reason code from gpio
* Additional sysfs files are
On Fri, May 31, 2013 at 12:02:49PM +0100, Wang, Yalin wrote:
> Hi Will,
>
> I have merge your code ,
> But there is a different ,
>
> +
> + ct_user_exit
I thought you didn't have ct_user_exit? In which case, just delete this
line.
> +#ifdef CONFIG_ALIGNMENT_TRAP
> + ldr ip,
Commit-ID: 6956664a5c4c32d5aa48fe96d5e2421a3e3f72d5
Gitweb: http://git.kernel.org/tip/6956664a5c4c32d5aa48fe96d5e2421a3e3f72d5
Author: Sukadev Bhattiprolu
AuthorDate: Fri, 29 Mar 2013 12:14:43 -0700
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 28 May 2013 16:23:51 +0300
perf
Commit-ID: 26353a61b977e57b58dd3555bc0422fea46c5ad6
Gitweb: http://git.kernel.org/tip/26353a61b977e57b58dd3555bc0422fea46c5ad6
Author: Namhyung Kim
AuthorDate: Mon, 1 Apr 2013 20:35:17 +0900
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 28 May 2013 16:23:52 +0300
perf hists:
Commit-ID: ceb2acbc2c1387c8785b3c98b482f5a2b89447c3
Gitweb: http://git.kernel.org/tip/ceb2acbc2c1387c8785b3c98b482f5a2b89447c3
Author: Namhyung Kim
AuthorDate: Mon, 1 Apr 2013 20:35:18 +0900
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 28 May 2013 16:23:52 +0300
perf hists:
Commit-ID: ded19d57a621e92a27a05972949ad3230f84d0b0
Gitweb: http://git.kernel.org/tip/ded19d57a621e92a27a05972949ad3230f84d0b0
Author: Namhyung Kim
AuthorDate: Mon, 1 Apr 2013 20:35:19 +0900
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 28 May 2013 16:23:53 +0300
perf report:
Commit-ID: 55369fc179b0572d0b4a06a9be1d2779b3ac22e0
Gitweb: http://git.kernel.org/tip/55369fc179b0572d0b4a06a9be1d2779b3ac22e0
Author: Namhyung Kim
AuthorDate: Mon, 1 Apr 2013 20:35:20 +0900
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 28 May 2013 16:23:53 +0300
perf sort:
Commit-ID: 2f532d09fa3a7eaf7cf1c23de9767eab8c8c0e7e
Gitweb: http://git.kernel.org/tip/2f532d09fa3a7eaf7cf1c23de9767eab8c8c0e7e
Author: Namhyung Kim
AuthorDate: Wed, 3 Apr 2013 21:26:10 +0900
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 28 May 2013 16:23:53 +0300
perf sort:
Commit-ID: afab87b91f3f331d55664172dad8e476e6ffca9d
Gitweb: http://git.kernel.org/tip/afab87b91f3f331d55664172dad8e476e6ffca9d
Author: Namhyung Kim
AuthorDate: Wed, 3 Apr 2013 21:26:11 +0900
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 28 May 2013 16:23:54 +0300
perf sort:
On Fri 31-05-13 03:22:59, David Rientjes wrote:
> On Fri, 31 May 2013, Michal Hocko wrote:
>
> > I have always discouraged people from running oom handler in the same
> > memcg (or even in the same hierarchy).
> >
>
> We allow users to control their own memcgs by chowning them, so they must
>
Commit-ID: 08e71542fd0f4a0e30b4e3794329d63ae891e0c0
Gitweb: http://git.kernel.org/tip/08e71542fd0f4a0e30b4e3794329d63ae891e0c0
Author: Namhyung Kim
AuthorDate: Wed, 3 Apr 2013 21:26:19 +0900
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 28 May 2013 16:23:54 +0300
perf sort:
Commit-ID: bc8b8c0d6ae55c3d11c381cfd6339c7557bbab44
Gitweb: http://git.kernel.org/tip/bc8b8c0d6ae55c3d11c381cfd6339c7557bbab44
Author: Arnaldo Carvalho de Melo
AuthorDate: Thu, 4 Apr 2013 12:41:22 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 28 May 2013 16:23:55 +0300
Commit-ID: dfd3b2fd485e3969a30b28e70aabfefa90b81c9c
Gitweb: http://git.kernel.org/tip/dfd3b2fd485e3969a30b28e70aabfefa90b81c9c
Author: Namhyung Kim
AuthorDate: Fri, 5 Apr 2013 10:26:31 +0900
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 28 May 2013 16:23:55 +0300
perf sort:
On Friday 31 May 2013 10:58:35 Neil Zhang wrote:
> bring up pxa988 with device tree support.
>
> Change-Id: I6fc869b7d5ff8dc6e4eb0042a89429200f7a9fb1
Please don't post silly extra headers like that.
> Signed-off-by: Neil Zhang
A couple of comments on the DT structure:
> + gic:
Commit-ID: 930477bdc227adbbff1d42ec9eba50a805cc9b78
Gitweb: http://git.kernel.org/tip/930477bdc227adbbff1d42ec9eba50a805cc9b78
Author: Namhyung Kim
AuthorDate: Fri, 5 Apr 2013 10:26:36 +0900
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 28 May 2013 16:23:56 +0300
perf sort:
Commit-ID: 8f0f684b7b640caeca319f7f4e18474d099d8606
Gitweb: http://git.kernel.org/tip/8f0f684b7b640caeca319f7f4e18474d099d8606
Author: Namhyung Kim
AuthorDate: Fri, 5 Apr 2013 10:26:37 +0900
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 28 May 2013 16:23:56 +0300
perf top: Use
Commit-ID: 9c796ec8dbc8dbfe41ce35a1ccb1b59b47148daf
Gitweb: http://git.kernel.org/tip/9c796ec8dbc8dbfe41ce35a1ccb1b59b47148daf
Author: Arnaldo Carvalho de Melo
AuthorDate: Fri, 26 Apr 2013 14:28:46 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 28 May 2013 16:23:56 +0300
Hi,
Improve Kconfig so that the relevant PHY driver can be explicitely
selected by the controller driver instead of relying on the user
to do so.
Detailed description in patch 1.
v2:
- Merge patches 3-5 into the first patch to prevent circular dependency
between the Kconfig options during
Convert PHY Drivers from menuconfig to menu so that the PHY drivers
can be explicitely selected by the controller drivers.
USB_PHY is no longer a user visible option. It is upto to the PHY
drivers to select it if needed. This patch does so for the existing
PHY drivers that use the USB_PHY
Commit-ID: f9619d693a3aad365598ed5f718bd5883c7cb7f8
Gitweb: http://git.kernel.org/tip/f9619d693a3aad365598ed5f718bd5883c7cb7f8
Author: Jiri Olsa
AuthorDate: Wed, 24 Apr 2013 11:37:29 +0200
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 28 May 2013 16:23:57 +0300
perf tools: Fix
Commit-ID: b3539d214f6000217aae97b5ae32df5b03faf850
Gitweb: http://git.kernel.org/tip/b3539d214f6000217aae97b5ae32df5b03faf850
Author: Sukadev Bhattiprolu
AuthorDate: Fri, 26 Apr 2013 10:17:56 -0700
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 28 May 2013 16:23:57 +0300
perf
Hi Will,
I see,
I will make one more test .
Thanks for your clarification .
-Original Message-
From: Will Deacon [mailto:will.dea...@arm.com]
Sent: Friday, May 31, 2013 7:13 PM
To: Wang, Yalin
Cc: 'richard -rw- weinberger'; 'linux-a...@vger.kernel.org';
'linux-kernel@vger.kernel.org';
ehci-omap needs NOP_USB_XCEIV PHY driver to function
properly, so select it. As the USB PHY drivers no longer
depend on USB_PHY, it is safe to select the PHY drivers.
Signed-off-by: Roger Quadros
Tested-by: Adrien Vergé
---
drivers/usb/host/Kconfig |4 +---
1 files changed, 1
Commit-ID: 89365e6c9ad4c0e090e4c6a4b67a3ce319381d89
Gitweb: http://git.kernel.org/tip/89365e6c9ad4c0e090e4c6a4b67a3ce319381d89
Author: Andi Kleen
AuthorDate: Wed, 24 Apr 2013 17:03:02 -0700
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 28 May 2013 16:23:58 +0300
perf tools:
* Yinghai Lu wrote:
> Commit 8d57470d cause a kernel panic while setting mem=2G.
'Commit 8d57470d' is not the standard way of how we refer to upstream
commits in changelogs. See commit 5e427ec2d066 as an example for the
proper format.
Thanks,
Ingo
--
To unsubscribe from this list:
Commit-ID: 804f7ac78803ed095bb0402d540f859ecb1be9f1
Gitweb: http://git.kernel.org/tip/804f7ac78803ed095bb0402d540f859ecb1be9f1
Author: David Ahern
AuthorDate: Mon, 6 May 2013 12:24:23 -0600
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 28 May 2013 16:23:58 +0300
perf record:
Commit-ID: 933cbb1c6c617a6ae167538c2fa503efc9c4a832
Gitweb: http://git.kernel.org/tip/933cbb1c6c617a6ae167538c2fa503efc9c4a832
Author: Namhyung Kim
AuthorDate: Tue, 14 May 2013 11:08:59 +0900
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 28 May 2013 16:23:59 +0300
perf top: Fix
801 - 900 of 1386 matches
Mail list logo
