From: Tom Zanussi [mailto:tom.zanu...@linux.intel.com]
>
>Hi Masami,
>
>On Thu, 2015-10-22 at 20:17 +0900, Masami Hiramatsu wrote:
>> Hi Tom,
>>
>> I've tested your series of the hist trigger v10 with
>> these testcases included in the couple of patches, which
>> tests following features.
>>
>>
On Fri, Oct 23, 2015 at 08:00:09AM +0300, Dan Carpenter wrote:
> On Fri, Oct 23, 2015 at 10:00:03AM +0530, Nilesh Kokane wrote:
> > Fixed- Return of an errno should typically be negative (ie: return -EAGAIN)
> >
>
> The changelog needs to describe the use visible effects of this change.
>
I
On Wed, Oct 21, 2015 at 11:10:03AM +0100, Sudeep Holla wrote:
> Though the mmc core driver should/will continue to support the legacy
> "nvidia,wakeup-source" property to enable SDIO as the wakeup source, we
> need to add support for the new standard property "wakeup-source".
>
> This patch adds
Fixed the braces issue for single statement.
Signed-off-by: Nilesh Kokane
---
drivers/staging/media/lirc/lirc_imon.c | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/drivers/staging/media/lirc/lirc_imon.c
b/drivers/staging/media/lirc/lirc_imon.c
index 62ec9f7..a6cae49
在 2015年10月23日 12:04, Doug Anderson 写道:
Caesar,
On Thu, Oct 22, 2015 at 9:54 PM, Caesar Wang wrote:
We need the OTP pin is gpio state before resetting the TSADC controller,
since the tshut polarity will generate a high signal.
Says:
The TSHUT temperature is setting more than 80 degree, the
在 2015年10月23日 12:04, Doug Anderson 写道:
Caesar,
On Thu, Oct 22, 2015 at 9:54 PM, Caesar Wang wrote:
We need the OTP pin is gpio state before resetting the TSADC controller,
since the tshut polarity will generate a high signal.
Says:
The TSHUT temperature is setting more than 80 degree, the
mcp794xx alarm registers must be written in BCD format. However, the
alarm programming logic neglected this by adding one to the value
after bin2bcd conversion has been already done, writing bad values
to month register in case the alarm being set is in October. In this
case, the alarm month value
On Fri, Oct 23, 2015 at 1:31 PM, Bjorn Helgaas wrote:
> Hi Ley,
>
> On Thu, Oct 22, 2015 at 05:27:28PM +0800, Ley Foon Tan wrote:
>> This patch adds the Altera PCIe host controller driver.
>
>> +static void altera_pcie_fixups(struct pci_bus *bus)
>> +{
>> + struct pci_dev *dev;
>> +
>> +
On Fri, Oct 23, 2015 at 10:39:19AM +0900, Krzysztof Kozlowski wrote:
> SRAM bindings for various SoCs, using the mmio-sram genalloc
> API, are spread over different places - per SoC vendor. Since all of
> these are quite similar (they depend on mmio-sram) move them to a common
> place.
>
>
On Fri, Oct 23, 2015 at 11:50:37AM +0800, Chen-Yu Tsai wrote:
> Hi everyone,
>
> This is v4 of the simplefb regulator support series. This series adds
> regulator claiming and enabling support for simplefb.
>
> Changes since v4:
> - Fixed inverted logic when testing the property name.
> -
Hi Robin,
On 2015/10/20 23:02, Robin Murphy wrote:
> On 20/10/15 09:45, Chen Feng wrote:
>> iommu/hisilicon: Add hi6220-SoC smmu driver
>
>> +
>> +static int hi6220_smmu_attach_dev(struct iommu_domain *domain,
>> + struct device *dev)
>> +{
>> +dev->archdata.iommu =
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Andrey Vagin
[ Upstream commit e9193d60d363e4dff75ff6d43a48f22be26d59c7 ]
Now send with MSG_PEEK can return data from multiple SKBs.
Unfortunately we take into account the
> So I checked the x86 code: the driver is always loaded as soon as the
> hardware is there (looking at PCI device IDs from the on-chip
> northbridge, for instance). The trick here is to have the Kconfig option
> defaulting to "=n", so a kernel builder would have to explicitly enable
> this.
The G920 can adjust the amount of 'turn' it permits, this patch adds
a sysfs file 'range' to control this.
---
drivers/hid/hid-logitech-hidpp.c | 140 ++-
1 file changed, 139 insertions(+), 1 deletion(-)
diff --git a/drivers/hid/hid-logitech-hidpp.c
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Dave Kleikamp
commit a66d7f724a96d6fd279bfbd2ee488def6b081bea upstream.
Some of the crypto algorithms write to the initialization vector,
but no space has been
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Guillaume Nault
[ Upstream commit e6740165b8f7f06d8caee0fceab3fb9d790a6fed ]
Since commit 2b018d57ff18 ("pppoe: drop PPPOX_ZOMBIEs in pppoe_release"),
pppoe_release()
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
[ Upstream commit 2306c704ce280c97a60d1f45333b822b40281dea ]
reqsk_timer_handler() tests if icsk_accept_queue.listen_opt
is NULL at its beginning.
By the
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
[ Upstream commit c7c49b8fde26b74277188bdc6c9dca38db6fa35b ]
Greg reported crashes hitting the following check in __sk_backlog_rcv()
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Wolfram Sang
commit 36d48fb5766aee9717e429f772046696b215282d upstream.
The core may register clients attached to this master which may use
funtionality from
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Pravin B Shelar
[ Upstream commit 6ae459bdaaeebc632b16e54dcbabb490c6931d61 ]
VXLAN device can receive skb with checksum partial. But the checksum
offset could be in outer
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
[ Upstream commit 29c6852602e259d2c1882f320b29d5c3fec0de04 ]
Before allowing lockless LISTEN processing, we need to make
sure to arm the SYN_RECV timer before
4.2-stable review patch. If anyone has any objections, please let me know.
--
From: Pravin B Shelar
[ Upstream commit 6ae459bdaaeebc632b16e54dcbabb490c6931d61 ]
VXLAN device can receive skb with checksum partial. But the checksum
offset could be in outer
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Pravin B Shelar
[ Upstream commit 6ae459bdaaeebc632b16e54dcbabb490c6931d61 ]
VXLAN device can receive skb with checksum partial. But the checksum
offset could be in outer
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Chris Mason
commit dc6c5fb3b514221f2e9d21ee626a9d95d3418dff upstream.
The code for btrfs inode-resolve has never worked properly for
files with enough hard links to trigger
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Aaron Conole
[ Upstream commit 9f389e35674f5b086edd70ed524ca0f287259725 ]
AF_UNIX sockets now return multiple skbs from recv() when MSG_PEEK flag
is set.
This is
4.2-stable review patch. If anyone has any objections, please let me know.
--
From: "Eric W. Biederman"
[ Upstream commit e332bc67cf5e5e5b71a1aec9750d0791aac65183 ]
As originally written rt6_uncached_list_flush_dev makes no sense when
called with dev ==
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Pravin B Shelar
[ Upstream commit 31b33dfb0a144469dd805514c9e63f4993729a48 ]
Earlier patch 6ae459bda tried to detect void ckecksum partial
skb by comparing pull length to
Hello,
On Fri, Oct 23, 2015 at 01:11:45PM +0200, Michal Hocko wrote:
> > The problem here is not lack
> > of execution resource but concurrency management misunderstanding the
> > situation.
>
> And this sounds like a bug to me.
I don't know. I can be argued either way, the other direction
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
[ Upstream commit c7c49b8fde26b74277188bdc6c9dca38db6fa35b ]
Greg reported crashes hitting the following check in __sk_backlog_rcv()
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Joe Perches
[ Upstream commit 077cb37fcf6f00a45f375161200b5ee0cd4e937b ]
It seems that kernel memory can leak into userspace by a
kmalloc, ethtool_get_strings, then
4.2-stable review patch. If anyone has any objections, please let me know.
--
From: Ivan Mikhaylov
[ Upstream commit 661dfc65f7981481ba2e31aaa702371e82336e56 ]
The size of the MAC register dump used to be the size specified by the
reg property in the device
4.2-stable review patch. If anyone has any objections, please let me know.
--
From: Shaohua Li
commit 424cdc14138088ada1b0e407a2195b2783c6e5ef upstream.
page_counter_memparse() returns pages for the threshold, while
mem_cgroup_usage() returns bytes for memory
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Wolfram Sang
commit 4f7effddf4549d57114289f273710f077c4c330a upstream.
The core may register clients attached to this master which may use
funtionality from
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Shaohua Li
commit 874bbfe600a660cba9c776b3957b1ce393151b76 upstream.
My system keeps crashing with below message. vmstat_update() schedules a delayed
work in current cpu and
4.2-stable review patch. If anyone has any objections, please let me know.
--
From: Mika Westerberg
commit 56d4b8a24cef5d66f0d10ac778a520d3c2c68a48 upstream.
ACPI SSCN/FMCN methods were originally added because then the platform can
provide
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Geert Uytterhoeven
commit 631d8b674f5f8235e9cb7e628b0fe9e5200e3158 upstream.
When compiling a MMU kernel with CPU_HAS_ADDRESS_SPACES=n (e.g. "MMU=y
allnoconfig": "echo
Here is another update of the richacl patch queue. I would like to ask for
feedback so that the core and local filesystem code (patches 1-25) can be
merged in the 4.4 merge window.
Changes since the last posting (http://lwn.net/Articles/661078/):
* On ext4, filesystems with the richacl feature
Richacls support permissions that allow to take ownership of a file,
change the file permissions, and set the file timestamps. Support that
by introducing new permission mask flags and by checking for those mask
flags in inode_change_ok().
Signed-off-by: Andreas Gruenbacher
The vfs does not apply the umask for file systems that support acls. The
test used for this used to be called IS_POSIXACL(). Switch to a new
IS_ACL() test to check for either posix acls or richacls instead. Add a new
MS_RICHACL flag and IS_RICHACL() test for richacls alone. The IS_POSIXACL()
test
We will need to call iop->permission and iop->get_acl from
inode_change_ok() for additional permission checks, and both take a
non-const inode.
Signed-off-by: Andreas Gruenbacher
Reviewed-by: J. Bruce Fields
---
fs/attr.c | 2 +-
Map between "system.richacl" xattrs and the in-kernel representation.
Signed-off-by: Andreas Gruenbacher
---
fs/Makefile| 2 +-
fs/richacl_xattr.c | 220 +
fs/xattr.c | 34
Automatic Inheritance (AI) allows changes to the acl of a directory to
propagate down to children.
This is mostly implemented in user space: when a process changes the
permissions of a directory and Automatic Inheritance is enabled for that
directory, the process must propagate those changes to
Doing a chmod() sets the file mode, which includes the file permission
bits. When a file has a richacl, the permissions that the richacl
grants need to be limited to what the new file permission bits allow.
This is done by setting the file masks in the richacl to what the file
permission bits
ACLs are considered equivalent to file modes if they only consist of
owner@, group@, and everyone@ entries, the owner@ permissions do not
depend on whether the owner is a member in the owning group, and no
inheritance flags are set. This test is used to avoid storing richacls
if the acl can be
Cache richacls in struct inode so that this doesn't have to be done
individually in each filesystem. This is similar to POSIX ACLs.
Signed-off-by: Andreas Gruenbacher
---
fs/inode.c | 11 ++--
fs/posix_acl.c | 2 +-
fs/richacl_base.c | 4
Hook the richacl permission checking function into the vfs.
Signed-off-by: Andreas Gruenbacher
---
fs/namei.c | 51 +--
fs/posix_acl.c | 6 +++---
2 files changed, 52 insertions(+), 5 deletions(-)
diff --git a/fs/namei.c
This patch-set extends the EINJ driver to allow injecting a memory
error to NVDIMM. It first extends iomem resource interface to support
checking a NVDIMM region.
Patch 1/3 changes region_intersects() to accept non-RAM regions, and
adds region_intersects_ram().
Patch 2/3 adds
Add region_intersects_pmem(), which checks if a specified address
range is persistent memory registered as "Persistent Memory" in
the iomem_resource list.
Note, it does not support legacy persistent memory registered as
"Persistent Memory (legacy)". It can be supported by extending
this function
On Thu, 15 Oct 2015, Franklin S Cooper Jr wrote:
> GPMC address information is provided by device tree. No longer need
> to include this information within hwmod.
>
> Signed-off-by: Franklin S Cooper Jr
Thanks, queued.
- Paul
--
To unsubscribe from this list: send the line
On Thu, 15 Oct 2015, Franklin S Cooper Jr wrote:
> ELM address information is provided by device tree. No longer need
> to include this information within hwmod.
>
> Signed-off-by: Franklin S Cooper Jr
The OMAP4 DTS files don't have the ELM address space declared. I'm going
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Jeff Layton
commit ee296d7c5709440f8abd36b5b65c6b3e388538d9 upstream.
They just call file_inode and then the corresponding *_inode_file_wait
function. Just make
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Wolfram Sang
commit eadd709f5d2e8aebb1b7bf49460e97a68d81a9b0 upstream.
The core may register clients attached to this master which may use
funtionality from
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Joe Perches
[ Upstream commit 077cb37fcf6f00a45f375161200b5ee0cd4e937b ]
It seems that kernel memory can leak into userspace by a
kmalloc, ethtool_get_strings, then
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Shaohua Li
commit 424cdc14138088ada1b0e407a2195b2783c6e5ef upstream.
page_counter_memparse() returns pages for the threshold, while
mem_cgroup_usage() returns bytes for memory
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Russell King
commit 8996eafdcbad149ac0f772fb1649fbb75c482a6a upstream.
Unlike shash algorithms, ahash drivers must implement export
and import as their descriptors
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Mika Westerberg
commit 56d4b8a24cef5d66f0d10ac778a520d3c2c68a48 upstream.
ACPI SSCN/FMCN methods were originally added because then the platform can
provide
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Ben Skeggs
commit f231976c2e8964ceaa9250e57d27c35ff03825c2 upstream.
We need to do this in order to prevent accesses to the device while it's
powered down. Userspace may
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Dave Airlie
commit bc8c131ccdd62d4ed4f33c6b50f92907e7c32dee upstream.
This allows tiled monitors to work with radeon once mst is enabled.
Signed-off-by: Dave Airlie
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Daniel Borkmann
[ Upstream commit 93d08b6966cf730ea669d4d98f43627597077153 ]
When sockets have a native eBPF program attached through
setsockopt(sk, SOL_SOCKET,
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Dave Airlie
commit ae491542cbbbcca0ec8938c37d4079a985e58440 upstream.
This zeroes the msg so no random stack data ends up getting
sent, it also limits the function to not
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Alex Deucher
commit 51a4726b04e880fdd9b4e0e58b13f70b0a68a7f5 upstream.
They were added relatively early in the driver init process
which meant that in some cases the
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Frederic Weisbecker
commit 90b62b5129d5cb50f62f40e684de7a1961e57197 upstream.
"CHECK" suggests it's only used as a comparison mask. But now it's used
further as a
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Aaron Conole
[ Upstream commit 9f389e35674f5b086edd70ed524ca0f287259725 ]
AF_UNIX sockets now return multiple skbs from recv() when MSG_PEEK flag
is set.
This is
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Ilya Dryomov
commit 3ebe138ac642a195c7f2efdb918f464734421fd6 upstream.
If rbd_dev_image_probe() in rbd_dev_probe_parent() fails, header_name
is freed twice: once in
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Wolfram Sang
commit eadd709f5d2e8aebb1b7bf49460e97a68d81a9b0 upstream.
The core may register clients attached to this master which may use
funtionality from
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Mika Westerberg
commit 56d4b8a24cef5d66f0d10ac778a520d3c2c68a48 upstream.
ACPI SSCN/FMCN methods were originally added because then the platform can
provide
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Wolfram Sang
commit 4f7effddf4549d57114289f273710f077c4c330a upstream.
The core may register clients attached to this master which may use
funtionality from
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
[ Upstream commit c7c49b8fde26b74277188bdc6c9dca38db6fa35b ]
Greg reported crashes hitting the following check in __sk_backlog_rcv()
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Alexander Couzens
[ Upstream commit 06a15f51cf3618e32a73871ee6a547ef7fd902b5 ]
There is a small chance that tunnel_free() is called before tunnel->del_work
scheduled
resulting
When plugged in the Logitech G920 wheel starts with USBID 046d:c261
and behaviors as a vendor specific class. If a 'magic' byte sequence
is sent the wheel will detach and reconnect as a HID device with the
USBID 046d:c262.
---
drivers/input/joystick/xpad.c | 16
1 file changed,
On Thu, Oct 22, 2015 at 01:30:42PM +0200, Jens Kuske wrote:
> On 22/10/15 11:14, Maxime Ripard wrote:
> > On Thu, Oct 22, 2015 at 10:57:45AM +0200, Jean-Francois Moine wrote:
> >> On Thu, 22 Oct 2015 10:47:35 +0200
> >> Maxime Ripard wrote:
> >>
> >>> Not really.
4.2-stable review patch. If anyone has any objections, please let me know.
--
From: Alexei Starovoitov
[ Upstream commit 6bf0577374cfb6c2301dbf4934a4f23ad3d72763 ]
Similar to commit c29390c6dfee ("xps: must clear sender_cpu before forwarding")
the
4.2-stable review patch. If anyone has any objections, please let me know.
--
From: WANG Cong
[ Upstream commit d40496a56430eac0d330378816954619899fe303 ]
Similar to commit c29390c6dfee ("xps: must clear sender_cpu before forwarding")
the
4.2-stable review patch. If anyone has any objections, please let me know.
--
From: Konstantin Khlebnikov
[ Upstream commit 598c12d0ba6de9060f04999746eb1e015774044b ]
When openvswitch tries allocate memory from offline numa node 0:
stats =
4.2-stable review patch. If anyone has any objections, please let me know.
--
From: Joe Perches
[ Upstream commit 077cb37fcf6f00a45f375161200b5ee0cd4e937b ]
It seems that kernel memory can leak into userspace by a
kmalloc, ethtool_get_strings, then
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Alexander Couzens
[ Upstream commit 06a15f51cf3618e32a73871ee6a547ef7fd902b5 ]
There is a small chance that tunnel_free() is called before tunnel->del_work
scheduled
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Aaron Conole
[ Upstream commit 4613012db1d911f80897f9446a49de817b2c4c47 ]
As suggested by Eric Dumazet this change replaces the
#define with a static inline function to
This is the start of the stable review cycle for the 4.2.5 release.
There are 54 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made by Sun Oct 25 17:45:07 UTC 2015.
Anything
4.2-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
[ Upstream commit 2306c704ce280c97a60d1f45333b822b40281dea ]
reqsk_timer_handler() tests if icsk_accept_queue.listen_opt
is NULL at its beginning.
By the
4.2-stable review patch. If anyone has any objections, please let me know.
--
From: Guillaume Nault
[ Upstream commit e6740165b8f7f06d8caee0fceab3fb9d790a6fed ]
Since commit 2b018d57ff18 ("pppoe: drop PPPOX_ZOMBIEs in pppoe_release"),
pppoe_release()
4.2-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
[ Upstream commit c7c49b8fde26b74277188bdc6c9dca38db6fa35b ]
Greg reported crashes hitting the following check in __sk_backlog_rcv()
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Michel Stam
[ Upstream commit 3cc81d85ee01e5a0b7ea2f4190e2ed1165f53c31 ]
I've noticed every time the interface is set to 'up,', the kernel
reports that the link speed is set
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Mike Snitzer
commit ba30670f4d5292c4e7f7980bbd5071f7c4794cdd upstream.
Fixes: ac8c3f3df ("dm thin: generate event when metadata threshold passed")
Signed-off-by: Mike
Hello, Tetsuo.
On Fri, Oct 23, 2015 at 09:25:11PM +0900, Tetsuo Handa wrote:
> WQ_MEM_RECLAIM only guarantees that a "struct task_struct" is preallocated
> in order to avoid failing to allocate it on demand due to a GFP_KERNEL
> allocation? Is this correct?
>
> WQ_CPU_INTENSIVE only guarantees
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Ilya Dryomov
commit 3ebe138ac642a195c7f2efdb918f464734421fd6 upstream.
If rbd_dev_image_probe() in rbd_dev_probe_parent() fails, header_name
is freed twice: once in
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Aaron Conole
[ Upstream commit 4613012db1d911f80897f9446a49de817b2c4c47 ]
As suggested by Eric Dumazet this change replaces the
#define with a static inline function to
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Charles Keepax
[ Upstream commit 436c2a5036b6ffe813310df2cf327d3b69be0734 ]
commit 3cc81d85ee01 ("asix: Don't reset PHY on if_up for ASIX 88772")
causes
As per the change to the rk3288 USB phy driver, we can now enable the
PHYs as reset providers. Do so.
Signed-off-by: Douglas Anderson
---
arch/arm/boot/dts/rk3288.dtsi | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/arm/boot/dts/rk3288.dtsi
4.2-stable review patch. If anyone has any objections, please let me know.
--
From: Thomas Gleixner
commit 56fd16cabac9cd8f15e2902898a9d0cc96e2fa70 upstream.
timekeeping_init() can set the wall time offset, so we need to
increment the clock_was_set_seq
4.2-stable review patch. If anyone has any objections, please let me know.
--
From: Steve Wise
commit c91aed9896946721bb30705ea2904edb3725dd61 upstream.
The server rdma_read_chunk_lcl() and rdma_read_chunk_frmr() functions
were not taking into
4.2-stable review patch. If anyone has any objections, please let me know.
--
From: Ilya Dryomov
commit 3ebe138ac642a195c7f2efdb918f464734421fd6 upstream.
If rbd_dev_image_probe() in rbd_dev_probe_parent() fails, header_name
is freed twice: once in
The "host1" port (AKA the dwc2 port that isn't the OTG port) on rk3288
has a hardware errata that causes everything to get confused when we get
a remote wakeup. It appears that the "port reset" bit that's in the USB
phy (located in the rk3288 GRF) fixes things up and appears safe to do.
This
4.2-stable review patch. If anyone has any objections, please let me know.
--
From: Steve Capper
commit 1a541b4e3cd6f5795022514114854b3e1345f24e upstream.
6910fa1 ("arm64: enable PTE type bit in the mask for pte_modify") fixes
a problem whereby a
4.2-stable review patch. If anyone has any objections, please let me know.
--
From: Will Deacon
commit b6dd8e0719c0d2d01429639a11b7bc2677de240c upstream.
Commit df057cc7b4fa ("arm64: errata: add module build workaround for
erratum #843419") sets
The "host1" port (AKA the dwc2 port that isn't the OTG port) on rk3288
has a hardware errata that causes everything to get confused when we get
a remote wakeup. It appears that the "port reset" bit that's in the USB
phy (located in the rk3288 GRF) fixes things up and appears safe to do.
We
On Wed, 21 Oct 2015 17:18:36 +0800
Tang Chen wrote:
>
> On 10/21/2015 05:00 PM, Vlastimil Babka wrote:
> > On 10/21/2015 04:20 AM, Changsheng Liu wrote:
> >>
> >>
> >> 在 2015/10/15 0:18, Vlastimil Babka 写道:
> >>> On 10/12/2015 08:58 AM, Changsheng Liu wrote:
>
On 10/21/2015 09:37 AM, Lan Tianyu wrote:
This patchset is to propose a new solution to add live migration support for
82599
SRIOV network card.
Im our solution, we prefer to put all device specific operation into VF and
PF driver and make code in the Qemu more general.
VF status migration
Hi,
On Fri, Oct 23, 2015 at 08:59:09AM -0500, Andrew F. Davis wrote:
> This series adds a helper macro to the SPI core that assigns the owner
> in spi_drivers so individual drivers do not have to do this, this is
> similar to other subsystems like platform_driver and i2c_driver that
> have made
In the write-through case, change the acl so that owner@ is granted the
permissions set in the owner mask (to match what the permission check
algorithm grants the owner).
Signed-off-by: Andreas Gruenbacher
Reviewed-by: J. Bruce Fields
---
The trailing everyone@ allow ace can grant permissions to all file
classes including the owner and group class. Before we can apply the
other mask to this entry to turn it into an "other class" entry, we need
to ensure that members of the owner or group class will not lose any
permissions from
801 - 900 of 1620 matches
Mail list logo