popen() causes an error message to print if perf-read-vdso32
does not run. Avoid that by not trying to run it if it was
not built. Ditto perf-read-vdsox32.
Signed-off-by: Adrian Hunter
---
tools/perf/config/Makefile | 8 ++--
tools/perf/util/vdso.c | 10 ++
2 files changed,
Use the new db_export facility to export data in a
database-friendly way.
A Python script selects the db_export mode by setting
a global variable 'perf_db_export_mode' to True. The
script then optionally implements functions to receive
table rows. The functions are:
evsel_table
perf tools copy VDSO out of memory. However, on 64-bit
machines there may be 32-bit compatibility VDOs also. To
copy those requires separate 32-bit executables. This
patch adds to the build additional programs perf-read-vdso32
and perf-read-vdsox32 for 32-bit and x32 respectively.
Add the ability to export detailed information about
paired calls and returns to Python db export and
the export-to-postgresql.py script.
Signed-off-by: Adrian Hunter
---
.../scripts/python/bin/export-to-postgresql-report | 15 ++--
tools/perf/scripts/python/export-to-postgresql.py | 66
'perf record' post-processes the event stream to create
a list of build-ids for object files for which sample
events have been recorded. That results in those object
files being recorded in the build-id cache.
In the case of VDSO, perf tools reads it from memory
and copies it into a temporary
Hi
Here are the remaining Intel PT preparation patches. They are
all patches that have been posted before, although "perf tools:
Do not attempt to run perf-read-vdso32 if it wasn't built" wasn't
sent as a separate email.
With regard to "32-bit compatibility VDSOs", you may recall that
Ingo had
On Tue, Oct 21, 2014 at 5:48 AM, Brian Vandre wrote:
> This fixes the checkpatch.pl warning:
> WARNING: line over 80 characters
>
> Signed-off-by: Brian Vandre
As a part of OPW [1] IIO cleanup project [2] we analyzed all checkpatch.pl
warnings / errors and we decided not to fix some of them as
On Wednesday 22 October 2014 19:10:05 Guenter Roeck wrote:
> On Wed, Oct 22, 2014 at 06:35:53PM +0200, Pali Rohár wrote:
> > On Wednesday 22 October 2014 18:19:47 Guenter Roeck wrote:
> > > On Wed, Oct 22, 2014 at 02:29:06PM +0200, Pali Rohár wrote:
> > > > On Tuesday 21 October 2014 06:27:23
On 10/22/2014 01:56 AM, Peter Zijlstra wrote:
> On Tue, Oct 21, 2014 at 08:09:48PM +0300, Kirill A. Shutemov wrote:
>> It would be interesting to see if the patchset affects non-condended case.
>> Like a one-threaded workload.
>
> It does, and not in a good way, I'll have to look at that... :/
From: Alexander Usyskin
commit cfda2794b5afe7ce64ee9605c64bef0e56a48125 upstream.
function 'strncpy' will fill whole buffer 'id.name' of fixed size (32)
with string value and will not leave place for NULL-terminator.
Possible buffer boundaries violation in following string operations.
Replace
On Wed, 22 Oct 2014 13:09:26 +0200
Dominik Dingel wrote:
> s390 has the special notion of storage keys which are some sort of page flags
> associated with physical pages and live outside of direct addressable memory.
> These storage keys can be queried and changed with a special set of
>
On Thu, Oct 23, 2014 at 03:37:14PM +0530, Sudip Mukherjee wrote:
> On Fri, Oct 17, 2014 at 07:05:19PM +, Paul Zimmerman wrote:
> > > From: Felipe Balbi [mailto:ba...@ti.com]
> > > Sent: Friday, October 17, 2014 11:52 AM
> > >
> > > On Fri, Oct 17, 2014 at 06:50:19PM +, Paul Zimmerman
On 10/22/2014 02:46 PM, Nishanth Menon wrote:
> Increase the maximum number of consoles possible to 10 since DRA7 now
> has the maximum number of consoles possible. without doing this, for
> example, enabling DRA7 UART10 results in internal data structures and
> console cannot match up and we
>
> +struct vm_area_struct *find_vma_srcu(struct mm_struct *mm, unsigned long
> addr)
> +{
> + struct vm_area_struct *vma;
> + unsigned int seq;
> +
> + WARN_ON_ONCE(!srcu_read_lock_held(_srcu));
> +
> + do {
> + seq = read_seqbegin(>mm_seq);
> + vma =
On Fri, Oct 17, 2014 at 07:05:19PM +, Paul Zimmerman wrote:
> > From: Felipe Balbi [mailto:ba...@ti.com]
> > Sent: Friday, October 17, 2014 11:52 AM
> >
> > On Fri, Oct 17, 2014 at 06:50:19PM +, Paul Zimmerman wrote:
> > > > From: Sudip Mukherjee [mailto:sudipm.mukher...@gmail.com]
> > >
On Thu, 23 Oct 2014, PERIER Romain wrote:
> 2014-10-22 17:50 GMT+02:00 Lee Jones :
> > On Wed, 22 Oct 2014, PERIER Romain wrote:
> >
> >> This is related to the following subject "[RFC v3 PATCH 1/5] of: Add
> >> standard property for poweroff capability" and depends on the
> >> corresponding
[ +CC: Guenter, Lee, linux-pm ]
On Tue, Oct 14, 2014 at 06:31:09AM +, Romain Perier wrote:
> Several drivers create their own devicetree property when they register
> poweroff capabilities. This is for example the case for mfd, regulator
> or power drivers which define
On Monday, October 20, 2014 10:28:53 AM Wilck, Martin wrote:
> On Fri, 2014-10-17 at 18:14 +0200, Corey Minyard wrote:
>
>
> > How about this. I did a little research, and there's something called
> > soft module dependencies. Apparently you can add:
> >
> > MODULE_SOFTDEP("post:
On Thu, Oct 23, 2014 at 11:40 AM, Greg KH wrote:
> On Thu, Oct 23, 2014 at 01:52:24AM -0700, russ.d...@gmail.com wrote:
>> From: Russ Dill
>>
>> This patch provides the FTDI genuine product verification steps
>> as contained within the new 2.12.00 official release. It ensures
>> that
Currently the error message is needlessly splitted across two lines.
Signed-off-by: Geert Uytterhoeven
Cc: David Airlie
---
drivers/gpu/drm/i915/i915_irq.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/i915/i915_irq.c b/drivers/gpu/drm/i915/i915_irq.c
Signed-off-by: Geert Uytterhoeven
Cc: John W. Linville
---
drivers/net/wireless/iwlegacy/4965-rs.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/wireless/iwlegacy/4965-rs.c
b/drivers/net/wireless/iwlegacy/4965-rs.c
index eaaeea19d8c5bcc9..bac60b2bc3f014a5
Signed-off-by: Geert Uytterhoeven
Cc: linux-...@vger.kernel.org
---
drivers/uwb/rsv.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/uwb/rsv.c b/drivers/uwb/rsv.c
index 0887ae982783b7df..536ad42b0a4b1d7e 100644
--- a/drivers/uwb/rsv.c
+++ b/drivers/uwb/rsv.c
@@
Currently the error message is needlessly splitted across two lines.
Signed-off-by: Geert Uytterhoeven
Cc: Rafael J. Wysocki
---
drivers/cpufreq/cpufreq-dt.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/cpufreq/cpufreq-dt.c b/drivers/cpufreq/cpufreq-dt.c
index
On Thu, Oct 23, 2014 at 01:47:37AM +0200, Hartmut Knaack wrote:
> Sudip Mukherjee schrieb am 22.10.2014 06:21:
> > On Tue, Oct 21, 2014 at 05:56:47PM -0500, Brian Vandre wrote:
> >> This fixes the 2 checkpatch.pl warnings:
> >> WARNING: line over 80 characters
> >>
> > please check your patch with
On 10/23/2014 10:16 AM, Alexandre Courbot wrote:
> Add the new flags argument to calls of (devm_)gpiod_get*() and
> remove any direction setting code afterwards.
>
> Currently both forms (with or without the flags argument)
> are valid thanks to transitional macros in
> . These macros will be
On 10/23/2014 10:16 AM, Alexandre Courbot wrote:
> Add the new flags argument to calls of (devm_)gpiod_get*() and
> remove any direction setting code afterwards.
>
> Currently both forms (with or without the flags argument)
> are valid thanks to transitional macros in
> . These macros will be
On Thu, Oct 23, 2014 at 01:52:24AM -0700, russ.d...@gmail.com wrote:
> From: Russ Dill
>
> This patch provides the FTDI genuine product verification steps
> as contained within the new 2.12.00 official release. It ensures
> that counterfeiters don't exploit engineering investment made
> by FTDI.
Thermal is TS-ADC Controller module supports
user-defined mode and automatic mode.
User-defined mode refers,TSADC all the control signals entirely by
software writing to register for direct control.
Automaic mode refers to the module automatically poll TSADC output,
and the results were
This add the necessary binding documentation for the thermal
found on Rockchip SoCs
Signed-off-by: zhaoyifeng
Signed-off-by: Caesar Wang
---
.../bindings/thermal/rockchip-thermal.txt | 53 ++
1 file changed, 53 insertions(+)
create mode 100644
This patch changes a dtsi file to contain the thermal data
on RK3288 and later SoCs. This data will
enable a thermal shutdown over 125C.
Signed-off-by: Caesar Wang
---
arch/arm/boot/dts/rk3288-thermal.dtsi | 65 +++
1 file changed, 65 insertions(+)
create mode
This patch is depend on rk3288-thermal.dtsi,or
it will compile error.
If the temperature over a period of time High,over 120C
the resulting TSHUT gave CRU module,let it reset
the entire chip,or via GPIO give PMIC.
Signed-off-by: Caesar Wang
---
arch/arm/boot/dts/rk3288.dtsi | 21
This series patchs tested on rk3288 SDK board and pinky-v1,v2 board.
I believe the driver can be used on the rk3288-evb board.
Add this driver, The system can reset the entire chip when
the thermal temperture over 120C, In case of rising over 125C
when tha hardware shorting,The sodftware will
when a thermal temperature over TSHUT.Default to via
CRU reset the entire chip on rk3288-evb Board,
TSHUT is low active on rk3288-evb board.
Signed-off-by: Caesar Wang
---
arch/arm/boot/dts/rk3288-evb.dtsi | 6 ++
1 file changed, 6 insertions(+)
diff --git
On Thu, Oct 23, 2014 at 05:15:18PM +0900, Alexandre Courbot wrote:
> Add the new flags argument to calls of (devm_)gpiod_get*() and
> remove any direction setting code afterwards.
Applied, thanks.
signature.asc
Description: Digital signature
Hi Peter,
2014-10-23 10:12 GMT+02:00 Peter De Schrijver :
> This breaks DT ABI stability right? An existing device tree using
> ti,system-power-controller won't work anymore after this patch right? I don't
> think that's acceptable.
>
This is why I converted all dts which use
Hello Mark,
> On 22/10/2014, at 18:48, Mark Brown wrote:
>
>> On Mon, Oct 20, 2014 at 04:47:51PM +0200, Javier Martinez Canillas wrote:
>>
>> +char *states[PM_SUSPEND_MAX + 1] = {
>> +[PM_SUSPEND_MEM] = "regulator-state-mem",
>> +[PM_SUSPEND_MAX] = "regulator-state-disk",
On Wed, Oct 22, 2014 at 09:52:19PM +0100, Arnd Bergmann wrote:
> On Wednesday 22 October 2014 16:59:14 Lorenzo Pieralisi wrote:
> > On Wed, Oct 01, 2014 at 10:38:45AM +0100, Arnd Bergmann wrote:
> >
> > [...]
> >
> > > The arm32 implementations of pci_domain_nr/pci_proc_domain can probably be
>
On Thu, Oct 23, 2014 at 09:54:05AM +0200, Cornelia Huck wrote:
> On Wed, 22 Oct 2014 21:44:08 +0300
> "Michael S. Tsirkin" wrote:
>
> > virtio 1.0 makes all memory structures LE, so
> > we need APIs to conditionally do a byteswap on BE
> > architectures.
> >
> > To make it easier to check code
On 23 October 2014 02:50, Martin K. Petersen wrote:
>> "Sitsofe" == Sitsofe Wheeler writes:
>
> Sitsofe> 2. On top of the above, when a disk is "small" (has less than
> Sitsofe>2^32 sectors which is typically < 2 TBytes in size) READ
> Sitsofe>CAPACITY(16) won't be triggered.
>
>
Following the logic of the previous patch, retrieve from the idle task the
expected timer sleep duration and pass it to the cpuidle framework.
Take the opportunity to remove the unused headers in the menu.c file.
This patch does not change the current behavior.
Signed-off-by: Daniel Lezcano
In the current code, the check to reflect or not the outcoming state is done
against the idle state which has been chosen and its value.
Instead of doing a check in each of the reflect functions, just don't call
reflect
if something went wrong in the idle path.
Signed-off-by: Daniel Lezcano
The first time the 'get_typical_function' is called, it computes an average
of zero as no data is filled yet. That leads the 'data->predicted_us' variable
to be set to zero too.
The caller, 'menu_select' will then do:
interactivity_req = data->predicted_us /
In order to prevent a pointless forward declaration, just move the function
at the beginning of the file.
This patch does not change the behavior of the governor, it is just code
reordering.
Signed-off-by: Daniel Lezcano
---
drivers/cpuidle/governors/menu.c | 149
When the pmqos latency requirement is set to zero that means "poll in all the
cases".
That is correctly implemented on x86 but not on the other archs.
As how is written the code, if the latency request is zero, the governor will
return zero, so corresponding, for x86, to the poll function, but
On Thu, Oct 23, 2014 at 10:53 AM, Peter Zijlstra wrote:
> On Wed, Oct 22, 2014 at 11:04:31PM +0200, Stephane Eranian wrote:
>> Here is a simple case:
>> Limiting each HT to only 2 counters, can be any, 2 out of 4 possible.
>>
>> HT0: you measure a MEM* in ctr2, it is started first, and it keeps
(2014/10/23 17:21), Namhyung Kim wrote:
> Hi Masami,
>
> On Thu, 23 Oct 2014 15:33:37 +0900, Masami Hiramatsu wrote:
>> (2014/10/23 14:54), Srikar Dronamraju wrote:
>>> I am somehow not able to figure out how perf probe comes into the
>>> current workflow.
>>>
>>> I think the current design was
On 2014-10-23 03:11, Steven Rostedt wrote:
> On Wed, 22 Oct 2014 21:44:08 +0200
> Michal Marek wrote:
>
>> Dne 22.10.2014 v 16:19 Steven Rostedt napsal(a):
>>>
>>> Commit 7ff525712acf "kbuild: fake the "Entering directory ..." message
>>> more simply" changed the output of "make kernelrelease"
On Wed, Oct 22, 2014 at 11:04:31PM +0200, Stephane Eranian wrote:
> Here is a simple case:
> Limiting each HT to only 2 counters, can be any, 2 out of 4 possible.
>
> HT0: you measure a MEM* in ctr2, it is started first, and it keeps running
> HT1: you measure PREC_DIST with PEBS (it requires
From: Russ Dill
This patch provides the FTDI genuine product verification steps
as contained within the new 2.12.00 official release. It ensures
that counterfeiters don't exploit engineering investment made
by FTDI. Counterfeit ICs are destroying innovation in the
industry.
FTDI recommends that
On 2014-10-22 22:35, Steven Rostedt wrote:
> On Wed, 22 Oct 2014 21:44:08 +0200
> Michal Marek wrote:
>
>> Dne 22.10.2014 v 16:19 Steven Rostedt napsal(a):
>>>
>>> Commit 7ff525712acf "kbuild: fake the "Entering directory ..." message
>>> more simply" changed the output of "make kernelrelease"
This patch adds the necessary functions to interface the HDMI audio CODEC.
Signed-off-by: Jean-Francois Moine
---
.../devicetree/bindings/drm/i2c/tda998x.txt| 18 ++
drivers/gpu/drm/i2c/Kconfig| 1 +
drivers/gpu/drm/i2c/tda998x_drv.c | 264
The NXP TDA998x HDMI transmitter may transmit audio to the HDMI link
from 2 different sources, I2S and S/PDIF.
This patch set first adds an interface between a HDMI transmitter and
the HDMI CODEC.
The interface is then used by the TDA998x driver to describe its audio
capabilities (DAIs), to give
Audio in HDMI asks for:
- the audio constraints of the HDMI device to be known when choosing
the audio routes in the audio subsystem, and
- the HDMI transmitter to know which of its audio inputs has been
chosen when audio streaming starts.
This patch adds the interface between a HDMI
ping?
On Sun, Oct 19, 2014 at 05:13:56PM +0200, Christoph Hellwig wrote:
> Fix the assumption that we can treat all blk-mq requests as tagged. For
> traditional SCSI that's wrong, as being tagged has a very explicit meaning
> on the wire.
>
> This is a little bit different from the version
On Wed, Oct 22, 2014 at 04:31:09PM +0200, Frans Klaver wrote:
> Currently the ltc2952 supports only one button sequence to initiate
> powerdown. This is not always desirable, as even prolonged button
> presses can happen in use.
>
> Allow ltc2952 users to pick their own power down sequence, by
В Ср, 22/10/2014 в 11:00 +0100, Juri Lelli пишет:
> On 21/10/14 15:21, Kirill Tkhai wrote:
> > В Вт, 21/10/2014 в 12:41 +0100, Juri Lelli пишет:
> >> On 21/10/14 11:48, Kirill Tkhai wrote:
> >>> В Вт, 21/10/2014 в 11:30 +0100, Juri Lelli пишет:
> Hi Kirill,
>
> sorry for the late
On 10/23/2014 10:15 AM, Joonsoo Kim wrote:
> On Tue, Oct 14, 2014 at 01:53:44PM -0700, a...@linux-foundation.org wrote:
>>
>> The patch titled
>> Subject: mm/compaction.c: avoid premature range skip in
>> isolate_migratepages_range
>> has been added to the -mm tree. Its filename is
>>
This function actually operates on a gpio_chip, so its prefix should
reflect that fact for consistency with other functions defined in
gpio/driver.h.
Signed-off-by: Alexandre Courbot
---
Just a consistency change ; hopefully we can slip this under the GPIO
tree without getting acked-bys from
drivers/net/ethernet/apm/xgene/xgene_enet_sgmac.c: In function
‘xgene_enet_ecc_init’:
drivers/net/ethernet/apm/xgene/xgene_enet_sgmac.c:126: warning: ‘data’ may be
used uninitialized in this function
Depending on the arbitrary value on the stack, the loop may terminate
too early, and cause a
On Wed, Oct 22, 2014 at 10:06:41PM -0700, Guenter Roeck wrote:
> On 10/22/2014 09:37 PM, Florian Fainelli wrote:
> >You probably want the number of temperature sensors to come from the
> >switch driver, and support arbitrary number of temperature sensors?
>
> In that case we would need the number
This patch is used to add vendor prefix for Micron Technology Inc in the
vendor-prefixes.txt file.
Micron Technology, Inc. is an American multinational corporation based in
Boise, Idaho,
best known for producing many forms of semiconductor devices. This includes
DRAM, SDRAM,
flash memory,
Hi Masami,
On Thu, 23 Oct 2014 15:33:37 +0900, Masami Hiramatsu wrote:
> (2014/10/23 14:54), Srikar Dronamraju wrote:
>> I am somehow not able to figure out how perf probe comes into the
>> current workflow.
>>
>> I think the current design was
>> 1. perf sdt-cache --add (only once per file)
>>
From: Byungchul Park
Usually, "msecs" notation means milli-seconds, and "usecs" notation
means micro-seconds. Since the unit used in the code is
micro-seconds, the notation should be replaced from msecs to usecs.
This confusing notation prevents us from understanding the code
correctly.
Add the new flags argument to calls of (devm_)gpiod_get*().
Currently both forms (with or without the flags argument)
are valid thanks to transitional macros in
. These macros will be removed once
all consumers are updated and the flags argument will become
compulsary.
Signed-off-by: Alexandre
From: Byungchul Park
Currently, function graph tracer prints "!" or "+" just before
function execution time to signal a function overhead, depending
on the time. Even it is usually enough to do that, we sometimes
need to be signaled for bigger execution time than 100 micro seconds.
For example,
From: Byungchul Park
Hello.
When I analysis the exit_mm() function to find out the reason why the
function spends much time occasionally, this patch was very useful.
I thought this patch cannot be useful only for me, but can be also
useful for anybody who want to be signaled for very large
Add the new flags argument to calls of (devm_)gpiod_get*() and
remove any direction setting code afterwards.
Currently both forms (with or without the flags argument)
are valid thanks to transitional macros in
. These macros will be removed once
all consumers are updated and the flags argument
Add the new flags argument to calls of (devm_)gpiod_get*() and
remove any direction setting code afterwards.
Currently both forms (with or without the flags argument)
are valid thanks to transitional macros in
. These macros will be removed once
all consumers are updated and the flags argument
On Tue, Oct 14, 2014 at 01:53:44PM -0700, a...@linux-foundation.org wrote:
>
> The patch titled
> Subject: mm/compaction.c: avoid premature range skip in
> isolate_migratepages_range
> has been added to the -mm tree. Its filename is
>
>
Hello,
On 2014-10-21 02:05, Laura Abbott wrote:
On 10/20/2014 6:50 AM, Stefan Hengelein wrote:
Well,
arch/arm/mm/dma-mapping.c: In function ‘__atomic_get_pages’:
arch/arm/mm/dma-mapping.c:1265:31: error: ‘atomic_pool’ undeclared
(first use in this function)
arch/arm/mm/dma-mapping.c: In
Add the new flags argument to calls of (devm_)gpiod_get*() and
remove any direction setting code afterwards.
Currently both forms (with or without the flags argument)
are valid thanks to transitional macros in
. These macros will be removed once
all consumers are updated and the flags argument
In free_pcppages_bulk(), we use cached migratetype of freepage
to determine type of buddy list where freepage will be added.
This information is stored when freepage is added to pcp list, so
if isolation of pageblock of this freepage begins after storing,
this cached information could be stale. In
There are two paths to reach core free function of buddy allocator,
__free_one_page(), one is free_one_page()->__free_one_page() and the
other is free_hot_cold_page()->free_pcppages_bulk()->__free_one_page().
Each paths has race condition causing serious problems. At first, this
patch is focused
Add the new flags argument to calls of (devm_)gpiod_get*() and
remove any direction setting code afterwards.
Currently both forms (with or without the flags argument)
are valid thanks to transitional macros in
. These macros will be removed once
all consumers are updated and the flags argument
On Thu, Oct 23, 2014 at 09:49:14AM +0200, Arnd Bergmann wrote:
> On Thursday 23 October 2014 16:07:12 Michael Ellerman wrote:
> > --- a/include/linux/kcmp.h
> > +++ b/include/linux/kcmp.h
> > @@ -1,17 +1,6 @@
> > #ifndef _LINUX_KCMP_H
> > #define _LINUX_KCMP_H
> >
> > -/* Comparison type */
>
On Thu, Oct 23, 2014 at 10:01:08AM +0200, Stephane Eranian wrote:
> On Thu, Oct 23, 2014 at 9:19 AM, Jiri Olsa wrote:
> > On Wed, Oct 22, 2014 at 02:31:51PM +0200, Jiri Olsa wrote:
> >> On Thu, Oct 09, 2014 at 06:34:40PM +0200, Stephane Eranian wrote:
> >> > From: Maria Dimakopoulou
SNIP
> >>
Current pageblock isolation logic could isolate each pageblock
individually. This causes freepage accounting problem if freepage with
pageblock order on isolate pageblock is merged with other freepage on
normal pageblock. We can prevent merging by restricting max order of
merging to pageblock
Andrew Morton writes:
> On Fri, 17 Oct 2014 10:08:06 +0530 "Aneesh Kumar K.V"
> wrote:
>
>> Update generic gup implementation with powerpc specific details.
>> On powerpc at pmd level we can have hugepte, normal pmd pointer
>> or a pointer to the hugepage directory.
>>
>> ...
>>
>> ---
On Wed, Oct 22, 2014 at 04:29:22PM +0200, Joerg Roedel wrote:
> On Wed, Oct 15, 2014 at 11:10:44AM +0200, Thierry Reding wrote:
> > It seems like I never got back to you on this. The reason here is that
> > for Tegra the IOMMU is part of a larger IP block. The IP block is
> > primarily a memory
On Wed, Oct 22, 2014 at 03:26:23PM +, Romain Perier wrote:
> No longer use custom property to define poweroff capability, use the standard
> DT property instead.
>
This breaks DT ABI stability right? An existing device tree using
ti,system-power-controller won't work anymore after this
On Thu, Oct 23, 2014 at 09:06:28AM +0900, Masanari Iida wrote:
> This patch fix following error while "make xmldocs"
>
> Warning(.//drivers/gpu/drm/drm_crtc.c:778): Excess function parameter
> 'mode' description in 'drm_connector_get_cmdline_mode'
>
> Signed-off-by: Masanari Iida
Thanks,
On Wed, Oct 22, 2014 at 02:09:43PM -0700, Paul E. McKenney wrote:
> > Yes, this works. FWIW, please feel free to add
> >
> > Reported-and-tested-by: Jiri Kosina
> >
> > once merging it.
>
> Done, and thank you for both the bug report and the testing!
Works here too.
Tested-by: Borislav
В Ср, 22/10/2014 в 23:30 +0200, Oleg Nesterov пишет:
> On 10/22, Kirill Tkhai wrote:
> >
> > Unlocked access to dst_rq->curr in task_numa_compare() is racy.
> > If curr task is exiting this may be a reason of use-after-free:
>
> Thanks.
>
> And as you pointed out, there are other examples of
On 22 October 2014 17:44, Geert Uytterhoeven wrote:
> On Wed, Oct 22, 2014 at 5:28 PM, Ulf Hansson wrote:
>> On 22 October 2014 17:09, Geert Uytterhoeven wrote:
>>> On Wed, Oct 22, 2014 at 5:01 PM, Ulf Hansson wrote:
>>> +void keystone_pm_domain_attach_dev(struct device *dev)
>>> {
On Wed, Oct 22, 2014 at 11:02:26AM +0300, Tomi Valkeinen wrote:
> On 18/10/14 00:13, Jani Nikula wrote:
> > Documentation/kbuild/kconfig-language.txt warns to use select with care,
> > and in general use select only for non-visible symbols and for symbols
> > with no dependencies, because select
Hi Laurent,
On Wed, Oct 22, 2014 at 11:16:03PM +0300, Laurent Pinchart wrote:
> Hi Maxime,
>
> On Thursday 16 October 2014 18:24:53 Maxime Ripard wrote:
> > On Thu, Oct 16, 2014 at 07:15:40PM +0300, Laurent Pinchart wrote:
> > > On Thursday 16 October 2014 12:17:05 Maxime Ripard wrote:
> > > >
All the caller of __free_one_page() has similar migratetype recheck logic,
so we can move it to __free_one_page(). This reduce line of code and help
future maintenance. This is also preparation step for "mm/page_alloc:
restrict max order of merging on isolated pageblock" which fix the
freepage
Changes from v3 to v4
* Patch 1: Add code comment on nr_isolate_pageblock on struct zone (Naoya)
Add one more check in free_one_page() that checks whether
migratetype is MIGRATE_ISOLATE or not.
* Patch 4: Use min() to prevent overflow of buddy merge order (Naoya)
* Remove RFC tag
*
On Wed, Oct 22, 2014 at 10:55:17AM -0500, Christoph Lameter wrote:
> We had to insert a preempt enable/disable in the fastpath a while ago. This
> was mainly due to a lot of state that is kept to be allocating from the per
> cpu freelist. In particular the page field is not covered by
>
On Thu, Oct 23, 2014 at 9:19 AM, Jiri Olsa wrote:
> On Wed, Oct 22, 2014 at 02:31:51PM +0200, Jiri Olsa wrote:
>> On Thu, Oct 09, 2014 at 06:34:40PM +0200, Stephane Eranian wrote:
>> > From: Maria Dimakopoulou
>>
>> SNIP
>>
>> > +static struct event_constraint *
>> >
On Wed, 22 Oct 2014 21:44:08 +0300
"Michael S. Tsirkin" wrote:
> virtio 1.0 makes all memory structures LE, so
> we need APIs to conditionally do a byteswap on BE
> architectures.
>
> To make it easier to check code statically,
> add virtio specific types for multi-byte integers
> in memory.
>
On Thursday 23 October 2014 12:16:13 Chenhui Zhao wrote:
> +extern void ls1_do_deepsleep(unsigned long addr);
> +extern void ls1_start_fsm(void);
> +extern void ls1_deepsleep_resume(void);
> +extern void ls1021a_set_secondary_entry(void);
> +extern int ls1_sram_code_size;
> +extern void
Thank you!
Probably we should add it to stable trees too?
--
Regards,
Roman
22.10.2014, 22:30, "Jeff Kirsher" :
> On Wed, 2014-10-22 at 17:50 +0400, Roman Gushchin wrote:
>> Incoming packet is dropped silently by sk_filter(), if the skb was
>> allocated from pfmemalloc reserves and the
On Thursday 23 October 2014 16:07:12 Michael Ellerman wrote:
> --- a/include/linux/kcmp.h
> +++ b/include/linux/kcmp.h
> @@ -1,17 +1,6 @@
> #ifndef _LINUX_KCMP_H
> #define _LINUX_KCMP_H
>
> -/* Comparison type */
> -enum kcmp_type {
> - KCMP_FILE,
> - KCMP_VM,
> - KCMP_FILES,
On Wed, Oct 22, 2014 at 04:28:51PM +0100, Robert Bragg wrote:
> + /* XXX: Not sure that this is really acceptable...
> + *
> + * i915_gem_context.c currently owns pinning/unpinning legacy
> + * context buffers and although that code has a
> + * get_context_alignment() func
Hello,
On 2014-10-23 08:03, Weijie Yang wrote:
On Thu, Oct 9, 2014 at 10:04 AM, Fengguang Wu wrote:
FYI, we noticed the below changes on
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
commit 478e86d7c8c5f41e29abb81b05b459d24bdc71a2 ("mm: cma: adjust address limit to
>> v1->v2:
>> Add a patch to make s390 MSI code build happy between patch "x86/xen/MSI:
>> E.."
>> and "s390/MSI: Use MSI..". Fix several typo problems found by Lucas.
>>
>> RFC->v1:
>> Updated "[patch 4/21] x86/xen/MSI: Eliminate...", export msi_chip instead
>> of #ifdef to fix MSI bug in xen
> > +
> > +static int sch_gpio_irq_type(struct irq_data *d, unsigned type)
> > +{
> > + struct sch_gpio *sch = container_of(d, struct sch_gpio, data);
> > + unsigned long flags;
> > + u32 gpio_num;
> > +
> > + if (d == NULL)
> > + return -EINVAL;
> > +
> > +
Thanks for the excellent review comments. I'll do another spin an try to
incorporate most them.
/Jarkko
On Wed, Oct 22, 2014 at 11:26:46AM -0600, Jason Gunthorpe wrote:
> On Wed, Oct 22, 2014 at 07:23:56PM +0300, Jarkko Sakkinen wrote:
> > Traversal of the ACPI device tree was not done right. It
2014-10-22 17:50 GMT+02:00 Lee Jones :
> On Wed, 22 Oct 2014, PERIER Romain wrote:
>
>> This is related to the following subject "[RFC v3 PATCH 1/5] of: Add
>> standard property for poweroff capability" and depends on the
>> corresponding patch.
>
> Then it should be sent in the same patch-set.
>
601 - 700 of 1456 matches
Mail list logo
