On Fri, 2018-12-07 at 15:41 +0100, Greg Kroah-Hartman wrote:
> On Fri, Dec 07, 2018 at 02:40:26PM +0530, Naresh Kamboju wrote:
> > On Thu, 6 Dec 2018 at 20:15, Greg Kroah-Hartman
> > wrote:
> > >
> > > This is the start of the stable review cycle for the 4.9.144 release.
> > > There are 101
Hi all,
the ARM imx27/31 ports and various sh boards use
dma_declare_coherent_memory on main memory taken from the memblock
allocator.
Is there any good reason these couldn't be switched to CMA areas?
Getting rid of these magic dma_declare_coherent_memory area would
help making the dma allocator
On Thu, Dec 06, 2018 at 08:30:27PM -0700, Jason Gunthorpe wrote:
> On Wed, Dec 05, 2018 at 12:36:26AM -0500, jgli...@redhat.com wrote:
> > From: Jérôme Glisse
> >
> > To avoid having to change many callback definition everytime we want
> > to add a parameter use a structure to group all
Dear Linux folks,
What driver is recommended for current AMD Ryzen based processors
like *AMD Ryzen 5 PRO 1500 Quad-Core Processor* or *AMD EPYC 7601
32-Core Processor*?
Only from the acpi-cpufreq Kconfig description, I assume, that that
driver should be used.
> config X86_ACPI_CPUFREQ
>
Dear Linux folks,
What driver is recommended for current AMD Ryzen based processors
like *AMD Ryzen 5 PRO 1500 Quad-Core Processor* or *AMD EPYC 7601
32-Core Processor*?
Only from the acpi-cpufreq Kconfig description, I assume, that that
driver should be used.
> config X86_ACPI_CPUFREQ
>
Currently we support only platform data for specifying the interconnect
endpoints. As now the endpoints are hard-coded into the consumer driver
this may lead to complications when a single driver is used by multiple
SoCs, which may have different interconnect topology.
To avoid cluttering the
Currently we support only platform data for specifying the interconnect
endpoints. As now the endpoints are hard-coded into the consumer driver
this may lead to complications when a single driver is used by multiple
SoCs, which may have different interconnect topology.
To avoid cluttering the
From: David Dai
Add RSC (Resource State Coordinator) provider
dictating network-on-chip interconnect bus performance
found on SDM845-based platforms.
Signed-off-by: David Dai
Signed-off-by: Georgi Djakov
---
arch/arm64/boot/dts/qcom/sdm845.dtsi | 5 +
1 file changed, 5 insertions(+)
From: David Dai
Add RSC (Resource State Coordinator) provider
dictating network-on-chip interconnect bus performance
found on SDM845-based platforms.
Signed-off-by: David Dai
Signed-off-by: Georgi Djakov
---
arch/arm64/boot/dts/qcom/sdm845.dtsi | 5 +
1 file changed, 5 insertions(+)
This binding is intended to represent the relations between the interconnect
controllers (providers) and consumer device nodes. It will allow creating links
between consumers and interconnect paths (exposed by interconnect providers).
Reviewed-by: Evan Green
Signed-off-by: Georgi Djakov
---
Recently the cmd_db_read_aux_data() function was changed to avoid using
memcpy and return a pointer instead. Update the code to the new API and
fix the build failure.
Fixes: ed3cafa79ea7 ("soc: qcom: cmd-db: Stop memcpy()ing in
cmd_db_read_aux_data()")
Signed-off-by: Georgi Djakov
---
This binding is intended to represent the relations between the interconnect
controllers (providers) and consumer device nodes. It will allow creating links
between consumers and interconnect paths (exposed by interconnect providers).
Reviewed-by: Evan Green
Signed-off-by: Georgi Djakov
---
Recently the cmd_db_read_aux_data() function was changed to avoid using
memcpy and return a pointer instead. Update the code to the new API and
fix the build failure.
Fixes: ed3cafa79ea7 ("soc: qcom: cmd-db: Stop memcpy()ing in
cmd_db_read_aux_data()")
Signed-off-by: Georgi Djakov
---
This patch introduces a new API to get requirements and configure the
interconnect buses across the entire chipset to fit with the current
demand.
The API is using a consumer/provider-based model, where the providers are
the interconnect buses and the consumers could be various drivers.
The
This patch introduces a new API to get requirements and configure the
interconnect buses across the entire chipset to fit with the current
demand.
The API is using a consumer/provider-based model, where the providers are
the interconnect buses and the consumers could be various drivers.
The
From: David Dai
Introduce Qualcomm SDM845 specific provider driver using the
interconnect framework.
Signed-off-by: David Dai
Signed-off-by: Georgi Djakov
---
.../bindings/interconnect/qcom,sdm845.txt | 24 +
drivers/interconnect/Kconfig | 5 +
From: David Dai
Introduce Qualcomm SDM845 specific provider driver using the
interconnect framework.
Signed-off-by: David Dai
Signed-off-by: Georgi Djakov
---
.../bindings/interconnect/qcom,sdm845.txt | 24 +
drivers/interconnect/Kconfig | 5 +
Add myself as the maintainer of the interconnect API.
Signed-off-by: Georgi Djakov
---
MAINTAINERS | 10 ++
1 file changed, 10 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 380e43f585d3..4f426863ff3b 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -7694,6 +7694,16 @@ L:
Add myself as the maintainer of the interconnect API.
Signed-off-by: Georgi Djakov
---
MAINTAINERS | 10 ++
1 file changed, 10 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 380e43f585d3..4f426863ff3b 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -7694,6 +7694,16 @@ L:
Add a functionality to provide information about the current constraints
per each node and provider.
Reviewed-by: Evan Green
Signed-off-by: Georgi Djakov
---
drivers/interconnect/core.c | 71 +
1 file changed, 71 insertions(+)
diff --git
Add a functionality to provide information about the current constraints
per each node and provider.
Reviewed-by: Evan Green
Signed-off-by: Georgi Djakov
---
drivers/interconnect/core.c | 71 +
1 file changed, 71 insertions(+)
diff --git
Modern SoCs have multiple processors and various dedicated cores (video, gpu,
graphics, modem). These cores are talking to each other and can generate a
lot of data flowing through the on-chip interconnects. These interconnect
buses could form different topologies such as crossbar, point to point
Modern SoCs have multiple processors and various dedicated cores (video, gpu,
graphics, modem). These cores are talking to each other and can generate a
lot of data flowing through the on-chip interconnects. These interconnect
buses could form different topologies such as crossbar, point to point
Hi James,
On Fri, Dec 7, 2018 at 3:44 PM James Morse wrote:
>
> Now that kexec_walk_memblock() can do the crash-kernel placement itself
> architectures that don't support kdump via kexe_file_load() need to
> explicitly forbid it.
>
> We don't support this on arm64 until the kernel can add the
Folks, can you take a look at this tree and see if this is useful
for USB:
http://git.infradead.org/users/hch/misc.git/shortlog/refs/heads/dma-noncoherent-allocator
The idea is that you use dma_alloc_attrs with the DMA_ATTR_NON_CONSISTENT
now that I've made sure it is avaiable everywhere [1],
Hi Rob,
On 12/5/18 18:16, Rob Herring wrote:
> On Tue, Nov 27, 2018 at 12:03 PM Georgi Djakov
> wrote:
>>
>> This patch introduces a new API to get requirements and configure the
>> interconnect buses across the entire chipset to fit with the current
>> demand.
>>
>> The API is using a
Hi Rob,
On 12/5/18 18:16, Rob Herring wrote:
> On Tue, Nov 27, 2018 at 12:03 PM Georgi Djakov
> wrote:
>>
>> This patch introduces a new API to get requirements and configure the
>> interconnect buses across the entire chipset to fit with the current
>> demand.
>>
>> The API is using a
On Fri, Dec 07, 2018 at 12:24:20PM -0200, Guilherme G. Piccoli wrote:
> Hi, thanks Dmitry for the re-spin - hopefully now the pa-risc issues
> are fixed.
>
> BTW, any news on the pa-risc testing? We're just waiting on this to get
> the patchset merged?
As far as I know it has been, I got a mail
On Fri, Dec 07, 2018 at 12:24:20PM -0200, Guilherme G. Piccoli wrote:
> Hi, thanks Dmitry for the re-spin - hopefully now the pa-risc issues
> are fixed.
>
> BTW, any news on the pa-risc testing? We're just waiting on this to get
> the patchset merged?
As far as I know it has been, I got a mail
On Wed, 5 Dec 2018 15:24:48 +0100
Borislav Petkov wrote:
> On Wed, Dec 05, 2018 at 10:49:06PM +0900, Masami Hiramatsu wrote:
> > I would like to put this prototype inside arch/x86/kernel/kprobes/core.c,
> > since that is locally used.
>
> Done.
>
> > Should we declare prototypes for __weak
On Wed, 5 Dec 2018 15:24:48 +0100
Borislav Petkov wrote:
> On Wed, Dec 05, 2018 at 10:49:06PM +0900, Masami Hiramatsu wrote:
> > I would like to put this prototype inside arch/x86/kernel/kprobes/core.c,
> > since that is locally used.
>
> Done.
>
> > Should we declare prototypes for __weak
On 07. 12. 18 14:29, Michal Simek wrote:
> On 07. 12. 18 12:29, Masahiro Yamada wrote:
>> On Thu, Dec 6, 2018 at 11:55 PM Michal Simek wrote:
>>>
>>> On 03. 12. 18 8:50, Masahiro Yamada wrote:
This patch set fixes various issues in microblaze Makefiles.
BTW, "simpleImage." works
On 07. 12. 18 14:29, Michal Simek wrote:
> On 07. 12. 18 12:29, Masahiro Yamada wrote:
>> On Thu, Dec 6, 2018 at 11:55 PM Michal Simek wrote:
>>>
>>> On 03. 12. 18 8:50, Masahiro Yamada wrote:
This patch set fixes various issues in microblaze Makefiles.
BTW, "simpleImage." works
On Fri, Dec 7, 2018 at 8:31 AM Paul Walmsley wrote:
>
>
> On Fri, 7 Dec 2018, Rob Herring wrote:
>
> > On Thu, Dec 6, 2018 at 6:46 PM Paul Walmsley
> > wrote:
> > > On Thu, 6 Dec 2018, Rob Herring wrote:
> > > > On Wed, Nov 21, 2018 at 05:06:56PM -0800, Paul Walmsley wrote:
> > > >
> > > > >
On Fri, Dec 7, 2018 at 8:31 AM Paul Walmsley wrote:
>
>
> On Fri, 7 Dec 2018, Rob Herring wrote:
>
> > On Thu, Dec 6, 2018 at 6:46 PM Paul Walmsley
> > wrote:
> > > On Thu, 6 Dec 2018, Rob Herring wrote:
> > > > On Wed, Nov 21, 2018 at 05:06:56PM -0800, Paul Walmsley wrote:
> > > >
> > > > >
> -Original Message-
> From: Dongli Zhang [mailto:dongli.zh...@oracle.com]
> Sent: 07 December 2018 15:10
> To: Paul Durrant ; linux-kernel@vger.kernel.org;
> xen-de...@lists.xenproject.org; linux-bl...@vger.kernel.org
> Cc: ax...@kernel.dk; Roger Pau Monne ;
> konrad.w...@oracle.com
>
On 07/12/18 14:58, Juergen Gross wrote:
> On 07/12/2018 14:52, Paolo Bonzini wrote:
>> On 07/12/18 14:50, Juergen Gross wrote:
>>> The PVH boot entry is in the same bzImage binary as the normal one.
>>> Its just another entry, similar to the Xen PV boot entry. So the binary
>>>
On 12/7/2018 7:23 AM, Marc Gonzalez wrote:
On 06/12/2018 23:11, Jeffrey Hugo wrote:
Add rpm smd clocks, PMIC and bus clocks which are required on MSM8998
for clients to vote on.
Signed-off-by: Jeffrey Hugo
---
v2
-fix compatible ordering nits per Stephen
On 12/7/2018 7:23 AM, Marc Gonzalez wrote:
On 06/12/2018 23:11, Jeffrey Hugo wrote:
Add rpm smd clocks, PMIC and bus clocks which are required on MSM8998
for clients to vote on.
Signed-off-by: Jeffrey Hugo
---
v2
-fix compatible ordering nits per Stephen
On Fri, Dec 07, 2018 at 08:41:18AM -0500, Steven Rostedt wrote:
> On Fri, 7 Dec 2018 09:58:39 +0100
> Peter Zijlstra wrote:
>
> > These patches give no justification *what*so*ever* for why we're doing
> > ugly arse things like this. And why does this, whatever this is, need to
> > be done in
On Fri, Dec 07, 2018 at 08:41:18AM -0500, Steven Rostedt wrote:
> On Fri, 7 Dec 2018 09:58:39 +0100
> Peter Zijlstra wrote:
>
> > These patches give no justification *what*so*ever* for why we're doing
> > ugly arse things like this. And why does this, whatever this is, need to
> > be done in
On 12/7/2018 3:30 AM, Marc Gonzalez wrote:
On 06/12/2018 23:11, Jeffrey Hugo wrote:
Add rpm smd clocks, PMIC and bus clocks which are required on MSM8998
for clients to vote on.
Signed-off-by: Jeffrey Hugo
---
v2
-fix compatible ordering nits per Stephen
On 12/7/2018 3:30 AM, Marc Gonzalez wrote:
On 06/12/2018 23:11, Jeffrey Hugo wrote:
Add rpm smd clocks, PMIC and bus clocks which are required on MSM8998
for clients to vote on.
Signed-off-by: Jeffrey Hugo
---
v2
-fix compatible ordering nits per Stephen
Hi Paul,
On 12/07/2018 05:39 PM, Paul Durrant wrote:
>> -Original Message-
>> From: Xen-devel [mailto:xen-devel-boun...@lists.xenproject.org] On Behalf
>> Of Dongli Zhang
>> Sent: 07 December 2018 04:18
>> To: linux-kernel@vger.kernel.org; xen-de...@lists.xenproject.org; linux-
>>
On Thu, 6 Dec 2018 19:20:45 -0500
Jerome Glisse wrote:
> On Thu, Dec 06, 2018 at 04:48:57PM -0700, Logan Gunthorpe wrote:
> >
> >
> > On 2018-12-06 4:38 p.m., Dave Hansen wrote:
> > > On 12/6/18 3:28 PM, Logan Gunthorpe wrote:
> > >> I didn't think this was meant to describe actual real
On Thu, 6 Dec 2018 19:20:45 -0500
Jerome Glisse wrote:
> On Thu, Dec 06, 2018 at 04:48:57PM -0700, Logan Gunthorpe wrote:
> >
> >
> > On 2018-12-06 4:38 p.m., Dave Hansen wrote:
> > > On 12/6/18 3:28 PM, Logan Gunthorpe wrote:
> > >> I didn't think this was meant to describe actual real
This is an automatic generated email to let you know that the following patch
were queued:
Subject: media: siano: Use kmemdup instead of duplicating its function
Author: Wen Yang
Date:Thu Dec 6 07:29:10 2018 -0500
kmemdup has implemented the function that kmalloc() + memcpy().
We prefer
I will work at the weekend to figure out where the problematic commit is.
— Christian
Sent from my iPhone
> On 7. Dec 2018, at 15:09, Christoph Hellwig wrote:
>
>> On Fri, Dec 07, 2018 at 11:18:18PM +1100, Michael Ellerman wrote:
>> Christoph Hellwig writes:
>>
>>> Ben / Michael,
>>>
>>>
On Fri, Dec 07, 2018 at 01:45:21PM +, Morten Rasmussen wrote:
> Hi,
>
> On Thu, Nov 29, 2018 at 03:28:16PM -0800, Atish Patra wrote:
> > The cpu-map DT entry in ARM64 can describe the CPU topology in
> > much better way compared to other existing approaches. RISC-V can
> > easily adopt this
On Fri, Dec 07, 2018 at 01:45:21PM +, Morten Rasmussen wrote:
> Hi,
>
> On Thu, Nov 29, 2018 at 03:28:16PM -0800, Atish Patra wrote:
> > The cpu-map DT entry in ARM64 can describe the CPU topology in
> > much better way compared to other existing approaches. RISC-V can
> > easily adopt this
On 12/7/18 7:16 AM, Nicolas Boichat wrote:
> IOMMUs using ARMv7 short-descriptor format require page tables
> (level 1 and 2) to be allocated within the first 4GB of RAM, even
> on 64-bit systems.
>
> For level 1/2 pages, ensure GFP_DMA32 is used if CONFIG_ZONE_DMA32
> is defined (e.g. on arm64
--
Dear beneficiary
To receive your ATM card credited with the sum of $1 Million award
from IMF contact us with your shipping information.
Thanka
Visa Inc.
--
Dear beneficiary
To receive your ATM card credited with the sum of $1 Million award
from IMF contact us with your shipping information.
Thanka
Visa Inc.
On Wed, 5 Dec 2018 14:41:30 +0100, Geert Uytterhoeven
wrote:
> When using these options, I do see a slowdown in early boot, but the issue
> is still there.
Hmm, the NIC of the board is NE2000 variants, so DMA coherency will
not be an issue anyway. So strange ...
The board has a PCI slot. If
On 12/6/2018 8:49 PM, Mimi Zohar wrote:
On Wed, 2018-12-05 at 15:31 -0500, Mimi Zohar wrote:
On Tue, 2018-12-04 at 15:40 -0800, Jarkko Sakkinen wrote:
On Tue, Dec 04, 2018 at 09:21:35AM +0100, Roberto Sassu wrote:
Currently the TPM driver allows other kernel subsystems to read only the
SHA1
On Wed, 5 Dec 2018 14:41:30 +0100, Geert Uytterhoeven
wrote:
> When using these options, I do see a slowdown in early boot, but the issue
> is still there.
Hmm, the NIC of the board is NE2000 variants, so DMA coherency will
not be an issue anyway. So strange ...
The board has a PCI slot. If
On 12/6/2018 8:49 PM, Mimi Zohar wrote:
On Wed, 2018-12-05 at 15:31 -0500, Mimi Zohar wrote:
On Tue, 2018-12-04 at 15:40 -0800, Jarkko Sakkinen wrote:
On Tue, Dec 04, 2018 at 09:21:35AM +0100, Roberto Sassu wrote:
Currently the TPM driver allows other kernel subsystems to read only the
SHA1
On 12/07/2018 05:21 AM, Peter Zijlstra wrote:
> On Thu, Dec 06, 2018 at 05:11:40PM -0800, Bart Van Assche wrote:
>> The next patch in this series uses the class name in code that
>> detects calls to lock_acquire() while a class key is being freed. Hence
>> retain the class name for lock classes
On 12/07/2018 05:21 AM, Peter Zijlstra wrote:
> On Thu, Dec 06, 2018 at 05:11:40PM -0800, Bart Van Assche wrote:
>> The next patch in this series uses the class name in code that
>> detects calls to lock_acquire() while a class key is being freed. Hence
>> retain the class name for lock classes
On 06/12/2018 18:42, Souptick Joarder wrote:
Convert to use vm_insert_range() to map range of kernel
memory to user vma.
Signed-off-by: Souptick Joarder
Tested-by: Heiko Stuebner
Acked-by: Heiko Stuebner
---
drivers/gpu/drm/rockchip/rockchip_drm_gem.c | 20 ++--
1 file
On Fri 07-12-18 22:27:13, Pingfan Liu wrote:
> On Fri, Dec 7, 2018 at 10:22 PM Michal Hocko wrote:
> >
> > On Fri 07-12-18 21:20:17, Pingfan Liu wrote:
> > [...]
> > > Hi Michal,
> > >
> > > As I mentioned in my previous email, I have manually apply the patch,
> > > and the patch can not work for
On Fri 07-12-18 22:27:13, Pingfan Liu wrote:
> On Fri, Dec 7, 2018 at 10:22 PM Michal Hocko wrote:
> >
> > On Fri 07-12-18 21:20:17, Pingfan Liu wrote:
> > [...]
> > > Hi Michal,
> > >
> > > As I mentioned in my previous email, I have manually apply the patch,
> > > and the patch can not work for
On 05/12/2018 08:32, Andrew Jones wrote:
> On Wed, Dec 05, 2018 at 09:15:51AM +0800, Peng Hao wrote:
>> Return 0 when there is enough kvm_mmu_memory_cache object.
>>
>> Signed-off-by: Peng Hao
>> ---
>> virt/kvm/arm/mmu.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git
Em Fri, 7 Dec 2018 00:14:38 +0530
Souptick Joarder escreveu:
> Convert to use vm_insert_range to map range of kernel memory
> to user vma.
>
> Signed-off-by: Souptick Joarder
> Reviewed-by: Matthew Wilcox
> Acked-by: Marek Szyprowski
It probably makes sense to apply it via mm tree, together
Em Fri, 7 Dec 2018 00:09:45 +0530
Souptick Joarder escreveu:
> Previouly drivers have their own way of mapping range of
> kernel pages/memory into user vma and this was done by
> invoking vm_insert_page() within a loop.
>
> As this pattern is common across different drivers, it can
> be
On Thu, 6 Dec 2018 10:56:48 +0100
Andrea Righi wrote:
> These interrupt functions are already non-attachable by kprobes.
> Blacklist them explicitly so that they can show up in
> /sys/kernel/debug/kprobes/blacklist and tools like BCC can use this
> additional information.
>
> Signed-off-by:
On Thu, 6 Dec 2018 10:56:48 +0100
Andrea Righi wrote:
> These interrupt functions are already non-attachable by kprobes.
> Blacklist them explicitly so that they can show up in
> /sys/kernel/debug/kprobes/blacklist and tools like BCC can use this
> additional information.
>
> Signed-off-by:
On Fri, Dec 07, 2018 at 01:04:05PM +0100, Greg KH wrote:
On Fri, Dec 07, 2018 at 05:21:49AM -0500, Bo YU wrote:
There is currently a missing terminating newline in non-switch case
match, when msg == NULL.
Signed-off-by: Bo YU
---
Changes in v3:
Improve the commit log,requested by rafael.
On 22/11/2018 03:10, k...@linuxonhyperv.com wrote:
> From: Michael Kelley
>
> Add ARM64-specific code to enable Hyper-V. This code includes:
> * Detecting Hyper-V and initializing the guest/Hyper-V interface
> * Setting up Hyper-V's synthetic clocks
> * Making hypercalls using the HVC
On Fri, Dec 07, 2018 at 01:04:05PM +0100, Greg KH wrote:
On Fri, Dec 07, 2018 at 05:21:49AM -0500, Bo YU wrote:
There is currently a missing terminating newline in non-switch case
match, when msg == NULL.
Signed-off-by: Bo YU
---
Changes in v3:
Improve the commit log,requested by rafael.
On 22/11/2018 03:10, k...@linuxonhyperv.com wrote:
> From: Michael Kelley
>
> Add ARM64-specific code to enable Hyper-V. This code includes:
> * Detecting Hyper-V and initializing the guest/Hyper-V interface
> * Setting up Hyper-V's synthetic clocks
> * Making hypercalls using the HVC
Hi,
On Wed, 5 Dec 2018 18:15:47 +0100
Borislav Petkov wrote:
> On Wed, Dec 05, 2018 at 05:25:26PM +0100, Ingo Molnar wrote:
> > Also, preferably the prototype should be eliminated via proper ordering
> > of functions from lower level to higher levels.
>
> Well, that trampoline_handler() is
On Fri, Dec 07, 2018 at 02:40:26PM +0530, Naresh Kamboju wrote:
> On Thu, 6 Dec 2018 at 20:15, Greg Kroah-Hartman
> wrote:
> >
> > This is the start of the stable review cycle for the 4.9.144 release.
> > There are 101 patches in this series, all will be posted as a response
> > to this one. If
Hi,
On Wed, 5 Dec 2018 18:15:47 +0100
Borislav Petkov wrote:
> On Wed, Dec 05, 2018 at 05:25:26PM +0100, Ingo Molnar wrote:
> > Also, preferably the prototype should be eliminated via proper ordering
> > of functions from lower level to higher levels.
>
> Well, that trampoline_handler() is
On Fri, Dec 07, 2018 at 02:40:26PM +0530, Naresh Kamboju wrote:
> On Thu, 6 Dec 2018 at 20:15, Greg Kroah-Hartman
> wrote:
> >
> > This is the start of the stable review cycle for the 4.9.144 release.
> > There are 101 patches in this series, all will be posted as a response
> > to this one. If
On 12/6/18 11:00 PM, David Rientjes wrote:
> This reverts commit 89c83fb539f95491be80cdd5158e6f0ce329e317.
>
> There are a couple of issues with 89c83fb539f9 independent of its partial
> revert in 2f0799a0ffc0 ("mm, thp: restore node-local hugepage
> allocations"):
>
> Firstly, the interaction
On Fri, Dec 07, 2018 at 09:03:27AM +, Jon Hunter wrote:
>
> On 06/12/2018 14:37, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.9.144 release.
> > There are 101 patches in this series, all will be posted as a response
> > to this one. If anyone has any
On Fri, Dec 07, 2018 at 09:03:27AM +, Jon Hunter wrote:
>
> On 06/12/2018 14:37, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.9.144 release.
> > There are 101 patches in this series, all will be posted as a response
> > to this one. If anyone has any
On 12/6/18 11:00 PM, David Rientjes wrote:
> This reverts commit 89c83fb539f95491be80cdd5158e6f0ce329e317.
>
> There are a couple of issues with 89c83fb539f9 independent of its partial
> revert in 2f0799a0ffc0 ("mm, thp: restore node-local hugepage
> allocations"):
>
> Firstly, the interaction
On Fri, Dec 07, 2018 at 02:13:18PM +, Minas Harutyunyan wrote:
>
> My patch doesn't pass sparse checking: "warning: context imbalance in
> 'dwc2_hsotg_core_init_disconnected' - unexpected unlock". Sparse persist!
> So, I need to re-work patch. Can I use your idea with
>
On 12/7/18 3:01 AM, Paolo Valente wrote:
>
>
>> Il giorno 7 dic 2018, alle ore 03:23, Jens Axboe ha
>> scritto:
>>
>> On 12/6/18 11:18 AM, Paolo Valente wrote:
>>> Hi Jens,
>>> the first patch in this series fixes an error in the decrementing of
>>> the counter of the number of groups with
On Thu, 6 Dec 2018, Florian Weimer wrote:
> > I seem to remember having to take extra care with how the three MIPS ABIs
> > wire the syscalls to get it right in glibc, but I take it then this has
> > been now addressed reliably enough for the glibc not to care how exactly
> > has been
On Fri, 7 Dec 2018, Rob Herring wrote:
> On Thu, Dec 6, 2018 at 6:46 PM Paul Walmsley wrote:
> > On Thu, 6 Dec 2018, Rob Herring wrote:
> > > On Wed, Nov 21, 2018 at 05:06:56PM -0800, Paul Walmsley wrote:
> > >
> > > > .../sifive/sifive-blocks-ip-versioning.txt| 38 +++
> >
On Fri, 7 Dec 2018, Rob Herring wrote:
> On Thu, Dec 6, 2018 at 6:46 PM Paul Walmsley wrote:
> > On Thu, 6 Dec 2018, Rob Herring wrote:
> > > On Wed, Nov 21, 2018 at 05:06:56PM -0800, Paul Walmsley wrote:
> > >
> > > > .../sifive/sifive-blocks-ip-versioning.txt| 38 +++
> >
On Thu, Dec 6, 2018 at 8:38 PM Christoph Hellwig wrote:
>
> On Fri, Nov 30, 2018 at 10:46:04AM +0100, Daniel Vetter wrote:
> > > Being able to dip into CMA and maybe iommu coalescing if we want to
> > > get fancy is indeed the only reason for this API. If we just wanted
> > > to map pages we
According to documentation, device isn't ready for communication,
until firmware asserts the CHG line. Add missing wait for this.
Signed-off-by: Paweł Chmiel
---
Changes from v3:
- Fix checkpatch issues
---
drivers/input/touchscreen/atmel_mxt_ts.c | 11 +++
1 file changed, 11
This patch adds optional regulators, which can be used to power
up touchscreen. After enabling regulators, we need to wait 150msec.
This value is taken from official driver.
It was tested on Samsung Galaxy i9000 (based on Samsung S5PV210 SOC).
Signed-off-by: Paweł Chmiel
---
Changes from v3:
According to documentation, device isn't ready for communication,
until firmware asserts the CHG line. Add missing wait for this.
Signed-off-by: Paweł Chmiel
---
Changes from v3:
- Fix checkpatch issues
---
drivers/input/touchscreen/atmel_mxt_ts.c | 11 +++
1 file changed, 11
This patch adds optional regulators, which can be used to power
up touchscreen. After enabling regulators, we need to wait 150msec.
This value is taken from official driver.
It was tested on Samsung Galaxy i9000 (based on Samsung S5PV210 SOC).
Signed-off-by: Paweł Chmiel
---
Changes from v3:
This patch series adds optional regulator support to atmel_mxt_ts.
First patch adds regulators to driver.
Second patch ensures that device is ready for communication.
Third patch updates documentation.
Changes from v3:
- Checkpatch fixes
- Drop punctuation from subject of one of patches
This patch series adds optional regulator support to atmel_mxt_ts.
First patch adds regulators to driver.
Second patch ensures that device is ready for communication.
Third patch updates documentation.
Changes from v3:
- Checkpatch fixes
- Drop punctuation from subject of one of patches
On Thu, Dec 6, 2018 at 11:56 PM Dmitry Torokhov
wrote:
>
> On Fri, Dec 07, 2018 at 08:46:05AM +1000, Peter Hutterer wrote:
> > On Thu, Dec 06, 2018 at 10:24:11AM +0100, Benjamin Tissoires wrote:
> > > On Thu, Dec 6, 2018 at 9:36 AM Martin Kepplinger
> > > wrote:
> > > >
> > > > On 06.12.18
Document new optional voltage regulators, which can be used
to power down/up touchscreen.
Signed-off-by: Paweł Chmiel
Reviewed-by: Rob Herring
---
Changes from v1:
- Added reviewed-by
---
.../devicetree/bindings/input/atmel,maxtouch.txt | 8
1 file changed, 8 insertions(+)
When the parallel port is usb based and the lp attaches to it, we do
get /dev/lp0, but when we remove the usb device and the parallel port
is gone, we are still left with /dev/lp0.
Unregister the device properly in the detach routine based on the port
number it has connected to.
Signed-off-by:
Urgently need money? We can help you!
Are you by the current situation in trouble or threatens you in trouble?
In this way, we give you the ability to take a new development.
As a rich person I feel obliged to assist people who are struggling to give
them a chance. Everyone deserved a second
On Thu, Dec 6, 2018 at 11:56 PM Dmitry Torokhov
wrote:
>
> On Fri, Dec 07, 2018 at 08:46:05AM +1000, Peter Hutterer wrote:
> > On Thu, Dec 06, 2018 at 10:24:11AM +0100, Benjamin Tissoires wrote:
> > > On Thu, Dec 6, 2018 at 9:36 AM Martin Kepplinger
> > > wrote:
> > > >
> > > > On 06.12.18
Document new optional voltage regulators, which can be used
to power down/up touchscreen.
Signed-off-by: Paweł Chmiel
Reviewed-by: Rob Herring
---
Changes from v1:
- Added reviewed-by
---
.../devicetree/bindings/input/atmel,maxtouch.txt | 8
1 file changed, 8 insertions(+)
When the parallel port is usb based and the lp attaches to it, we do
get /dev/lp0, but when we remove the usb device and the parallel port
is gone, we are still left with /dev/lp0.
Unregister the device properly in the detach routine based on the port
number it has connected to.
Signed-off-by:
Urgently need money? We can help you!
Are you by the current situation in trouble or threatens you in trouble?
In this way, we give you the ability to take a new development.
As a rich person I feel obliged to assist people who are struggling to give
them a chance. Everyone deserved a second
When the parallel port is usb based and the lp attaches to it based on
LP_PARPORT_AUTO, we do get /dev/lp0 and when we remove the usb device
/dev/lp0 is unregistered. But if we now reconnect the usb device we get
/dev/lp1, another disconnection and reconnection and we get /dev/lp2.
Use the port
701 - 800 of 1346 matches
Mail list logo
