On Fri, 13 Oct 2017, Nicolas Pitre wrote:
> On Sat, 14 Oct 2017, Al Viro wrote:
>
> > On Fri, Oct 13, 2017 at 04:09:23PM -0400, Nicolas Pitre wrote:
> > > On Fri, 13 Oct 2017, Al Viro wrote:
> > >
> > > > OK... I wonder if it should simply define stubs for kill_mtd_super(),
> > > > mtd_unpoint(
> + pagefault_disable();
> + switch (len) {
> + case 1:
> + if (__get_user(tmp._u8, (uint8_t __user *)p))
> + goto end;
> + tmp._u8 += (uint8_t)count;
> + if (__put_user(tmp._u8, (uint8_t __user *)p))
> + goto e
Last month the vector management code was reworked, and as a result of the
changes, e.g. commit 22d0b12f3560 ("genirq/irqdomain: Add force
reactivation flag to irq domains"), commit 4900be83602b ("x86/vector/msi:
Switch to global reservation mode") etc, now we must add this new flag
MSI_FLAG_MUST_
Could anyone take a look at this patch which fixes the xattr-read
issue? Thanks anyway.
Jason
On Thu, Jun 22, 2017 at 3:21 PM, Jason Xing wrote:
> When doing ecryptfs_read_and_validate_xattr_region(), eCryptfs
> reads only 16 bytes from xattr region. However, the lower filesystem
> like ext4 alw
> That sounds so obvious and stupid that you might go "What do you
> mean?", but for things to work for libraries, they have to work
> together with *other* users, and with *independent* users.
As far as I can see the current model fundamentally only works for
one user per process (because there i
2017-10-12 18:56 GMT+09:00 Masahiro Yamada :
>
> Kbuild works in objtree, not in srctree. So, __FILE__ is prefixed
> with $(srctree)/ for out-of-tree build.
>
> For example, WARN_ON() will look as follows if you built your kernel
> out of source tree:
>
> WARNING: CPU: 1 PID: 1 at /path/to/build/d
Hi Vinod,
On Thu, Sep 28, 2017 at 11:26 PM, Maxime Ripard
wrote:
> On Thu, Sep 28, 2017 at 01:49:17AM +, Stefan Brüns wrote:
>> Commit 3a03ea763a67 ("dmaengine: sun6i: Add support for Allwinner A83T
>> (sun8i) variant") and commit f008db8c00c1 ("dmaengine: sun6i: Add support for
>> Allwinner
The backend has various clocks and reset controls that need to be
enabled and deasserted before register access is possible.
Move the creation of the regmap to after the clocks and reset controls
have been configured where it makes more sense.
Signed-off-by: Chen-Yu Tsai
---
drivers/gpu/drm/sun
Commit 4636ce93d5b2 ("drm/fb-cma-helper: Add drm_fb_cma_get_gem_addr()")
adds a new helper, which covers fetching a drm_framebuffer's GEM object
and calculating the buffer address for a given plane.
This patch uses this helper to replace our own open coded version of the
same function.
Signed-off
While debugging inverted color from the HDMI output on the A10, I
found that the lowest 3 bits were set. These were cleared on A20
boards that had normal display output. By manually toggling these
bits the mapping of the color components to these bits was found.
While these are not used anywhere,
Many of the backend's layer configuration registers have undefined
default values. This poses a risk as we use regmap_update_bits in
some places, and don't overwrite the whole register.
At probe/bind time we explicitly clear all the control registers
by writing 0 to them. This patch adds a more de
Hi,
Here's another bunch of cleanups for sun4i-drm. Most of these were
found while working on A10/A20 DRM and HDMI support. To be clear,
nothing was broken before these patches.
Patch 1 trims the sun4i-drm probe sequence by not adding repeating
components. The component can deal with duplicates,
The display backend, as well as other peripherals that have a DRAM
clock gate and access DRAM directly, bypassing the system bus,
address the DRAM starting from 0x0, while physical addresses the
system uses starts from 0x4000 (or 0x2000 in A80's case).
Correct the address configured into t
Initially we configured the PAD_CTRL1 register at probe/bind time.
However it seems the HDMI controller will modify some of the bits
in this register by itself. On the A10 it is particularly annoying
as it toggles the output invert bits, which inverts the colors on
the display output.
The U-boot d
Even though the components framework can handle duplicate entries,
the extra entries cause a lot more debug messages to be generated,
which would be confusing to developers not familiar with our driver
and the framework in general.
Instead, we can scan the relatively small queue and check if the
c
On Fri, Oct 13, 2017 at 8:01 PM, Andi Kleen wrote:
>
> As far as I can see the current model fundamentally only works for
> one user per process (because there is only a single range and abort IP)
No, it should work for libraries, you just need to always initialize
the proper start/commit/abort I
On 10/13/2017 04:10 PM, Hoan Tran wrote:
This patch supports xgene-hwmon v2 which uses the non-cachable memory
as the PCC shared memory.
Signed-off-by: Hoan Tran
---
v3
- Use local version variable
- Use inline calls instead of the private map function
v2
- Map PCC shared mem by ioremap(
Hi Guenter,
On Fri, Oct 13, 2017 at 9:28 PM, Guenter Roeck wrote:
> On 10/13/2017 04:10 PM, Hoan Tran wrote:
>>
>> This patch supports xgene-hwmon v2 which uses the non-cachable memory
>> as the PCC shared memory.
>>
>> Signed-off-by: Hoan Tran
>> ---
>> v3
>> - Use local version variable
>>
On Fri, Oct 13, 2017 at 4:49 PM, Brian Gerst wrote:
> On Fri, Oct 13, 2017 at 5:03 PM, Andy Lutomirski wrote:
>> On Fri, Oct 13, 2017 at 1:39 PM, Dave Hansen
>> wrote:
>>>
>>> I noticed that we don't have tracepoints for sys_modify_ldt(). I
>>> think that's because we define it directly instead
On 10/13/2017 09:38 PM, Hoan Tran wrote:
Hi Guenter,
On Fri, Oct 13, 2017 at 9:28 PM, Guenter Roeck wrote:
On 10/13/2017 04:10 PM, Hoan Tran wrote:
This patch supports xgene-hwmon v2 which uses the non-cachable memory
as the PCC shared memory.
Signed-off-by: Hoan Tran
---
v3
- Use local
Hi
On Fri, Oct 13, 2017 at 9:54 PM, Guenter Roeck wrote:
> On 10/13/2017 09:38 PM, Hoan Tran wrote:
>>
>> Hi Guenter,
>>
>> On Fri, Oct 13, 2017 at 9:28 PM, Guenter Roeck wrote:
>>>
>>> On 10/13/2017 04:10 PM, Hoan Tran wrote:
This patch supports xgene-hwmon v2 which uses the non-
On Fri, Oct 13, 2017 at 02:23:07PM -0600, Jens Axboe wrote:
> On 10/13/2017 01:21 PM, Jens Axboe wrote:
> > On 10/13/2017 01:08 PM, Jens Axboe wrote:
> >> On 10/13/2017 12:05 PM, Ming Lei wrote:
> >>> Hi Jens,
> >>>
> >>> In Red Hat internal storage test wrt. blk-mq scheduler, we found that I/O
> >
Hi,
On Oct 14 2017 07:46, PaX Team wrote:
> what KERNEXEC on i386 does is that it executes kernel code in its own 0-based
> code segment hence the 'low' code addresses. due to the current logic that
> checks for SNDRV_CTL_ELEM_ACCESS_TLV_CALLBACK in get_kctl_0dB_offset, this
> callback address is
There is a lot of error checking in place for the format of the WMI
descriptor buffer, but some of the potentially raised issues should
be considered critical failures.
If the buffer size or header don't match, this is a good indication
that the buffer format changed in a way that the rest of the
The existing way that the dell-smbios helper module and associated
other drivers (dell-laptop, dell-wmi) communicate with the platform
really isn't secure. It requires creating a buffer in physical
DMA32 memory space and passing that to the platform via SMM.
Since the platform got a physical memo
For WMI operations that are only Set or Query read or write sysfs
attributes created by WMI vendor drivers make sense.
For other WMI operations that are run on Method, there needs to be a
way to guarantee to userspace that the results from the method call
belong to the data request to the method c
Method type WMI objects need to be able to describe the size of
the interface that they will expect to use.
Export this information to sysfs and allow vendor drivers to
set it.
Signed-off-by: Mario Limonciello
---
drivers/platform/x86/wmi.c | 31 +++
include/linux/wm
When a userspace interface is introduced to dell-smbios filtering
support will be used to make sure that userspace doesn't make calls
deemed unsafe or that can cause the kernel drivers to get out of
sync.
A blacklist is provided for the following:
- Items that are in use by other kernel drivers
-
The dell-smbios stack only currently uses an SMI interface which grants
direct access to physical memory to the firmware SMM methods via a pointer.
This dispatcher driver adds a WMI-ACPI interface that is detected by WMI
probe and preferred over the SMI interface in dell-smbios.
Changing this to
Some cases the wrong type was used for errors and checks can be
done more cleanly.
Signed-off-by: Mario Limonciello
Reviewed-by: Edward O'Callaghan
Suggested-by: Andy Shevchenko
---
drivers/platform/x86/dell-wmi.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/d
Currently userspace tools can access system tokens via the dcdbas
kernel module and a SMI call that will cause the platform to execute
SMM code.
With a goal in mind of deprecating the dcdbas kernel module a different
method for accessing these tokens from userspace needs to be created.
This is in
WSMT is as an attestation to the OS that the platform won't
modify memory outside of pre-defined areas.
If a platform has WSMT enabled in BIOS setup, SMM calls through
dcdbas will fail. The only way to access platform data in these
instances is through the WMI SMBIOS calling interface.
Signed-of
This splits up the dell-smbios driver into two drivers:
* dell-smbios
* dell-smbios-smm
dell-smbios can operate with multiple different dispatcher drivers to
perform SMBIOS operations.
Also modify the interface that dell-laptop and dell-wmi use align to this
model more closely. Rather than a sin
The proper way to indicate that a system is a 'supported' Dell System
is by the presence of this string in OEM strings.
Allowing the driver to load on non-Dell systems will have undefined
results.
Signed-off-by: Mario Limonciello
---
drivers/platform/x86/dell-smbios.c | 7 +++
1 file change
It's important for the driver to provide a R/W ioctl to ensure that
two competing userspace processes don't race to provide or read each
others data.
This userspace character device will be used to perform SMBIOS calls
from any applications.
It provides an ioctl that will allow passing the WMI ca
All communication on individual GUIDs should occur in separate drivers.
Allowing a driver to communicate with the bus to another GUID is just
a hack that discourages drivers to adopt the bus model.
The information found from the WMI descriptor driver is now exported
for use by other drivers.
Sign
Some platforms this year will be adopting 32k WMI buffer, so don't
complain when encountering those.
Signed-off-by: Mario Limonciello
---
drivers/platform/x86/dell-wmi.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/platform/x86/dell-wmi.c b/drivers/platform/x86
The only driver using this was dell-wmi, and it really was a hack.
The driver was getting a data attribute from another driver and this
type of action should not be encouraged.
Rather drivers that need to interact with one another should pass
data back and forth via exported functions.
Signed-off
Drivers properly using the wmibus can pass their wmi_device
pointer rather than the GUID back to the WMI bus to evaluate
the proper methods.
Any "new" drivers added that use the WMI bus should use this
rather than the old wmi_evaluate_method that would take the
GUID.
Signed-off-by: Mario Limoncie
> On 13 Oct 2017, at 17.58, Javier González wrote:
>
>
>>> On 13 Oct 2017, at 17.35, Rakesh Pandit wrote:
>>>
On Fri, Oct 13, 2017 at 07:58:09AM -0700, Christoph Hellwig wrote:
On Fri, Oct 13, 2017 at 02:45:51PM +0200, Matias Bjørling wrote:
From: Rakesh Pandit
When
Hi Bhumika,
[auto build test WARNING on balbi-usb/next]
[also build test WARNING on v4.14-rc4 next-20171013]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Bhumika-Goyal/usb-gadget-configfs
Hi Arnd,
Le 13/10/2017 à 13:15, Arnd Bergmann a écrit :
> On Wed, Oct 11, 2017 at 10:03 AM, Cyrille Pitchen
> wrote:
>> Le 25/08/2017 à 10:12, Bin Meng a écrit :
>>> The Intel SPI-NOR driver is dependent on LPC_ICH to get the platform
>>> data. Select it in the Kconfig.
>>>
>>> Signed-off-by: Bin
Hi all,
+ Arnd, who reported this issue too
Le 14/10/2017 à 02:31, Randy Dunlap a écrit :
> On 10/13/17 14:06, Mark Brown wrote:
>> Changes since 20171012:
>>
>> The rdma tree gained a conflict.
>
>
> on i386:
>
> CONFIG_PCI is not enabled.
>
> ../drivers/mfd/lpc_ich.c: In function 'lpc_ich_i
On Sat, Oct 14, 2017 at 12:42 AM, Andy Lutomirski wrote:
> On Fri, Oct 13, 2017 at 4:49 PM, Brian Gerst wrote:
>> On Fri, Oct 13, 2017 at 5:03 PM, Andy Lutomirski wrote:
>>> On Fri, Oct 13, 2017 at 1:39 PM, Dave Hansen
>>> wrote:
I noticed that we don't have tracepoints for sys_modify
Just to be explicit what I've had in mind. This hasn't been even compile
tested but it should provide at least an idea where I am trying to go..
---
diff --git a/mm/memcontrol.c b/mm/memcontrol.c
index d5f3a62887cf..91fa05372114 100644
--- a/mm/memcontrol.c
+++ b/mm/memcontrol.c
@@ -1528,26 +1528,3
It doesn't cause a run-time bug, but these bitfields should be unsigned.
When it's signed ->dl_throttled is set to either 0 or -1, instead of
0 and 1 as expected. The sched.h file is included into tons of places
so Sparse generates a flood of warnings like this:
./include/linux/sched.h:477:54: er
On 2017-10-12 11:24:54 [-0700], Paul E. McKenney wrote:
> So I keep mainline as is, and the local_irq_save()-to-local_lock_irqsave()
> conversion happens in -rt, given that mainline doesn't have a
> local_lock_irqsave(), correct?
yes, that would be nice :)
> And just so you know, there is one pat
On Thu 12-10-17 19:22:05, Sasha Levin wrote:
> We have missed removing some code as part of removing the kmemcheck
> hooks.
>
> Unfourtenatly this got missed during my review, and the code was
> still building.
>
> Reported-by: Michal Hocko
> Signed-off-by: Sasha Levin
Yes this would be the pr
The devices running at SuperSpeedPlus speed are also LPM capable.
Apply usb3 hardware LPM attributes to those devices as well.
Signed-off-by: Lu Baolu
---
drivers/usb/core/sysfs.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/usb/core/sysfs.c b/drivers/usb/core/sy
Updated version; Steve could you route these 4 patches, they're mostly
kernel/trace/ related.
---
Subject: perf/ftrace: Fix function trace events
From: Peter Zijlstra
Date: Tue Oct 10 17:15:47 CEST 2017
The function-trace <-> perf interface is a tad messed up. Where all
the other trace <-> perf
Hi Steven,
On Thu, Oct 12, 2017 at 6:44 PM, Steven Rostedt wrote:
>
> [ Resending again, including linux...@vger.kernel.org this time ]
>
> From: Steven Rostedt (VMware)
>
> Commit 74704ac6 ("tracing, perf: Add more power related events") added
> new events, among them were trace_clock_enable, t
Hi Dave,
here's a pull request to net tree, more info in the signed tag below.
Please let me know if there are any problems.
Kalle
The following changes since commit 3e747fa18202896b5be66b88478352d5880fb8eb:
Merge ath-current from ath.git (2017-09-25 10:06:12 +0300)
are available in the git
On Thu, Oct 12, 2017 at 11:13:21PM -0700, Andrey Smirnov wrote:
> Add a driver for RAVE Supervisory Processor, an MCU implementing
> varoius bits of housekeeping functionality (watchdoging, backlight
> control, LED control, etc) on RAVE family of products by Zodiac
> Inflight Innovations.
>
> This
This looks much better, thanks. I'm not a big fan of the games with
IS_ENABLED and letting the compiler optimize code away, but you're
the maintainer..
Reviewed-by: Christoph Hellwig
As said before I'm no big fan of all the debug chatter, but the rest
looks fine, so:
Reviewed-by: Christoph Hellwig
Two trivial patches to the DT resolver code.
Stephen Boyd (2):
of/resolver: Simplify to be32_add_cpu()
of/resolver: Replace kmalloc + memcpy with kmemdup()
drivers/of/resolver.c | 8 ++--
1 file changed, 2 insertions(+), 6 deletions(-)
--
2.14.GIT
Save one line.
Signed-off-by: Stephen Boyd
---
drivers/of/resolver.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/of/resolver.c b/drivers/of/resolver.c
index 2d58253bf2f7..bd21a66f6930 100644
--- a/drivers/of/resolver.c
+++ b/drivers/of/resolver.c
@@ -84,10 +84,9
This is the same as be32_add_cpu(), so simplify the code and
remove the now unused local variable.
Signed-off-by: Stephen Boyd
---
drivers/of/resolver.c | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/drivers/of/resolver.c b/drivers/of/resolver.c
index 99309cb7d372..2d582
Prefer kcalloc over kzalloc to allocate an array.
This patch fixes checkcpatch issue.
Signed-off-by: Harsha Sharma
---
Changes in v2:
-kcalloc will take 3 arguments
drivers/gpu/drm/drm_crtc_helper.c | 4 ++--
drivers/gpu/drm/drm_fb_helper.c| 2 +-
drivers/gpu/drm/drm_plane_helper.c | 2 +-
This wasn't documented.
Signed-off-by: Stephen Boyd
---
drivers/of/fdt.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/of/fdt.c b/drivers/of/fdt.c
index ce30c9a588a4..4ea4dad13707 100644
--- a/drivers/of/fdt.c
+++ b/drivers/of/fdt.c
@@ -467,6 +467,7 @@ static int unflatten_dt_nodes
On Thu, Oct 12, 2017 at 7:05 PM, Andy Shevchenko
wrote:
> On Thu, 2017-10-12 at 15:31 +0200, Arnd Bergmann wrote:
>> On Thu, Jun 8, 2017 at 3:48 PM, Andy Shevchenko
>> wrote:
>>
>> > diff --git a/kernel/debug/kdb/kdb_main.c
>> > b/kernel/debug/kdb/kdb_main.c
>> > index c8146d53ca67..2a6f12be79d8
of_fdt_unflatten_tree() already sets the flag on the node to
OF_DETACHED, because of_fdt_unflatten_tree() calls
__unflatten_device_tree() with the detached bool set to true.
Signed-off-by: Stephen Boyd
---
drivers/of/unittest.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/of/unit
The commit a76caf55e5b35 ("thermal: Add devfreq cooling") is able
to disable OPP as a cooling device. In result, both update_devfreq()
and {min|max}_freq_show() have to consider the 'opp->available'
status of each OPP.
So, this patch adds the 'scaling_{min|max}_freq' to struct devfreq
in order to
of_fdt_unflatten_tree() already sets the flag on this node to
OF_DETACHED, because of_fdt_unflatten_tree() calls
__unflatten_device_tree() with the detached bool set to true.
Cc: Rob Herring
Cc: Frank Rowand
Signed-off-by: Stephen Boyd
---
drivers/gpu/drm/tilcdc/tilcdc_slave_compat.c | 1 -
1
This patch registers the Exynos Bus-Frequency scaling device
as a cooling device of thermal management.
Signed-off-by: Chanwoo Choi
Cc: Kukjin Kim
Cc: Krzysztof Kozlowski
Cc: linux-samsung-...@vger.kernel.org
Cc: linux-arm-ker...@lists.infradead.org
Cc: linux-kernel@vger.kernel.org
---
drivers
This patch changes the return type of devfreq_set_freq_table()
from 'void' to 'int' in order to check whether it fails or not.
And This patch just removes the 'devfreq' prefix and the description
of function. Because the helper functions are only used by the devfreq.
Signed-off-by: Chanwoo Choi
The commit a76caf55e5b35 ("thermal: Add devfreq cooling") allows
the devfreq device to use the cooling device. When the cooling down
are required, the devfreq_cooling.c disables the OPP entry with
the dev_pm_opp_disable(). In result, 'available_frequencies'[1]
sysfs node never came to show the all
The freq_table array of each devfreq device is always not NULL.
In result, it is unneeded to check whether profile->freq_table
is NULL or not.
Signed-off-by: Chanwoo Choi
---
drivers/devfreq/devfreq.c | 7 +++
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/drivers/devfreq/devf
These patches makes the devfreq to use the OPP interface and clean-up codes.
[Detaild Descripion]
The commit a76caf55e5b3 ("thermal: Add devfreq cooling") provides
the devfreq cooling device by using the OPP interface such as
dev_pm_opp_disable() and dev_pm_opp_enable(). It means that
the OPP inte
Prior to that, the devfreq device uses the governor name when adding
the itself. In order to prevent the mistake used the wrong governor name,
this patch defines the governor name as a constant and then uses them
instead of using the string directly.
Signed-off-by: Chanwoo Choi
Cc: Kukjin Kim
Cc
Prior to that, the min/max_freq of the devfreq device are always zero
before the user changes the min/max_freq through sysfs entries.
It might make the confusion for the min/max_freq.
This patch initializes the available min/max_freq by using the OPP
during adding the devfreq device.
Acked-by: My
This reverts commit 3104fa3081126c9bda35793af5f335d0ee0d5818.
The {min|max}_freq_show() show the stored value of the struct devfreq.
But, if the drivers/thermal/devfreq_cooling.c disables the specific
frequency value, {min|max}_freq_show() have to check this situation
before showing the stored val
arm64: dts: add ufs node for Hisilicon.
Signed-off-by: Li Wei
---
arch/arm64/boot/dts/hisilicon/hi3660-hikey960.dts | 5 +
arch/arm64/boot/dts/hisilicon/hi3660.dtsi | 19 +++
2 files changed, 24 insertions(+)
diff --git a/arch/arm64/boot/dts/hisilicon/hi3660-hikey96
add ufs node document for Hisilicon.
Signed-off-by: Li Wei
---
Documentation/devicetree/bindings/ufs/ufs-hisi.txt | 47 ++
1 file changed, 47 insertions(+)
create mode 100644 Documentation/devicetree/bindings/ufs/ufs-hisi.txt
diff --git a/Documentation/devicetree/bindings/u
Partitions in HiKey960 are formatted as f2fs and squashfs.
f2fs is for userdata; squashfs is for system. Both partitions are required
by Android.
Signed-off-by: Li Wei
Signed-off-by: Zhangfei Gao
Signed-off-by: Guodong Xu
---
arch/arm64/configs/defconfig | 8
1 file changed, 8 inserti
This enable configs for Hisilicon Hi UFS driver.
Signed-off-by: Li Wei
Signed-off-by: Zhangfei Gao
Signed-off-by: Guodong Xu
---
arch/arm64/configs/defconfig | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
index 34480e9af2e
add Hisilicon ufs driver code.
Signed-off-by: Li Wei
Signed-off-by: Geng Jianfeng
Signed-off-by: Zang Leigang
Signed-off-by: Yu Jianfeng
---
drivers/scsi/ufs/Kconfig| 9 +
drivers/scsi/ufs/Makefile | 1 +
drivers/scsi/ufs/ufs-hisi.c | 625
This patchset adds driver support for UFS for Hi3660 SoC. It is verified on
HiKey960 board.
Li Wei (5):
scsi: ufs: add Hisilicon ufs driver code
dt-bindings: scsi: ufs: add document for hisi-ufs
arm64: dts: add ufs dts node
arm64: defconfig: enable configs for Hisilicon ufs
arm64: defco
On Thu, Oct 12, 2017 at 05:56:35PM +0200, Peter Zijlstra wrote:
> On Thu, Oct 12, 2017 at 08:38:17AM -0700, Tejun Heo wrote:
> >
> > As long as we have the same level of protection, simpler code is of
> > course preferable. That said, I haven't followed the discussion
> > closely and don't want t
On Fri, 13 Oct 2017, Harsha Sharma wrote:
> Prefer kcalloc over kzalloc to allocate an array.
> This patch fixes checkcpatch issue.
>
> Signed-off-by: Harsha Sharma
Reviewed-by: Jani Nikula
> ---
> Changes in v2:
> -kcalloc will take 3 arguments
>
> drivers/gpu/drm/drm_crtc_helper.c | 4 ++
On Thu, 12 Oct 2017, Tom Saeger wrote:
> Signed-off-by: Tom Saeger
> ---
> .../RCU/Design/Expedited-Grace-Periods/Expedited-Grace-Periods.html | 2
> +-
Someone(tm) should convert the last three html files to rst one of these
days!
In the mean time, I guess this is good enough.
BR,
Jani.
Hi Mathieu,
On Thu, 12 Oct 2017 10:57:09 -0600
Mathieu Poirier wrote:
[...]
> >> Regardless of how we proceed (using existing CPUset list or new ones) we
> >> need to deal with DL tasks that span more than one root domain, something
> >> that will typically happen after a CPUset operation. For
On Thu 12-10-17 08:28:25, Andi Kleen wrote:
> On Thu, Oct 12, 2017 at 10:46:33AM +0200, Michal Hocko wrote:
> > [CC Christoph who seems to be the author of the code]
>
> Actually you can blame me. I did the mistake originally.
> It was found many years ago, but then it was already too late
> to ch
Hi,
On 09/26/2017 01:25 PM, Nickey Yang wrote:
This patch correct Feedback divider setting:
1、Set Feedback divider [8:5] when HIGH_PROGRAM_EN
2、Due to the use of a "by 2 pre-scaler," the range of the
feedback multiplication Feedback divider is limited to even
division numbers, and Feedback divid
Done with following coccinelle patch
@r@
expression x;
void* e;
type T;
identifier f;
@@
(
*((T *)e)
|
((T *)x)[...]
|
((T*)x)->f
|
- (T*)
e
)
Signed-off-by: Harsha Sharma
---
drivers/gpu/drm/amd/powerplay/hwmgr/cz_hwmgr.c| 6 +++---
drivers/gpu/drm/amd/powerplay/hwmgr/hwmgr.c
Hi Robin,
On 2017-10-11 15:56, Robin Murphy wrote:
xHCI requires that data buffers do not cross 64KB boundaries (and are
thus at most 64KB long as well) - whilst xhci_queue_{bulk,isoc}_tx()
already split their input buffers into individual TRBs as necessary,
it's still a good idea to advertise t
On Mon, Oct 09, 2017 at 05:31:41PM +1100, Tobin C. Harding wrote:
> Code currently prints the address of the kvm_vcpu structure in an error
> message. It is not immediately clear what value this address adds to
> the error string, we can use the vcpu ID instead.
I would say it's not immediately c
Hi,
Comment below.
On 09/26/2017 01:25 PM, Nickey Yang wrote:
This patch add dual mipi channel support:
1.add definition of dsi1 register and grf operation.
2.dsi0 and dsi1 will work in master and slave mode
when driving dual mipi panel.
@@ -1226,6 +1367,13 @@ static int rockchip_mipi_pa
Maintain the consistency with objtool subcommands, by
printing cmd_usage() of top level commands, along with
the error. When incorrect option/command is passed to
objtool. Also change the exit code to 129, like other
objtool subcommands.
After the patch:
$ ./objtool -j
Unknown option: -j
usage:
The meson i2c driver seems to be compatible with more SoCs than
initially thought. Let's use the most generic compatible he have in
DT instead of the gxbb specific one
Signed-off-by: Jerome Brunet
---
Documentation/devicetree/bindings/i2c/i2c-meson.txt | 2 +-
drivers/i2c/busses/i2c-meson.c
On Fri, Oct 06, 2017 at 12:39:20PM +0100, Alex Bennée wrote:
> If we are using guest debug to single-step the guest we need to ensure
> we exit after emulating the instruction. This only affects
> instructions completely emulated by the kernel. For userspace emulated
> instructions we need to exit
On 12/10/17 23:40, Andrew Morton wrote:
On Thu, 12 Oct 2017 16:06:11 +0200 Arnd Bergmann wrote:
kdb is the only user of the __current_kernel_time() interface, which is
not y2038 safe and should be removed at some point.
The kdb code also goes to great lengths to print the time in a
human-read
This patch uses the simpler dma_set_mask_and_coherent() instead of
doing these as separate steps
Signed-off-by: Chunfeng Yun
---
drivers/usb/host/xhci-mtk.c |7 +--
1 file changed, 1 insertion(+), 6 deletions(-)
diff --git a/drivers/usb/host/xhci-mtk.c b/drivers/usb/host/xhci-mtk.c
inde
This is useful to find out the root cause when the Super Speed doesn't
work. Such as when the T-PHY is switched to PCIe or SATA, and affects
Super Speed function, the check will fail.
Signed-off-by: Chunfeng Yun
---
drivers/usb/host/xhci-mtk.c |4
1 file changed, 4 insertions(+)
diff -
Make use of ports count from xhci but not from ippc in
xhci_mtk_sch_init()
Signed-off-by: Chunfeng Yun
---
drivers/usb/host/xhci-mtk-sch.c |3 ++-
drivers/usb/host/xhci-mtk.c |3 ---
2 files changed, 2 insertions(+), 4 deletions(-)
diff --git a/drivers/usb/host/xhci-mtk-sch.c b/driv
On Fri, Oct 13, 2017 at 04:56:33PM +0900, Byungchul Park wrote:
> On Thu, Oct 12, 2017 at 05:56:35PM +0200, Peter Zijlstra wrote:
> > On Thu, Oct 12, 2017 at 08:38:17AM -0700, Tejun Heo wrote:
> > >
> > > As long as we have the same level of protection, simpler code is of
> > > course preferable.
The wakeup debounce clocks for each ports in fact are not
needed, so remove them.
Signed-off-by: Chunfeng Yun
---
drivers/usb/host/xhci-mtk.c | 33 -
drivers/usb/host/xhci-mtk.h |2 --
2 files changed, 35 deletions(-)
diff --git a/drivers/usb/host/xhci-mtk.
There are mcu_bus and dma_bus clocks needed to be controlled by
driver on some SoCs, so add them as optional ones
Signed-off-by: Chunfeng Yun
---
drivers/usb/host/xhci-mtk.c | 79 ---
drivers/usb/host/xhci-mtk.h |2 ++
2 files changed, 62 insertions(
Remove dummy clocks for usb wakeup and add optional ones for
MCU_BUS_CK and DMA_BUS_CK.
Signed-off-by: Chunfeng Yun
Acked-by: Rob Herring
---
.../devicetree/bindings/usb/mediatek,mtk-xhci.txt | 18 --
1 file changed, 8 insertions(+), 10 deletions(-)
diff --git a/Documentatio
Due to all MediaTek SoCs with xHCI host controller use this
driver, remove limitation for specific SoCs
Signed-off-by: Chunfeng Yun
---
drivers/usb/host/Kconfig |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/usb/host/Kconfig b/drivers/usb/host/Kconfig
index fa
1 - 100 of 1004 matches
Mail list logo
