On 08/12/18 9:24 PM, Nishanth Menon wrote:
> On 14:12-20181207, Faiz Abbas wrote:
>
>> +
>> +&sdhci0 {
>> +status = "okay";
>> +pinctrl-names = "default";
>> +pinctrl-0 = <&main_mmc0_pins_default>;
>> +bus-width = <8>;
>> +non-removable;
>> +ti,driver-strength-ohm = <50>;
>
On Mon, 10 Dec 2018 at 11:11, Paul Burton wrote:
>
> Hi Firoz,
>
> On Mon, Dec 10, 2018 at 11:05:38AM +0530, Firoz Khan wrote:
> > Please review this patch series and queue it for linux-next.
>
> It's been ~4 days, 2 of which were a weekend. I'll get to it, but
> pinging so often won't help.
Sure
On several arches, virt_to_phys() is in io.h
Build fails without it:
CC lib/test_debug_virtual.o
lib/test_debug_virtual.c: In function 'test_debug_virtual_init':
lib/test_debug_virtual.c:26:7: error: implicit declaration of function
'virt_to_phys' [-Werror=implicit-function-declaration]
On Mon, Dec 10, 2018 at 08:59:02AM +0100, jacopo mondi wrote:
> Hi Sakari,
>thanks for digging this out
>
> On Mon, Dec 10, 2018 at 01:39:17AM +0200, sakari.ai...@iki.fi wrote:
> > Hi Jacopo,
> >
> > On Fri, Dec 29, 2017 at 01:22:26PM +0100, Jacopo Mondi wrote:
> > > The following commits:
> >
Add level active IRQ support to regmap-irq irqchip. Change breaks
existing regmap-irq type setting. Convert the existing drivers which
use regmap-irq with trigger type setting (gpio-max77620) to work
with this new approach. So we do not magically support level-active
IRQs on gpio-max77620 - but add
On Wed, Dec 05, 2018 at 11:41:01AM -0800, Stephen Boyd wrote:
> No worries, I fixed it up and merged to clk-next.
Hi Stephen,
In order to send imx7ulp device tree for 4.21, I pulled branch
clk-imx7ulp into IMX tree to resolve the dependency on clock ID
definitions. So please keep the branch stab
Hi Segher,
On Sun, Dec 2, 2018 at 3:48 PM Segher Boessenkool
wrote:
>
> On Fri, Nov 30, 2018 at 10:06:02AM +0100, Boris Petkov wrote:
> > On November 29, 2018 1:25:02 PM GMT+01:00, Segher Boessenkool
> > wrote:
> > >This will only be fixed from GCC 9 on, if the compiler adopts it. The
> > >ke
Hi Yogesh,
On Mon, 10 Dec 2018 04:13:28 +
Yogesh Narayan Gaur wrote:
> Hi Mark,
>
> Patch has been resend [1], this patch is depends on the series of patch[2]
> and this series has been applied by Boris already.
You're still not asking the right person. Every patches touching
things in dr
G'day Anson,
On 10/12/2018 3:17 PM, Anson Huang wrote:
The magnetometer's power supply could be controlled by regulator
on some platforms, such as i.MX6Q-SABRESD board, the mag3110's
power supply is controlled by a GPIO fixed regulator, need to make
sure the regulator is enabled before any commu
On Sun 2018-12-09 23:47:17, Josh Triplett wrote:
> On Sun, Dec 09, 2018 at 09:06:00PM +0100, Pavel Machek wrote:
> ...
> > > > > The default permissions for the device are 600.
> > > >
> > > > Good. This does not belong to non-root.
> > >
> > > There are entirely legitimate use cases for using th
On Sat, 2018-12-08 at 12:24 +0100, Pavel Machek wrote:
> On Sat 2018-12-08 12:13:46, Pavel Machek wrote:
> > Hi!
> >
> > > > > > There's one similar for nouveau in Bugzilla, but it seems like a
> > > > > > genuine
> > > > > > memory corruption (1 bit flipped):
> > > > > >
> > > > > > https://bug
Hi Lee,
On Mon, Dec 10, 2018 at 06:27:18AM +, Lee Jones wrote:
> On Sat, 08 Dec 2018, Quentin Schulz wrote:
>
> > Hi Lee,
> >
> > On Fri, Dec 07, 2018 at 07:22:37PM +, Lee Jones wrote:
> > > On Fri, 07 Dec 2018, Vasily Khoruzhick wrote:
> > >
> > > > On Fri, Dec 7, 2018 at 8:40 AM Lee J
On Sun, 2018-12-09 at 12:18 +0100, Pavel Machek wrote:
> Hi!
>
> Another day, another problem... but this one is different from the
> previous hang, as machine survives.
Please, file a bug. It says so even in the splat...
Regards, Joonas
>
> Chromium was running with youtube video playing.
>
On Mon 10-12-18 16:49:54, Chanho Min wrote:
> prepare_bprm_creds is not used outside exec.c, so there's no reason for it
> to have external linkage.
>
> Signed-off-by: Chanho Min
Acked-by: Michal Hocko
> ---
> fs/exec.c | 2 +-
> include/linux/binfmts.h | 1 -
> 2 files changed,
Zebu boards were added in v4.9 and then renamed to "haps" in v4.10.
Thus backporting
commit 64234961c145 (ARC: configs: Remove CONFIG_INITRAMFS_SOURCE from
defconfigs)
we missed "zebu" defconfigs in v4.9.
Note this is only applicable to "linux-4.9.y"!
Spotted by KerneCI, see [1].
[1]
https://
On Fri 07-12-18 15:05:28, David Rientjes wrote:
> On Fri, 7 Dec 2018, Michal Hocko wrote:
[...]
> > > Secondly, prior to 89c83fb539f9, alloc_pages_vma() implemented a somewhat
> > > different policy for hugepage allocations, which were allocated through
> > > alloc_hugepage_vma(). For hugepage a
On Sun, 9 Dec 2018 at 09:17, Pavel Machek wrote:
>
> On Fri 2018-12-07 13:32:54, Krzysztof Kozlowski wrote:
> > Allow initialization of pattern used in pattern trigger from Device Tree
> > property.
> >
> > This is especially useful for embedded systems where the pattern trigger
> > would be used
On Sun, 9 Dec 2018 at 19:55, Jacek Anaszewski
wrote:
>
> On 12/8/18 7:44 PM, Jacek Anaszewski wrote:
> > Hi Krzysztof,
> >
> > Thank you for the patch set.
> >
> > Applied 1/4 and 2/4.
> >
> > I'll hold on merging 3/4 until we sort out the issues
> > I have with this one. Please refer to my commen
Hi Boris,
Sorry for confusion.
My intention was just to point to the correct patch number only. Earlier you
have asked Mark to pick the patch [1] but that patch number was not correct.
[1] https://lkml.org/lkml/2018/12/5/758
--
Regards
Yogesh Gaur
> -Original Message-
> From: Boris Br
On Mon, Dec 10, 2018 at 04:49:54PM +0900, Chanho Min wrote:
> prepare_bprm_creds is not used outside exec.c, so there's no reason for it
> to have external linkage.
Applied...
From: Tudor Ambarus
The clock-frequency property is not mandatory for the i2c buses. If it's
not present in the device tree, the buses __usually__ assume it's 100kHZ
(see altera, at91, axxia, etc.). Broadcom uses a 375kHZ default
clock-frequency, so the default clock frequency varies from bus to
From: Tudor Ambarus
The clock-frequency property is not mandatory for the i2c buses. If it's
not present in the device tree, the buses __usually__ assume it's 100kHZ
(see altera, at91, axxia, etc.). Broadcom uses a 375kHZ default
clock-frequency, so the default clock frequency varies from bus to
From: Tudor Ambarus
The clock-frequency property is not mandatory for the i2c buses. If it's
not present in the device tree, the buses __usually__ assume it's 100kHZ
(see altera, at91, axxia, etc.). Broadcom uses a 375kHZ default
clock-frequency, so the default clock frequency varies from bus to
On Wed, 3 Oct 2018 22:26:03 +0530
Vignesh R wrote:
> Cadence OSPI controller IP supports Octal IO (x8 IO lines),
> It also has an integrated PHY. IP register layout is very
> similar to existing QSPI IP except for additional bits to support Octal
> and Octal DDR mode. Therefore, extend current dr
On Sun, 9 Dec 2018 14:17:18 +0530
Vignesh R wrote:
> Hi Boris,
>
> On 03/10/18 10:26 PM, Vignesh R wrote:
> > This series adds support for octal mode of mt35x flash. Also, adds
> > support for OSPI version of Cadence QSPI controller.
> >
> > Based on top of patches adding basic support for mt35
Hi Dmitry,
On Mon, Dec 10, 2018 at 5:30 AM Dmitry V. Levin wrote:
> syscall_get_* functions are required to be implemented on all
> architectures in order to extend the generic ptrace API with
> PTRACE_GET_SYSCALL_INFO request.
>
> This introduces asm/syscall.h on m68k implementing all 5 syscall_
Drivers might want to remove some sysfs files, which needs the same
locks and ends up angering lockdep. Relevant snippet of the stack
trace:
kernfs_remove_by_name_ns+0x3b/0x80
bus_remove_driver+0x92/0xa0
acpi_video_unregister+0x24/0x40
i915_driver_unload+0x42/0x130 [i915]
i915_pci_remove
On Mon, 10 Dec 2018 08:39:20 +
Yogesh Narayan Gaur wrote:
> Hi Boris,
>
> Sorry for confusion.
>
> My intention was just to point to the correct patch number only. Earlier you
> have asked Mark to pick the patch [1] but that patch number was not correct.
Look at the context in [1] (we hav
The structure cs_etm_queue uses 'prev_packet' to point to previous
packet, this can be used to combine with new coming packet to generate
samples.
In function cs_etm__flush() it swaps packets only when the flag
'etm->synth_opts.last_branch' is true, this means that it will not
swap packets if with
perf cs-etm module converts decoder elements to packets and then we have
more context crossing packets to generate synthenize samples, finally
perf tool can faciliate samples for statistics and report the results.
This patch series is to address several issues found related with
packets handling a
If decoder outputs EO_TRACE element, it means the end of the trace
buffer; this is a discontinuity and in this case the end of trace data
needs to be saved.
This patch generates CS_ETM_DISCONTINUITY packet for EO_TRACE element
hereby flushing the end of trace data in cs-etm.c.
Cc: Mathieu Poirier
On Wed, Dec 05, 2018 at 07:59:17PM +0800, Brian Starkey wrote:
> Hi James,
>
> On Wed, Dec 05, 2018 at 10:20:13AM +, james qian wang (Arm Technology
> China) wrote:
> > Signed-off-by: James (Qian) Wang
> > ---
> > MAINTAINERS | 8
> > 1 file changed, 8 insertions(+)
> >
> > diff -
At the end of trace buffer handling, function cs_etm__flush() is invoked
to flush any remaining branch stack entries. As a side effect, it also
generates branch sample, because the 'etmq->packet' doesn't contains any
new coming packet but point to one stale packet after packets swapping,
so it wro
TRACE_ON element is used at the beginning of trace, it also can be
appeared in the middle of trace data to indicate discontinuity; for
example, it's possible to see multiple TRACE_ON elements in the trace
stream if the trace is being limited by address range filtering.
Furthermore, except TRACE_ON
The exception packet appears as one element with 'elem_type' ==
OCSD_GEN_TRC_ELEM_EXCEPTION or OCSD_GEN_TRC_ELEM_EXCEPTION_RET,
which present for exception entry and exit respectively. The decoder
set packet fields 'packet->exc' and 'packet->exc_ret' to indicate the
exception packets; but exceptio
CoreSight tracer driver might insert barrier packet between different
buffers, thus the decoder can spot the boundaries based on the barrier
packet; the decoder is possible to hit a barrier packet and emit a
NO_SYNC element, then the decoder will find a periodic synchronisation
point inside that ne
Dear Sir,
I need your support to relocate and invest in your country. I ask your
assistance because I don’t have knowledge about
business and the rules that guide your country for safe investment.
Will you promise to be sincere with me?
Please contact me for more information details!
With bes
On Sun, Dec 09, 2018 at 04:57:43PM -0800, Nadav Amit wrote:
> > On Dec 8, 2018, at 2:52 AM, Peter Zijlstra wrote:
> > My patch proposed here:
> >
> > https://marc.info/?l=linux-mm&m=154409548410209
> >
> > would actually fix that one I think, preempt_count() uses
> > raw_cpu_read_4() which wil
On Mon, Dec 03, 2018 at 01:37:37PM +, Suzuki K Poulose wrote:
> Hi Anshuman,
>
> On 03/12/2018 12:11, Anshuman Khandual wrote:
> >
> >
> >On 10/31/2018 11:27 PM, Punit Agrawal wrote:
> >>The code for operations such as marking the pfn as dirty, and
> >>dcache/icache maintenance during stage 2
On Thu, Dec 6, 2018 at 8:08 PM Marcelo Ricardo Leitner
wrote:
>
> On Thu, Dec 06, 2018 at 11:36:08AM +0100, Alexander Potapenko wrote:
> > On Wed, Dec 5, 2018 at 8:31 PM syzbot
> > wrote:
> > >
> > > Hello,
> > >
> > > syzbot found the following crash on:
> > >
> > > HEAD commit:fffec98ae2a6
On Monday, December 10, 2018 6:14:54 AM CET Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the driver-core tree got a conflict in:
>
> drivers/base/platform.c
> u
> between commit:
>
> 2d51ac9086fd ("driver core: platform: Remove duplicated
> device_remove_properties() ca
On Mon, Dec 03, 2018 at 07:02:23PM +0530, Anshuman Khandual wrote:
>
>
> On 10/31/2018 11:27 PM, Punit Agrawal wrote:
> > Stage 2 fault handler marks a page as executable if it is handling an
> > execution fault or if it was a permission fault in which case the
> > executable bit needs to be pres
Hi Felipe,
>-Original Message-
>From: Felipe Balbi [mailto:ba...@kernel.org]
>Sent: Monday, December 10, 2018 12:24 PM
>To: Anurag Kumar Vulisha ; Greg Kroah-Hartman
>; Shuah Khan ; Alan Stern
>; Johan Hovold ; Jaejoong Kim
>; Benjamin Herrenschmidt ;
>Roger Quadros ; Manu Gautam ;
>martin
On Wed, Dec 05, 2018 at 10:47:10AM +, Suzuki K Poulose wrote:
>
>
> On 03/12/2018 13:32, Anshuman Khandual wrote:
> >
> >
> >On 10/31/2018 11:27 PM, Punit Agrawal wrote:
> >>Stage 2 fault handler marks a page as executable if it is handling an
> >>execution fault or if it was a permission fau
Hi,
On Fri, 2018-12-07 at 22:22 +0100, Jernej Škrabec wrote:
> Hi!
>
> Dne sreda, 05. december 2018 ob 10:24:44 CET je Paul Kocialkowski napisal(a):
> > This adds the Video Engine node for the A64. Since it can map the whole
> > DRAM range, there is no particular need for a reserved memory node
>
On 06 December 2018 03:02, Kyle Tso wrote:
> Current matching rules ensure that the voltage range of selected Source
> Capability is entirely within the range defined in one of the Sink
> Capabilities. This
> is reasonable but not practical because Sink may not support wide range of
> voltage whe
On Mon, Dec 03, 2018 at 07:20:08PM +0530, Anshuman Khandual wrote:
>
>
> On 10/31/2018 11:27 PM, Punit Agrawal wrote:
> > Introduce helpers to abstract architectural handling of the conversion
> > of pfn to page table entries and marking a PMD page table entry as a
> > block entry.
>
> Why is th
Hi,
Anurag Kumar Vulisha writes:
> Thanks for reviewing this patch. Lets consider an example where a
> request has num_sgs > 0 and each sg is mapped to a TRB and the last
> TRB has the IOC bit set. Once the controller is done with the
> transfer, it generates XferInProgress for
On Mon, Dec 10, 2018 at 09:58:53AM +0100, Rafael J. Wysocki wrote:
> On Monday, December 10, 2018 6:14:54 AM CET Stephen Rothwell wrote:
> > Hi all,
> >
> > Today's linux-next merge of the driver-core tree got a conflict in:
> >
> > drivers/base/platform.c
> > u
> > between commit:
> >
> > 2
On Thu, Dec 6, 2018 at 3:55 PM Greg KH wrote:
>
> On Wed, Dec 05, 2018 at 12:41:35PM -0800, Evan Green wrote:
> > On Tue, Nov 27, 2018 at 10:03 AM Georgi Djakov
> > wrote:
> > >
> > > Modern SoCs have multiple processors and various dedicated cores (video,
> > > gpu,
> > > graphics, modem). The
In case we are using simplefb or another conflicting framebuffer, make
the call to drm_fb_helper_remove_conflicting_framebuffers()
Signed-off-by: Maxime Jourdan
---
drivers/gpu/drm/meson/meson_drv.c | 19 +++
1 file changed, 19 insertions(+)
diff --git a/drivers/gpu/drm/meson/me
Hi Vignesh,
On 06/12/18 12:32, Vignesh R wrote:
> Hi Roger,
>
> On 05/12/18 8:49 PM, Roger Quadros wrote:
>> The AM654 SoC from TI contains a DWC3 controller. Add
>> support for it.
>>
>> Signed-off-by: Roger Quadros
>> ---
>> Documentation/devicetree/bindings/usb/keystone-usb.txt | 4 ++--
>>
On Fri, Dec 07, 2018 at 05:57:42PM +, John Garry wrote:
> A friendly reminder. Can you please let me know your position on this patch?
I am waiting for a Reviewed-by or at least Acked-by from Robin on it
before I put it in my tree.
Regards,
Joerg
On Wed, Dec 05, 2018 at 05:57:51PM +, Suzuki K Poulose wrote:
>
>
> On 01/11/2018 13:38, Christoffer Dall wrote:
> >On Wed, Oct 31, 2018 at 05:57:42PM +, Punit Agrawal wrote:
> >>In preparation for creating PUD hugepages at stage 2, add support for
> >>detecting execute permissions on PUD
On Sat, Dec 08, 2018 at 07:05:12PM +0100, Tore Anderson wrote:
> The HP lt4132 is a rebranded Huawei ME906s-158 LTE modem.
>
> The interface with protocol 0x16 is "CDC ECM & NCM" according to the *.inf
> files included with the Windows driver. Attaching the option driver to it
> doesn't result in
SimpleFB allows transferring a framebuffer from the firmware/bootloader
to the kernel, while making sure the related clocks and power supplies
stay enabled.
Add nodes for CVBS and HDMI Simple Framebuffers.
Signed-off-by: Maxime Jourdan
---
arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi | 25 ++
Similar to simple-framebuffer-sunxi, we support different display pipelines
that the firmware is free to choose from.
This documents the "amlogic,simple-framebuffer" compatible and the
"amlogic,pipeline" extension.
Signed-off-by: Maxime Jourdan
---
.../display/simple-framebuffer-meson.txt
On Mon, Dec 10, 2018 at 10:05 AM Maxime Jourdan wrote:
>
> In case we are using simplefb or another conflicting framebuffer, make
> the call to drm_fb_helper_remove_conflicting_framebuffers()
>
> Signed-off-by: Maxime Jourdan
> ---
> drivers/gpu/drm/meson/meson_drv.c | 19 +++
>
On Tue, Dec 04, 2018 at 11:23:11PM +0200, Andy Shevchenko wrote:
> There are users which print time and date represented by content of
> struct rtc_time in human readable format.
>
> Instead of open coding that each time introduce %ptR[dt][r] specifier.
>
Petr, is it now looks good to you? Can y
Hi all,
Changes since 20181207:
The thermal tree lost its build failure.
The rdma tree still had its build failure so I used the version from
next-20181203.
The net-next tree gained conflicts against the net tree.
The drm-msm tree gained a conflict against the drm tree.
The rcu tree gained a
On Fri, Dec 07, 2018 at 02:50:42AM +, YueHaibing wrote:
> Fixes gcc '-Wunused-but-set-variable' warning:
>
> drivers/usb/serial/mos7840.c: In function 'mos7840_send_cmd_write_baud_rate':
> drivers/usb/serial/mos7840.c:1584:16: warning:
> variable 'number' set but not used [-Wunused-but-set-va
On Fri, Dec 07, 2018 at 03:11:01PM -0500, Paul Gortmaker wrote:
> The Kconfig currently controlling compilation of this code is:
>
> drivers/mfd/Kconfig:config MFD_WM831X_I2C
> drivers/mfd/Kconfig:bool "Wolfson Microelectronics WM831x/2x PMICs with
> I2C"
>
> ...meaning that it currently is
On Fri, Dec 07, 2018 at 03:11:00PM -0500, Paul Gortmaker wrote:
> The Kconfig currently controlling compilation of this code is:
>
> drivers/mfd/Kconfig:config MFD_WM831X_SPI
> drivers/mfd/Kconfig:bool "Wolfson Microelectronics WM831x/2x PMICs with
> SPI"
>
> ...meaning that it currently is
On Fri, Dec 07, 2018 at 03:11:02PM -0500, Paul Gortmaker wrote:
> The Kconfig currently controlling compilation of this code is:
>
> drivers/mfd/Kconfig:config MFD_WM831X
> drivers/mfd/Kconfig:bool
>
> ...meaning that it currently is not being built as a module by anyone.
>
> Lets remove the
Hi all,
Commit
24985cf0be81 ("ext4: use IS_ENCRYPTED() to check encryption status")
is missing a Signed-off-by from its committer.
--
Cheers,
Stephen Rothwell
pgpknmQmHSDjF.pgp
Description: OpenPGP digital signature
From: Colin Ian King
There is a spelling mistake in a pr_err message, fix this.
Signed-off-by: Colin Ian King
---
drivers/gpu/drm/selftests/test-drm_damage_helper.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/selftests/test-drm_damage_helper.c
b/drivers
On Fri, Dec 07, 2018 at 03:11:03PM -0500, Paul Gortmaker wrote:
> The Kconfig currently controlling compilation of this code is:
>
> drivers/mfd/Kconfig:config MFD_WM8350_I2C
> drivers/mfd/Kconfig:bool "Wolfson Microelectronics WM8350 with I2C"
>
> ...meaning that it currently is not being bu
In case we are using simplefb or another conflicting framebuffer, make
the call to drm_fb_helper_remove_conflicting_framebuffers()
Signed-off-by: Maxime Jourdan
---
drivers/gpu/drm/meson/meson_drv.c | 20
1 file changed, 20 insertions(+)
diff --git a/drivers/gpu/drm/meson/m
On Fri, Dec 07, 2018 at 03:11:05PM -0500, Paul Gortmaker wrote:
> The Kconfig currently controlling compilation of this code is:
>
> drivers/mfd/Kconfig:config MFD_WM8400
> drivers/mfd/Kconfig:bool "Wolfson Microelectronics WM8400"
>
> ...meaning that it currently is not being built as a modu
From: Colin Ian King
There is a spelling mistake in a msg string, fix this.
Signed-off-by: Colin Ian King
---
drivers/net/ethernet/hisilicon/hns3/hns3pf/hclge_err.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/ethernet/hisilicon/hns3/hns3pf/hclge_err.c
b/dri
Hi,
I rebased on top of Jacek's patches and, as I could not find them on git kernel
tree, I included them here. Also with small fixup.
Changes since v1:
1. Rebase on Jacek's patches.
2. Add patch 3/5 for fixup of Jacek's solution.
3. Drop first two patches from the series (applied).
4. Patch 5/5:
Allow initialization of pattern used in pattern trigger from Device Tree
property.
This is especially useful for embedded systems where the pattern trigger
would be used to indicate the process of boot status in a nice,
user-friendly blinking way. This initialization pattern will be used
till use
Trigger driver can be initialized after the LED class device driver. In
such case led_trigger_set_default() won't be called and flag
LED_INIT_DEFAULT_TRIGGER should be set from led_trigger_register().
Signed-off-by: Krzysztof Kozlowski
---
drivers/leds/led-triggers.c | 4 +++-
1 file changed, 3
From: Jacek Anaszewski
It is of no avail to continue iterating through registered
triggers in the led_trigger_set_default() after the trigger to set
has been found. Add "break" statement to fix this omission.
Signed-off-by: Jacek Anaszewski
Acked-by: Pavel Machek
Signed-off-by: Krzysztof Kozlo
From: Jacek Anaszewski
Add the flag LED_INIT_DEFAULT_TRIGGER for indicating that trigger
being set is a default trigger for the LED class device, and
thus it should be initialized with settings provided in the fwnode.
Set the flag in the led_trigger_set_default(). It is expected to be
cleared in
Document new linux,trigger-pattern property for initialization of LED
pattern trigger.
Signed-off-by: Krzysztof Kozlowski
---
Documentation/devicetree/bindings/leds/common.txt | 7 +++
1 file changed, 7 insertions(+)
diff --git a/Documentation/devicetree/bindings/leds/common.txt
b/Document
Ooops, $SUBJECT should be:
"drm/selftest: fix spelling mistake "dimention" -> "dimension"
On 10/12/2018 09:26, Colin King wrote:
> From: Colin Ian King
>
> There is a spelling mistake in a pr_err message, fix this.
>
> Signed-off-by: Colin Ian King
> ---
> drivers/gpu/drm/selftests/test-drm_
Hi all,
Commit
42632988767e ("phy: ti: fix semicolon.cocci warnings")
is missing a Signed-off-by from its committer.
--
Cheers,
Stephen Rothwell
pgpOdxl0PRnV7.pgp
Description: OpenPGP digital signature
Hi Sergey,
+ lkml.
On Fri, Dec 07, 2018 at 06:50:04PM +0900, Sergey Senozhatsky wrote:
> On (12/06/18 11:58), Feng Tang wrote:
> > > Same here, I tried on several platforms and hardly get the sysrq magic key
> > > working, though it works while system is running.
> > >
> > > And it make me wonde
On 28/11/2018 13:50, Manivannan Sadhasivam wrote:
> Add interrupt driver for RDA Micro RDA8810PL SoC.
>
> Signed-off-by: Andreas Färber
> Signed-off-by: Manivannan Sadhasivam
Reviewed-by: Marc Zyngier
Given the dependency on the platform Kconfig entry, how do you want this
to be merged?
Than
Hi:
This series tries to fix various issues of vhost:
- Patch 1 adds a missing write barrier between used idx updating and
logging.
- Patch 2-3 brings back the protection of device IOTLB through vq
mutex, this fixes possible use after free in device IOTLB entries.
- Patch 4 fixes the diry pag
Vhost dirty page logging API is designed to sync through GPA. But we
try to log GIOVA when device IOTLB is enabled. This is wrong and may
lead to missing data after migration.
To solve this issue, when logging with device IOTLB enabled, we will:
1) reuse the device IOTLB translation result of GIO
When we try to do rx busy polling in tx path in commit 441abde4cd84
("net: vhost: add rx busy polling in tx path"), we lock rx vq mutex
after tx vq mutex is held. This may lead deadlock so we try to lock vq
one by one in commit 78139c94dc8c ("net: vhost: lock the vqs one by
one"). With this commit,
We miss a write barrier that guarantees used idx is updated and seen
before log. This will let userspace sync and copy used ring before
used idx is update. Fix this by adding a barrier before log_write().
Fixes: 8dd014adfea6f ("vhost-net: mergeable buffers support")
Signed-off-by: Jason Wang
---
Hi Frieder,
Thanks for the review. Please find my comments inline.
> -Original Message-
> From: Schrempf Frieder [mailto:frieder.schre...@kontron.de]
> Sent: Thursday, December 6, 2018 2:53 PM
> To: Yogesh Narayan Gaur ; linux-
> m...@lists.infradead.org; boris.brezil...@bootlin.com; mare
This reverts commit 78139c94dc8c96a478e67dab3bee84dc6eccb5fd. We don't
protect device IOTLB with vq mutex, which will lead e.g use after free
for device IOTLB entries. And since we've exact the same lock order
with the help of previous patch, it's safe to revert it without having
deadlock.
Fixes:
On Tue, Dec 04, 2018 at 08:46:41AM +, Dexuan Cui wrote:
> > From: Greg KH
> > Sent: Monday, December 3, 2018 11:43 PM
> > On Tue, Dec 04, 2018 at 03:35:13PM +1100, Stephen Rothwell wrote:
> > > Hi all,
> > >
> > > Today's linux-next merge of the char-misc tree got a conflict in:
> > >
> > >
On Sat 08-12-18 00:49:44, Al Viro wrote:
> On Fri, Dec 07, 2018 at 08:49:16PM +0100, Alexander Lochmann wrote:
>
> > > _What_ SUID bit? We are talking about a write to block device, for fsck
> > > sake...
> > >
> > That's the way I understood Jan's explanation:
> > "
> > Thinking more about thi
On Sun, Dec 09, 2018 at 11:44:19AM -0500, Theodore Y. Ts'o wrote:
> On Sun, Dec 09, 2018 at 12:30:39PM +0100, Greg KH wrote:
> > > P.P.P.S. If I were king, I'd be asking for a huge number of kunit
> > > tests for block-mq to be developed, and then running them under a
> > > Thread Sanitizer.
> >
On Mon, Dec 10, 2018 at 11:33:49AM +0300, Alexey Brodkin wrote:
> Zebu boards were added in v4.9 and then renamed to "haps" in v4.10.
>
> Thus backporting
> commit 64234961c145 (ARC: configs: Remove CONFIG_INITRAMFS_SOURCE from
> defconfigs)
> we missed "zebu" defconfigs in v4.9.
>
> Note this i
HGz -> GHz
Signed-off-by: Michael Straube
---
drivers/staging/rtl8723bs/TODO | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/rtl8723bs/TODO b/drivers/staging/rtl8723bs/TODO
index 80dbdaca3a8f..58e02f944b6d 100644
--- a/drivers/staging/rtl8723bs/TODO
+++ b/driv
The function rtw_port_switch_chk() returns always false.
Remove the function and related dead code.
Signed-off-by: Michael Straube
---
drivers/staging/rtl8723bs/core/rtw_mlme_ext.c | 34 ---
.../staging/rtl8723bs/include/rtw_mlme_ext.h | 1 -
2 files changed, 35 deletions(-)
d
On Mon, Dec 10, 2018 at 1:49 AM Linus Torvalds
wrote:
> Most of it looks pretty small and normal. Would I have preferred for
> there to be less churn? Yes. But it's certainly smaller than rc5 was,
> so we're moving in the right direction, and we have at least one more
> rc to go.
>
> I say "at le
Am Sonntag, 9. Dezember 2018, 23:14:05 CET schrieb Heiko Stuebner:
Forgot the
From: Rob Herring
here, but if you're ok with how it looks I can apply it to my tree.
Heiko
> Convert Rockchip SoC bindings to DT schema format using json-schema.
>
> Cc: Mark Rutland
> Cc: Heiko Stuebner
> Cc: d
Hi Anson,
On Mon, Dec 10, 2018 at 5:17 AM Anson Huang wrote:
> + data->vdd_reg = devm_regulator_get_optional(&client->dev, "vdd");
> + if (!IS_ERR(data->vdd_reg)) {
> + ret = regulator_enable(data->vdd_reg);
> + if (ret) {
> + dev_err
Hi Marc,
On Mon, Dec 10, 2018 at 09:39:13AM +, Marc Zyngier wrote:
> On 28/11/2018 13:50, Manivannan Sadhasivam wrote:
> > Add interrupt driver for RDA Micro RDA8810PL SoC.
> >
> > Signed-off-by: Andreas Färber
> > Signed-off-by: Manivannan Sadhasivam
>
> Reviewed-by: Marc Zyngier
>
> Gi
On 2018/12/10 15:11, Sergey Senozhatsky wrote:
> On (12/10/18 05:58), Liu, Chuansheng wrote:
>>> On (12/10/18 05:40), Liu, Chuansheng wrote:
@@ -130,6 +130,13 @@ static void check_hung_task(struct task_struct *t,
>>> unsigned long timeout)
init_utsname()->version);
On Mon, Dec 10, 2018 at 12:32:21AM +0200, Igor Stoppa wrote:
>
>
> On 06/12/2018 11:44, Peter Zijlstra wrote:
> > On Wed, Dec 05, 2018 at 03:13:56PM -0800, Andy Lutomirski wrote:
> >
> > > > + if (op == WR_MEMCPY)
> > > > + memcpy((void *)wr_poking_addr, (void *)src, len);
>
On 08/12/2018 00:08, Lyude Paul wrote:
> uh
> didn't we fix this weeks ago? with "drm/nouveau: tegra: Call
> nouveau_drm_device_init()"
Yes here's the fix from Thierry:
https://patchwork.freedesktop.org/patch/263587/
and I can confirm that it does fix the Oops when applied on top
syzbot reported a kernel-infoleak, which is caused by an uninitialized
field(sin6_flowinfo) of addr->a.v6 in sctp_inet6addr_event().
The call trace is as below:
BUG: KMSAN: kernel-infoleak in _copy_to_user+0x19a/0x230 lib/usercopy.c:33
CPU: 1 PID: 8164 Comm: syz-executor2 Not tainted 4.20.0-rc
1 - 100 of 1204 matches
Mail list logo
