On Wed, Mar 01, 2017 at 09:59:33AM +, Juri Lelli wrote:
> I'd err on the side of clearness and safety (where I assume the current
> code is safer only because it has been tested for a while :). However,
> if you can prove in a reproducible manner that the changes you are
> proposing make
On Wed, Mar 01, 2017 at 09:59:33AM +, Juri Lelli wrote:
> I'd err on the side of clearness and safety (where I assume the current
> code is safer only because it has been tested for a while :). However,
> if you can prove in a reproducible manner that the changes you are
> proposing make
On Wed, 1 Mar 2017 12:18:30 +0100
Frode Isaksen wrote:
> On 01/03/2017 11:18, Boris Brezillon wrote:
> > On Wed, 1 Mar 2017 11:09:57 +0100
> > Cyrille Pitchen wrote:
> >
> >> Le 28/02/2017 à 22:39, Richard Weinberger a écrit :
> >>> Vignesh,
On Wed, 1 Mar 2017 12:18:30 +0100
Frode Isaksen wrote:
> On 01/03/2017 11:18, Boris Brezillon wrote:
> > On Wed, 1 Mar 2017 11:09:57 +0100
> > Cyrille Pitchen wrote:
> >
> >> Le 28/02/2017 à 22:39, Richard Weinberger a écrit :
> >>> Vignesh,
> >>>
> >>> Am 27.02.2017 um 13:08 schrieb
Without this I am getting the following messages at boot on my Trimslice:
tlv320aic23-codec 2-001a: Control not supported for path LLINEIN -> [NULL]
-> Line Input
tlv320aic23-codec 2-001a: ASoC: no dapm match for LLINEIN --> NULL --> Line
Input
tlv320aic23-codec 2-001a: ASoC: Failed to
On Mon, 20 Feb 2017, Dou Liyang wrote:
> In ACPI spec, we can declare processors using both Processor and
> Device operator. And before we use the ACPI table, we should check
> the correctness for all processors in ACPI namespace.
>
> But, Currently, the check handle is just include only the
Without this I am getting the following messages at boot on my Trimslice:
tlv320aic23-codec 2-001a: Control not supported for path LLINEIN -> [NULL]
-> Line Input
tlv320aic23-codec 2-001a: ASoC: no dapm match for LLINEIN --> NULL --> Line
Input
tlv320aic23-codec 2-001a: ASoC: Failed to
On Mon, 20 Feb 2017, Dou Liyang wrote:
> In ACPI spec, we can declare processors using both Processor and
> Device operator. And before we use the ACPI table, we should check
> the correctness for all processors in ACPI namespace.
>
> But, Currently, the check handle is just include only the
Hi Archit,
Thank you for the review!
On Wed, Mar 01, 2017 at 09:38:48AM +0530, Archit Taneja wrote:
>
>
> On 02/28/2017 07:58 PM, Peter Senna Tschudin wrote:
> > The video processing pipeline on the second output on the GE B850v3:
> >
> > Host -> LVDS|--(STDP4028)--|DP ->
Hi Archit,
Thank you for the review!
On Wed, Mar 01, 2017 at 09:38:48AM +0530, Archit Taneja wrote:
>
>
> On 02/28/2017 07:58 PM, Peter Senna Tschudin wrote:
> > The video processing pipeline on the second output on the GE B850v3:
> >
> > Host -> LVDS|--(STDP4028)--|DP ->
On Wed, 1 Mar 2017 17:16:30 +0530
Vignesh R wrote:
> On Wednesday 01 March 2017 04:13 PM, Cyrille Pitchen wrote:
> > Le 01/03/2017 à 05:54, Vignesh R a écrit :
> >>
> >>
> >> On Wednesday 01 March 2017 03:11 AM, Richard Weinberger wrote:
> >>> Vignesh,
> >>>
> >>> Am
On Wed, 1 Mar 2017 17:16:30 +0530
Vignesh R wrote:
> On Wednesday 01 March 2017 04:13 PM, Cyrille Pitchen wrote:
> > Le 01/03/2017 à 05:54, Vignesh R a écrit :
> >>
> >>
> >> On Wednesday 01 March 2017 03:11 AM, Richard Weinberger wrote:
> >>> Vignesh,
> >>>
> >>> Am 27.02.2017 um 13:08
> On Mon, 22 Feb 2017, Ajay Kaher wrote:
>
>> On Mon, 20 Feb 2017, Ajay Kaher wrote:
>>
>>> Alan, as per my understanding I have shifted the lock from
>>> release_usb_class() to destroy_usb_class() in patch v3.
>>> If it is not right, please explain in detail which race condition
>>> I have
> On Mon, 22 Feb 2017, Ajay Kaher wrote:
>
>> On Mon, 20 Feb 2017, Ajay Kaher wrote:
>>
>>> Alan, as per my understanding I have shifted the lock from
>>> release_usb_class() to destroy_usb_class() in patch v3.
>>> If it is not right, please explain in detail which race condition
>>> I have
On Wed, Mar 01, 2017 at 11:43:28AM +0100, Peter Zijlstra wrote:
> On Wed, Mar 01, 2017 at 04:21:28PM +0900, Byungchul Park wrote:
> > On Tue, Feb 28, 2017 at 07:15:47PM +0100, Peter Zijlstra wrote:
> > > On Wed, Jan 18, 2017 at 10:17:32PM +0900, Byungchul Park wrote:
> > > > + /*
> > > > +
On Wed, Mar 01, 2017 at 11:43:28AM +0100, Peter Zijlstra wrote:
> On Wed, Mar 01, 2017 at 04:21:28PM +0900, Byungchul Park wrote:
> > On Tue, Feb 28, 2017 at 07:15:47PM +0100, Peter Zijlstra wrote:
> > > On Wed, Jan 18, 2017 at 10:17:32PM +0900, Byungchul Park wrote:
> > > > + /*
> > > > +
On Tue, Feb 21, 2017 at 2:15 AM, Reshetova, Elena
wrote:
>> On Mon, Feb 20, 2017 at 5:19 AM, Elena Reshetova
>> wrote:
>> > refcount_t type and corresponding API should be
>> > used instead of atomic_t when the variable is used as
>> > a
On Tue, Feb 21, 2017 at 2:15 AM, Reshetova, Elena
wrote:
>> On Mon, Feb 20, 2017 at 5:19 AM, Elena Reshetova
>> wrote:
>> > refcount_t type and corresponding API should be
>> > used instead of atomic_t when the variable is used as
>> > a reference counter. This allows to avoid accidental
>> >
Hi Peter,
On 01/03/17 13:00, Peter Huewe wrote:
>
>
> Am 1. März 2017 12:51:16 MEZ schrieb Enric Balletbo i Serra
> :
>> From: Sonny Rao
>>
>> The suspend/resume behavior of the TPM can be controlled
>> by setting "powered-while-suspended"
Hi Peter,
On 01/03/17 13:00, Peter Huewe wrote:
>
>
> Am 1. März 2017 12:51:16 MEZ schrieb Enric Balletbo i Serra
> :
>> From: Sonny Rao
>>
>> The suspend/resume behavior of the TPM can be controlled
>> by setting "powered-while-suspended" in the DTS.
>>
>> Signed-off-by: Sonny Rao
>>
On Tue, Feb 28, 2017 at 11:35:04PM +0100, Stephan Müller wrote:
> Am Dienstag, 28. Februar 2017, 17:45:53 CET schrieb Corentin Labbe:
>
> Hi Corentin,
>
> > On Tue, Feb 28, 2017 at 05:08:35PM +0100, Stephan Müller wrote:
> > > Am Dienstag, 28. Februar 2017, 16:59:53 CET schrieb Corentin Labbe:
>
On Tue, Feb 28, 2017 at 11:35:04PM +0100, Stephan Müller wrote:
> Am Dienstag, 28. Februar 2017, 17:45:53 CET schrieb Corentin Labbe:
>
> Hi Corentin,
>
> > On Tue, Feb 28, 2017 at 05:08:35PM +0100, Stephan Müller wrote:
> > > Am Dienstag, 28. Februar 2017, 16:59:53 CET schrieb Corentin Labbe:
>
On 02/01/2017 06:46 PM, Sudeep Holla wrote:
> Commit c7cef0a84912 ("console: Add extensible console matching") added
> match() method to struct console which allows the console to perform
> console command line matching instead of (or in addition to) default
> console matching (ie., by fixed
On 02/01/2017 06:46 PM, Sudeep Holla wrote:
> Commit c7cef0a84912 ("console: Add extensible console matching") added
> match() method to struct console which allows the console to perform
> console command line matching instead of (or in addition to) default
> console matching (ie., by fixed
ISP CSI1 module needs all the bits correctly set to work.
Signed-off-by: Ivaylo Dimitrov
Signed-off-by: Pavel Machek
index ca09523..e6584a2 100644
--- a/drivers/media/platform/omap3isp/ispccp2.c
+++ b/drivers/media/platform/omap3isp/ispccp2.c
@@
ISP CSI1 module needs all the bits correctly set to work.
Signed-off-by: Ivaylo Dimitrov
Signed-off-by: Pavel Machek
index ca09523..e6584a2 100644
--- a/drivers/media/platform/omap3isp/ispccp2.c
+++ b/drivers/media/platform/omap3isp/ispccp2.c
@@ -213,14 +236,17 @@ static int
Am 1. März 2017 12:51:16 MEZ schrieb Enric Balletbo i Serra
:
>From: Sonny Rao
>
>The suspend/resume behavior of the TPM can be controlled
>by setting "powered-while-suspended" in the DTS.
>
>Signed-off-by: Sonny Rao
Am 1. März 2017 12:51:16 MEZ schrieb Enric Balletbo i Serra
:
>From: Sonny Rao
>
>The suspend/resume behavior of the TPM can be controlled
>by setting "powered-while-suspended" in the DTS.
>
>Signed-off-by: Sonny Rao
>Signed-off-by: Enric Balletbo i Serra
>---
From: Doug Anderson
This is a sucky change to bump up the time we'll wait for the EC. Why
is it sucky? If 200ms for a transfer is a common thing it will have a
massively bad impact on keyboard responsiveness.
It still seems like a good idea to do this, though, because
Commit-ID: 25b68a8f0ab13a98de02650208ec927796659898
Gitweb: http://git.kernel.org/tip/25b68a8f0ab13a98de02650208ec927796659898
Author: Stephen Smalley
AuthorDate: Fri, 17 Feb 2017 10:13:59 -0500
Committer: Thomas Gleixner
CommitDate: Wed, 1 Mar
From: Doug Anderson
This is a sucky change to bump up the time we'll wait for the EC. Why
is it sucky? If 200ms for a transfer is a common thing it will have a
massively bad impact on keyboard responsiveness.
It still seems like a good idea to do this, though, because we have a
gas gauge that
Commit-ID: 25b68a8f0ab13a98de02650208ec927796659898
Gitweb: http://git.kernel.org/tip/25b68a8f0ab13a98de02650208ec927796659898
Author: Stephen Smalley
AuthorDate: Fri, 17 Feb 2017 10:13:59 -0500
Committer: Thomas Gleixner
CommitDate: Wed, 1 Mar 2017 12:53:44 +0100
timerfd: Only check
Dear RT folks!
I'm pleased to announce the v4.9.13-rt11 patch set.
Changes since v4.9.13-rt10:
- The lockdep fix in last release failed to compile for UP and
MODULE=n configs. Fixed by Dan Murphy.
Known issues
- CPU hotplug got a little better but can deadlock.
The delta patch
Dear RT folks!
I'm pleased to announce the v4.9.13-rt11 patch set.
Changes since v4.9.13-rt10:
- The lockdep fix in last release failed to compile for UP and
MODULE=n configs. Fixed by Dan Murphy.
Known issues
- CPU hotplug got a little better but can deadlock.
The delta patch
Add u2phy config information in the data of match table for
rk3328.
Signed-off-by: Meng Dongyang
---
drivers/phy/phy-rockchip-inno-usb2.c | 21 +
1 file changed, 21 insertions(+)
diff --git a/drivers/phy/phy-rockchip-inno-usb2.c
Add u2phy config information in the data of match table for
rk3328.
Signed-off-by: Meng Dongyang
---
drivers/phy/phy-rockchip-inno-usb2.c | 21 +
1 file changed, 21 insertions(+)
diff --git a/drivers/phy/phy-rockchip-inno-usb2.c
b/drivers/phy/phy-rockchip-inno-usb2.c
index
Due to the u2phy registers are separated from general grf, we need to
add u2phy grf node and place u2phy node in it. And on some platform,
the 480m clock may need to assign clock parent in dts in stead of
clock driver. So this patch add u2phy grf node and property of
assigned-clocks and
Due to the u2phy registers are separated from general grf, we need to
add u2phy grf node and place u2phy node in it. And on some platform,
the 480m clock may need to assign clock parent in dts in stead of
clock driver. So this patch add u2phy grf node and property of
assigned-clocks and
Resend this series to involve maintainer of phy documentation
The config information of RK3328 about address and port property
is different from before platform. So add config information in the
data of match table and documentation of the device tree bindings
of u2phy.
Meng Dongyang (2):
From: Sonny Rao
The suspend/resume behavior of the TPM can be controlled
by setting "powered-while-suspended" in the DTS.
Signed-off-by: Sonny Rao
Signed-off-by: Enric Balletbo i Serra
---
Resend this series to involve maintainer of phy documentation
The config information of RK3328 about address and port property
is different from before platform. So add config information in the
data of match table and documentation of the device tree bindings
of u2phy.
Meng Dongyang (2):
From: Sonny Rao
The suspend/resume behavior of the TPM can be controlled
by setting "powered-while-suspended" in the DTS.
Signed-off-by: Sonny Rao
Signed-off-by: Enric Balletbo i Serra
---
Documentation/devicetree/bindings/tpm/tpm.txt | 25 +
Use colorspace provided by the user as we are only doing scaling and
color encoding conversion, we won't be able to transform the colorspace
itself and the colorspace won't mater in that operation.
Also always use output colorspace on the capture side.
If the user does not provide a colorspace
Use colorspace provided by the user as we are only doing scaling and
color encoding conversion, we won't be able to transform the colorspace
itself and the colorspace won't mater in that operation.
Also always use output colorspace on the capture side.
If the user does not provide a colorspace
Hello,
This patchset fixes a few issues on the colorspace logic for the exynos-gsc
and s5p-mfc drivers.
We now handle the colorspace in those drivers, and make sure to respect user
setting if
possible.
We also now set the 'v4l2_pix_format:field' if userspace passed ANY, and
replicate users
Hello,
This patchset fixes a few issues on the colorspace logic for the exynos-gsc
and s5p-mfc drivers.
We now handle the colorspace in those drivers, and make sure to respect user
setting if
possible.
We also now set the 'v4l2_pix_format:field' if userspace passed ANY, and
replicate users
It is required by the standard that the field order is set by the
driver, default to NONE in case any is provided, but we can basically
accept any value provided by the userspace as we will anyway not
be able to do any deinterlacing.
In this patch we also make sure to pass the interlacing mode
The same MALI-450 MP3 GPU is present in the GXBB and GXL SoCs.
The node is simply added in the meson-gxbb.dtsi file.
For GXL, since a lot is shared with the GXM that has a MALI-T820 IP, this
patch adds a new meson-gxl-mali.dtsi and is included in the SoC specific
dtsi files.
Signed-off-by: Neil
It is required by the standard that the field order is set by the
driver, default to NONE in case any is provided, but we can basically
accept any value provided by the userspace as we will anyway not
be able to do any deinterlacing.
In this patch we also make sure to pass the interlacing mode
The same MALI-450 MP3 GPU is present in the GXBB and GXL SoCs.
The node is simply added in the meson-gxbb.dtsi file.
For GXL, since a lot is shared with the GXM that has a MALI-T820 IP, this
patch adds a new meson-gxl-mali.dtsi and is included in the SoC specific
dtsi files.
Signed-off-by: Neil
On Wednesday 01 March 2017 03:39 PM, Cyrille Pitchen wrote:
> Le 28/02/2017 à 22:39, Richard Weinberger a écrit :
>> Vignesh,
>>
>> Am 27.02.2017 um 13:08 schrieb Vignesh R:
>>> Filesystems like UBIFS may pass vmalloc'd buffers to SPI NOR layer which
>>> will end up in SPI layer. SPI core does
On Wednesday 01 March 2017 03:39 PM, Cyrille Pitchen wrote:
> Le 28/02/2017 à 22:39, Richard Weinberger a écrit :
>> Vignesh,
>>
>> Am 27.02.2017 um 13:08 schrieb Vignesh R:
>>> Filesystems like UBIFS may pass vmalloc'd buffers to SPI NOR layer which
>>> will end up in SPI layer. SPI core does
On Tue, Feb 28, 2017 at 05:19:51PM -0600, Tom Lendacky wrote:
> Device drivers don't supply set_dma_mask() since that is part of the
> dma_map_ops structure. The fm10k_pf.c file function is unrelated to this
> (it's part of an internal driver structure). The dma_map_ops structure
> is setup by the
On Tue, Feb 28, 2017 at 05:19:51PM -0600, Tom Lendacky wrote:
> Device drivers don't supply set_dma_mask() since that is part of the
> dma_map_ops structure. The fm10k_pf.c file function is unrelated to this
> (it's part of an internal driver structure). The dma_map_ops structure
> is setup by the
Since the merge of the Mali dt bindings at [1], add support for Mali clocks
and DT node.
The Mali is clocked by two identical clock paths behind a glitch free mux
to safely change frequency while running.
So these clocks must be added to the meson-gxbb clock controller.
Changes since v1 at [2] :
Since the merge of the Mali dt bindings at [1], add support for Mali clocks
and DT node.
The Mali is clocked by two identical clock paths behind a glitch free mux
to safely change frequency while running.
So these clocks must be added to the meson-gxbb clock controller.
Changes since v1 at [2] :
Commit 21caf2fc1931 ("mm: teach mm by current context info to not do I/O
during memory allocation") added the memalloc_noio_(save|restore) functions
to enable people to modify the MM behavior by disbaling I/O during memory
allocation. This was further extended in Fixes: 934f3072c17c ("mm: clear
Commit 21caf2fc1931 ("mm: teach mm by current context info to not do I/O
during memory allocation") added the memalloc_noio_(save|restore) functions
to enable people to modify the MM behavior by disbaling I/O during memory
allocation. This was further extended in Fixes: 934f3072c17c ("mm: clear
On Wed, Mar 1, 2017 at 11:42 AM, Loh, Tien Hock wrote:
> On Rab, 2017-03-01 at 10:01 +0100, Arnd Bergmann wrote:
>> On Wed, Mar 1, 2017 at 8:23 AM, Loh, Tien Hock > Another option would be to fold the timestamp into the revision
>> attribute,
>>
On 01/03/2017 11:43, Cyrille Pitchen wrote:
> Le 01/03/2017 à 05:54, Vignesh R a écrit :
>>
>> On Wednesday 01 March 2017 03:11 AM, Richard Weinberger wrote:
>>> Vignesh,
>>>
>>> Am 27.02.2017 um 13:08 schrieb Vignesh R:
Many SPI controller drivers use DMA to read/write from m25p80
On Wed, Mar 1, 2017 at 11:42 AM, Loh, Tien Hock wrote:
> On Rab, 2017-03-01 at 10:01 +0100, Arnd Bergmann wrote:
>> On Wed, Mar 1, 2017 at 8:23 AM, Loh, Tien Hock > Another option would be to fold the timestamp into the revision
>> attribute,
>> but whether that is a reasonable place for it would
On 01/03/2017 11:43, Cyrille Pitchen wrote:
> Le 01/03/2017 à 05:54, Vignesh R a écrit :
>>
>> On Wednesday 01 March 2017 03:11 AM, Richard Weinberger wrote:
>>> Vignesh,
>>>
>>> Am 27.02.2017 um 13:08 schrieb Vignesh R:
Many SPI controller drivers use DMA to read/write from m25p80
On Tue, 28 Feb 2017 12:23:01 -0600
Eric Blake wrote:
> On 02/28/2017 11:03 AM, Greg Kurz wrote:
> > According to the POSIX.1-2008 manual page [1], the fchmodat() function has
> > a flag argument which may be passed the following value:
> >
> > AT_SYMLINK_NOFOLLOW
> > If
On Tue, 28 Feb 2017 12:23:01 -0600
Eric Blake wrote:
> On 02/28/2017 11:03 AM, Greg Kurz wrote:
> > According to the POSIX.1-2008 manual page [1], the fchmodat() function has
> > a flag argument which may be passed the following value:
> >
> > AT_SYMLINK_NOFOLLOW
> > If path names a
On Monday, February 20, 2017 12:51 PM +0100, Karol Wachowski wrote:
> Reuse events from KnightsLanding for KnightsMill
>
> Signed-off-by: Karol Wachowski
> ---
> tools/perf/pmu-events/arch/x86/mapfile.csv | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git
The triplet present in "opp-microvolt" property should be in the order
, while all the examples have it in the order
.
Fix it.
Luckily all of the users of "opp-microvolt" property have applied brain
instead of copying the examples from documentation and none of the
actual dts files have it
On Monday, February 20, 2017 12:51 PM +0100, Karol Wachowski wrote:
> Reuse events from KnightsLanding for KnightsMill
>
> Signed-off-by: Karol Wachowski
> ---
> tools/perf/pmu-events/arch/x86/mapfile.csv | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git
The triplet present in "opp-microvolt" property should be in the order
, while all the examples have it in the order
.
Fix it.
Luckily all of the users of "opp-microvolt" property have applied brain
instead of copying the examples from documentation and none of the
actual dts files have it
From: Benson Leung
This is the driver for the USB Type C cable detection mechanism
built into the ChromeOS Embedded Controller on systems that
have USB Type-C ports.
At present, this allows for the presence of display out, but in
future, it may also be used to notify host
From: Benson Leung
This is the driver for the USB Type C cable detection mechanism
built into the ChromeOS Embedded Controller on systems that
have USB Type-C ports.
At present, this allows for the presence of display out, but in
future, it may also be used to notify host and device type cables
On 01/03/2017 11:18, Boris Brezillon wrote:
> On Wed, 1 Mar 2017 11:09:57 +0100
> Cyrille Pitchen wrote:
>
>> Le 28/02/2017 à 22:39, Richard Weinberger a écrit :
>>> Vignesh,
>>>
>>> Am 27.02.2017 um 13:08 schrieb Vignesh R:
Filesystems like UBIFS may pass
On 01/03/2017 11:18, Boris Brezillon wrote:
> On Wed, 1 Mar 2017 11:09:57 +0100
> Cyrille Pitchen wrote:
>
>> Le 28/02/2017 à 22:39, Richard Weinberger a écrit :
>>> Vignesh,
>>>
>>> Am 27.02.2017 um 13:08 schrieb Vignesh R:
Filesystems like UBIFS may pass vmalloc'd buffers to SPI NOR
Dear all,
Now that the drm/rockchip landed it's time to review the extcon cros-ec driver.
The
cdn-dp driver uses this extcon driver to get cable status and the presence of
display
out.
This driver is based on the one available in chromeos-4.4 kernel but removing
all the USB switch role stuff,
Dear all,
Now that the drm/rockchip landed it's time to review the extcon cros-ec driver.
The
cdn-dp driver uses this extcon driver to get cable status and the presence of
display
out.
This driver is based on the one available in chromeos-4.4 kernel but removing
all the USB switch role stuff,
From: Benson Leung
This patch add documentation for binding of USB Type C cable detection
mechanism is using EXTCON subsystem. The device can detect the presence
of display out but it may also detect other external accessories when
external accessories is attached or
On Mon, 20 Feb 2017, Dou Liyang wrote:
Please make your subject line short and a precise summary phrase, not an
overlong sentence.
> After we revert the the mapping of "cpuid <-> nodeid" fixed at the
> booting time. and do it at the hot-plug time. we should also do the
> verification of
From: Benson Leung
This patch add documentation for binding of USB Type C cable detection
mechanism is using EXTCON subsystem. The device can detect the presence
of display out but it may also detect other external accessories when
external accessories is attached or detached.
Signed-off-by:
On Mon, 20 Feb 2017, Dou Liyang wrote:
Please make your subject line short and a precise summary phrase, not an
overlong sentence.
> After we revert the the mapping of "cpuid <-> nodeid" fixed at the
> booting time. and do it at the hot-plug time. we should also do the
> verification of
Hi Dmitry,
On 02/28/2017 11:46 PM, Dmitry Torokhov wrote:
> Also rename 'priv' variables to eeti.
>
> Signed-off-by: Dmitry Torokhov
> ---
>
> Hi,
>
> This is all is not tested as I do not have the hardware, so if anyone
> has raumfeld device that would be awesome.
Hi Dmitry,
On 02/28/2017 11:46 PM, Dmitry Torokhov wrote:
> Also rename 'priv' variables to eeti.
>
> Signed-off-by: Dmitry Torokhov
> ---
>
> Hi,
>
> This is all is not tested as I do not have the hardware, so if anyone
> has raumfeld device that would be awesome.
I have no access to such
refcount_t type and corresponding API should be
used instead of atomic_t when the variable is used as
a reference counter. This allows to avoid accidental
refcounter overflows that might lead to use-after-free
situations.
Signed-off-by: Elena Reshetova
Signed-off-by:
On 02/28/2017 09:05 PM, Linus Torvalds wrote:
On Tue, Feb 28, 2017 at 7:24 PM, Peter Hutterer
wrote:
I suspect you're just triggering a bug that wasn't triggered by the ps/2
emulation. you can run linput-debug-events --verbose and have a look at the
various state
refcount_t type and corresponding API should be
used instead of atomic_t when the variable is used as
a reference counter. This allows to avoid accidental
refcounter overflows that might lead to use-after-free
situations.
Signed-off-by: Elena Reshetova
Signed-off-by: Hans Liljestrand
On 02/28/2017 09:05 PM, Linus Torvalds wrote:
On Tue, Feb 28, 2017 at 7:24 PM, Peter Hutterer
wrote:
I suspect you're just triggering a bug that wasn't triggered by the ps/2
emulation. you can run linput-debug-events --verbose and have a look at the
various state debugging information, that
refcount_t type and corresponding API should be
used instead of atomic_t when the variable is used as
a reference counter. This allows to avoid accidental
refcounter overflows that might lead to use-after-free
situations.
Signed-off-by: Elena Reshetova
Signed-off-by:
refcount_t type and corresponding API should be
used instead of atomic_t when the variable is used as
a reference counter. This allows to avoid accidental
refcounter overflows that might lead to use-after-free
situations.
Signed-off-by: Elena Reshetova
Signed-off-by: Hans Liljestrand
From: Andi Kleen
Add generic infrastructure to perf stat to output ratios for "MetricExpr"
entries in the event lists. Many events are more useful as ratios
than in raw form, typically some count in relation to total ticks.
Transfer the MetricExpr information from the
From: Andi Kleen
Add generic infrastructure to perf stat to output ratios for "MetricExpr"
entries in the event lists. Many events are more useful as ratios
than in raw form, typically some count in relation to total ticks.
Transfer the MetricExpr information from the alias to the evsel.
We
On Tue, Feb 28, 2017 at 05:28:48PM -0600, Tom Lendacky wrote:
> That's a good idea, I'll expand on that. I probably won't be that
> direct in my comment though :)
You either haven't dealt with firmware long enough or you're much better
person than me. :-)))
--
Regards/Gruss,
Boris.
Good
On Tue, Feb 28, 2017 at 05:28:48PM -0600, Tom Lendacky wrote:
> That's a good idea, I'll expand on that. I probably won't be that
> direct in my comment though :)
You either haven't dealt with firmware long enough or you're much better
person than me. :-)))
--
Regards/Gruss,
Boris.
Good
On Wed, Mar 01, 2017 at 01:40:33PM +0900, Byungchul Park wrote:
> Right. I decided to force MAX_XHLOCKS_NR to be power of 2 and everything
> became easy. Thank you very much.
Something like:
BUILD_BUG_ON(MAX_XHLOCKS_NR & (MAX_XHLOCK_NR - 1));
Should enforce I think.
On Wed, Mar 01, 2017 at 01:40:33PM +0900, Byungchul Park wrote:
> Right. I decided to force MAX_XHLOCKS_NR to be power of 2 and everything
> became easy. Thank you very much.
Something like:
BUILD_BUG_ON(MAX_XHLOCKS_NR & (MAX_XHLOCK_NR - 1));
Should enforce I think.
On Tue, Feb 28, 2017 at 10:31:15AM -0800, Randy Dunlap wrote:
> From: Randy Dunlap
>
> Fix kconfig dependencies when COMPILE_TEST is enabled so that
> interdependent module dependencies are configured as needed.
>
> Fixes build when WM831X_WATCHDOG=m and COMPILE_TEST=y.
>
On Tue, Feb 28, 2017 at 10:31:15AM -0800, Randy Dunlap wrote:
> From: Randy Dunlap
>
> Fix kconfig dependencies when COMPILE_TEST is enabled so that
> interdependent module dependencies are configured as needed.
>
> Fixes build when WM831X_WATCHDOG=m and COMPILE_TEST=y.
> No other WM831X
From: "david.wu"
If the pwm was not enabled at uboot loader, pwm could not work for clock
always disabled at pwm driver. The pwm clock is enabled at beginning of
pwm_apply(), but disabled at end of pwm_apply().
If the pwm was enabled at uboot loader, pwm clock is always
From: "david.wu"
If the pwm was not enabled at uboot loader, pwm could not work for clock
always disabled at pwm driver. The pwm clock is enabled at beginning of
pwm_apply(), but disabled at end of pwm_apply().
If the pwm was enabled at uboot loader, pwm clock is always enabled unless
closed by
Hi Boris,
在 2017/3/1 18:19, Boris Brezillon 写道:
On Wed, 1 Mar 2017 18:16:02 +0800
David Wu wrote:
From: "david.wu"
If the pwm was not enabled at uboot loader, pwm could not work for clock
always disabled at pwm driver. The pwm clock is
Hi Boris,
在 2017/3/1 18:19, Boris Brezillon 写道:
On Wed, 1 Mar 2017 18:16:02 +0800
David Wu wrote:
From: "david.wu"
If the pwm was not enabled at uboot loader, pwm could not work for clock
always disabled at pwm driver. The pwm clock is enabled at beginning of
pwm_apply(), but disabled at
On 1.03.2017 12:31, Michal Hocko wrote:
> On Wed 01-03-17 11:22:51, Vlastimil Babka wrote:
>> On 03/01/2017 08:48 AM, Nikolay Borisov wrote:
>>> Commit 21caf2fc1931 ("mm: teach mm by current context info to not do I/O
>>> during memory allocation") added the memalloc_noio_(save|restore)
Le 01/03/2017 à 05:54, Vignesh R a écrit :
>
>
> On Wednesday 01 March 2017 03:11 AM, Richard Weinberger wrote:
>> Vignesh,
>>
>> Am 27.02.2017 um 13:08 schrieb Vignesh R:
>>> Many SPI controller drivers use DMA to read/write from m25p80 compatible
>>> flashes. Therefore enable bounce buffers
1301 - 1400 of 1758 matches
Mail list logo