The software_node_get_parent() returned a pointer to the parent swnode,
but did not take a reference to it, leading the caller to put a reference
that was not taken. Take that reference now.
Fixes: 59abd83672f7 ("drivers: base: Introducing software nodes to the firmware
node framework")
Signed-of
Hi all,
This set adds functionality into the device property API (counting a
node's parents as well as obtaining its name) in order to support printing
fwnode names using a new conversion specifier "%pfw". The names that are
produced are equivalent to its OF counterpart "%pOF" on OF systems for th
The prefix is used for printing purpose before a node, and it also works
as a separator between two nodes.
Signed-off-by: Sakari Ailus
Acked-by: Rob Herring (for OF)
Reviewed-by: Andy Shevchenko
---
drivers/acpi/property.c | 22 ++
drivers/base/property.c | 12 +++
> -Original Message-
> From: zhangsha (A)
> Sent: 2019年9月18日 21:06
> To: jay.vosbu...@canonical.com; vfal...@gmail.com; a...@greyhouse.net;
> da...@davemloft.net; net...@vger.kernel.org; linux-kernel@vger.kernel.org;
> yuehaibing ; hunongda ;
> Chenzhendong (alex) ; zhangsha (A)
>
> Subj
On Di, 17.09.19 19:29, Willy Tarreau (w...@1wt.eu) wrote:
> > What do you expect these systems to do though?
> >
> > I mean, think about general purpose distros: they put together live
> > images that are supposed to work on a myriad of similar (as in: same
> > arch) but otherwise very different s
On 9/18/19 5:01 PM, Michael Ellerman wrote:
"Naveen N. Rao" writes:
Michael Ellerman wrote:
"Gautham R. Shenoy" writes:
From: "Gautham R. Shenoy"
Also, since we expose [S]PURR through sysfs, any tools that make use of
that directly are also affected due to this.
But again if we
This series add DT bindings and driver for TI wrapper for Cadence UFS
IP that is present on TI's J721e SoC
Vignesh Raghavendra (2):
dt-bindings: ufs: ti,j721e-ufs.yaml: Add binding for TI UFS wrapper
scsi: ufs: Add driver for TI wrapper for Cadence UFS IP
.../devicetree/bindings/ufs/ti,j721e
Add binding documentation of TI wrapper for Cadence UFS Controller.
Signed-off-by: Vignesh Raghavendra
---
.../devicetree/bindings/ufs/ti,j721e-ufs.yaml | 45 +++
1 file changed, 45 insertions(+)
create mode 100644 Documentation/devicetree/bindings/ufs/ti,j721e-ufs.yaml
diff --
TI's J721e SoC has a Cadence UFS IP with a TI specific wrapper. This is
a minimal driver to configure the wrapper. It releases the UFS slave
device out of reset and sets up registers to indicate PHY reference
clock input frequency before probing child Cadence UFS driver.
Signed-off-by: Vignesh Rag
This looks sensibe to me. x86 folks let me know if you guys want
to pick this up or if I should take it.
On Tue, Sep 17, 2019 at 03:01:13PM +0200, Thomas Hellström (VMware) wrote:
> As far as I can tell there are no current users of dma_mmap_coherent() with
> SEV or SME encryption which means tha
On Wed, Sep 18, 2019 at 05:59:09AM -0700, Guenter Roeck wrote:
> On 9/17/19 11:18 PM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.19.74 release.
> > There are 50 patches in this series, all will be posted as a response
> > to this one. If anyone has any iss
On Thu, Sep 12, 2019 at 01:49:40PM +, Christophe Leroy wrote:
> This series adds support for GENERIC_EARLY_IOREMAP on powerpc.
>
> It also adds a warning in the standard ioremap() when it's called
> before vmalloc is available in order to help locate those users.
>
> Next step will be to incr
On Wed, Sep 18, 2019 at 04:48:00PM +0800, amy.s...@advantech.com.tw wrote:
> From: "amy.shih"
>
> Voltage sensors overlap with external temperature sensors. Detect
> the multi-function of voltage, thermal diode and thermistor from
> register VT_ADC_MD_REG to set value of vsen_mask in nct7904_data
On Wed, Sep 18, 2019 at 2:57 PM Michael S. Tsirkin wrote:
> Overall this looks ok to me. Handling full vq by a timer is really gross
> but it's correct - just terribly inefficient.
Yes. The reason this didn't get too much attention is that it's
relatively difficult to make the queues actually f
On Di, 17.09.19 23:38, Martin Steigerwald (mar...@lichtvoll.de) wrote:
> (I know that it still with /dev/urandom, so if it is using RDRAND now,
> this may indeed be different, but would it then deplete entropy the CPU
> has available and that by default is fed into the Linux crng as well
> (even w
On Mon, 16 Sep 2019, Yash Shah wrote:
> On Sat, Sep 14, 2019 at 2:50 AM Palmer Dabbelt wrote:
> >
> > On Tue, 10 Sep 2019 02:52:07 PDT (-0700), yash.s...@sifive.com wrote:
> > > Hi,
> > >
> > > Any comments on this patch?
> >
> > I don't see "sifive,pwm0" in the DT bindings documentation, and it
On 18/09/19 15:15, Will Deacon wrote:
> When records are written to the coalesced MMIO ring in response to a
> vCPU MMIO exit, the 'ring->last' field is used to index the ring buffer
> page. Although we hold the 'kvm->ring_lock' at this point, the ring
> structure is mapped directly into the host u
Hi Laurent,
Thanks for fixing this, just a few comments.
Laurent Dufour writes:
> Since the commit ba2dd8a26baa ("powerpc/pseries/mm: call H_BLOCK_REMOVE"),
> the call to H_BLOCK_REMOVE is always done if the feature is exhibited.
>
> However, the hypervisor may not support all the block size for
Hi Laurent,
Comments below ...
Laurent Dufour writes:
> The PAPR document specifies the TLB Block Invalidate Characteristics which
> tells for each couple segment base page size, actual page size, the size of
^
"pair of" again
> the block the hcall H_BLOCK_REMO
Hi Laurent,
Few comments ...
Laurent Dufour writes:
> Now we do not call _BLOCK_REMOVE all the time when the feature is
> exhibited.
This isn't true until after the patch is applied, ie. the tense is
wrong. The rest of the change log explains things fine, so just drop
that sentence I think.
Ca
On Wed, Sep 18, 2019 at 6:10 AM Pragnesh Patel
wrote:
>
> Convert the spi-sifive binding to DT schema format.
>
> Signed-off-by: Pragnesh Patel
> ---
>
> Changes in v2:
> - Remove address-cells and size-cells property
> - Added valid values for sifive,fifo-depth and sifive,max-bits-per-word
> p
On 9/18/19 7:06 AM, Greg KH wrote:
On Tue, Sep 17, 2019 at 09:29:52AM -0500, Pierre-Louis Bossart wrote:
On 9/17/19 12:55 AM, Greg KH wrote:
On Mon, Sep 16, 2019 at 04:23:41PM -0500, Pierre-Louis Bossart wrote:
+/**
+ * sdw_intel_probe() - SoundWire Intel probe routine
+ * @parent_handle: ACPI
On Wed, Sep 18, 2019 at 5:08 AM Maciej Falkowski
wrote:
>
>
> On 9/17/19 3:05 PM, Rob Herring wrote:
>
> > On Tue, Sep 17, 2019 at 7:05 AM Maciej Falkowski
> > wrote:
> >> Convert Samsung I2S controller to newer dt-schema format.
> >>
> >> Signed-off-by: Maciej Falkowski
> >> Signed-off-by: Mare
On Wed, Sep 18, 2019 at 03:40:03PM +0200, Greg Kroah-Hartman wrote:
> On Wed, Sep 18, 2019 at 05:59:09AM -0700, Guenter Roeck wrote:
> > On 9/17/19 11:18 PM, Greg Kroah-Hartman wrote:
> > > This is the start of the stable review cycle for the 4.19.74 release.
> > > There are 50 patches in this seri
On 2019-09-17, Jann Horn wrote:
> On Wed, Sep 4, 2019 at 10:21 PM Aleksa Sarai wrote:
> > The ability for userspace to "re-open" file descriptors through
> > /proc/self/fd has been a very useful tool for all sorts of usecases
> > (container runtimes are one common example). However, the current
>
> Subject: Re: [PATCH V6 1/2] dt-bindings: mailbox: add binding doc for the
> ARM SMC/HVC mailbox
>
> On Wed, Sep 18, 2019 at 3:53 AM Peng Fan wrote:
>
> > > >
> > > > > +
> > > > > + "#mbox-cells":
> > > > > +const: 1
> > > >
> > > > Why is this "1"? What is this number used for? It used t
Tnx Rob for the review.
Shall be part of v3.
Waiting for responses from Arnd and James and will publish v3.
On 9/18/2019 4:35 PM, Rob Herring wrote:
On Tue, Sep 10, 2019 at 10:05:08PM +0300, Talel Shenhar wrote:
Document Amazon's Annapurna Labs POS SoC binding.
Signed-off-by: Talel Shenhar
On Wed, Sep 18, 2019 at 08:48:33AM -0500, Pierre-Louis Bossart wrote:
> On 9/18/19 7:06 AM, Greg KH wrote:
> > On Tue, Sep 17, 2019 at 09:29:52AM -0500, Pierre-Louis Bossart wrote:
> > > On 9/17/19 12:55 AM, Greg KH wrote:
> > > > On Mon, Sep 16, 2019 at 04:23:41PM -0500, Pierre-Louis Bossart wrote
On Mi, 18.09.19 00:10, Martin Steigerwald (mar...@lichtvoll.de) wrote:
> > getrandom() will never "consume entropy" in a way that will block any
> > users of getrandom(). If you don't have enough collected entropy to
> > seed the rng, getrandom() will block. If you do, getrandom() will
> > generat
On Wed, Sep 18, 2019 at 03:53:02PM +0200, Greg KH wrote:
> On Wed, Sep 18, 2019 at 08:48:33AM -0500, Pierre-Louis Bossart wrote:
> > On 9/18/19 7:06 AM, Greg KH wrote:
> > > On Tue, Sep 17, 2019 at 09:29:52AM -0500, Pierre-Louis Bossart wrote:
> > > > On 9/17/19 12:55 AM, Greg KH wrote:
> > > > > O
On Wed, 18 Sep 2019 at 11:51, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.14.145 release.
> There are 45 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Re
On Wed, 18 Sep 2019 16:34:07 +0300
Sakari Ailus wrote:
> There are no in-kernel %p[fF] users left. Convert the traceevent tool,
> too, to align with the kernel.
>
> Signed-off-by: Sakari Ailus
> Cc: Steven Rostedt
> Cc: Arnaldo Carvalho de Melo
> Cc: Tzvetomir Stoyanov
> Cc: linux-trace-de..
On Wed, 18 Sep 2019 08:31:57 -0500
Jassi Brar wrote:
Hi,
> On Wed, Sep 18, 2019 at 5:00 AM Andre Przywara wrote:
>
> > >
> > > >
> > > > > + };
> > > > > +};
> > > >
> > > > If this is the data structure that this mailbox controller uses, I
> > > > would expect
> > > > this to be docume
On Wed, Sep 18, 2019 at 03:41:40PM +0200, Paolo Bonzini wrote:
> On 18/09/19 15:15, Will Deacon wrote:
> > When records are written to the coalesced MMIO ring in response to a
> > vCPU MMIO exit, the 'ring->last' field is used to index the ring buffer
> > page. Although we hold the 'kvm->ring_lock'
18.09.2019 18:38, Lennart Poettering пишет:
On Di, 17.09.19 19:29, Willy Tarreau (w...@1wt.eu) wrote:
What do you expect these systems to do though?
I mean, think about general purpose distros: they put together live
images that are supposed to work on a myriad of similar (as in: same
arch) bu
On Wed, 18 Sep 2019 16:34:15 +0300
Sakari Ailus wrote:
> Add a note warning of re-use of obsolete %pf or %pF extensions.
>
> Signed-off-by: Sakari Ailus
> Cc: Steven Rostedt
Suggested-by: Steven Rostedt (VMware)
> ---
> lib/vsprintf.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --g
On Wed, Sep 18, 2019 at 09:19:14PM +0800, Jia He wrote:
> When we tested pmdk unit test [1] vmmalloc_fork TEST1 in arm64 guest, there
> will be a double page fault in __copy_from_user_inatomic of cow_user_page.
>
> Below call trace is from arm64 do_page_fault for debugging purpose
> [ 110.016195]
From: Matt Delco
The first/last indexes are typically shared with a user app.
The app can change the 'last' index that the kernel uses
to store the next result. This change sanity checks the index
before using it for writing to a potentially arbitrary address.
This fixes CVE-2019-14821.
Cc: st
Compatible property is not of type 'string' so replace enum
with items.
Signed-off-by: Pragnesh Patel
---
Documentation/devicetree/bindings/regulator/fixed-regulator.yaml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/regulator/fixed-regulat
Le 17/09/2019 à 03:43, Alastair D'Silva a écrit :
From: Alastair D'Silva
Add functions to map/unmap LPC memory
Signed-off-by: Alastair D'Silva
---
drivers/misc/ocxl/config.c| 4 +++
drivers/misc/ocxl/core.c | 50 +++
drivers/misc/ocxl/link.
Le 17/09/2019 à 03:42, Alastair D'Silva a écrit :
From: Alastair D'Silva
Tally up the LPC memory on an OpenCAPI link & allow it to be mapped
Signed-off-by: Alastair D'Silva
---
drivers/misc/ocxl/core.c | 9 +
drivers/misc/ocxl/link.c | 61 +
Le 17/09/2019 à 03:42, Alastair D'Silva a écrit :
From: Alastair D'Silva
Map & release OpenCAPI LPC memory.
Signed-off-by: Alastair D'Silva
---
arch/powerpc/include/asm/pnv-ocxl.h | 2 ++
arch/powerpc/platforms/powernv/ocxl.c | 42 +++
2 files changed, 44 ins
According to the DP83865 datasheet "The 10 Mbps HDX loopback can be
disabled in the expanded memory register 0x1C0.1." The driver erroneously
used bit 0 instead of bit 1.
Signed-off-by: Peter Mamonov
---
drivers/net/phy/national.c | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
dif
On 18/09/2019 16.28, Rob Herring wrote:
> On Tue, Sep 10, 2019 at 02:45:57PM +0300, Peter Ujfalusi wrote:
>> Make the dma-channel-mask to be usable for controllers with more than 32
>> channels.
>>
>> Signed-off-by: Peter Ujfalusi
>> ---
>> Documentation/devicetree/bindings/dma/dma-common.yaml
On 18/09/2019 16.29, Rob Herring wrote:
> On Tue, Sep 10, 2019 at 02:45:58PM +0300, Peter Ujfalusi wrote:
>> Similarly to paRAM slots, channels can be used by other cores.
>>
>> The common dma-channel-mask property can be used for specifying the
>> available channels.
>>
>> Signed-off-by: Peter
Since commit 26202873bb51 ("avr32: remove support for AVR32
architecture") there is no more user of platform_device_id and we
should only use dt bindings
Signed-off-by: Kamel Bouhara
---
drivers/pwm/Kconfig | 2 +-
drivers/pwm/pwm-atmel.c | 29 +++--
2 files changed,
On Wed, Sep 18, 2019 at 04:01:42PM +0200, Paolo Bonzini wrote:
> From: Matt Delco
>
> The first/last indexes are typically shared with a user app.
> The app can change the 'last' index that the kernel uses
> to store the next result. This change sanity checks the index
> before using it for writ
pecify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url:
https://github.com/0day-ci/linux/commits/Gene-Chen/mfd-mt6360-add-pmic-mt6360-driver/20190918-181041
config: s390-allmodconfig (attached as .config)
compiler: s390-linux-gcc (GCC) 7.4.0
reproduce:
On 18/09/19 15:59, Will Deacon wrote:
> Okey doke, as long as it gets fixed! My minor concerns with the error-checking
> variant are:
>
> * Whether or not you need a READ_ONCE to prevent the compiler potentially
> reloading 'ring->last' after validation
Yes, it certainly needs READ_ONCE. I
-Original Message-
From: Nikolaus Voss [mailto:n...@vosn.de]
Sent: Monday, September 16, 2019 2:47 AM
To: Moore, Robert
Cc: Ferry Toth ; Shevchenko, Andriy
; Schmauss, Erik ; Rafael
J. Wysocki ; Len Brown ; Jacek Anaszewski
; Pavel Machek ; Dan Murphy
; linux-a...@vger.kernel.org;
> -Original Message-
> From: Markus Elfring
> Sent: Wednesday, September 18, 2019 7:01 PM
> To: net...@vger.kernel.org; linux-arm-ker...@lists.infradead.org; David S.
> Miller ; Hans Ulli Kroll ;
> Hauke Mehrtens ; Linus Walleij
> ; Michal Simek ; Radhey
> Shyam Pandey
> Cc: LKML ; kernel
On Wed, 18 Sep 2019, Andrey Konovalov wrote:
> > > Why does dumy_hcd require CONFIG_HZ=1000? The comment doesn't really
> > > explain the reason.
> >
> > Oh, that's simple enough. USB events tend to happen at millisecond
> > intervals. The data on the USB bus is organized into frames (and
> > mi
On Wed, Sep 18, 2019 at 05:03:40PM +0300, Peter Mamonov wrote:
> According to the DP83865 datasheet "The 10 Mbps HDX loopback can be
> disabled in the expanded memory register 0x1C0.1." The driver erroneously
> used bit 0 instead of bit 1.
>
> Signed-off-by: Peter Mamonov
> ---
> drivers/net/phy
On Wed, Sep 18, 2019 at 13:41:04 +0100, Parth Shah wrote...
> Hello everyone,
Hi Parth,
thanks for staring this discussion.
[ + patrick.bell...@matbug.net ] my new email address, since with
@arm.com I will not be reachable anymore starting next week.
> As per the discussion in LPC2019, new pe
On Wed, Sep 18, 2019 at 09:19:12PM +0800, Jia He wrote:
> +/* Decouple AF from AFDBM. */
> +bool cpu_has_hw_af(void)
> +{
> + return (read_cpuid(ID_AA64MMFR1_EL1) & 0xf);
> +}
> +
Do you really want to call read_cpuid() every time? I would have thought
you'd want to use the static branch mech
On Wed, Sep 18, 2019 at 4:44 AM Andre Przywara wrote:
>
> > which needs 9 arguments to work. The fact that the fist argument is
> > always going to be same on a platform is just the way we use this
> > instruction.
> >
> > > We should be as strict as possible to avoid any security issues.
> > >
>
Hi Jia,
On 18/09/2019 14:19, Jia He wrote:
We unconditionally set the HW_AFDBM capability and only enable it on
CPUs which really have the feature. But sometimes we need to know
whether this cpu has the capability of HW AF. So decouple AF from
DBM by new helper cpu_has_hw_af().
Signed-off-by: J
On 9/18/19 12:19 PM, Andrew Murray wrote:
> On Mon, Sep 16, 2019 at 11:41:36PM +0300, Denis Efremov wrote:
>> To iterate through all possible BARs, loop conditions refactored to the
>> *number* of BARs "i < PCI_STD_NUM_BARS", instead of the index of the last
>> valid BAR "i <= BAR_5". This is more
On Wed, Sep 18, 2019 at 9:04 AM Peter Ujfalusi wrote:
>
>
>
> On 18/09/2019 16.28, Rob Herring wrote:
> > On Tue, Sep 10, 2019 at 02:45:57PM +0300, Peter Ujfalusi wrote:
> >> Make the dma-channel-mask to be usable for controllers with more than 32
> >> channels.
> >>
> >> Signed-off-by: Peter Ujfa
Linus,
this pull request is independent of the merge window. Please pull it as it
fixes a longstanding bug that was recently found by both Google humans
and bots (syzkaller).
The following changes since commit a9c20bb0206ae9384bd470a6832dd8913730add9:
Merge tag 'kvm-s390-master-5.3-1' of
git
On Wed, Sep 18, 2019 at 8:58 AM Andre Przywara wrote:
>
> > > Also there is mbox_chan_txdone() with which a controller driver can
> > > signal TX completion explicitly.
> > >
> > No. Controller can use that only if it has specified txdone_irq, which
> > is not the case here.
>
> I see. So does t
On Tue, 17 Sep 2019, Abhishek Pandit-Subedi wrote:
> On a Realtek USB bluetooth device, I wanted a simple and consistent way
> to put the device in reset during suspend (2 reasons: to save power and
> disable BT as a wakeup source). Resetting it in the suspend callback
> causes a detach and the re
Changes in v3:
- Squash code changes to single patch to avoid compilation error
The changes in this patchset will not affect the userspace interface.
Rather, these changes are intended to simplify the kernelspace Counter
callbacks for counter device driver authors.
The following main changes are
Count data is now always represented as an unsigned integer, while
Signal data is either SIGNAL_LOW or SIGNAL_HIGH.
Signed-off-by: William Breathitt Gray
---
Documentation/driver-api/generic-counter.rst | 22 +++-
1 file changed, 8 insertions(+), 14 deletions(-)
diff --git a/Doc
The count_read and count_write callbacks are simplified to pass val as
unsigned long rather than as an opaque data structure. The opaque
counter_count_read_value and counter_count_write_value structures,
counter_count_value_type enum, and relevant counter_count_read_value_set
and counter_count_writ
On 9/18/19 11:58 AM, Andrew Murray wrote:
> On Mon, Sep 16, 2019 at 11:41:38PM +0300, Denis Efremov wrote:
>> Remove local definition PCI_BAR_COUNT for the number of PCI BARs and use
>> global one PCI_STD_NUM_BARS instead.
>>
>> Acked-by: Sebastian Ott
>> Cc: Gerald Schaefer
>> Signed-off-by: Den
CC crypto keys people
TL;DR: CONFIG_CRYPTO_DH=y is reported to cause boot delays of several
minutes on old and slow machines. Can KEY_DH_OPERATIONS be made tristate?
On Wed, Sep 18, 2019 at 4:08 PM Geert Uytterhoeven wrote:
> On Wed, Sep 18, 2019 at 3:57 PM John Paul Adrian Glaubitz
> wrote:
>
On Wed, Sep 18, 2019 at 9:02 AM Pragnesh Patel
wrote:
>
The subject could be more specific rather than being one that applies
to any dt_binding_check breakage in regulators.
> Compatible property is not of type 'string' so replace enum
> with items.
>
> Signed-off-by: Pragnesh Patel
> ---
> Do
On Wed, Sep 18, 2019 at 10:00:23AM -0400, Steven Rostedt wrote:
> On Wed, 18 Sep 2019 16:34:15 +0300
> Sakari Ailus wrote:
>
> > Add a note warning of re-use of obsolete %pf or %pF extensions.
> >
> > Signed-off-by: Sakari Ailus
> > Cc: Steven Rostedt
>
> Suggested-by: Steven Rostedt (VMware)
Hi,
On Sat, Sep 14, 2019 at 08:42:22AM +0200, Jernej Škrabec wrote:
> Dne četrtek, 12. september 2019 ob 22:26:47 CEST je Maxime Ripard napisal(a):
> > Hi,
> >
> > On Thu, Sep 12, 2019 at 07:51:31PM +0200, Jernej Skrabec wrote:
> > > + dev->regmap = devm_regmap_init_mmio(dev->dev, dev->base,
> > >
On Wed, 18 Sep 2019, Moore, Robert wrote:
-Original Message-
From: Nikolaus Voss [mailto:n...@vosn.de]
Sent: Monday, September 16, 2019 2:47 AM
To: Moore, Robert
Cc: Ferry Toth ; Shevchenko, Andriy ; Schmauss, Erik
; Rafael J. Wysocki ; Len Brown ; Jacek Anaszewski
; Pavel Machek ; D
On 9/18/19 12:17 PM, Andrew Murray wrote:
> On Mon, Sep 16, 2019 at 11:41:49PM +0300, Denis Efremov wrote:
>> Refactor loops to use idiomatic C style and avoid the fencepost error
>> of using "i < PCI_STD_RESOURCE_END" when "i <= PCI_STD_RESOURCE_END"
>> is required, e.g., commit 2f686f1d9bee ("PCI
On Wed, Sep 18, 2019 at 01:51:21PM +0800, Jason Wang wrote:
>
> On 2019/9/17 下午6:58, Tiwei Bie wrote:
> > On Tue, Sep 17, 2019 at 11:32:03AM +0800, Jason Wang wrote:
> > > On 2019/9/17 上午9:02, Tiwei Bie wrote:
> > > > This RFC is to demonstrate below ideas,
> > > >
> > > > a) Build vhost-mdev on
On Wed, Sep 18, 2019 at 05:51:10AM +, Yonghong Song wrote:
>
> Adding cc to b...@vger.kernel.org mailing list since this is really
> bpf related.
>
> On 9/17/19 10:24 PM, jinshan.xi...@gmail.com wrote:
> > From: Jinshan Xiong
> >
> > Invoking bpf program only if kprobe based perf_event has
Add a note warning of re-use of obsolete %pf or %pF extensions.
Signed-off-by: Sakari Ailus
Cc: Steven Rostedt
Suggested-by: Steven Rostedt (VMware)
---
lib/vsprintf.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/lib/vsprintf.c b/lib/vsprintf.c
index b00b57f9f911f..ef094e6124798 10064
On Mon, Sep 09, 2019 at 08:10:07PM -0700, Sagi Grimberg wrote:
> Hey Ming,
>
> > > > Ok, so the real problem is per-cpu bounded tasks.
> > > >
> > > > I share Thomas opinion about a NAPI like approach.
> > >
> > > We already have that, its irq_poll, but it seems that for this
> > > use-case, we
Currently there's no easy way to make perf scripts in sync with
tracepoints. One possible way is to run perf's tests regularly, another way
is once we changes the definitions of tracepoints we must keep in mind that
the perf scripts which are using these tracepoints must be changed as well.
So I ad
A new perf script page-reclaim is introduced in this patchset.
This new script is used to report the page reclaim details. The possible
usage of this script is as bellow,
- identify latency spike caused by direct reclaim
- whehter the latency spike is relevant with pageout
- why is page reclaim req
A new perf script page-reclaim is introduced in this patch. This new script
is used to report the page reclaim details. The possible usage of this
script is as bellow,
- identify latency spike caused by direct reclaim
- whehter the latency spike is relevant with pageout
- why is page reclaim reques
On Wed, 18 Sep 2019, Matthias Maennich wrote:
> Follow common practice and retire printk(KERN_ERR ...) in favor of
> pr_fmt and pr_err.
As long as you're changing this, why not change it to dev_err()
instead? That would be a lot more useful.
> Cc: Alan Stern
> Cc: Greg Kroah-Hartman
> Cc: us
On Mon, 2019-09-16 at 10:42 -0400, Steven Rostedt wrote:
> On Thu, 12 Sep 2019 08:05:41 -0400
> Qian Cai wrote:
>
> > > drivers/char/random.c | 7 ---
> > > 1 file changed, 4 insertions(+), 3 deletions(-)
> > >
> > > diff --git a/drivers/char/random.c b/drivers/char/random.c
> > > index 9b5
Hi,
On 18/09/2019 16:05:34+0200, Kamel Bouhara wrote:
> Since commit 26202873bb51 ("avr32: remove support for AVR32
> architecture") there is no more user of platform_device_id and we
> should only use dt bindings
>
> Signed-off-by: Kamel Bouhara
> ---
> drivers/pwm/Kconfig | 2 +-
> drive
Am Dienstag, den 17.09.2019, 14:27 -0700 schrieb Abhishek Pandit-
Subedi:
> On a Realtek USB bluetooth device, I wanted a simple and consistent way
> to put the device in reset during suspend (2 reasons: to save power and
The device really uses less power if you reset it before suspendening
it?
>
I was investigating a rcu stall warning on ARM64 Renesas Rcar3
platform. On analysis I found that rcu stall warning was because the
rcu_preempt kthread was starved of cpu time. rcu_preempt was blocked in
the function schedule_timeout() and never woken up. On further
investigation I found that local
When a cpu requests broadcasting, before starting the tick broadcast
hrtimer, bc_set_next() checks if the timer callback (bc_handler) is
active using hrtimer_try_to_cancel(). But hrtimer_try_to_cancel() does
not provide the required synchronization when the callback is active on
other core.
The cal
On Tue, Sep 17, 2019 at 11:43:47PM +0100, Russell King - ARM Linux admin wrote:
> On Tue, Sep 17, 2019 at 11:30:13PM +0100, Russell King - ARM Linux admin
> wrote:
> > On Tue, Sep 17, 2019 at 04:32:53PM +0300, tinywrkb wrote:
> > > Here's the output of # mii-tool -v -v eth0
> > >
> > > * linux-t
On Wed, 18 Sep 2019 09:19:46 -0500
Jassi Brar wrote:
Hi,
> On Wed, Sep 18, 2019 at 4:44 AM Andre Przywara wrote:
>
> >
> > > which needs 9 arguments to work. The fact that the fist argument is
> > > always going to be same on a platform is just the way we use this
> > > instruction.
> > >
On Mon, Sep 09, 2019 at 08:42:35PM +0200, Jernej Skrabec wrote:
> Depending on kernel and bootloader configuration, it's possible that
> Realtek ethernet PHY isn't powered on properly. According to the
> datasheet, it needs 30ms to power up and then some more time before it
> can be used.
>
> Fix t
According to the DP83865 datasheet "The 10 Mbps HDX loopback can be
disabled in the expanded memory register 0x1C0.1." The driver erroneously
used bit 0 instead of bit 1.
Signed-off-by: Peter Mamonov
---
drivers/net/phy/national.c | 9 ++---
1 file changed, 6 insertions(+), 3 deletions(-)
d
18.09.2019 18:59, Alexander E. Patrakov пишет:
18.09.2019 18:38, Lennart Poettering пишет:
On Di, 17.09.19 19:29, Willy Tarreau (w...@1wt.eu) wrote:
What do you expect these systems to do though?
I mean, think about general purpose distros: they put together live
images that are supposed to w
Dearest one.
Good day to you. I am using this medium to request for your assistance
in transferring ownership of the sum of $12.5m I discovered during
auditing in my bank. I'm Mrs Juliana Pedro Audit and Account manager
of my Bank Branch in Ouagadougou-Burkina Faso, Please if you are
interested ki
On 09/13/19 14:30, Dietmar Eggemann wrote:
> On 9/4/19 4:40 PM, Qais Yousef wrote:
> > On 09/04/19 07:25, Steven Rostedt wrote:
> >> On Tue, 3 Sep 2019 11:33:29 +0100
> >> Qais Yousef wrote:
>
> [...]
>
> >>> @@ -1614,7 +1660,8 @@ static void put_prev_task_rt(struct rq *rq, struct
> >>> task_s
LPTimer can use a 32KHz clock for counting. It depends on clock tree
configuration. In such a case, PWM output frequency range is limited.
Although unlikely, nothing prevents user from requesting a PWM frequency
above counting clock (32KHz for instance):
- This causes (prd - 1) = 0x to be writt
Since commit 26202873bb51 ("avr32: remove support for AVR32
architecture") there is no more user of platform_device_id and we
should only use dt bindings
Signed-off-by: Kamel Bouhara
---
Changelog:
v1->v2
- Remove whole function atmel_pwm_get_driver_data and call
of_device_get_match_data fro
Hello Nicolas,
On Wed, Sep 18, 2019 at 11:44:55AM +0200, Nicolas Dichtel wrote:
> Le 17/09/2019 à 17:53, George G. Davis a écrit :
> [snip]
> > Ping, "Linux 5.3" kernel has been released [1] and it appears that the
> > 5.4 merge window is open. The patch [2] remains unchanged since my initial
> >
On Wed, Sep 18, 2019 at 1:19 PM syzbot
wrote:
>
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:a7f89616 Merge branch 'for-5.3-fixes' of git://git.kernel...
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=15c3307960
> kernel config:
Hi Adam,
On 19-09-18 12:41, Adam Thomson wrote:
> On 17 September 2019 13:43, Marco Felsch wrote:
>
> > Currently the suspend reg_field maps to the pmic voltage selection bits
> > and is used during suspend_enabe/disable() and during get_mode(). This
> > seems to be wrong for both use cases.
>
>
On Wed, 18 Sep 2019, greentime...@sifive.com wrote:
> From: Greentime Hu
>
> To adjust the place of VMALLOC_* and FIXADDR_* defined location to let
> VMEMMAP_*
> get it.
>
> CC init/main.o
> In file included from ./include/linux/mm.h:99,
> from ./include/linux/ring_buff
On 06/09/2019 07:10, Vinod Koul wrote:
> SM8150 UFS PHY is v4 of QMP phy. Add support for V4 QMP phy register
> defines and support for SM8150 QMP UFS PHY.
>
> Signed-off-by: Vinod Koul
> Reviewed-by: Bjorn Andersson
> ---
> drivers/phy/qualcomm/phy-qcom-qmp.c | 125 +++
On 18/09/2019 16:57:16+0200, Kamel Bouhara wrote:
> Since commit 26202873bb51 ("avr32: remove support for AVR32
> architecture") there is no more user of platform_device_id and we
> should only use dt bindings
>
> Signed-off-by: Kamel Bouhara
Acked-by: Alexandre Belloni
>cj ---
> Changelog:
>
301 - 400 of 847 matches
Mail list logo
