Re: "special" key when Lenovo Yoga 900 in tablet mode

On Tue, Dec 15, 2015 at 9:27 PM, Nish Aravamudan wrote: > So the Lenovo Yoga 900 has 4 "modes" (laptop, tent, stand and tablet). > In tablet mode, it appears that the following is printed roughly every > second: > > atkbd serio0: Unknown key pressed (translated set 2, code 0xbf on >

Re: [PATCH v3] serial: 8250: add gpio support to exar

On Sun, Dec 20, 2015 at 4:47 PM, Sudip Mukherjee wrote: > On Sun, Dec 20, 2015 at 04:18:17PM +0200, Andy Shevchenko wrote: >> On Sun, Dec 20, 2015 at 3:24 PM, Sudip Mukherjee >> wrote: >> > Exar XR17V352/354/358 chips have 16 multi-purpose inputs/outputs which >> > can be controlled using gpio

Re: [PATCH 08/10] perf tools: Add --raw-trace option

On Wed, Dec 16, 2015 at 12:35:41AM +0900, Namhyung Kim wrote: > The --raw-trace option is to prevent pretty printing by event's > print_fmt or plugin. Besides that, each dynamic sort key now receives > 'raw' suffix separated by '/' to apply the raw trace to a specific > field. > > $ perf

Re: [PATCH 1/1] Fix 'sleeping function called from invalid context' warning in sysrq generated crash.

On Fri, 18 Dec 2015, Paul E. McKenney wrote: > On Thu, Dec 17, 2015 at 05:15:10PM -0800, Ani Sinha wrote: > > Commit 984d74a72076a1 ("sysrq: rcu-ify __handle_sysrq") > > replaced spin_lock_irqsave() calls with > > rcu_read_lock() calls in sysrq. Since rcu_read_lock() does not > > disable

Re: [PATCH v3] serial: 8250: add gpio support to exar

On Sun, Dec 20, 2015 at 04:18:17PM +0200, Andy Shevchenko wrote: > On Sun, Dec 20, 2015 at 3:24 PM, Sudip Mukherjee > wrote: > > Exar XR17V352/354/358 chips have 16 multi-purpose inputs/outputs which > > can be controlled using gpio interface. > > Add support to use these pins and select

Re: [PATCH v1 0/6] Support the rk3036 Kylin board

Hi Caesar, Am Sonntag, 20. Dezember 2015, 20:49:14 schrieb Caesar Wang: > Hi Heiko, > > 在 2015年12月20日 01:16, Heiko Stübner 写道: > > Hi Caesar, > > > > Am Donnerstag, 17. Dezember 2015, 22:21:46 schrieb Caesar Wang: > >> Kylin-board is based on RK3036 SOCs, add the initiation > >> version for

Re: [PATCH v5] extcon: add Maxim MAX3355 driver

Hi, This patch depend on GPIOLIB configuration as following: I modified it with following diff and applied it. diff --git a/drivers/extcon/Kconfig b/drivers/extcon/Kconfig index ba4db7d..3d89e60 100644 --- a/drivers/extcon/Kconfig +++ b/drivers/extcon/Kconfig @@ -54,6 +54,7 @@ config

Re: [PATCH v3] serial: 8250: add gpio support to exar

On Sun, Dec 20, 2015 at 3:24 PM, Sudip Mukherjee wrote: > Exar XR17V352/354/358 chips have 16 multi-purpose inputs/outputs which > can be controlled using gpio interface. > Add support to use these pins and select GPIO_SYSFS also so that these > pins can be used from the userspace through sysfs.

Re: [PATCH 06/10] perf tools: Try to show pretty printed output for dynamic sort keys

On Wed, Dec 16, 2015 at 12:35:39AM +0900, Namhyung Kim wrote: SNIP > struct trace_seq seq; > + char *str, *pos; > + struct format_field *field; > + struct pevent_record rec = { > + .cpu = he->cpu, > + .data = he->raw_data, > + .size =

Re: Aw: Re: [RFC PATCH urcu on mips, parisc] Fix: compat_futex should work-around futex signal-restart kernel bug

- On Dec 19, 2015, at 5:37 AM, Helge Deller del...@gmx.de wrote: > Hi Mathieu, > > On 18.12.2015 21:42, Helge Deller wrote: >> On 18.12.2015 20:58, Mathieu Desnoyers wrote: >> When testing liburcu on a 3.18 Linux kernel, 2-core MIPS (cpu model : >> Ingenic JZRISC V4.15 FPU V0.0), we

[PATCH] ibmveth: consolidate kmalloc of array, memset 0 to kcalloc

This is an API consolidation only. The use of kmalloc + memset to 0 is equivalent to kcalloc in this case as it is allocating an array of elements. Signed-off-by: Nicholas Mc Guire --- Found by coccinelle script (relaxed version of scripts/coccinelle/api/alloc/kzalloc-simple.cocci) Patch was

Re: [PATCH 05/10] perf tools: Add dynamic sort key for tracepoint events

Hi Jiri, On Sun, Dec 20, 2015 at 02:51:32PM +0100, Jiri Olsa wrote: > On Wed, Dec 16, 2015 at 12:35:38AM +0900, Namhyung Kim wrote: > > SNIP > > > + > > + if (!len) > > + len = hde_width(hde); > > + > > + return len; > > +} > > + > > +static int __sort__hde_entry(struct

Re: [PATCH 05/10] perf tools: Add dynamic sort key for tracepoint events

On Wed, Dec 16, 2015 at 12:35:38AM +0900, Namhyung Kim wrote: SNIP > + > + if (!len) > + len = hde_width(hde); > + > + return len; > +} > + > +static int __sort__hde_entry(struct perf_hpp_fmt *fmt, struct perf_hpp *hpp, > + struct hist_entry *he) > +{

Re: [PATCH 1/2] x86/msr: add on cpu read/modify/write function

Jacob, On Fri, 11 Dec 2015, Jacob Pan wrote: > +static inline int rmwmsrl_safe_on_cpu(unsigned int cpu, u32 msr_no, u64 > mask, u64 bits) > +{ > + int err; > + u64 val; > + > + err = rdmsrl_safe(msr_no, ); > + if (err) > + goto out; > + > + val &= ~mask; > +

[PATCH v3] serial: 8250: add gpio support to exar

Exar XR17V352/354/358 chips have 16 multi-purpose inputs/outputs which can be controlled using gpio interface. Add support to use these pins and select GPIO_SYSFS also so that these pins can be used from the userspace through sysfs. Tested-by: Rob Groner Signed-off-by: Sudip Mukherjee --- v3:

[tip:locking/core] futex: Allow FUTEX_CLOCK_REALTIME with FUTEX_WAIT op

Commit-ID: 337f13046ff03717a9e99675284a817527440a49 Gitweb: http://git.kernel.org/tip/337f13046ff03717a9e99675284a817527440a49 Author: Darren Hart AuthorDate: Fri, 18 Dec 2015 13:36:37 -0800 Committer: Thomas Gleixner CommitDate: Sun, 20 Dec 2015 12:43:25 +0100 futex: Allow

[tip:locking/core] futex: Remove pointless put_pi_state calls in requeue()

Commit-ID: 4959f2de11ca532a120a337429e5576fd283700f Gitweb: http://git.kernel.org/tip/4959f2de11ca532a120a337429e5576fd283700f Author: Thomas Gleixner AuthorDate: Sat, 19 Dec 2015 20:07:40 + Committer: Thomas Gleixner CommitDate: Sun, 20 Dec 2015 12:43:25 +0100 futex: Remove

[tip:locking/core] futex: Cleanup the goto confusion in requeue_pi()

Commit-ID: 885c2cb770b5ac2507c41bc9f91a5d1c98337bee Gitweb: http://git.kernel.org/tip/885c2cb770b5ac2507c41bc9f91a5d1c98337bee Author: Thomas Gleixner AuthorDate: Sat, 19 Dec 2015 20:07:41 + Committer: Thomas Gleixner CommitDate: Sun, 20 Dec 2015 12:43:25 +0100 futex: Cleanup the

[tip:locking/core] futex: Document pi_state refcounting in requeue code

Commit-ID: ecb38b78f698a51988ec456751b20440e54702fb Gitweb: http://git.kernel.org/tip/ecb38b78f698a51988ec456751b20440e54702fb Author: Thomas Gleixner AuthorDate: Sat, 19 Dec 2015 20:07:39 + Committer: Thomas Gleixner CommitDate: Sun, 20 Dec 2015 12:43:24 +0100 futex: Document

[tip:locking/core] futex: Drop refcount if requeue_pi() acquired the rtmutex

Commit-ID: fb75a4282d0d9a3c7c44d940582c2d226cf3acfb Gitweb: http://git.kernel.org/tip/fb75a4282d0d9a3c7c44d940582c2d226cf3acfb Author: Thomas Gleixner AuthorDate: Sat, 19 Dec 2015 20:07:38 + Committer: Thomas Gleixner CommitDate: Sun, 20 Dec 2015 12:43:24 +0100 futex: Drop

[tip:locking/core] futex: Rename free_pi_state() to put_pi_state( )

Commit-ID: 29e9ee5d48c35d6cf8afe09bdf03f77125c9ac11 Gitweb: http://git.kernel.org/tip/29e9ee5d48c35d6cf8afe09bdf03f77125c9ac11 Author: Thomas Gleixner AuthorDate: Sat, 19 Dec 2015 20:07:39 + Committer: Thomas Gleixner CommitDate: Sun, 20 Dec 2015 12:43:24 +0100 futex: Rename

Re: [PATCH] posix-clock: Use an unsigned data type for a variable

Reuse the type from this poll call instead. >>> >>> Why use uint when the function return type it unsigned int? >> >> Do you prefer to express the type modifier once more there? > > I don't know what the sentence means, Can it be a matter of taste if the key word "unsigned" should be

[GIT PULL] RTC fixes for 4.4 #2

Hi Linus, Please pull those late fixes for the RTC subsystem for 4.4. The following changes since commit 3abb1ada21a4fb5b2920457a2e5c8483abb09a45: rtc: ds1307: fix alarm reading at probe time (2015-11-26 18:11:26 +0100) are available in the git repository at:

RE: [char-misc-next v2 7/7] watchdog: mei_wdt: re-register device on event

> > > > That breaks the existing behaviour of hot pluggable watchdog interfaces > > > and is different to just about any other device in the kernel. Today with > > > any desktop or server distribution you can already trivially arrange for > > > watchdog daemons to start at the point a watchdog is

Re: Indent issus in kernel module development

I tried it. Not worked unfortunately,. ```bash $ ~/share/linux/scripts/checkpatch.pl --fix --types=spacing testcompletion.c total: 0 errors, 0 warnings, 0 lines checked testcompletion.c has no obvious style problems and is ready for submission. NOTE: Used message types: SPACING ``` 2015-12-19

Re: [PATCH] posix-clock: Use an unsigned data type for a variable

On Sun, 20 Dec 2015, SF Markus Elfring wrote: > >> Reuse the type from this poll call instead. > > > > Why use uint when the function return type it unsigned int? > > Do you prefer to express the type modifier once more there? I don't know what the sentence means, but I think that the type

Re: [PATCH] Input: xpad - use LED API when identifying wireless controllers

2015-12-20 8:55 GMT+01:00 Dmitry Torokhov : > On Sat, Dec 19, 2015 at 10:17:09PM +0100, Clement Calmels wrote: >> On Wed, 16 Dec 2015 14:44:08 -0800 >> Dmitry Torokhov wrote: >> >> > When lighting up the segment identifying wireless controller, Instead >> > of sending command directly to the

Re: [PATCH v1 0/6] Support the rk3036 Kylin board

Hi Heiko, 在 2015年12月20日 01:16, Heiko Stübner 写道: Hi Caesar, Am Donnerstag, 17. Dezember 2015, 22:21:46 schrieb Caesar Wang: Kylin-board is based on RK3036 SOCs, add the initiation version for working. I've applied: - patch1 (please include the "rockchip:" part in dts subjects) - patch3

Re: [PATCH] posix-clock: Use an unsigned data type for a variable

>> Reuse the type from this poll call instead. > > Why use uint when the function return type it unsigned int? Do you prefer to express the type modifier once more there? > On the other hand, why is the function return type unsigned int > when there is a return of a negative constant? This

[PATCH] Drivers: hv: vmbus: fix the building warning with hyperv-keyboard

With the recent change af3ff643ea91ba64dd8d0b1cbed54d44512f96cd (Drivers: hv: vmbus: Use uuid_le type consistently), we always get this warning: CC [M] drivers/input/serio/hyperv-keyboard.o drivers/input/serio/hyperv-keyboard.c:427:2: warning: missing braces around initializer

Re: [PATCH v5 2/2] spi: sun4i: Add support for wait time between word transmissions

Hi, 2015-12-18 12:16 GMT+01:00 Maxime Ripard : >> sun4i_spi_write(sspi, SUN4I_CLK_CTL_REG, reg); >> >> + /* >> + * Setup wait time between words. >> + * >> + * Wait time is set in SPI_CLK cycles. The SPI hardware needs 3 >> + * additional cycles to setup the wait

Re: [PATCH v3 3/7] tpm_tis: Do not fall back to a hardcoded address for TPM2

On Fri, Dec 18, 2015 at 09:51:27AM -0700, Jason Gunthorpe wrote: > On Fri, Dec 18, 2015 at 11:34:32AM +0200, Jarkko Sakkinen wrote: > > > + st = acpi_get_table(ACPI_SIG_TPM2, 1, > > > + (struct acpi_table_header **) ); > > > + if (ACPI_FAILURE(st) || tbl->header.length <

RE: [char-misc-next v2 6/7] watchdog: mei_wdt: register wd device only if required

> > On 12/17/2015 06:49 AM, Tomas Winkler wrote: > > From: Alexander Usyskin > > > > For Intel Broadwell and newer platforms, the ME device can inform > > the host whether the watchdog functionality is activated or not. > > If the watchdog functionality is not activated then the watchdog

firmware_class warnings on resume

I hit this warning fairly frequently when resuming 4.4-rc5: ret = usermodehelper_read_trylock(); if (WARN_ON(ret)) { dev_err(device, "firmware: %s will not be loaded\n", name); goto out; } It seems like it could be improved in two

Re: [PATCH v5] rtc: support DS1302 RTC on ICP DAS LP-8x4x

On Sat, 2015-12-19 at 21:38 -0600, Rob Herring wrote: > On Tue, Dec 15, 2015 at 08:45:23PM +0300, Sergei Ianovich wrote: > > Nothing in this is specific to ICP, so the subject should be updated. > > > Signed-off-by: Sergei Ianovich > > CC: Alexandre Belloni > > --- > >    v4..v5 > >    * drop

Re: [PATCH v3 9/9] phy: omap-usb2: use *syscon* framework API to power on/off the PHY

Hi Rob, On Sunday 20 December 2015 09:09 AM, Rob Herring wrote: > On Tue, Dec 15, 2015 at 02:46:08PM +0530, Kishon Vijay Abraham I wrote: >> Deprecate using phy-omap-control driver to power on/off the PHY, >> and use *syscon* framework to do the same. This handles >> powering on/off the PHY for

RE: [char-misc-next 4/7] watchdog: mei_wdt: add status debugfs entry

> >>> +#if IS_ENABLED(CONFIG_DEBUG_FS) > >>> +static const char *mei_wdt_state_str(enum mei_wdt_state state) > >>> +{ > >>> + switch (state) { > >>> + case MEI_WDT_IDLE: return "IDLE"; > >>> + case MEI_WDT_START: return "START"; > >>> + case MEI_WDT_RUNNING: return "RUNNING"; > >>> + case

Re: [PATCH 3/3] RTC/PCF85063: fix time/date setting

On 07/12/2015 at 14:49:34 +0100, Juergen Borleis wrote : > When setting a new time/date the RTC's clock must be stopped first, in > order to write the time/date registers in an atomic manner. > So, this change stops the clock first and then writes the time/date > registers and the clock control

[tip:x86/apic] x86/irq: Export functions to allow MSI domains in modules

Commit-ID: c8f3e518d3444ee9200a4987421fcee60f768f11 Gitweb: http://git.kernel.org/tip/c8f3e518d3444ee9200a4987421fcee60f768f11 Author: Jake Oshins AuthorDate: Thu, 10 Dec 2015 17:52:59 + Committer: Thomas Gleixner CommitDate: Sun, 20 Dec 2015 12:40:49 +0100 x86/irq: Export

[PATCH v2] iio: add ad5761 DAC driver

ad5761 is a 1-channel DAC with configurable output range. The driver uses the regulator interface for its voltage ref. It shares its register layout with ad5761r, ad5721 and ad5721r. Differences: ad5761* are 16 bit, ad5721* are 12 bits. ad57*1r have an internal reference. --- v2: A lot of

This Is A MIRACLE, I Have Cured My Diabetes, from: Latoya Richards

. Hi, There is a complete natural treatment that treats the r00t cause of diabetes that the medical establishment has been hiding from you all along. A treatment that is 100 percent effective yet totally unknown to your doctor and almost all doctors around the country. Watch our presentaion

Re: [PATCH 2/3] RTC/PCF85063: fix time/date reading (part II)

Hi, On 07/12/2015 at 14:49:33 +0100, Juergen Borleis wrote : > Use the function to read the whole time/date register in one turn and now > check if the RTC signals an invalid time/date (due to a battery power loss > for example). In this case ignore the time/date until it is really set > again. >

[tip:irq/core] genirq/msi: Export functions to allow MSI domains in modules

Commit-ID: a4289dc2ec3a5821076a78ee9678909b4eff297e Gitweb: http://git.kernel.org/tip/a4289dc2ec3a5821076a78ee9678909b4eff297e Author: Jake Oshins AuthorDate: Thu, 10 Dec 2015 17:52:59 + Committer: Thomas Gleixner CommitDate: Sun, 20 Dec 2015 12:26:52 +0100 genirq/msi: Export

[PATCH 1/4] ASoC: imx-pcm-dma: add NULL test

Add NULL test on call to devm_kzalloc. The semantic match that finds this problem is as follows: (http://coccinelle.lip6.fr/) // @@ expression x; @@ * x = devm_kzalloc(...); ... when != x == NULL *x // Signed-off-by: Julia Lawall --- sound/soc/fsl/imx-pcm-dma.c |2 ++ 1 file

[PATCH 2/4] ASoC: omap-hdmi-audio: add NULL test

Add NULL test on call to devm_kzalloc. The semantic match that finds this problem is as follows: (http://coccinelle.lip6.fr/) // @@ expression x; identifier fld; @@ * x = devm_kzalloc(...); ... when != x == NULL x->fld // Signed-off-by: Julia Lawall ---

[PATCH 3/4] s390/cio: add NULL test

Add NULL test on call to kzalloc. The semantic match that finds this problem is as follows: (http://coccinelle.lip6.fr/) // @@ expression x; identifier fld; @@ * x = kzalloc(...); ... when != x == NULL x->fld // Signed-off-by: Julia Lawall --- drivers/s390/char/con3215.c |2 ++ 1

[PATCH 0/4] add NULL test

Add NULL tests on various calls to kzalloc and devm_kzalloc. The semantic match that finds these problems is as follows: (http://coccinelle.lip6.fr/) // @@ expression x,y; identifier fld; @@ ( x = \(vmalloc\|kmalloc\|kzalloc\|kcalloc\|kmem_cache_alloc\|krealloc\| kmemdup\|kstrdup\|

[PATCH 4/4] ASoC: Intel: add NULL test

Add NULL test on call to devm_kzalloc. The semantic match that finds this problem is as follows: (http://coccinelle.lip6.fr/) // @@ expression x; identifier fld; @@ * x = devm_kzalloc(...); ... when != x == NULL x->fld // Signed-off-by: Julia Lawall ---

Re: [PATCH] iio: add ad5761 DAC driver

Hello Peter: Thanks for your review! I agree on all your points but one: On Sat, Dec 19, 2015 at 6:06 PM, Peter Meerwald-Stadler wrote: >> + .info_mask_separate = BIT(IIO_CHAN_INFO_RAW), \ >> + .info_mask_shared_by_type = BIT(IIO_CHAN_INFO_SCALE) | \ >> +

Re: [PATCH v4 1/2] serial: rewrite pxa2xx-uart to use 8250_core

On Sun, 2015-12-20 at 00:12 +0100, Robert Jarzmik wrote: > Sergei Ianovich writes: > > > On Sat, 2015-12-19 at 20:31 +0100, Robert Jarzmik wrote: > > > Sergei Ianovich writes: > > > Thanks for spotting this. This is caused by a change in the latest > > > > version of the patch (SERIAL_8250_PXA

Re: [PATCH] iio: add ad5761 DAC driver

Hello Jonthan Thanks for your comments, I have fixed all the style problems in v2, so we can focus in the range parameter. On Sat, Dec 19, 2015 at 5:31 PM, Jonathan Cameron wrote: > Range isn't actually specified in the ABI docs. > Documenation\ABI\testing\sysfs-bus-iio* > The control interface

Re: [PATCH] posix-clock: Use an unsigned data type for a variable

On Sun, 20 Dec 2015, SF Markus Elfring wrote: > From: Markus Elfring > Date: Sun, 20 Dec 2015 09:09:34 +0100 > > The data type "int" was used by the variable "result" in the > function "posix_clock_poll" even though the type "uint" will usually > be needed for the return value from a call of

[PATCH v2 3/4] x86/vdso: Remove pvclock fixmap machinery

Acked-by: Paolo Bonzini Signed-off-by: Andy Lutomirski --- arch/x86/entry/vdso/vclock_gettime.c | 1 - arch/x86/entry/vdso/vma.c| 1 + arch/x86/include/asm/fixmap.h| 5 - arch/x86/include/asm/pvclock.h | 5 - arch/x86/kernel/kvmclock.c | 6 --

[PATCH v2 4/4] x86/vdso: Enable vdso pvclock access on all vdso variants

Now that pvclock doesn't require access to the fixmap, all vdso variants can use it. The kernel side isn't wired up for 32-bit kernels yet, but this covers 32-bit and x32 userspace on 64-bit kernels. Acked-by: Paolo Bonzini Signed-off-by: Andy Lutomirski ---

[PATCH v2 2/4] x86/vdso: Get pvclock data from the vvar VMA instead of the fixmap

Acked-by: Paolo Bonzini Signed-off-by: Andy Lutomirski --- arch/x86/entry/vdso/vclock_gettime.c | 20 arch/x86/entry/vdso/vdso-layout.lds.S | 3 ++- arch/x86/entry/vdso/vdso2c.c | 3 +++ arch/x86/entry/vdso/vma.c | 13 +

[PATCH v2 1/4] x86, vdso, pvclock: Simplify and speed up the vdso pvclock reader

From: Andy Lutomirski The pvclock vdso code was too abstracted to understand easily and excessively paranoid. Simplify it for a huge speedup. This opens the door for additional simplifications, as the vdso no longer accesses the pvti for any vcpu other than vcpu 0. Before, vclock_gettime

[PATCH v2 0/4] x86: KVM vdso and clock improvements

x86: KVM vdso and clock improvements NB: patch 1 doesn't really belong here, but it makes this a lot easier for me to test. Patch 1, if it's okay at all, should go though the kvm tree. The rest should probably go through tip:x86/vdso once they're reviewed. I'll do a followup to enable vdso

Re: [PATCH v5] mtd: support BB SRAM on ICP DAS LP-8x4x

On Sat, 2015-12-19 at 21:38 -0600, Rob Herring wrote: > On Tue, Dec 15, 2015 at 09:58:53PM +0300, Sergei Ianovich wrote: > > This provides an MTD device driver for 512kB of battery backed up > > SRAM > > on ICPDAS LP-8X4X programmable automation controllers. > > > > SRAM chip is connected via

Re: [char-misc-next 4/7] watchdog: mei_wdt: add status debugfs entry

On 12/20/2015 01:44 AM, Winkler, Tomas wrote: On 12/17/2015 06:49 AM, Tomas Winkler wrote: Add entry for dumping current watchdog internal state Signed-off-by: Tomas Winkler --- drivers/watchdog/mei_wdt.c | 84 ++ 1 file changed, 84

[PATCH] ARM: dts: veyron: enable the tsadc on pinky board

I think the tsadc is fakly hand on pinky board, maybe that's fixed in newest kernel. As the following patch is a example: https://patchwork.kernel.org/patch/7472051/ I don't have meet this issue on pinky board. Let me know if that's still hanging on pinky board. Signed-off-by: Caesar Wang ---

JUST REPLY YES ONLY

Hello My proposal will give us 2 million in seven days reply "YES" for details. Regards, Richard. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: [Propose] Isolate core_pattern in mnt namespace.

Dongsheng Yang writes: > On 12/20/2015 10:37 AM, Al Viro wrote: >> On Sun, Dec 20, 2015 at 10:14:29AM +0800, Dongsheng Yang wrote: >>> On 12/17/2015 07:23 PM, Dongsheng Yang wrote: Hi guys, We are working on making core dump behaviour isolated in container. But the problem

Re: [PATCH] devpts: Sensible /dev/ptmx & force newinstance

"H. Peter Anvin" writes: > Does it matter if it mounts devpts twice? It seems like a waste of a > minuscule amount of memory, and nothing else. It breaks system("mknod /tmp/ptmx c 5 2"); open("/tmp/ptmx"); As it opens a pty in an inaccessible instance of devpts. When previously the instance

RE: [char-misc-next 4/7] watchdog: mei_wdt: add status debugfs entry

> On 12/17/2015 06:49 AM, Tomas Winkler wrote: > > Add entry for dumping current watchdog internal state > > > > Signed-off-by: Tomas Winkler > > --- > > drivers/watchdog/mei_wdt.c | 84 > ++ > > 1 file changed, 84 insertions(+) > > > > diff --git

[PATCH] ASoC: ssm2518: Use a signed return type for ssm2518_lookup_mcs()

From: Markus Elfring Date: Sun, 20 Dec 2015 10:34:25 +0100 The return type "unsigned int" was used by the ssm2518_lookup_mcs() function even though it will eventually return a negative error code. Improve this implementation detail by deletion of the type modifier then. This issue was detected

Re: [PATCH 2/2] x86/mm/pat: Change free_memtype() to free shrinking range

Toshi, On Wed, 9 Dec 2015, Toshi Kani wrote: > diff --git a/arch/x86/mm/pat_rbtree.c b/arch/x86/mm/pat_rbtree.c > index 6393108..d6faef8 100644 > --- a/arch/x86/mm/pat_rbtree.c > +++ b/arch/x86/mm/pat_rbtree.c > @@ -107,7 +112,12 @@ static struct memtype *memtype_rb_exact_match(struct > rb_root

new barrier type for paravirt (was Re: [PATCH] virtio_ring: use smp_store_mb)

On Thu, Dec 17, 2015 at 03:39:10PM +0100, Peter Zijlstra wrote: > On Thu, Dec 17, 2015 at 04:33:44PM +0200, Michael S. Tsirkin wrote: > > On Thu, Dec 17, 2015 at 02:57:26PM +0100, Peter Zijlstra wrote: > > > > > > You could of course go fix that instead of mutilating things into > > > sort-of

Re: [PATCH 1/2] x86/mm/pat: Change untrack_pfn() to handle unmapped vma

Toshi, On Wed, 9 Dec 2015, Toshi Kani wrote: > diff --git a/arch/x86/mm/pat.c b/arch/x86/mm/pat.c > index 188e3e0..f3e391e 100644 > --- a/arch/x86/mm/pat.c > +++ b/arch/x86/mm/pat.c > @@ -966,8 +966,14 @@ int track_pfn_insert(struct vm_area_struct *vma, > pgprot_t *prot, > > /* > *

Re: [PATCH v3 0/5] Fix a trivial typo and support rk3228/rk3399 SoCs for thermal driver.

在 2015年12月18日 04:09, Eduardo Valentin 写道: Hello, On Thu, Dec 03, 2015 at 04:48:38PM +0800, Caesar Wang wrote: This series pacthes to support the next soc for this thermal driver. I don't add the dts thermal data since these SoCs have *_not_* land in this mainline. I believe these SoCs dts

Re: [PATCH v3 7/8] clk: rockchip: fix usbphy-related clocks

Hi, On Saturday 19 December 2015 10:51 PM, Heiko Stübner wrote: > Hi Kishon, > > Am Dienstag, 15. Dezember 2015, 16:22:32 schrieb Kishon Vijay Abraham I: >> On Friday 20 November 2015 02:52 AM, Heiko Stuebner wrote: >>> The otgphy clocks really only drive the phy blocks. These in turn >>>

[PATCH v4 2/5] thermal: rockchip: fix a impossible condition caused by the warning

As the Dan report the smatch check the thermal driver warning: drivers/thermal/rockchip_thermal.c:551 rockchip_configure_from_dt() warn: impossible condition '(thermal->tshut_temp > ((~0 >> 1))) => (s32min-s32max > s32max)' Although The shut_temp read from DT is u32,the temperature is currently

Re: [RESEND GIT PULL 0/9] phy: for 4.4 -rc

On Friday 18 December 2015 10:57 PM, Greg KH wrote: > On Tue, Dec 15, 2015 at 03:34:15PM +0530, Kishon Vijay Abraham I wrote: >> Hi Greg, >> >> Looks like this have not been merged yet. Can you merge it in this >> -rc cycle. Let me know if I have to change something. >> >> Bulk of the changes

CONTACT HIM NOW FOR YOUR ATM CARD DELIVERY

Attention, We have deposited your fund ($7.500`00USD) through UPS department after our finally meeting regarding your ATM CARD, All you will do is to contact UPS director Andy Chalk via E-mail:(chalka...@gmail.com). he will give you direction on how you will be receiving your ATM CARD

[PATCH] posix-clock: Use an unsigned data type for a variable

From: Markus Elfring Date: Sun, 20 Dec 2015 09:09:34 +0100 The data type "int" was used by the variable "result" in the function "posix_clock_poll" even though the type "uint" will usually be needed for the return value from a call of the function which was assigned to the pointer "poll" of the

[PATCH 0/4] clocksource/vt8500: Fix hangs in small delays

From: Roman Volkov vt8500 hangs in nanosleep() function, starting from commit c6eb3f70d4482806dc2d3e1e3c7736f497b1d418, making the system unusable. Per investigation, looks like set_next_event() now receives too small delta and fails with -ETIME. Google group discussion:

[PATCH 3/4] clocksource/vt8500: Use MIN_OSCR_DELTA from PXA

From: Roman Volkov Since vt8500 and PXA timers are identical, use MIN_OSCR_DELTA from PXA, which is bigger than existing value. It is required to determine the minimum delay which hardware can generate. This commit fixes vt8500 breakage in Linux 4.2 introduced by c6eb3f7

Re: IO errors after "block: remove bio_get_nr_vecs()"

On 2015-12-21 04:42, Kent Overstreet wrote: On Mon, Dec 21, 2015 at 04:25:12AM +0500, Artem S. Tashkinov wrote: On 2015-12-20 23:18, Christoph Hellwig wrote: >On Sun, Dec 20, 2015 at 09:51:14AM -0800, Linus Torvalds wrote: >>Kent, Jens, Christoph et al, >> please see this bugzilla: >> >>

Re: [PATCH] ARM: dma-mapping: Just allocate one chunk at a time

Hi Tomasz, On Friday 18 December 2015 15:05:45 Tomasz Figa wrote: > On Fri, Dec 18, 2015 at 7:31 AM, Doug Anderson wrote: > > On Thu, Dec 17, 2015 at 12:30 PM, Douglas Anderson wrote: > >> The __iommu_alloc_buffer() is expected to be called to allocate pretty > >> sizeable buffers. Upon simple

RE: [PATCH v2 2/2] KVM: x86: Add lowest-priority support for vt-d posted-interrupts

> -Original Message- > From: linux-kernel-ow...@vger.kernel.org [mailto:linux-kernel- > ow...@vger.kernel.org] On Behalf Of Yang Zhang > Sent: Monday, December 21, 2015 9:50 AM > To: Wu, Feng ; pbonz...@redhat.com; > rkrc...@redhat.com > Cc: k...@vger.kernel.org;

Re: [PATCH v5] extcon: add Maxim MAX3355 driver

Hi, On 2015년 12월 21일 02:15, Sergei Shtylyov wrote: > Hello. > > On 12/20/2015 05:31 PM, Chanwoo Choi wrote: > >> This patch depend on GPIOLIB configuration as following: >> I modified it with following diff and applied it. >> >> diff --git a/drivers/extcon/Kconfig b/drivers/extcon/Kconfig >>

linux-next: manual merge of the clockevents tree with the tip tree

Hi Daniel, Today's linux-next merge of the clockevents tree got a conflict in: drivers/clocksource/h8300_timer16.c between commit: d33f250af4e6 ("clocksource/drivers/h8300: Use ioread / iowrite") from the tip tree and commit: 1ddca16cc5b3 ("clocksource/drivers/h8300: Use ioread /

Re: IO errors after "block: remove bio_get_nr_vecs()"

On Sun, Dec 20, 2015 at 5:50 PM, Artem S. Tashkinov wrote: > > P.S. I know Linus doesn't condone PAE but I still find it more preferrable > than running a mixed environment with almost zero benefit in regard to > performance and quite obvious performance regressions related to

linux-next: build failure after merge of the pinctrl tree

Hi Linus, After merging the pinctrl tree, today's linux-next build (arm multi_v7_defconfig) failed like this: drivers/pinctrl/bcm/pinctrl-iproc-gpio.c:640:50: warning: 'struct cygnus_gpio' declared inside parameter list static void iproc_gpio_unregister_pinconf(struct cygnus_gpio *chip)

Re: livepatch: reuse module loader code to write relocations

+++ Petr Mladek [17/12/15 16:45 +0100]: On Wed 2015-12-16 00:40:48, Jessica Yu wrote: Turns out the string parsing stuff, even with the help of lib/string.c, doesn't look very pretty. As I'm working on v3, I'm starting to think having klp_write_object_relocations() loop simply through all the

[PATCH 2/4] clocksource/vt8500: Remove the 'loops' variable

From: Roman Volkov The purpose of the 'loops' variable is unclear. vt8500 hardware does not require any protections, in case if these variables intended for preventing infinite loops (identical PXA timer works perfectly without these ones). If the loops count will not be

[PATCH 4/4] clocksource/vt8500: Add register R/W functions

From: Roman Volkov vt8500 timer requires special synchronization for accessing some of its registers. Define special read and write functions to handle this process transparently. To perform a read from the Timer Count register, user must write a one to the Timer Control

Re: [PATCH] regulator: lp8788: constify regulator_ops structures

On 20/12/15 00:43, Julia Lawall wrote: The regulator_ops structures are never modified, so declare them as const. Done with the help of Coccinelle. Signed-off-by: Julia Lawall Acked-by: Milo Kim --- drivers/regulator/lp8788-buck.c |4 ++--

Re: IO errors after "block: remove bio_get_nr_vecs()"

On 2015-12-20 23:41, Linus Torvalds wrote: On Sun, Dec 20, 2015 at 10:18 AM, Christoph Hellwig wrote: Artem, can you re-check the commits around this series again? I would be extremtly surprised if it's really this particular commit and not one just before it causing the problem - it just

[PATCH v1 0/4] um: Add seccomp support

This series add seccomp support to User-mode Linux (i386 and x86_64 subarchitectures) and fix ptrace issues. This apply on v4.4-rc4 and pass all the 48 tests from selftest/seccomp. Regards, Mickaël Mickaël Salaün (4): um: Fix ptrace GETREGS/SETREGS bugs selftests/seccomp: Remove the need

Re: [PATCH v2 2/2] KVM: x86: Add lowest-priority support for vt-d posted-interrupts

On 2015/12/21 9:55, Wu, Feng wrote: -Original Message- From: linux-kernel-ow...@vger.kernel.org [mailto:linux-kernel- ow...@vger.kernel.org] On Behalf Of Yang Zhang Sent: Monday, December 21, 2015 9:50 AM To: Wu, Feng ; pbonz...@redhat.com; rkrc...@redhat.com Cc:

Re: IO errors after "block: remove bio_get_nr_vecs()"

On Mon, Dec 21, 2015 at 9:50 AM, Artem S. Tashkinov wrote: >> BTW, I have posted very similar issue in the link: >> >> http://marc.info/?l=linux-ide=145066119623811=2 >> >> Artem, I noticed from bugzillar that the hardware is i386, just >> wondering if PAE is enabled? If yes,

Re: [PATCH v7 4/4] gicv2m: acpi: Introducing GICv2m ACPI support

On Thursday, December 10, 2015 08:55:30 AM Suravee Suthikulpanit wrote: > This patch introduces gicv2m_acpi_init(), which uses information > in MADT GIC MSI frames structure to initialize GICv2m driver. > It also exposes gicv2m_init() function, which simplifies callers > to a single GICv2m init

[RFC] theoretical race between memory hotplug and pfn iterator

Hello, memory-hotplug folks. I found theoretical problems between memory hotplug and pfn iterator. For example, pfn iterator works something like below. for (pfn = zone_start_pfn; pfn < zone_end_pfn; pfn++) { if (!pfn_valid(pfn)) continue; page =

Re: IO errors after "block: remove bio_get_nr_vecs()"

On 2015-12-21 08:21, Ming Lei wrote: On Mon, Dec 21, 2015 at 10:25 AM, Artem S. Tashkinov wrote: # cat /sys/block/sda/queue/{max_hw_sectors_kb,max_sectors_kb,max_segments,max_segment_size} 32767 32767 168 65536 Looks it is fine, then maybe it is related with BIOVEC_PHYS_MERGEABLE(),

Re: IO errors after "block: remove bio_get_nr_vecs()"

On Sun, Dec 20, 2015 at 8:26 PM, Tejun Heo wrote: > > I wonder whether ahci is screwing up command / sg table setup in a way > that e.g. if there are too many segments the sg table overflows into > the neighboring one which is now being exposed by upper layer being > fixed to

[PATCH] kexec: Move some memembers and definitions within the scope of CONFIG_KEXEC_FILE

Move the stuff currently only used by the kexec file code within CONFIG_KEXEC_FILE (and CONFIG_KEXEC_VERIFY_SIG). Also move internal "struct kexec_sha_region" and "struct kexec_buf" into "kexec_internal.h". Signed-off-by: Xunlei Pang --- arch/x86/kernel/machine_kexec_64.c |

WANTED new maintainer for Linux/md (and mdadm)

hi, I became maintainer for md (Linux Software RAID) in late 2001 and on the whole it has been fun and a valuable experience. But I have been losing interest in recent years (https://lwn.net/Articles/511073/) and as was mentioned at the kernel summit, I would like to resign. Some years ago

Re: IO errors after "block: remove bio_get_nr_vecs()"

Artem, can you please reproduce the issue with the following patch applied and attach the kernel log? Thanks. --- drivers/ata/libahci.c | 40 ++-- drivers/ata/libata-eh.c |4 drivers/ata/libata-scsi.c |1 + 3 files changed, 43

Re: [Propose] Isolate core_pattern in mnt namespace.

On 2015/12/20 18:47, Eric W. Biederman wrote: > Dongsheng Yang writes: > >> On 12/20/2015 10:37 AM, Al Viro wrote: >>> On Sun, Dec 20, 2015 at 10:14:29AM +0800, Dongsheng Yang wrote: On 12/17/2015 07:23 PM, Dongsheng Yang wrote: > Hi guys, > We are

Re: [PATCH v3 5/5] hisilicon/dts: Add hi655x pmic dts node

Mark, On 2015/12/19 1:58, Mark Brown wrote: > On Thu, Dec 17, 2015 at 11:27:27AM +0800, chenfeng wrote: > >> +- regulator-vset-regs: Voltage set register offset. >> +- regulator-vset-mask: voltage set control mask. >> +- regulator-n-vol: The num of support voltages. >> +-

<    1   2   3   4   5   6   >