On Thu, May 16, 2019 at 06:48:40AM +1000, Tobin C. Harding wrote:
> On Wed, May 15, 2019 at 12:55:55PM +0200, Greg Kroah-Hartman wrote:
> > From: "Tobin C. Harding"
> >
> > [ Upstream commit bdfad5aec1392b93495b77b864d58d7f101dc1c1 ]
>
> Greg you are not going to back port all of these kobject
Presently __bdev_dax_supported() checks if first sector of last
page ( last_page ) on the block device is aligned to page
boundary. However the code to compute 'last_page' assumes that there
are 8 sectors/page assuming a 4K page-size.
This assumption breaks on architectures which use a different
Hi Mark
>
> On Mon, Apr 29, 2019 at 10:46:03AM +, S.j. Wang wrote:
>
> > + cs42xx8->gpio_reset = of_get_named_gpio(dev->of_node, "gpio-
> reset", 0);
> > + if (gpio_is_valid(cs42xx8->gpio_reset)) {
> > + ret = devm_gpio_request_one(dev, cs42xx8->gpio_reset,
> > +
Hello Nicholas,
On Thu, May 16, 2019 at 02:55:42PM +1000, Nicholas Piggin wrote:
> Abhishek's on May 13, 2019 7:49 pm:
> > On 05/08/2019 10:29 AM, Nicholas Piggin wrote:
> >> Abhishek Goel's on April 22, 2019 4:32 pm:
> >>> Currently, the cpuidle governors determine what idle state a idling CPU
On 05/15/2019 05:19 PM, Mark Rutland wrote:
> Hi Anshuman,
>
> On Tue, May 14, 2019 at 02:30:07PM +0530, Anshuman Khandual wrote:
>> Memory removal from an arch perspective involves tearing down two different
>> kernel based mappings i.e vmemmap and linear while releasing related page
>> table
On Wed, May 15, 2019 at 07:06:52PM +0200, Roberto Sassu wrote:
> On 5/15/2019 6:08 PM, Arvind Sankar wrote:
> > On Wed, May 15, 2019 at 01:19:04PM +0200, Roberto Sassu wrote:
> >> On 5/15/2019 2:52 AM, Arvind Sankar wrote:
> > I don't understand what you mean? The IMA hashes are signed by some
Andrew,
Can this go via the -mm tree?
On Wed, May 01, 2019 at 10:56:14PM +0300, Mike Rapoport wrote:
> Hi,
>
> For several architectures the ARCH_SELECT_MEMORY_MODEL has no real effect
> because the dependencies for the memory model are always evaluated to a
> single value.
>
> Remove the
On Wed, May 15, 2019 at 11:27:04AM -0700, Andy Lutomirski wrote:
> Hi, LSM and SELinux people-
>
> We're trying to figure out how SGX fits in with LSMs. For background,
> an SGX library is functionally a bit like a DSO, except that it's
> nominally resistant to attack from outside and the
The i2c-ocore driver already has a polling mode interface.But it needs
a workaround for FU540 Chipset on HiFive unleashed board (RevA00).
There is an erratum in FU540 chip that prevents interrupt driven i2c
transfers from working, and also the I2C controller's interrupt bit
cannot be cleared if
Update device id table for Opencore's I2C master based re-implementation
used in FU540-c000 chipset on HiFive Unleashed platform.
Device ID's include Sifive, soc-specific device for chip specific tweaks
and sifive IP block specific device for generic programming model.
Signed-off-by: Sagar
Add FU540-C000 specific device tree bindings to already
available i2-ocores file. This device is available on
HiFive Unleashed Rev A00 board. Move interrupt and interrupt
parents under optional property list as these can be optional.
The FU540-C000 SoC from sifive, has an Opencore's I2C block
The patch is based on mainline v5.1 and extends DT-bindings for Opencore based
I2C IP block reimplemented
in FU540 SoC, available on HiFive unleashed board (Rev A00), and also provides
a workaround for broken IRQ
which affects the already available I2C polling mode interface in mainline, for
On Wed, May 15, 2019 at 07:27:02AM -0700, Andy Lutomirski wrote:
>
> > On May 15, 2019, at 4:00 AM, Jarkko Sakkinen
> > wrote:
> >
> >> On Wed, May 15, 2019 at 01:35:31PM +0300, Jarkko Sakkinen wrote:
> >> This brings me to an open question in Andy's model: lets say that we
> >> change the
On Wed, May 15, 2019 at 06:21:47AM -0700, Sean Christopherson wrote:
> On Wed, May 15, 2019 at 01:35:31PM +0300, Jarkko Sakkinen wrote:
> > On Tue, May 14, 2019 at 01:45:27PM -0700, Sean Christopherson wrote:
> > > On Tue, May 14, 2019 at 08:13:36AM -0700, Andy Lutomirski wrote:
> > > > I think
On Thu, May 16, 2019 at 4:51 AM Laura Abbott wrote:
>
> Commit 691efbedc60d ("arm64: vdso: use $(LD) instead of $(CC) to
> link VDSO") switched to using LD explicitly. The --build-id option
> needs to be passed explicitly, similar to x86. Add this option.
>
> Fixes: 691efbedc60d ("arm64: vdso:
Abhishek's on May 13, 2019 7:49 pm:
> On 05/08/2019 10:29 AM, Nicholas Piggin wrote:
>> Abhishek Goel's on April 22, 2019 4:32 pm:
>>> Currently, the cpuidle governors determine what idle state a idling CPU
>>> should enter into based on heuristics that depend on the idle history on
>>> that CPU.
Hello Linus,
Please consider the following thermal soc changes for v5.2-rc1.
The following changes since commit 37624b58542fb9f2d9a70e6ea006ef8a5f66c30b:
Linux 5.1-rc7 (2019-04-28 17:04:13 -0700)
are available in the git repository at:
> On May 15, 2019, at 8:03 PM, Xing, Cedric wrote:
>
> Hi Andy,
>
>> From: Andy Lutomirski [mailto:l...@kernel.org]
>>
>>> On Wed, May 15, 2019 at 3:46 PM James Morris wrote:
>>>
>>> On Wed, 15 May 2019, Andy Lutomirski wrote:
>>>
> Why not just use an xattr, like security.sgx ?
kernel: 4.4.180-rc1
git repo: https://git.linaro.org/lkft/arm64-stable-rc.git
git branch: 4.4.180-rc1-hikey-20190515-440
git commit: 4acf8bfa73bb083efe32d6b2623a48f49e662657
git describe: 4.4.180-rc1-hikey-20190515-440
Test details:
https://qa-reports.linaro.org/lkft/linaro-hikey-stab
On Wed, 15 May 2019 at 16:53, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.19.44 release.
> There are 113 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.
>
>
lp87561 is a single output 4-phase regulator configuration.
Add support for the same.
Signed-off-by: Keerthy
---
.../devicetree/bindings/mfd/lp87565.txt | 36 +++
1 file changed, 36 insertions(+)
diff --git a/Documentation/devicetree/bindings/mfd/lp87565.txt
Add support for 4-phase lp87561 combination.
Signed-off-by: Keerthy
---
drivers/mfd/lp87565.c | 4
include/linux/mfd/lp87565.h | 2 ++
2 files changed, 6 insertions(+)
diff --git a/drivers/mfd/lp87565.c b/drivers/mfd/lp87565.c
index 32d2a07d4354..8ad688fe75f9 100644
---
The LP8756x family has a single output 4-phase regulator
configuration. Add support for the same. The control
lies in the master buck which is buck0 for 4-phase
configuration. Enable/disable/voltage set happen via
buck0 registers.
Data Sheet: https://www.ti.com/lit/ds/symlink/lp87561-q1.pdf
Add support for 4-phase lp87561 combination.
Data Sheet: https://www.ti.com/lit/ds/symlink/lp87561-q1.pdf
Keerthy (3):
dt-bindings: mfd: lp87565: Add lp87561 configuration
mfd: lp87565: Add support for 4-phase lp87561 combination
regulator: lp87565: Add 4-phase lp87561 regulator support
On Sat, Apr 20, 2019 at 10:00:35PM +0800, Wanglai Shi wrote:
> This patch adds DT bindings for the CoreSight trace components
> on hi3660, which is used by 96boards Hikey960.
>
> Signed-off-by: Wanglai Shi
Hi Wei,
Mathieu and me both have reviewed this patch, could you pick up this
patch?
If ulite_probe is not called or failed to registed
uart_register_driver, unload the module will call
uart_unregister_driver, which will tigger NULL
pointer dereference like this:
BUG: KASAN: null-ptr-deref in tty_unregister_driver+0x19/0x100
Read of size 4 at addr 0034 by task
Hi all,
Please do not add any v5.3 material to your linux-next included
trees/branches until after v5.2-rc1 has been released.
Changes since 20190515:
The ftrace tree gained conflicts against Linus' tree.
Non-merge commits (relative to Linus' tree): 1940
2029 files changed, 60303 insertions
On 5/15/19 3:56 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 5.1.3 release.
There are 46 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
On 5/15/19 3:54 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 5.0.17 release.
There are 137 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
On 5/15/19 3:54 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.19.44 release.
There are 113 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
On 5/15/19 3:54 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.14.120 release.
There are 115 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
On 5/15/19 3:55 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.9.177 release.
There are 51 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
On 5/15/19 3:51 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.4.180 release.
There are 266 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
On 5/15/19 3:54 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.18.140 release.
There are 86 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
Hi Steve,
On Wed, 15 May 2019 21:53:05 -0400 Steven Rostedt wrote:
>
> I mentioned this conflict and the entry_64.S one to Linus when
> submitting my pull request. I fixed it up too in my ftrace/conflicts
> branch.
And he has merged your branch now, so all good.
--
Cheers,
Stephen Rothwell
On May 15, 2019 8:05:29 PM PDT, Masami Hiramatsu wrote:
>
>> >> diff --git a/kernel/trace/trace_events.c
>b/kernel/trace/trace_events.c
>> >> index 5b3b0c3..81c038e 100644
>> >> --- a/kernel/trace/trace_events.c
>> >> +++ b/kernel/trace/trace_events.c
>> >> @@ -832,6 +832,7 @@ static int
On Wed, May 15, 2019 at 7:20 PM Will Deacon wrote:
>
> On Wed, May 15, 2019 at 07:13:19PM +0530, Arun KS wrote:
> > __early_cpu_boot_status is of type int. Fix up the calls to
> > update_early_cpu_boot_status, to use a w register.
> >
> > Signed-off-by: Arun KS
> > Acked-by: Mark Rutland
> >
This patch selects CONFIG_IMX_SCU_SOC by default to support
i.MX system controller unit SoC info driver.
Signed-off-by: Anson Huang
---
No changes.
---
arch/arm64/configs/defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
Add i.MX SCU SoC info driver to support i.MX8QXP SoC, introduce
driver dependency into Kconfig as CONFIG_IMX_SCU must be
selected to support i.MX SCU SoC driver, also need to use
platform driver model to make sure IMX_SCU driver is probed
before i.MX SCU SoC driver.
With this patch, SoC info can
On Wed, May 15, 2019 at 10:00:00PM +0800, Liu Song wrote:
> Although the deleted entry can not be seen by changing
> the rec_len of the parent directory entry. However we
> can piggyback set the entry's inode to 0. There is no
> harm and an entry with an inode of 0 means that the
> entry has been
On Thu, 16 May 2019 at 01:21, Sean Christopherson
wrote:
>
> On Wed, May 15, 2019 at 12:11:53PM +0800, Wanpeng Li wrote:
> > From: Wanpeng Li
> >
> > Expose the per-vCPU advancement information to the user via per-vCPU debugfs
> > entry. wait_lapic_expire() call was moved above
On Thu, 16 May 2019 at 01:42, Sean Christopherson
wrote:
>
> On Wed, May 15, 2019 at 12:11:54PM +0800, Wanpeng Li wrote:
> > From: Wanpeng Li
> >
> > Advance lapic timer tries to hidden the hypervisor overhead between the
> > host emulated timer fires and the guest awares the timer is fired.
From: Wanpeng Li
Extract adaptive tune timer advancement logic to a single function.
Cc: Paolo Bonzini
Cc: Radim Krčmář
Cc: Sean Christopherson
Cc: Liran Alon
Signed-off-by: Wanpeng Li
---
arch/x86/kvm/lapic.c | 57 ++--
1 file changed, 33
From: Wanpeng Li
Advance lapic timer tries to hidden the hypervisor overhead between the
host emulated timer fires and the guest awares the timer is fired. However,
it just hidden the time between apic_timer_fn/handle_preemption_timer ->
wait_lapic_expire, instead of the real position of
From: Wanpeng Li
wait_lapic_expire() call was moved above guest_enter_irqoff() because of
its tracepoint, which violated the RCU extended quiescent state invoked
by guest_enter_irqoff()[1][2]. This patch simply moves the tracepoint
below guest_exit_irqoff() in vcpu_enter_guest(). Snapshot the
From: Wanpeng Li
After commit c3941d9e0 (KVM: lapic: Allow user to disable adaptive tuning of
timer advancement), '-1' enables adaptive tuning starting from default
advancment of 1000ns. However, we should expose an int instead of an overflow
uint module parameter.
Before patch:
From: Wanpeng Li
Expose per-vCPU timer_advance_ns to userspace, so it is able to
query the auto-adjusted value.
Cc: Paolo Bonzini
Cc: Radim Krčmář
Cc: Sean Christopherson
Cc: Liran Alon
Signed-off-by: Wanpeng Li
---
arch/x86/kvm/debugfs.c | 16
1 file changed, 16
Advance lapic timer tries to hidden the hypervisor overhead between the
host emulated timer fires and the guest awares the timer is fired. However,
it just hidden the time between apic_timer_fn/handle_preemption_timer ->
wait_lapic_expire, instead of the real position of vmentry which is
Hi,
On Wed, 15 May 2019 18:51:23 -0700
Divya Indi wrote:
> Hi Masami,
>
> Thanks for pointing it out.
>
> Yes, it should not be static.
>
> On 5/15/19 5:09 PM, Masami Hiramatsu wrote:
> > HI Divya,
> >
> > On Wed, 20 Mar 2019 11:28:51 -0700
> > Divya Indi wrote:
> >
> >> Ftrace provides the
Hi Andy,
> From: Andy Lutomirski [mailto:l...@kernel.org]
>
> On Wed, May 15, 2019 at 3:46 PM James Morris wrote:
> >
> > On Wed, 15 May 2019, Andy Lutomirski wrote:
> >
> > > > Why not just use an xattr, like security.sgx ?
> > >
> > > Wouldn't this make it so that only someone with
merged into cifs-2.6.git for-next
On Wed, May 15, 2019 at 4:09 PM wrote:
>
> From: Long Li
>
> SMBDirect manages its own ports in the transport layer, there is no need to
> check the port to find a connection.
>
> Signed-off-by: Long Li
> ---
> fs/cifs/connect.c | 4
> 1 file changed, 4
merged into cifs-2.6.git for-next
On Wed, May 15, 2019 at 4:10 PM wrote:
>
> From: Long Li
>
> An IOCTL uses up to 2 iovs. The 1st iov is the command itself, the 2nd iov is
> optional data for that command. The 1st iov is always allocated on the heap
> but the 2nd iov may point to a variable on
On Wed, May 15, 2019 at 09:42:11PM +0930, Arthur Marsh wrote:
> I have built kernels with the attached patch applied and run git gc
> on the patched kernels (both the 32 bit kernel on the Pentium-D and
> the 64 bit kernel on the Athlon II X4 640).
>
> There were a couple of warnings from other
Ping...
> -Original Message-
> From: Anson Huang
> Sent: Thursday, May 9, 2019 9:44 AM
> To: 'Anson Huang' ; robh...@kernel.org;
> mark.rutl...@arm.com; shawn...@kernel.org; s.ha...@pengutronix.de;
> ker...@pengutronix.de; feste...@gmail.com; catalin.mari...@arm.com;
>
Hi Enric
On Wed, May 15, 2019 at 11:23:13PM +0200, Enric Balletbo Serra wrote:
> Missatge de Enric Balletbo i Serra del
> dia dc., 15 de maig 2019 a les 15:00:
> >
> > Hi,
> >
> > On 4/5/19 15:34, Rushikesh S Kadam wrote:
> > > This driver implements a slim layer to enable the ChromeOS
> > > EC
Hi all
Fill buffers, load ports are shared between threads on the same physical core.
We need to run more than one vm on the same physical core.
Is there any complete mitigation for environments utilizing SMT?
It seems you just sent the same email twice, please check my previous reply.
Thanks,
Gao Xiang
On 2019/5/16 10:11, Mao, Chenxi wrote:
> Hi Xiang:
>
> I checked the deliver history.
> There is only below delivery related with lz4.c
> Pull request:616
> 4e3accc Fix Dict Size Test in
On Wed, May 15, 2019 at 9:59 PM Lorenzo Pieralisi
wrote:
>
> On Tue, May 14, 2019 at 01:35:20PM +0800, Ley Foon Tan wrote:
> > On Wed, Apr 24, 2019 at 12:57 PM Ley Foon Tan
> > wrote:
> > >
> > > Altera MSI IP is a soft IP and is only available after
> > > FPGA image is programmed.
> > >
> > >
On 2019/5/16 10:07, Mao, Chenxi wrote:
> Hi Xiang:
>
> I checked the deliver history.
> There is only below delivery related with lz4.c
> Pull request:616
> 4e3accc Fix Dict Size Test in `LZ4_compress_fast_continue()`
> 535636f Don't Attach Very Small Dictionaries
> This 2 changes seems like
Hi Xiang:
I checked the deliver history.
There is only below delivery related with lz4.c
Pull request:616
4e3accc Fix Dict Size Test in `LZ4_compress_fast_continue()`
535636f Don't Attach Very Small Dictionaries
This 2 changes seems like ONLY bug fixes for dictionary fix baesd on 1.8.3
Based on
Hi Xiang:
I checked the deliver history.
There is only below delivery related with lz4.c
Pull request:616
4e3accc Fix Dict Size Test in `LZ4_compress_fast_continue()`
535636f Don't Attach Very Small Dictionaries
This 2 changes seems like ONLY bug fixes for dictionary fix baesd on 1.8.3
Based on
The pull request you sent on Wed, 15 May 2019 20:38:50 +0200:
> git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git
> for-linus-5.2b-rc1-tag
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/5fd09ba68297c967f5ba6bea9c3b444d34f80ee5
Thank you!
--
Deet-doot-dot,
The pull request you sent on Wed, 15 May 2019 21:35:00 +0200:
> ssh://g...@gitolite.kernel.org/pub/scm/linux/kernel/git/sre/linux-power-supply.git
> tags/for-v5.2
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/8649efb2f8750dcabff018a27784bab4ecb9f88f
Thank you!
--
The pull request you sent on Wed, 15 May 2019 17:05:58 -0700:
> git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm
> tags/libnvdimm-fixes-5.2-rc1
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/83f3ef3de625a5766de2382f9e077d4daafd5bac
Thank you!
--
The pull request you sent on Wed, 15 May 2019 14:26:58 -0400:
> git://linux-nfs.org/~bfields/linux.git tags/nfsd-5.2
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/700a800a949467cb86491763b983e1edcdee8642
Thank you!
--
Deet-doot-dot, I am a bot.
On Thu, 16 May 2019 at 00:07, Greg Kroah-Hartman
wrote:
>
> On Wed, May 15, 2019 at 08:24:27PM +0200, Greg Kroah-Hartman wrote:
> > On Wed, May 15, 2019 at 11:17:05AM -0700, Guenter Roeck wrote:
> > > On Wed, May 15, 2019 at 12:54:40PM +0200, Greg Kroah-Hartman wrote:
> > > > This is the start of
On Wed, 15 May 2019 18:49:57 PDT (-0700), Linus Torvalds wrote:
On Wed, May 15, 2019 at 6:43 PM Palmer Dabbelt wrote:
Linus: I'm not sure how to tag this PR as a mistake, so I'm going to just send
another one. If this gets merged then I'll handle the follow-on.
Just emailing in the same
On Thu, 16 May 2019 11:05:48 +1000
Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the ftrace tree got a conflict in:
>
> include/linux/compiler.h
>
> between commit:
>
> 37686b1353cf ("tracing: Improve "if" macro code generation")
>
> from Linus' tree and commit:
>
>
Hi Masami,
Thanks for pointing it out.
Yes, it should not be static.
On 5/15/19 5:09 PM, Masami Hiramatsu wrote:
HI Divya,
On Wed, 20 Mar 2019 11:28:51 -0700
Divya Indi wrote:
Ftrace provides the feature “instances” that provides the capability to
create multiple Ftrace ring buffers.
Describe the memory related to page table walks as non-cachable for iommu
instances that are not DMA coherent.
Signed-off-by: Bjorn Andersson
---
drivers/iommu/io-pgtable-arm.c | 12 +---
1 file changed, 9 insertions(+), 3 deletions(-)
diff --git a/drivers/iommu/io-pgtable-arm.c
On Wed, 15 May 2019 12:08:36 PDT (-0700), atish.pa...@wdc.com wrote:
On 5/15/19 10:40 AM, Palmer Dabbelt wrote:
The following changes since commit 085b7755808aa11f78ab9377257e1dad2e6fa4bb:
Linux 5.1-rc6 (2019-04-21 10:45:57 -0700)
are available in the Git repository at:
On Wed 15 May 14:50 PDT 2019, Doug Anderson wrote:
> Hi,
>
> On Tue, May 14, 2019 at 9:10 PM Rob Clark wrote:
>
> > On Mon, May 13, 2019 at 3:48 PM Doug Anderson wrote:
> > >
> > > Hi,
> > >
> > > On Thu, May 9, 2019 at 11:44 AM Rob Clark wrote:
> > >
> > > > From: Douglas Anderson
> > > >
On Wed, May 15, 2019 at 6:43 PM Palmer Dabbelt wrote:
>
> Linus: I'm not sure how to tag this PR as a mistake, so I'm going to just send
> another one. If this gets merged then I'll handle the follow-on.
Just emailing in the same thread ends up with me hopefully seeing the
"oops, cancel pull
Hi Yann and Xiang:
For this FAST_DEC_LOOP change, I only pick up decompress related patches to
current kernel LZ4 implementation(based on 1.8.3).
Here is my cherry-pick list:
2589c44 created LZ4_FAST_DEC_LOOP build macro
605d811 enable LZ4_FAST_DEC_LOOP build macro on aarch64/GCC by default
On Wed, May 15, 2019 at 10:56 AM Steven Rostedt wrote:
>
> Updates to ktest.pl
Your pull request is showing stale data.
> - Handle meta data in GRUB_MENU
>
> - Add variable to cusomize what return value the reboot code should return.
These were already long merged, from your first pull
The pull request you sent on Wed, 15 May 2019 13:36:14 -0400:
> git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
> trace-v5.2
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/d2d8b146043ae7e250aef1fb312971f6f479d487
Thank you!
--
Deet-doot-dot,
Currently kobject_add_varg() calls kobject_set_name_vargs() then returns
the return value of kobject_add_internal(). kobject_set_name_vargs()
allocates memory for the name string. When kobject_add_varg() returns
an error we do not know if memory was allocated or not. If we check the
return
The pull request you sent on Wed, 15 May 2019 13:56:02 -0400:
> git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-ktest.git
> ktest-v5.2
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/b06ed1e7a2fa9b636f368a9e97c3c8877623f8b2
Thank you!
--
Deet-doot-dot,
On Wed, 15 May 2019 16:45:31 -0700
Linus Torvalds wrote:
> On Wed, May 15, 2019 at 10:56 AM Steven Rostedt wrote:
> >
> > Updates to ktest.pl
>
> Your pull request is showing stale data.
>
> > - Handle meta data in GRUB_MENU
> >
> > - Add variable to cusomize what return value the reboot
HI Divya,
On Wed, 20 Mar 2019 11:28:51 -0700
Divya Indi wrote:
> Ftrace provides the feature “instances” that provides the capability to
> create multiple Ftrace ring buffers. However, currently these buffers
> are created/accessed via userspace only. The kernel APIs providing these
> features
Hi Linus, please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm
tags/libnvdimm-fixes-5.2-rc1
...to receive just a small collection of fixes this time around. The
new virtio-pmem driver is nearly ready, but some last minute
device-mapper acks and virtio questions made it
On Wed, 2019-05-15 at 16:25 -0700, Dan Williams wrote:
>
> > diff --git a/drivers/nvdimm/btt.c b/drivers/nvdimm/btt.c
> > index 4671776f5623..9f02a99cfac0 100644
> > --- a/drivers/nvdimm/btt.c
> > +++ b/drivers/nvdimm/btt.c
> > @@ -1269,11 +1269,9 @@ static int btt_read_pg(struct btt *btt, struct
Make some structs and functions static to fix build warning, parts of
warning shown below,
amples/vfio-mdev/mtty.c:730:5: warning: symbol 'mtty_create' was not declared.
Should it be static?
samples/vfio-mdev/mtty.c:780:5: warning: symbol 'mtty_remove' was not declared.
Should it be static?
Hi all,
Today's linux-next merge of the ftrace tree got a conflict in:
arch/x86/entry/entry_64.S
between commits:
8f34c5b5afce ("x86/exceptions: Make IST index zero based")
3207426925d2 ("x86/exceptions: Disconnect IST index and stack order")
2a594d4ccf3f ("x86/exceptions: Split debug
On Tue, May 14, 2019 at 11:01:42PM +0800, Alex Williamson wrote:
> On Tue, 14 May 2019 09:43:44 +0200
> Erik Skultety wrote:
>
> > On Tue, May 14, 2019 at 03:32:19AM -0400, Yan Zhao wrote:
> > > On Tue, May 14, 2019 at 03:20:40PM +0800, Erik Skultety wrote:
> > > > On Tue, May 14, 2019 at
On Wed, 15 May 2019 16:38:58 -0500, Sean Christopherson
wrote:
On Wed, May 15, 2019 at 11:27:04AM -0700, Andy Lutomirski wrote:
2) Just like any other DSO, there are potential issues with how
enclaves deal with writable vs executable memory. This takes two
forms. First, a task should
On Wed, May 15, 2019 at 5:25 PM Verma, Vishal L
wrote:
>
> On Wed, 2019-05-15 at 16:25 -0700, Dan Williams wrote:
> >
> > > diff --git a/drivers/nvdimm/btt.c b/drivers/nvdimm/btt.c
> > > index 4671776f5623..9f02a99cfac0 100644
> > > --- a/drivers/nvdimm/btt.c
> > > +++ b/drivers/nvdimm/btt.c
> >
On Wed, May 15, 2019 at 5:27 PM Steven Rostedt wrote:
>
> I can do this, but it needs testing and all that before sending to you,
> and may not make the merge window. Is that fine?
It's fine. The warning is annoying, but that's my own fault for
updating my system just before the merge window.
>>}
>>
>> diff --git a/drivers/nvdimm/bus.c b/drivers/nvdimm/bus.c
>> index 7ff684159f29..2eb6a6cfe9e4 100644
>> --- a/drivers/nvdimm/bus.c
>> +++ b/drivers/nvdimm/bus.c
>> @@ -642,7 +642,7 @@ static struct attribute *nd_device_attributes[] = {
>>NULL,
>> };
>>
>> -/**
> On May 15, 2019, at 7:25 PM, Dan Williams wrote:
>
> On Tue, May 14, 2019 at 8:08 AM Qian Cai wrote:
>>
>> Several places (dimm_devs.c, core.c etc) include label.h but only
>> label.c uses NSINDEX_SIGNATURE, so move its definition to label.c
>> instead.
>> In file included from
+#ifndef _SOC_QCOM_RMNET_H_
+#define _SOC_QCOM_RMNET_H_
+
+#include
+
+/* Header structure that precedes packets in ETH_P_MAP protocol */
+struct rmnet_map_header {
+ u8 pad_len : 6;
+ u8 reserved_bit: 1;
+ u8 cd_bit : 1;
+ u8 mux_id;
On Wed, 15 May 2019 16:31:34 -0700
Linus Torvalds wrote:
> On Wed, May 15, 2019 at 4:29 PM Linus Torvalds
> wrote:
> >
> > One option is to just rewrite it something like
> >
> > const unsigned int offset = offsetof(struct trace_iterator, seq);
> > memset(offset+(void *), 0,
在 2019年05月15日 21:30, Borislav Petkov 写道:
> On Tue, Apr 30, 2019 at 03:44:20PM +0800, Lianbo Jiang wrote:
>> When SEV is active, the second kernel image is loaded into the
>> encrypted memory. Lets make sure that when kexec builds the
>> identity mapping page table it adds the memory encryption
Fix build warning,
kernel/fork.c:125:5: warning: symbol 'max_threads' was not declared. Should it
be static?
Reported-by: Hulk Robot
Signed-off-by: Kefeng Wang
---
kernel/fork.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/fork.c b/kernel/fork.c
index
On Wed, 2019-05-15 at 17:26 -0700, Dan Williams wrote:
> On Wed, May 15, 2019 at 5:25 PM Verma, Vishal L
> wrote:
> > On Wed, 2019-05-15 at 16:25 -0700, Dan Williams wrote:
> > > > diff --git a/drivers/nvdimm/btt.c b/drivers/nvdimm/btt.c
> > > > index 4671776f5623..9f02a99cfac0 100644
> > > >
Hi all,
Today's linux-next merge of the ftrace tree got a conflict in:
include/linux/compiler.h
between commit:
37686b1353cf ("tracing: Improve "if" macro code generation")
from Linus' tree and commit:
a15fd609ad53 ("tracing: Simplify "if" macro code")
from the ftrace tree.
I fixed
On Thu, 16 May 2019 at 02:42, Ankur Arora wrote:
>
> On 5/14/19 6:50 AM, Marcelo Tosatti wrote:
> > On Mon, May 13, 2019 at 05:20:37PM +0800, Wanpeng Li wrote:
> >> On Wed, 8 May 2019 at 02:57, Marcelo Tosatti wrote:
> >>>
> >>>
> >>> Certain workloads perform poorly on KVM compared to baremetal
On Wed, 2019-05-15 at 06:20 +, Christophe Leroy wrote:
> Strict module RWX is just like strict kernel RWX, but for modules -
> so
> loadable modules aren't marked both writable and executable at the
> same
> time. This is handled by the generic code in kernel/module.c, and
> simply requires
On Wed, May 15, 2019 at 04:44:19PM -0600, shuah wrote:
Hi Sasha and Dhaval,
On 4/11/19 11:37 AM, Dhaval Giani wrote:
Hi Folks,
This is a call for participation for the Linux Testing microconference
at LPC this year.
For those who were at LPC last year, as the closing panel mentioned,
testing
On 2019/5/16 7:48, Mao, Chenxi wrote:
> Hi Yann and Xiang:
> For this FAST_DEC_LOOP change, I only pick up decompress related patches to
> current kernel LZ4 implementation(based on 1.8.3).
> Here is my cherry-pick list:
> 2589c44 created LZ4_FAST_DEC_LOOP build macro
> 605d811 enable
1 - 100 of 1557 matches
Mail list logo
