Commit 5e572cab92f0bb5 ("tpm: Enable CLKRUN protocol for Braswell
systems") disabled CLKRUN protocol during TPM transactions and re-enabled
once the transaction is completed. But there were still some corner cases
observed where, reading of TPM header failed for savestate command
while going to
-for-tuntap/20180101-105946
config: i386-randconfig-x072-201800 (attached as .config)
compiler: gcc-7 (Debian 7.2.0-12) 7.2.1 20171025
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All warnings (new ones prefixed by >>):
drivers//net/tun.c: In fu
Fix the typo, 'status' should be instead of 'status2'.
Fixes: b0a9c37b0178 ("soundwire: Add slave status handling")
Signed-off-by: Wei Yongjun
---
drivers/soundwire/bus.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git
Move static variable ilb_base_addr to tpm_tis_data.
Signed-off-by: Azhar Shaikh
Reviewed-by: Jarkko Sakkinen
Tested-by: Jarkko Sakkinen
Signed-off-by: Jarkko Sakkinen
Hi Stephen,
Thanks for reporting this.
I have uploaded new patchset to tpmdd mailing list.
Regards,
Azhar Shaikh
>-Original Message-
>From: Stephen Rothwell [mailto:s...@canb.auug.org.au]
>Sent: Monday, January 1, 2018 6:51 PM
>To: Jarkko Sakkinen
>Cc:
Changes from v1:
- Patch 1: "tpm: Keep CLKRUN enabled throughout the duration of transmit_cmd()"
- Add NULL checks before calling clk_toggle callback
- Use IS_ENABLED instead of ifdef in tpm_tis_clkrun_toggle()
- Do not call tpm_platform_begin_xfer() and tpm_platform_end_xfer()
from
Fixes the following sparse warnings:
drivers/tee/tee_shm.c:115:16: warning:
symbol '__tee_shm_alloc' was not declared. Should it be static?
Signed-off-by: Wei Yongjun
---
drivers/tee/tee_shm.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git
On 30/12/17 8:58 PM, "Himanshu Jha" wrote:
>Use dma_zalloc_coherent instead of dma_alloc_coherent followed by memset
>0.
>
>Generated-by: scripts/coccinelle/api/alloc/kzalloc-simple.cocci
>
>Suggested-by: Luis R. Rodriguez
>Signed-off-by:
On Mon, Jan 01, 2018 at 08:05:43PM -0800, Azhar Shaikh wrote:
> - return tpm_chip_register(chip);
> + rc = tpm_chip_register(chip);
> + if (rc && is_bsw())
> + iounmap(priv->ilb_base_addr);
> +
> + return rc;
> out_err:
> tpm_tis_remove(chip);
> + if
On 30/12/17 8:58 PM, "Himanshu Jha" wrote:
>Use dma_zalloc_coherent instead of dma_alloc_coherent followed by memset
>0.
>
>Generated-by: scripts/coccinelle/api/alloc/kzalloc-simple.cocci
>
>Suggested-by: Luis R. Rodriguez
>Signed-off-by:
On 30/12/17 8:58 PM, "Himanshu Jha" wrote:
>Use dma_zalloc_coherent instead of dma_alloc_coherent followed by
>memset 0.
>
>Generated-by: scripts/coccinelle/api/alloc/kzalloc-simple.cocci
>
>Suggested-by: Luis R. Rodriguez
>Signed-off-by:
On Thu 14 Dec 09:33 PST 2017, srinivas.kandaga...@linaro.org wrote:
> From: Srinivas Kandagatla
>
> This patch adds basic support to Q6 ASM (Audio Stream Manager) module on
> Q6DSP. ASM supports up to 8 concurrent streams. each stream can be setup
> as
>-Original Message-
>From: Jason Gunthorpe [mailto:j...@ziepe.ca]
>Sent: Monday, January 1, 2018 8:41 PM
>To: Shaikh, Azhar
>Cc: jarkko.sakki...@linux.intel.com; peterhu...@gmx.de; linux-security-
>mod...@vger.kernel.org; linux-integr...@vger.kernel.org; linux-
We have introduced one interface to get the RTC range, so this patch
exports the valid range supported by RTC hardware to userspace.
Signed-off-by: Baolin Wang
---
Documentation/rtc.txt |2 ++
drivers/rtc/rtc-sysfs.c | 30 ++
2 files
In order to the setting time values are not beyond the limitation
supported by RTC hardware, we introduce one interface to tell the
hardware range to the RTC core, which are used to valid if the
setting time values are in the RTC hardware range.
Moreover we also need the RTC hardware range to
Add the get_range interface for sc27xx RTC driver to tell the RTC
core what is the valid range for RTC hardware device.
Signed-off-by: Baolin Wang
---
drivers/rtc/rtc-sc27xx.c | 10 ++
1 file changed, 10 insertions(+)
diff --git a/drivers/rtc/rtc-sc27xx.c
>From our investigation for all RTC drivers, 1 driver will be expired before
year 2017, 7 drivers will be expired before year 2038, 23 drivers will be
expired before year 2069, 72 drivers will be expired before 2100 and 104
drivers will be expired before 2106. Especially for these early expired
commit 84fe2cab4859 ("cpu_cooling: Drop static-power related stuff")
removed support for static-power in kernel, but it missed reflecting the
same in documentation. Remove the static power related documentation
bits as well.
Reported-by: Javi Merino
Signed-off-by: Viresh
>-Original Message-
>From: linux-integrity-ow...@vger.kernel.org [mailto:linux-integrity-
>ow...@vger.kernel.org] On Behalf Of Shaikh, Azhar
>Sent: Monday, January 1, 2018 9:02 PM
>To: Jason Gunthorpe
>Cc: jarkko.sakki...@linux.intel.com; peterhu...@gmx.de;
-Original Message-
From: Himanshu Jha [mailto:himanshujha199...@gmail.com]
Sent: 30 December 2017 20:59
To: j...@linux.vnet.ibm.com; martin.peter...@oracle.com; aacr...@adaptec.com
Cc: Gurumurthy, Anil ; Kalluru, Sudarsana
;
Hi,
On 12/29/2017 11:58 AM, Kishon Vijay Abraham I wrote:
> Hi,
>
> On Friday 29 December 2017 09:54 AM, Manu Gautam wrote:
>> Hi,
[snip]
>
> suggest using switch in such case.. and not all PHY drivers do specific
> configurations for specific speeds.
>> This looks clumsy.
>> Where as if bits to
On Sat, 2017-12-30 at 09:03 +1100, Benjamin Herrenschmidt wrote:
> On Tue, 2017-12-26 at 17:32 -0800, Stephen Boyd wrote:
> > > I noticed we do have a few i2c based clock drivers... how are they ever
> > > supposed to work ? i2c bus controllers are allowed to sleep and the i2c
> > > core takes
On Thu 14 Dec 09:33 PST 2017, srinivas.kandaga...@linaro.org wrote:
> From: Srinivas Kandagatla
>
> This patch adds support to memory map and unmap regions commands in
> q6asm module.
>
> Signed-off-by: Srinivas Kandagatla
> ---
On Fri, 2017-12-22 at 13:15 +1030, Joel Stanley wrote:
> This adds the stub of a driver for the ASPEED SoCs. The clocks are
> defined and the static registration is set up.
>
> Reviewed-by: Andrew Jeffery
> Signed-off-by: Joel Stanley
Reviewed-by: Benjamin
On Fri, 2017-12-22 at 13:15 +1030, Joel Stanley wrote:
> This registers the core clocks; those which are required to calculate
> the rate of the timer peripheral so the system can load a clocksource
> driver.
>
> Reviewed-by: Andrew Jeffery
> Signed-off-by: Joel Stanley
On Fri, 2017-12-22 at 13:15 +1030, Joel Stanley wrote:
> There are some resets that are not associated with gates. These are
> represented by a reset controller.
>
> Reviewed-by: Andrew Jeffery
> Signed-off-by: Joel Stanley
Reviewed-by: Benjamin Herrenschmidt
On Fri, 2017-12-22 at 13:15 +1030, Joel Stanley wrote:
> The majority of the clocks in the system are gates paired with a reset
> controller that holds the IP in reset.
>
> This borrows from clk_hw_register_gate, but registers two 'gates', one
> to control the clock enable register and the other
On 12/28/2017 10:19 PM, Richard Cochran wrote:
On Tue, Dec 26, 2017 at 01:07:35PM +0530, Sagar Arun Kamble wrote:
Or can we provide simpler versions for covering some defaults? At
least reducing the number of arguments would make things easier.
Thought about specifying 1. cyclecounter read
On 12/28/2017 10:07 AM, Viresh Kumar wrote:
> On 27-12-17, 15:54, Rob Herring wrote:
>> On Wed, Dec 27, 2017 at 2:56 AM, Viresh Kumar
>> wrote:
>>> On 26-12-17, 14:29, Rob Herring wrote:
On Mon, Dec 18, 2017 at 03:51:30PM +0530, Viresh Kumar wrote:
>>>
> +On
Fixes the following sparse warning:
drivers/md/dm-raid.c:33:1: warning:
symbol 'raid_sets' was not declared. Should it be static?
Signed-off-by: Wei Yongjun
---
drivers/md/dm-raid.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On 2018/1/1 9:29, Jaegeuk Kim wrote:
> This patch allows root to reserve some blocks via mount option.
>
> "-o reserve_root=N" means N x 4KB-sized blocks for root only.
>
> Signed-off-by: Jaegeuk Kim
> ---
>
> Change log from v2:
> - wrong submission. :P
>
>
NVME_CTRL_RESETTING used to indicate the range of nvme initializing
strictly in fd634f41(nvme: merge probe_work and reset_work), but it
is not now. The NVME_CTRL_RESETTING is set before queue the
reset_work, there could be a big gap before the reset work handles
the outstanding requests. So when
On 2018/1/1 9:31, Jaegeuk Kim wrote:
> We can give another chance to write user data, which can resolve
> generic/441.
>
> Signed-off-by: Jaegeuk Kim
Reviewed-by: Chao Yu
Thanks,
On 02-01-18, 11:35, Rajendra Nayak wrote:
> I would want to reiterate what I have been saying for a while, that for these
> patches
> to be usable on any qualcomm platform completely we need support to associate
> multiple power-domains to a single device which is missing today.
Sure, but I had
The FAT filesystem partition volume label can be read with
FAT_IOCTL_GET_VOLUME_LABEL and written with FAT_IOCTL_SET_VOLUME_LABEL.
FAT volume label (volume name) is exactly same stored in boot sector and root
directory. Thus, the boot sector just needs to be upgrade when the label
writing.
v6:
Signed-off-by: ChenGuanqiao
---
fs/fat/fat.h | 6 ++
fs/fat/inode.c| 15 ---
include/uapi/linux/msdos_fs.h | 2 ++
3 files changed, 20 insertions(+), 3 deletions(-)
diff --git a/fs/fat/fat.h b/fs/fat/fat.h
index
On Sun, Dec 17, 2017 at 09:18:42PM -0800, Deepa Dinamani wrote:
> struct timeval which is part of struct input_event to
> maintain the event times is not y2038 safe.
>
> Real time timestamps are also not ideal for input_event
> as this time can go backwards as noted in the patch
> a80b83b7b8 by
Hi Wysocki and Brown,
May I know wether you have checked this? Thanks!
On Fri, Dec 22, 2017 at 11:11:10PM +0800, changbin...@intel.com wrote:
> From: Changbin Du
>
> The ACPI_MASKABLE_GPE_MAX is larger than the number of bits that u64 can
> represent. This result in
Hi Andrew,
Today's linux-next merge of the akpm tree got a conflict in:
ipc/mqueue.c
between commits:
3ec41d6c2257 ("tidy do_mq_open() up a bit")
946086abeddf ("mqueue: switch to on-demand creation of internal mount")
from the vfs tree and patch:
"ipc, mqueue: lazy call
Hi Deepa,
On Sun, Dec 17, 2017 at 09:18:43PM -0800, Deepa Dinamani wrote:
> struct timeval is not y2038 safe.
>
> All references to timeval in the kernel will be replaced
> by y2038 safe structures.
> Replace all references to timeval with y2038 safe
> struct timespec64 here.
>
> struct
On 2017/12/30 15:42, Yunlong Song wrote:
> In some case, the node blocks has wrong blkaddr whose segment type is
You mean *data block* has wrong blkaddr whose segment type is NODE?
> NODE, e.g., recover inode has missing xattr flag and the blkaddr is in
> the xattr range. Since fsck.f2fs does
Signed-off-by: ChenGuanqiao
---
fs/fat/file.c | 150 ++
1 file changed, 150 insertions(+)
diff --git a/fs/fat/file.c b/fs/fat/file.c
index 4724cc9ad650..829c91ef1ea0 100644
--- a/fs/fat/file.c
+++
Signed-off-by: ChenGuanqiao
---
fs/fat/dir.c | 62
1 file changed, 62 insertions(+)
diff --git a/fs/fat/dir.c b/fs/fat/dir.c
index 81cecbe6d7cf..63aab656c08e 100644
--- a/fs/fat/dir.c
+++ b/fs/fat/dir.c
@@
On Thu, Dec 28, 2017 at 04:30:50PM +0800, Zhuohua Li wrote:
> fixed a spelling mistake: buttong -> button
>
> Signed-off-by: Zhuohua Li
Applied, thank you.
> ---
> drivers/input/misc/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git
Modify mark_ntfs_record_dirty to support circular buffer list.
alloc_page_buffers created circular buffer list. So the circular list
linking in ntfs_sync_mft_mirror is unnecessary.
Signed-off-by: Sean Fu
---
fs/ntfs/aops.c | 6 ++
fs/ntfs/mft.c | 4
2 files
1.Create circular buffer list in alloc_page_buffers.
Remove unnecessary traversal in link_dev_buffers to create circular buffer list.
Make nobh_write_begin and nobh_write_end to support circular buffer list.
2.fs/ntfs: Make ntfs to support circular buffer list.
3.md: bitmap: Support circular
Make alloc_page_buffers to create circular buffer list instead linear
list.
Remove unnecessary traversal in link_dev_buffers to create circular
buffer list.
Make nobh_write_begin and nobh_write_end to support circular buffer list
traversal.
Signed-off-by: Sean Fu
---
Modify write_page free_buffers and read_page to support circular buffer
list.
Signed-off-by: Sean Fu
---
drivers/md/md-bitmap.c | 36 +++-
1 file changed, 19 insertions(+), 17 deletions(-)
diff --git a/drivers/md/md-bitmap.c
Hi Andrew,
After merging the akpm-current tree, today's linux-next build (arm
multi_v7_defconfig) produced this warning:
WARNING: vmlinux: 'abort' exported twice. Previous export was in vmlinux
WARNING: vmlinux: 'abort' exported twice. Previous export was in vmlinux
Introduced by commit
On Fri, 2017-12-22 at 13:15 +1030, Joel Stanley wrote:
> This registers a platform driver to set up all of the non-core clocks.
>
> The clocks that have configurable rates are now registered.
>
> Reviewed-by: Andrew Jeffery
> Signed-off-by: Joel Stanley
On Thu, Dec 21, 2017 at 8:46 PM, Arnd Bergmann wrote:
> On Wed, Dec 6, 2017 at 9:57 AM, Amit Kucheria
> wrote:
>> (Adding Arnd)
>>
>> Now that the merge window rush has abated, can you please apply this
>> trivial series?
>>
>> On Mon, Nov 6, 2017 at
Hi all,
Changes since 20171222:
New tree: iversion
The clk tree gained a build failure so I used the version from
next-20171222.
The vfs tree gained a conflict against Linus' tree
The v4l-dvb tree gained conflicts against the vfs tree.
The drm tree gained a build failure due to a bad
Changes in v2:
* Changed usage of clk_hw_is_prepared() to __clk_is_enabled()
in clk_rcg2_shared_ops to fix build test error.
Changes in v1:
This patch series does the miscellaneous changes for RCGs
used in SDM845.
1. Clear hardware clock control bit of RCGs where HW clock
control bit is set
For some root clock generators, there could be child branches which are
controlled by an entity other than application processor subsystem. For
such RCGs, as per application processor subsystem clock driver, all of its
downstream clocks are disabled and RCG is in disabled state but in actual
For upcoming targets like sdm845, POR value of the hardware clock control
bit is set for most of root clocks which needs to be cleared for software
to be able to control. For older targets like MSM8996, this bit is reserved
bit and having POR value as 0 so this patch will work for the older
Hello,
On Thu, Dec 21, 2017 at 10:08:46AM -0800, kan.li...@intel.com wrote:
> From: Kan Liang
>
> The direction of overwrite mode is backward. The last mmap__read_event
> will set tail to map->prev. Need to correct the map->prev to head which
> is the end of next read.
Why
On Tue, Jan 02, 2018 at 02:54:49PM +0800, Sean Fu wrote:
> Modify write_page free_buffers and read_page to support circular buffer
> list.
>
> Signed-off-by: Sean Fu
> ---
> drivers/md/md-bitmap.c | 36 +++-
> 1 file changed, 19 insertions(+),
Hi Eduardo,
On Mon, Jan 1, 2018 at 7:21 PM, Eduardo Valentin wrote:
> On Sun, Nov 19, 2017 at 12:04:27PM +0100, Geert Uytterhoeven wrote:
>> With gcc-4.1.2:
>>
>> drivers/thermal/hisi_thermal.c: In function ‘hisi_thermal_probe’:
>> drivers/thermal/hisi_thermal.c:530:
On Tue, Jan 2, 2018 at 5:09 AM, Wei Yongjun wrote:
> Fixes the following sparse warnings:
>
> drivers/tee/tee_shm.c:115:16: warning:
> symbol '__tee_shm_alloc' was not declared. Should it be static?
>
> Signed-off-by: Wei Yongjun
> ---
>
Hi Baolin,
Could you have a look at
https://git.kernel.org/pub/scm/linux/kernel/git/abelloni/linux.git/commit/?h=rtc-ranges
My approach has multiple advantages as it works for 64-bit counters and
the range can be updated at runtime.
On 02/01/2018 at 13:10:05 +0800, Baolin Wang wrote:
> In order
The user space interface allows specifying the type and mask field used
to allocate the cipher. Only a subset of the possible flags are intended
for user space. Therefore, white-list the allowed flags.
In case the user space caller uses at least one non-allowed flag, EINVAL
is returned.
Hi,
sorry, I forgot the right tags.
---8<---
The user space interface allows specifying the type and mask field used
to allocate the cipher. Only a subset of the possible flags are intended
for user space. Therefore, white-list the allowed flags.
In case the user space caller uses at least one
On 24/12/17 03:50, Nick Desaulniers wrote:
> The header declares this function as __init but is defined in __ref
> section.
>
> Signed-off-by: Nick Desaulniers
Reviewed-by: Juergen Gross
Juergen
No fucntional change. Add nvme_pci_pre_init to package the nvme
specified initialization work before configuring admin queue.
Then nvme_pci_enable and nvme_pci_configure_admin_queue could be
clearer.
Signed-off-by: Jianchao Wang
---
drivers/nvme/host/pci.c | 145
No functional change. Just change name of functions corresponding
to setup adminq to make it more readable.
nvme_pci_configure_admin_queue -> nvme_pci_setup_adminq
nvme_alloc_admin_tags -> nvme_pci_start_adminq
Signed-off-by: Jianchao Wang
---
On 12/30/2017 3:16 PM, Matthew Wilcox wrote:
On Fri, Dec 29, 2017 at 04:28:51PM +0900, Byungchul Park wrote:
On Thu, Dec 28, 2017 at 10:51:46PM -0500, Theodore Ts'o wrote:
On Fri, Dec 29, 2017 at 10:47:36AM +0900, Byungchul Park wrote:
(1) The best way: To classify all waiters correctly.
Dear Alan,
First, please note, that your mailer (MUA) doesn’t set the references
header, which breaks threading for people not having their own answers
in the inbox.
Am 31.12.2017 um 22:16 schrieb Alan Stern:
On Sun, 31 Dec 2017, Paul Menzel wrote:
Am 29.12.2017 um 17:14 schrieb Alan
The problem: the scheduler wanting to stack tasks way too deeply has
become far too common a behavior, and IMHO a very very bad one.
While booting...
systemd-udevd-529 [001] d...17.425644: select_task_rq_fair: NAK
systemd-udevd:818 rejects cpu:7:w3072:r:3 -> cpu:1:w4096:r:4
> -Original Message-
> From: Marcin Wojtas [mailto:m...@semihalf.com]
> Sent: Monday, January 01, 2018 12:18 PM
> To: Russell King - ARM Linux
> Cc: Stefan Chulski ; Thomas Petazzoni
> ; Andrew Lunn
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Tobias Jordan
[ Upstream commit 589bf32f09852041fbd3b7ce1a9e703f95c230ba ]
add appropriate calls to clk_disable_unprepare() by jumping to out_mdio
in case
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Kevin Cernekee
[ Upstream commit a46182b00290839fa3fa159d54fd3237bd8669f0 ]
Closing a multicast socket after the final IPv4 address is deleted
from an interface can
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Fugang Duan
[ Upstream commit 178e5f57a8d8f8fc5799a624b96fc31ef9a29ffa ]
The enet IP only support 32 bit, it will use swiotlb buffer to do dma
mapping when xmit buffer
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Nikolay Aleksandrov
[ Upstream commit 84aeb437ab98a2bce3d4b2111c79723aedfceb33 ]
The early call to br_stp_change_bridge_id in bridge's newlink can cause
a memory
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Ido Schimmel
[ Upstream commit b4681c2829e24943aadd1a7bb3a30d41d0a20050 ]
Since commit 0ddcf43d5d4a ("ipv4: FIB Local/MAIN table collapse") the
local table uses the same
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Gal Pressman
[ Upstream commit 6323514116404cc651df1b7fffa1311ddf8ce647 ]
mlx5e_vxlan_lookup_port is called both from mlx5e_add_vxlan_port (user
context) and
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Gal Pressman
[ Upstream commit 2989ad1ec03021ee6d2193c35414f1d970a243de ]
The assumption that the next header field contains the transport
protocol is wrong for IPv6
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Eran Ben Elisha
[ Upstream commit 37e92a9d4fe38dc3e7308913575983a6a088c8d4 ]
In mlx5_ifc, struct size was not complete, and thus driver was sending
garbage after the last
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Andy Lutomirski
commit ca6c99c0794875c6d1db6e22f246699691ab7e6b upstream.
flush_tlb_page() was very similar to flush_tlb_mm_range() except that
it had a couple of issues:
-
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Andy Lutomirski
commit ce4a4e565f5264909a18c733b864c3f74467f69e upstream.
The UP asm/tlbflush.h generates somewhat nicer code than the SMP version.
Aside from that, it's
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Maciej S. Szmigiero
commit 695b78b548d8a26288f041e907ff17758df9e1d5 upstream.
AC'97 ops (register read / write) need SSI regmap and clock, so they have
to be set
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Johan Hovold
commit bc6476d6c1edcb9b97621b5131bd169aa81f27db upstream.
Fix child-node lookup during probe, which ended up searching the whole
device tree depth-first starting
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Tonghao Zhang
[ Upstream commit 8cb38a602478e9f806571f6920b0a3298aabf042 ]
The patch(180d8cd942ce) replaces all uses of struct sock fields'
memory_pressure,
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Ben Hutchings
commit 50dd2ea8ef67a1617e0c0658bcbec4b9fb03b936 upstream.
The checks for whether another region/block header could be present
are subtracting the
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: "Michael S. Tsirkin"
[ Upstream commit a8ceb5dbfde1092b466936bca0ff3be127ecf38e ]
Users of ptr_ring expect that it's safe to give the
data structure a pointer and have it be
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Yuval Mintz
[ Upstream commit fccff0862838908d21eaf956d57e09c6c189f7c5 ]
Learning is currently enabled for ports which are OVS slaves -
even though OVS doesn't need this
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Ido Schimmel
[ Upstream commit 58acfd714e6b02e8617448b431c2b64a2f1f0792 ]
Currently, parameters such as oif and source address are not taken into
account during fibmatch
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Kamal Heib
[ Upstream commit bae115a2bb479142605726e6aa130f43f50e801a ]
Currently, if a size of zero is passed to
mlx5_fpga_mem_{read|write}_i2c()
the "err" return value
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Julian Wiedmann
[ Upstream commit 7fbd9493f0eeae8cef58300505a9ef5c8fce6313 ]
Just as for an explicit enable/disable, toggling the takeover mode also
requires that
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Andy Lutomirski
commit 03f4424f348e8be95eb1bbeba09461cd7b867828 upstream.
Provide infrastructure to:
- find a kernel PMD for a mapping which must be visible to user space
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Steven Rostedt (VMware)
commit 4397f04575c44e1440ec2e49b6302785c95fd2f8 upstream.
Jing Xia and Chunyan Zhang reported that on failing to allocate part of the
tracing
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Andy Lutomirski
commit 85900ea51577e31b186e523c8f4e068c79ecc7d3 upstream.
Make VSYSCALLs work fully in PTI mode by mapping them properly to the user
space visible page
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Steven Rostedt (VMware)
commit 6b7e633fe9c24682df550e5311f47fb524701586 upstream.
The ring_buffer_read_page() takes care of zeroing out any extra data in the
page that it
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Yelena Krivosheev
commit 4423c18e466afdfb02a36ee8b9f901d144b3c607 upstream.
When port connect to PHY in polling mode (with poll interval 1 sec),
port and phy link status
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Tobias Jordan
[ Upstream commit 589bf32f09852041fbd3b7ce1a9e703f95c230ba ]
add appropriate calls to clk_disable_unprepare() by jumping to out_mdio
in case
Hello,
Kindly respond back to me on the crude oil email i sent to you. Please let
know if you did not get it to have it resent.
Regards,
L
Engr. E. C
Sent from my iphone
On Mon, Jan 01, 2018 at 10:53:07AM -0500, Alan Stern wrote:
> On Mon, 1 Jan 2018, Himanshu Jha wrote:
>
> > On Sun, Dec 31, 2017 at 04:20:45PM -0500, Alan Stern wrote:
> > > On Sun, 31 Dec 2017, Himanshu Jha wrote:
> > >
> > > > Use dma_zalloc_coherent for allocating zeroed
> > > > memory and
From: Markus Elfring
Date: Mon, 1 Jan 2018 18:45:17 +0100
The script "checkpatch.pl" pointed information out like the following.
WARNING: void function return statements are not generally useful
Thus remove such a statement in the affected function.
Hi all,
After merging the netfilter-next tree, today's linux-next build (arm
multi_v7_defconfig) produced this warning:
In file included from net/ipv6/af_inet6.c:45:0:
include/linux/netfilter_ipv6.h:38:51: warning: 'struct nf_queue_entry' declared
inside parameter list
int (*reroute)(struct
The POSTED_INTR_NV field is constant (though it differs between the vmcs01 and
vmcs02), there is no need to reload it on vmexit to L1.
Signed-off-by: Paolo Bonzini
---
arch/x86/kvm/vmx.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/arch/x86/kvm/vmx.c
Drop all of the code related to .remove hook and make use of
devm_nvmem_register() instead.
Cc: Srinivas Kandagatla
Cc: Heiko Stuebner
Cc: Masahiro Yamada
Cc: Carlo Caione
Cc: Kevin Hilman
1 - 100 of 1286 matches
Mail list logo