From: Tony Lindgren
Let's configure the keypad in a way where it's usable out of the
box for Linux console use. To do this, let's follow the standard
PC keyboard layout for ctrl, shift and alt keys:
Ctrl = what is labeled as shift
Alt = what is labeled as SYM
Shift = what is
On Wed, 2017-02-22 at 16:11 +1100, Suraj Jitindar Singh wrote:
> On Fri, 2017-02-17 at 14:28 +1100, Cyril Bur wrote:
>
> I may be too late, but see below...
> > In order to manage server systems, there is typically another
> > processor
> > known as a BMC (Baseboard Management Controller) which
Hi,
Tony, since your omap4-droid4 dts patches were not
yet in a public repository and they would merge conflict
with my patches I put them all together into a single
patchset. I also added my Tested-By to your patches.
The mounting-matrix for the sensors and the touchscreen's
rotation assume,
From: Tony Lindgren
Let's configure the keypad in a way where it's usable out of the
box for Linux console use. To do this, let's follow the standard
PC keyboard layout for ctrl, shift and alt keys:
Ctrl = what is labeled as shift
Alt = what is labeled as SYM
Shift = what is lableled as caps
On Wed, 2017-02-22 at 16:11 +1100, Suraj Jitindar Singh wrote:
> On Fri, 2017-02-17 at 14:28 +1100, Cyril Bur wrote:
>
> I may be too late, but see below...
> > In order to manage server systems, there is typically another
> > processor
> > known as a BMC (Baseboard Management Controller) which
Hi,
Tony, since your omap4-droid4 dts patches were not
yet in a public repository and they would merge conflict
with my patches I put them all together into a single
patchset. I also added my Tested-By to your patches.
The mounting-matrix for the sensors and the touchscreen's
rotation assume,
On Wed, Mar 01, 2017 at 11:42:54PM +0100, Arnd Bergmann wrote:
> On Wed, Mar 1, 2017 at 5:53 PM, Josh Poimboeuf wrote:
> > On Wed, Mar 01, 2017 at 04:27:29PM +0100, Arnd Bergmann wrote:
>
> > I see no apparent reason for the ud2.
>
> It's the possible division by zero. This
On Wed, Mar 01, 2017 at 11:42:54PM +0100, Arnd Bergmann wrote:
> On Wed, Mar 1, 2017 at 5:53 PM, Josh Poimboeuf wrote:
> > On Wed, Mar 01, 2017 at 04:27:29PM +0100, Arnd Bergmann wrote:
>
> > I see no apparent reason for the ud2.
>
> It's the possible division by zero. This change would avoid
On Droid 4 "Volume Down" and "Keypad Slide" keys are
connected via SoC GPIOs, "Power Key" via CPCAP and
all other keys via SoC keypad Matrix. This adds the
GPIO keys.
Signed-off-by: Sebastian Reichel
---
arch/arm/boot/dts/omap4-droid4-xt894.dts | 21 +
1
On Droid 4 "Volume Down" and "Keypad Slide" keys are
connected via SoC GPIOs, "Power Key" via CPCAP and
all other keys via SoC keypad Matrix. This adds the
GPIO keys.
Signed-off-by: Sebastian Reichel
---
arch/arm/boot/dts/omap4-droid4-xt894.dts | 21 +
1 file changed, 21
Droid4's touchscreen can be used with mainline's maxtouch
driver. The touchscreen's lower area is used for four soft
buttons (KEY_MENU, KEY_HOME, KEY_BACK, KEY_SEARCH), but that
is currently not supported by the mainline kernel.
Signed-off-by: Sebastian Reichel
---
From: Tony Lindgren
With drivers/mfd/motorola-cpcap.c and drivers/regulator/cpcap-regulator.c
we can now configure proper regulators for droid 4.
Let's add regulator voltages and switch over MMC, eMMC and WLAN to use
the CPCAP regulators.
Cc: devicet...@vger.kernel.org
Cc:
Droid4's touchscreen can be used with mainline's maxtouch
driver. The touchscreen's lower area is used for four soft
buttons (KEY_MENU, KEY_HOME, KEY_BACK, KEY_SEARCH), but that
is currently not supported by the mainline kernel.
Signed-off-by: Sebastian Reichel
---
From: Tony Lindgren
With drivers/mfd/motorola-cpcap.c and drivers/regulator/cpcap-regulator.c
we can now configure proper regulators for droid 4.
Let's add regulator voltages and switch over MMC, eMMC and WLAN to use
the CPCAP regulators.
Cc: devicet...@vger.kernel.org
Cc: Marcel Partap
Cc:
Does the patch below fix it?
I'll test you patch in a bit and let you know.
It seem to work.
But to be really sure I let the box running with this setup over night.
8<--
--- a/drivers/net/ethernet/intel/e1000e/netdev.c
+++
Does the patch below fix it?
I'll test you patch in a bit and let you know.
It seem to work.
But to be really sure I let the box running with this setup over night.
8<--
--- a/drivers/net/ethernet/intel/e1000e/netdev.c
+++
Hi Chao,
BTW, we need to add a shrinker for this as well, right?
Thanks,
On 02/23, Chao Yu wrote:
> In scenario of intensively node allocation, free nids will be ran out
> soon, then it needs to stop to load free nids by traversing NAT blocks,
> in worse case, if NAT blocks does not be cached
From: Andrew Pinski
In this patchset ILP32 ABI support is added. Additionally to AARCH32,
which is binary-compatible with ARM, ILP32 is (mostly) ABI-compatible.
>From now, AARCH32_EL0 (former COMPAT) config option means the support of
AARCH32 userspace, ARM64_ILP32 -
On Wed, 1 Mar 2017 21:44:26 +0100
Hans-Christian Noren Egtvedt wrote:
> Hello all,
>
> The AVR32 architecture is not keeping up with the development of the kernel,
> and since it shares so much of the drivers with Atmel ARM SoC, it is starting
> to hinder these drivers to
Hi Chao,
BTW, we need to add a shrinker for this as well, right?
Thanks,
On 02/23, Chao Yu wrote:
> In scenario of intensively node allocation, free nids will be ran out
> soon, then it needs to stop to load free nids by traversing NAT blocks,
> in worse case, if NAT blocks does not be cached
From: Andrew Pinski
In this patchset ILP32 ABI support is added. Additionally to AARCH32,
which is binary-compatible with ARM, ILP32 is (mostly) ABI-compatible.
>From now, AARCH32_EL0 (former COMPAT) config option means the support of
AARCH32 userspace, ARM64_ILP32 - support of ILP32 ABI (see
On Wed, 1 Mar 2017 21:44:26 +0100
Hans-Christian Noren Egtvedt wrote:
> Hello all,
>
> The AVR32 architecture is not keeping up with the development of the kernel,
> and since it shares so much of the drivers with Atmel ARM SoC, it is starting
> to hinder these drivers to develop swiftly.
Em Fri, Feb 24, 2017 at 01:14:18PM +0100, Peter Zijlstra escreveu:
> On Tue, Feb 21, 2017 at 07:31:23PM +0530, Hari Bathini wrote:
> > With the advert of container technologies like docker, that depend
> > on namespaces for isolation, there is a need for tracing support for
> > namespaces. This
Em Fri, Feb 24, 2017 at 01:14:18PM +0100, Peter Zijlstra escreveu:
> On Tue, Feb 21, 2017 at 07:31:23PM +0530, Hari Bathini wrote:
> > With the advert of container technologies like docker, that depend
> > on namespaces for isolation, there is a need for tracing support for
> > namespaces. This
On Tue, Feb 28, 2017 at 10:11:56AM -0700, Logan Gunthorpe wrote:
>
> > This driver doesn't have anything to do with the PCI core, other than
> > using the pci_register_driver() interface (just like all other drivers
> > for PCI-connected devices), so drivers/pci doesn't really feel like
> > the
On Tue, Feb 28, 2017 at 10:11:56AM -0700, Logan Gunthorpe wrote:
>
> > This driver doesn't have anything to do with the PCI core, other than
> > using the pci_register_driver() interface (just like all other drivers
> > for PCI-connected devices), so drivers/pci doesn't really feel like
> > the
Replace size_t with __kernel_size_t to fix asm/shmbuf.h userspace
compilation errors like this:
/usr/include/asm-generic/shmbuf.h:28:2: error: unknown type name 'size_t'
size_t shm_segsz; /* size of segment (bytes) */
x32 is the only architecture where sizeof(size_t) is less than
Replace size_t with __kernel_size_t to fix asm/shmbuf.h userspace
compilation errors like this:
/usr/include/asm-generic/shmbuf.h:28:2: error: unknown type name 'size_t'
size_t shm_segsz; /* size of segment (bytes) */
x32 is the only architecture where sizeof(size_t) is less than
On Wed, Mar 01, 2017 at 05:23:38PM -0700, Logan Gunthorpe wrote:
> > That could help, but this would mean cdev would have to insert a shim
> > to grab locks around the various file ops.
>
> Hmm, I was hoping something more along the lines of actually killing the
> processes instead of just
On Wed, Mar 01, 2017 at 05:23:38PM -0700, Logan Gunthorpe wrote:
> > That could help, but this would mean cdev would have to insert a shim
> > to grab locks around the various file ops.
>
> Hmm, I was hoping something more along the lines of actually killing the
> processes instead of just
On 03/01/2017 11:58 AM, Sven Schmidt wrote:
Hi Guenter, Tobias and Sandra,
thanks for your effort here.
On Tue, Feb 28, 2017 at 10:14:13AM -0800, Guenter Roeck wrote:
On Tue, Feb 28, 2017 at 10:53:56AM -0700, Sandra Loosemore wrote:
On 02/28/2017 08:53 AM, Tobias Klauser wrote:
(adding
On 03/01/2017 11:58 AM, Sven Schmidt wrote:
Hi Guenter, Tobias and Sandra,
thanks for your effort here.
On Tue, Feb 28, 2017 at 10:14:13AM -0800, Guenter Roeck wrote:
On Tue, Feb 28, 2017 at 10:53:56AM -0700, Sandra Loosemore wrote:
On 02/28/2017 08:53 AM, Tobias Klauser wrote:
(adding
On Tue, Feb 28, 2017 at 08:12:46PM +0300, Cyrill Gorcunov wrote:
> With current epoll architecture target files are addressed
> with file_struct and file descriptor number, where the last
> is not unique. Moreover files can be transferred from another
> process via unix socket, added into queue
On Tue, Feb 28, 2017 at 08:12:46PM +0300, Cyrill Gorcunov wrote:
> With current epoll architecture target files are addressed
> with file_struct and file descriptor number, where the last
> is not unique. Moreover files can be transferred from another
> process via unix socket, added into queue
set_memory_* functions have moved to set_memory.h. Switch to this
explicitly.
Signed-off-by: Laura Abbott
---
kernel/module.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/kernel/module.c b/kernel/module.c
index 7eba6de..c0f04b3 100644
--- a/kernel/module.c
+++
On Wed 01-03-17 16:46:59, Peter Zijlstra wrote:
> On Wed, Mar 01, 2017 at 01:29:57PM +0200, Nikolay Borisov wrote:
> > Commit 21caf2fc1931 ("mm: teach mm by current context info to not do I/O
> > during memory allocation") added the memalloc_noio_(save|restore) functions
> > to enable people to
The set_memory_* functions have moved to set_memory.h. Use that header
explicitly.
Signed-off-by: Laura Abbott
---
arch/arm64/mm/pageattr.c | 1 +
arch/arm64/net/bpf_jit_comp.c | 1 +
2 files changed, 2 insertions(+)
diff --git a/arch/arm64/mm/pageattr.c
set_memory_* functions have moved to set_memory.h. Switch to this
explicitly.
Signed-off-by: Laura Abbott
---
kernel/module.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/kernel/module.c b/kernel/module.c
index 7eba6de..c0f04b3 100644
--- a/kernel/module.c
+++ b/kernel/module.c
@@ -49,6
On Wed 01-03-17 16:46:59, Peter Zijlstra wrote:
> On Wed, Mar 01, 2017 at 01:29:57PM +0200, Nikolay Borisov wrote:
> > Commit 21caf2fc1931 ("mm: teach mm by current context info to not do I/O
> > during memory allocation") added the memalloc_noio_(save|restore) functions
> > to enable people to
The set_memory_* functions have moved to set_memory.h. Use that header
explicitly.
Signed-off-by: Laura Abbott
---
arch/arm64/mm/pageattr.c | 1 +
arch/arm64/net/bpf_jit_comp.c | 1 +
2 files changed, 2 insertions(+)
diff --git a/arch/arm64/mm/pageattr.c b/arch/arm64/mm/pageattr.c
index
On 01/03/17 05:32 PM, Bjorn Helgaas wrote:
> It's not a perfect fit in drivers/pci because it's not bus
> infrastructure and I don't want to be the default maintainer of it,
> but I agree there's not really an alternative that's clearly better,
> so let's leave it where it is for now.
Sounds
On 01/03/17 05:32 PM, Bjorn Helgaas wrote:
> It's not a perfect fit in drivers/pci because it's not bus
> infrastructure and I don't want to be the default maintainer of it,
> but I agree there's not really an alternative that's clearly better,
> so let's leave it where it is for now.
Sounds
On Wed, Mar 01, 2017 at 03:49:04PM -0700, Logan Gunthorpe wrote:
> Seems to me like an elegant solution would be to implement a 'cdev_kill'
> function which could kill all the processes using a cdev. Thus, during
> an unbind, a driver could call it and be sure that there are no users
> left and
On Wed, Mar 01, 2017 at 03:49:04PM -0700, Logan Gunthorpe wrote:
> Seems to me like an elegant solution would be to implement a 'cdev_kill'
> function which could kill all the processes using a cdev. Thus, during
> an unbind, a driver could call it and be sure that there are no users
> left and
On Wed, Mar 01, 2017 at 09:02:33AM -0700, Mathieu Poirier wrote:
> On Tue, Feb 28, 2017 at 11:06:59PM +0800, Leo Yan wrote:
> > This is refactor to add function of_coresight_get_cpu(), so it's used to
> > retrieve CPU id for coresight component. Finally can use it as a common
> > function for
From: Gary Lin
Date: Wed, 1 Mar 2017 16:25:51 +0800
> Commit 07016151a446 ("bpf, verifier: further improve search
> pruning") increased the limit of processed instructions from
> 32k to 64k, but the comment still mentioned the 32k limit.
> This commit updates the comment to
On Wed, Mar 01, 2017 at 09:02:33AM -0700, Mathieu Poirier wrote:
> On Tue, Feb 28, 2017 at 11:06:59PM +0800, Leo Yan wrote:
> > This is refactor to add function of_coresight_get_cpu(), so it's used to
> > retrieve CPU id for coresight component. Finally can use it as a common
> > function for
From: Gary Lin
Date: Wed, 1 Mar 2017 16:25:51 +0800
> Commit 07016151a446 ("bpf, verifier: further improve search
> pruning") increased the limit of processed instructions from
> 32k to 64k, but the comment still mentioned the 32k limit.
> This commit updates the comment to reflect the change.
On Wed, Mar 01, 2017 at 02:39:09PM -0800, Sonny Rao wrote:
> > We recently added global suspend/resume callbacks to the TPM
> > core. Those call backs do not power off the TPM, they just prepare its
> > internal state to loose power to the chip. Skipping that process on
> > hardware that does not
On Wed, Mar 01, 2017 at 02:39:09PM -0800, Sonny Rao wrote:
> > We recently added global suspend/resume callbacks to the TPM
> > core. Those call backs do not power off the TPM, they just prepare its
> > internal state to loose power to the chip. Skipping that process on
> > hardware that does not
On Wed, Mar 01, 2017 at 10:35:56AM -0700, Mathieu Poirier wrote:
> On Tue, Feb 28, 2017 at 11:07:00PM +0800, Leo Yan wrote:
> > Coresight includes debug module and usually the module connects with CPU
> > debug logic. ARMv8 architecture reference manual (ARM DDI 0487A.k) has
> > description for
On Wed, Mar 01, 2017 at 10:35:56AM -0700, Mathieu Poirier wrote:
> On Tue, Feb 28, 2017 at 11:07:00PM +0800, Leo Yan wrote:
> > Coresight includes debug module and usually the module connects with CPU
> > debug logic. ARMv8 architecture reference manual (ARM DDI 0487A.k) has
> > description for
On Wed, Mar 01, 2017 at 12:46:34PM +0800, Xiong Zhou wrote:
> Hi,
>
> It's reproduciable, not everytime though. Ext4 works fine.
On ext4 fsstress won't run bulkstat because it doesn't exist. Either
way this smells like a MM issue to me as there were not XFS changes
in that area recently.
On Wed, Mar 01, 2017 at 12:46:34PM +0800, Xiong Zhou wrote:
> Hi,
>
> It's reproduciable, not everytime though. Ext4 works fine.
On ext4 fsstress won't run bulkstat because it doesn't exist. Either
way this smells like a MM issue to me as there were not XFS changes
in that area recently.
Two fixes for the security subsystem:
1) Keys: split both rcu_dereference_key() and user_key_payload() into
versions which can be called with or without holding the key semaphore.
2) SELinux: fix Android init(8) breakage due to new cgroup security
labeling support when using older policy.
Two fixes for the security subsystem:
1) Keys: split both rcu_dereference_key() and user_key_payload() into
versions which can be called with or without holding the key semaphore.
2) SELinux: fix Android init(8) breakage due to new cgroup security
labeling support when using older policy.
This driver supports the Motorola CPCAP PMIC found on
some of Motorola's mobile phones, such as the Droid 4.
Tested-by: Tony Lindgren
Signed-off-by: Sebastian Reichel
---
Changes since PATCHv3:
- Modified DT binding document to mention parent device
---
This driver supports the Motorola CPCAP PMIC found on
some of Motorola's mobile phones, such as the Droid 4.
Tested-by: Tony Lindgren
Signed-off-by: Sebastian Reichel
---
Changes since PATCHv3:
- Modified DT binding document to mention parent device
---
On Wed, Mar 01, 2017 at 04:36:17PM +0100, Enric Balletbo i Serra wrote:
> From: Bryan Freed
>
> When the I2C Infineon part is attached to an I2C adapter that imposes
> a size limitation, large requests will fail with -EOPNOTSUPP. Retry
> them with a sane minimum size without
On Wed, Mar 01, 2017 at 04:36:17PM +0100, Enric Balletbo i Serra wrote:
> From: Bryan Freed
>
> When the I2C Infineon part is attached to an I2C adapter that imposes
> a size limitation, large requests will fail with -EOPNOTSUPP. Retry
> them with a sane minimum size without re-issuing the 0x05
On Wed, Mar 01, 2017 at 07:52:18AM -0800, Dan Williams wrote:
> On Wed, Mar 1, 2017 at 4:51 AM, Heiko Carstens
> wrote:
> > Since it is anything but obvious why Dan wrote in changelog of b5d24fda9c3d
> > ("mm, devm_memremap_pages: hold device_hotplug lock over
> >
On Wed, Mar 01, 2017 at 07:52:18AM -0800, Dan Williams wrote:
> On Wed, Mar 1, 2017 at 4:51 AM, Heiko Carstens
> wrote:
> > Since it is anything but obvious why Dan wrote in changelog of b5d24fda9c3d
> > ("mm, devm_memremap_pages: hold device_hotplug lock over
> > mem_hotplug_{begin, done}") that
On March 1, 2017 4:18:54 PM PST, "Dmitry V. Levin" wrote:
>Replace size_t to fix the following asm/signal.h userspace compilation
>error:
>
>/usr/include/asm/signal.h:126:2: error: unknown type name 'size_t'
> size_t ss_size;
>
>size_t is replaced with __kernel_size_t in all
Motorola was involved in semiconductor and mobile phone business.
The "motorola," prefix is already used by a couple of bindings:
* rtc/rtc-cmos.txt
* mfd/motorola-cpcap.txt
* regulator/cpcap-regulator.txt
Apart from that it is used in the DT file for the Droid 4 mobile
phone.
Acked-by: Rob
Motorola was involved in semiconductor and mobile phone business.
The "motorola," prefix is already used by a couple of bindings:
* rtc/rtc-cmos.txt
* mfd/motorola-cpcap.txt
* regulator/cpcap-regulator.txt
Apart from that it is used in the DT file for the Droid 4 mobile
phone.
Acked-by: Rob
On March 1, 2017 4:18:54 PM PST, "Dmitry V. Levin" wrote:
>Replace size_t to fix the following asm/signal.h userspace compilation
>error:
>
>/usr/include/asm/signal.h:126:2: error: unknown type name 'size_t'
> size_t ss_size;
>
>size_t is replaced with __kernel_size_t in all cases except x32
set_memory_* functions have moved to set_memory.h. Switch to this
explicitly.
Signed-off-by: Laura Abbott
---
kernel/power/snapshot.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/kernel/power/snapshot.c b/kernel/power/snapshot.c
index 905d5bb..4302815 100644
---
Include to fix asm/sembuf.h userspace compilation errors
like this:
/usr/include/asm/sembuf.h:14:20: error: field 'sem_perm' has incomplete type
struct ipc64_perm sem_perm; /* permissions .. see ipc.h */
/usr/include/asm/sembuf.h:15:2: error: unknown type name '__kernel_time_t'
set_memory_* functions have moved to set_memory.h. Switch to this
explicitly.
Signed-off-by: Laura Abbott
---
kernel/power/snapshot.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/kernel/power/snapshot.c b/kernel/power/snapshot.c
index 905d5bb..4302815 100644
---
Include to fix asm/sembuf.h userspace compilation errors
like this:
/usr/include/asm/sembuf.h:14:20: error: field 'sem_perm' has incomplete type
struct ipc64_perm sem_perm; /* permissions .. see ipc.h */
/usr/include/asm/sembuf.h:15:2: error: unknown type name '__kernel_time_t'
set_memory_* functions have moved to set_memory.h. Switch to this
explicitly
Signed-off-by: Laura Abbott
---
arch/s390/kernel/ftrace.c| 1 +
arch/s390/kernel/kprobes.c | 2 +-
arch/s390/kernel/machine_kexec.c | 1 +
arch/s390/mm/init.c | 1 +
set_memory_* functions have moved to set_memory.h. Switch to this
explicitly
Signed-off-by: Laura Abbott
---
arch/s390/kernel/ftrace.c| 1 +
arch/s390/kernel/kprobes.c | 2 +-
arch/s390/kernel/machine_kexec.c | 1 +
arch/s390/mm/init.c | 1 +
arch/s390/mm/pageattr.c
Even if bus is not hot-pluggable, devices can be unbound from the
driver via sysfs, so we should not be using __exit annotations on
remove() methods. The only exception is drivers registered with
platform_driver_probe() which specifically disables sysfs bind/unbind
attributes.
Signed-off-by:
Even if bus is not hot-pluggable, devices can be unbound from the
driver via sysfs, so we should not be using __exit annotations on
remove() methods. The only exception is drivers registered with
platform_driver_probe() which specifically disables sysfs bind/unbind
attributes.
Signed-off-by:
Include to fix asm/msgbuf.h userspace compilation errors
like this:
/usr/include/asm-generic/msgbuf.h:25:20: error: field 'msg_perm' has incomplete
type
struct ipc64_perm msg_perm;
/usr/include/asm-generic/msgbuf.h:26:2: error: unknown type name
'__kernel_time_t'
__kernel_time_t msg_stime;
set_memory_* functions have moved to set_memory.h. Switch to this
explicitly.
Signed-off-by: Laura Abbott
---
drivers/watchdog/hpwdt.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/watchdog/hpwdt.c b/drivers/watchdog/hpwdt.c
index
Include to fix asm/msgbuf.h userspace compilation errors
like this:
/usr/include/asm-generic/msgbuf.h:25:20: error: field 'msg_perm' has incomplete
type
struct ipc64_perm msg_perm;
/usr/include/asm-generic/msgbuf.h:26:2: error: unknown type name
'__kernel_time_t'
__kernel_time_t msg_stime;
set_memory_* functions have moved to set_memory.h. Switch to this
explicitly.
Signed-off-by: Laura Abbott
---
drivers/watchdog/hpwdt.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/watchdog/hpwdt.c b/drivers/watchdog/hpwdt.c
index 70c7194..67fbe35 100644
---
set_memory_* functions have moved to set_memory.h. Switch to this
explicitly.
Signed-off-by: Laura Abbott
---
drivers/gpu/drm/amd/amdgpu/amdgpu_gart.c | 1 +
drivers/gpu/drm/gma500/gtt.c | 1 +
drivers/gpu/drm/gma500/psb_drv.c | 1 +
set_memory_* functions have moved to set_memory.h. Switch to this
explicitly.
Signed-off-by: Laura Abbott
---
drivers/gpu/drm/amd/amdgpu/amdgpu_gart.c | 1 +
drivers/gpu/drm/gma500/gtt.c | 1 +
drivers/gpu/drm/gma500/psb_drv.c | 1 +
drivers/gpu/drm/radeon/radeon_gart.c
set_memory_* functions have moved to set_memory.h. Switch to this
explicitly
Signed-off-by: Laura Abbott
---
arch/arm/mm/pageattr.c| 1 +
arch/arm/net/bpf_jit_32.c | 2 +-
2 files changed, 2 insertions(+), 1 deletion(-)
diff --git a/arch/arm/mm/pageattr.c
set_memory_* functions have moved to set_memory.h. Switch to this
explicitly
Signed-off-by: Laura Abbott
---
arch/arm/mm/pageattr.c| 1 +
arch/arm/net/bpf_jit_32.c | 2 +-
2 files changed, 2 insertions(+), 1 deletion(-)
diff --git a/arch/arm/mm/pageattr.c b/arch/arm/mm/pageattr.c
index
Include to fix asm/shmbuf.h userspace compilation errors
like this:
/usr/include/asm-generic/shmbuf.h:26:20: error: field 'shm_perm' has incomplete
type
struct ipc64_perm shm_perm; /* operation perms */
/usr/include/asm-generic/shmbuf.h:28:2: error: unknown type name
'__kernel_time_t'
Include to fix asm/shmbuf.h userspace compilation errors
like this:
/usr/include/asm-generic/shmbuf.h:26:20: error: field 'shm_perm' has incomplete
type
struct ipc64_perm shm_perm; /* operation perms */
/usr/include/asm-generic/shmbuf.h:28:2: error: unknown type name
'__kernel_time_t'
Motorola CPCAP is a PMIC found in multiple smartphones.
This driver adds support for the power/on button and has
been tested in Droid 4.
Acked-by: Rob Herring
Signed-off-by: Sebastian Reichel
---
Changes since PATCHv1:
- Fix device for
Motorola CPCAP is a PMIC found in multiple smartphones.
This driver adds support for the power/on button and has
been tested in Droid 4.
Acked-by: Rob Herring
Signed-off-by: Sebastian Reichel
---
Changes since PATCHv1:
- Fix device for devm_request_threaded_irq()
- Add Acked-By from Rob
set_memory_* functions have moved to set_memory.h. Switch to this
explicitly.
Signed-off-by: Laura Abbott
---
drivers/char/agp/amd-k7-agp.c | 1 +
drivers/char/agp/ati-agp.c| 1 +
drivers/char/agp/generic.c| 2 +-
drivers/char/agp/intel-gtt.c | 1 +
set_memory_* functions have moved to set_memory.h. Switch to this
explicitly.
Signed-off-by: Laura Abbott
---
include/linux/filter.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/filter.h b/include/linux/filter.h
index 0c167fd..c2b403f
set_memory_* functions have moved to set_memory.h. Switch to this
explicitly.
Signed-off-by: Laura Abbott
---
drivers/char/agp/amd-k7-agp.c | 1 +
drivers/char/agp/ati-agp.c| 1 +
drivers/char/agp/generic.c| 2 +-
drivers/char/agp/intel-gtt.c | 1 +
drivers/char/agp/sworks-agp.c | 1 +
set_memory_* functions have moved to set_memory.h. Switch to this
explicitly.
Signed-off-by: Laura Abbott
---
include/linux/filter.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/filter.h b/include/linux/filter.h
index 0c167fd..c2b403f 100644
---
CPCAP can sense if IRQ is currently set or not. This
functionality is required for a few subdevices, such
as the power button and usb phy modules.
Signed-off-by: Sebastian Reichel
---
Changes since PATCHv1:
- Newly introduced patch
---
drivers/mfd/motorola-cpcap.c | 25
CPCAP can sense if IRQ is currently set or not. This
functionality is required for a few subdevices, such
as the power button and usb phy modules.
Signed-off-by: Sebastian Reichel
---
Changes since PATCHv1:
- Newly introduced patch
---
drivers/mfd/motorola-cpcap.c | 25
Hi,
On Wed, Mar 01, 2017 at 03:33:23PM -0800, Dmitry Torokhov wrote:
> Even if bus is not hot-pluggable, devices can be unbound from the
> driver via sysfs, so we should not be using __exit annotations on
> remove() methods. The only exception is drivers registered with
> platform_driver_probe(),
Hi,
On Wed, Mar 01, 2017 at 03:33:23PM -0800, Dmitry Torokhov wrote:
> Even if bus is not hot-pluggable, devices can be unbound from the
> driver via sysfs, so we should not be using __exit annotations on
> remove() methods. The only exception is drivers registered with
> platform_driver_probe(),
Replace size_t with __kernel_size_t to fix asm/signal.h userspace
compilation errors like this:
/usr/include/asm-generic/signal.h:116:2: error: unknown type name 'size_t'
size_t ss_size;
This change is not applicable to x86 port because x32 is the only
architecture where sizeof(size_t) <
Hi Ksenija!
Ksenija Stanojevic writes:
> +static int mxs_lradc_ts_register(struct mxs_lradc_ts *ts)
> +{
> + struct input_dev *input = ts->ts_input;
> + struct device *dev = ts->dev;
> +
> + input = devm_input_allocate_device(dev);
> + if (!input)
> + return -ENOMEM;
>
Hi Ksenija!
Ksenija Stanojevic writes:
> +static int mxs_lradc_ts_register(struct mxs_lradc_ts *ts)
> +{
> + struct input_dev *input = ts->ts_input;
> + struct device *dev = ts->dev;
> +
> + input = devm_input_allocate_device(dev);
> + if (!input)
> + return -ENOMEM;
>
Replace size_t with __kernel_size_t to fix asm/signal.h userspace
compilation errors like this:
/usr/include/asm-generic/signal.h:116:2: error: unknown type name 'size_t'
size_t ss_size;
This change is not applicable to x86 port because x32 is the only
architecture where sizeof(size_t) <
On Tue, Feb 28, 2017 at 7:55 AM, Joe Perches wrote:
> Use a more common logging style.
>
> Miscellanea:
>
> o Coalesce formats and realign arguments
> o Neaten a few macros now using pr_
>
> Signed-off-by: Joe Perches
Applied. Thanks!
Alex
> ---
>
On Tue, Feb 28, 2017 at 7:55 AM, Joe Perches wrote:
> Use a more common logging style.
>
> Miscellanea:
>
> o Coalesce formats and realign arguments
> o Neaten a few macros now using pr_
>
> Signed-off-by: Joe Perches
Applied. Thanks!
Alex
> ---
> drivers/gpu/drm/amd/amdgpu/amdgpu.h
301 - 400 of 1758 matches
Mail list logo