Hello Greg,
This is v2 of the pull request for habanalabs driver for kernel 5.3.
v2 contains the missing sign-off-by tags for the relevant commits.
The commits mostly contains improvements to the existing code base.
Nothing too exciting this time.
Please see the tag message for details on what
If QCOM_Q6V5_MSS is set but QCOM_MDT_LOADER is not,
building will fails:
drivers/remoteproc/qcom_q6v5_mss.o: In function `q6v5_start':
qcom_q6v5_mss.c:(.text+0x3260): undefined reference to `qcom_mdt_read_metadata'
Add QCOM_MDT_LOADER dependency for QCOM_Q6V5_MSS.
Reported-by: Hulk Robot
Fixes:
On Thu, Jul 4, 2019 at 9:41 AM Greg KH wrote:
>
> On Thu, Jul 04, 2019 at 08:40:10AM +0200, Greg KH wrote:
> > On Thu, Jul 04, 2019 at 09:22:59AM +0300, Oded Gabbay wrote:
> > > Hello Greg,
> > >
> > > This is the pull request for habanalabs driver for kernel 5.3.
> > >
> > > It mostly contains im
On 2019/6/29 10:42, Xiongfeng Wang wrote:
We set 'cpu_possible_mask' based on the enabled GICC node in MADT. If
the GICC node is disabled, we will skip initializing the kernel data
structure for that CPU.
To support CPU hotplug, we need to initialize some CPU related data
structure in advance.
On 7/4/2019 1:32 AM, Mathieu Poirier wrote:
Hi Greg,
On Thu, 27 Jun 2019 at 12:15, Sai Prakash Ranjan
wrote:
Do not assume the affinity to CPU0 if cpu phandle is omitted.
Update the DT binding rules to reflect the same by changing it
to a required property.
Signed-off-by: Sai Prakash Ranjan
On Thu, Jul 04, 2019 at 08:40:10AM +0200, Greg KH wrote:
> On Thu, Jul 04, 2019 at 09:22:59AM +0300, Oded Gabbay wrote:
> > Hello Greg,
> >
> > This is the pull request for habanalabs driver for kernel 5.3.
> >
> > It mostly contains improvements to the existing code base. Nothing too
> > excitin
On Thu, Jul 04, 2019 at 09:22:59AM +0300, Oded Gabbay wrote:
> Hello Greg,
>
> This is the pull request for habanalabs driver for kernel 5.3.
>
> It mostly contains improvements to the existing code base. Nothing too
> exciting this time.
>
> Please see the tag message for details on what this p
Hi Steve,
Would you have any comment on this?
Thank you,
On Thu, 20 Jun 2019 00:07:09 +0900
Masami Hiramatsu wrote:
> Hello,
>
> This is the 2nd version of multi-probes per event support on ftrace
> and perf-tools.
>
> Previous version is here;
> https://lkml.org/lkml/2019/5/31/573
>
> >Fro
On 2019/7/4 下午2:21, Tiwei Bie wrote:
On Thu, Jul 04, 2019 at 12:31:48PM +0800, Jason Wang wrote:
On 2019/7/3 下午9:08, Tiwei Bie wrote:
On Wed, Jul 03, 2019 at 08:16:23PM +0800, Jason Wang wrote:
On 2019/7/3 下午7:52, Tiwei Bie wrote:
On Wed, Jul 03, 2019 at 06:09:51PM +0800, Jason Wang wrote:
aused by commit
3db1b636c07e ("usb:gadget Separated decoding functions from dwc3 driver.")
I have used the usb tree from next-20190703 for today.
This also occurs in the usb-gadget tree so I have used the version of
that from next-20190703 as well.
--
Cheers,
Stephen Rothwell
pgp7D8wqoqEie
On 7/4/19 12:57 AM, Paul Walmsley wrote:
Hi Alex,
Thanks for writing and testing these patches, and thanks for your patience
waiting for reviews and testing.
No problem :)
On Mon, 1 Jul 2019, Alexandre Ghiti wrote:
This series introduces hugetlbfs support for both riscv 32/64. Riscv32
is
在 2019/7/4 10:04, Jason Gunthorpe 写道:
> On Thu, Jul 04, 2019 at 12:02:35PM +1000, Stephen Rothwell wrote:
>> Hi all,
>>
>> On Mon, 1 Jul 2019 14:14:31 +1000 Stephen Rothwell
>> wrote:
>>> Hi all,
>>>
>>> After merging the rdma tree, today's linux-next build (x86_64
>>> allmodconfig) failed like t
On Thu, 2019-07-04 at 07:41 +0200, Greg KH wrote:
> On Thu, Jul 04, 2019 at 08:57:53AM +1000, Benjamin Herrenschmidt
> wrote:
> > On Wed, 2019-07-03 at 21:37 +0200, Greg KH wrote:
> > > Ok, I guess I have to take this patch, as the other one is so bad
> > > :)
> > >
> > > But, I need a very large
On Thu, Jul 04, 2019 at 04:17:30PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> After merging the driver-core tree, today's linux-next build (arm
> multi_v7_defconfig) produced this warning:
>
> fs/ubifs/debug.c: In function 'dbg_debugfs_init_fs':
> fs/ubifs/debug.c:2812:6: warning: unused variab
On Thu, 2019-07-04 at 07:40 +0200, Greg KH wrote:
> On Thu, Jul 04, 2019 at 08:57:13AM +1000, Benjamin Herrenschmidt
> wrote:
> > On Wed, 2019-07-03 at 21:36 +0200, Greg KH wrote:
> > >
> > > > -static struct kobject *get_device_parent(struct device *dev,
> > > > -
On Thu, Jul 04, 2019 at 12:47:38PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the mlx5-next tree got a conflict in:
>
> drivers/infiniband/hw/mlx5/cq.c
>
> between commit:
>
> e39afe3d6dbd ("RDMA: Convert CQ allocations to be under core
> responsibility")
>
> from
Fix Kconfig warning for PCENGINES_APU2 symbol:
WARNING: unmet direct dependencies detected for GPIO_AMD_FCH
Depends on [n]: GPIOLIB [=n] && HAS_IOMEM [=y]
Selected by [y]:
- PCENGINES_APU2 [=y] && X86 [=y] && X86_PLATFORM_DEVICES [=y] && INPUT [=y]
&& INPUT_KEYBOARD [=y] && LEDS_CLASS [=y]
On 5/13/2019 3:54 PM, Viresh Kumar wrote:
The OPP core requires the virtual device pointers to set performance
state on behalf of the device, for the multiple power domain case. The
genpd API (dev_pm_domain_attach_by_name()) has evolved now to support
even the single power domain case and that
Hi all,
After merging the driver-core tree, today's linux-next build (x86_64
allmodconfig) produced this warning:
fs/orangefs/orangefs-debugfs.c: In function 'orangefs_debugfs_init':
fs/orangefs/orangefs-debugfs.c:193:1: warning: label 'out' defined but not used
[-Wunused-label]
out:
^~~
fs/or
From: Anson Huang
Assign highest OPP as suspend OPP to reduce suspend/resume
latency on i.MX8MM.
Signed-off-by: Anson Huang
---
This patch is based on https://patchwork.kernel.org/patch/11023813/
---
arch/arm64/boot/dts/freescale/imx8mm.dtsi | 1 +
1 file changed, 1 insertion(+)
diff --git a/
From: Anson Huang
Assign highest OPP as suspend OPP to reduce suspend/resume
latency on i.MX8MQ.
Signed-off-by: Anson Huang
---
This patch is based on https://patchwork.kernel.org/patch/11023815/
---
arch/arm64/boot/dts/freescale/imx8mq.dtsi | 2 ++
1 file changed, 2 insertions(+)
diff --git
Hello Greg,
This is the pull request for habanalabs driver for kernel 5.3.
It mostly contains improvements to the existing code base. Nothing too
exciting this time.
Please see the tag message for details on what this pull request contains.
Thanks,
Oded
The following changes since commit 60e85
On Thu, Jul 04, 2019 at 12:31:48PM +0800, Jason Wang wrote:
> On 2019/7/3 下午9:08, Tiwei Bie wrote:
> > On Wed, Jul 03, 2019 at 08:16:23PM +0800, Jason Wang wrote:
> > > On 2019/7/3 下午7:52, Tiwei Bie wrote:
> > > > On Wed, Jul 03, 2019 at 06:09:51PM +0800, Jason Wang wrote:
> > > > > On 2019/7/3 下午5
On 2019/7/4 14:04, Jia He wrote:
> Hi Xiongfeng
>
> Sorry, I missed your latter mail, you used a emulated SCI interrupt
Yes, I only used a emulated SCI interrupt. My colleague is working on the qemu
part.
He used the GED device in qemu. But there is still some other issues with the
qemu
and
Hi all,
After merging the driver-core tree, today's linux-next build (arm
multi_v7_defconfig) produced this warning:
fs/ubifs/debug.c: In function 'dbg_debugfs_init_fs':
fs/ubifs/debug.c:2812:6: warning: unused variable 'err' [-Wunused-variable]
int err, n;
^~~
Introduced by commit
70
Fixes checkpatch warning "Comparison to NULL could be written [...]".
Signed-off-by: Simon Sandström
---
drivers/staging/kpc2000/kpc2000_spi.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/kpc2000/kpc2000_spi.c
b/drivers/staging/kpc2000/kpc2000_spi.c
in
Fixes checkpatch warning "Comparison to NULL could be written [...]".
Signed-off-by: Simon Sandström
---
drivers/staging/kpc2000/kpc_dma/fileops.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/kpc2000/kpc_dma/fileops.c
b/drivers/staging/kpc2000/kpc_dma/file
Fixes checkpatch warning "Comparison to NULL could be written [...]".
Signed-off-by: Simon Sandström
---
drivers/staging/kpc2000/kpc_dma/dma.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/kpc2000/kpc_dma/dma.c
b/drivers/staging/kpc2000/kpc_dma/dma.c
in
Hi,
These patches simplifies a few comparisons to NULL ("foo == NULL" =>
"!foo") in staging/kpc2000, as reported by checkpatch.pl.
- Simon
Simon Sandström (3):
staging: kpc2000: simplify comparison to NULL in kpc2000_spi.c
staging: kpc2000: simplify comparison to NULL in dma.c
staging: kpc
All fpu__xstate_clear_all_cpu_caps() does is to invoke one simple
function since commit
73e3a7d2a7c3b ("x86/fpu: Remove the explicit clearing of XSAVE dependent
features")
so it will be better to simply invoke that function directly.
Inline fpu__xstate_clear_all_cpu_caps().
Signed-off-by: Se
> > > > @@ -155,22 +171,26 @@ static int stmmac_mdio_read(struct mii_bus
> > > > *bus,
> > > int phyaddr, int phyreg)
> > > > struct stmmac_priv *priv = netdev_priv(ndev);
> > > > unsigned int mii_address = priv->hw->mii.addr;
> > > > unsigned int mii_data = priv->hw->mii.da
Hi Xiongfeng
Sorry, I missed your latter mail, you used a emulated SCI interrupt
---
Cheers,
Justin (Jia He)
On 2019/7/4 11:26, Xiongfeng Wang wrote:
Hi Justin,
On 2019/7/4 11:00, Jia He wrote:
Hi Xiongfeng
It is a little bit awkful that I am also investigating acpi based cpu hotplug
issu
On Wed, 3 Jul 2019 at 05:32, Benjamin Herrenschmidt
wrote:
>
> On Wed, 2019-07-03 at 03:39 +, Joel Stanley wrote:
> > Hello Greg,
> >
> > We've not had a MAINAINERS entry for drivers/fsi, so this fixes that. It
> > names
> > Jeremy and I as maintainers, so if it works for you we will send pul
This is a driver, do not call "raw" sysfs functions, instead call driver
core ones. Specifically convert the use of sysfs_create_files() and
sysfs_remove_files() to use device_add_groups() and
device_remove_groups()
Cc: Wu Hao
Cc: Alan Tull
Cc: Moritz Fischer
Cc: linux-f...@vger.kernel.org
Sig
On Wed, 3 Jul 2019 22:01:05 -0400
Steven Rostedt wrote:
> On Thu, 4 Jul 2019 10:51:26 +0900
> Masami Hiramatsu wrote:
>
> > > > diff --git a/tools/testing/selftests/ftrace/test.d/functions
> > > > b/tools/testing/selftests/ftrace/test.d/functions
> > > > index 779ec11f61bd..a7b06291e32c 100644
Hi Xiongfeng
On 2019/7/4 11:26, Xiongfeng Wang wrote:
Hi Justin,
On 2019/7/4 11:00, Jia He wrote:
Hi Xiongfeng
It is a little bit awkful that I am also investigating acpi based cpu hotplug
issue silimar with
your idea. My question is your purpose to implement the vcpu hotplug in arm64
qem
On Wed, 2019-07-03 at 08:37 -0700, Joe Perches wrote:
> On Wed, 2019-07-03 at 17:03 +0800, Yingjoe Chen wrote:
> > On Wed, 2019-07-03 at 01:42 -0700, Joe Perches wrote:
> > > On Wed, 2019-07-03 at 16:30 +0800, Miles Chen wrote:
> > > > This change reports a warning when "default n" is used.
> > > >
On Thu, Jul 04, 2019 at 08:57:53AM +1000, Benjamin Herrenschmidt wrote:
> On Wed, 2019-07-03 at 21:37 +0200, Greg KH wrote:
> > Ok, I guess I have to take this patch, as the other one is so bad :)
> >
> > But, I need a very large comment here saying why we are poking around in
> > a kref and why w
On Thu, Jul 04, 2019 at 08:57:13AM +1000, Benjamin Herrenschmidt wrote:
> On Wed, 2019-07-03 at 21:36 +0200, Greg KH wrote:
> >
> > > -static struct kobject *get_device_parent(struct device *dev,
> > > - struct device *parent)
> > > +/**
> > > + * __get_device_pare
On Wed, 3 Jul 2019, Andrew F. Davis wrote:
On 7/2/19 6:12 AM, Nikolaus Voss wrote:
On Mon, 1 Jul 2019, Andrew F. Davis wrote:
On 7/1/19 11:35 AM, Nikolaus Voss wrote:
On Mon, 1 Jul 2019, Andrew F. Davis wrote:
On 7/1/19 9:42 AM, Nikolaus Voss wrote:
Replace enum tas572x_type with struct tas5
Tested and booted in my x86 system. No regressions.
Tested and booted on my x86 system. No regressions.
Booted and tested in my x86 systems. No regressions.
Hi,
I'm in the process of updating our products from a 4.4 based kernel to
5.1 (and probably 5.2 since that release is imminent).
On one product which uses a Freescale/NXP P2041 CPU, IDT pcie bridge and
Marvell switch chip[1].
Annoyingly the hardware has a reset line that holds the switch chip
On Tue, Jun 25, 2019 at 1:31 AM Matthias Kaehlcke wrote:
>
> gen_compile_command.py currently assumes that the .cmd files and the
> source code live in the same directory, which is not the case when
> a separate KBUILD_OUTPUT directory is used.
>
> Add a new option to specify this the kbuild outpu
It is possible that the rcuperf kernel test runs concurrently with init
starting up. During this time, the system is running all grace periods
as expedited. However, rcuperf can also be run for normal GP tests.
Right now, it depends on a holdoff time before starting the test to
ensure grace perio
On 2019/7/3 下午9:08, Tiwei Bie wrote:
On Wed, Jul 03, 2019 at 08:16:23PM +0800, Jason Wang wrote:
On 2019/7/3 下午7:52, Tiwei Bie wrote:
On Wed, Jul 03, 2019 at 06:09:51PM +0800, Jason Wang wrote:
On 2019/7/3 下午5:13, Tiwei Bie wrote:
Details about this can be found here:
https://lwn.net/Artic
The NMI handlers handle_percpu_devid_fasteoi_nmi() and
handle_fasteoi_nmi() added by commit 2dcf1fbcad35 ("genirq: Provide NMI
handlers") do not update the interrupt counts. Due to that the NMI
interrupt count does not show up correctly in /proc/interrupts.
Update the functions to fix this. With t
desc->flags may already have values set by of_gpiochip_add() so make
sure that this isn't undone when setting the initial direction.
Fixes: 3edfb7bd76bd1cba ("gpiolib: Show correct direction from the beginning")
Signed-off-by: Chris Packham
---
Notes:
Changes in v2:
- add braces to avoid
On Wed, Jul 03, 2019 at 04:25:52PM +0800, Kefeng Wang wrote:
> pcpu_setup_first_chunk() will panic or BUG_ON if the are some
> error and doesn't return any error, hence it can be defined to
> return void.
>
> Signed-off-by: Kefeng Wang
> ---
> arch/ia64/mm/contig.c| 5 +
> arch/ia64/mm/
在 2019/7/4 12:07, wangxi 写道:
>
>
> 在 2019/7/4 10:04, Jason Gunthorpe 写道:
>> On Thu, Jul 04, 2019 at 12:02:35PM +1000, Stephen Rothwell wrote:
>>> Hi all,
>>>
>>> On Mon, 1 Jul 2019 14:14:31 +1000 Stephen Rothwell
>>> wrote:
Hi all,
After merging the rdma tree, today's lin
在 2019/7/4 10:04, Jason Gunthorpe 写道:
> On Thu, Jul 04, 2019 at 12:02:35PM +1000, Stephen Rothwell wrote:
>> Hi all,
>>
>> On Mon, 1 Jul 2019 14:14:31 +1000 Stephen Rothwell
>> wrote:
>>>
>>> Hi all,
>>>
>>> After merging the rdma tree, today's linux-next build (x86_64
>>> allmodconfig) failed
On 2019/6/28 下午8:36, Stefano Garzarella wrote:
Before to call vdev->config->reset(vdev) we need to be sure that
no one is accessing the device, for this reason, we add new variables
in the struct virtio_vsock to stop the workers during the .remove().
This patch also add few comments before vde
On 2019/7/3 下午6:41, Stefano Garzarella wrote:
On Wed, Jul 03, 2019 at 05:53:58PM +0800, Jason Wang wrote:
On 2019/6/28 下午8:36, Stefano Garzarella wrote:
Some callbacks used by the upper layers can run while we are in the
.remove(). A potential use-after-free can happen, because we free
the_vi
Hi all,
Today's linux-next merge of the device-mapper tree got a conflict in:
Documentation/device-mapper/snapshot.rst
between commit:
f0ba43774cea ("docs: convert docs to ReST and rename to *.rst")
from the jc_docs tree and commit:
a8a9f1434a86 ("dm snapshot: add optional discard suppo
The nr_allocated_banks and allocated banks are initialized as part of
tpm_chip_register. Currently, this is done as part of auto startup
function. However, some drivers, like the ibm vtpm driver, do not run
auto startup during initialization. This results in uninitialized memory
issue and causes a
On Thu, Jul 04, 2019 at 01:33:16AM +, Voon, Weifeng wrote:
> > > @@ -155,22 +171,26 @@ static int stmmac_mdio_read(struct mii_bus *bus,
> > int phyaddr, int phyreg)
> > > struct stmmac_priv *priv = netdev_priv(ndev);
> > > unsigned int mii_address = priv->hw->mii.addr;
> > > unsigned int
Hi Justin,
On 2019/7/4 11:00, Jia He wrote:
> Hi Xiongfeng
>
> It is a little bit awkful that I am also investigating acpi based cpu
> hotplug issue silimar with
>
> your idea. My question is your purpose to implement the vcpu hotplug in arm64
> qemu?
Yes, my purpose is to implement the vcpu
On Wed, Jul 03, 2019 at 02:28:41PM -0700, Dan Williams wrote:
> On Wed, Jul 3, 2019 at 12:53 PM Matthew Wilcox wrote:
> > @@ -211,7 +215,8 @@ static void *get_unlocked_entry(struct xa_state *xas)
> > for (;;) {
> > entry = xas_find_conflict(xas);
> > if (!en
This initial implementation of a tiny subset of DTrace functionality
provides the following options:
dtrace [-lvV] [-b bufsz] -s script
-b set trace buffer size
-l list probes (only works with '-s script' for now)
-s enable or list probes for the spec
This patch is also available, applied to bpf-next, at the following URL:
https://github.com/oracle/dtrace-linux-kernel/tree/dtrace-bpf
As suggested in feedback to my earlier patch submissions, this code takes an
approach to avoid kernel code changes as much as possible. The current patch
Hi Xiongfeng
It is a little bit awkful that I am also investigating acpi based cpu hotplug
issue silimar with
your idea. My question is your purpose to implement the vcpu hotplug in arm64
qemu?
Thanks for the ellaboration
---
Cheers,
Justin (Jia He)
On 2019/6/28 19:13, Xiongfeng Wang wrot
Hi Lorenzo,
Thanks for your comments!
> -Original Message-
> From: Lorenzo Pieralisi
> Sent: 2019年7月3日 23:19
> To: Z.q. Hou
> Cc: linux-...@vger.kernel.org; linux-arm-ker...@lists.infradead.org;
> devicet...@vger.kernel.org; linux-kernel@vger.kernel.org;
> bhelg...@google.com; robh...@k
Remove unneeded memset as alloc_etherdev is using kvzalloc which uses
__GFP_ZERO flag
Signed-off-by: Hariprasad Kelam
---
drivers/net/ethernet/allwinner/sun4i-emac.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/net/ethernet/allwinner/sun4i-emac.c
b/drivers/net/ethernet/allwinner/s
Hi all,
Today's linux-next merge of the mlx5-next tree got a conflict in:
drivers/infiniband/hw/mlx5/cq.c
between commit:
e39afe3d6dbd ("RDMA: Convert CQ allocations to be under core responsibility")
from the rdma tree and commit:
38164b771947 ("net/mlx5: mlx5_core_create_cq() enhanceme
Add "gfp_t" support in synthetic_events, then the "gfp_t" type
parameter in some functions can be traced.
Signed-off-by: Zhengjun Xing
---
kernel/trace/trace_events_hist.c | 4
1 file changed, 4 insertions(+)
diff --git a/kernel/trace/trace_events_hist.c b/kernel/trace/trace_events_hist.c
With some upcoming patches to save/restore the Hyper-V drivers related
states, a Linux VM running on Hyper-V will be able to hibernate. When
a Linux VM hibernates, unluckily we must disable the memory hot-add/remove
and balloon up/down capabilities in the hv_balloon driver
(drivers/hv/hv_balloon.
Hi Lorenzo,
Thanks for your comments!
> -Original Message-
> From: Lorenzo Pieralisi
> Sent: 2019年7月3日 23:10
> To: Z.q. Hou
> Cc: linux-...@vger.kernel.org; linux-arm-ker...@lists.infradead.org;
> devicet...@vger.kernel.org; linux-kernel@vger.kernel.org;
> bhelg...@google.com; robh...@k
Hi Lorenzo,
Thanks for your comments!
> -Original Message-
> From: Lorenzo Pieralisi
> Sent: 2019年7月3日 22:17
> To: Z.q. Hou
> Cc: linux-...@vger.kernel.org; linux-arm-ker...@lists.infradead.org;
> devicet...@vger.kernel.org; linux-kernel@vger.kernel.org;
> bhelg...@google.com; robh...@k
Several drivers cast a struct device pointer to a struct
platform_device pointer only to then call platform_get_drvdata().
To improve readability, these constructs can be simplified
by using dev_get_drvdata() directly.
Signed-off-by: Fuqian Huang
---
Changes in v2:
- Make the commit message mor
Several drivers cast a struct device pointer to a struct
platform_device pointer only to then call platform_get_drvdata().
To improve readability, these constructs can be simplified
by using dev_get_drvdata() directly.
Signed-off-by: Fuqian Huang
---
Changes in v2:
- Make the commit message mor
Several drivers cast a struct device pointer to a struct
platform_device pointer only to then call platform_get_drvdata().
To improve readability, these constructs can be simplified
by using dev_get_drvdata() directly.
Signed-off-by: Fuqian Huang
---
Changes in v2:
- Make the commit message mor
Several drivers cast a struct device pointer to a struct
platform_device pointer only to then call platform_get_drvdata().
To improve readability, these constructs can be simplified
by using dev_get_drvdata() directly.
Signed-off-by: Fuqian Huang
---
Changes in v2:
- Make the commit message mor
Several drivers cast a struct device pointer to a struct
platform_device pointer only to then call platform_get_drvdata().
To improve readability, these constructs can be simplified
by using dev_get_drvdata() directly.
Signed-off-by: Fuqian Huang
---
Changes in v2:
- Make the commit message mor
Several drivers cast a struct device pointer to a struct
platform_device pointer only to then call platform_get_drvdata().
To improve readability, these constructs can be simplified
by using dev_get_drvdata() directly.
Signed-off-by: Fuqian Huang
---
Changes in v2:
- Make the commit message mor
Several drivers cast a struct device pointer to a struct
platform_device pointer only to then call platform_get_drvdata().
To improve readability, these constructs can be simplified
by using dev_get_drvdata() directly.
Signed-off-by: Fuqian Huang
---
Changes in v2:
- Make the commit message mor
Hi Lorenzo,
Thanks a lot for your comments!
> -Original Message-
> From: Lorenzo Pieralisi
> Sent: 2019年7月3日 18:33
> To: Z.q. Hou
> Cc: linux-...@vger.kernel.org; linux-arm-ker...@lists.infradead.org;
> devicet...@vger.kernel.org; linux-kernel@vger.kernel.org;
> bhelg...@google.com; rob
Primarily this allows the clkout signal to be disabled and save some
power when running off battery backup. However, all hardware implemented
values are implemented. Uses default value of 32768Hz if node is not
specified.
Signed-off-by: Michael McCormick
---
drivers/rtc/rtc-pcf85063.c | 52 +
On Wed, Jul 03, 2019 at 05:30:59PM +0200, Arnd Bergmann wrote:
> clang emits a warning about a negative shift count for an
> unused part of a conditional constant expression:
>
> drivers/soc/rockchip/pm_domains.c:795:21: error: shift count is negative
> [-Werror,-Wshift-count-negative]
>
With the boot parameter "hv_nopvspin" specified a Hyperv guest should
not make use of paravirt spinlocks, but behave as if running on bare
metal. This is not true, however, as the qspinlock code will fall back
to a test-and-set scheme when it is detecting a hypervisor.
In order to avoid this disab
The pull request you sent on Wed, 3 Jul 2019 10:55:11 -0400:
> git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
> trace-v5.2-rc5
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/550d1f5bda33fa3b203d8cf8df1396825dbfd213
Thank you!
--
Deet-doot-dot
The pull request you sent on Wed, 3 Jul 2019 14:30:51 +0200:
> git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio.git
> tags/gpio-v5.2-4
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/179c96d9f715a619811ded5dcbd35b1fee8caf69
Thank you!
--
Deet-doot-dot
在 2019/7/4 10:04, Jason Gunthorpe 写道:
> On Thu, Jul 04, 2019 at 12:02:35PM +1000, Stephen Rothwell wrote:
>> Hi all,
>>
>> On Mon, 1 Jul 2019 14:14:31 +1000 Stephen Rothwell
>> wrote:
>>> Hi all,
>>>
>>> After merging the rdma tree, today's linux-next build (x86_64
>>> allmodconfig) failed like t
Hi Krzysztof,
I am sorry, It is my mistake to forget about VF50 used EDMA IP with little
endian.
The Register(CHCFG0 - CHCFG15) of our platform designed as follows:
*---*
| Offset | Big endian Register| Little endia
Hi all,
Today's linux-next merge of the net-next tree got a conflict in:
tools/testing/selftests/net/config
between commit:
ff95bf28c234 ("selftests/net: skip psock_tpacket test if KALLSYMS was not
enabled")
from the net tree and commit:
af5136f95045 ("selftests/net: SO_TXTIME with ETF
On Thu, Jul 04, 2019 at 12:02:35PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> On Mon, 1 Jul 2019 14:14:31 +1000 Stephen Rothwell
> wrote:
> >
> > Hi all,
> >
> > After merging the rdma tree, today's linux-next build (x86_64
> > allmodconfig) failed like this:
> >
> > WARNING: modpost: missin
Hi all,
On Mon, 1 Jul 2019 14:14:31 +1000 Stephen Rothwell
wrote:
>
> Hi all,
>
> After merging the rdma tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> WARNING: modpost: missing MODULE_LICENSE() in
> drivers/infiniband/hw/hns/hns_roce_ah.o
> see include/linux/mod
On Thu, 4 Jul 2019 10:51:26 +0900
Masami Hiramatsu wrote:
> > > diff --git a/tools/testing/selftests/ftrace/test.d/functions
> > > b/tools/testing/selftests/ftrace/test.d/functions
> > > index 779ec11f61bd..a7b06291e32c 100644
> > > --- a/tools/testing/selftests/ftrace/test.d/functions
> > > +++
On Wed, 3 Jul 2019 16:00:09 -0400
Steven Rostedt wrote:
> On Wed, 03 Jul 2019 15:50:01 -0400
> Steven Rostedt wrote:
>
> > From: "Steven Rostedt (VMware)"
> >
> > While testing on a very old kernel (3.5), the tests failed because the write
> > to set_event_pid in the setup code, did not exist
On Wed, 03 Jul 2019 15:50:01 -0400
Steven Rostedt wrote:
> From: "Steven Rostedt (VMware)"
>
> While testing on a very old kernel (3.5), the tests failed because the write
> to set_event_pid in the setup code, did not exist. The tests themselves
> could pass, but the setup failed causing an err
On Wed, 03 Jul 2019 15:50:00 -0400
Steven Rostedt wrote:
> From: "Steven Rostedt (VMware)"
>
> If the kernel is not configured with ftrace enabled, the ftracetest
> selftests should return the error code of "4" as that is the kselftests
> "skip" code, and not "1" which means an error.
>
> To d
On Wed, Jul 03, 2019 at 12:31:57PM -0600, Alex Williamson wrote:
> On Wed, 3 Jul 2019 17:13:39 +0800
> Tiwei Bie wrote:
> > diff --git a/include/uapi/linux/vfio.h b/include/uapi/linux/vfio.h
> > index 8f10748dac79..6c5718ab7eeb 100644
> > --- a/include/uapi/linux/vfio.h
> > +++ b/include/uapi/lin
> > @@ -155,22 +171,26 @@ static int stmmac_mdio_read(struct mii_bus *bus,
> int phyaddr, int phyreg)
> > struct stmmac_priv *priv = netdev_priv(ndev);
> > unsigned int mii_address = priv->hw->mii.addr;
> > unsigned int mii_data = priv->hw->mii.data;
> > - u32 v;
> > - int data;
> >
On 2019/7/3 21:57, David Howells wrote:
> YueHaibing wrote:
>
>> Fixes gcc '-Wunused-but-set-variable' warning:
>>
>> security/integrity/digsig.c: In function 'integrity_init_keyring':
>> security/integrity/digsig.c:99:18: warning:
>> variable 'acl' set but not used [-Wunused-but-set-variable]
>
In virtualization environment, PV extensions (drivers, interrupts,
timers, etc) are enabled in the majority of use cases which is the
best option.
However, in some cases (kexec not fully working, benchmarking)
we want to disable PV extensions. We have "xen_nopv" for that purpose
but only for XEN.
.. as they are only called at early bootup stage. In fact, other
functions in x86_hyper_xen_hvm.init.* are all marked as __init.
Unexport xen_hvm_need_lapic as it's never used outside.
Signed-off-by: Zhenzhong Duan
Reviewed-by: Juergen Gross
Cc: Boris Ostrovsky
Cc: Stefano Stabellini
Cc: Thom
PVH guest needs PV extentions to work, so "nopv" parameter should be
ignored for PVH but not for HVM guest.
If PVH guest boots up via the Xen-PVH boot entry, xen_pvh is set early,
we know it's PVH guest and ignore "nopv" parameter directly.
If PVH guest boots up via the normal boot entry same as
Hi,
In virtualization environment, PV extensions (drivers, interrupts,
timers, etc) are enabled in the majority of use cases which is the
best option.
However, in some cases (kexec not fully working, benchmarking, etc)
we want to disable PV extensions. We have xen_nopv for that purpose
but only f
Clean up unnecessory code after that operation.
Signed-off-by: Zhenzhong Duan
Cc: Boris Ostrovsky
Cc: Juergen Gross
Cc: Stefano Stabellini
Cc: Thomas Gleixner
Cc: Ingo Molnar
Cc: Borislav Petkov
---
Documentation/admin-guide/kernel-parameters.txt | 2 ++
arch/x86/xen/enlighten_hvm.c
CCed a couple of people.
On Mon, Jun 17, 2019 at 3:15 PM Cedric Hombourger
wrote:
>
> Debian-based distributions place libc header files in a machine
> specific directory (/usr/include/) instead of
> /usr/include/asm to support installation of the linux-libc-dev
> package from multiple architectu
1 - 100 of 1024 matches
Mail list logo
