On Mon, Nov 30, 2015 at 01:55:19PM +0100, Linus Walleij wrote:
> On Fri, Nov 20, 2015 at 10:45 PM, Li Yang wrote:
>
> > - if (IS_ERR(i2c_imx->pinctrl)) {
> > + /* bailout on -ENOMEM or -EPROBE_DEFER, continue for other errors */
> > + if (PTR_ERR(i2c_imx->pinctrl) == -ENOMEM ||
On Tue, Dec 15, 2015 at 03:22:26PM +0800, Liguo Zhang wrote:
> For mt8173 platform with auto restart support, when doing i2c multi
> transfer in high speed, we should ignore the first restart irq after
> the master code, otherwise the first transfer will be discarded.
>
> Signed-off-by: Liguo Zhan
On Wed, Dec 16, 2015 at 06:49:59PM -0600, Suravee Suthikulanit wrote:
> Mika,
>
> On 12/16/2015 8:54 AM, Mika Westerberg wrote:
> >On Wed, Dec 16, 2015 at 08:29:38AM -0600, Suravee Suthikulpanit wrote:
> >>>
> >>>
> >>>On 12/16/2015 03:16 AM, Mika Westerberg wrote:
> >On Tue, Dec 15, 2015 at
>> I am a bit surprised that you do not like such source code fine-tuning.
>
> It's moving stuff around for no real reason, why would I like it?
Can such fine-tuning result in positive effects for the run-time behaviour?
> Reading and reviewing and applying this type of stuff takes away from
>
On Sun, Dec 27, 2015 at 06:45:59PM +0800, Geliang Tang wrote:
> Use to_pci_dev() instead of open-coding it.
>
> Signed-off-by: Geliang Tang
Applied to for-next, thanks!
signature.asc
Description: Digital signature
On Sun, Dec 27, 2015 at 09:15:42PM +0800, Geliang Tang wrote:
> Use to_platform_device() instead of open-coding it.
>
> Signed-off-by: Geliang Tang
Applied to for-next, thanks!
signature.asc
Description: Digital signature
On 2015/11/06, Dmitry Vyukov reported a deadlock involving the splice
system call and AF_UNIX sockets,
http://lists.openwall.net/netdev/2015/11/06/24
The situation was analyzed as
(a while ago) A: socketpair()
B: splice() from a pipe to /mnt/regular_file
does sb_start_write() on /mnt
C:
On Wed, Dec 02, 2015 at 03:18:59PM +0800, Peter Hung wrote:
> This driver is for Fintek F81532/F81534 USB to Serial Ports IC.
Do you have a pointer to datasheets and/or information about these
devices? Can't seem to find anything on Fintek's homepage.
> Features:
> 1. F81534 is 1-to-4 & F81532 is
Fix checkpatch.pl warnings in panel.c
Signed-off-by: Ksenija Stanojevic
Ksenija Stanojevic (2):
Staging: panel: Fix line over 80 characters
Staging: panel: Remove space
drivers/staging/panel/panel.c | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
--
1.9.1
--
To unsubscribe
Move statement into line below the comment to follow 80 characters per
line rule.
Found by checkpatch.pl
Signed-off-by: Ksenija Stanojevic
---
Changes in v2:
- don't split comment in multiline
drivers/staging/panel/panel.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff -
No space is necessary after a cast, therefore remove it.
Found by checkpatch.pl
Signed-off-by: Ksenija Stanojevic
---
Changes in v2:
- nothing
drivers/staging/panel/panel.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/panel/panel.c b/drivers/sta
This patchset is based on checkpatch fixes made by previous patches.
Here I tried to address all suggestions made by Dan and Willy.
Signed-off-by: Ksenija Stanojevic
Ksenija Stanojevic (5):
Staging: panel: Use u8 type
Staging: panel: Remove typedef pmask_t
Staging: panel: Remove ULL
Stag
Declare om, im, omask and imask as u8 to remove any confusion if
that describes the 8 bits of the data bus on the parallel port.
Also change return type of lcd_write_data() to u8.
Signed-off-by: Ksenija Stanojevic
---
v2: nothing
drivers/staging/panel/panel.c | 6 +++---
1 file changed, 3 inser
Use __u64 instead of pmask_t and remove pmask_t since is useless.
Signed-off-by: Ksenija Stanojevic
---
v2: nothing
drivers/staging/panel/panel.c | 24 +++-
1 file changed, 11 insertions(+), 13 deletions(-)
diff --git a/drivers/staging/panel/panel.c b/drivers/staging/panel/
Remove ULL on om and im, since it's useless.
Signed-off-by: Ksenija Stanojevic
---
v2: leave ULL on m and v.
drivers/staging/panel/panel.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/panel/panel.c b/drivers/staging/panel/panel.c
index 7138ee7..e9641ea
out is 0-9 so it's too much for om, therefore reduce value range for
*name from '0'-'9' to '0'-'7'.
Signed-off-by: Ksenija Stanojevic
---
v2: nothing
drivers/staging/panel/panel.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/panel/panel.c b/drivers/staging/
Repace 'for' statement by strchr() function to make code more readable.
Signed-off-by: Ksenija Stanojevic
---
v2: use strchr().
drivers/staging/panel/panel.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/drivers/staging/panel/panel.c b/drivers/staging/panel/pan
On Sun, Jan 03, 2016 at 07:50:18PM +0100, SF Markus Elfring wrote:
> >> I am a bit surprised that you do not like such source code fine-tuning.
> >
> > It's moving stuff around for no real reason, why would I like it?
>
> Can such fine-tuning result in positive effects for the run-time behaviour?
On Thu, Dec 31, 2015 at 10:36 PM, Al Viro wrote:
> In cases when we need to pin the symlink body in some manner, we
> need to undo whatever we'd done once the caller is done with the body.
> That went through several variants, the latest (in -next right now) being
> "have non-NULL ->put_li
use the definition in include/uapi/linux/xattr.h
igned-off-by: Toralf Förster
---
security/commoncap.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/security/commoncap.c b/security/commoncap.c
index 1832cf7..907a3ef 100644
--- a/security/commoncap.c
+++ b/security/commo
use the definition in include/uapi/linux/xattr.h
Signed-off-by: Toralf Förster
---
fs/ext4/xattr_security.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/ext4/xattr_security.c b/fs/ext4/xattr_security.c
index 36f4c1a..1a3d629 100644
--- a/fs/ext4/xattr_security.c
+++ b/f
use the definition in include/uapi/linux/xattr.h
Signed-off-by: Toralf Förster
---
security/commoncap.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/security/commoncap.c b/security/commoncap.c
index 1832cf7..907a3ef 100644
--- a/security/commoncap.c
+++ b/security/comm
>> Can such fine-tuning result in positive effects for the run-time behaviour?
>
> If you can not benchmark and show the proof, don't even start to claim
> such a thing.
Which measurement results would you accept for further discussion?
>> My suggestions can result in measurable differences.
>
On Sun, Jan 03, 2016 at 07:12:47AM +, Al Viro wrote:
> While trying to write documentation on allocator choice, I've run
> into something odd:
> /*
> * __vmalloc() will allocate data pages and auxillary structures (e.g.
> * pagetables) with GFP_KERNEL, yet we may
On Sun, Jan 03, 2016 at 09:10:45PM +0100, SF Markus Elfring wrote:
> >> Can such fine-tuning result in positive effects for the run-time behaviour?
> >
> > If you can not benchmark and show the proof, don't even start to claim
> > such a thing.
>
> Which measurement results would you accept for f
>> Which measurement results would you accept for further discussion?
>
> If you don't know how to show your results, then this whole discussion
> is pointless.
I could show test results. But it could happen that I would choose insufficient
variations for execution environments.
I am unsure abou
On Sun, Jan 03, 2016 at 11:53:21AM -0800, Linus Torvalds wrote:
> On Thu, Dec 31, 2015 at 10:36 PM, Al Viro wrote:
> > In cases when we need to pin the symlink body in some manner, we
> > need to undo whatever we'd done once the caller is done with the body.
> > That went through several v
On Sat, Jan 02, 2016 at 11:43:09AM -0500, Matthew Wilcox wrote:
> On Thu, Dec 31, 2015 at 10:30:27AM +1100, Dave Chinner wrote:
> > > @@ -1637,6 +1669,7 @@ xfs_filemap_pfn_mkwrite(
> > > static const struct vm_operations_struct xfs_file_vm_ops = {
> > > .fault = xfs_filemap_fault,
> > >
On Mon, Jan 04, 2016 at 07:12:33AM +1100, Dave Chinner wrote:
> That'd be a nice start, though it doesn't address callers of
> vm_map_ram() which also has hard-coded GFP_KERNEL allocation masks
> for various allocations.
... all 3 of them, that is - XFS, android/ion/ion_heap.c and
v4l2-core. 5 c
On Sun, Jan 3, 2016 at 12:21 PM, Al Viro wrote:
>
> Just to make sure - that does include 13/13, presumably?
Ugh, no, I had set that aside and then forgot all about it.
I'm not sure about 13/13. I'm ok with it, but I'm not sure it's any
less confusing than the cookie was.
I like how it removes
On Tue, Dec 15, 2015 at 10:11:45AM +0100, Andrea Gelmini wrote:
> On Tue, Dec 15, 2015 at 08:22:20AM +1100, Dave Chinner wrote:
> > $ gdb vmlinux
> >
> > (gdb) l *(xfs_iflush_cluster+0x9d7)
>
> It's not working. Shame on me, I forgot to set "Compile the kernel with debug
> info".
>
> I'm re
Commit 4ea14a53d8f881034fa9e186653821c4e3d9a8fb ("Input: gpio-keys -
report error when disabling unsupported key") tried to prevent an
unsupported key to disabled. Unfortunately it effectively broke the driver
in a way so no key is possible to be disabled. Fix that by providing the
correct verify l
> > I would beg to differ. As a tool for understanding the differences as you
> > step through the versions it's invaluable.
>
> This removes intentional formatting that
> makes reading comments easier.
And this matters at the end of the patch series because ?
--
To unsubscribe from this list: s
Add a number of DPCD definitions from DP 1.1
Signed-off-by: Enric Balletbo i Serra
---
include/drm/drm_dp_helper.h | 10 ++
1 file changed, 10 insertions(+)
diff --git a/include/drm/drm_dp_helper.h b/include/drm/drm_dp_helper.h
index bb9d0de..9b0c990 100644
--- a/include/drm/drm_dp_help
The MPEG Source (MS) InfoFrame is in EIA/CEA-861B. It describes aspects of
the compressed video stream that were used to produce the uncompressed
video.
The patch adds functions to work with MPEG InfoFrames.
Signed-off-by: Enric Balletbo i Serra
---
drivers/video/hdmi.c | 156 ++
The ANX7814 is an ultra-low power Full-HD (1080p60) SlimPort transmitter
designed for portable devices.
You can add support to your board with current binding.
Example:
anx7814: anx7814@38 {
compatible = "analogix,anx7814";
reg = <0x38>;
in
At the moment it only supports ANX7814.
The ANX7814 is an ultra-low power Full-HD (1080p60) SlimPort transmitter
designed for portable devices. The ANX7814 transforms the HDMI output of
an application processor to MyDP or DisplayPort.
The driver supports HDMI to DP pass-through mode and works usi
Hi all,
This is another version of the patch set to introduce the anx7814 transmitter.
Any comments are welcome.
The following series add initial support for the Slimport ANX7814 transmitter, a
ultra-low power Full-HD (1080p60) transmitter designed for portable device.
The driver was originally
Analogix Semiconductor develops analog and mixed-signal devices for digital
media and communications interconnect applications.
Signed-off-by: Enric Balletbo i Serra
Acked-by: Rob Herring
---
Documentation/devicetree/bindings/vendor-prefixes.txt | 1 +
1 file changed, 1 insertion(+)
diff --git
On Sun, Jan 03, 2016 at 12:41:47PM -0800, Linus Torvalds wrote:
> I like how it removes "put_link()" as a callback, but at the same time
> I think it's even more abstract than the cookie was.
>
> The main worry I have is that the naming is generic, but there's only
> a single very specialized use
On Mon, Dec 28, 2015 at 11:15:30AM +0100, Geert Uytterhoeven wrote:
> Hi Simon,
>
> On Mon, Dec 28, 2015 at 6:01 AM, Simon Horman wrote:
> > On Mon, Dec 21, 2015 at 11:33:44AM +0100, Geert Uytterhoeven wrote:
> >> As of commit e488ca9f8d4f62c2 ("doc: dt: mtd: partitions: add compatible
> >> prope
(using an email address for James that shouldn't bounce)
On Sun, 2016-01-03 at 21:29 +, One Thousand Gnomes wrote:
> > > I would beg to differ. As a tool for understanding the
> > > differences as you
> > > step through the versions it's invaluable.
> >
> > This removes intentional formatting
Den 17.12.2015 00:55, skrev Eric Anholt:
This should be a complete port of bcm2835 functionality to bcm2836
(Raspberry Pi 2).
Signed-off-by: Eric Anholt
---
v2: Implement Arnd's feedback to not split to ARCH_BCM2836, and
instead use more conditionals in ARCH_BCM2835. Also reduce diff
On Sun, 2016-01-03 at 22:05 +, One Thousand Gnomes wrote:
> On Sun, 03 Jan 2016 13:46:22 -0800
> Joe Perches wrote:
>
> > (using an email address for James that shouldn't bounce)
> >
> > On Sun, 2016-01-03 at 21:29 +, One Thousand Gnomes wrote:
> > > > > I would beg to differ. As a tool
This is an odd one..
Out of memory: Kill process 5861 (trinity-c10) score 504 or sacrifice child
BUG: spinlock recursion on CPU#1, trinity-c8/8828
lock: 0x8800a3635410, .magic: dead4ead, .owner: trinity-c8/8828,
.owner_cpu: 1
CPU: 1 PID: 8828 Comm: trinity-c8 Not tainted 4.4.0-rc7-gelk-debug
From: Borislav Petkov
... from the final ELF image's symbol table as they're not really needed
there.
Before:
$ readelf -a vmlinux | grep verify_cpu
43: 810001a9 0 NOTYPE LOCAL DEFAULT1 verify_cpu
45: 8100028f 0 NOTYPE LOCAL DEFAULT1
verify_cpu_no_lo
Hi Wolfram,
On 01/03/2016 12:45 PM, Wolfram Sang wrote:
On Wed, Dec 16, 2015 at 06:49:59PM -0600, Suravee Suthikulanit wrote:
Mika,
On 12/16/2015 8:54 AM, Mika Westerberg wrote:
On Wed, Dec 16, 2015 at 08:29:38AM -0600, Suravee Suthikulpanit wrote:
On 12/16/2015 03:16 AM, Mika Westerberg w
On 12/23/2015 09:04 PM, Guenter Roeck wrote:
Commit 2a037f310bab ("MIPS: VDSO: Fix build error") tries to fix a build
error seen with binutils 2.24 and earlier. However, the fix does not work,
and again results in the already known build errors if the kernel is built
with an earlier version of bi
The lifetime of the watchdog device pointer is different from the lifetime
of its character device. Remove it entirely to avoid race conditions, and
to make sure that drivers don't start to use it again.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a mes
The lifetime of the watchdog device pointer is different from the lifetime
of its character device. Remove it entirely to avoid race conditions.
Signed-off-by: Guenter Roeck
---
Documentation/watchdog/watchdog-kernel-api.txt | 2 --
drivers/watchdog/watchdog_core.c | 8
dr
The watchdog core now supports creating driver specific sysfs attributes
when creating the watchdog device.
Signed-off-by: Guenter Roeck
---
drivers/watchdog/ziirave_wdt.c | 20 +++-
1 file changed, 3 insertions(+), 17 deletions(-)
diff --git a/drivers/watchdog/ziirave_wdt.c b/d
The Zodiac watchdog driver attaches additional sysfs attributes to the
watchdog device. This has a number of problems: The watchdog device
lifetime differs from the driver lifetime, and the device structure
should therefore not be accessed from drivers. Also, creating sysfs
attributes after driver
Hi Ted,
After merging the ext4 tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
fs/ext4/ioctl.c: In function 'ext4_ioctl_setproject':
fs/ext4/ioctl.c:399:26: error: implicit declaration of function 'dqget'
[-Werror=implicit-function-declaration]
transfer_to[PRJQUOTA] =
On Sat, Jan 02, 2016 at 08:39:21PM -0800, Dmitry Torokhov wrote:
> On Thu, Dec 31, 2015 at 03:36:47AM +0530, Aniroop Mathur wrote:
> > This patch introduces concept to drop partial events in evdev handler
> > itself after emptying the buffer which are dropped by all evdev
> > clients in userspace a
The WinSystems WS16C48 device provides 48 lines of digital I/O. In
addition, the first 24 lines may be used for interrupt-handled edge
detection; rising edge detection and falling edge detection are
supported.
This driver provides GPIO and IRQ support for these 48 channels of
digital I/O. The base
This patch adds support for hidma engine. The driver consists of two
logical blocks. The DMA engine interface and the low-level interface.
The hardware only supports memcpy/memset and this driver only support
memcpy interface. HW and driver doesn't support slave interface.
Signed-off-by: Sinan Kay
Add debugfs hooks for debugging the execution behavior of the DMA
channel. The debugfs hooks get initialized by the probe function and
uninitialized by the remove function.
A stats file is created in debugfs. The stats file will show the
information about each HIDMA channel as well as each asynchr
The Qualcomm Technologies HIDMA device has been designed
to support virtualization technology. The driver has been
divided into two to follow the hardware design.
1. HIDMA Management driver
2. HIDMA Channel driver
Each HIDMA HW consists of multiple channels. These channels
share some set of commo
Add documentation for the Qualcomm Technologies HIDMA driver.
Signed-off-by: Sinan Kaya
Acked-by: Rob Herring
---
.../devicetree/bindings/dma/qcom_hidma_mgmt.txt| 79 ++
1 file changed, 79 insertions(+)
create mode 100644 Documentation/devicetree/bindings/dma/qcom_hidma
In order to create a relationship model between the channels and the
management object, we are adding support for object hierarchy to the
drivers. This patch simplifies the userspace application development.
We will not have to traverse different firmware paths based on device
tree or ACPI baed ker
The Qualcomm Technologies HIDMA device has been designed to support
virtualization technology. The driver has been divided into two to follow
the hardware design.
1. HIDMA Management driver
2. HIDMA Channel driver
Each HIDMA HW consists of multiple channels. These channels share some set
of commo
This patch implements the hardware hooks for the HIDMA channel driver.
The main functions of interest are:
- hidma_ll_init
- hidma_ll_request
- hidma_ll_queue_request
- hidma_ll_hw_start
OS layer calls the hidma_ll_init function during probe to set up the
hardware. At this moment, the number of s
Creating a QCOM directory for all QCOM DMA source files.
Signed-off-by: Sinan Kaya
Reviewed-by: Andy Gtoss
---
drivers/dma/Kconfig| 11 ++-
drivers/dma/Makefile | 2 +-
drivers/dma/qcom/Kconfig | 8
d
Hi Vinod,
On 1/3/2016 7:06 PM, Sinan Kaya wrote:
> The Qualcomm Technologies HIDMA device has been designed
> to support virtualization technology. The driver has been
> divided into two to follow the hardware design.
>
> 1. HIDMA Management driver
> 2. HIDMA Channel driver
>
> Each HIDMA HW con
Hi, Yu,
Chao Yu writes:
> Hi Ying,
>
>> -Original Message-
>> From: kernel test robot [mailto:ying.hu...@linux.intel.com]
>> Sent: Monday, December 28, 2015 9:40 AM
>> To: Chao Yu
>> Cc: l...@01.org; LKML; Jaegeuk Kim
>> Subject: [lkp] [f2fs] 75cd4e098d: xfstests.generic.042.fail
>>
>>
On Fri, Jan 01, 2016 at 11:36:13AM +0200, Michael S. Tsirkin wrote:
> On Mon, Dec 28, 2015 at 08:35:13AM +0900, Minchan Kim wrote:
> > In balloon_page_dequeue, pages_lock should cover the loop
> > (ie, list_for_each_entry_safe). Otherwise, the cursor page could
> > be isolated by compaction and the
Hi Ying,
> -Original Message-
> From: Huang, Ying [mailto:ying.hu...@intel.com]
> Sent: Monday, January 04, 2016 8:17 AM
> To: Chao Yu
> Cc: 'Jaegeuk Kim'; l...@01.org; 'LKML'
> Subject: Re: [LKP] [lkp] [f2fs] 75cd4e098d: xfstests.generic.042.fail
>
> Hi, Yu,
>
> Chao Yu writes:
>
> >
On 2016/1/4 0:08, Geliang Tang wrote:
This patch makes /proc/cgroups aligned like this:
$ cat /proc/cgroups
#subsys_namehierarchy num_cgroups enabled
cpuset 11 1 1
cpu2 1 1
cpuacct
This adds two bits of fixup class information to a fixup entry,
generalizing the uaccess_err hack currently in place.
Forward-ported-from-3.9-by: Tony Luck
Signed-off-by: Andy Lutomirski
---
arch/x86/include/asm/asm.h | 70 ++
arch/x86/mm/extable.c
Make use of the EXTABLE_FAULT exception table entries. This routine
returns a structure to indicate the result of the copy:
struct mcsafe_ret {
u64 trapnr;
u64 remain;
};
If the copy is successful, then both 'trapnr' and 'remain' are zero.
If we faulted during the copy, then 'tra
Extend the severity checking code to add a new context IN_KERN_RECOV
which is used to indicate that the machine check was triggered by code
in the kernel with a EXTABLE_CLASS_FAULT fixup entry.
Major re-work to the tail code in do_machine_check() to make all this
readable/maintainable. One functio
Make per-class functions for exception table fixup. Add #defines
and general prettiness to make it clear how all the parts tie
together.
Add a new class that fills %rax with the fault number of the exception.
Signed-off-by: Tony Luck
---
arch/x86/include/asm/asm.h | 24 ++-
arch
This series is initially targeted at the folks doing filesystems
on top of NVDIMMs. They really want to be able to return -EIO
when there is a h/w error (just like spinning rust, and SSD does).
I plan to use the same infrastructure to write a machine check aware
"copy_from_user()" that will SIGBUS
Hi Marcin,
On Fri, Jan 01, 2016 at 04:03:21AM +0100, Marcin Ślusarz wrote:
> Steam frequently puts game binaries in folders with spaces.
>
> Note: "(deleted)" markers are now treated as part of the file name.
>
> It probably worked before 6064803313bad9ae4cae233a9d56678adb2b6e7c
> ("perf tools:
Normally, me doing an eighth release candidate means that there is
some unresolved issue that still needs more time to get fixed. This
time around, it just means that I want to make sure that everybody is
back from the holidays and there isn't anything pending, and that
people have time to get thei
On Wed, Dec 30, 2015 at 9:59 AM, Andy Lutomirski wrote:
> This adds two bits of fixup class information to a fixup entry,
> generalizing the uaccess_err hack currently in place.
>
> Forward-ported-from-3.9-by: Tony Luck
> Signed-off-by: Andy Lutomirski
Crivens! I messed up when "git cherrypick
On Thu, 2015-12-31 at 15:24 +1100, Stephen Rothwell wrote:
> Hi James,
>
> Today's linux-next merge of the security tree got a conflict in:
>
> security/integrity/ima/ima_fs.c
>
> between commit:
>
> 3bc8f29b149e ("new helper: memdup_user_nul()")
>
> from the vfs tree and commit:
>
> 38
On 2015/12/31 15:13, Jason Wang wrote:
This patch tries to implement an device IOTLB for vhost. This could be
used with for co-operation with userspace(qemu) implementation of
iommu for a secure DMA environment in guest.
The idea is simple. When vhost meets an IOTLB miss, it will request
the ass
Hi all,
On Thu, 31 Dec 2015 13:30:22 +1100 Stephen Rothwell
wrote:
>
> Hi Doug,
>
> Today's linux-next merge of the rdma tree got conflicts in a quite a
> few files between (mostly, I think) commit:
>
> 6c7b6d2d442c ("IB: merge struct ib_device_attr into struct ib_device")
>
> from the nfsd
FYI, we noticed the below changes on
https://github.com/0day-ci/linux
Rainer-Weikusat/af_unix-Fix-splice-bind-deadlock/20151228-041437
commit 039b21aaee6515d0197e26321204f319b4ea6e9e ("af_unix: Fix splice-bind
deadlock")
The commit failed for the bind01 test case of LTP syscalls test suite.
To
On 2016/1/1 20:09, Chen Yu wrote:
Commit be4c9dd7aee5 ("cpuset: enable onlined cpu/node in effective masks")
leverages cpuset's cpus_allowed and its parent's effective_cpus to calculate
the new_cpus by:
cpumask_and(&new_cpus, cs->cpus_allowed, parent_cs(cs)->effective_cpus);
However cpus_allowe
Hi Mimi,
On Sun, 03 Jan 2016 20:37:20 -0500 Mimi Zohar wrote:
>
> FYI, I pushed out Petko's patch to linux-integrity/next earlier today.
> His patch moves taking the ima_write_mutex to after the the call to
> copy_from_user(), as discussed. This obviously won't fix the conflict
> with Al's patch
> -Original Message-
> From: Radim Krčmář [mailto:rkrc...@redhat.com]
> Sent: Thursday, December 24, 2015 1:22 AM
> To: Wu, Feng
> Cc: pbonz...@redhat.com; k...@vger.kernel.org; linux-
> ker...@vger.kernel.org
> Subject: Re: [PATCH v2 2/2] KVM: x86: Add lowest-priority support for vt-d
>
Hi Zefan,
> -Original Message-
> From: Zefan Li [mailto:lize...@huawei.com]
> Sent: Monday, January 04, 2016 9:52 AM
> To: Chen, Yu C; cgro...@vger.kernel.org
> Cc: linux-kernel@vger.kernel.org; Vlastimil Babka; Rik van Riel; Joonsoo Kim;
> David Rientjes; Vishnu Pratap Singh; Pintu Kumar;
On 2016/1/1 20:09, Chen Yu wrote:
Commit be4c9dd7aee5 ("cpuset: enable onlined cpu/node in effective
masks") leverages cpuset's cpus_allowed and its parent's
effective_cpus to calculate the new_cpus by:
cpumask_and(&new_cpus, cs->cpus_allowed,
parent_cs(cs)->effective_cpus);
However cpus_allowe
Hi,
> From: David Lang [mailto:da...@lang.hm]
> Sent: Sunday, January 3, 2016 2:45 PM
>
> what is ACPICA and why should we care about divergence between it and the
> linux
> upstream? Where is it to be found?
[Lv Zheng]
You can find ACPICA at: https://acpica.org.
Source code of ACPICA can be fou
Hi, Rafael
> From: Rafael J. Wysocki [mailto:r...@rjwysocki.net]
> Sent: Friday, January 1, 2016 11:05 AM
> Subject: Re: [PATCH 00/42] ACPICA: 20151218 Release
>
> On Tuesday, December 29, 2015 01:52:19 PM Lv Zheng wrote:
> > The 20151218 ACPICA kernel-resident subsystem updates are linuxized bas
Hi all,
Today's linux-next merge of the integrity tree got a conflict in:
security/integrity/ima/ima_fs.c
between commit:
3bc8f29b149e ("new helper: memdup_user_nul()")
from the vfs tree and commit:
6427e6c71c8b ("ima: ima_write_policy() limit locking")
from the integrity tree.
I fixe
On 01/03/2016 08:44 PM, Stephen Rothwell wrote:
> Hi all,
>
> On Thu, 31 Dec 2015 13:30:22 +1100 Stephen Rothwell
> wrote:
>>
>> Hi Doug,
>>
>> Today's linux-next merge of the rdma tree got conflicts in a quite a
>> few files between (mostly, I think) commit:
>>
>> 6c7b6d2d442c ("IB: merge str
This patch implement hw_reset function for DesignWare
MMC controller. By adding this feature, mmc blk can
do some basic recovery.
>From Synopsys DesignWare Cores Mobile Storage Host Databook
(Section 7.4.4), we get the details:
1. Program CMD12 to end any transfer in process.
2. Wait for DTO, even
[Just cc'ing the security tree maintainer, since this will soon be in
his tree and is related to a conflict between that tree and the vfs
tree.]
On Mon, 4 Jan 2016 13:52:21 +1100 Stephen Rothwell
wrote:
>
> Hi all,
>
> Today's linux-next merge of the integrity tree got a conflict in:
>
> sec
On Thu, 2015-12-31 at 22:19 +0800, Daniel Kurtz wrote:
> On Wed, Dec 30, 2015 at 8:36 PM, Henry Chen wrote:
> >
> > The STAUPD_TRIG will be enable when WDT_INT enable on probe function, if
> > doesn't enable STAUPD_PRD together, interrupt will be triggered because
> > STAUPD timeout. To avoid unex
For supporting the usb charger, it adds the usb_charger_init() and
usb_charger_exit() functions for usb charger initialization and exit.
It will report to the usb charger when the gadget state is changed,
then the usb charger can do the power things.
Introduce a callback 'get_charger_type' which
This patch introduces the usb charger driver based on usb gadget that
makes an enhancement to a power driver. It works well in practice but
that requires a system with suitable hardware.
The basic conception of the usb charger is that, when one usb charger
is added or removed by reporting from the
When the usb gadget supporting for usb charger is ready, the usb charger
should get the type by the 'get_charger_type' callback which is implemented
by the usb gadget operations, and get the usb charger pointer from struct
'usb_gadget'.
Signed-off-by: Baolin Wang
---
drivers/usb/gadget/charger.c
Integrate with the newly added USB charger interface to limit the current
we draw from the USB input based on the input device configuration
identified by the USB stack, allowing us to charge more quickly from high
current inputs without drawing more current than specified from others.
Signed-off-
Currently the Linux kernel does not provide any standard integration of this
feature that integrates the USB subsystem with the system power regulation
provided by PMICs meaning that either vendors must add this in their kernels
or USB gadget devices based on Linux (such as mobile phones) may not b
On Mon, Jan 04, 2016 at 01:52:21PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the integrity tree got a conflict in:
>
> security/integrity/ima/ima_fs.c
>
> between commit:
>
> 3bc8f29b149e ("new helper: memdup_user_nul()")
>
> from the vfs tree and commit:
>
dw_mmc driver never use this macro, so remove it from
multi_v7_defconfig
Signed-off-by: Shawn Lin
---
arch/arm/configs/multi_v7_defconfig | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/arm/configs/multi_v7_defconfig
b/arch/arm/configs/multi_v7_defconfig
index 69a22fd..c362199 100644
-
dw_mmc driver never use this macro, so we remove it from
arch/arm64/configs/defconfig
Signed-off-by: Shawn Lin
---
arch/arm64/configs/defconfig | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
index bdd7aa3..2c56551 100644
--- a/arch
101 - 200 of 286 matches
Mail list logo
