From: Christophe JAILLET
Date: Fri, 7 Oct 2016 22:58:47 +0200
> Size used with 'dma_alloc_coherent()' and 'dma_free_coherent()' should be
> consistent.
> Here, the size of a pointer is used in dma_alloc... and the size of the
> pointed structure is used in dma_free...
>
> This has been spotted
Hi Uffe, Arnd and Scott,
Any comments on this latest patcheset?
Could we consider to merge it if no any other changes needed?
:)
Thanks.
Best regards,
Yangbo Lu
> -Original Message-
> From: Y.B. Lu
> Sent: Monday, September 26, 2016 11:15 AM
> To: linux-...@vger.kernel.org; ulf.hans...
On 10/07/2016 11:42 AM, Bjorn Helgaas wrote:
> Use a device-specific name, "ls", for struct ls_pcie pointers
> to hint that this is device-specific information. No functional change
> intended.
how about ls_pcie instead of ls ?
Roy
We have seen on a number of benchmarks that the scheduler does not operate
like you (I) would expect. One of the tools we have examined a trace file
and showed that, for a "long" period of time, two processes were sharing a
single cpu. That, in itself, is not startling, but there were a number
Size used with 'dma_alloc_coherent()' and 'dma_free_coherent()' should be
consistent.
Here, the size of a pointer is used in dma_alloc... and the size of the
pointed structure is used in dma_free...
This has been spotted with coccinelle, using the following script:
@r@
express
Hi Arnaldo,
Please pull the JSON perf event lists for Powerpc and Intel CPUs.
The following changes since commit 1859e245e6ba91c0c46078622c5f0d6871b940f0:
perf tools: Handle completion of upper case events (2016-10-06 17:00:04 -0300)
are available in the git repository at:
g...@github.com:s
On Fri, Oct 07, 2016 at 05:05:05PM +, Roy Zang wrote:
> On 10/07/2016 11:42 AM, Bjorn Helgaas wrote:
> > Use a device-specific name, "ls", for struct ls_pcie pointers
> > to hint that this is device-specific information. No functional change
> > intended.
> how about ls_pcie instead of ls ?
ls_add_pcie_port() doesn't use the platform_device pointer passed to it, so
remove it. No functional change intended.
Signed-off-by: Bjorn Helgaas
---
drivers/pci/host/pci-layerscape.c |5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/drivers/pci/host/pci-layerscape.c
Do the basic pcie_port setup in the probe function for consistency with
other drivers. No functional change intended.
Signed-off-by: Bjorn Helgaas
---
drivers/pci/host/pci-layerscape.c | 12 +++-
1 file changed, 7 insertions(+), 5 deletions(-)
diff --git a/drivers/pci/host/pci-layers
Use a local "struct device *dev" for brevity and consistency with other
drivers. No functional change intended.
Signed-off-by: Bjorn Helgaas
---
drivers/pci/host/pci-layerscape.c | 16 +---
1 file changed, 9 insertions(+), 7 deletions(-)
diff --git a/drivers/pci/host/pci-layersca
Reorder struct ls_pcie to put generic fields first. No functional change
intended.
Signed-off-by: Bjorn Helgaas
---
drivers/pci/host/pci-layerscape.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/pci/host/pci-layerscape.c
b/drivers/pci/host/pci-layerscape.c
ind
Remove the struct ls_pcie.dbi member, which is a duplicate of the generic
pp.dbi_base member. No functional change intended.
Signed-off-by: Bjorn Helgaas
---
drivers/pci/host/pci-layerscape.c | 24 +++-
1 file changed, 11 insertions(+), 13 deletions(-)
diff --git a/driver
Only interfaces used from outside the driver, e.g., those called by the
DesignWare core, need to accept pointers to the generic struct pcie_port.
Internal interfaces can accept pointers to the device-specific struct,
which makes them more straightforward. No functional change intended.
Signed-off
Use a device-specific name, "ls", for struct ls_pcie pointers
to hint that this is device-specific information. No functional change
intended.
Signed-off-by: Bjorn Helgaas
---
drivers/pci/host/pci-layerscape.c | 86 +++--
1 file changed, 43 insertions(+), 43 de
Can we just switch this on? Powerpc does not use relative extables
(that's a nice exercise left for the reader), so it should just use
the standard sort.
This patch seems to work, famous last words...
Sorting probably only takes a few ms on any real hardware, but on on
very large kernel configs,
This commit results in boot stopping after the following messages.
Any additional information I could provide?
U-Boot 2010.12-svn19826 (Apr 24 2013 - 20:01:21)
CPU: P1014, Version: 1.0, (0x80f10110)
Core: E500, Version: 5.1, (0x80212151)
Clock Configuration:
CPU0:800 MHz,
CCB:4
On 9/21/16, Denis Kirjanov wrote:
> That's unclear why lockdep shows the following warning but adding a
> lockdep class to struct pmac_i2c_bus solves it
>
> [ 20.507795] ==
> [ 20.507796] [ INFO: possible circular locking dependency detected
Am 27.09.2016 um 01:08 schrieb Scott Wood:
On Mon, 2016-09-26 at 10:48 +0200, David Engraf wrote:
Am 25.09.2016 um 08:20 schrieb Scott Wood:
On Mon, Aug 22, 2016 at 04:46:43PM +0200, David Engraf wrote:
The PowerPC e5500/e6500 architecture is based on the e500mc core. Enable
CONFIG_E500 and
Hi Balbir, Michael,
On Tue, Oct 04, 2016 at 10:33:27PM +1100, Balbir Singh wrote:
>
>
> On 04/10/16 21:32, Michael Ellerman wrote:
> > "Gautham R. Shenoy" writes:
> >
> >> From: "Gautham R. Shenoy"
> >>
> >> The power9_idle_stop method currently takes only the requested stop
> >> level as a
19 matches
Mail list logo
