Debug message would print "Enabling" even when disabling plane.
Fix it.
Fixes: 9d75b8c0b999 (drm/sun4i: add support for Allwinner DE2 mixers)
Signed-off-by: Jernej Skrabec
---
drivers/gpu/drm/sun4i/sun8i_mixer.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git
BSP driver always sets blend mode for all channels, no matter if they
are really used or not. Do the same here.
The exact meaning of the value is not exactly known, but BSP driver
mentions "SRC OVER" and by digging through code some more info can be
found.
Signed-off-by: Jernej Skrabec
---
Current code sets alpha mode to global alpha mode and global alpha
value to 0xff which is totaly opaque. That is not needed for two
reasons:
- only one plane is active and thus it can be blended only with
background, which is black,
- it will hinder proper blending when more than one plane is
Add ti,syscon-unaligned-access property to PCIe RC nodes in order to
enable workaround for errata i870 in PCIe RC mode as well.
Signed-off-by: Vignesh R
---
arch/arm/boot/dts/dra7.dtsi | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/boot/dts/dra7.dtsi
Current DE2 driver is very basic and uses a lot of magic constants since
there is no documentation and knowledge about it was limited at the time.
With studying BSP source code, deeper knowledge was gained which allows
to improve mainline driver considerably.
At the beginning of this series,
Format mask is one bit too short. Fix it.
Fixes: 9d75b8c0b999 (drm/sun4i: add support for Allwinner DE2 mixers)
Signed-off-by: Jernej Skrabec
---
drivers/gpu/drm/sun4i/sun8i_mixer.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/sun4i/sun8i_mixer.h
On (11/30/17 19:26), Sergey Senozhatsky wrote:
> On (11/30/17 10:23), David Laight wrote:
> [..]
> > > Maybe I'm being thick, but... if we're rendering these addresses
> > > unusable by hashing them, why not just print something like
> > > "" in their place? That loses the uniqueness thing but I
On Friday 01 December 2017 11:43 AM, Vignesh R wrote:
> This series contains two fixes:
> 1. Make workaround for errata i870 applicable in Host mode as
> well(previously it was enabled only for EP mode) as per errata
> documentation: http://www.ti.com/lit/er/sprz429k/sprz429k.pdf
> 2. Fix
Errata i870 is applicable in both EP and RC mode. Therefore rename
function dra7xx_pcie_ep_unaligned_memaccess(), that implements errata
workaround, to dra7xx_pcie_unaligned_memaccess() and call it from a
common place. So, that errata workaround is applied for both modes of
operation.
On Tue, Nov 28, 2017 at 11:49:28AM +0200, yoss...@mellanox.com wrote:
> From: Yossef Efraim
>
> In case of wrap around, replay_esn->oseq_hi is not updated
> before it is tested for it's actual value, leading function
> to fail with overflow indication and packets being dropped.
>
> This patch
On Tue, Nov 28, 2017 at 11:49:29AM +0200, yoss...@mellanox.com wrote:
> From: Yossef Efraim
>
> xfrm_dev_state_add function returns success for unsupported HW SA options.
> Resulting the calling function to create SW SA without corrlating HW SA.
> Desipte IPSec device offloading option was
On Tue, Nov 28, 2017 at 11:49:30AM +0200, yoss...@mellanox.com wrote:
> From: Yossef Efraim
>
> This patch adds ESN support to IPsec device offload.
> Adding new xfrm device operation to synchronize device ESN.
>
> Signed-off-by: Yossef Efraim
> ---
> include/linux/netdevice.h | 1 +
>
This is a bit oddly formatted, since it's meant to by a set of changes
to a tree, not a normal patch set.
"x86/orc: Don't bail on stack overflow" is a fixed version of
"x86/unwinder/orc: Don't bail on stack overflow". If you'd rather
just manually patch it, change "regs->sp" to "state->sp". Bug
Signed-off-by: Andy Lutomirski
---
arch/x86/kvm/vmx.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
index a6f4f095f8f4..2abe0073b573 100644
--- a/arch/x86/kvm/vmx.c
+++ b/arch/x86/kvm/vmx.c
@@ -2291,7 +2291,7 @@ static void
This fixes a huge performance regression.
Please add to the changelog:
This patch actually seems to be a small speedup. With this patch,
SYSCALL touches an extra cache line and an extra virtual page, but
the pipeline no longer stalls waiting for SWAPGS. It seems that, at
least in a tight loop,
The TSS is a fairly juicy target for exploits, and, now that the TSS
is in the cpu_entry_area, it's no longer protected by kASLR. Make it
read-only on x86_64.
On x86_32, it can't be RO because it's written by the CPU during task
switches, and we use a task gate for double faults. I'd also be
I'm not entirely certain, but I suspect this caused the last kbuild
bot error. I wasn't able to reproduce it, but it seems plausble.
Add to the commit log:
The IST stacks are unlike the rest of cpu_entry_area: they're used
even for entries from kernel mode. This means that they should be set
Signed-off-by: Andy Lutomirski
---
arch/x86/kvm/vmx.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
index 2abe0073b573..62ee4362e1c1 100644
--- a/arch/x86/kvm/vmx.c
+++ b/arch/x86/kvm/vmx.c
@@ -2291,7 +2291,7 @@ static void
If we overflow the stack into a guard page and then try to unwind it
with ORC, it should work well: by construction, there can't be any
meaningful data in the guard page because no writes to the guard page
will have succeeded.
This patch fixes a bug that unwinding from working correctly: if the
From: Ravi Eluri
Removed lot of redundant device tree syntax from imx28-evk device tree
to make it more robust and readable.
Total four changesets and are described as follows:
Changeset 1 removes unit addresses for all peripherals of imx28 in
imx28-evk DT as they are already defined in the
From: Ravi Eluri
Unit addresses for all peripherals of imx28 are defined in
the corresponding dtsi file, use phandles instead of unit addresses
to reference peripheral nodes in dts files. This makes the DT more
robust and readable.
Signed-off-by: Ravi Eluri
Signed-off-by: Suniel Mahesh
---
From: Ravi Eluri
Cleaned up device tree.
Signed-off-by: Ravi Eluri
Signed-off-by: Suniel Mahesh
---
Note:
- This is the fourth patch of the four patch series.
- Patch was compile tested and built(ARCH=arm, imx28) on linux-next
(latest).
- No build issues reported.
- Please discard this
From: Ravi Eluri
Unit addresses for the system buses of imx28 are defined in
the corresponding dtsi file. Any peripheral node on APBH, APBX
and AHB busses can be accessed via phandle. Removed duplicate
system bus unit address entries, this makes the DT more robust
and readable.
Signed-off-by:
It was suggested that the feature would only be adopted in niches like
Android and I pointed out that it's not really relevant to Android.
It's a waste of time to try convincing me that it's useful elsewhere. I
never said or implied that it wasn't.
On Thu, 2017-11-30 at 09:50 +0100, Djalal
From: Ravi Eluri
Moved regulator, sound, leds, backlight nodes to the top of the
device tree, cleaned up for better readability.
Signed-off-by: Ravi Eluri
Signed-off-by: Suniel Mahesh
---
Note:
- This is the third patch of the four patch series.
- Patch was compile tested and built(ARCH=arm,
> > + case MSR_IA32_RTIT_ADDR0_A ... MSR_IA32_RTIT_ADDR3_B: {
> > + u32 eax, ebx, ecx, edx;
> > +
> > + cpuid_count(0x14, 1, , , , );
>
> Please cache the cpuid_count result, or do the cpuid_count after testing
> vmx_pt_supported() (which you can use
Hi Matthias,
On 2017年11月29日 04:48, Matthias Kaehlcke wrote:
El Tue, Nov 28, 2017 at 07:20:05PM +0800 Nickey Yang ha dit:
Add the ROCKCHIP DSI controller driver that uses the Synopsys DesignWare
MIPI DSI host controller bridge.
v2:
add err_pllref, remove unnecessary encoder.enable &
Hi,
I think I am triggering a blk-mq + bfq bug that I can reproduce 100%
of the time by using gdisk (1.0.1-1 in Debian stretch) to write a
partition table to a USB flash drive. After it is triggered, IO hangs
forever to that device and the machine cannot be shut down cleanly.
I have reproduced
Hi James,
First, thank you for reviewing and comment!
On Thu, Nov 30, 2017 at 07:51:03AM -0800, James Bottomley wrote:
> On Wed, 2017-11-29 at 22:11 +0800, Lee, Chun-Yi wrote:
> > The mok can not be trusted when the secure boot is disabled. Which
> > means that the kernel embedded certificate
On Thu, Nov 30, 2017 at 12:57:00PM +0100, Geert Uytterhoeven wrote:
> From: Paul Gortmaker
>
> The Kconfig currently controlling compilation of this code is:
>
> config SIMPLE_PM_BUS
> bool "Simple Power-Managed Bus Driver"
>
> ...meaning that it currently is not being built as a
The Innolux P097PFG panel is 9.7" panel with 1536X2048
resolution, it reuse P079ZCA panel driver, so improve
p079ZCA dt-binding to support P097PFG.
Signed-off-by: Lin Huang
---
.../devicetree/bindings/display/panel/innolux,p079zca.txt | 11 +--
1 file changed, 9 insertions(+), 2
Support Innolux P097PFG 9.7" 1536x2048 TFT LCD panel,
it refactor Innolux P079ZCA panel driver, let it support
multi panel, and add support P097PFG panel in this driver.
Signed-off-by: Lin Huang
---
Changes in v2:
- change regulator property name to meet the panel datasheet
On 2017年12月01日 13:54, w...@redhat.com wrote:
From: Wei Xu
tun_recvmsg() supports accepting skb by msg_control after
commit ac77cfd4258f ("tun: support receiving skb through msg_control"),
the skb if presented should be freed within the function, otherwise it
would be leaked.
Signed-off-by:
On 2017年12月01日 13:54, w...@redhat.com wrote:
From: Wei Xu
tap_recvmsg() supports accepting skb by msg_control after
commit 3b4ba04acca8 ("tap: support receiving skb from msg_control"),
the skb if presented should be freed within the function, otherwise
it would be leaked.
Signed-off-by: Wei
On 2017年12月01日 13:54, w...@redhat.com wrote:
From: Wei Xu
Matthew found a roughly 40% tcp throughput regression with commit
c67df11f(vhost_net: try batch dequing from skb array) as discussed
in the following thread:
https://www.mail-archive.com/netdev@vger.kernel.org/msg187936.html
On Thu, Nov 30, 2017 at 10:39:48AM -0500, Joshua Abraham wrote:
> diff --git a/drivers/staging/xgifb/XGI_main_26.c
> b/drivers/staging/xgifb/XGI_main_26.c
> index 6feecc55d2bc..6de66eaad96b 100644
> --- a/drivers/staging/xgifb/XGI_main_26.c
> +++ b/drivers/staging/xgifb/XGI_main_26.c
> @@ -34,16
On Thu 30-11-17 13:17:06, Andrew Morton wrote:
> On Thu, 30 Nov 2017 07:53:35 +0100 Michal Hocko wrote:
>
> > > mm... So we have a caller which hopes to be getting highmem pages but
> > > isn't. Caller then proceeds to pointlessly kmap the page and wonders
> > > why it isn't getting as much
On Wed, Nov 22, 2017 at 08:05:00AM -0800, syzbot wrote:
> syzkaller has found reproducer for the following crash on
> 0c86a6bd85ff0629cd2c5141027fc1c8bb6cde9c
> git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git/master
> compiler: gcc (GCC) 7.1.1 20170620
> .config is attached
> Raw
Sean,
IMHO, it will good if we can have all generic hdcp1.4 authentication
flow in drm helpers and all interested display drivers to use them.
This Design will make the extending of hdcp easy for other display
drivers based on DRM.
We can have the required drm_hdcp_shim type of
On 11/30, Chao Yu wrote:
> On 2017/11/28 8:23, Hyunchul Lee wrote:
> > From: Hyunchul Lee
> >
> > This implements which hint is passed down to block layer
> > for datas from the specific segment type.
> >
> > segment type hints
> > -
> >
Sean,
We might want to check the panel's HDCP capability? Agreed that majority
of HDMI/DP panel's supports it, but there is a possibility that we might
avoid authentication on non-hdcp panels.
As per HDCP specification, check for valid bksv will serve the purpose.
On Thursday 30 November
On 11/30/2017, 08:59 PM, Josh Poimboeuf wrote:
> On Thu, Nov 30, 2017 at 01:57:10PM -0600, Josh Poimboeuf wrote:
>> On Thu, Nov 30, 2017 at 09:03:24AM +0100, Jiri Slaby wrote:
>>> save_stack_trace_reliable now returns "non reliable" when there are
>>> kernel pt_regs on stack. This means an
Hi Chao,
This is really hard to review and risky a lot to apply it shortly. Do we have a
strong reason we have to do this? The original design goal was to minimize
allocation delay which is almost zero for now. Of course, I agreed that there'd
be some trade-off though, we don't have a critical
On Fri, Dec 01, 2017 at 12:53:31PM +0530, Ramalingam C wrote:
> Sean,
>
> IMHO, it will good if we can have all generic hdcp1.4 authentication flow in
> drm helpers and all interested display drivers to use them.
>
> This Design will make the extending of hdcp easy for other display drivers
>
Hi will
I find a warning by a syzkaller test;
When the mmap syscall is called to create a virtual memory,
firstly it delete a old huge page mapping area;
Before splitting the huge page, the pmd of a huge page is set up.
But The PTE_AF is zreo belonging to the current pmd of huge
On Wed, Nov 29, 2017 at 10:27:00AM +0100, Dmitry Vyukov wrote:
> On Tue, Nov 28, 2017 at 8:48 AM, wrote:
> > From: Joonsoo Kim
> >
> > Hello,
> >
> > This patchset introduces a new tool, valid access checker.
> >
> > Vchecker is a dynamic memory error detector. It provides a new debug feature
>
> Am 30.11.2017 um 16:24 schrieb Tony Lindgren :
>
> * H. Nikolaus Schaller [171128 18:35]:
>> Hi,
>>
>>> Am 28.11.2017 um 17:18 schrieb Tony Lindgren :
>>>
>>> * H. Nikolaus Schaller [171128 16:17]:
Hi Tony,
> Am 28.11.2017 um 17:04 schrieb Tony Lindgren :
>
> * H.
Changes V4:
* removed already accepted panel driver patches
* reworded commit subject to clarify
2017-11-28 16:49:00: Changes V3:
* stay compatible with old DTB files which still use "toppoly" (suggested by
Tomi Valkeinen)
* replaced MODULE_ALIAS entries by MODULE_DEVICE_TABLE (suggested by
We can remove the unnecessary "omapdss," prefix because
the omapdrm driver takes care of it when matching with
the driver table.
Signed-off-by: H. Nikolaus Schaller
---
arch/arm/boot/dts/omap3-pandora-common.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Official vendor string is now "tpo" and not "toppoly".
Requires patch "omapdrm: panel: fix compatible vendor string for td028ttec1"
so that the driver understands both.
Signed-off-by: H. Nikolaus Schaller
---
arch/arm/boot/dts/omap3-gta04.dtsi | 2 +-
1 file changed, 1 insertion(+), 1
On 12/1/2017 2:33 AM, Saeed Mahameed wrote:
On Mon, Nov 27, 2017 at 2:05 AM, Sagar Arun Kamble
wrote:
On 11/24/2017 7:01 PM, Thomas Gleixner wrote:
On Fri, 24 Nov 2017, Sagar Arun Kamble wrote:
On 11/24/2017 12:29 AM, Thomas Gleixner wrote:
On Thu, 23 Nov 2017, Sagar Arun Kamble wrote:
There is no real need for the users of timecounters to define cyclecounter
and timecounter variables separately. Since timecounter will always be
based on cyclecounter, have cyclecounter struct as member of timecounter
struct.
Suggested-by: Chris Wilson
Signed-off-by: Sagar Arun Kamble
Cc:
> Am 01.12.2017 um 02:57 schrieb Rob Herring :
>
> On Tue, Nov 28, 2017 at 04:48:54PM +0100, H. Nikolaus Schaller wrote:
>> The vendor name was "toppoly" but other panels and the vendor list
>> have defined it as "tpo". So let's fix it in driver and bindings.
>>
>> We keep the old definition in
On Fri, Dec 1, 2017 at 6:35 AM, Bjorn Andersson
wrote:
> On Thu 30 Nov 00:18 PST 2017, Philippe Ombredanne wrote:
>
>> Bjorn,
>>
>> On Thu, Nov 30, 2017 at 2:16 AM, Bjorn Andersson
>> wrote:
>> []
>> > diff --git a/drivers/soc/qcom/qmi_interface.c
>> > b/drivers/soc/qcom/qmi_interface.c
>> >
add bindings documentation for Wi2Wi W2SG00x4 GPS module.
Signed-off-by: H. Nikolaus Schaller
Acked-by: Rob Herring
---
.../devicetree/bindings/gps/wi2wi,w2sg0004.txt | 24 ++
1 file changed, 24 insertions(+)
create mode 100644
Changes V5:
* clarified to keep it in drivers/misc and not create a new group drivers/gps
* fix formatting of new entry in omap3-gta04.dtsi (suggested by Tony Lindgren)
* removed MODULE_ALIAS (suggested by Andrew F. Davis)
* some more formatting, code fixes (suggested by Andrew F. Davis)
* apply
Add driver for Wi2Wi W2SG0004/84 GPS module connected to some SoC UART.
It uses serdev API hooks to monitor and forward the UART traffic to /dev/ttyGPSn
and turn on/off the module. It also detects if the module is turned on (sends
data)
but should be off, e.g. if it was already turned on during
GTA04 has a W2SG0004/84 connected to UART2 of the OMAP3
processor. A GPIO can pulse the on/off toggle switch.
The VSIM regulator is used to power on/off the LNA of an external
active GPS antenna so that a driver can turn the LNA off if GPS is
not needed to save battery energy.
Signed-off-by: H.
Introduce vendor prefix for Wi2Wi, Inc. for W2SG00x4 GPS modules
and W2CBW003 Bluetooth/WiFi combo (CSR/Marvell).
Signed-off-by: H. Nikolaus Schaller
Acked-by: Rob Herring
---
Documentation/devicetree/bindings/vendor-prefixes.txt | 1 +
1 file changed, 1 insertion(+)
diff --git
This allows to set CONFIG_W2SG0004_DEBUG which will
make the driver report more activities and it will turn on the
GPS module during boot while the driver assumes that it
is off. This can be used to debug the correct functioning of
the hardware. Therefore we add it as an option to the driver
From: Joonsoo Kim
v2
o previous failure in linux-next turned out that it's not the problem of
this patchset. It was caused by the wrong assumption by specific
architecture.
lkml.kernel.org/r/20171114173719.ga28...@atomide.com
o add missing cache flush to the patch "ARM: CMA: avoid double
From: Joonsoo Kim
Now, all reserved pages for CMA region are belong to the ZONE_MOVABLE
and it only serves for a request with GFP_HIGHMEM && GFP_MOVABLE.
Therefore, we don't need to maintain ALLOC_CMA at all.
Reviewed-by: Aneesh Kumar K.V
Acked-by: Vlastimil Babka
Signed-off-by: Joonsoo Kim
From: Joonsoo Kim
CMA area is now managed by the separate zone, ZONE_MOVABLE,
to fix many MM related problems. In this implementation, if
CONFIG_HIGHMEM = y, then ZONE_MOVABLE is considered as HIGHMEM and
the memory of the CMA area is also considered as HIGHMEM.
That means that they are
From: Joonsoo Kim
0. History
This patchset is the follow-up of the discussion about the
"Introduce ZONE_CMA (v7)" [1]. Please reference it if more information
is needed.
1. What does this patch do?
This patch changes the management way for the memory of the CMA area
in the MM subsystem.
On Fri, Dec 01, 2017 at 12:12:14AM +0530, Jagan Teki wrote:
> Brava Keller is A64 based IoT device, which support
> - Allwinner A64 Cortex-A53
> - AXP803 PMIC
> - 1GB DDR3 RAM
> - 8GB eMMC
> - Mali-400MP2 GPU
> - AP6330 Wifi/BLE
> - Camera OV5640
> - USB Host and OTG
>
> Signed-off-by: Jagan Teki
Carlos,
On Thu, Nov 30, 2017 at 11:53 PM, James Hogan wrote:
> On Tue, Nov 28, 2017 at 04:55:35PM -0800, David Daney wrote:
>> From: Carlos Munoz
>>
>> Add a global resource manager to manage tagged pointers within
>> bootmem allocated memory. This is used by various functional
>> blocks in the
On Thu, 30 Nov 2017, Jacek Anaszewski wrote:
> On 11/30/2017 09:31 AM, Lee Jones wrote:
> > On Thu, 30 Nov 2017, Lee Jones wrote:
> >
> >> On Wed, 29 Nov 2017, Bjorn Andersson wrote:
> >>
> >>> The pointer returned by of_device_get_match_data() doesn't have the same
> >>> size as u32 on 64-bit
On Thu, 30 Nov 2017, Bjorn Andersson wrote:
> The pointer returned by of_device_get_match_data() doesn't have the same
> size as u32 on 64-bit architectures, causing a compile warning when
> compile-testing the driver on such platform.
>
> Cast the return value of of_device_get_match_data() to
save_stack_trace_reliable now returns "non reliable" when there are
kernel pt_regs on stack. This means an interrupt or exception happened.
Somewhere down the route. It is a problem for frame pointer unwinder,
because the frame might now have been set up yet when the irq happened,
so it might fail
Make sure that save_stack_trace_reliable reached userspace when saying
"this stack trace is reliable."
Place this check only after stack unwinding error check, so that the
stack is printed if something really went wrong during unwinding.
Signed-off-by: Jiri Slaby
Cc: Thomas Gleixner
Cc: Ingo
On Thu, Nov 30, 2017 at 1:47 AM, Eric Biggers wrote:
> On Tue, Nov 28, 2017 at 09:06:06PM -0800, Eric Biggers wrote:
>> On Tue, Nov 28, 2017 at 01:30:26PM -0800, Andrew Morton wrote:
>> >
>> > It looks like blkcipher_walk_done() passed a bad address to kfree().
>> >
>>
>> Indeed, it's freeing
On Thu, Nov 30, 2017 at 02:04:01AM -0500, Mikulas Patocka wrote:
>
>
> On Tue, 28 Nov 2017, Greg KH wrote:
>
> > On Mon, Nov 27, 2017 at 07:05:22PM -0500, Mikulas Patocka wrote:
> > >
> > >
> > > On Sat, 25 Nov 2017, Greg KH wrote:
> > >
> > > > On Mon, Nov 13, 2017 at 02:00:45PM -0500,
On Thu, Nov 30, 2017 at 08:47:18AM +0100, Peter Zijlstra wrote:
> On Wed, Nov 29, 2017 at 04:41:45PM +0100, Daniel Vetter wrote:
> > cross-release ftl
> >
> > From Chris:
> >
> > "Fwiw, this isn't cross-release but us reloading the module many times,
> > creating a whole host of new lockclasses.
On Thu, Nov 30, 2017 at 7:47 AM, Sergey Senozhatsky
wrote:
> Hi,
>
> On (11/30/17 10:26), Fengguang Wu wrote:
>> FYI this happens in mainline kernel v4.15-rc1 .
>> It shows up after v4.14 . Bisect is on the way.
>
> hm, printk saw no changes between 4.14 and 4.15
>
>
>> It occurs in 4 out of 4
In host mode reading from DPTXSIZn returning invalid value in
dwc2_check_param_tx_fifo_sizes function.
In total TxFIFO size calculations unnecessarily reducing by ep_info.
hw->total_fifo_size can be fully allocated for FIFO's.
Added num_dev_in_eps member in dwc2_hw_params structure to save
Commit 3840ed9548f7 ("tty: goldfish: Implement support for kernel
'earlycon' parameter") breaks an allmodconfig config on x86:
| LD vmlinux.o
| MODPOST vmlinux.o
|drivers/tty/serial/earlycon.o: In function `parse_options':
|drivers/tty/serial/earlycon.c:97: undefined reference to
On Thu, Nov 30, 2017 at 12:59 AM, Wendy Liang wrote:
> diff --git a/drivers/mailbox/zynqmp-ipi-mailbox.c
> b/drivers/mailbox/zynqmp-ipi-mailbox.c
> new file mode 100644
> index 000..229f26c
> --- /dev/null
> +++ b/drivers/mailbox/zynqmp-ipi-mailbox.c
> @@ -0,0 +1,633 @@
> +/*
Since arm64 also has __raw I/O accessors, add __aarch64__ in fb.h.
This is a supplement for commmit
981409b25e2a99409b26daa67293ca1cfd5ea0a0
Signed-off-by: Ji Zhang
---
include/linux/fb.h | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/include/linux/fb.h
Bjorn,
On Thu, Nov 30, 2017 at 2:16 AM, Bjorn Andersson
wrote:
[]
> diff --git a/drivers/soc/qcom/qmi_interface.c
> b/drivers/soc/qcom/qmi_interface.c
> new file mode 100644
> index ..4027b52b0834
> --- /dev/null
> +++ b/drivers/soc/qcom/qmi_interface.c
> @@ -0,0 +1,857 @@
> +/*
> +
On Wed, Nov 29, 2017 at 11:11 PM, Alexandre Belloni
wrote:
> On 28/11/2017 at 08:39:27 +0100, linux-kernel-...@beckhoff.com wrote:
>> From: Patrick Bruenn
[]
>> diff --git a/drivers/rtc/rtc-mxc_v2.c b/drivers/rtc/rtc-mxc_v2.c
>> new file mode 100644
>> index ..5049b521b38e
>> ---
On Thu, Nov 30, 2017 at 10:32:19AM +0800, Fengguang Wu wrote:
> Hello,
>
> FYI this happens in mainline kernel 4.15.0-rc1.
> It looks like a new regression and hard to bisect.
>
> It occurs in 1 out of 57 boots.
>
> [ 10.009610] chown (367) used greatest stack depth: 26944 bytes left
> Kernel
On Wed, Nov 29, 2017 at 03:24:22PM -0700, Shuah Khan wrote:
> usbip attach fails to find a free port when the device on the first port
> is a USB_SPEED_SUPER device and non-super speed device is being attached.
> It keeps checking the first port and returns without a match getting stuck
> in a
On Wed, Nov 29, 2017 at 11:51 PM, Kun Yi wrote:
> On Tue, Nov 14, 2017 at 8:11 AM, Oleksandr Shamray
> wrote:
[]
>> diff --git a/drivers/jtag/jtag-aspeed.c b/drivers/jtag/jtag-aspeed.c
>> new file mode 100644
>> index 000..a6e2417
>> --- /dev/null
>> +++ b/drivers/jtag/jtag-aspeed.c
>> @@
On Wed 29-11-17 19:16:39, John Hubbard wrote:
[...]
> Hi Michal,
>
> I've taken the liberty of mostly rewriting this part, in order to more
> closely
> match the existing paragraphs; to fix minor typos; and to attempt to slightly
> clarify the paragraph.
>
> +.BR MAP_FIXED_SAFE " (since Linux
Updated version based on feedback from John.
---
>From ade1eba229b558431581448e7d7838f0e1fe2c49 Mon Sep 17 00:00:00 2001
From: Michal Hocko
Date: Wed, 29 Nov 2017 15:32:08 +0100
Subject: [PATCH] mmap.2: document new MAP_FIXED_SAFE flag
4.16+ kernels offer a new MAP_FIXED_SAFE flag which allows
On Thu, Nov 30, 2017 at 2:44 AM, Song Liu wrote:
> The test compares old text based kprobe API with PERF_TYPE_KPROBE.
>
> Here is a sample output of this test:
>
> Creating 1000 kprobes with text-based API takes 6.979683 seconds
> Cleaning 1000 kprobes with text-based API takes 84.897687 seconds
>>> On 29.11.17 at 18:38, wrote:
>>> In the case of bus or slot reset, our goal is to reset connected PCIe
>>> fabric/card/endpoint.
>>> The connected card/endpoint can be multi-function device. So, same
>>> walk-through and checking
>>> is needed irrespective of type of reset being used.
>> I
/\/\/\/\/\/\On Wed, Nov 29, 2017 at 10:50 PM, Paul Lawrence
wrote:
> clang's AddressSanitizer implementation adds redzones on either side of
> alloca()ed buffers. These redzones are 32-byte aligned and at least 32
> bytes long.
>
> __asan_alloca_poison() is passed the size and address of the
On Thu, Nov 30, 2017 at 06:16:58AM +0100, Thomas Meyer wrote:
> On Thu, Nov 30, 2017 at 11:36:06AM +0800, Fengguang Wu wrote:
> > [ 40.847825]
> > ==
> > [ 40.848720] BUG: KASAN: use-after-free in cmp_ex_search+0x29/0x71:
> >
On Thu, 30 Nov 2017, Stephen Rothwell wrote:
> Hi Lee,
>
> After merging the mfd tree, today's linux-next build (x86_64 allmodconfig)
> produced this warning:
>
> drivers/leds/leds-pm8058.c: In function 'pm8058_led_probe':
> drivers/leds/leds-pm8058.c:109:17: warning: cast from pointer to
On (11/30/17 09:16), Dmitry Vyukov wrote:
[..]
> > to be honest, this backtrace hardly makes any sense to me.
> >
> > vprintk_emit()
> > reserve_standard_io_resources()
> > __flush_tlb_all()
> >vprintk_emit()
> > __down_trylock_console_sem()
> > wake_up_klogd()
> >
On Wed, 29 Nov 2017, Bjorn Andersson wrote:
> The pointer returned by of_device_get_match_data() doesn't have the same
> size as u32 on 64-bit architectures, causing issues when compile testing
> the driver on such platform. Make ledtype unsigned long instead, to
> solve this problem.
>
> Fixes:
On Thu, Nov 30, 2017 at 9:26 AM, Dmitry Vyukov wrote:
> /\/\/\/\/\/\On Wed, Nov 29, 2017 at 10:50 PM, Paul Lawrence
> wrote:
>> clang's AddressSanitizer implementation adds redzones on either side of
>> alloca()ed buffers. These redzones are 32-byte aligned and at least 32
>> bytes long.
>>
>>
>>> On 29.11.17 at 20:44, wrote:
> So, we will use the following sequence to reset the requested
> device/function.
>
> - FLR (as first option)
> - BUS/SLOT reset (as fall-back option) if FLR is not supported or any
> issue with FLR
It looks to me as if the slot reset could also fail despite
On Wed, Nov 29, 2017 at 10:50 PM, 'Paul Lawrence' via kasan-dev
wrote:
> Signed-off-by: Greg Hackmann
> Signed-off-by: Paul Lawrence
>
> lib/test_kasan.c | 22 ++
> 1 file changed, 22 insertions(+)
>
> diff --git a/lib/test_kasan.c b/lib/test_kasan.c
> index
On Wed, Nov 29, 2017 at 10:50 PM, 'Paul Lawrence' via kasan-dev
wrote:
> From: Alexander Potapenko
>
> As a code-size optimization, LLVM builds since r279383 may
> bulk-manipulate the shadow region when (un)poisoning large memory
> blocks. This requires new callbacks that simply do an
On Thu, 30 Nov 2017, Lee Jones wrote:
> On Wed, 29 Nov 2017, Bjorn Andersson wrote:
>
> > The pointer returned by of_device_get_match_data() doesn't have the same
> > size as u32 on 64-bit architectures, causing issues when compile testing
> > the driver on such platform. Make ledtype unsigned
When user tries to group imc (In-Memory Collections) event with
normal event, (sometime) kernel crashes with following log:
Faulting instruction address: 0x
[link register ] c010ce88 power_check_constraints+0x128/0x980
...
c010e238
On Wed, Nov 29, 2017 at 10:50 PM, 'Paul Lawrence' via kasan-dev
wrote:
> Use cc-option to figure out whether the compiler's sanitizer uses
> LLVM-style parameters ("-mllvm -asan-foo=bar") or GCC-style parameters
> ("--param asan-foo=bar").
>
> Signed-off-by: Greg Hackmann
> Signed-off-by: Paul
On Wed, Nov 29, 2017 at 10:50 PM, 'Paul Lawrence' via kasan-dev
wrote:
> For now we can hard-code ASAN ABI level 5, since historical clang builds
> can't build the kernel anyway. We also need to emulate gcc's
> __SANITIZE_ADDRESS__ flag, or memset() calls won't be instrumented.
>
>
1201 - 1300 of 2288 matches
Mail list logo
