Bus clear feature of Tegra I2C controller helps to recover from
bus hang when I2C master loses the bus arbitration due to the
slave device holding SDA LOW continuously for some unknown reasons.
Per I2C specification, the device that held the bus LOW should
release it within 9 clock pulses.
From: Tom Zanussi
The hist trigger action code currently implements two essentially
hard-coded pairs of 'actions' - onmax(), which tracks a variable and
saves some event fields when a max is hit, and onmatch(), which is
hard-coded to generate a synthetic event.
These hardcoded pairs (track
From: Tom Zanussi
Add Documentation for the hist:handlerXXX($var).snapshot() action.
Signed-off-by: Tom Zanussi
---
Documentation/trace/histogram.rst | 110 ++
1 file changed, 110 insertions(+)
diff --git a/Documentation/trace/histogram.rst
From: Tom Zanussi
Currently, the onmatch action data binds the onmatch action to data
related to synthetic event generation. Since we want to allow the
onmatch handler to potentially invoke a different action, and because
we expect other handlers to generate synthetic events, we need to
From: Tom Zanussi
Currently, tracing snapshots are context-free - they capture the ring
buffer contents at the time the tracing_snapshot() function was
invoked, and nothing else. Additionally, they're always taken
unconditionally - the calling code can decide whether or not to take a
snapshot,
From: Tom Zanussi
Add support for hist:handlerXXX($var).snapshot(), which will take a
snapshot of the current trace buffer whenever handlerXXX is hit.
As a first user, this also adds snapshot() action support for the
onmax() handler i.e. hist:onmax($var).snapshot().
Also, the hist trigger key
From: Tom Zanussi
Apparently this directory was missed in the license cleanup process -
add the missing identifiers to the trigger/inter-event test cases.
Signed-off-by: Tom Zanussi
---
.../ftrace/test.d/trigger/inter-event/trigger-extended-error-support.tc | 1 +
From: Tom Zanussi
Add a 'trace(synthetic_event_name, params)' alternative to
synthetic_event_name(params).
Currently, the syntax used for generating synthetic events is to
invoke synthetic_event_name(params) i.e. use the synthetic event name
as a function call.
Users requested a new form that
From: Tom Zanussi
Add support for a hist:onchange($var) handler, similar to the onmax()
handler but triggering whenever there's any change in $var, not just a
max.
Signed-off-by: Tom Zanussi
---
kernel/trace/trace.c | 3 ++-
kernel/trace/trace_events_hist.c | 58
From: Tom Zanussi
Add a test case verifying that basic action combinations fail as
expected.
Signed-off-by: Tom Zanussi
---
.../inter-event/trigger-action-hist-xfail.tc | 30 ++
1 file changed, 30 insertions(+)
create mode 100644
From: Tom Zanussi
Add a test case verifying the basic functionality of the
hist:onchange($var) handler.
Signed-off-by: Tom Zanussi
Acked-by: Masami Hiramatsu
---
.../inter-event/trigger-onchange-action-hist.tc| 28 ++
1 file changed, 28 insertions(+)
create mode
Hi Palmer,
On Tue, 05 Feb 2019 10:47:43 -0800 (PST) Palmer Dabbelt
wrote:
>
> Thanks. Is there a script I should be running to pre-check these?
I run the attached script on each set of new commits that turn up.
--
Cheers,
Stephen Rothwell
check_fixes
Description: application/shellscript
From: Tom Zanussi
The action/handler code refactoring didn't change the action/handler
syntax, but did generalize it - the Documentation should reflect that.
Signed-off-by: Tom Zanussi
---
Documentation/trace/histogram.rst | 56 ++-
1 file changed, 43
From: Tom Zanussi
Add Documentation for the hist:onchange($var) handler.
Signed-off-by: Tom Zanussi
---
Documentation/trace/histogram.rst | 98 +++
1 file changed, 98 insertions(+)
diff --git a/Documentation/trace/histogram.rst
From: Tom Zanussi
Hi,
This is v14 of the hist trigger snapshot and onchange additions
patchset.
This version fixes compile errors flagged by the kbuild test robot
when CONFIG_TRACER_SNAPSHOT isn't defined, along with a couple minor
cleanups. Everything else remains the same.
Thanks,
Tom
From: Tom Zanussi
Add a test case verifying the basic functionality of the
hist:snapshot() action.
Signed-off-by: Tom Zanussi
Acked-by: Masami Hiramatsu
---
.../inter-event/trigger-snapshot-action-hist.tc| 43 ++
1 file changed, 43 insertions(+)
create mode 100644
From: Tom Zanussi
Add a test case for the alternative trace(
---
.../inter-event/trigger-trace-action-hist.tc | 42 ++
1 file changed, 42 insertions(+)
create mode 100644
tools/testing/selftests/ftrace/test.d/trigger/inter-event/trigger-trace-action-hist.tc
diff
From: Tom Zanussi
The action refactor code allowed actions and handlers to be separated,
but the existing onmax handler and save action code is still not
flexible enough to handle arbitrary coupling. This change generalizes
them and in the process makes additional handlers and actions easier
to
--
Lieber Freund (Assalamu Alaikum),
Ich bin auf Ihre E-Mail-Adresse vor einer privaten Suche gestoßen,
obwohl Sie sie benötigen
Ihre Hilfe. Mein Name ist Aisha Al-Gaddafi, eine alleinerziehende
Mutter und Witwe
mit drei Kindern. Ich bin die einzige leibliche Tochter des späten
Libyen
On 2/5/2019 3:32 PM, Stephen Boyd wrote:
Quoting Jeffrey Hugo (2019-02-05 14:15:16)
On 2/5/2019 3:01 PM, Stephen Boyd wrote:
Quoting Jeffrey Hugo (2019-01-30 08:35:44)
The XO clock generally feeds into other clock controllers as the parent
for a lot of clock generators.
Fixes: 6131dc81211c
On 2/5/2019 3:16 PM, Stephen Boyd wrote:
Quoting Jeffrey Hugo (2019-02-05 14:08:43)
On 2/5/2019 3:02 PM, Stephen Boyd wrote:
Quoting Jeffrey Hugo (2019-01-30 08:35:59)
Document the multimedia clock controller found on MSM8998
Signed-off-by: Jeffrey Hugo
---
On Thu, Jan 31, 2019 at 06:09:51PM +0100, Håkon Bugge wrote:
> Using CX-3 virtual functions, either from a bare-metal machine or
> pass-through from a VM, MAD packets are proxied through the PF driver.
>
> Since the VMs have separate name spaces for MAD Transaction Ids
> (TIDs), the PF driver has
In function pistachio_usb_phy_power_on(), local variable "val"
could be uninitialized if function regmap_read() returns -EINVAL.
However, it will be used directly in the if statement, which
is potentially unsafe.
Signed-off-by: Yizhuo
---
drivers/phy/phy-pistachio-usb.c | 8 ++--
1 file
Quoting Jeffrey Hugo (2019-02-05 14:15:16)
> On 2/5/2019 3:01 PM, Stephen Boyd wrote:
> > Quoting Jeffrey Hugo (2019-01-30 08:35:44)
> >> The XO clock generally feeds into other clock controllers as the parent
> >> for a lot of clock generators.
> >>
> >> Fixes: 6131dc81211c (clk: qcom: smd: Add
> From: Boris Brezillon
> Sent: Sunday, February 3, 2019 12:35 AM
> > +Przemyslaw
> >
> > On Fri, 1 Feb 2019 07:30:39 +0800
> > Liu Jian wrote:
> >
> > > In function do_write_buffer(), in the for loop, there is a case
> > > chip_ready() returns 1 while chip_good() returns 0, so it never
> >
On Tue, Feb 05, 2019 at 07:02:18PM +0100, Christoph Hellwig wrote:
> On Tue, Feb 05, 2019 at 06:56:11PM +0100, Thierry Reding wrote:
> > Sure, here you go:
> >
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/drivers/gpu/host1x/cdma.c#n106
>
> Yes, I think we
On Tue, Feb 05, 2019 at 09:47:32PM +0100, Uwe Kleine-König wrote:
> Hello,
>
> On Tue, Feb 05, 2019 at 01:40:27PM +0100, Fabrice Gasnier wrote:
> > Add suspend/resume PM sleep ops. When going to low power, disable
> > active PWM channel. Active PWM channel is resumed, by calling
> >
On Tue, 5 Feb 2019 17:33:38 +
wrote:
> From: Tudor Ambarus
>
> The sam9x60 qspi controller uses 2 clocks, one for the peripheral register
> access, the other for the qspi core and phy. Both are mandatory. It uses
> different transfer type bits in IFR register. It has dedicated registers
>
On Thu, 10 Jan 2019 16:05:11 -0800 Joe Perches wrote:
> Using SPDX commenting style // or /* is specified for
> various file types in Documentation/process/license-rules.rst
> so add an appropriate test for .[chsS] files because many
> proposed file additions and patches do not use the correct
Updating LED state requires access to regmap and therefore we may sleep, so
we could not do that directly form set_brightness() method. Historically
we used private work to adjust the brightness, but with the introduction of
set_brightness_blocking() we no longer need it.
As a bonus, not having
On 2/5/19 2:13 PM, Florian Fainelli wrote:
> ethsw implements SWITCHDEV_ATTR_ID_PORT_PARENT_ID and we want to get rid
> of switchdev_ops eventually, ease that migration by implementing a
> ndo_get_port_parent_id() function which returns what
> switchdev_port_attr_get() would do.
>
>
Quoting Neil Armstrong (2019-02-04 01:13:30)
> + * Register offsets from the data sheet must be multiplied by 4.
> + */
> +#define AO_RTI_STATUS_REG3 0x0C
> +#define AO_RTI_PWR_CNTL_REG0 0x10
> +#define AO_RTI_GEN_CNTL_REG0 0x40
> +#define AO_CLK_GATE0 0x4c
> +#define
Hi all,
Today's linux-next merge of the mips tree got conflicts in:
arch/mips/include/asm/barrier.h
arch/mips/include/asm/pgtable.h
between commit:
e02e07e3127d ("MIPS: Loongson: Introduce and use loongson_llsc_mb()")
from the mips-fixes tree and commits:
535113896e80 ("MIPS: Add
Quoting Jeffrey Hugo (2019-02-05 14:12:00)
> On 2/5/2019 3:06 PM, Stephen Boyd wrote:
> > Quoting Jeffrey Hugo (2019-01-30 08:36:11)
> > [..]
> >> +};
> >> +MODULE_DEVICE_TABLE(of, mmcc_msm8998_match_table);
> >> +
> >> +static int mmcc_msm8998_probe(struct platform_device *pdev)
> >> +{
> >> +
Quoting Jeffrey Hugo (2019-02-05 14:08:43)
> On 2/5/2019 3:02 PM, Stephen Boyd wrote:
> > Quoting Jeffrey Hugo (2019-01-30 08:35:59)
> >> Document the multimedia clock controller found on MSM8998
> >>
> >> Signed-off-by: Jeffrey Hugo
> >> ---
> >>
In function sun8i_dwmac_set_syscon(), local variable "val" could
be uninitialized if function regmap_read() returns -EINVAL.
However, it will be used directly in the if statement, which
is potentially unsafe.
Signed-off-by: Yizhuo
---
drivers/net/ethernet/stmicro/stmmac/dwmac-sun8i.c | 9
On 2/5/2019 3:01 PM, Stephen Boyd wrote:
Quoting Jeffrey Hugo (2019-01-30 08:35:44)
The XO clock generally feeds into other clock controllers as the parent
for a lot of clock generators.
Fixes: 6131dc81211c (clk: qcom: smd: Add support for MSM8998 rpm clocks)
Signed-off-by: Jeffrey Hugo
Liquidio only supports SWITCHDEV_ATTR_ID_PORT_PARENT_ID, which makes it
a great candidate to be converted to use the ndo_get_port_parent_id()
NDO instead of implementing switchdev_port_attr_get().
Signed-off-by: Florian Fainelli
---
.../net/ethernet/cavium/liquidio/lio_main.c | 22
mlxsw implements SWITCHDEV_ATTR_ID_PORT_PARENT_ID and we want to get rid
of switchdev_ops eventually, ease that migration by implementing a
ndo_get_port_parent_id() function which returns what
switchdev_port_attr_get() would do.
Signed-off-by: Florian Fainelli
---
netdevsim only supports SWITCHDEV_ATTR_ID_PORT_PARENT_ID, which makes it a
great candidate to be converted to use the ndo_get_port_parent_id() NDO
instead of implementing switchdev_port_attr_get().
Signed-off-by: Florian Fainelli
---
drivers/net/netdevsim/netdev.c | 22 ++
1
Ocelot only supports SWITCHDEV_ATTR_ID_PORT_PARENT_ID as a valid
switchdev attribute getter, convert it to use ndo_get_port_parent_id()
and get rid of the switchdev_ops::switchdev_port_attr_get altogether.
Signed-off-by: Florian Fainelli
---
drivers/net/ethernet/mscc/ocelot.c | 33
ethsw implements SWITCHDEV_ATTR_ID_PORT_PARENT_ID and we want to get rid
of switchdev_ops eventually, ease that migration by implementing a
ndo_get_port_parent_id() function which returns what
switchdev_port_attr_get() would do.
Signed-off-by: Florian Fainelli
---
DSA implements SWITCHDEV_ATTR_ID_PORT_PARENT_ID and we want to get rid
of switchdev_ops eventually, ease that migration by implementing a
ndo_get_port_parent_id() function which returns what
switchdev_port_attr_get() would do.
Signed-off-by: Florian Fainelli
---
net/dsa/slave.c | 18
mlxsw implements SWITCHDEV_ATTR_ID_PORT_PARENT_ID and we want to get rid
of switchdev_ops eventually, ease that migration by implementing a
ndo_get_port_parent_id() function which returns what
switchdev_port_attr_get() would do.
Signed-off-by: Florian Fainelli
---
The NXP's Vybryd vf610 can work as a SPI slave device (the CS and clock
signals are provided by master).
It is possible to specify a single device to work in that mode. As we do
use DMA for transferring data, the RX channel must be prepared for
incoming data.
Moreover, in slave mode we just set a
Now that we have a dedicated NDO for getting a port's parent ID, get rid
of SWITCHDEV_ATTR_ID_PORT_PARENT_ID and convert all callers to use the
NDO exclusively. This is a preliminary change to getting rid of
switchdev_ops eventually.
Signed-off-by: Florian Fainelli
---
include/net/switchdev.h
NFP only supports SWITCHDEV_ATTR_ID_PORT_PARENT_ID, which makes it a
great candidate to be converted to use the ndo_get_port_parent_id() NDO
instead of implementing switchdev_port_attr_get().
Since NFP uses switchdev_port_same_parent_id() convert it to use
netdev_port_same_parent_id().
mlx5e only supports SWITCHDEV_ATTR_ID_PORT_PARENT_ID, which makes it a
great candidate to be converted to use the ndo_get_port_parent_id() NDO
instead of implementing switchdev_port_attr_get().
Since mlx5e makes use of switchdev_port_parent_id() convert it to use
netdev_port_same_parent_id().
In preparation for getting rid of switchdev_ops, create a dedicated NDO
operation for getting the port's parent identifier. There are
essentially two classes of drivers that need to implement getting the
port's parent ID which are VF/PF drivers with a built-in switch, and
pure switchdev drivers
BNXT only supports SWITCHDEV_ATTR_ID_PORT_PARENT_ID, which makes it a
great candidate to be converted to use the ndo_get_port_parent_id() NDO
instead of implementing switchdev_port_attr_get(). The conversion is
straight forward here since the PF and VF code use the same getter.
Since bnxt makes
On Tue, Feb 05, 2019 at 07:05:41PM +0100, Philipp Zabel wrote:
> Hi Thierry,
>
> On Fri, 2019-02-01 at 15:00 +0100, Thierry Reding wrote:
> [...]
> > It sounds pretty good and elegant actually. Let me try to restate to see
> > if I understand correctly:
> >
> > So basically what you're saying is
Hi all,
Based on discussion with Ido and feedback from Jakub there are clearly
two classes of users that implement SWITCHDEV_ATTR_ID_PORT_PARENT_ID:
- PF/VF drivers which typically only implement return the port's parent
ID, yet have to implement switchdev_port_attr_get() just for that
-
On 2/5/2019 3:06 PM, Stephen Boyd wrote:
Quoting Jeffrey Hugo (2019-01-30 08:36:11)
[..]
+};
+MODULE_DEVICE_TABLE(of, mmcc_msm8998_match_table);
+
+static int mmcc_msm8998_probe(struct platform_device *pdev)
+{
+ struct device *dev = >dev;
+ int i, ret;
+ struct regmap
On 11/01/2019 07:09:02+, Anson Huang wrote:
> During system suspend, the SNVS RTC's clock will be disabled in
> noirq suspend phase, but SNVS RTC's alarm interrupt could still
> arrive, system will hang if SNVS RTC driver tries to access register
> without clock enabled, this patch fixes the
On 2/5/2019 3:03 PM, Stephen Boyd wrote:
Quoting Jeffrey Hugo (2019-01-30 08:36:24)
diff --git a/arch/arm64/boot/dts/qcom/msm8998.dtsi
b/arch/arm64/boot/dts/qcom/msm8998.dtsi
index 7136ab1..5673a65 100644
--- a/arch/arm64/boot/dts/qcom/msm8998.dtsi
+++ b/arch/arm64/boot/dts/qcom/msm8998.dtsi
On 2/5/2019 3:02 PM, Stephen Boyd wrote:
Quoting Jeffrey Hugo (2019-01-30 08:35:59)
Document the multimedia clock controller found on MSM8998
Signed-off-by: Jeffrey Hugo
---
Documentation/devicetree/bindings/clock/qcom,mmcc.txt | 7 +++
1 file changed, 7 insertions(+)
diff --git
On Thu, Aug 25, 2016 at 2:19 PM Luis R. Rodriguez wrote:
>
> On Thu, Aug 25, 2016 at 09:43:13AM +0200, Christoph Hellwig wrote:
> > The idea seems useful, but I reallt don't like the 'reverse-engineering'
> > approach.
> >
> > If we want to this properly from the ground up we should just split
Quoting Jeffrey Hugo (2019-01-30 08:36:11)
[..]
> +};
> +MODULE_DEVICE_TABLE(of, mmcc_msm8998_match_table);
> +
> +static int mmcc_msm8998_probe(struct platform_device *pdev)
> +{
> + struct device *dev = >dev;
> + int i, ret;
> + struct regmap *regmap;
> + struct clk *c;
>
On Thu, 31 Jan 2019 21:15:17 -0800 Dan Williams
wrote:
> +config SHUFFLE_PAGE_ALLOCATOR
> + bool "Page allocator randomization"
> + default SLAB_FREELIST_RANDOM && ACPI_NUMA
> + help
SLAB_FREELIST_RANDOM is default n, so this patchset won't get much
runtime testing.
How about you
On Tue, Feb 5, 2019 at 4:43 PM Dmitry Torokhov
wrote:
>
> OK, great, I'll write up a patch for cap11xx and others if I find them.
>
Possibly also drivers/input/keyboard/lm8323.c
On 2/1/19 11:24 AM, Florian Fainelli wrote:
> On some platforms (e.g.: ARCH_BRCMSTB) it is possible to enter
> "poweroff" while leaving some wake-up sources enabled such as key
> presses in order to allow for the system to wake-up.
>
> Wire up a .shutdown() callback which calls into the existing
Quoting Jeffrey Hugo (2019-01-30 08:36:24)
> diff --git a/arch/arm64/boot/dts/qcom/msm8998.dtsi
> b/arch/arm64/boot/dts/qcom/msm8998.dtsi
> index 7136ab1..5673a65 100644
> --- a/arch/arm64/boot/dts/qcom/msm8998.dtsi
> +++ b/arch/arm64/boot/dts/qcom/msm8998.dtsi
> @@ -814,6 +814,21 @@
>
Quoting Jeffrey Hugo (2019-01-30 08:35:59)
> Document the multimedia clock controller found on MSM8998
>
> Signed-off-by: Jeffrey Hugo
> ---
> Documentation/devicetree/bindings/clock/qcom,mmcc.txt | 7 +++
> 1 file changed, 7 insertions(+)
>
> diff --git
Quoting Jeffrey Hugo (2019-01-30 08:35:44)
> The XO clock generally feeds into other clock controllers as the parent
> for a lot of clock generators.
>
> Fixes: 6131dc81211c (clk: qcom: smd: Add support for MSM8998 rpm clocks)
> Signed-off-by: Jeffrey Hugo
We've historically left out the XO clk
On 05/02/2019 18:04:49+, Colin King wrote:
> From: Colin Ian King
>
> Shifting a u8 by 24 will cause the value to be promoted to an integer. If
> the top bit of the u8 is set then the following conversion to an unsigned
> long will sign extend the value causing the upper 32 bits to be set in
On 09/01/2019 10:59:40+, oliver.r...@wago.com wrote:
> The Ricoh chips have slightly different register layouts
> and the r2221 chip uses bit 5 as the oscillator halt sensor bit.
>
> Signed-off-by: Olive Rohe
> ---
> drivers/rtc/rtc-rs5c372.c | 32 +---
> 1 file
On Tue, Feb 05, 2019 at 04:54:03PM -0500, Nitesh Narayan Lal wrote:
>
> On 2/5/19 3:45 PM, Michael S. Tsirkin wrote:
> > On Mon, Feb 04, 2019 at 03:18:53PM -0500, Nitesh Narayan Lal wrote:
> >> This patch enables the kernel to scan the per cpu array and
> >> compress it by removing the
Hi,
On 11/01/2019 13:15:39+, oliver.r...@wago.com wrote:
> When the oscillator of the rtc gets interrupted,
> e.g. due to an empty battery, reading from the rtc will now return an error
> and the oscillator bit will be cleared, once the rtc is successfully reset.
>
> Signed-off-by: Oliver
On 2/5/19 5:38 AM, Tom Talpey wrote:
>
> Ok, I'm satisfied the four-9's latency spike is in not your code. :-)
> Results look good relative to baseline. Thanks for doublechecking!
>
> Tom.
Great, in that case, I'll put the new before-and-after results in the next
version. Appreciate your help
Remove @flags from tpm_transmit() API. It is no longer used for
anything.
Signed-off-by: Jarkko Sakkinen
Reviewed-by: Stefan Berger
Tested-by: Stefan Berger
---
v4:
* Fix typos in comments.
v3:
* Fix typo i.e. %s/reminding/remaining/g
v2:
* There was a trailing double colon in the end of the
On 2/5/19 3:45 PM, Michael S. Tsirkin wrote:
> On Mon, Feb 04, 2019 at 03:18:53PM -0500, Nitesh Narayan Lal wrote:
>> This patch enables the kernel to scan the per cpu array and
>> compress it by removing the repetitive/re-allocated pages.
>> Once the per cpu array is completely filled with pages
On 2/5/19 8:40 AM, Mike Rapoport wrote:
> Hi John,
>
> On Sun, Feb 03, 2019 at 09:21:35PM -0800, john.hubb...@gmail.com wrote:
>> From: John Hubbard
>>
>> 1. Added Documentation/vm/get_user_pages.rst
>>
>> 2. Added a GET_USER_PAGES entry in MAINTAINERS
>>
>> Cc: Dan Williams
>> Cc: Jan Kara
>>
On Tue, Feb 05, 2019 at 10:24:47PM +0100, Jacek Anaszewski wrote:
> Hi Dmitry,
>
> On 2/5/19 9:18 AM, Dmitry Torokhov wrote:
> > Hi Sven,
> >
> > On Mon, Feb 04, 2019 at 05:09:52PM -0500, Sven Van Asbroeck wrote:
> > > The work which is scheduled by led_classdev->brightness_set() is
> > >
Thinh Nguyen wrote:
> Bjorn Helgaas wrote:
>> On Tue, Feb 05, 2019 at 08:38:58PM +, Thinh Nguyen wrote:
>>> Hi Bjorn,
>>>
>>> Bjorn Helgaas wrote:
On Fri, Feb 01, 2019 at 08:27:00PM +, Thinh Nguyen wrote:
> Lukas Wunner wrote:
>> On Thu, Jan 31, 2019 at 11:46:23PM +, Thinh
Quoting Paul Cercueil (2019-01-25 07:34:36)
> The UDC clock is gated when the bit is cleared, not when it is set.
>
> Signed-off-by: Paul Cercueil
> Tested-by: Artur Rojek
> ---
Applied to clk-next
Quoting Weiyi Lu (2018-12-13 18:04:16)
> Add new clock according to 3rd ECO design change.
> It's the parent clock of audio clock mux.
>
> Signed-off-by: Weiyi Lu
> ---
Applied to clk-next
Quoting Weiyi Lu (2018-12-13 18:04:17)
> According to 3rd ECO design change,
> 1. Add new fixed factor clock of audio.
> 2. Add the parent clocks for audio clock mux.
>
> Signed-off-by: Weiyi Lu
> ---
Applied to clk-next
Stephen Rothwell writes:
> Hi Eric,
>
> In commit
>
> a692933a8769 ("signal: Always attempt to allocate siginfo for SIGSTOP")
>
> Fixes tag
>
> Fixes: 6dfc88977e42 ("[PATCH] shared thread signals")
>
> has these problem(s):
>
> - Target SHA1 does not exist
The SHA1 tag does exist and I
Hi Dmitry,
On 2/5/19 9:18 AM, Dmitry Torokhov wrote:
Hi Sven,
On Mon, Feb 04, 2019 at 05:09:52PM -0500, Sven Van Asbroeck wrote:
The work which is scheduled by led_classdev->brightness_set() is
potentially left pending or running until after the driver module
is unloaded.
Fix by using
On Sun 2019-02-03 13:20:07, Harry Pan wrote:
> This patch gives the reader an intuitive metric of the time cost by
> the kernel issuing a filesystem sync during suspend; although developer
> can guess by the timestamp of next log or enable the ftrace power event
> for manual calculation, this
On Fri, 1 Feb 2019 18:42:29 -0800 Andy Lutomirski wrote:
> On Fri, Feb 1, 2019 at 12:54 PM Chang S. Bae wrote:
> >
> > For testing (or root-only) purposes, the new flag will serve to tag the
> > kernel taint accurately.
> >
> > When adding a new feature support, patches need to be incrementally
On 2/4/19 8:56 AM, Petr Mladek wrote:
Add proper error handling when allocating or getting shadow variables
in the selftest. It prevents an invalid pointer access in some situations.
It shows the good programming practice in the others.
The error codes are just the best guess and specific for
Hi,
Bisect pointed to commit:
commit 078a85f2806f0ffd11289009462a6a390f9adb5c
Author: Charles Keepax
Date: Thu Jan 31 13:30:18 2019 +
ASoC: dapm: Only power up active channels from a DAI
as a bad commit for NULL pointer on my Odroid XU3 and Odroid U3 board when
doing
On Tue, Feb 05, 2019 at 02:50:39PM +0100, Daniel Bristot de Oliveira wrote:
> >> + if (jump_label_can_update_check(entry, init)) {
> >> + arch_jump_label_transform(entry,
> >> +jump_label_type(entry));
> >
> > Yeah, let that
On Tue, Feb 05, 2019 at 07:24:39AM -0500, Mimi Zohar wrote:
> On Mon, 2019-02-04 at 14:30 -0800, Luis Chamberlain wrote:
> > On Mon, Feb 04, 2019 at 05:05:10PM -0500, Mimi Zohar wrote:
> > > On Mon, 2019-02-04 at 12:38 -0800, Luis Chamberlain wrote:
>
> > > I don't see a need for an additional
On 02/05/2019 04:07 PM, Alex Kogan wrote:
>> Doing time analysis on a randomized algorithm isn't my idea of fun.
>>
>>> It seems that even today, qspinlock does not support RT_PREEMPT, given
>>> that it uses per-CPU queue nodes.
>> It does work with RT, commit:
>>
>> 7aa54be29765
On Mon, 4 Feb 2019 18:53:08 -0800 Ivan Delalande wrote:
> We were seeing unexplained segfaults in coreutils processes and other
> basic utilities on systems with print-fatal-signals enabled:
>
> [ 311.001986] potentially unexpected fatal signal 11.
> [ 311.001993] CPU: 3 PID: 4565
[ Resending after correcting an issue with the included URL and correcting a
typo
in Waiman’s name — sorry about that! ]
> On Feb 5, 2019, at 4:22 AM, Peter Zijlstra wrote:
>
> On Mon, Feb 04, 2019 at 10:35:09PM -0500, Alex Kogan wrote:
>>
>>> On Jan 31, 2019, at 5:00 AM, Peter Zijlstra
According to PCIe 3.0, the presence detect state is a logical OR of
in-band and out-of-band presence. With this, we'd expect the presence
state to always be asserted when the link comes up.
Not all hardware follows this, and it is possible for the presence to
come up after the link. In this case,
Bjorn Helgaas wrote:
> On Tue, Feb 05, 2019 at 08:38:58PM +, Thinh Nguyen wrote:
>> Hi Bjorn,
>>
>> Bjorn Helgaas wrote:
>>> On Fri, Feb 01, 2019 at 08:27:00PM +, Thinh Nguyen wrote:
Lukas Wunner wrote:
> On Thu, Jan 31, 2019 at 11:46:23PM +, Thinh Nguyen wrote:
>> ---
On Tue, Feb 05, 2019 at 08:38:58PM +, Thinh Nguyen wrote:
> Hi Bjorn,
>
> Bjorn Helgaas wrote:
> > On Fri, Feb 01, 2019 at 08:27:00PM +, Thinh Nguyen wrote:
> >> Lukas Wunner wrote:
> >>> On Thu, Jan 31, 2019 at 11:46:23PM +, Thinh Nguyen wrote:
> --- a/drivers/pci/quirks.c
>
On Tue, Feb 05, 2019 at 02:40:22PM -0500, James Bottomley wrote:
> On Mon, 2019-02-04 at 15:37 +0200, Jarkko Sakkinen wrote:
> > diff --git a/drivers/char/tpm/tpm_i2c_infineon.c
> > b/drivers/char/tpm/tpm_i2c_infineon.c
> > index 9086edc9066b..b9d5a1dda8d2 100644
> > ---
On Tue, Feb 05, 2019 at 02:56:02PM +, Winkler, Tomas wrote:
>
>
> > -Original Message-
> > From: Jarkko Sakkinen [mailto:jarkko.sakki...@linux.intel.com]
> > Sent: Tuesday, February 05, 2019 16:36
> > To: Winkler, Tomas
> > Cc: linux-integr...@vger.kernel.org;
On Wed, Feb 06, 2019 at 07:12:57AM +1100, James Morris wrote:
> On Tue, 5 Feb 2019, Jarkko Sakkinen wrote:
>
> > On Mon, Feb 04, 2019 at 03:16:40PM +0200, Jarkko Sakkinen wrote:
> > > Added the tests that I've been using for testing TPM 2.0 functionality
> > > for a long time but have been
On Fri, Feb 01, 2019 at 09:09:46AM +0100, Christoph Hellwig wrote:
> For some reason patch 5 didn't make it to my inbox, but assuming
> nothing has changed this whole series looks good to me now.
Could you send a formal series ack pls?
On Thu, Jan 31, 2019 at 05:33:58PM +0100, Joerg Roedel wrote:
> Hi,
>
> here is the next version of this patch-set. Previous
> versions can be found here:
>
> V1: https://lore.kernel.org/lkml/20190110134433.15672-1-j...@8bytes.org/
>
> V2:
On Mon, Feb 04, 2019 at 03:18:52PM -0500, Nitesh Narayan Lal wrote:
> This patch enables the caller to expose a single buffers to the
> other end using vring descriptor. It also allows the caller to
> perform this action in synchornous manner by using virtqueue_kick_sync.
>
> Signed-off-by:
On Tue, Feb 05, 2019 at 01:30:27PM -0500, Dennis Zhou wrote:
> On Tue, Feb 05, 2019 at 07:27:49PM +0100, David Sterba wrote:
> > On Tue, Feb 05, 2019 at 06:07:49PM +0100, David Sterba wrote:
> > > On Tue, Feb 05, 2019 at 05:51:13PM +0100, David Sterba wrote:
> > > > On Tue, Feb 05, 2019 at
Hello,
On Tue, Feb 05, 2019 at 01:40:27PM +0100, Fabrice Gasnier wrote:
> Add suspend/resume PM sleep ops. When going to low power, disable
> active PWM channel. Active PWM channel is resumed, by calling
> pwm_apply_state(). This is inspired by Thierry's comment in [1].
> Don't touch inactive
From: Bjorn Helgaas
8c56df372bc1 ("net: add support for Cavium PTP coprocessor") added the
Cavium PTP coprocessor driver and enabled it by default. Remove the
"default y" because the driver only applies to Cavium ThunderX processors.
Fixes: 8c56df372bc1 ("net: add support for Cavium PTP
201 - 300 of 928 matches
Mail list logo
