As we now have the 'priv' pointer in most of the places we can use
priv->lock directly, dropping extra indirection in the SFR region
spinlock access.
Signed-off-by: Sylwester Nawrocki
Acked-by: Krzysztof Kozlowski
---
sound/soc/samsung/i2s.c | 51 +++--
1
There is now no users of this flag so remove it together with related
data structure field.
Signed-off-by: Sylwester Nawrocki
Acked-by: Krzysztof Kozlowski
---
include/sound/dmaengine_pcm.h | 6 --
sound/soc/soc-generic-dmaengine-pcm.c | 21 -
2 files changed,
Spelling error fixes, upper/lower case letter changes.
Signed-off-by: Sylwester Nawrocki
---
sound/soc/samsung/i2s.c | 29 +++--
1 file changed, 15 insertions(+), 14 deletions(-)
diff --git a/sound/soc/samsung/i2s.c b/sound/soc/samsung/i2s.c
index
This patch extends DAPM routing and adds secondary CPU DAI entry
to support the secondary audio PCM interface on Odroid XU4.
Signed-off-by: Sylwester Nawrocki
---
arch/arm/boot/dts/exynos5422-odroidxu4.dts | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git
If the probe call is on the primary DAI we can use 'other' in place of
i2s->sec_dai, if the probe call is on the secondary DAI we can use 'i2s'
in place of other->sec_dai.
While at it fix one whitespace issue.
Signed-off-by: Sylwester Nawrocki
---
sound/soc/samsung/i2s.c | 7 +++
1 file
Adds test for stack initialization coverage. We have several build options
that control the level of stack variable initialization. This test lets us
visualize which options cover which cases, and provide tests for some of
the pathological padding conditions the compiler will sometimes fail to
This patch adds DAPM widgets required to model the internal mixer
of the I2S controller merging audio streams from the primary and
from the secondary PCM interface.
Signed-off-by: Sylwester Nawrocki
Acked-by: Krzysztof Kozlowski
---
sound/soc/samsung/i2s.c | 27 ++-
1
This patch adds DPCM links in order to support the secondary I2S interface.
For the secondary PCM interface to be actually available one more entry
should be added to the sound-dai property in sound/cpu node in DT.
The changes in driver are done in a way so we are backwards compatible with
The core clock is also common for both CPU DAIs so move it to
the driver's private data structure.
Signed-off-by: Sylwester Nawrocki
Acked-by: Krzysztof Kozlowski
---
sound/soc/samsung/i2s.c | 27 ++-
1 file changed, 14 insertions(+), 13 deletions(-)
diff --git
This patch extends DAPM routing and adds secondary CPU DAI entry
to support the secondary audio PCM interface on Odroid XU3.
Signed-off-by: Sylwester Nawrocki
---
arch/arm/boot/dts/exynos5422-odroidxu3-audio.dtsi | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git
Change indentation so this macro definition spans 2 rows and looks
more consistent with surrounding code.
Signed-off-by: Sylwester Nawrocki
---
sound/soc/samsung/i2s.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/sound/soc/samsung/i2s.c b/sound/soc/samsung/i2s.c
Replace GPL v2.0 license statements with SPDX license identifier.
Signed-off-by: Sylwester Nawrocki
---
sound/soc/samsung/i2s.c | 16 ++--
1 file changed, 6 insertions(+), 10 deletions(-)
diff --git a/sound/soc/samsung/i2s.c b/sound/soc/samsung/i2s.c
index
Here is the detailed description for memrchr:
https://linux.die.net/man/3/memrchr
Signed-off-by: Xiang Xiao
---
include/linux/string.h | 1 +
lib/string.c | 21 +
2 files changed, 22 insertions(+)
diff --git a/include/linux/string.h b/include/linux/string.h
index
On Tue, Feb 12, 2019 at 6:49 PM Sudeep Holla wrote:
>
> On Mon, Feb 11, 2019 at 05:20:20PM +0100, Ulf Hansson wrote:
> > On Thu, 7 Feb 2019 at 16:29, Sudeep Holla wrote:
> > >
> > > On Thu, Feb 07, 2019 at 04:18:57PM +0100, Ulf Hansson wrote:
> > > > On Thu, 7 Feb 2019 at 16:06, Sudeep Holla
Add missing break statement in order to prevent the code from falling
through to the default case and return -EINVAL every time.
This bug was found thanks to the ongoing efforts to enable
-Wimplicit-fallthrough.
Fixes: 58dd7c0a2a6e ("Staging: comedi: add ni_660x driver")
Cc:
Because log may already add the timestamp sometime
Signed-off-by: Xiang Xiao
---
include/linux/kern_levels.h | 2 ++
include/linux/printk.h | 1 +
kernel/printk/printk.c | 7 ++-
3 files changed, 9 insertions(+), 1 deletion(-)
diff --git a/include/linux/kern_levels.h
On Tue 2019-02-12 11:50:36, Sasha Levin wrote:
> On Mon, Feb 11, 2019 at 09:51:25PM +0100, Pavel Machek wrote:
> >Hi!
> >
> >>4.9-stable review patch. If anyone has any objections, please let me know.
> >>
> >>--
> >>
> >>[ Upstream commit f36797ee43802b367e59f0f9a9805304a4ff0c98
n preparation to enabling -Wimplicit-fallthrough, mark switch
cases where we are expecting to fall through.
This patch fixes the following warning:
drivers/rapidio/devices/rio_mport_cdev.c: In function ‘mport_release_mapping’:
drivers/rapidio/devices/rio_mport_cdev.c:2151:3: warning: this
On Tue, Feb 05, 2019 at 10:27:00AM +0530, Srinath Mannam wrote:
> In the current implementation, config read output data 0x0001 is
> assumed as CRS completion. But sometimes 0x0001 can be a valid data.
>
> IPROC PCIe host controller has a register to show config read request
> status
On 2/12/19 17:40, Mark Brown wrote:
> On Thu, Feb 07, 2019 at 06:00:08PM +0100, Sylwester Nawrocki wrote:
>
>> I am not entirely sure we should be removing the
>> SND_DMAENGINE_PCM_FLAG_CUSTOM_CHANNEL_NAME flag like this, it might all
>> be a bit more explicit with the flag.
>
> I'm fairly happy
On Tue, Feb 12, 2019 at 07:07:31PM +0100, Rafael J. Wysocki wrote:
> On Tue, Feb 12, 2019 at 6:49 PM Sudeep Holla wrote:
> >
> > On Mon, Feb 11, 2019 at 05:20:20PM +0100, Ulf Hansson wrote:
> > > On Thu, 7 Feb 2019 at 16:29, Sudeep Holla wrote:
> > > >
> > > > On Thu, Feb 07, 2019 at 04:18:57PM
On 2/9/19 3:00 AM, Brice Goglin wrote:
> I've used your patches on fake hardware (memmap=xx!yy) with an older
> nvdimm-pending branch (without Keith's patches). It worked fine. This
> time I am running on real Intel hardware. Any idea where to look ?
I've run them on real Intel hardware too.
To avoid potential confusion, explicitly ignore "security=" when "lsm=" is
used on the command line, and report that it is happening.
Suggested-by: Tetsuo Handa
Signed-off-by: Kees Cook
---
Documentation/admin-guide/kernel-parameters.txt | 10 --
security/security.c
> On Feb 11, 2019, at 2:47 PM, Andy Lutomirski wrote:
>
> On Mon, Feb 11, 2019 at 11:18 AM Nadav Amit wrote:
>>
>> +
>> + /*
>> +* If breakpoints are enabled, disable them while the temporary mm is
>> +* used - they do not belong and might cause wrong signals or
>>
(cc-ing Paul Hardwick, mentioned as maintainer of the driver)
Hi,
> > there's still something unclear to me about dc->card_type being used as
> > size argument to ioremap_nocache().
> >
> > dc->base_addr is the sum of all six io region lengths, not the size of
> > region 0 which we are trying
On Mon, Feb 11, 2019 at 4:59 PM Tetsuo Handa
wrote:
> Kees Cook wrote:
> > On Mon, Feb 11, 2019 at 4:21 PM Tetsuo Handa
> > wrote:
> > >
> > > Kees Cook wrote:
> > > > To avoid potential confusion, explicitly ignore "security=" when "lsm="
> > > > is
> > > > used on the command line, and report
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.
This patch sorts all the include headers alphabetically for the
I2C Tegra driver.
Acked-by: Thierry Reding
Reviewed-by: Dmitry Osipenko
Signed-off-by: Sowjanya Komatineni
---
[V9/V10/V11/V12/V13/V14/V15/V16/V17/V18/V19] : Rebased to 5.0-rc4
[V3/V4/V5/V7/V8] : Removed unsued headers in tegra
This patch sorts all the include headers alphabetically for the
I2C Tegra driver.
Acked-by: Thierry Reding
Reviewed-by: Dmitry Osipenko
Signed-off-by: Sowjanya Komatineni
---
[V9/V10/V11/V12/V13/V14/V15/V16/V17/V18/V19] : Rebased to 5.0-rc4
[V3/V4/V5/V7/V8] : Removed unsued headers in tegra
On Tue, 12 Feb 2019 at 17:28, Rafael J. Wysocki wrote:
>
> On Tue, Feb 12, 2019 at 5:18 PM Ulf Hansson wrote:
> >
> > On Tue, 12 Feb 2019 at 13:10, Rafael J. Wysocki wrote:
> > >
> > > From: Rafael J. Wysocki
> > >
> > > Commit 4080ab083000 ("PM-runtime: Take suppliers into account in
> > >
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: Frederic Weisbecker
Date: Tue, 12 Feb 2019 18:13:51 +0100
> For those who missed the infinitely invasive and carpal tunnel
> unfriendly v1: https://lwn.net/Articles/768157/
>
> Softirqs masking is an all or nothing operation. It's currently not
> possible to disable a single vector. Yet
From: "Gustavo A. R. Silva"
Date: Mon, 11 Feb 2019 16:34:44 -0600
> In preparation to enabling -Wimplicit-fallthrough, mark switch
> cases where we are expecting to fall through.
>
> This patch fixes the following warning:
>
> drivers/isdn/gigaset/ser-gigaset.c: In function
From: "Gustavo A. R. Silva"
Date: Mon, 11 Feb 2019 16:42:37 -0600
> In preparation to enabling -Wimplicit-fallthrough, mark switch
> cases where we are expecting to fall through.
>
> This patch fixes the following warnings:
>
> drivers/isdn/i4l/isdn_v110.c: In function ‘EncodeMatrix’:
>
From: "Gustavo A. R. Silva"
Date: Mon, 11 Feb 2019 16:38:21 -0600
> In preparation to enabling -Wimplicit-fallthrough, mark switch
> cases where we are expecting to fall through.
>
> This patch fixes the following warnings:
>
> drivers/isdn/i4l/isdn_tty.c: In function ‘isdn_tty_edit_at’:
>
Please ignore all Patch V19 series. Will resend.
Dmitry/Thierry
I am using below stable tags in commit message based on V18 feedback to get
patch applied to old kernels
Git send email considers whole text after Cc as email address and reports badly
formatted address.
Is there any format that I
On Tue, Feb 12, 2019 at 08:40:03AM -0700, shuah wrote:
> On 2/11/19 7:13 AM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.20.8 release.
> > There are 352 patches in this series, all will be posted as a response
> > to this one. If anyone has any issues with
On Tue, Feb 12, 2019 at 11:41:35PM +0800, cgxu519 wrote:
> On 2/12/19 11:20 PM, Greg KH wrote:
> > On Tue, Feb 12, 2019 at 11:18:22PM +0800, cgxu519 wrote:
> > > On 2/12/19 5:02 PM, Greg KH wrote:
> > > > On Tue, Feb 12, 2019 at 04:47:39PM +0800, Chengguang Xu wrote:
> > > > > Currently chardev
On Wed, Feb 13, 2019 at 02:06:49AM +0800, Xiang Xiao wrote:
> Here is the detailed description for memrchr:
> https://linux.die.net/man/3/memrchr
Please put it in the changelog, as web pages move and go away :(
>
> Signed-off-by: Xiang Xiao
> ---
> include/linux/string.h | 1 +
>
On Tue, Feb 12, 2019 at 06:49:42PM +0100, Lukas Wunner wrote:
> On Wed, Feb 06, 2019 at 04:17:26PM +0300, Mika Westerberg wrote:
> > /* dword 0 */
> > hop.next_hop = path->hops[i].next_hop_index;
> > hop.out_port = path->hops[i].out_port->port;
> > -
atch
https://lore.kernel.org/lkml/20170126115819.58875-2-kirill.shute...@linux.intel.com/
Signed-off-by: Matthew Wilcox
---
v2: Rebase on top of linux-next 20190212
Fixed a missing s/head/page/ in filemap_map_pages
Include missing calls to xas_store() in __split_huge_page
include/linux/page
On 02/12/2019 08:25 AM, Peter Zijlstra wrote:
> On Tue, Feb 12, 2019 at 02:24:04PM +0100, Peter Zijlstra wrote:
>> On Mon, Feb 11, 2019 at 02:31:26PM -0500, Waiman Long wrote:
>>> Modify __down_read_trylock() to make it generate slightly better code
>>> (smaller and maybe a tiny bit faster).
>>>
From: Konstantin Khlebnikov
Date: Sat, 09 Feb 2019 13:35:52 +0300
> Field idiag_ext in struct inet_diag_req_v2 used as bitmap of requested
> extensions has only 8 bits. Thus extensions starting from DCTCPINFO
> cannot be requested directly. Some of them included into response
> unconditionally
On Tue, Feb 12, 2019 at 08:41:50AM -0800, Guenter Roeck wrote:
> On 2/11/19 6:13 AM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.20.8 release.
> > There are 352 patches in this series, all will be posted as a response
> > to this one. If anyone has any
On Tue, Feb 05, 2019 at 10:27:01AM +0530, Srinath Mannam wrote:
> Add configuration to support IPROC PCIe host controller outbound memory
> window mapping with SOC address range inside 4GB boundary, which is 32 bit
> AXI address.
I do not understand what this means, explain it to me and rewrite
From: Kal Conley
Date: Sun, 10 Feb 2019 09:57:11 +0100
> When calculating rb->frames_per_block * req->tp_block_nr the result
> can overflow. Check it for overflow without limiting the total buffer
> size to UINT_MAX.
>
> This change fixes support for packet ring buffers >= UINT_MAX.
>
> Fixes:
On 02/12/2019 01:36 PM, Waiman Long wrote:
> On 02/12/2019 08:25 AM, Peter Zijlstra wrote:
>> On Tue, Feb 12, 2019 at 02:24:04PM +0100, Peter Zijlstra wrote:
>>> On Mon, Feb 11, 2019 at 02:31:26PM -0500, Waiman Long wrote:
Modify __down_read_trylock() to make it generate slightly better code
On Tue, Feb 12, 2019 at 09:55:11PM +0530, Naresh Kamboju wrote:
> On Mon, 11 Feb 2019 at 19:51, Greg Kroah-Hartman
> wrote:
> >
> > This is the start of the stable review cycle for the 4.20.8 release.
> > There are 352 patches in this series, all will be posted as a response
> > to this one. If
On Tue, Feb 12, 2019 at 10:19:57AM +, Jon Hunter wrote:
>
> On 11/02/2019 14:16, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.14.99 release.
> > There are 205 patches in this series, all will be posted as a response
> > to this one. If anyone has any
* Christoph Hellwig [190212 07:27]:
> Instead of setting up a kernel pointer to track the current PIO address,
> track the offset in the current page, and do an atomic kmap for the page
> while doing the actual PIO operations.
I'm currently having issues booting my test devices (770 and n8x0)
On Mon, 11 Feb 2019 18:11:53 -0500
Daniel Jordan wrote:
> On Mon, Feb 11, 2019 at 03:56:20PM -0700, Jason Gunthorpe wrote:
> > On Mon, Feb 11, 2019 at 05:44:33PM -0500, Daniel Jordan wrote:
> > > @@ -266,24 +267,15 @@ static int vfio_lock_acct(struct vfio_dma *dma,
> > > long npage, bool
12.02.2019 21:32, Sowjanya Komatineni пишет:
> Please ignore all Patch V19 series. Will resend.
>
> Dmitry/Thierry
> I am using below stable tags in commit message based on V18 feedback to get
> patch applied to old kernels
> Git send email considers whole text after Cc as email address and
On Mon, Feb 11, 2019 at 12:22:18PM -0800, Paul E. McKenney wrote:
> On Mon, Feb 11, 2019 at 05:29:48PM +, Will Deacon wrote:
> > The "KERNEL I/O BARRIER EFFECTS" section of memory-barriers.txt is vague,
> > x86-centric, out-of-date, incomplete and demonstrably incorrect in places.
> > This is
On Tue, Feb 12, 2019 at 03:53:21PM +0530, Anup Patel wrote:
> If it is initramfs (i.e. CPIO image) then contents of CPIO archive
> are extracted to create a ramfs instance.
>
> If it is initrd (i.e. some filesystem image) then RAM block device
> is created in-place at initrd location. (Please
Add missing break statement in order to prevent the code from falling
through to the default case and return -EINVAL every time.
This bug was found thanks to the ongoing efforts to enable
-Wimplicit-fallthrough.
Fixes: aa94f225 ("staging: comedi: ni_660x: tidy up
ni_660x_set_pfi_routing()")
> 12.02.2019 21:32, Sowjanya Komatineni пишет:
> > Please ignore all Patch V19 series. Will resend.
> >
> > Dmitry/Thierry
> > I am using below stable tags in commit message based on V18 feedback
> > to get patch applied to old kernels Git send email considers whole text
> > after Cc as email
On Mon, Feb 11, 2019 at 02:46:42PM +0100, Christoph Hellwig wrote:
> As far as I can tell IBFT is a firmware table and has nothing to do with
> the good old ISA bus. And even if it the two would be the same on x86
> anyway. So remove the isa_virt_to_bus call in preparation of eventually
>
Hi,
Please, drop this.
I've just sent v2 with the right Fixes tag:
https://lore.kernel.org/patchwork/patch/1041301/
Thanks
--
Gustavo
On 2/12/19 12:08 PM, Gustavo A. R. Silva wrote:
> Add missing break statement in order to prevent the code from falling
> through to the default case and
On Mon, Feb 11, 2019 at 12:43:23PM -0600, Gustavo A. R. Silva wrote:
> Add missing break statement in order to prevent the code from falling
> through to case ISCSI_BOOT_TGT_NAME, which is unnecessary.
>
> This bug was found thanks to the ongoing efforts to enable
> -Wimplicit-fallthrough.
>
>
On Tue, Feb 12, 2019 at 03:04:22PM +0100, Lukas Wunner wrote:
> On Wed, Feb 06, 2019 at 04:17:28PM +0300, Mika Westerberg wrote:
> > The only way to expand Thunderbolt topology is through the NULL adapter
> > ports (typically ports 1, 2, 3 and 4). There is no point handling
> > Thunderbolt hotplug
On Fri, Jan 18, 2019 at 03:10:26PM +0800, Dongli Zhang wrote:
> Fix the comment as swiotlb_bounce() is used to copy from original dma
> location to swiotlb buffer during swiotlb_tbl_map_single(), while to
> copy from swiotlb buffer to original dma location during
> swiotlb_tbl_unmap_single().
I
On Tue, Feb 12, 2019 at 09:56:45AM -0800, Roman Gushchin wrote:
> The patchset contains few changes to the vmalloc code, which are
> leading to some performance gains and code simplification.
>
> Also, it exports a number of pages, used by vmalloc(),
> in /proc/meminfo.
>
> Patch (1) removes
Freezer.c will contain an implementation of cgroup v2 freezer,
so let's rename the v1 freezer to avoid naming conflicts.
Signed-off-by: Roman Gushchin
Cc: Tejun Heo
Cc: kernel-t...@fb.com
---
kernel/cgroup/Makefile| 2 +-
kernel/cgroup/{freezer.c => legacy_freezer.c} |
Cgroup v1 implements the freezer controller, which provides an ability
to stop the workload in a cgroup and temporarily free up some
resources (cpu, io, network bandwidth and, potentially, memory)
for some other tasks. Cgroup v2 lacks this functionality.
This patch implements freezer for cgroup
The number of descendant cgroups and the number of dying
descendant cgroups are currently synchronized using the cgroup_mutex.
The number of descendant cgroups will be required by the cgroup v2
freezer, which will use it to determine if a cgroup is frozen
(depending on total number of descendants
This patch implements 8 tests for the freezer controller for
cgroup v2:
1) a simple test, which aims to freeze and unfreeze a cgroup with 100
processes
2) a more complicated tree test, which creates a hierarchy of cgroups,
puts some processes in some cgroups, and tries to freeze and unfreeze
Describe cgroup v2 freezer interface in the cgroup v2 admin guide.
Signed-off-by: Roman Gushchin
Reviewed-by: Mike Rapoport
Cc: Tejun Heo
Cc: linux-...@vger.kernel.org
Cc: kernel-t...@fb.com
---
Documentation/admin-guide/cgroup-v2.rst | 27 +
1 file changed, 27
The helper is identical to the existing cgroup_task_count()
except it doesn't take the css_set_lock by itself, assuming
that the caller does.
Also, move cgroup_task_count() implementation into
kernel/cgroup/cgroup.c, as there is nothing specific to cgroup v1.
Signed-off-by: Roman Gushchin
Cc:
If the cgroup destruction races with an exit() of a belonging
process(es), cg_kill_all() may fail. It's not a good reason to make
cg_destroy() fail and leave the cgroup in place, potentially causing
next test runs to fail.
Signed-off-by: Roman Gushchin
Cc: Shuah Khan
Cc: Tejun Heo
Cc:
This patchset implements freezer for cgroup v2.
It provides similar functionality as v1 freezer, but the interface
conforms to the cgroup v2 interface design principles, and it
provides a better user experience: tasks can be killed, ptrace works,
there is no separate controller, which has to be
Hi,
* Martyn Welch [190211 04:27]:
> The Bosch Guardian is a TI am335x based device.
>
> It's hardware specifications are as follows:
>
> * 256 MB DDR3 memory
> * 512 MB NAND Flash
> * USB OTG
> * RS232
> * MicroSD external storage
> * LCD Display interface
Thanks applying into
On 2/12/19 12:46 PM, Konrad Rzeszutek Wilk wrote:
> On Mon, Feb 11, 2019 at 12:43:23PM -0600, Gustavo A. R. Silva wrote:
>> Add missing break statement in order to prevent the code from falling
>> through to case ISCSI_BOOT_TGT_NAME, which is unnecessary.
>>
>> This bug was found thanks to the
Hello,
syzbot found the following crash on:
HEAD commit:aa0c38cf39de Merge branch 'fixes' of git://git.kernel.org/..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1460eca740
kernel config: https://syzkaller.appspot.com/x/.config?x=ee434566c893c7b1
This patch set unflattens device trees when running DT's unittest. It is
a follow up to
https://www.spinics.net/lists/linux-kselftest/msg05454.html part of the
KUnit RFC v3 thread
(https://www.spinics.net/lists/linux-kselftest/msg05431.html). Rob asked
me to submit this patch separately along with
UML supports enabling OF, and is useful for running the device tree
tests, so add support for unflattening device tree blobs so we can
actually use it.
Signed-off-by: Brendan Higgins
---
drivers/of/unittest.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/of/unittest.c
Here is the detailed description for memrchr:
void *memrchr(const void *s, int c, size_t n);
The memrchr() function is like the memchr() function, except
that it searches backward from the end of the n bytes pointed
to by s instead of forward from the beginning.
The memrchr() functions return a
On Tue, 12 Feb 2019 17:56:18 +1100
Alexey Kardashevskiy wrote:
> On 12/02/2019 09:44, Daniel Jordan wrote:
> > Beginning with bc3e53f682d9 ("mm: distinguish between mlocked and pinned
> > pages"), locked and pinned pages are accounted separately. The SPAPR
> > TCE VFIO IOMMU driver accounts
On Mon, Feb 11, 2019 at 11:41 PM Krzysztof Kozlowski wrote:
>
> On Mon, 11 Feb 2019 at 19:40, Gustavo A. R. Silva
> wrote:
> >
> > In preparation to enabling -Wimplicit-fallthrough, mark switch
> > cases where we are expecting to fall through.
> >
> > This patch fixes the following warnings:
> >
On Tue, Feb 12, 2019 at 09:26:48PM +0530, Aneesh Kumar K.V wrote:
> Vivek Goyal writes:
>
> > Hi,
> >
> > Here are RFC patches for virtio-fs. Looking for feedback on this approach.
> >
> > These patches should apply on top of 4.20-rc5. We have also put code for
> > various components here.
> >
>
On Tue, Feb 12, 2019 at 7:20 PM Sudeep Holla wrote:
>
> On Tue, Feb 12, 2019 at 07:07:31PM +0100, Rafael J. Wysocki wrote:
> > On Tue, Feb 12, 2019 at 6:49 PM Sudeep Holla wrote:
> > >
> > > On Mon, Feb 11, 2019 at 05:20:20PM +0100, Ulf Hansson wrote:
> > > > On Thu, 7 Feb 2019 at 16:29, Sudeep
From: Maxime Chevallier
Date: Mon, 11 Feb 2019 15:25:25 +0100
> The 802.3bz standard defines 2 modes based on the NBASET alliance work
> that allow to use 2.5Gbps and 5Gbps speeds on Cat 5e, 6 and 7 cables.
>
> This series adds the necessary infrastructure to handle these modes with
> C45 PHYs.
On Tue, Feb 12, 2019 at 02:55:42PM +0100, Lukas Wunner wrote:
> On Mon, Feb 11, 2019 at 11:54:36AM +0200, Mika Westerberg wrote:
> > On Mon, Feb 11, 2019 at 07:16:00AM +0100, Lukas Wunner wrote:
> > > On Wed, Feb 06, 2019 at 04:17:23PM +0300, Mika Westerberg wrote:
> > > > +/**
> > > > + *
Hello,
syzbot found the following crash on:
HEAD commit:d4104460aec1 Add linux-next specific files for 20190211
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=14140124c0
kernel config: https://syzkaller.appspot.com/x/.config?x=c8a112d3b0d6719b
Hello,
syzbot found the following crash on:
HEAD commit:b5829453d81a Add linux-next specific files for 20190212
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1662de24c0
kernel config: https://syzkaller.appspot.com/x/.config?x=4085ec231ef9027d
On Tue, Feb 12, 2019 at 7:28 PM Ulf Hansson wrote:
>
> On Tue, 12 Feb 2019 at 17:28, Rafael J. Wysocki wrote:
> >
> > On Tue, Feb 12, 2019 at 5:18 PM Ulf Hansson wrote:
> > >
> > > On Tue, 12 Feb 2019 at 13:10, Rafael J. Wysocki
> > > wrote:
> > > >
> > > > From: Rafael J. Wysocki
> > > >
>
Tegra186 and prior supports maximum 4K bytes per packet transfer
including 12 bytes of packet header.
This patch fixes max write length limit to account packet header
size for transfers.
Cc: sta...@vger.kernel.org # 4.4+
Reviewed-by: Dmitry Osipenko
Signed-off-by: Sowjanya Komatineni
---
Tegra194 allows max of 64K bytes and Tegra186 and prior allows
max of 4K bytes of transfer per packet.
one sec timeout is not enough for transfers more than 10K bytes
at STD bus rate.
This patch updates I2C transfer timeout based on the transfer size
and I2C bus rate to allow enough time during
This patch adds DMA support for Tegra I2C.
Tegra I2C TX and RX FIFO depth is 8 words. PIO mode is used for
transfer size of the max FIFO depth and DMA mode is used for
transfer size higher than max FIFO depth to save CPU overhead.
PIO mode needs full intervention of CPU to fill or empty FIFO's
This patch sorts all the include headers alphabetically for the
I2C Tegra driver.
Acked-by: Thierry Reding
Reviewed-by: Dmitry Osipenko
Signed-off-by: Sowjanya Komatineni
---
[V9/V10/V11/V12/V13/V14/V15/V16/V17/V18/V19] : Rebased to 5.0-rc4
[V3/V4/V5/V7/V8] : Removed unsued headers in tegra
This patch adds I2C interface timing registers support for
proper bus rate configuration along with meeting the I2C spec
setup and hold times based on the tuning performed on Tegra210,
Tegra186 and Tegra194 platforms.
I2C_INTERFACE_TIMING_0 register contains TLOW and THIGH field
and Tegra I2C
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.
On 12.02.2019 12:33, Lorenzo Pieralisi wrote:
> On Tue, Feb 12, 2019 at 09:54:54AM +0100, Lucas Stach wrote:
>> Hi Bjorn,
>>
>> Am Montag, den 11.02.2019, 15:39 -0600 schrieb Bjorn Helgaas:
>> > On Wed, Feb 06, 2019 at 10:57:32AM +0100, Stefan Agner wrote:
>> > > Define the length of the DBI
Tegra194 supports maximum 64K bytes per packet including 12 bytes of
packet header irrespective of PIO or DMA mode transfer.
This patch updates Tegra194 max write length to account for packet
header size for transfers.
Cc: sta...@vger.kernel.org # 4.20+
Reviewed-by: Dmitry Osipenko
On Wed, Feb 13, 2019 at 2:34 AM Greg KH wrote:
>
> On Wed, Feb 13, 2019 at 02:06:49AM +0800, Xiang Xiao wrote:
> > Here is the detailed description for memrchr:
> > https://linux.die.net/man/3/memrchr
>
> Please put it in the changelog, as web pages move and go away :(
Sure.
>
> >
> >
On Sun, Feb 10, 2019 at 7:21 PM Deepa Dinamani wrote:
>
> On Feb 10, 2019, at 7:43 AM, Ran Rozenstein wrote:
>
> >> Subject: [PATCH net-next v5 09/12] socket: Add SO_TIMESTAMPING_NEW
> >>
> >> Add SO_TIMESTAMPING_NEW variant of socket timestamp options.
> >> This is the y2038 safe versions of
On Wed, Feb 13, 2019 at 02:54:43AM +0800, Xiang Xiao wrote:
> Here is the detailed description for memrchr:
>
> void *memrchr(const void *s, int c, size_t n);
>
> The memrchr() function is like the memchr() function, except
> that it searches backward from the end of the n bytes pointed
> to by
On Wed, Feb 13, 2019 at 02:54:43AM +0800, Xiang Xiao wrote:
> Here is the detailed description for memrchr:
>
> void *memrchr(const void *s, int c, size_t n);
>
> The memrchr() function is like the memchr() function, except
> that it searches backward from the end of the n bytes pointed
> to by
On 11.02.2019 15:25, Maxime Chevallier wrote:
> The 802.3bz specification, based on previous by the NBASET alliance,
> defines the 2.5GBaseT and 5GBaseT link modes for ethernet traffic on
> cat5e, cat6 and cat7 cables.
>
> These mode integrate with the already defined C45 MDIO PMA/PMD registers
>
On Wed, Feb 13, 2019 at 03:09:19AM +0800, xiang xiao wrote:
> On Wed, Feb 13, 2019 at 2:34 AM Greg KH wrote:
> >
> > On Wed, Feb 13, 2019 at 02:06:49AM +0800, Xiang Xiao wrote:
> > > Here is the detailed description for memrchr:
> > > https://linux.die.net/man/3/memrchr
> >
> > Please put it in
On Tue, Feb 12, 2019 at 11:04:27AM -0800, syzbot wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:d4104460aec1 Add linux-next specific files for 20190211
> git tree: linux-next
I can't find this commit. How can I know for sure which commits are in?
Recent
801 - 900 of 1653 matches
Mail list logo
