On Friday 20 February 2015 10:24:35 Arnd Bergmann wrote:
> On Thursday 19 February 2015 17:49:50 Pali Rohár wrote:
> > Offset for smc91x must be zero otherwise smc91x linux kernel
> > driver does not detect smc91x ethernet hardware in qemu
> > N900 machine.
> >
> > Signed-off-by: Pali Rohár
>
>
* Jiri Kosina wrote:
> Alright, so to sum it up:
>
> - current stack dumping (even looking at /proc//stack) is not
> guaranteed to yield "correct" results in case the task is running at the
> time the stack is being examined
Don't even _think_ about trying to base something as
dangerous
On Friday 20 February 2015 09:22:26 Pavel Machek wrote:
> On Fri 2015-02-20 00:41:41, Pali Rohár wrote:
> > Without this patch function pm_runtime_get_sync() returns 0
> > even when some omap subfunction fails. This patch properly
> > propagate error codes from omap functions back to caller.
> >
>
On Fri, Feb 20, 2015 at 09:54:48AM +0100, Paul Bolle wrote:
> Your commit c5f43f0a70fc ("s390: remove 31 bit support") is included in
> today's linux-next (ie, next-20150220). I noticed because a script I use
> to check linux-next spotted a problem with it.
>
> T
Hi,
Here is the 4th version of of perf buildid-cache update.
This has a small updates from v2 for each patch. According to
Arnaldo's comment, I updated the document about --update
option in the first patch, and renamed --remove-all to
--purge in the second patch (it also updated document).
Only o
On Thu, Feb 19, 2015 at 2:52 AM, Nicolas Saenz Julienne
wrote:
> The gpio_chip operations receive a pointer the gpio_chip struct which is
> contained in the driver's private struct, yet the container_of call in those
> functions point to the mfd struct defined in include/linux/mfd/tps65912.h.
>
>
Add new buildid cache if the update target file is not cached.
This can happen when an old binary is replaced by new one
after caching the old one. In this case, user sees his operation
just failed. But it does not look straight, since user just
pass the binary "path", not "build-id".
# .
Add --purge FILE to remove all caches of FILE.
Since the current --remove FILE removes a cache which has
same build-id of given FILE. Since the command takes a
FILE path, it can confuse user who tries to remove cache
about FILE path.
-
# ./perf buildid-cache -v --add ./perf
Adding 133b7b
On Thu, Feb 19, 2015 at 9:48 PM, Robert Jarzmik wrote:
> David Miller writes:
>
>>> Now if you can make it in -rc2 or -rc3, this revert should be forgotten.
>>> But if
>>> you can't make it for 3.20, I'll push for the revert.
>>>
>>> So I think it's up to you now, and let's see what Gregh says a
* Peter Zijlstra wrote:
> > So this whole approach looks fragile for several reasons:
> >
> >- 'mode setting' callbacks are just bad by design
> > because they mix several functions into the same entry
> > point, complicating the handler functions
> > unnecessarily. We shoul
Em Fri, 20 Feb 2015 10:29:42 +0100
Arnd Bergmann escreveu:
> On Thursday 19 February 2015 16:06:18 Michal Marek wrote:
> > > We have similar problems in other areas
> > > of the kernel. In theory, we could enforce the VIDEO_TUNER driver to
> > > be modular here by adding lots of dependencies to i
On Wed, 2015-02-18 at 20:31 -0500, J. Bruce Fields wrote:
> On Thu, Feb 19, 2015 at 08:39:01AM +0800, Ian Kent wrote:
> > On Wed, 2015-02-18 at 15:59 -0500, J. Bruce Fields wrote:
> > > On Wed, Feb 18, 2015 at 12:31:32PM -0500, J. Bruce Fields wrote:
> > > > On Wed, Feb 18, 2015 at 12:06:20PM -0500
On Tue, 17 Feb 2015, Andrew Morton wrote:
> > It isn't possible to get the stack of a running task (other than
> > current) because we don't have the stack pointer and the stack can be
> > inconsistent anyway. Add a safe stack saving facility which only saves
> > the stack of the task if it's sle
On Thursday 19 February 2015 16:06:18 Michal Marek wrote:
> > We have similar problems in other areas
> > of the kernel. In theory, we could enforce the VIDEO_TUNER driver to
> > be modular here by adding lots of dependencies to it:
> >
> > config VIDEO_TUNER
> > tristate
> > depends o
* Linus Torvalds wrote:
> On Thu, Feb 19, 2015 at 9:39 AM, Linus Torvalds
> wrote:
> > On Thu, Feb 19, 2015 at 8:59 AM, Linus Torvalds
> > wrote:
> >>
> >> Are there known errata for the x2apic?
> >
> > .. and in particular, do we still have to worry about
> > the traditional local apic "if t
On 02/19/15 at 07:35pm, Yinghai Lu wrote:
> On Thu, Feb 19, 2015 at 6:13 PM, Baoquan He wrote:
> > On 02/18/15 at 11:47am, Yinghai Lu wrote:
> >
> > Kaslr need both virtual and physical address be randomized, otherwise
> > it doesn't make sense. Please check what hpa said about this issue:
> >
> >
On Thursday 19 February 2015 17:49:50 Pali Rohár wrote:
> Offset for smc91x must be zero otherwise smc91x linux kernel driver does not
> detect smc91x ethernet hardware in qemu N900 machine.
>
> Signed-off-by: Pali Rohár
>
Is that the same offset on real hardware, or could this be a mistake in
On Thu, Feb 19, 2015 at 05:05:28PM +, Peter Zijlstra wrote:
> On Thu, Feb 19, 2015 at 05:02:36PM +, Morten Rasmussen wrote:
> > > There is no actual function definition in this patch; this would hinder
> > > linking, no?
> >
> > The function definition already lives further down in fair.c.
Commit f47233c2d34 ("x86/mm/ASLR: Propagate base load address
calculation") causes PAGE_SIZE redefinition warnings for UML subarch
builds. This is caused by added includes that were leftovers from previous
patch versions are are not actually needed (especially page_types.h
inlcude in module.c).
On Thu, Feb 19, 2015 at 09:08:50PM -0800, Paul E. McKenney wrote:
> Hello!
>
> This series, possibly for v3.21, contains changes that allow in-kernel
> code to specify that all subsequent synchronous grace-period primitives
> (synchronize_rcu() and friends) be expedited. New rcu_expedite_gp()
> a
Fix:
drivers/base/component.c: In function 'find_components':
drivers/base/component.c:97:3: warning: format '%u' expects argument of type
'unsigned int', but argument 4 has type 'size_t' [-Wformat]
on ARM64 builds.
Signed-off-by: Russell King
---
drivers/base/component.c | 2 +-
1 file changed
(2015/02/19 17:08), Masami Hiramatsu wrote:
> Add --purge FILE to remove all caches of FILE.
> Since the current --remove FILE removes a cache which has
> same build-id of given FILE. Since the command takes a
> FILE path, it can confuse user who tries to remove cache
> about FILE path.
>
>
On Thu, Feb 19, 2015 at 09:21:51PM +0100, Fabian Frederick wrote:
> replace remaining direct access to current->state by slower
> helper function in drivers branch.
> Some of them could be optimized later using __set_current_state().
This changelog needs help. Going by this you just make the drive
Your commit c5f43f0a70fc ("s390: remove 31 bit support") is included in
today's linux-next (ie, next-20150220). I noticed because a script I use
to check linux-next spotted a problem with it.
That commit removed the Kconfig symbol MARCH_G5. It didn't remove all
references to
Alright, so to sum it up:
- current stack dumping (even looking at /proc//stack) is not
guaranteed to yield "correct" results in case the task is running at the
time the stack is being examined
- the only fool-proof way is to send IPI-NMI to all CPUs, and synchronize
the handlers between
On Fri, Feb 20, 2015 at 09:38:42AM +0100, Ingo Molnar wrote:
>
> * Viresh Kumar wrote:
>
> > Many clockevent drivers are using a switch block for handling modes in their
> > ->set_mode() callback. Some of these do not have a 'default' case and
> > adding a
> > new mode in the 'enum clock_event_
Hi,
Very very sad to not receive any comments from dm maintainers
in the past 2 mouths. I implemented read-caching for v3 because
they like to see this feature in but no comment...
I still believe they reevaluate dm-writeboost because I don't
think this driver isn't bad as they claim.
They reall
* Viresh Kumar wrote:
> Many clockevent drivers are using a switch block for handling modes in their
> ->set_mode() callback. Some of these do not have a 'default' case and adding a
> new mode in the 'enum clock_event_mode', starts giving following warnings for
> these platforms about unhandled
On 19/02/15 21:42, Jiri Olsa wrote:
> On Thu, Feb 19, 2015 at 01:22:33PM -0500, David Ahern wrote:
>> perf_time_to_tsc and tsc_to_perf_time are only used for x86. Make
>> inclusion of tsc.c dependent on x86 as well.
>
> hum, should we move it to arch/x86/util/tsc.c and remove util/tsc.c?
It is no
On 02/19/2015 10:15 PM, Stanimir Varbanov wrote:
The commit fb93f520e (dmaengine: qcom_bam_dma: Generalize BAM
register offset calculations) wrongly populated base offsets
for event registers for bam v1.4.
Signed-off-by: Stanimir Varbanov
---
drivers/dma/qcom_bam_dma.c |6 +++---
1 fil
Hello Eric, Vivek,
Do you have any comment to this patch?
On 2015/02/05 17:59, HATAYAMA Daisuke wrote:
The commit f06e5153f4ae2e2f3b0300f0e260e40cb7fefd45 introduced
"crash_kexec_post_notifiers" kernel boot option, which toggles
wheather panic() calls crash_kexec() before or after panic_notifie
> > > > > > In current state I review all 3 patches as:
> > > > > >
> > > > > > Rejected-by: Pali Rohár
> > > > > > [It breaks booting Nokia N900 device]
> > > > >
> > > > > next step, figure why it's broken. Working just fine here
> > > > > on AM335x which has the same musb IP.
> > > >
> > > >
Thanks Andrew for your comments,
On 19/02/15 18:12, Andrew Lunn wrote:
+
+Required properties:
+
+eeproms: List of phandle and data cell specifier triplet, one triplet
+for each data cell the device might be interested in. The
+triplet consists of the phandle to the eeprom provid
On Fri 2015-02-20 00:41:41, Pali Rohár wrote:
> Without this patch function pm_runtime_get_sync() returns 0 even when some
> omap subfunction fails. This patch properly propagate error codes from omap
> functions back to caller.
>
> This patch fix problem, when loading omap-aes driver in qemu caus
On Thu, Feb 19, 2015 at 12:01:14PM -0600, Rob Herring wrote:
> On Wed, Feb 18, 2015 at 8:08 PM, Frank Rowand wrote:
> > On 2/18/2015 6:59 AM, Pantelis Antoniou wrote:
> >> Implement a method of applying DT quirks early in the boot sequence.
> >>
> >> A DT quirk is a subtree of the boot DT that can
On 20/02/15 02:36, Stephen Boyd wrote:
On 02/19/15 09:08, Srinivas Kandagatla wrote:
diff --git a/drivers/Kconfig b/drivers/Kconfig
index c70d6e4..d7afc82 100644
--- a/drivers/Kconfig
+++ b/drivers/Kconfig
@@ -184,4 +184,6 @@ source "drivers/thunderbolt/Kconfig"
source "drivers/android/Kcon
* Adrien Schildknecht wrote:
> show_stack_log_lvl() does not set the log level after a new line,
> the following messages printed with pr_cont are thus assigned to the
> default log level.
> This patch prepends the log level to the next message following a new
> line.
>
> print_trace_address()
On Thu, Feb 19, 2015 at 09:30:58AM -0800, Frank Rowand wrote:
> On 2/19/2015 9:00 AM, Pantelis Antoniou wrote:
> > Hi Frank,
> >
> >> On Feb 19, 2015, at 18:48 , Frank Rowand wrote:
> >>
> >> On 2/19/2015 6:29 AM, Pantelis Antoniou wrote:
> >>> Hi Mark,
> >>>
> On Feb 18, 2015, at 19:31 , Ma
601 - 638 of 638 matches
Mail list logo
