On Mon, Aug 31, 2015 at 02:51:08PM +0800, Qu Wenruo wrote:
>
>
> Alexandru Moise wrote on 2015/08/31 09:32 +0300:
> >On Mon, Aug 31, 2015 at 09:44:49AM +0800, Qu Wenruo wrote:
> >From the perspective of users, qgroup's referenced or exclusive
> is negative,but user can not continu
Powerpc provides hcall events that also provides insights into guest
behaviour. Enhance perf kvm to record and analyze hcall events.
- To trace hcall events :
perf kvm stat record
- To show the results :
perf kvm stat report --event=hcall
The result shows the number of hypervisor calls fro
perf kvm can be used to analyze guest exit reasons. This support already
exists in x86. Hence, porting it to powerpc.
- To trace KVM events :
perf kvm stat record
If many guests are running, we can track for a specific guest by using
--pid as in : perf kvm stat record --pid
- To see the
This patch removes the "const" qualifier from kvm_events_tp declaration
to account for the fact that powerpc will need to update this variable
dynamically depending on the machine type.
Signed-off-by: Hemant Kumar
---
tools/perf/arch/s390/util/kvm-stat.c | 2 +-
tools/perf/arch/x86/util/kvm-stat
On Thu, 2015-08-27 at 13:56 -0400, Mathieu Desnoyers wrote:
> Allow it to be used from SPU, since it should not have unwanted
> side-effects.
>
> [ Untested on this architecture. To try it out: fetch linux-next/akpm,
> apply this patch, build/run a membarrier-enabled kernel, and do make
> ksel
On Fri, 2015-07-10 at 16:58 -0400, Mathieu Desnoyers wrote:
> From: Pranith Kumar
>
> This patch adds a self test for the membarrier system call.
>
> CC: Michael Ellerman
Sorry I only just saw this due to some over zealous filtering on my end.
> diff --git a/tools/testing/selftests/membarrie
Alexandru Moise wrote on 2015/08/31 09:32 +0300:
On Mon, Aug 31, 2015 at 09:44:49AM +0800, Qu Wenruo wrote:
>From the perspective of users, qgroup's referenced or exclusive
is negative,but user can not continue to write data! a workaround
way is to cast u64 to s64 when doing qgroup
On Mon, Aug 31, 2015 at 8:40 AM, Stephen Rothwell wrote:
> After merging the gpio tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/gpio/gpio-etraxfs.c: In function 'etraxfs_gpio_irq_request_resources':
> drivers/gpio/gpio-etraxfs.c:300:2: error: 'ret' undeclare
To analyze the exit events with perf, we need to export the related
tracepoints through kvm_perf.h. kvm_perf.h is to be added in the
arch/powerpc directory, where the kvm tracepoints needed to trace the
KVM exit events are defined.
To indicate that the tracepoints are book3s_hv specific, suffix _H
To analyze the hcalls with perf kvm stat, we need the hcall related
tracepoint information to be exported.
This patch adds hcall tracepoints "kvm_hv:kvm_hcall_enter" and
"kvm_hv:kvm_hcall_exit" to kvm_perf.h. So, perf will now know to look
for these tracepoints if "perf kvm stat record" is invoked
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I'm announcing the release of the 3.12.47 kernel.
All users of the 3.12 kernel series must upgrade.
The updated 3.12.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-3.12.y
and can be
Hi Linus,
After merging the gpio tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/gpio/gpio-etraxfs.c: In function 'etraxfs_gpio_irq_request_resources':
drivers/gpio/gpio-etraxfs.c:300:2: error: 'ret' undeclared (first use in this
function)
ret = gpiochip_lock_as_
On Mon, Aug 31, 2015 at 09:44:49AM +0800, Qu Wenruo wrote:
> >>>From the perspective of users, qgroup's referenced or exclusive
> >>is negative,but user can not continue to write data! a workaround
> >>way is to cast u64 to s64 when doing qgroup reservation
> >
> >I am unable to reprodu
This patch adds following attributes to watchdog device's sysfs interface.
* state - reads whether device is active or not
* identity - reads Watchdog device's identity string.
* timeout - reads current timeout.
* timeleft - reads timeleft before watchdog generates a reset
* bootstatus - reads sta
The following changes since commit
d770e558e21961ad6cfdf0ff7df0eb5d7d4f0754:
Linux 4.2-rc1 (2015-07-05 11:01:52 -0700)
are available in the git repository at:
git://git.lwn.net/linux-2.6.git tags/docs-for-linus
for you to fetch changes up to ce14c5831364118324b10c0355dead062b9ddd40:
Docu
On Thu, Aug 27, 2015 at 12:37:00AM +, Kuninori Morimoto wrote:
> From: Nobuhiro Iwamatsu
>
> The reg variable used when setting PCIECAR register need to be masked by 0xFC
> by restriction of the corresponding register.
> This adds PCIE_CONF_REGNO are macros for masking changes that PCIE_CONF_
Hello Linus,
could you please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/jack/linux-fs.git for_linus
The biggest change in the pull is the removal of ext3 filesystem driver
(~28k lines removed). Ext4 driver is a full featured replacement these
days and both RH and SUSE use it f
Presumably because gcc can't generate bt... whether or not it is worth it is
another matter.
On August 30, 2015 11:05:49 PM PDT, Ingo Molnar wrote:
>
>* Michael S. Tsirkin wrote:
>
>> +static __always_inline int __constant_test_bit(long nr, const
>unsigned long *addr)
>> +{
>> +return ((1UL
On 2015년 08월 29일 02:32, Casey Schaufler wrote:
> On 8/26/2015 6:58 PM, Jonghwa Lee wrote:
>> Current Smack object's label is always given by userspace.
>> So there might be a certain gap between the time of file creation
>> and the time of applying actual label. And because of the time gap,
>> it r
* Michael S. Tsirkin wrote:
> +static __always_inline int __constant_test_bit(long nr, const unsigned long
> *addr)
> +{
> + return ((1UL << (nr & (BITS_PER_LONG-1))) &
> + (addr[nr >> _BITOPS_LONG_SHIFT])) != 0;
> +}
> +
> +static inline int __variable_test_bit(long nr, const u
* Oleg Nesterov wrote:
> On 08/29, Ingo Molnar wrote:
> >
> > So I'm wondering, is there any strong reason why we couldn't use a double
> > linked
> > list and still do FIFO and remove that silly linear list walking hack?
>
> This will obviously enlarge callback_head, and it is often embedded.
From: Changsheng Liu
After the user config CONFIG_MOVABLE_NODE and movable_node kernel option,
When the memory is hot added, should_add_memory_movable() return 0
because all zones including movable zone are empty,
so the memory that was hot added will be added to the normal zone
and the normal z
On Fri, Aug 28, 2015 at 03:39:43PM +0100, Lorenzo Pieralisi wrote:
> Hi Dennis,
>
> You should CC linux-...@vger.kernel.org and the PCI subsystem
> maintainer next time.
>
>
Good reminder! Thanks, mate ;-)
> On Fri, Aug 28, 2015 at 01:49:23PM +0100, Dennis Chen wrote:
> > This patch will fall b
Hi,
On Saturday 29 August 2015 12:33 AM, Tony Lindgren wrote:
> * Olof Johansson [150828 11:11]:
>> Hi,
>>
>> On Thu, Aug 27, 2015 at 2:13 AM, Kishon Vijay Abraham I
>> wrote:
>>> Now return error only if the return value of
>>> devm_regulator_get_optional() is not the same as -ENODEV, since wi
On Tue, Aug 18, 2015 at 8:56 PM, Vaishali Thakkar
wrote:
> Revert the problematic part of commit 470805eb9f31 ("ASoC: tegra:
> Convert to managed resources"). Before this commit, PM cleanup was
> performed after the component was unregistered. But returning
> directly will skip PM cleanup. So, to
> On Aug 30, 2015, at 01:08, Linus Torvalds
> wrote:
>
> On Sat, Aug 29, 2015 at 7:11 AM, Eric Dumazet wrote:
>>
>> If this needs to be kept, maybe then add following, to make sure
>> we flush the list at most every BITS_PER_LONG files
>
> Hmm.
>
> I'm wondering if we should just make close
Switch update interrupt mask bit with regmap_update_bits, and clear
interrupt status by writing 1 to relevant bit before setting mask in
fsl_dcu_drm_irq_init function.
Signed-off-by: Jianwei Wang
---
drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_drv.c | 26 +++---
1 file changed, 7 ins
Hi Mark,
Yes, this patch solved the issue.It avoid the null function and just
need to handle the native endian case.
Thanks.
Henry
On Fri, 2015-08-28 at 20:11 +0100, Mark Brown wrote:
> When doing a bulk read from a device which lacks raw I/O support we fall
> back to doing register at a time re
On Tue, Aug 25, 2015 at 5:38 PM, Grygorii Strashko
wrote:
> On 08/24/2015 03:05 PM, Peng Fan wrote:
>>
>> Use devm_* API to simplify driver code.
>>
>> Signed-off-by: Peng Fan
>> Cc: Linus Walleij
>> Cc: Alexandre Courbot
>
> ---
>>
>> drivers/gpio/gpiolib.c | 11 +--
>> 1 file chan
From: Aleksey Makarov
Date: Sun, 30 Aug 2015 12:29:08 +0300
> v2:
> - The unused affinity_mask field of the structure cmp_queue
> has been deleted. (thanks to David Miller)
> - The unneeded initializers have been dropped. (thanks to Alexey Klimov)
> - The commit message "net: thunderx: R
On Tue, Aug 18, 2015 at 4:34 AM, Bjorn Andersson
wrote:
> On Sun 16 Aug 23:59 PDT 2015, Alexandre Courbot wrote:
>
>> On Thu, Aug 13, 2015 at 10:06 PM, Linus Walleij
>> wrote:
>> > On Tue, Aug 11, 2015 at 12:41 AM, Bjorn Andersson
>> > wrote:
>> >
>> >> But then the question first goes to Linus
>From 08df419517694c4dd9ff328f5644b46a99c2999e Mon Sep 17 00:00:00 2001
From: "Du, Changbin"
Date: Thu, 23 Jul 2015 20:08:04 +0800
Subject: [PATCH v2] usb/gadget: make composite gadget meet usb compliance for
vbus draw
USB-IF compliance requirement limits the vbus current according to
current st
From: Raghavendra K T
Date: Sun, 30 Aug 2015 11:29:40 +0530
> While creating 1000 containers, perf is showing lot of time spent in
> snmp_fold_field on a large cpu system.
>
> The current patch tries to improve by reordering the statistics gathering.
...
Series applied, thanks.
--
To unsubscri
On 08/30/2015 09:16 PM, Huang Rui wrote:
On Fri, Aug 28, 2015 at 07:05:13AM -0700, Guenter Roeck wrote:
On 08/28/2015 03:45 AM, Huang Rui wrote:
On Thu, Aug 27, 2015 at 10:30:43AM -0700, Guenter Roeck wrote:
On Thu, Aug 27, 2015 at 04:07:43PM +0800, Huang Rui wrote:
This patch introduces an a
Commit 3adeb2566b9b ("MIPS: Loongson: Improve LEFI firmware interface")
made the number of UARTs dynamic if LEFI_FIRMWARE_INTERFACE is configured.
Unfortunately, it did not initialize the number of UARTs if
LEFI_FIRMWARE_INTERFACE is not configured. As a result, the Fulong2e
system has no console.
On Fri, Aug 28, 2015 at 07:05:13AM -0700, Guenter Roeck wrote:
> On 08/28/2015 03:45 AM, Huang Rui wrote:
> >On Thu, Aug 27, 2015 at 10:30:43AM -0700, Guenter Roeck wrote:
> >>On Thu, Aug 27, 2015 at 04:07:43PM +0800, Huang Rui wrote:
> >>>This patch introduces an algorithm that computes the averag
On Tue, 2015-08-18 at 12:31 +0530, naresh.kamb...@linaro.org wrote:
> From: Naresh Kamboju
>
> diff --git a/tools/testing/selftests/zram/Makefile
> b/tools/testing/selftests/zram/Makefile
> new file mode 100644
> index 000..ec45513
> --- /dev/null
> +++ b/tools/testing/selftests/zram/Makefil
For state->fb may be NULL in fsl_dcu_drm_plane_atomic_check function,
if so, return -EINVAL. No need check in fsl_dcu_drm_plane_atomic_update
anymore.
Signed-off-by: Jianwei Wang
---
drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_plane.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --g
Add Hardkernel Odroid XU4 board Device Tree sources. The board differs
from Odroid XU3 and XU3-Lite by:
1. No green and red leds (except standard red power led).
2. No audio codec.
3. Two USB3 ports in host mode (no micro USB3 connector for OTG).
4. Realtek RTL8153-CG gigabit network adapter (inste
On Wed, Aug 26, 2015 at 10:27:44AM -0500, Nathan Sullivan wrote:
> The Xilinx Zynq udc does not need the CI_HDRC_DISABLE_STREAMING flag,
> unlike the default platform data. Add platform data specific to the
> Zynq udc.
>
You may add the possible reason, eg, tx buffer is not enough.
Others are o
On Mon, Aug 31, 2015 at 09:01:51AM +0530, punnaiah choudary kalluri wrote:
> On Mon, Aug 31, 2015 at 6:10 AM, Peter Chen wrote:
> > On Fri, Aug 28, 2015 at 09:42:56AM -0500, Nathan Sullivan wrote:
> >> On Fri, Aug 28, 2015 at 09:30:12AM +0800, Peter Chen wrote:
> >> > On Thu, Aug 27, 2015 at 09:33
On Tue, Aug 25, 2015 at 12:16 PM, punnaiah choudary kalluri
wrote:
> Hi Rob,
>
> On Tue, Aug 25, 2015 at 12:23 AM, Rob Herring wrote:
>> On Wed, Aug 5, 2015 at 10:19 PM, Punnaiah Choudary Kalluri
>> wrote:
>>> Device-tree binding documentation for Xilinx zynqmp dma engine used in
>>> Zynq UltraS
From: Xunlei Pang
Since we are using cpuidle_driver::safe_state_index directly as the
target state index, it is better to add the sanity check at the point
of registering the driver.
Signed-off-by: Xunlei Pang
---
v2->v3:
Move the code to a new cpuidle_coupled_state_verify() depending on
CONFI
On Mon, Aug 31, 2015 at 6:10 AM, Peter Chen wrote:
> On Fri, Aug 28, 2015 at 09:42:56AM -0500, Nathan Sullivan wrote:
>> On Fri, Aug 28, 2015 at 09:30:12AM +0800, Peter Chen wrote:
>> > On Thu, Aug 27, 2015 at 09:33:07AM -0500, Nathan Sullivan wrote:
>> > > On Thu, Aug 27, 2015 at 01:11:30PM +0530
On Fri, 2015-08-14 at 21:43 +0800, Bamvor Jian Zhang wrote:
> Signed-off-by: Bamvor Jian Zhang
> ---
> tools/testing/selftests/vm/Makefile | 12
> 1 file changed, 12 insertions(+)
>
> diff --git a/tools/testing/selftests/vm/Makefile
> b/tools/testing/selftests/vm/Makefile
> index b
Hi Jiri,
Today's linux-next merge of the trivial tree got a conflict in:
drivers/gpu/drm/nouveau/nvkm/engine/gr/nv10.c
between commit:
109c2f2f1c42 ("drm/nouveau/gr: switch to subdev printk macros")
from the drm tree and commit:
4bb138a47b7f ("drm/nouveau/gr: Fix typo in nv10.c")
from
On 08/26/2015 01:10 PM, Jason Wang wrote:
> On 08/25/2015 07:51 PM, Michael S. Tsirkin wrote:
>> > On Tue, Aug 25, 2015 at 05:05:47PM +0800, Jason Wang wrote:
>> > We register wildcard mmio eventfd on two buses, one for KVM_MMIO_BUS
>> > and another is KVM_FAST_MMIO_BUS. This leads to i
On 29/08/2015:09:51:24 AM, Guenter Roeck wrote:
> > * timeout - reads current timeout and writes to program a new timeout.
Now, this is the only file which has write permission. I hope, that is fine. Pl
let me know if you expected this to be as RO as well.
~Pratyush
--
To unsubscribe from this li
On 08/30/2015 05:12 PM, Michael S. Tsirkin wrote:
Even when we skip data decoding, MMIO is slightly slower
than port IO because it uses the page-tables, so the CPU
must do a pagewalk on each access.
This overhead is normally masked by using the TLB cache:
but not so for KVM MMIO, where PTEs ar
On Sun, Aug 30, 2015 at 2:18 PM, Brian Gerst wrote:
> On Sat, Aug 29, 2015 at 12:10 PM, Andy Lutomirski wrote:
>> On Sat, Aug 29, 2015 at 8:20 AM, Brian Gerst wrote:
>>> This patch set contains several cleanups to the 32-bit VDSO. The
>>> main change is to only build one VDSO image, and select
On 08/28/2015 08:25 PM, Vlad Yasevich wrote:
> On 08/27/2015 10:42 PM, Jason Wang wrote:
>> >
>> >
>> > On 08/27/2015 06:43 PM, Michael S. Tsirkin wrote:
>>> >> On Wed, Aug 26, 2015 at 01:45:30PM +0800, Jason Wang wrote:
>>>
>>> On 08/26/2015 12:32 AM, Vlad Yasevich wrote:
>
Hi Romain,
在 08/30/2015 08:16 PM, Romain Perier 写道:
Hi,
Could you rebase your serie onto linux-next or 4.2-rc8 ? it does not
apply here...
Thanks for try to applied, and feel sorry for that failed.
This v3 series was rebased on github.com/torvalds/linux.git, so I should
rebase on kernel/next
This is from https://bugzilla.redhat.com/show_bug.cgi?id=1258223
[0.036000] BUG: unable to handle kernel paging request at 55501e06
[0.036000] IP: [] common_interrupt+0xb/0x38
[0.036000] *pde =
[0.036000] Oops: [#1] SMP
[0.036000] Modules linked in:
[0.03600
On Fri, Aug 28, 2015 at 05:20:20PM -0700, Ray Jui wrote:
>
>
> On 8/28/2015 4:47 PM, Jon Mason wrote:
> > Add a very minimalistic set of Northstar Plus Device Tree files which
> > describes the SoC and the BCM958625 implementation. The perpherials
> > described are:
> >
> > ARM Cortex A9 CPU
>
> [...]
>
Hi, ulf
We find this bug on Intel-C3230RK platform for very small probability.
Whereas I can easily reproduce this case if I add a mdelay(1) or
longer delay as Jialing did.
This patch seems useful to me. Should we push it forward? :)
>>>
>>>
>>> It
On Fri, Aug 28, 2015 at 09:42:56AM -0500, Nathan Sullivan wrote:
> On Fri, Aug 28, 2015 at 09:30:12AM +0800, Peter Chen wrote:
> > On Thu, Aug 27, 2015 at 09:33:07AM -0500, Nathan Sullivan wrote:
> > > On Thu, Aug 27, 2015 at 01:11:30PM +0530, punnaiah choudary kalluri wrote:
> > > > Hi,
> > > >
>
When driver get exception ic type (0xFF), maybe occurred from wrong
I2C protocol communication, system crash or other unknown situation,
we need to reset ic type from iap_version.
---
drivers/input/mouse/elan_i2c_core.c | 14 +-
1 file changed, 9 insertions(+), 5 deletions(-)
diff -
Alexandru Moise wrote on 2015/08/29 11:45 +:
This patch reverts commit: b4fcd6be6bbd702ae1a6545c9b413681850a9814
Wang Shilong added those casts as a workaround for a bug reproduced
using the following steps:
Steps to reproduce:
mkfs.btrfs
mount
dd if=/dev/zero o
"Frank Ch. Eigler" writes:
> Hi, Rusty -
>
> We just [1] came across your patch [2] from last year (merged into
> 3.17), wherein the RO/NX mapping settings for module sections were
> moved to an earlier point in the module-loading sequence.
>
> That patch also moved the MODULE_STATE_COMING notifie
On (08/27/15 16:59), Kirill A. Shutemov wrote:
> We are going to rework how compound_head() work. It will not use
> page->first_page as we have it now.
>
> The only other user of page->first_page beyond compound pages is
> zsmalloc.
>
> Let's use page->private instead of page->first_page here. It
On Sat, Aug 29, 2015 at 09:33:54AM -0700, Guenter Roeck wrote:
> On Thu, Aug 27, 2015 at 04:07:46PM +0800, Huang Rui wrote:
> > Andreas Herrmann won't take the maintainer of fam15h_power driver. I
> > will take it and appreciate him for the great contributions on this
> > driver.
> >
> > Signed-of
Hi Oleg,
On Sat, Aug 29, 2015 at 04:27:07PM +0200, Oleg Nesterov wrote:
> Hello Boqun,
>
...
> > By this, I think you actually means the example below the added text,
> > i.e. the example for "to repeat..", right?
>
> And above. Even
>
> The barrier occurs before the task state is cleared
Juergen Gross writes:
> Ping?
Acked-by: Rusty Russell
Cheers,
Rusty.
> On 08/06/2015 01:55 PM, Juergen Gross wrote:
>> Remove the paravirt operation "get_tsc_khz" as it is used nowhere.
>>
>> Signed-off-by: Juergen Gross
>> ---
>> arch/x86/include/asm/paravirt_types.h | 1 -
>> 1 file chan
Hi, Rusty -
We just [1] came across your patch [2] from last year (merged into
3.17), wherein the RO/NX mapping settings for module sections were
moved to an earlier point in the module-loading sequence.
That patch also moved the MODULE_STATE_COMING notifier call to
complete_formation(), which is
Hi Linus,
On Fri, 21 Aug 2015 09:57:33 +1000 Stephen Rothwell
wrote:
>
> On Thu, 20 Aug 2015 12:11:21 -0700 Greg KH wrote:
> >
> > All have been in linux-next with no reported issues.
>
> Except see below.
>
> > Eduardo Valentin (4):
> > serial: imx: introduce serial_imx_enable_wakeup()
These drivers already have an I2C device id table that is used to create
module aliases and the used MODULE_ALIAS() was either already in the I2C
table so it was redundant or wasn't a valid I2C id so it was never used.
Signed-off-by: Javier Martinez Canillas
---
drivers/power/bq24190_charger.c
The driver has a I2C device id table that is used to create the module
aliases which already contains a "rt5033". So the alias is not needed.
Signed-off-by: Javier Martinez Canillas
---
drivers/mfd/rt5033.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/mfd/rt5033.c b/drivers/mfd/r
The driver has a I2C device id table that is used to create the module
aliases and also "bcm590xx" isn't a supported I2C id, so it's never used.
Signed-off-by: Javier Martinez Canillas
---
drivers/mfd/bcm590xx.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/mfd/bcm590xx.c b/driver
On Sun, Aug 30, 2015 at 11:05:23PM +0200, Geert Uytterhoeven wrote:
> Below is the list of build error/warning regressions/improvements in
> v4.2[1] compared to v4.1[2].
>
> Summarized:
> - build errors: +8/-53
> - build warnings: +127/-265
>
> JFYI, when comparing v4.2[1] to v4.2-rc8[3], the
Hi Linus,
Please pull hwmon updates for Linux v4.3 from signed tag:
git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git
hwmon-for-linus-v4.3
Thanks,
Guenter
--
The following changes since commit f7644cbfcdf03528f0f450f3940c4985b2291f49:
Linux 4.2-rc6 (2015-08-09 1
reg-init implementation is borowerd from
broadcom,c45-reg-init and marvell,reg-init.
Signed-off-by: Constantine Shulyupin
---
---
.../devicetree/bindings/hwmon/nct7802.txt | 27 ++
1 file changed, 27 insertions(+)
create mode 100644 Documentation/devicetree/bindings
The driver has a I2C device id table that is used to create the module
aliases and also "ad_dpot" isn't a supported I2C id, so it's never used.
Signed-off-by: Javier Martinez Canillas
---
drivers/misc/ad525x_dpot-i2c.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/misc/ad525x_dpot
The driver has a I2C device id table that is used to create the module
aliases and also "sx150x" isn't a supported I2C id, so it's never used.
Signed-off-by: Javier Martinez Canillas
---
drivers/gpio/gpio-sx150x.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/gpio/gpio-sx150x.c b/
The driver has a I2C device id table that is used to create the modaliases
which already contains "synaptics_rmi4_ts". So the alias is not needed.
Signed-off-by: Javier Martinez Canillas
---
drivers/staging/ste_rmi4/synaptics_i2c_rmi4.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/driver
I've lost track of what's up and down in this, but now that I look at
this again let me throw in my two observations of stupid gcc behaviour:
For the current code, both debian's gcc (4.7) and 5.1 partially inlines
_find_next_bit, namely the "if (!nbits || start >= nbits)" test. I know it
does it to
Hi Yoshinori,
The h8300 tree today has been based on linux-next. This cannto work.
Please rebase this onto Linus' tree (or some other stable base).
I cannot use your tree in this state, so it will be dropped from
linux-next until it is fixed. Also, Linus cannot pull it in this state.
--
Cheer
The driver has a I2C device id table that is used to create the modaliases
and also "sc16is7xx" is not a supported I2C id, so it's never used.
Signed-off-by: Javier Martinez Canillas
---
drivers/tty/serial/sc16is7xx.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/tty/serial/sc16is
The driver has a I2C device id table that is used to create the modaliases
and also "adp8860-backlight" is not a supported I2C id, so it's never used.
Signed-off-by: Javier Martinez Canillas
---
drivers/video/backlight/adp8860_bl.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/vid
The driver has a I2C device id table that is used to create the modaliases
and also "adp8870-backlight" is not a supported I2C id, so it's never used.
Signed-off-by: Javier Martinez Canillas
---
drivers/video/backlight/adp8870_bl.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/vid
On Thu, 2015-27-08 at 09:50:19 UTC, Ian Munsie wrote:
> From: Ian Munsie
>
> The cxl user api uses the address_space associated with the file when we
> need to force unmap all cxl mmap regions (e.g. on eeh, driver detach,
> etc). Currently, contexts allocated through the kernel api do not do
> th
On Thu, 2015-27-08 at 09:50:18 UTC, Ian Munsie wrote:
> From: Ian Munsie
>
> If the cxl_context_alloc() call fails, we return immediately without
> releasing the reference on the AFU device, allowing it to leak.
>
> This patch switches to using goto style error handling so that the
> device is r
On Sat, Aug 29, 2015 at 12:10 PM, Andy Lutomirski wrote:
> On Sat, Aug 29, 2015 at 8:20 AM, Brian Gerst wrote:
>> This patch set contains several cleanups to the 32-bit VDSO. The
>> main change is to only build one VDSO image, and select the syscall
>> entry point at runtime.
>
> Oh no, we have
On Sun, Aug 30, 2015 at 11:05 PM, Geert Uytterhoeven
wrote:
> JFYI, when comparing v4.2[1] to v4.2-rc8[3], the summaries are:
> - build errors: +0/-3
Nice!
> [1] http://kisskb.ellerman.id.au/kisskb/head/9309/ (all 254 configs)
> [3] http://kisskb.ellerman.id.au/kisskb/head/9289/ (252 out of 25
Below is the list of build error/warning regressions/improvements in
v4.2[1] compared to v4.1[2].
Summarized:
- build errors: +8/-53
- build warnings: +127/-265
JFYI, when comparing v4.2[1] to v4.2-rc8[3], the summaries are:
- build errors: +0/-3
- build warnings: +27/-30
Note that there
Hi Linus,
The following changes since commit d770e558e21961ad6cfdf0ff7df0eb5d7d4f0754:
Linux 4.2-rc1 (2015-07-05 11:01:52 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/geert/linux-m68k.git for-linus
for you to fetch changes up to 1ecb4
The original version only considered the case where the then branch
contains only one call to PTR_ERR. Reimplement the whole thing to allow
multiple calls, with potentially different arguments.
Signed-off-by: Julia Lawall
---
scripts/coccinelle/tests/odd_ptr_err.cocci | 120 ++
Move initialization of msg->status up over the call to dev_err, in both
calls to ep93xx_spi_dma_prepare, and change the reference in the call to
dev_err to msg->status, to both fix the wrong argument to PTR_ERR in the
second case and to make the dev_err line a little shorter. This required
further
On Sun, 30 Aug 2015, walter harms wrote:
>
>
> Am 30.08.2015 20:05, schrieb Julia Lawall:
> > Apply PTR_ERR to the value that was recently assigned.
> >
> > The semantic match that finds this problem is as follows:
> > (http://coccinelle.lip6.fr/)
> >
> > //
> > @@
> > expression x,y;
> > @
The PXA architecture provides a DMA to pump data from the nand
controller to memory and the other way around. Add it to the binding
description.
Signed-off-by: Robert Jarzmik
---
Documentation/devicetree/bindings/mtd/pxa3xx-nand.txt | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Document
Guennadi Liakhovetski writes:
>> +last_buf = list_entry(pcdev->capture.prev,
>> + struct pxa_buffer, vb.queue);
>
> You can use list_last_entry()
Ok.
>> +last_status = dma_async_is_tx_complete(pcdev->dma_chans[chan],
>> +
On Friday 28 August 2015 17:17:27 Luis R. Rodriguez wrote:
> From: "Luis R. Rodriguez"
>
> The S390 architecture requires a custom pci_iomap() implementation
> as the asm-generic implementation assumes there are disjunctions
> between PCI BARs, and on S390 PCI BAR are not disjunctive, S390 requir
Guennadi Liakhovetski writes:
> This still seems to break compilation to me. Could you compile-test after
> each your patch, please?
Ah yes. Ill timing, I had sent the v4 before having these comments, so I'll have
to fix it in v5.
Cheers.
--
Robert
--
To unsubscribe from this list: send the l
From: Robert Jarzmik
Fix the error path where the video buffer wasn't allocated nor
mapped. In this case, in the driver free path don't try to unmap memory
which was not mapped in the first place.
Signed-off-by: Robert Jarzmik
---
drivers/media/platform/soc_camera/pxa_camera.c | 6 --
1 fi
From: Robert Jarzmik
This moves the dma irq handling functions up in the source file, so that
they are available before DMA preparation functions. It prepares the
conversion to DMA engine, where the descriptors are populated with these
functions as callbacks.
Signed-off-by: Robert Jarzmik
---
S
Convert pxa_camera to dmaengine. This removes all DMA registers
manipulation in favor of the more generic dmaengine API.
The functional level should be the same as before. The biggest change is
in the videobuf_sg_splice() function, which splits a videobuf-dma into
several scatterlists for 3 planes
Hi Guennadi,
This is the forth round.
This time sg_split() was a consequence of (a) and (b), ie. sg_split() move into
kernel's lib/ directory, and following dmaengine "reuse" flag introduction,
change pxa_camera accordingly.
Happy review.
Cheers.
Robert Jarzmik (4):
media: pxa_camera: fix th
After the conversion of pxa architecture to common clock framework, the
NAND clock can be disabled on driver exit.
In this case, it happens that if the driver used the NAND and set the
DFI arbitration bit, the next access to a static memory controller area,
such as an ethernet card, will stall the
From: Robert Jarzmik
In preparation for dmaengine conversion, move the camera interrupt
handling into a tasklet. This won't change the global flow, as this
interrupt is only used to detect the end of frame and activate DMA fifos
handling.
Signed-off-by: Robert Jarzmik
---
drivers/media/platfor
SLAB's implementation of kmem_cache_alloc() works as follows:
1. First, it tries to allocate from the preferred NUMA node without
issuing reclaim.
2. If step 1 fails, it tries all nodes in the order of preference,
again without invoking reclaimer
3. Only if steps 1 and 2 fails, it falls
Commit 6af3142bed1f52 ("mm/slub: don't wait for high-order page
allocation") made allocate_slab() try to allocate high order slab pages
without __GFP_WAIT in order to avoid invoking reclaim/compaction when we
can fall back on low order pages. However, it broke memcg/memory.high
logic in case kmem a
1 - 100 of 193 matches
Mail list logo
