On 3/23/15 12:35 AM, Ingo Molnar wrote:
* Alexei Starovoitov wrote:
+void read_trace_pipe(void)
+{
+ int trace_fd;
+
+ trace_fd = open(DEBUGFS "trace_pipe", O_RDONLY, 0);
+ if (trace_fd < 0)
+ return;
+
+ while (1) {
+ static char buf[4096];
2015-03-23 15:30 GMT+09:00 Namhyung Kim :
> The perf kmem command records and analyze kernel memory allocation
> only for SLAB objects. This patch implement a simple page allocator
> analyzer using kmem:mm_page_alloc and kmem:mm_page_free events.
>
> It adds two new options of --slab and --page.
On Mon, 23 Mar 2015 18:10:01 +0100
Denys Vlasenko wrote:
> On 03/23/2015 03:18 PM, Steven Rostedt wrote:
> > On Sat, 21 Mar 2015 21:44:37 +0100
> > Denys Vlasenko wrote:
> >
> >> Instead of PER_CPU_VAR(kernel_stack), 64-bit code
> >> can use PER_CPU_VAR(cpu_tss + TSS_sp0).
> >
> > The change l
2015-03-23 15:30 GMT+09:00 Namhyung Kim :
> Add new sort keys for page: page, order, mtype, gfp - existing
> 'bytes', 'hit' and 'callsite' sort keys also work for page. Note that
> -s/--sort option should be preceded by either of --slab or --page
> option to determine where the sort keys applies.
On 03/23/2015 12:58 PM, Richard Cochran wrote:
On Mon, Mar 23, 2015 at 12:02:03PM -0400, Chris Metcalf wrote:
>This driver is 64-bit only. Would it make more sense to just change
>the accessors from gettime/settime to gettime/settime64 and nothing
>else, i.e. rely on the current behavior that t
On Mon, 23 Mar 2015, Nicolas Ferre wrote:
> Le 17/03/2015 20:02, Alan Stern a �crit :
> > On Tue, 17 Mar 2015, Boris Brezillon wrote:
> >
> >> Now that the system clock driver is forwarding set_rate request to the
> >> parent clock, we can safely call clk_set_rate on the system clk and get
> >> r
On 3/23/15 12:29 AM, Ingo Molnar wrote:
** **
** This means that this is a DEBUG kernel and it is **
** unsafe for production use. **
But I think printing that it's unsafe for production use is over the
top: it
Hello, Namhyung.
2015-03-23 15:30 GMT+09:00 Namhyung Kim :
> Hello,
>
> Currently perf kmem command only analyzes SLAB memory allocation. And
> I'd like to introduce page allocation analysis also. Users can use
> --slab and/or --page option to select it. If none of these options
> are used, it
Hi Andreas, Hakjoo,
Thanks for the patch.
2015-03-16 7:00 GMT+09:00 Andreas Färber :
> From: Hakjoo Kim
>
> Add Samsung EXYNOS5410 SoC specific data to enable pinctrl
> support for all platforms based on EXYNOS5410.
>
> Signed-off-by: Hakjoo Kim
> [AF: Rebased onto Exynos5260, irq_chip consolid
Hi Luis,
This seems OK to me, but I'm curious about a few things.
On Fri, Mar 20, 2015 at 6:17 PM, Luis R. Rodriguez
wrote:
> From: "Luis R. Rodriguez"
>
> This allows drivers to take advantage of write-combining
> when possible. Ideally we'd have pci_read_bases() just
> peg an IORESOURCE_WC fl
On Mon, Mar 23, 2015 at 10:15:03AM +0100, Ludovic Desroches wrote:
> On Sat, Mar 21, 2015 at 12:42:06PM -0700, Maxime Ripard wrote:
>
> [...]
>
> > +/*
> > + * Besoin d'une fonction pour pusher un descriptor vers un pchan
> > + *
> > + * Flow normal:
> > + * - Election d'un pchan (Framework)
>
From: Jiri Pirko
Date: Mon, 23 Mar 2015 14:18:39 +0100
> Sat, Mar 21, 2015 at 07:02:40PM CET, andreimar...@gmail.com wrote:
>>Fixed a space coding style issue found by checkpatch.pl in rocker.c
>>
>>Signed-off-by: Andrei Maresu
>>---
>> drivers/net/ethernet/rocker/rocker.c | 2 +-
>> 1 file chang
On Sat, Mar 21, 2015 at 11:43:56AM +0100, Hans de Goede wrote:
> Hi,
>
> On 20-03-15 21:56, Maxime Ripard wrote:
> >Hi,
> >
> >On Fri, Mar 20, 2015 at 03:04:28PM +0100, Daniel Lezcano wrote:
> >>On 03/19/2015 11:53 PM, Maxime Ripard wrote:
> >>>Hi Daniel,
> >>>
> >>>On Thu, Mar 05, 2015 at 11:20:5
At Mon, 23 Mar 2015 17:07:15 +0100,
Denys Vlasenko wrote:
>
> On 03/23/2015 02:22 PM, Takashi Iwai wrote:
> > At Mon, 23 Mar 2015 10:35:41 +0100,
> > Takashi Iwai wrote:
> >>
> >> At Mon, 23 Mar 2015 10:02:52 +0100,
> >> Takashi Iwai wrote:
> >>>
> >>> At Fri, 20 Mar 2015 19:16:53 +0100,
> >>> Den
On Mon, 2015-03-23 at 11:33 -0400, Changwoo Min wrote:
> hfsplus_file_fsync() siliently ignores the return value of
> sync_inode_metadata().
> If an error occurs at sync_inode_metadata() and subsequent updates of other
> file
> system metadata (b-trees) succeed, file system metadata will be inco
On Mon, Mar 23, 2015 at 06:10:01PM +0100, Denys Vlasenko wrote:
> We want to get rid of kernel_stack, since it is redundant:
> in 64-bits, PER_CPU_VAR(cpu_tss + TSS_sp0) can be used instead,
> in 32-bits, PER_CPU_VAR(cpu_current_top_of_stack) can be used instead.
We probably should have a macro un
On Mon, Mar 23, 2015 at 10:05 AM, Linus Torvalds
wrote:
> On Mon, Mar 23, 2015 at 9:55 AM, David Miller wrote:
>>
>> Some perf bug fixes from David Ahern, and the fix for that nasty
>> memmove() bug.
>
> That doesn't seem to be marked for stable? Or do you do the same thing
> as for networking, a
On 03/23/2015 03:18 PM, Steven Rostedt wrote:
> On Sat, 21 Mar 2015 21:44:37 +0100
> Denys Vlasenko wrote:
>
>> Instead of PER_CPU_VAR(kernel_stack), 64-bit code
>> can use PER_CPU_VAR(cpu_tss + TSS_sp0).
>
> The change log here is lacking an answer to "why". It only states what
> it does. What'
Hello everyone, this is my first attempt at bisecting a kernel to solve a
bug. Please bear with me.
I have successfully bisected and located a commit that is causing my
problem. Look at commit 166afb64511.
ktime_to_us returns s64, but the commit changes it so ktime_to_us just
returns what kt
On Mon, Mar 23, 2015 at 9:55 AM, David Miller wrote:
>
> Some perf bug fixes from David Ahern, and the fix for that nasty
> memmove() bug.
That doesn't seem to be marked for stable? Or do you do the same thing
as for networking, and just collect stable patches manually?
Pulled,
On Mon, Mar 23, 2015 at 12:34:04PM +, Jeff Epler wrote:
> On Fri, Mar 20, 2015 at 11:14:40AM +, Javi Merino wrote:
> > +/*
> > + * Same as above but for u64 dividends. divisor must be a 32-bit
> > + * number.
> > + */
> > +#define DIV_ROUND_CLOSEST_ULL(x, divisor)( \
> > +{
On Monday 23 March 2015 12:39:48 Hans de Goede wrote:
> Hi,
>
> On 22-03-15 14:46, Pali Rohár wrote:
> > This patch adds detection of trackstick for v7 protocol
> > devices. Code in this patch is used in official Dell
> > touchpad linux drivers for Dell models: Dell Latitude
> > E5250/5250, E5450/
On 03/23/2015 05:16 AM, Tero Kristo wrote:
> On 03/20/2015 11:54 PM, Eduardo Valentin wrote:
>> On Fri, Mar 20, 2015 at 02:47:39PM -0500, Nishanth Menon wrote:
>>> From: Tero Kristo
[...]
>> Can't we simple change the polling value for the omap5 case and reuse
>> the omap4 file?
>
> Hmm yea, I
Ping !
> -Original Message-
> From: Kedareswara rao Appana [mailto:appana.durga@xilinx.com]
> Sent: Monday, March 02, 2015 11:27 PM
> To: dan.j.willi...@intel.com; vinod.k...@intel.com; Michal Simek; Soren
> Brinkmann; robh...@kernel.org; pawel.m...@arm.com;
> mark.rutl...@arm.co; ijc+
1) Validate iov ranges before feeding them into iov_iter_init(), from
Al Viro.
2) We changed copy_from_msghdr_from_user() to zero out the msg_namelen is
a NULL pointer is given for the msg_name. Do the same in the compat
code too. From Catalin Marinas.
3) Fix partially initialized tup
On Mon, Mar 23, 2015 at 9:25 AM, David Miller wrote:
>
> Ok, here is what I committed.
So I wonder - looking at that assembly, I get the feeling that it
isn't any better code than gcc could generate from simple C code.
Would it perhaps be better to turn memmove() into C?
That's particularly tru
Hi,
On Mon, Mar 23, 2015 at 4:52 AM, Lee Jones wrote:
> On Tue, 10 Mar 2015, Chen-Yu Tsai wrote:
>
>> From: Boris BREZILLON
>>
>> Add support for the AXP22x PMIC devices to the existing AXP20x driver.
>> This includes the AXP221 and AXP223, which are identical except for
>> the external data bus
On Mon, Mar 23, 2015 at 12:02:03PM -0400, Chris Metcalf wrote:
> This driver is 64-bit only. Would it make more sense to just change
> the accessors from gettime/settime to gettime/settime64 and nothing
> else, i.e. rely on the current behavior that timespec and timespec64
> are the same type, and
Le 23 mars 2015 13:49:24 GMT-03:00, Stephane Eranian a
écrit :
>On Sun, Mar 22, 2015 at 5:27 PM, Namhyung Kim
>wrote:().
>>
>> Did you play with acme/perf/core not tip/perf/core? I got same
>> problem but then I realize it's not the Arnaldo's tree. When I
>> changed to acme/perf/core the pro
On Mon, Mar 23, 2015 at 08:37:42AM -0700, Paul E. McKenney wrote:
> On Mon, Mar 23, 2015 at 02:00:41PM +, Russell King - ARM Linux wrote:
> > On Mon, Mar 23, 2015 at 06:21:33AM -0700, Paul E. McKenney wrote:
> > > On Mon, Mar 23, 2015 at 12:55:45PM +, Russell King - ARM Linux wrote:
> > > >
Hi Linus,
Could you pull these FS-Cache fixes please?
The main thrust of the fixes are:
(1) Handle a race between operation submission on an object (eg. reading data
from that object) and the object transitioning to the dead state. The
race shows up as an assertion at fs/cachefiles/i
On Mon, Mar 23, 2015 at 11:00:53AM +, Peter Rosin wrote:
> Strongly agreed that we should fix this before it is published (I assumed
> that is was included in 3.19, it felt so long ago that Mark merged it...). My
> preference would be to remove the pll-lock things entirely though. Assuming
> y
Some perf bug fixes from David Ahern, and the fix for that nasty
memmove() bug.
Please pull, thanks a lot!
The following changes since commit b314acaccd7e0d55314d96be4a33b5f50d0b3344:
Merge branch 'for-linus' of
git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input (2015-03-19 16:43:10
-
David>
David> [PATCH] sparc64: Fix several bugs in memmove().
David> Firstly, handle zero length calls properly. Believe it or not there
David> are a few of these happening during early boot.
David> Next, we can't just drop to a memcpy() call in the forward copy case
David>
On some platforms, the low level PM code may not be initialized correctly for
a specific cpu. In this case, the EXNIO tells the cpuidle driver to not
initialize the cpuidle device as the associated low level PM is not operational.
That prevents the system to crash and allows to handle the error gr
On Sun, Mar 22, 2015 at 5:27 PM, Namhyung Kim wrote:
> Hi Stephane,
>
> On Fri, Mar 20, 2015 at 02:12:30PM -0700, Stephane Eranian wrote:
>> On Fri, Mar 20, 2015 at 2:07 PM, Arnaldo Carvalho de Melo
>> wrote:
>> > Em Fri, Mar 20, 2015 at 05:39:22PM -0300, Arnaldo Carvalho de Melo
>> > escreveu:
On Mon, Mar 23, 2015 at 03:22:14PM +0800, Jiang Liu wrote:
> Commit 63f1789ec716("Ignore resources consumed by host bridge itself")
> tries to ignore resources consumed by PCI host bridge itself by
> checking IORESOURCE_WINDOW flag, which causes regression on some
> platforms.
"Do. Or do not. Th
This vDSO code only gets used by 64-bit kernel,
not 32-bit. In 64-bit kernels, data segment is the same
for 32-bit and 64-bit userspace, and SYSRET insn does load %ss
with its selector. No need to repeat it by hand. Segment loads
are somewhat expensive: tens of cycles.
Signed-off-by: Denys Vlasenk
On Mon, Mar 16, 2015 at 02:15:46PM +, Morten Rasmussen wrote:
> You are absolutely right. The current code is broken for system
> topologies where all cpus share the same clock source. To be honest, it
> is actually worse than that and you already pointed out the reason. We
> don't have a way o
Hi Takahiro,
On Mon, 2015-03-23 at 20:53 +0900, AKASHI Takahiro wrote:
> diff --git a/arch/arm/kvm/mmu.c b/arch/arm/kvm/mmu.c
> index 3e6859b..428f41c 100644
> --- a/arch/arm/kvm/mmu.c
> +++ b/arch/arm/kvm/mmu.c
...
> +phys_addr_t kvm_get_stub_vectors(void)
> +{
> + return virt_to_phys(__hyp
Some versions of this controller do not advertise their 3.0v and
8bit bus-width support capabilities. It is required to explicitly
set these capabilities for the specific controller versions.
Signed-off-by: Georgi Djakov
---
Changes since v2:
* Use the generic sdhci bitfield defines, as the bit
On Mon, 2015-03-09 at 09:13 -0700, Sudeep Dutt wrote:
> On Mon, 2015-02-23 at 16:45 -0800, Sudeep Dutt wrote:
> > On Mon, 2015-01-26 at 16:32 -0800, Sudeep Dutt wrote:
> > > ChangeLog:
> > > =
> > >
> > > v2 => v3:
> > > a) Formatting fixes for SCIF header file documentation, data type fix
Hi,
On Monday, February 23, 2015 10:07:50 AM Viresh Kumar wrote:
> On 20 February 2015 at 21:50, Bartlomiej Zolnierkiewicz
> wrote:
> > Allow driver build for !THERMAL or !CPU_THERMAL cases.
> >
> > The new dependency rule is the same as the one that CPUFREQ_DT
> > option has (for cpufreq-dt dri
On Mon, Mar 23, 2015 at 09:43:17AM -0400, Steven Rostedt wrote:
> On Mon, 23 Mar 2015 14:34:42 +0100
> Ingo Molnar wrote:
> >
> > Even if it was documented (it isn't), it's pretty weird terminology -
> > please use clearer formulations, like 'patched function' or 'unpatched
> > function' or 'fu
From: Fu Wei
This is a update of Chinese documentation:Documentation/zh_CN/arm64/memory.txt
It is based on the modifications of Documentation/arm64/memory.txt in
submission:
"08375198", "4edae01e", "a24637d5", "383c2799".
Signed-off-by: Fu Wei
---
Documentation/zh_CN/arm64/memory.txt | 65 ++
On Sat, Mar 21, 2015 at 12:42:06PM -0700, Maxime Ripard wrote:
> This framework aims at easing the development of dmaengine drivers by
> providing
> generic implementations of the functions usually required by dmaengine, while
> abstracting away most of the logic required.
>
> It is very relevant
On 23/03/2015 at 11:11:35 +0100, Nicolas Ferre wrote :
> Le 16/03/2015 23:44, Alexandre Belloni a écrit :
> > Use syscon/regmap to configure the smc. This allows to avoid using
> > at91sam9_smc.h and to compile the driver in a multiplatform configuration.
> >
> > The driver will still not probe un
On Mon 2015-03-23 09:58:53, Steven Rostedt wrote:
> On Mon, 23 Mar 2015 14:53:06 +0100
> Ingo Molnar wrote:
>
>
> > > I think it has to do with their RCU like patching functionality,
> > > where some tasks are still executing the old function and others are
> > > executing the new function. [.
On Mon, Mar 23, 2015 at 05:25:53PM +0100, Silvan Jegen wrote:
> Remove dead code, make goto label names more expressive and add a label
> in order to call mantis_dvb_exit if mantis_uart_init fails.
>
> Also make sure that mantis_pci_exit is called if we fail the
> mantis_stream_control call and th
Tomasz,
On Mon, Mar 23, 2015 at 12:27 AM, Tomasz Figa wrote:
> IOMMU should be able to use single pages as well as bigger blocks, so if
> higher order allocations fail, we should not affect state of the system,
> with events such as OOM killer, but rather fall back to order 0
> allocations.
>
> T
Hi Rob, Philipp,
Am Mittwoch, 11. März 2015, 09:51:21 schrieb Philipp Zabel:
> Am Dienstag, den 10.03.2015, 14:05 -0500 schrieb Rob Herring:
> > I've only been copied on this latest pull request and a version from
> > March of last year which Grant nak'ed. This series did not go to
> > devicetree
Hi Archit,
> Hi Hai,
>
> On 03/19/2015 02:35 AM, h...@codeaurora.org wrote:
>> Hi Archit,
>>
>> Thanks for your comments. Please see my response for some comments
>> below.
>> Comments without response will be addressed in patch version 2. I will
>> wait for other comments if any to push patch V2.
On Mon, Mar 23, 2015 at 03:28:37PM +, Daniel Thompson wrote:
> On 20/03/15 14:28, Dave Martin wrote:
> >On Wed, Mar 18, 2015 at 02:20:22PM +, Daniel Thompson wrote:
> >>Currently the magic SysRq functions can accessed by sending a break on
> >>the serial port. Unfortunately some networked s
Em Mon, Mar 23, 2015 at 07:44:37AM -0600, David Ahern escreveu:
> On 3/23/15 2:18 AM, Namhyung Kim wrote:
> >>Just curious, could you try to measure the performance impact of this
> >>change?
> >
> > $ time perf record --call-graph dwarf -o kbuild.xxx -a -- sleep 30
> > [ perf record: Woken up
Ping !
> -Original Message-
> From: Kedareswara rao Appana [mailto:appana.durga@xilinx.com]
> Sent: Monday, March 02, 2015 11:25 PM
> To: dan.j.willi...@intel.com; vinod.k...@intel.com; Michal Simek; Soren
> Brinkmann
> Cc: dmaeng...@vger.kernel.org; linux-arm-ker...@lists.infradead.or
Remove dead code, make goto label names more expressive and add a label
in order to call mantis_dvb_exit if mantis_uart_init fails.
Also make sure that mantis_pci_exit is called if we fail the
mantis_stream_control call and that we call mantis_i2c_exit if
mantis_get_mac fails.
Signed-off-by: Silv
From: David Miller
Date: Sun, 22 Mar 2015 22:19:06 -0400 (EDT)
> I'll work on a fix.
Ok, here is what I committed. David et al., let me know if you still
see the crashes with this applied.
Of course, I'll queue this up for -stable as well.
Thanks!
[PATCH] sparc64: Fix s
On Mon, Mar 23, 2015 at 03:41:02PM +, Daniel Lezcano wrote:
> On 03/21/2015 09:35 PM, Lorenzo Pieralisi wrote:
> > On Fri, Mar 20, 2015 at 11:44:00AM +, Daniel Lezcano wrote:
> >> Some architectures have some cpus which does not support idle states.
> >>
> >> Let the underlying low level co
Hi Vinod,
Sorry for the delay in reply. Answers for the comments inline.
> -Original Message-
> From: Vinod Koul [mailto:vinod.k...@intel.com]
> Sent: Tuesday, March 17, 2015 4:38 PM
> To: Appana Durga Kedareswara Rao
> Cc: dan.j.willi...@intel.com; Michal Simek; Soren Brinkmann;
> dmaeng
The low power sleep mode on wm5110 requires that the LDO1 regulator be
set to 1.175V prior to entering sleep, then returned to 1.2V after
exiting sleep mode. This patch apply these regulator settings.
Signed-off-by: Charles Keepax
Acked-by: Mark Brown
---
drivers/mfd/arizona-core.c | 52 +
wm5102 applies a custom hardware boot sequence, for this the SYSCLK
needs to be enabled. This patch factors out the code that enables
SYSCLK for this sequence such that it can be used for other boot time
operations that require SYSCLK.
Signed-off-by: Charles Keepax
---
Changes since v3:
- Split
Some register settings must be applied before the first time low power
sleep mode is entered on the wm5110 to ensure optimium performance.
These settings require SYSCLK to be enabled whilst they are being
applied. This patch applies the settings using the recently factored out
boot time SYSCLK func
This patch adds support for the 1.175V mode on the LDO1 regulator on the
wm5110. This is need as part of the low power sleep mode operation.
Signed-off-by: Charles Keepax
Acked-by: Mark Brown
---
drivers/regulator/arizona-ldo1.c | 15 +++
1 files changed, 15 insertions(+), 0 delet
On Mon, 23 Mar 2015 16:05:29 +0100
Gerd Hoffmann wrote:
> On Mo, 2015-03-23 at 15:54 +0100, Michael S. Tsirkin wrote:
> > On Mon, Mar 23, 2015 at 03:27:35PM +0100, Gerd Hoffmann wrote:
> > > Hi,
> > >
> > > > > > > You are doing leXXX everywhere, that's VERSION_1 dependency.
> > > > > > > virt
On Wed, Feb 04, 2015 at 06:31:06PM +, Morten Rasmussen wrote:
> Add another member to the family of per-cpu sched_domain shortcut
> pointers. This one, sd_ea, points to the highest level at which energy
> model is provided. At this level and all levels below all sched_groups
> have energy model
Em Mon, Mar 23, 2015 at 11:50:05AM +0800, Yunlong Song escreveu:
> Signed-off-by: Yunlong Song
> Signed-off-by: Namhyung Kim
Humm, this doesn't seem to apply (Namhyung's S-o-B), as this patch was
made by you and is not going thru him, right? And I haven't seen him
providing any endorsement tags.
On Mon, Mar 23, 2015 at 9:19 AM, Russell King - ARM Linux
wrote:
> On Mon, Mar 23, 2015 at 09:32:54PM +0800, Shawn Guo wrote:
>> On Mon, Mar 16, 2015 at 03:53:49PM -0600, George Joseph wrote:
>> > The Cubox has a recessed button between the HDMI and RJ-45 connectors
>> > that wasn't mapped in the
On Wed, Feb 04, 2015 at 06:31:05PM +, Morten Rasmussen wrote:
> @@ -4596,9 +4596,10 @@ static int get_cpu_usage(int cpu)
> {
> unsigned long usage = cpu_rq(cpu)->cfs.utilization_load_avg;
> unsigned long blocked = cpu_rq(cpu)->cfs.utilization_blocked_avg;
> + unsigned long cap
On 03/23/15 01:34, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20150320:
>
on x86_64:
../sound/soc/codecs/rt5645.c:2858:1: warning: data definition has no type or
storage class [enabled by default]
module_i2c_driver(rt5645_i2c_driver);
^
../sound/soc/codecs/rt5645.c:2858:1: error: ty
Hello,
On 03/16/2015 03:16 PM, Javier Martinez Canillas wrote:
> Andrzej,
>
> I looked at the Exynos5250 manual and I didn't find anything obvious
> that is missing in the DISP1 pd dev node but the asynchronous bridges
> clocks needed on Exynos5420 was also not well documented so I don't
> know i
On Mon, 23 Mar 2015, Linus Walleij wrote:
> This strips the STMPE touchscreen input driver to only probe
> and acquire its configuration from the device tree. No in-kernel
> platforms use the static platform data so there is no point in
> keeping it around.
>
> Signed-off-by: Linus Walleij
> ---
On Mon, 23 Mar 2015, Linus Walleij wrote:
> The STMPE platform data is only populated from the device tree
> in all existing users, so push the struct and make the OF case
> the norm.
>
> Signed-off-by: Linus Walleij
> ---
> drivers/mfd/stmpe.c | 41 ++-
On 03/23/2015 02:22 PM, Takashi Iwai wrote:
> At Mon, 23 Mar 2015 10:35:41 +0100,
> Takashi Iwai wrote:
>>
>> At Mon, 23 Mar 2015 10:02:52 +0100,
>> Takashi Iwai wrote:
>>>
>>> At Fri, 20 Mar 2015 19:16:53 +0100,
>>> Denys Vlasenko wrote:
Takashi, are you willing to reproduce the panic one mor
On Mon, Mar 23, 2015 at 5:04 PM, Suzuki K. Poulose
wrote:
> On 23/03/15 15:17, Suzuki K. Poulose wrote:
>>
>> On 23/03/15 15:10, Valentin Rothberg wrote:
>>>
>>> Hi Suzuki,
>>>
>>> your commit c9966c98697a ("arm-cci: Split the code for PMU vs driver
>>> support") renames the Kconfig option ARM_CCI
On 23/03/15 15:17, Suzuki K. Poulose wrote:
On 23/03/15 15:10, Valentin Rothberg wrote:
Hi Suzuki,
your commit c9966c98697a ("arm-cci: Split the code for PMU vs driver
support") renames the Kconfig option ARM_CCI to ARM_CCI400_PORT_CTRL.
However, the commit does not rename all references on ARM
On 03/20/2015 04:20 PM, Peter Zijlstra wrote:
> On Fri, Mar 20, 2015 at 03:41:54PM -0400, William Cohen wrote:
>>
>> There isn't any desire to aggregate the different cgroup data
>> together. The desired grouping is measurements per cgroup, kind of
>> like the pid scoping for perf but for a cgroup.
On 03/21/2015 05:39 PM, Richard Cochran wrote:
This driver calls code (via gxio_mpipe_get/set_timestamp) that makes
the assumption that the tv_sec field is 64 bits wide. So apparently
this driver is 64 bit only. So maybe this driver and device are ready
for 2038, but maybe not.
Not even compil
Hi Bo,
On Mon, Mar 23, 2015 at 06:14:17PM +0800, Bo Shen wrote:
> Hi Jonathan Richardson,
>
> On 03/21/2015 08:57 AM, Jonathan Richardson wrote:
> >+static struct platform_driver iproc_ts_driver = {
> >+.probe = iproc_ts_probe,
>
> Just a little curious, is the .remove function missing or it
On Mon, Mar 23, 2015 at 10:31:58AM -0400, Vivek Goyal wrote:
> > > I think one of the motivations behind this patch was call to kmsg_dump().
> > > Some vendors have been wanting to have the capability to save kernel logs
> > > to some NVRAM before transition to second kernel happens. Their argument
On Mon, 23 Mar 2015, Pavel Machek wrote:
> On Mon 2015-03-23 15:02:13, Lee Jones wrote:
> > On Mon, 23 Mar 2015, Pavel Machek wrote:
> > > On Mon 2015-03-23 12:07:43, Lee Jones wrote:
> > > > This patch requires a DT Ack.
> > >
> > > No, it requires DT people to be notified -- and they were, few
On Mon, Mar 23, 2015 at 04:29:01PM +0100, Linus Walleij wrote:
> This strips the STMPE touchscreen input driver to only probe
> and acquire its configuration from the device tree. No in-kernel
> platforms use the static platform data so there is no point in
> keeping it around.
>
> Signed-off-by:
On Mon 2015-03-23 10:31:51, Eduardo Valentin wrote:
> On Sun, Jan 18, 2015 at 09:28:24PM +0100, Pavel Machek wrote:
> >
> > Add support for omap3430 sensor. Tested on Nokia N900.
> >
> > Fix help text to be closer to english.
> >
> > Ifdefs in ti-bandgap.h are not neccessary, as users have #ifde
* Tero Kristo [150323 06:25]:
> On 03/23/2015 12:35 AM, Tony Lindgren wrote:
> >+static u32 ti_fapll_synth_set_frac_rate(struct fapll_synth *synth,
> >+unsigned long rate,
> >+unsigned long parent_rate)
> >+{
> >+u32 post_
On Mon, 2015-03-23 at 20:53 +0900, AKASHI Takahiro wrote:
> The current kvm implementation keeps EL2 vector table installed even
> when the system is shut down. This prevents kexec from putting the system
> with kvm back into EL2 when starting a new kernel.
This is a kvm bug fix, so I think the su
Le 17/03/2015 20:02, Alan Stern a écrit :
> On Tue, 17 Mar 2015, Boris Brezillon wrote:
>
>> Now that the system clock driver is forwarding set_rate request to the
>> parent clock, we can safely call clk_set_rate on the system clk and get
>> rid of the uclk field.
>>
>> Signed-off-by: Boris Brezil
Hi Eric,
On 03/23/2015 05:38 PM, Eric Dumazet wrote:
On Mon, 2015-03-23 at 13:38 +0300, Alexey Kodanev wrote:
\
@@ -1538,7 +1525,7 @@ do_time_wait:
&ipv6_hdr(skb)->saddr, th->source,
&ipv6_hdr(skb)->daddr,
On Mon 2015-03-23 15:02:13, Lee Jones wrote:
> On Mon, 23 Mar 2015, Pavel Machek wrote:
> > On Mon 2015-03-23 12:07:43, Lee Jones wrote:
> > > This patch requires a DT Ack.
> >
> > No, it requires DT people to be notified -- and they were, few times
> > by now.
> >
> > They clearly don't care.
>
On 03/23/15 01:34, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20150320:
>
on x86_64:
drivers/built-in.o: In function `printer_func_unbind':
f_printer.c:(.text+0x56e25f): undefined reference to `usb_free_all_descriptors'
drivers/built-in.o: In function `printer_attr_release':
f_printer
On Mon, 2015-03-23 at 14:52 +0100, Pablo Neira Ayuso wrote:
> I would also prefer if you include the explicit header files in that
> patch too. Could you send us a v2? Please, Cc:
> netfilter-de...@vger.kernel.org
As I wrote to Stephen, I'd prefer to #include
kernel.h where it's not already specif
On 03/21/2015 09:35 PM, Lorenzo Pieralisi wrote:
On Fri, Mar 20, 2015 at 11:44:00AM +, Daniel Lezcano wrote:
Some architectures have some cpus which does not support idle states.
Let the underlying low level code to return -ENXIO when it is not
possible to set an idle state.
Well, this is
On Mon, Mar 23, 2015 at 02:00:41PM +, Russell King - ARM Linux wrote:
> On Mon, Mar 23, 2015 at 06:21:33AM -0700, Paul E. McKenney wrote:
> > On Mon, Mar 23, 2015 at 12:55:45PM +, Russell King - ARM Linux wrote:
> > > What if the cpu_hotplug_state for the CPU changes between reading it
> >
On Tue, 2015-03-24 at 00:38 +1100, Stephen Rothwell wrote:
> Hi Joe,
Hi Stephen.
> I am not sure what you are getting at here. kernel.h does not include
> kern_levels.h (but printk.h does). I, for one, am always happier when
> necessary include files are explicitly included.
kernel.h -> printk
On Mon, Mar 23, 2015 at 08:19:43AM +0100, Ingo Molnar wrote:
>
> * Baoquan He wrote:
>
> > CC more people ...
> >
> > On 03/07/15 at 01:31am, "Hatayama, Daisuke/畑山 大輔" wrote:
> > > The commit f06e5153f4ae2e2f3b0300f0e260e40cb7fefd45 introduced
> > > "crash_kexec_post_notifiers" kernel boot opti
On 03/22/2015 10:18 PM, Tejun Heo wrote:
From 1ebf33901ecc75d9496862dceb1ef0377980587c Mon Sep 17 00:00:00 2001
From: Tejun Heo
Date: Mon, 23 Mar 2015 00:08:19 -0400
2f800fbd777b ("writeback: fix dirtied pages accounting on redirty")
introduced account_page_redirty() which reverts stat updates
On 3/21/2015 10:39 PM, Richard Cochran wrote:
This device stores the number of seconds in a 32 bit register. So
more work is needed on this driver before the year 2038 comes around.
Compile tested only.
I cannot perform tests on my side, unfortunately. I have no setup at
this moment. Added Ra
Do not call power_supply_powers() if power_supply_register() failed
earlier. This fixes possible NULL pointer dereference by
power_supply_powers() in such case.
Signed-off-by: Krzysztof Kozlowski
Reported-by: Dan Carpenter
---
The patch was prepared on top of next-20150323. It depends on
On Mon, 23 Mar 2015 08:25:07 -0700
"Paul E. McKenney" wrote:
> > Not sure why this was 9 patches. I think this could have easily been a
> > single patch.
>
> In order to make it easier to deal with conflicts and to move patches
> across this series as needed. I could consolidate them later on,
On Fri, Mar 20, 2015 at 5:49 PM, Dave Airlie wrote:
>
> Hi Linus,
>
> a bunch of fixes across drivers,
> radeon: disable two ended allocation for now, it breaks some stuff
> amdkfd: misc fixes
> nouveau: fix irq loop problem, add basic support for GM206 (new hw)
> i915: fix some WARNs people were
hfsplus_file_fsync() siliently ignores the return value of
sync_inode_metadata().
If an error occurs at sync_inode_metadata() and subsequent updates of other file
system metadata (b-trees) succeed, file system metadata will be inconsistent.
Signed-off-by: Changwoo Min
---
fs/hfsplus/inode.c |
On 03/23/2015 04:27 PM, Lorenzo Pieralisi wrote:
On Fri, Mar 20, 2015 at 11:43:53AM +, Daniel Lezcano wrote:
There is a big number of cpuidle drivers for the ARM architecture.
These drivers have been cleaned up and grouped into the drivers/cpuidle
directory to keep track of the changes more
301 - 400 of 785 matches
Mail list logo
