On Mon, May 15, 2017 at 09:36:29AM +0100, Juri Lelli wrote:
> Hi,
>
> On 12/05/17 10:25, Steven Rostedt wrote:
> > On Fri, 12 May 2017 14:48:45 +0900
> > Byungchul Park wrote:
> >
> > > cpudl.elements is an instance that should be protected with a spin lock.
> > > Without it, the code would be i
Hi Jonathan,
On Mon, 15 May 2017 11:15:19 -0600
Jonathan Corbet wrote:
> On Mon, 15 May 2017 14:09:12 +0200
> Boris Brezillon wrote:
>
> > > mtd: adjust kernel-docs to avoid Sphinx/kerneldoc warnings
> >
> > Not sure how you plan to merge these changes, but if it goes through
> > a sing
Here, Clock enable can failed. So adding an error check for
clk_prepare_enable.
Signed-off-by: Arvind Yadav
---
drivers/cpufreq/kirkwood-cpufreq.c | 13 +++--
1 file changed, 11 insertions(+), 2 deletions(-)
diff --git a/drivers/cpufreq/kirkwood-cpufreq.c
b/drivers/cpufreq/kirkwood-cpu
On Mon, May 15, 2017 at 09:12:03PM +0200, Thomas Gleixner wrote:
> On Mon, 15 May 2017, Steven Rostedt wrote:
>
> > On Sun, 14 May 2017 20:27:33 +0200
> > Thomas Gleixner wrote:
> >
> > > might_sleep() checks are enabled after the boot process is done. That
> > > hides
> > > bugs in the smp bri
On May 16 2017 or thereabouts, Zheng, Lv wrote:
> Hi,
>
> > From: linux-acpi-ow...@vger.kernel.org
> > [mailto:linux-acpi-ow...@vger.kernel.org] On Behalf Of Zheng,
> > Lv
> > Subject: RE: [PATCH 2/2] Revert "ACPI / button: Change default behavior to
> > lid_init_state=open"
> >
> > Hi, Guys
>
On Tue, May 16, 2017 at 02:45:33PM +0900, Sergey Senozhatsky wrote:
> On (05/16/17 14:26), Minchan Kim wrote:
> [..]
> > > + /*
> > > +* Free memory associated with this sector
> > > +* before overwriting unused sectors.
> > > +*/
> > > + zram_slot_lock(zram, ind
The variables which are processed by RCU functions should be annotated
as RCU, otherwise sparse will report the errors like below:
"error: incompatible types in comparison expression (different
address spaces)"
Signed-off-by: Chunyan Zhang
---
Changes in v2:
* Addressed Steven's comments
- Us
Hi Eric,
On Monday 15 May 2017 17:03:29 Eric Anholt wrote:
> Laurent Pinchart writes:
> > On Thursday 11 May 2017 16:56:23 Eric Anholt wrote:
> >> The Raspberry Pi 7" Touchscreen is a DPI touchscreen panel with
> >> DSI->DPI bridge and touchscreen controller integrated, that connects
> >> to the
Signed-off-by: Jandy Gou
---
drivers/staging/fbtft/fbtft-io.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/fbtft/fbtft-io.c b/drivers/staging/fbtft/fbtft-io.c
index d868405..ffb9a3b 100644
--- a/drivers/staging/fbtft/fbtft-io.c
+++ b/drivers/staging/fbtft/fb
Below is the list of build error/warning regressions/improvements in
v4.12-rc1[1] compared to v4.11[2].
Summarized:
- build errors: +10/-3
- build warnings: +27788/-966
Note that there may be false regressions, as some logs are incomplete.
Still, they're build errors/warnings.
Happy fixing!
On Tue, May 16, 2017 at 9:25 AM, Geert Uytterhoeven
wrote:
>
> 10 error regressions:
> + /home/kisskb/slave/src/drivers/base/power/domain.c: error: 'pm_wq'
> undeclared (first use in this function): => 279:13
> + /home/kisskb/slave/src/drivers/base/power/domain.c: error: 'struct
> dev_pm_in
Hi Oza,
[auto build test ERROR on v4.9-rc8]
[cannot apply to next-20170516]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Oza-Pawandeep/of-pci-dma-fix-DMA-configuration-for-PCI-masters
On Tue, 16 May 2017, Peter Zijlstra wrote:
> On Mon, May 15, 2017 at 09:12:03PM +0200, Thomas Gleixner wrote:
> > On Mon, 15 May 2017, Steven Rostedt wrote:
> >
> > > On Sun, 14 May 2017 20:27:33 +0200
> > > Thomas Gleixner wrote:
> > >
> > > > might_sleep() checks are enabled after the boot pro
On (05/16/17 16:16), Minchan Kim wrote:
> > but would this be correct? the data is not valid - we failed to store
> > the valid one. but instead we assure application that read()/swapin/etc.,
> > depending on the usage scenario, is successful (even though the data is
> > not what application really
On Fri, Apr 28, 2017 at 10:17:43AM +0300, Peter De Schrijver wrote:
> On Thu, Apr 13, 2017 at 10:48:19AM +0300, Peter De Schrijver wrote:
> > On Wed, Apr 12, 2017 at 09:46:05AM -0700, Stephen Boyd wrote:
> > > On 03/21, Peter De Schrijver wrote:
> > > > Whenever a user change its min or max rate li
The PWM driver has now capability to specify the PWM polarity
which is e.g. for backlight control. Allow to make use of PWM
polarity by specifying pwm-cells to be 3 in the base dt.
Signed-off-by: Stefan Agner
---
arch/arm/boot/dts/imx7-colibri.dtsi | 2 +-
arch/arm/boot/dts/imx7d-nitrogen7.dts
There are some leftovers testing for pvh guest mode in pv-only source
files. Remove them.
Signed-off-by: Juergen Gross
---
arch/x86/xen/enlighten_pv.c | 15 ++-
arch/x86/xen/mmu_pv.c | 98 +
2 files changed, 40 insertions(+), 73 deletions(-)
Le 16/05/2017 à 07:15, Masahiro Yamada a écrit :
> Since commit 61562f981e92 ("uapi: export all arch specifics
> directories"), "make INSTALL_HDR_PATH=$root/usr headers_install"
> deletes standard glibc headers and others in $root/usr/include.
>
> The cause of the issue is that headers_install now
fix the sparse warning:
drivers/staging/fbtft/fbtft-io.c:74:29:
warning: incorrect type in assignment (different base types)
drivers/staging/fbtft/fbtft-io.c:74:29:expected unsigned long
long [unsigned] [long] [long long] [usertype]
drivers/staging/fbtft/fbtft
On Mon, May 08, 2017 at 08:13:37PM +0800, kernel test robot wrote:
> Greetings,
>
> 0day kernel testing robot got the below dmesg and the first bad commit is
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
>
> commit e66267161971155a8b4756b4e17f2f2f82b9f842
> Author
Signed-off-by: Jandy Gou
---
drivers/staging/fbtft/fbtft-io.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/fbtft/fbtft-io.c b/drivers/staging/fbtft/fbtft-io.c
index d868405..ffb9a3b 100644
--- a/drivers/staging/fbtft/fbtft-io.c
+++ b/drivers/staging/fbtft/fb
Hi Iwai-san,
On Fri, May 12, 2017 at 10:01 AM, Takashi Iwai wrote:
>> > But, looking at the tree again, I noticed that ALSA isn't built yet at
>> > all for m68k. I don't remember why it's disabled.
>> > Jaroslav, do you know the reason behind it?
>>
>> Because ALSA doesn't have any drivers that
Signed-off-by: Yixun Lan
---
drivers/tty/serial/meson_uart.c | 18 --
1 file changed, 16 insertions(+), 2 deletions(-)
diff --git a/drivers/tty/serial/meson_uart.c b/drivers/tty/serial/meson_uart.c
index 60f16795d16b..f0d9222db82f 100644
--- a/drivers/tty/serial/meson_uart.c
+++
On Mon, May 15, 2017 at 10:16:30AM -0700, Randy Dunlap wrote:
> From: Randy Dunlap
>
> The greybus-dev mailing list is a members-only list and is
> moderated for non-subscribers.
>
> Signed-off-by: Randy Dunlap
Acked-by: Johan Hovold
> ---
> MAINTAINERS |2 +-
> 1 file changed, 1 insert
On Mon, May 15, 2017 at 04:49:16PM +0300, Haim Daniel wrote:
> me@haim-toshiba1 ~ $ dpkg -l sparse
> Desired=Unknown/Install/Remove/Purge/Hold
> |
> Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
> |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
> ||/ Name
On Sun, 14 May 2017, Mark Brown wrote:
> On Thu, May 04, 2017 at 12:36:25AM -0400, Javier Martinez Canillas wrote:
>
> > Acked-by: Mark Brown
>
> Since I'm expected to apply this I wouldn't normally expect to see my
> ack - like I say if I'm acking something for me it's normally because I
> exp
The Spreadtrum hardware spinlock device can provide hardware assistance
for synchronization between the multiple subsystems.
Signed-off-by: Baolin Wang
---
drivers/hwspinlock/Kconfig |9 ++
drivers/hwspinlock/Makefile |1 +
drivers/hwspinlock/sprd_hwspinlock.c | 243 +
On Mon, May 15, 2017 at 05:10:18PM +0300, Haim Daniel wrote:
> -remove duplicate tty allocation code for serial and printer drivers.
> -add missing tty c_ispeed and c_ospeed initialization to 9600.
> -fix sparse warning: too long initializer-string for array of char.
This is a GCC warning and not
In addition to introducing the new compatible string the bindings
description is reworked to be more generic.
Signed-off-by: Andrew Jeffery
---
.../bindings/interrupt-controller/aspeed,ast2400-vic.txt | 9 +
drivers/irqchip/irq-aspeed-vic.c | 3 ++-
Also clean up space-before-tab issues in the documentation.
Signed-off-by: Andrew Jeffery
---
Documentation/devicetree/bindings/timer/moxa,moxart-timer.txt | 5 +++--
drivers/clocksource/moxart_timer.c| 3 ++-
2 files changed, 5 insertions(+), 3 deletions(-)
diff --g
Signed-off-by: Andrew Jeffery
---
arch/arm/boot/dts/aspeed-g5.dtsi | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm/boot/dts/aspeed-g5.dtsi b/arch/arm/boot/dts/aspeed-g5.dtsi
index a0bea4a6ec77..48a092e735d9 100644
--- a/arch/arm/boot/dts/aspeed-g5.dtsi
+++ b/arch/
On Tue, May 16, 2017 at 03:45:29PM +0800, Yixun Lan wrote:
> Signed-off-by: Yixun Lan
I don't accept patches without any changelog text, sorry.
Please fix.
thanks,
greg k-h
On Tue, May 16, 2017 at 03:42:27PM +0800, Jandy Gou wrote:
> Signed-off-by: Jandy Gou
Your subject is a bit messed up :(
Please fix and resend.
No need for the 0/1 email for just a single patch.
thanks,
greg k-h
Hi,
On 15/05/2017 at 20:51:30 -0700, Oliver Hartkopp wrote:
> On 05/15/2017 06:50 AM, Marc Kleine-Budde wrote:
> > On 05/12/2017 08:37 AM, Quentin Schulz wrote:
> > > On 05/05/2017 15:50, Quentin Schulz wrote:
> > > > To avoid possible ECC/parity checksum errors when reading an
> > > > uninitializ
On 12 May 2017 at 18:44, Peter Zijlstra wrote:
> For consistencies sake, we should have only a single reading of
> tg->shares.
>
> Signed-off-by: Peter Zijlstra (Intel)
Acked-by: Vincent Guittot
Fixing coding guideline errors reported by 'checkpatch.pl'
Signed-off-by: Pushkar Jambhlekar
---
drivers/staging/ccree/ssi_cipher.c | 158 +++--
1 file changed, 80 insertions(+), 78 deletions(-)
diff --git a/drivers/staging/ccree/ssi_cipher.c
b/drivers/staging/c
On Mon, May 15, 2017 at 08:30:13PM -0400, Rob Clark wrote:
> On Mon, May 15, 2017 at 1:20 PM, Liviu Dudau wrote:
> > From: Brian Starkey
> >
> > Writeback connectors represent writeback engines which can write the
> > CRTC output to a memory framebuffer. Add a writeback connector type and
> > rel
On 2017/05/15 01:22PM, Steven Rostedt wrote:
> On Sun, 14 May 2017 01:01:01 +0530
> "Naveen N. Rao" wrote:
>
> > Handle a NULL glob properly.
> >
> > Signed-off-by: Naveen N. Rao
> > ---
> > kernel/trace/ftrace.c | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git
Hi,
"Gustavo A. R. Silva" writes:
> Hello everybody,
>
> While looking into Coverity ID 145958 I ran into the following piece
> of code at drivers/usb/gadget/udc/amd5536udc.c:852:
>
> } else if (i == buf_len) {
> /* first td */
> td = (struct udc_data_dma *)phys_to_virt(
>
On Mon, May 15, 2017 at 02:14:13PM -0500, Dave Kleikamp wrote:
> With CONFIG_RT_GROUP_SCHED defined, do_sched_rt_period_timer() sequentially
> takes each cpu's rq->lock. On a large, busy system, the cumulative time it
> takes to acquire each lock can be excessive, even triggering a watchdog
> timeo
On Tue, May 16, 2017 at 01:35:52PM +0530, Pushkar Jambhlekar wrote:
> Fixing coding guideline errors reported by 'checkpatch.pl'
That is very "vague", you are going to have to be specific here.
Also remember you can only do "one type of thing" per patch, and no,
"fix all warnings" is not one type
On Mon, May 15, 2017 at 03:13:16PM +0200, Vlastimil Babka wrote:
> A customer has reported a soft-lockup when running a proprietary intensive
> memory stress test, where the trace on multiple CPU's looks like this:
>
> RIP: 0010:[]
> [] native_queued_spin_lock_slowpath+0x10e/0x190
> ...
> Call
On 15/05/2017 at 19:34:17 -0700, Moritz Fischer wrote:
> On Fri, May 12, 2017 at 07:00:29PM -0500, Rob Herring wrote:
> > On Tue, May 09, 2017 at 11:20:20AM -0700, Moritz Fischer wrote:
> > > + <0> for RTC
> > > + <1> for RTC + Alarm (Interrupt)
> > > +
Hi Chris,
[auto build test ERROR on hwmon/hwmon-next]
[also build test ERROR on v4.12-rc1 next-20170516]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Chris-Packham/hwmon-adt7475-fan-stall
On Mon, May 15, 2017 at 11:40:43AM -0700, Paul E. McKenney wrote:
> Given that you acquire the global pmus_lock when doing the
> get_online_cpus(), and given that CPU hotplug is rare, is it possible
> to momentarily acquire the global pmus_lock in perf_event_init_cpu()
> and perf_event_exit_cpu()
Hello,
Any input on this topic?
Kind Regards,
Bogdan
On Thursday, May 04, 2017 1:55 PM Bogdan Mirea wrote:
>
> Hi Oleksij,
>
> On Thursday, May 04, 2017 12:27 PM, Oleksij Rempel wrote:
> > Hi Bogdan,
> >
> > are there any example what and how bootloader should do to provide
> > correct values?
I have discussed this with our gcc guys and here is what they say:
On Wed 10-05-17 10:38:44, Michal Hocko wrote:
[...]
> But I
> still do not understand which part of the code is undefined and why. My
> reading and understanding of the C specification is that
> struct A {
> int a;
> in
Here, Clock enable can failed. So adding an error check for
clk_prepare_enable.
Signed-off-by: Arvind Yadav
---
drivers/crypto/img-hash.c | 12 ++--
1 file changed, 10 insertions(+), 2 deletions(-)
diff --git a/drivers/crypto/img-hash.c b/drivers/crypto/img-hash.c
index 9b07f3d8..0c6a91
fix the following sparse warning:
drivers/staging/fbtft/fbtft-io.c:74:29: warning: incorrect type in assignment
(different base types) drivers/staging/fbtft/fbtft-io.c:74:29:expected
unsigned long long [unsigned] [long] [long long] [usertype]
drivers/staging/fbtft/fbtft-io.c:74:29:got
Hi, Benjamin
> > > > > >> >> > > > > For example, such a hwdb entry is:
> > > > > >> >> > > > > libinput:name:*Lid
> > > > > >> >> > > > > Switch*:dmi:*svnMicrosoftCorporation:pnSurface3:*
> > > > > >> >> > > > > LIBINPUT_ATTR_LID_SWITCH_RELIABILITY=write_open
> > > > > >> >> Well, if it worked
* Yury Norov wrote:
> I collected about 700 results in dmesg, and took 600 fastest.
> For the vanilla kernel, the average value is 368, and for patched
> kernel it is 388. It's 5% slower. But the standard deviation is
> really big for both series' - 131 and 106 cycles respectively, which
> is ~
Fixed a warning : struct comedi_lrange is generally constant.
Signed-off-by: Srishti Sharma
---
drivers/staging/comedi/comedidev.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/comedi/comedidev.h
b/drivers/staging/comedi/comedidev.h
index 1bb9986..82df090 1
Fixing 'checkpatch.pl' ERROR: code indent should use tabs where possible
Signed-off-by: Pushkar Jambhlekar
---
drivers/staging/ccree/ssi_aead.c | 32
1 file changed, 16 insertions(+), 16 deletions(-)
diff --git a/drivers/staging/ccree/ssi_aead.c b/drivers/stagin
This is not a full event list, but a short list of useful events.
Signed-off-by: Ganapatrao Kulkarni
---
tools/perf/pmu-events/arch/arm64/mapfile.csv | 15 ++
.../arm64/thunderx2/implementation-defined.json| 62 ++
2 files changed, 77 insertions(+)
create mode
Extending json/jevent framework for parsing arm64 event files.
Adding jevents for ThunderX2 implementation defined PMU events.
v3:
- Addressed comments from Will Deacon and Jayachandran C.
- Rebased to 4.12-rc1
v2:
- Updated as per Mark Rutland's suggestions.
- Added provision for get
cpuid string will not be same on all CPUs on heterogeneous
platforms like ARM's big.LITTLE, adding provision(using pmu->cpus)
to find cpuid string from associated CPUs of PMU CORE device.
Signed-off-by: Ganapatrao Kulkarni
---
tools/perf/arch/powerpc/util/header.c | 2 +-
tools/perf/arch/x86/uti
On some platforms, PMU core devices sysfs name is not cpu.
Adding function is_pmu_core to detect as core device using
core device specific hints in sysfs.
For arm64 platforms, all core devices have file "cpus" in sysfs.
Signed-off-by: Ganapatrao Kulkarni
---
tools/perf/util/pmu.c | 44 +
function get_cpuid_str returns MIDR string of the first online
cpu from the range of cpus associated with the pmu core device.
Signed-off-by: Ganapatrao Kulkarni
---
tools/perf/arch/arm64/util/Build| 1 +
tools/perf/arch/arm64/util/header.c | 59 +
2 file
Over night I had the following oops on my system (some KVM guests with memory
pressure)
[10752.649057] Unable to handle kernel pointer dereference in virtual kernel
address space
[10752.649062] Failing address: f000 TEID: f803
[10752.649063] Fault in home space mode while
On Mon 15-05-17 16:44:26, Pasha Tatashin wrote:
> On 05/15/2017 03:38 PM, Michal Hocko wrote:
> >I do not think this is the right approach. Your measurements just show
> >that sparc could have a more optimized memset for small sizes. If you
> >keep the same memset only for the parallel initializati
On Tue, Apr 18, 2017 at 04:19:30PM -0500, Tom Lendacky wrote:
> The SMP MP-table is built by UEFI and placed in memory in a decrypted
> state. These tables are accessed using a mix of early_memremap(),
> early_memunmap(), phys_to_virt() and virt_to_phys(). Change all accesses
> to use early_memrema
Compile test your patches.
regards,
dan carpenter
On 16-5-2017 1:13, Luis R. Rodriguez wrote:
> On Fri, May 12, 2017 at 11:02:26PM +0200, Arend Van Spriel wrote:
>> try again.. replacing email address from Michał
>> On 12-5-2017 22:55, Arend Van Spriel wrote:
>>> Let me explain the idea to refresh your memory (and mine). It started
>>> when we wer
On Tue, 16 May 2017 09:45:04 +0200,
Geert Uytterhoeven wrote:
>
> Hi Iwai-san,
>
> On Fri, May 12, 2017 at 10:01 AM, Takashi Iwai wrote:
> >> > But, looking at the tree again, I noticed that ALSA isn't built yet at
> >> > all for m68k. I don't remember why it's disabled.
> >> > Jaroslav, do you
Hi Williamson,
Sorry I am busy on other task, I will look if I can get the dmesg log tomorrow.
My submitted patch is try to disable the possibility of the OS reallocating
resources for VF device in sriov_init(), if VF BAR is empty at BIOS/OS hand-off.
-Collins Cheng
-Original Message-
Since this driver does no detection of hardware, it might be used with
a non-sir port. Escape out if we are spinning.
Signed-off-by: Sean Young
---
drivers/media/rc/sir_ir.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/drivers/media/rc/sir_ir.c b/drivers/media/rc/sir_ir.c
index e12e
On Mon 15-05-17 12:57:15, Joonsoo Kim wrote:
> On Fri, May 12, 2017 at 08:38:15AM +0200, Michal Hocko wrote:
[...]
> > I really do not want to question your "simple test" but page_zonenum is
> > used in many performance sensitive paths and proving it doesn't regress
> > would require testing many d
From: "Gautham R. Shenoy"
On wakeup from a deep stop state which is supposed to lose the
hypervisor state, we don't restore the LPCR to the old value but set
it to a "sane" value via cur_cpu_spec->cpu_restore().
The problem is that the "sane" value doesn't include UPRT and the HR
bits which are
From: "Gautham R. Shenoy"
On Power9 DD1 due to a hardware bug the Power-Saving Level Status
field (PLS) of the PSSCR for a thread waking up from a deep state can
under-report if some other thread in the core is in a shallow stop
state. The scenario in which this can manifest is as follows:
From: "Gautham R. Shenoy"
The lower 8 bits of core_idle_state_ptr tracks the number of non-idle
threads in the core. This is supposed to be initialized to bit-map
corresponding to the threads_per_core. However, currently it is
initialized to PNV_CORE_IDLE_THREAD_BITS (0xFF). This is correct for
P
From: "Gautham R. Shenoy"
On POWER8, in case of
- nap: both timebase and hypervisor state is retained.
- fast-sleep: timebase is lost. But the hypervisor state is retained.
- winkle: timebase and hypervisor state is lost.
Hence, the current code for handling exit from a idle state as
From: Akshay Adiga
Some of the SPR values (HID0, MSR, SPRG0) don't change during the run
time of a booted kernel, once they have been initialized.
The contents of these SPRs are lost when the CPUs enter deep stop
states. So instead saving and restoring SPRs from the kernel, use the
stop-api prov
From: "Gautham R. Shenoy"
Hi,
This patch series contains some of the fixes required for enabling
support for deep stop states such as STOP4 and STOP11 via CPU-Hotplug.
These fixes mainly ensure that some of the hypervisor resources which
are lost during the deep stop state are correctly restore
From: "Gautham R. Shenoy"
The current code in the cpuidle-powernv intialization only allows deep
stop states (indicated by OPAL_PM_STOP_INST_DEEP) which lose timebase
(indicated by OPAL_PM_TIMEBASE_STOP). This assumption goes back to
POWER8 time where deep states used to lose the timebase. Howeve
As the documentation for dwfl_frame_pc says, frames that
are no activation frames need to have their program counter
decremented by one to properly find the function of the caller.
This fixes many cases where perf report currently attributes
the cost to the next line. I.e. I have code like this:
On Dienstag, 16. Mai 2017 03:57:53 CEST Namhyung Kim wrote:
> On Mon, May 15, 2017 at 05:13:06PM +0200, Milian Wolff wrote:
> > On Monday, May 15, 2017 5:04:44 PM CEST Milian Wolff wrote:
> > > As the documentation for dwfl_frame_pc says, frames that
> > > are no activation frames need to have thei
>
> I could see a case being make for CAP_SYS_TTY_CONFIG. However I still
> choose to do with CAP_SYS_ADMIN because it is already in use in the
> TIOCSTI ioctl.
>
Matt Brown don't give me existing behaviour.CAP_SYS_ADMIN is
overload. The documentation tells you that you are not to expand it
a
From: Michal Hocko
drm_malloc* has grown their own kmalloc with vmalloc fallback
implementations. MM has grown kvmalloc* helpers in the meantime. Let's
use those because it a) reduces the code and b) MM has a better idea
how to implement fallbacks (e.g. do not vmalloc before kmalloc is tried
with
So, is there some interest in this? I am not going to push this if there
is a general consensus that we do not need to do anything about the
current situation or need a different approach.
On Tue 07-03-17 16:48:39, Michal Hocko wrote:
> Hi,
> this is a follow up for __GFP_REPEAT clean up merged in
On Tue, May 16, 2017 at 02:00:23PM +0530, srishti wrote:
> Fixed a warning : struct comedi_lrange is generally constant.
>
> Signed-off-by: Srishti Sharma
As Dan pointed out, you _HAVE_ to test-build your changes.
Also, your "From:" line didn't match your signed-off-by line, so I
couldn't accep
On Thu 11-05-17 20:18:13, Roman Gushchin wrote:
> Commit 4b4cea91691d ("mm: vmscan: fix IO/refault regression in
> cache workingset transition") introduced three new entries in memory
> stat file:
> - workingset_refault,
> - workingset_activate,
> - workingset_nodereclaim.
>
> This
This moves the #ifdef in C code to a Kconfig dependency. Also we move the
gigantic_page_supported() function to be arch specific. This gives arch to
conditionally enable runtime allocation of gigantic huge page. Architectures
like ppc64 supports different gigantic huge page size (16G and 1G) based
POWER9 supports hugepages of size 2M and 1G in radix MMU mode. This patch
enables the usage of 1G page size for hugetlbfs. This also update the helper
such we can do 1G page allocation at runtime.
We still don't enable 1G page size on DD1 version. This is to avoid doing
workaround mentioned in com
Em Mon, 15 May 2017 10:09:40 +0200
Cornelia Huck escreveu:
> On Fri, 12 May 2017 11:00:11 -0300
> Mauro Carvalho Chehab wrote:
>
> > Use pandoc to convert documentation to ReST by calling
> > Documentation/sphinx/tmplcvt script.
> >
> > Signed-off-by: Mauro Carvalho Chehab
> > ---
> > Docume
Folowing patch set cleans some warnings and checkups from checkpatch.pl
and also fix code to better fot linux code style.
Changes since v2 [1]:
* staging: sm750fb: unifying macro usage and definitions
* move definition of MHZ macro from c file to header.
[1] https://lkml.org/lkml/2017/5/
This patch removes typedefs from enum and renames it from "typedef enum
_clock_type_t" to "enum clock_type" as per kernel coding standards.
Signed-off-by: Matej Dujava
---
drivers/staging/sm750fb/ddk750_chip.h | 8
drivers/staging/sm750fb/ddk750_mode.c | 2 +-
drivers/staging/sm750fb/dd
This patch breaks lines that are longer than 80 characters and joins
together those, that are too short and can be placed at one.
Function calls and declarations are updated to fit kernel code style.
Signed-off-by: Matej Dujava
---
drivers/staging/sm750fb/ddk750_chip.c | 7 +++--
drivers/sta
This patch removes typedefs from enum and renames it from
"typedef enum _DPMS_t" to "enum DPMS" as per kernel coding standards.
Signed-off-by: Matej Dujava
---
drivers/staging/sm750fb/ddk750_power.c | 2 +-
drivers/staging/sm750fb/ddk750_power.h | 7 +++
2 files changed, 4 insertions(+), 5 d
This patch removes typedefs from enum and renames it from "typedef enum
_sii164_hot_plug_mode_t" to "enum sii164_hot_plug_mode" as per kernel
coding standards.
Signed-off-by: Matej Dujava
---
drivers/staging/sm750fb/ddk750_sii164.c | 2 +-
drivers/staging/sm750fb/ddk750_sii164.h | 4 ++--
2 file
This patch removes typedefs from enum and renames it from "typedef enum
_disp_output_t" to "enum disp_output" as per kernel coding standards.
Signed-off-by: Matej Dujava
---
drivers/staging/sm750fb/ddk750_display.c | 2 +-
drivers/staging/sm750fb/ddk750_display.h | 8
drivers/staging/sm
From: Colin Ian King
Trivial fix to spelling mistake in seq_printf message.
Fixes: a8b9370fc79c1 ("drm/i915/guc: Dump the GuC stage descriptor pool in
debugfs")
Signed-off-by: Colin Ian King
---
drivers/gpu/drm/i915/i915_debugfs.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --
With generic code now handling hugetlb entries at pgd level and also
supporting hugepage directory format, we can now remove the powerpc
sepcific follow_huge_addr implementation.
Signed-off-by: Aneesh Kumar K.V
---
arch/powerpc/mm/hugetlbpage.c | 64 ---
1
Architectures like ppc64 supports hugepage size that is not mapped to any of
of the page table levels. Instead they add an alternate page table entry format
called hugepage directory (hugepd). hugepd indicates that the page table entry
maps
to a set of hugetlb pages. Add support for this in generi
This enable to use the hugepd_t type early. No functional change in this patch.
Signed-off-by: Aneesh Kumar K.V
---
include/linux/hugetlb.h | 47 ---
1 file changed, 24 insertions(+), 23 deletions(-)
diff --git a/include/linux/hugetlb.h b/include/linu
From: Anshuman Khandual
ppc64 supports pgd hugetlb entries. Add code to handle hugetlb pgd entries to
follow_page_mask so that ppc64 can switch to it to handle hugetlbe entries.
Signed-off-by: Anshuman Khandual
Signed-off-by: Aneesh Kumar K.V
---
include/linux/hugetlb.h | 4
mm/gup.c
Signed-off-by: Aneesh Kumar K.V
---
arch/powerpc/mm/hugetlbpage.c | 43 +++
1 file changed, 43 insertions(+)
diff --git a/arch/powerpc/mm/hugetlbpage.c b/arch/powerpc/mm/hugetlbpage.c
index 80f6d2ed551a..5c829a83a4cc 100644
--- a/arch/powerpc/mm/hugetlbpag
Signed-off-by: Aneesh Kumar K.V
---
arch/powerpc/platforms/Kconfig.cputype | 5 +
1 file changed, 5 insertions(+)
diff --git a/arch/powerpc/platforms/Kconfig.cputype
b/arch/powerpc/platforms/Kconfig.cputype
index 8017542d..8acc4f27d101 100644
--- a/arch/powerpc/platforms/Kconfig.cputype
HugeTLB migration support for PPC64
Changes from V1:
* Added Reviewed-by:
* Drop follow_huge_addr from powerpc
Aneesh Kumar K.V (8):
mm/hugetlb/migration: Use set_huge_pte_at instead of set_pte_at
mm/follow_page_mask: Split follow_page_mask to smaller functions.
mm/hugetlb: export hugetlb_e
We will be using this later from the ppc64 code. Change the return type to bool.
Reviewed-by: Naoya Horiguchi
Signed-off-by: Aneesh Kumar K.V
---
include/linux/hugetlb.h | 1 +
mm/hugetlb.c| 8
2 files changed, 5 insertions(+), 4 deletions(-)
diff --git a/include/linux/hug
Makes code reading easy. No functional changes in this patch. In a followup
patch, we will be updating the follow_page_mask to handle hugetlb hugepd format
so that archs like ppc64 can switch to the generic version. This split helps
in doing that nicely.
Reviewed-by: Naoya Horiguchi
Signed-off-by
1 - 100 of 800 matches
Mail list logo
