Le 18/02/2019 à 10:27, Michael Ellerman a écrit :
Christophe Leroy writes:
diff --git a/arch/powerpc/include/asm/ppc_asm.h
b/arch/powerpc/include/asm/ppc_asm.h
index e0637730a8e7..dba2c1038363 100644
--- a/arch/powerpc/include/asm/ppc_asm.h
+++ b/arch/powerpc/include/asm/ppc_asm.h
@@ -251,
* Julia Lawall [190219 17:33]:
> On Tue, 19 Feb 2019, Tony Lindgren wrote:
> > In general, if the device tree node is never used afterwards,
> > should this be just:
> >
> > r = of_platform_populate(node, NULL, NULL, &pdev->dev);
> > of_node_put(dev_node);
> > if (r) {
> >
* Tony Lindgren [190219 17:11]:
> * Lokesh Vutla [190219 16:19]:
> > yes. How different is this from any of the above mentioned drivers using
> > firmware specific ids. Like sci pm domain[1] driver utilizes the same
> > device id for enabling any device in the system. Similarly clock
> > driver[2
On Tue, Feb 19, 2019 at 05:55:33PM +0100, Vlastimil Babka wrote:
> On 2/14/19 9:38 PM, Andrew Morton wrote:
> > On Thu, 14 Feb 2019 12:45:51 + Peng Fan wrote:
> >
> >> In case cma_init_reserved_mem failed, need to free the memblock allocated
> >> by memblock_reserve or memblock_alloc_range.
>
On Mon, 18 Feb 2019 19:08:48 +0100
Pierre Morel wrote:
> Libudev relies on having a subsystem link for non-root devices. To
> avoid libudev (and potentially other userspace tools) choking on the
> matrix device let us introduce a vfio_ap bus and with that the vfio_ap
> bus subsytem, and make the
Replace Alan Douglas with Tom Joseph as the current PCI
Cadence host/endpoint controller maintainer.
Signed-off-by: Lorenzo Pieralisi
Cc: Bjorn Helgaas
Cc: Tom Joseph
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 32d76a9
> On Feb 19, 2019, at 12:32 PM, Håkon Bugge wrote:
>
>
>
>> On 19 Feb 2019, at 15:58, Chuck Lever wrote:
>>
>> Hey Håkon-
>>
>>> On Feb 18, 2019, at 1:33 PM, Håkon Bugge wrote:
>>>
>>> MAD packet sending/receiving is not properly virtualized in
>>> CX-3. Hence, these are proxied through
On 2/18/19 5:42 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.20.11 release.
There are 92 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.
Responses should be made
On 02/19, Guenter Roeck wrote:
>
> On Tue, Feb 19, 2019 at 01:37:57PM +0100, Oleg Nesterov wrote:
> >
> > looks unrelated...
> >
>
> Indeed...
>
> The underlying problem is in the error handling code of ace_setup(),
> which calls put_disk() followed by blk_cleanup_queue(). put_disk()
> calls disk_r
On Tue, 19 Feb 2019, Tony Lindgren wrote:
> Hi,
>
> Adding devicetree list, Julia, Rob and Tomi to Cc.
>
> * Peng Hao [190212 23:11]:
> > of_find_device_by_node() takes a reference to the struct device
> > when it finds a match via get_device.When returning error we should
> > call put_device.
On Tue, Feb 19, 2019 at 09:34:56AM -0700, Jason Gunthorpe wrote:
> > - Your real name is formatted incorrectly. It should be like "Yue Haibig"
> > as shown in [1].
> > - If there is no actual regression, this change is useless.
>
> Clarity of the code is a laudible goal - not everything is about
Hi all,
I have been looking at using Linux RT in Dom0. Once the guest is started,
the console is ending to have a lot of warning (see trace below).
After some investigation, this is because the irq handler will now be threaded.
I can reproduce the same error with the vanilla Linux when passing th
On Tue, 19 Feb 2019, Tony Lindgren wrote:
> Hi,
>
> Adding devicetree list, Julia, Rob and Tomi to Cc.
>
> * Peng Hao [190212 23:11]:
> > of_find_device_by_node() takes a reference to the struct device
> > when it finds a match via get_device.When returning error we should
> > call put_device.
Multi-master support is defeatured on Tegra210 and Tegra186 due to
known bugs.
This patch removes multi-master support for Tegra210 and Tegra186
I2C HW feature.
Acked-by: Thierry Reding
Signed-off-by: Sowjanya Komatineni
---
drivers/i2c/busses/i2c-tegra.c | 4 ++--
1 file changed, 2 insertions
Tegra186 does not have master FIFO control register and instead
uses FIFO control register like prior Tegra chipset.
This patch fixes this and prevents crashing during boot when
accessing FIFO control registers.
Acked-by: Thierry Reding
Signed-off-by: Sowjanya Komatineni
---
drivers/i2c/busse
On 2/18/19 5:42 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.19.24 release.
There are 85 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.
Responses should be made
On 2/18/19 5:43 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.14.102 release.
There are 62 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.
Responses should be made
On 2/18/19 5:43 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.9.159 release.
There are 58 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.
Responses should be made
On 2/18/19 5:42 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.4.175 release.
There are 143 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.
Responses should be made
On Tue, Feb 19, 2019 at 09:05:31AM +0300, Alexey Dobriyan wrote:
> > /proc/kheaders.txz
>
> This is gross.
It is a bit gross, but it solves a long standing problem we have nicely. And
there's also /proc/config.gz.
> > The feature is also buildable as a module just in case the user desires
> > it
> Thanks for the suggestion! So I had a closer look at that driver to try
> and see what could go wrong and it looks like I found a few things
> there.
Hi Paul
Yes, this driver has issues. If i remember correctly, it got merged
while i was on vacation. I pointed out a few issues, but the authors
On Tue, Feb 19, 2019 at 7:24 AM Vlastimil Babka wrote:
>
> On 2/1/19 6:15 AM, Dan Williams wrote:
> > In preparation for runtime randomization of the zone lists, take all
> > (well, most of) the list_*() functions in the buddy allocator and put
> > them in helper functions. Provide a common contro
On Mon, Feb 18, 2019 at 03:25:31PM +0100, Brice Goglin wrote:
> Le 14/02/2019 à 18:10, Keith Busch a écrit :
> > Determining the cpu and memory node local relationships is quite
> > different this time (PATCH 7/10). The local relationship to a memory
> > target will be either *only* the node
On 2019-02-14 14:37:14 [+0100], Juri Lelli wrote:
> Hi,
Hi,
> Now, I'm sending this and an RFC, as I'm wondering if the first behavior
> is actually what we want, and it is not odd at all for reasons that are
> not evident to me at the moment. In this case this posting might also
> function as a q
Document support for ADIS16480 Inertial Measurement Unit.
Signed-off-by: Stefan Popa
---
.../devicetree/bindings/iio/imu/adi,adis16480.txt | 49 ++
MAINTAINERS| 1 +
2 files changed, 50 insertions(+)
create mode 100644 Documentation/
All supported devices provide internal temperature measurement from -40 C
to +85 C, with +25 C representing value 0x00.
This patch treats the temperature scale in a generic way, similar to the
accelerometer and gyroscope scales. So far, there are no temperature max
scale differences between the su
The ADIS16495 and ADIS16497 are inertial systems that include a triaxis
gyroscope and a triaxis accelerometer. The serial peripheral interface
(SPI) provide a simple interface for data collection and configuration
control. The devices are similar to ADIS16475, ADIS16480, ADIS16485 and
ADIS16488, th
The driver does not have a struct of_device_id table, but supported
devices are registered via Device Trees. This patch adds OF device ID
table.
Signed-off-by: Stefan Popa
---
drivers/iio/imu/adis16480.c | 10 ++
1 file changed, 10 insertions(+)
diff --git a/drivers/iio/imu/adis16480.c
The FNCTIO_CTRL register provides configuration control for each I/O pin
(DIO1, DIO2, DIO3 and DIO4).
This patch adds the option to configure each DIOx pin as data ready
indicator with positive or negative polarity by reading the 'interrupts'
and 'interrupt-names' properties from the devicetree. T
The FNCTIO_CTRL register, Bits[3:0] provide three configuration options
for the data ready function: on/off, polarity, and DIOx line. The
factory default assigns DIO2 as a positive polarity, data ready signal.
The adis16480_enable_irq() function, overwrites this configuration when
it enables/disab
This series has as main goal to add support for ADIS1649x family of devices as
part of the already existing adis16480, but on the way it also deals with some
outstanding items:
* Make drdy pin configurable
* Add OF device ID table
* Deal with the temperature max scale in a generic way
* Add missin
On Mon, Feb 18, 2019 at 08:50:25PM -0800, Sowjanya Komatineni wrote:
> multi-master support is defeatured on Tegra210 and Tegra186 due to
> known bugs.
Nit: "Multi-master" because it's the beginning of a sentence.
>
> This patch removes multi-master support for Tegra210 and Tegra186
> i2c hw fea
On Wed, 13 Feb 2019 09:44:45 -0500
Steven Rostedt wrote:
> Reviewed-by: Steven Rostedt (VMware)
>
> Does anyone have any issues or comments about this patch?
I'm going to start pinging people once a week, looking for comments on
this patch ;-)
-- Steve
On Mon, Feb 18, 2019 at 08:50:24PM -0800, Sowjanya Komatineni wrote:
> Tegra186 does not have master fifo control register and instead
> uses fifo control register like prior tegra chipset.
>
> This patch fixes this and prevents crashing during boot when
> accessing fifo control registers.
>
> Si
* Lokesh Vutla [190219 16:19]:
> yes. How different is this from any of the above mentioned drivers using
> firmware specific ids. Like sci pm domain[1] driver utilizes the same
> device id for enabling any device in the system. Similarly clock
> driver[2] uses the same device ids and clock ids sp
Reading from /dev/random may return data while the getrandom
syscall is still blocking.
Those bytes are not yet cryptographically secure.
The first byte from /dev/random can have as little
as 8 bits entropy estimation. Once a read blocks, it will
block until /proc/sys/kernel/random/read_wakeup_t
On 2/19/19 10:29 AM, codrin.ciubota...@microchip.com wrote:
> From: Codrin Ciubotariu
>
> The ADCs are sleeping when the SLEEP bit is set and running when it's
> cleared, so the bit should be inverted.
> Tested on pcm1863.
>
Did this work for you before? Strange it would if reversed, I wonder i
On Tue, Feb 19, 2019 at 05:53:26PM +0100, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> Commit 4c06c4e6cf63 ("driver core: Fix possible supplier PM-usage
> counter imbalance") introduced a regression that causes suppliers
> to be suspended prematurely for device links added during consum
On 2/19/19 10:29 AM, codrin.ciubota...@microchip.com wrote:
> From: Codrin Ciubotariu
>
> According to DS, the gain is between -12 dB and 40 dB, with a 0.5 dB step.
> Tested on pcm1863.
>
> Signed-off-by: Codrin Ciubotariu
> ---
Acked-by: Andrew F. Davis
>
> Changes in v2:
> - fixed title
Hi,
Adding devicetree list, Julia, Rob and Tomi to Cc.
* Peng Hao [190212 23:11]:
> of_find_device_by_node() takes a reference to the struct device
> when it finds a match via get_device.When returning error we should
> call put_device.
>
> Signed-off-by: Peng Hao
> ---
> arch/arm/mach-omap2/
Hi Tom,
the $SUBJECT should be reformatted, please read:
https://www.kernel.org/doc/html/latest/process/submitting-patches.html
Also, while using get_maintainer.pl to derive a sane CC list is good,
it has to be used with some common sense, it is not really needed for
this patch.
There is no nee
Remove the child nodes of the sckc as they are not necessary anymore.
Signed-off-by: Alexandre Belloni
---
arch/arm/boot/dts/at91sam9g45.dtsi | 25 +++--
1 file changed, 3 insertions(+), 22 deletions(-)
diff --git a/arch/arm/boot/dts/at91sam9g45.dtsi
b/arch/arm/boot/dts/at9
Remove the child nodes of the sckc as they are not necessary anymore.
Signed-off-by: Alexandre Belloni
---
arch/arm/boot/dts/at91sam9rl.dtsi | 25 +++--
1 file changed, 3 insertions(+), 22 deletions(-)
diff --git a/arch/arm/boot/dts/at91sam9rl.dtsi
b/arch/arm/boot/dts/at91s
Clang-9 makes some different inlining decisions compared to gcc, which
leads to a warning about a possible stack overflow problem when building
with CONFIG_KASAN, including when setting asan-stack=0, which avoids
most other frame overflow warnings:
drivers/media/platform/vicodec/codec-fwht.c:673:1
The sama5d3 slow RC oscillator as a different startup time than all the
previous SoCs. Handle that using its own compatible.
Signed-off-by: Alexandre Belloni
---
drivers/clk/at91/sckc.c | 17 +++--
1 file changed, 15 insertions(+), 2 deletions(-)
diff --git a/drivers/clk/at91/sckc.c
Remove the child nodes of the sckc as they are not necessary anymore.
Also, switch to the new atmel,sama5d3-sckc compatible string to use the
proper startup time for the RC oscillator (500 µs instead of 75).
Signed-off-by: Alexandre Belloni
---
arch/arm/boot/dts/at91-wb50n.dtsi | 2 +-
arch/ar
clang-8 warns about one function here when KASAN is enabled, even
without the 'asan-stack' option:
drivers/media/usb/go7007/go7007-fw.c:1551:5: warning: stack frame size of 2656
bytes in function
I have reported this issue in the llvm bugzilla, but to make
it work with the clang-8 release, a sma
Two saa7146/hexium files contain a construct that causes a warning
when built with clang:
drivers/media/pci/saa7146/hexium_orion.c:210:12: error: stack frame size of
2272 bytes in function 'hexium_probe'
[-Werror,-Wframe-larger-than=]
static int hexium_probe(struct saa7146_dev *dev)
Remove the child nodes of the sckc as they are not necessary anymore.
Signed-off-by: Alexandre Belloni
---
arch/arm/boot/dts/at91sam9x5.dtsi | 23 +++
1 file changed, 3 insertions(+), 20 deletions(-)
diff --git a/arch/arm/boot/dts/at91sam9x5.dtsi
b/arch/arm/boot/dts/at91sam
Remove the need for child nodes in the sckc binding and register the whole
sckc tree (3 clocks in total) from the sckc node.
DT backward compatibility is kept by looking for properties in child nodes
when they are not present in the sckc node.
Signed-off-by: Alexandre Belloni
---
drivers/clk/at
Remove the need for child nodes in the sckc binding to be able to remove
dtc warnings and have a more modern binding.
Also document optional properties.
Cc: Rob Herring
Signed-off-by: Alexandre Belloni
---
.../devicetree/bindings/clock/at91-clock.txt | 30 ---
1 file changed,
From: Michael Hennerich
Some devices like the ADIS16460 IMU require a stall period between
transfers. The default value of 10us are not enough. Introduce a per
transfer configurable delay.
Signed-off-by: Michael Hennerich
Signed-off-by: Stefan Popa
---
drivers/spi/spi.c | 3 ++-
include
Hi,
This is a rework of the sckc DT bindings to avoid warnings with dtc.
DT backward compatibility is kept.
This series also fix a possible issue with the sama5d3 slow RC
oscillator.
The sckc driver changes and documetation can go through the clk tree and
we will handle th DT changes.
Alexandre
On 2/18/2019 10:40 PM, Len Brown wrote:
From: Len Brown
like core_siblings, except it shows which die are in the same package.
This is needed for lscpu(1) to correctly display die topology.
Signed-off-by: Len Brown
Cc: linux-...@vger.kernel.org
Signed-off-by: Len Brown
---
Documentatio
On Tue, 2019-02-19 at 15:27 +0800, Jason Yan wrote:
> If we remove the scsi disk when running io with fio, oops occured with
> the following condition.
>
> [scsi_eh_0] [fio]
> scsi_end_request
> ->blk_update_request
> ->end_bio(io returned to userspace)
>
David Howells writes:
The container id details are ludicrous and will break practically
every use case. This completely unacceptable.
Nacked-by: "Eric W. Biederman"
> diff --git a/include/linux/container.h b/include/linux/container.h
> new file mode 100644
> index ..0a8918435097
>
On 2/18/19 12:59 AM, Arthur Demchenkov wrote:
> The flags were just read by bq27xxx_battery_update(),
> no need to read them again.
>
> Signed-off-by: Arthur Demchenkov
> ---
Nothing obviously wrong with this patch so:
Reviewed-by: Andrew F. Davis
At this point we have W1 regmap and so we now
On 2/14/19 9:38 PM, Andrew Morton wrote:
> On Thu, 14 Feb 2019 12:45:51 + Peng Fan wrote:
>
>> In case cma_init_reserved_mem failed, need to free the memblock allocated
>> by memblock_reserve or memblock_alloc_range.
>>
>> ...
>>
>> --- a/mm/cma.c
>> +++ b/mm/cma.c
>> @@ -353,12 +353,14 @@ in
On Mon, Feb 18, 2019 at 2:47 AM Minchan Kim wrote:
>
> On Mon, Feb 18, 2019 at 09:32:08AM +0100, Greg KH wrote:
> > On Mon, Feb 18, 2019 at 05:11:45PM +0900, Minchan Kim wrote:
> > > binder has used write-side mmap_sem semaphore to release memory
> > > mapped at address space of the process. Howev
On 02/19/2019 03:13 PM, Alban Crequy wrote:
> From: Alban Crequy
>
> bpftool has support for attach types "stream_verdict" and
> "stream_parser" but the documentation was referring to them as
> "skb_verdict" and "skb_parse". The inconsistency comes from commit
> b7d3826c2ed6 ("bpf: bpftool, add s
On 2/18/19 5:42 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.18.135 release.
There are 108 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.
Responses should be mad
From: Rafael J. Wysocki
Commit 4c06c4e6cf63 ("driver core: Fix possible supplier PM-usage
counter imbalance") introduced a regression that causes suppliers
to be suspended prematurely for device links added during consumer
driver probe if the initial PM-runtime status of the consumer is
"suspende
nck() looks at the last id in an array and unfortunately,
at91sam9x35_periphck has a sentinel, hence the id is 0 and the calculated
number of peripheral clocks is 1 instead of a maximum of 31.
Fixes: 1eabdc2f9dd8 ("clk: at91: add at91sam9x5 PMCs driver")
Signed-off-by: Alexandre Belloni
---
driv
If xace hardware reports a bad version number, the error handling code
in ace_setup() calls put_disk(), followed by queue cleanup. However, since
the disk data structure has the queue pointer set, put_disk() also
cleans and releases the queue. This results in blk_cleanup_queue()
accessing an alread
On 2/18/2019 10:40 PM, Len Brown wrote:
From: Len Brown
Some new systems have multiple software-visible die within each package.
The new CPUID.1F leaf can enumerate this multi-die/package topology.
CPUID.1F a super-set of the CPUID.B "Extended Toplogy Leaf",
and a common updated routine can
On Tue, 19 Feb 2019 16:27:16 +
Marc Zyngier wrote:
> On Tue, 19 Feb 2019 16:57:23 +0100
> Thomas Bogendoerfer wrote:
>
> Hi Thomas,
>
> > When creating hierarchy domains use irq_default_domain as parent, if no
> > parent was given by the caller. This avoids adding helper code for
> > query
On 2/18/19 1:05 PM, Tejun Heo wrote:
On Sat, Feb 16, 2019 at 08:56:04AM +0800, Yang Shi wrote:
Since PSI has implemented some kind of measure of memory pressure, the
statement about lack of such measure is not true anymore.
Cc: Tejun Heo
Cc: Johannes Weiner
Cc: Jonathan Corbet
Signed-off-
On 2/18/19 7:40 PM, Len Brown wrote:
From: Zhang Rui
This patch introduces coretemp driver support
for new dual-die/package systems.
On the new dual-die/package systems, the package temperature MSRs becomes
die-scope. Thus instead of one hwmon device per physical package, now
there should be o
David Howells writes:
> Some filesystem system calls, such as mkdirat(), take a 'directory fd' to
> specify the pathwalk origin. This takes either AT_FDCWD or a file
> descriptor that refers to an open directory.
>
> Make it possible to supply a container fd, as obtained from
> container_create(
Em Tue, Feb 19, 2019 at 04:36:39PM +0100, Thomas Richter escreveu:
> Commit 489338a717a0 ("perf tests evsel-tp-sched: Fix bitwise operator")
> causes test case 14 "Parse sched tracepoints fields" to fail on s390.
> This test succeeds on x86.
> In fact this test now fails on all architectures with t
David Howells writes:
> Provide a system call to open a socket inside of a container, using that
> container's network namespace. This allows netlink to be used to manage
> the container.
>
> fd = container_socket(int container_fd,
> int domain, int type, int pr
On Tue, 19 Feb 2019 at 17:02, Kamil Konieczny
wrote:
>
> Fix bug "s5p-sss crypto driver doesn't set next AES-CBC IV". While at this,
> fix also AES-CTR mode. Tested on Odroid U3 with Eric Biggers branch
> "iv-out-testing".
>
> Signed-off-by: Kamil Konieczny
> Reported-by: Eric Biggers
> ---
> Ch
On 19/02/2019 16:35, Michael S. Tsirkin wrote:
> On Tue, Feb 19, 2019 at 01:57:13PM +, Colin King wrote:
>> From: Colin Ian King
>>
>> Currently the loop that calls log_write_hva on each iovec is never
>> executed because of an incorrect error check on the return from the
>> call to translate_
David Howells writes:
> Allow a single process to be forked directly into a container using a new
> syscall, thereby 'booting' the container:
>
> pid_t pid = fork_into_container(int container_fd);
>
> This process will be the 'init' process of the container.
>
> Further attempts to fork int
On Sun, Feb 17, 2019 at 04:25:10PM +0800, yuank...@codeaurora.org wrote:
> On 2019-02-05 07:30 AM, Luis Chamberlain wrote:
> > On Mon, Jan 14, 2019 at 05:58:30PM +0800, yuank...@codeaurora.org wrote:
> > > Hi,
> > >
> > > Refined at below.
> > >
> > > From bbd0d9c8f28eb78ca34353347c3d4092e88f
On Tue, Feb 19, 2019 at 05:22:50PM +0100 Peter Zijlstra wrote:
> On Tue, Feb 19, 2019 at 11:13:43AM -0500, Phil Auld wrote:
> > On Mon, Feb 18, 2019 at 05:56:23PM +0100 Peter Zijlstra wrote:
> > > In preparation of playing games with rq->lock, abstract the thing
> > > using an accessor.
> > >
> >
On Tue, Feb 19, 2019 at 11:02:41AM -0500, Mathieu Desnoyers wrote:
> - On Feb 18, 2019, at 4:55 PM, Rich Felker dal...@libc.org wrote:
>
> > On Mon, Feb 18, 2019 at 10:22:32AM -0500, Mathieu Desnoyers wrote:
> >> - On Feb 17, 2019, at 5:08 PM, Rich Felker dal...@libc.org wrote:
> >>
> >>
On Tue, Feb 19, 2019 at 01:57:13PM +, Colin King wrote:
> From: Colin Ian King
>
> Currently the loop that calls log_write_hva on each iovec is never
> executed because of an incorrect error check on the return from the
> call to translate_desc. The check should be checking for a -ve error
>
wt., 19 lut 2019 o 17:14 Marc Zyngier napisał(a):
>
> On Tue, 19 Feb 2019 17:06:44 +0100
> Bartosz Golaszewski wrote:
>
> > From: Bartosz Golaszewski
> >
> > Implement the irq_set_type() callback and call irqd_set_trigger_type()
> > internally so that users interested in the configured trigger t
So you missed the main mailing lists for discussion of this kind of
thing, and the maintainer. So I have reservations about the quality of
your due diligence already.
Looking at your description you are introducing a container id.
You don't descibe which namespace your contianer id lives in.
Wi
On Tue, Feb 19, 2019 at 12:35:32PM +0200, Jarkko Sakkinen wrote:
> On Tue, Feb 19, 2019 at 05:15:47PM +0800, YueHaibing wrote:
> > On 2019/2/19 16:59, Jarkko Sakkinen wrote:
> > > On Tue, Feb 19, 2019 at 03:26:18PM +0800, YueHaibing wrote:
> > >> calc_tpm2_event_size return size of the event which
From: Codrin Ciubotariu
The ADCs are sleeping when the SLEEP bit is set and running when it's
cleared, so the bit should be inverted.
Tested on pcm1863.
Signed-off-by: Codrin Ciubotariu
---
Changes in v2:
- none;
sound/soc/codecs/pcm186x.c | 6 +++---
1 file changed, 3 insertions(+), 3 dele
On 11/28/18 6:15 PM, Darren Hart wrote:
> On Thu, Jul 05, 2018 at 03:38:07PM -0500, Gustavo A. R. Silva wrote:
>> In preparation to enabling -Wimplicit-fallthrough, mark switch cases
>> where we are expecting to fall through.
>>
>> Signed-off-by: Gustavo A. R. Silva
>
> I've applied this patch
From: Codrin Ciubotariu
According to DS, the gain is between -12 dB and 40 dB, with a 0.5 dB step.
Tested on pcm1863.
Signed-off-by: Codrin Ciubotariu
---
Changes in v2:
- fixed title - added correct macro;
- revert the removal of a new line;
sound/soc/codecs/pcm186x.c | 2 +-
1 file chang
Immediate data transfers (IDT) allow the HCD to copy small chunks of
data (up to 8bytes) directly into its output transfer TRBs. This avoids
the somewhat expensive DMA mappings that are performed by default on
most URBs submissions.
In the case an URB was suitable for IDT. The data is directly cop
On 2019-02-19 17:27:41 [+0100], Juri Lelli wrote:
> It is better. Warning message doesn't appear anymore.
Okay, thanks.
Sebastian
On Sun, 2019-02-17 at 21:11 +0800, Ming Lei wrote:
> The following patch should fix this issue:
>
>
> diff --git a/block/blk-merge.c b/block/blk-merge.c
> index bed065904677..066b66430523 100644
> --- a/block/blk-merge.c
> +++ b/block/blk-merge.c
> @@ -363,13 +363,15 @@ static unsigned int __blk_
On 19/02/19 17:06, Sebastian Andrzej Siewior wrote:
> On 2019-02-19 15:58:26 [+0100], Juri Lelli wrote:
> > Hi,
> Hi,
>
> > I've been seeing those messages while running some stress tests (hog
> > tasks pinned to CPUs).
> >
> > Have yet to see them after I applied this patch earlier this morning
On Tue, 19 Feb 2019 16:57:23 +0100
Thomas Bogendoerfer wrote:
Hi Thomas,
> When creating hierarchy domains use irq_default_domain as parent, if no
> parent was given by the caller. This avoids adding helper code for
> querying the underlying platform irq domain.
>
> Signed-off-by: Thomas Bogend
On Tue, Feb 19, 2019 at 01:37:57PM +0100, Oleg Nesterov wrote:
> On 02/18, Guenter Roeck wrote:
> >
> > Unfortunately, this patch causes one of my qemu emulations to crash.
> > The crash is not always seen, but at least with every other boot attempt.
>
> Hmm. I can't imagine how this change can ca
From: Codrin Ciubotariu
The ADCs are sleeping when the SLEEP bit is set and running when it's
cleared, so the bit should be inverted.
Tested on pcm1863.
Signed-off-by: Codrin Ciubotariu
---
sound/soc/codecs/pcm186x.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/sou
On Mon, Feb 18, 2019 at 6:46 PM Andrea Arcangeli wrote:
>
> Hello,
>
> On Mon, Feb 18, 2019 at 03:47:22PM -0800, Alexander Duyck wrote:
> > essentially fragmented them. I guess hugepaged went through and
> > started trying to reassemble the huge pages and as a result there have
> > been apps that
From: Codrin Ciubotariu
According to DS, the gain is between -12 dB and 40 dB, with a 0.5 dB step.
Tested on pcm1863.
Signed-off-by: Codrin Ciubotariu
---
sound/soc/codecs/pcm186x.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/sound/soc/codecs/pcm186x.c b/sound/soc/cod
On Tue, Feb 19, 2019 at 11:13:43AM -0500, Phil Auld wrote:
> On Mon, Feb 18, 2019 at 05:56:23PM +0100 Peter Zijlstra wrote:
> > In preparation of playing games with rq->lock, abstract the thing
> > using an accessor.
> >
> > Signed-off-by: Peter Zijlstra (Intel)
>
> Hi Peter,
>
> Sorry... what
On Thu, Feb 14, 2019 at 11:20:36PM +0800, Ley Foon Tan wrote:
> Add PCIe Root Port support for Stratix 10 device.
>
> Main differences:
Main differences with what ? We need to rewrite this commit log.
> - HIP interface to access Root Port configuration register.
> - TLP programming flow:
> - O
On 19.02.2019 18:15, Codrin Ciubotariu - M19940 wrote:
> From: Codrin Ciubotariu
>
> According to DS, the gain is between -12 dB and 40 dB, with a 0.5 dB step.
> Tested on pcm1863.
>
> Signed-off-by: Codrin Ciubotariu
> ---
> sound/soc/codecs/pcm186x.c | 3 +--
> 1 file changed, 1 insertion(
This patch adds driver for Cadence HPNFC NAND controller.
Signed-off-by: Piotr Sroka
---
Changes for v2:
- create one universal wait function for all events instead of one
function per event.
- split one big function executing nand operations to separate
functions one per each type of operati
Signed-off-by: Piotr Sroka
---
Changes for v2:
- remove chip dependends parameters from dts bindings
- add names for register ranges in dts bindings
- add generic bindings to describe NAND chip representation
under the NAND controller node
---
.../bindings/mtd/cadence-nand-controller.txt
On 2/19/2019 9:05 PM, Tony Lindgren wrote:
> * Lokesh Vutla [190219 08:51]:
>> Hi Tony,
>>
>> On 18/02/19 8:02 PM, Tony Lindgren wrote:
>>> * Lokesh Vutla [190216 03:30]:
On 2/15/2019 9:46 PM, Tony Lindgren wrote:
> The dts node for the interrupt controller should describe a
> pro
[ Added Masami too. Start of thread is here:
http://lkml.kernel.org/r/20190215174712.372898...@goodmis.org ]
On Mon, 18 Feb 2019 10:23:44 -0800
Linus Torvalds wrote:
> So it would be good to not just say "user or kernel", but actually say
> what *kind* of kernel access it expects.
Note, kpr
501 - 600 of 1032 matches
Mail list logo
