On 11/19/2016 12:27 AM, Bjorn Andersson wrote:
On Wed 16 Nov 06:41 PST 2016, Avaneesh Kumar Dwivedi wrote:
i have been a little delayed for posting replies to patch comments,
hopefully onward it should be quick and fast.
I would greatly appreciate if you allow for a discussion before postin
On Mon, Nov 21, 2016 at 08:06:44PM +0100, Ard Biesheuvel wrote:
> On 21 November 2016 at 20:05, Peter Jones wrote:
> > On Mon, Nov 21, 2016 at 04:42:45PM +, Ard Biesheuvel wrote:
> >> On 21 November 2016 at 16:26, Josh Boyer wrote:
> >> > On Mon, Nov 21, 2016 at 11:18 AM, Ard Biesheuvel
> >>
On Mon, Nov 21, 2016 at 11:24:01AM +0530, Sanchayan Maity wrote:
> Current DMA implementation had a bug where the DMA transfer would
> exit the loop in dspi_transfer_one_message after the completion of
> a single transfer. This results in a multi message transfer submitted
> with SPI_IOC_MESSAGE to
The patch
spi: spi-fsl-dspi: Fix SPI transfer issue when using multiple SPI_IOC_MESSAGE
has been applied to the spi tree at
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the
On 11/17/2016 07:09 AM, Johannes Thumshirn wrote:
> Don't use fc_bsg_job::request and fc_bsg_job::reply directly, but use
> helper variables bsg_request and bsg_reply. This will be helpfull when
> transitioning to bsg-lib.
>
> Signed-off-by: Johannes Thumshirn
> Reviewed-by: Hannes Reinecke
> -
On Mon, 21 Nov 2016 10:37:00 -0800
Andi Kleen wrote:
> Just adding a few inlines won't fix the gigantic bloat that is currently
> there. See the PT trace I posted earlier (it was even truncated, it's
> actually worse). Just a single enabled trace point took about a us.
If you want to play with
Hello Mark,
On 16-11-21 19:18:47, Mark Brown wrote:
> On Mon, Nov 21, 2016 at 11:24:01AM +0530, Sanchayan Maity wrote:
> > Current DMA implementation had a bug where the DMA transfer would
> > exit the loop in dspi_transfer_one_message after the completion of
> > a single transfer. This results in
On 11/21/16 08:23, Sudeep Holla wrote:
>
>
> On 21/11/16 16:05, Frank Rowand wrote:
>> Hi Sudeep,
>>
>> On 11/18/16 12:22, Frank Rowand wrote:
>>> On 11/18/16 02:41, Sudeep Holla wrote:
On 17/11/16 21:00, Frank Rowand wrote:
> On 11/17/16 07:32, Sudeep Holla wrote:
>> Curre
Inserting images with Sphinx is tricky, due to its limited
image support. So, the Kernel building system needs to
provide some help for it to work.
Document how to do it.
Signed-off-by: Mauro Carvalho Chehab
---
v2: Add the text fixes proposed by Daniel Vetter.
Documentation/doc-guide/images.
Not only media documents may have images. So, move the
rules for building images from graphviz and from SVG to
the Documentation makefile.
With this change, if some Documentation subdir "foo"
can now specify that he has SVG and/or DOT source images
that are included inside the documentation.
All
Hello Mark,
On 16-11-22 00:44:30, maitysancha...@gmail.com wrote:
> Hello Mark,
>
> On 16-11-21 19:18:47, Mark Brown wrote:
> > On Mon, Nov 21, 2016 at 11:24:01AM +0530, Sanchayan Maity wrote:
> > > Current DMA implementation had a bug where the DMA transfer would
> > > exit the loop in dspi_tran
> On Mon, Nov 21, 2016 at 04:49:15PM +0100, Peter Zijlstra wrote:
> > > Speaking of non-fitting patterns. This one is quite common in
> > > networking code for refcounters:
> > >
> > > if (atomic_cmpxchg(&cur->refcnt, 1, 0) == 1) {} This is from
> > > net/netfilter/nfnetlink_acct.c, but there are s
On 11/17/2016 03:25 PM, Jon Mason wrote:
> The second SDIO seems to have been forgotten to be enabled in the
> Northstar2 SVK dts. Also, the PCI PHY entries are missing from the PCI
> bus device tree entries.
Series applied, thanks Jon
--
Florian
On 11/19/2016 1:00 AM, Bjorn Andersson wrote:
On Wed 16 Nov 07:17 PST 2016, Avaneesh Kumar Dwivedi wrote:
On 11/8/2016 12:19 PM, Bjorn Andersson wrote:
On Mon 07 Nov 04:37 PST 2016, Avaneesh Kumar Dwivedi wrote:
Handling of clock and regulator resources as well as reset
register programin
On 21 November 2016 at 20:18, Peter Jones wrote:
> On Mon, Nov 21, 2016 at 08:06:44PM +0100, Ard Biesheuvel wrote:
>> On 21 November 2016 at 20:05, Peter Jones wrote:
>> > On Mon, Nov 21, 2016 at 04:42:45PM +, Ard Biesheuvel wrote:
>> >> On 21 November 2016 at 16:26, Josh Boyer
>> >> wrote:
> -Original Message-
> From: Yao Yuan [mailto:yao.y...@nxp.com]
> Sent: Monday, November 21, 2016 7:28 AM
> To: Krzeminski, Marcin (Nokia - PL/Wroclaw)
> ; Han Xu
> Cc: David Woodhouse ; linux-
> ker...@vger.kernel.org; linux-...@lists.infradead.org;
> han...@freescale.com; Brian Norris
Em Mon, 21 Nov 2016 16:44:28 +0100
Johannes Berg escreveu:
> > > > You had pointed me to this plugin before
> > > > https://pythonhosted.org/sphinxcontrib-aafig/
> > > >
> > > > but I don't think it can actually represent any of the pictures.
> > >
> > > No, but there are some ascii art image
From: Jeff Westfahl
Use the MTD function 'max_bad_blocks' to compute the UBI bad_peb_limit,
if the function is implemented for an MTD and doesn't return an error.
Signed-off-by: Jeff Westfahl
Signed-off-by: Zach Brown
Acked-by: Boris Brezillon
---
drivers/mtd/ubi/build.c | 4
1 file cha
ONFI compliant chips contain the values for the max_bb_per_die and
blocks_per_die fields in the parameter page. When the ONFI paged is
retrieved/parsed the chip's fields are set by the corresponding fields
in the param page.
Signed-off-by: Zach Brown
Acked-by: Boris Brezillon
---
drivers/mtd/na
On 11/20/2016 12:28 PM, David Lechner wrote:
This adds a new driver for the TI ADS7950 family of ADC chips. These
communicate using SPI and come in 8/10/12-bit and 4/8/12/16 channel
varieties.
Signed-off-by: David Lechner
---
v2 changes:
* Got rid of XX wildcards - using ADS7950 everywhere
*
For ONFI-compliant NAND devices, the ONFI parameters report the maximum number
of bad blocks per LUN that will be encountered over the lifetime of the device,
so we can use that information to get a more accurate (and smaller) value for
the UBI bad PEB limit.
The ONFI parameter "maxiumum number of
On 16 November 2016 at 23:27, One Thousand Gnomes
wrote:
> Whether it's a good idea aside
>
> You need to filter or lock down kernel module options because a lot of
> modules let you set the I/O port or similar (eg mmio) which means you can
> hack the entire machine with say the 8250 driver just b
From: Jeff Westfahl
If implemented, 'max_bad_blocks' returns the maximum number of bad
blocks to reserve for an MTD. An implementation for NAND is coming soon.
Signed-off-by: Jeff Westfahl
Signed-off-by: Zach Brown
Acked-by: Boris Brezillon
---
drivers/mtd/mtdpart.c | 12
incl
Implement the new mtd function 'max_bad_blocks'. Using the chip's
max_bb_per_die and blocks_per_die fields to determine the maximum bad
blocks to reserve for an MTD.
Signed-off-by: Jeff Westfahl
Signed-off-by: Zach Brown
Acked-by: Boris Brezillon
---
drivers/mtd/nand/nand_base.c | 35 +
The fields max_bb_per_die and blocks_per_die are useful determining the
number of bad blocks a MTD needs to allocate. How they are set will
depend on if the chip is ONFI, JEDEC or a full-id entry in the nand_ids
table.
Signed-off-by: Zach Brown
Acked-by: Boris Brezillon
---
include/linux/mtd/na
On Mon, Nov 21, 2016 at 11:46:51AM +, David Howells wrote:
> Lukas Wunner wrote:
> > We already have the efi_call_early() macro to call boot services
> > in a manner that works across all arches and bitness variants.
> >
> > In 4.10 there will be an efi_call_proto() macro to allow the same
>
smatch warned:
sval_binop_signed: invalid divide LLONG_MIN/-1
and this fixes it. It's actually good to have, in order to avoid accidental
checking for negative return values here.
Signed-off-by: Martin Kepplinger
---
drivers/iio/accel/mma8452.c | 4 ++--
1 file changed, 2 insertions(+),
On Fri, 2016-11-18 at 00:03 +, Thomas Gleixner wrote:
> We solely intended to convert that driver to the hotplug state
> machine and
> stumbled over a large pile of insanities, which are all interwoven
> with the
> package management:
Thanks Thomas for fixes.
But I did a very simple test on 4.
On Mon, Nov 21, 2016 at 05:23:11PM +, Gabriele Paoloni wrote:
> Hi Bjorn
>
> > -Original Message-
> > From: linux-pci-ow...@vger.kernel.org [mailto:linux-pci-
> > ow...@vger.kernel.org] On Behalf Of Bjorn Helgaas
> > Sent: 21 November 2016 16:47
> > To: Gabriele Paoloni
> > Cc: Bjorn H
On Mon, Nov 21, 2016 at 2:27 PM, Reshetova, Elena
wrote:
>> On Mon, Nov 21, 2016 at 04:49:15PM +0100, Peter Zijlstra wrote:
>> > > Speaking of non-fitting patterns. This one is quite common in
>> > > networking code for refcounters:
>> > >
>> > > if (atomic_cmpxchg(&cur->refcnt, 1, 0) == 1) {} Thi
On Mon, Nov 21, 2016 at 01:24:38PM -0500, Steven Rostedt wrote:
>
> Paul,
>
>
> On Mon, 21 Nov 2016 12:55:01 -0500
> Steven Rostedt wrote:
>
> > On Mon, 21 Nov 2016 18:18:53 +0100
> > Peter Zijlstra wrote:
> >
> > > Its not ftrace as such though, its RCU, ftrace simply uses RCU to avoid
> >
On Sun, Nov 20, 2016 at 10:58:08PM +0100, Manuel Schölling wrote:
> Add a scrollback buffers for each VGA console. The benefit is that
> the scrollback history is not flushed when switching between consoles
> but is persistent.
> The buffers are allocated on demand when a new console is opened.
>
> -Original Message-
> From: netdev-ow...@vger.kernel.org [mailto:netdev-
> ow...@vger.kernel.org] On Behalf Of Leon Romanovsky
> Sent: Monday, November 21, 2016 5:14 PM
> To: Salil Mehta
> Cc: dledf...@redhat.com; Huwei (Xavier); oulijun;
> mehta.salil@gmail.com; linux-r...@vger.kernel
On 11/21/16 08:20, Sudeep Holla wrote:
>
>
> On 18/11/16 20:22, Frank Rowand wrote:
>> On 11/18/16 02:41, Sudeep Holla wrote:
>>>
>>>
>>> On 17/11/16 21:00, Frank Rowand wrote:
On 11/17/16 07:32, Sudeep Holla wrote:
> Currently platforms/drivers needing to get the machine model name are
On Mon, Nov 21, 2016 at 04:58:25PM +0100, Wim Osterholt wrote:
>
> I didn't find traces of kernel-4.9-rc5 being ran on any of my laptops, so I
> can't have seen a crash on rc5. It seems rc5 and rc6 is safe now.
Neither 4.8.10, nor 4.8.9 show the bug.
It must be a bug ouside cdc_acm that they have
From: Christopher Covington
Ensure that reads of the PMCCNTR_EL0 are monotonically increasing,
even for the smallest delta of two subsequent reads.
Signed-off-by: Christopher Covington
Signed-off-by: Wei Huang
---
arm/pmu.c | 156 ++
From: Christopher Covington
Calculate the numbers of cycles per instruction (CPI) implied by ARM
PMU cycle counter values. The code includes a strict checking facility
intended for the -icount option in TCG mode in the configuration file.
Signed-off-by: Christopher Covington
Signed-off-by: Wei
Declare the structure ieee802154_ops as const as it is only passed as an
argument to the function ieee802154_alloc_hw. This argument is of type
const struct ieee802154_ops *, so ieee80254_ops structures having this
property can be declared as const.
Done using Coccinelle:
@r1 disable optional_qua
From: Christopher Covington
Beginning with a simple sanity check of the control register, add
a unit test for the ARM Performance Monitors Unit (PMU).
Signed-off-by: Christopher Covington
Signed-off-by: Wei Huang
Reviewed-by: Andrew Jones
---
arm/Makefile.common | 3 ++-
arm/pmu.c
Changes from v9:
* Move PMCCNTR related configuration from pmu_init() to sub-tests
* Change the name of loop test function to precise_cycles_loop()
* Print out error detail for each test case in check_cpi()
* Fix cpi convertion from argv
* Change the loop calculation in measure_instrs() after cpi i
On Mon, Nov 21, 2016 at 05:53:01PM +0100, Michael Walle wrote:
> Am 2016-11-19 19:05, schrieb Guenter Roeck:
> >Hi Michael,
> >
> >On Fri, Oct 14, 2016 at 11:43:35AM +0200, Michael Walle wrote:
> >>This patch adds support for the min, max and alarm attributes of the
> >>voltage and temperature chan
This is certainly not the first time this has been brought up, but I'd like to
try and get some consensus on the best way to move this forward. Allowing
devices to talk directly improves performance and reduces latency by avoiding
the use of staging buffers in system memory. Also in cases wher
On 21/11/16 12:49, Laxman Dewangan wrote:
>
> On Monday 21 November 2016 04:38 PM, Jon Hunter wrote:
>>>
>>> I had a discussion with the ASIC on this and as per them
>>> 1.8 V nominal is (1.62V, 1.98V)
>>> 3.3 V nominal is (2.97V,3.63V)
>>>
>>> I am working with them to update the TRM d
From: Babu Moger
Date: Mon, 21 Nov 2016 14:25:50 -0600
> Hi Dave,
>
> On 11/21/2016 12:42 PM, David Miller wrote:
>> From: Babu Moger
>> Date: Tue, 1 Nov 2016 14:13:43 -0700
>>
>>> This is an attempt to cleanup watchdog handlers. Right now,
>>> kernel/watchdog.c implements both softlockup and
Hello.
On 21/11/16 21:30, Bhumika Goyal wrote:
Declare the structure ieee802154_ops as const as it is only passed as an
argument to the function ieee802154_alloc_hw. This argument is of type
const struct ieee802154_ops *, so ieee80254_ops structures having this
property can be declared as const
On 11/17/2016 6:31 AM, Neftin, Sasha wrote:
On 11/13/2016 10:34 AM, Neftin, Sasha wrote:
On 11/11/2016 12:35 AM, Baicar, Tyler wrote:
Hello Sasha,
On 11/9/2016 11:19 PM, Neftin, Sasha wrote:
On 11/9/2016 11:41 PM, Tyler Baicar wrote:
Move IRQ free code so that it will happen regardless of th
On 11/21/2016 12:13 PM, Steven Rostedt wrote:
On Fri, 20 Nov 2015 15:57:22 -0500
Josef Bacik wrote:
We use trace-cmd pretty extensively inside of Facebook for various things, such
as live gathering of statistics. Currently this involves launching trace-cmd to
record data and then processing t
On Mon, Nov 21, 2016 at 02:30:13PM +, One Thousand Gnomes wrote:
> > > increase in timestamp resoultion of at least another 10e-3 is
> > > likely
> >
> > Is it, though? To be useful, surely you have to be able to jam quite a few
> > instructions into a 1ns block, including memory access
> > http://halobates.de/tracepoint-trace
>
> There's a lot of push and pop regs due to function calling. There's
> places that inlines can still improve things, and perhaps even some
> likely unlikelys well placed.
Assuming you avoid all the push/pop and all the call/ret this would only be
~25% o
On Mon, 21 Nov 2016 07:21:02 +0100
Eric Auger wrote:
> Capability header next field is an offset relative to the start of
> the INFO buffer. tmp->next is assigned the proper value but iterations
> implemented in vfio_info_cap_add and vfio_info_cap_shift use next
> as an offset between the headers
On 11/21/16 11:24, Frank Rowand wrote:
> On 11/21/16 08:23, Sudeep Holla wrote:
>>
>>
>> On 21/11/16 16:05, Frank Rowand wrote:
>>> Hi Sudeep,
>>>
>>> On 11/18/16 12:22, Frank Rowand wrote:
On 11/18/16 02:41, Sudeep Holla wrote:
>
>
> On 17/11/16 21:00, Frank Rowand wrote:
>> O
On Mon, Nov 21, 2016 at 5:46 PM, Peter Zijlstra wrote:
> On Mon, Nov 21, 2016 at 04:24:24PM +, Patrick Bellasi wrote:
>> On 21-Nov 16:26, Peter Zijlstra wrote:
>
>> > In any case, worth trying, see what happens.
>>
>> Are you saying that you would like to see the code which implements a
>> mor
On Fri, 2016-11-18 at 22:21 +0800, Geliang Tang wrote:
> Drop duplicate header device.h from phy3250.c.
>
> Signed-off-by: Geliang Tang
> ---
> arch/arm/mach-lpc32xx/phy3250.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/arch/arm/mach-lpc32xx/phy3250.c b/arch/arm/mach-lpc32xx/phy3250
On 09/11/16 13:06, Laxman Dewangan wrote:
> NVIDIA Tegra124 and later SoCs support the multi-voltage level and
> low power state of some of its IO pads. The IO pads can work in
> the voltage of the 1.8V and 3.3V of IO voltage from IO power rail
> sources. When IO interfaces are not used then IO pa
From: Bhumika Goyal
Date: Tue, 22 Nov 2016 02:00:14 +0530
> Declare the structure ieee802154_ops as const as it is only passed as an
> argument to the function ieee802154_alloc_hw. This argument is of type
> const struct ieee802154_ops *, so ieee80254_ops structures having this
> property can be
On Mon, Nov 21, 2016 at 10:26 AM, H. Peter Anvin wrote:
> On 11/21/16 10:00, Linus Torvalds wrote:
>>
>> I'd much rather we go back to just making the "cs" entry explicitly
>> 16-bit, and have a separate padding entry, the way we used to long
>> long ago.
>>
>
> I would agree 100% with this.
We _
Adding -f/--force option to go through ownership validation:
$ sudo perf c2c report
File perf.data not owned by current user or root (use -f to override)
$ sudo perf c2c report -f
Link: http://lkml.kernel.org/n/tip-p035bwv1lr24lf6n5apt2...@git.kernel.org
Signed-off-by: Jiri Olsa
---
tool
It was useful for debug to see file descriptors for each event.
Before:
$ perf stat -vvv -e cycles,cache-misses ls
...
sys_perf_event_open: pid 12146 cpu -1 group_fd -1 flags 0x8
...
sys_perf_event_open: pid 12146 cpu -1 group_fd 3 flags 0x8
sys_perf_event_open failed, error -13
hi,
sending the c2c default HITM sort/display fix (patch 4,5) plus
few other small fixes.
Also available in here:
git://git.kernel.org/pub/scm/linux/kernel/git/jolsa/perf.git
perf/fixes
thanks,
jirka
---
Jiri Olsa (6):
perf tools: Show event fd in debug output
perf c2c report: Se
Because of the early browser switch we won't get possible
error messages, like for:
$ sudo perf c2c report -d lcl
File perf.data not owned by current user or root (use -f to override)
Link: http://lkml.kernel.org/n/tip-hn3lrw728ealu38e2gfan...@git.kernel.org
Signed-off-by: Jiri Olsa
---
t
Counting total HITMs in special field. This will ease
up addition of total HITM sorting into c2c report in
following patch.
Link: http://lkml.kernel.org/n/tip-wkmgepbip59wui4pnm6yj...@git.kernel.org
Signed-off-by: Jiri Olsa
---
tools/perf/util/mem-events.c | 12 ++--
tools/perf/util/mem-
Adding support for cascading options added by Namhyung in:
commit 369a2478973a ("tools lib subcmd: Support cascading options")
This way the report and record command share options with
with c2c command and can save some option duplicates. For
now it's the 'v' option.
Link: http://lkml.kernel.or
On Mon, 21 Nov 2016, Pandruvada, Srinivas wrote:
> On Fri, 2016-11-18 at 00:03 +, Thomas Gleixner wrote:
> > We solely intended to convert that driver to the hotplug state
> > machine and
> > stumbled over a large pile of insanities, which are all interwoven
> > with the
> > package management
Hi Wei,
On 11/21/2016 03:24 PM, Wei Huang wrote:
> From: Christopher Covington
I really appreciate your work on these patches. If for any or all of these
you have more lines added/modified than me (or using any other better
metric), please make sure to change the author to be you with
`git commi
Currently we display cacheline list sorted on remote HITMs by default.
The problem is that they might not be always counted and 'perf c2c report'
displays empty output. Thus it's more convenient to display and sort
cacheline list based on total HITMs and have the best change to see data
in default
Add TI SCI reset controller binding. This describes the DT binding
details for a reset controller node providing reset management services
to hardware blocks (reset consumers) using the Texas Instrument's System
Control Interface (TI SCI) protocol to communicate to a system controller
block present
Hello all,
This series adds a reset controller driver that uses the TI SCI
protocol to manage resets.
The TI SCI protocol is used to communicate with power management
controllers used by some SoCs. These controllers manage the various
power domains, clocks, and resets available on a SoC.
This se
Since we register pcie_pme_driver only for PCI_EXP_TYPE_ROOT_PORT, the PME
driver never claims Root Complex Event Collectors.
Remove unused code related to Root Complex Event Collectors.
Signed-off-by: Bjorn Helgaas
---
drivers/pci/pcie/pme.c | 17 +
1 file changed, 1 insertio
Remove the unused DRIVER_VERSION, DRIVER_AUTHOR, and DRIVER_DESC macros.
The author information is already included in a comment above.
Signed-off-by: Bjorn Helgaas
---
drivers/pci/pcie/aer/aerdrv.c |7 ---
1 file changed, 7 deletions(-)
diff --git a/drivers/pci/pcie/aer/aerdrv.c b/driv
Remove a few messages that don't contain any useful information, e.g.,
pcie_pme :00:02.0:pcie01: service driver pcie_pme loaded
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
pciehp :80:02.0:pcie04: service driver pciehp loaded
pciehp: PCI Express Hot Plug Controller Driver versio
We already log a "Signaling PME" whenever the PME service driver claims a
Root Port. In fact, we also log the same message for every device in the
hierarchy below the Root Port.
Log the "Signaling PME" once (only for the Root Port, since we can
trivially find out which devices are below the Root
Remove the "service driver %s loaded" and unloaded messages. All service
drivers already log something in their probe functions, where they can log
more useful details.
Signed-off-by: Bjorn Helgaas
---
drivers/pci/pcie/portdrv_core.c |3 ---
1 file changed, 3 deletions(-)
diff --git a/driv
Remove the "PCI Hot Plug PCI Core" version message. I don't think it
contains any useful information. Remove unused #defines and move the
author information to a comment.
Signed-off-by: Bjorn Helgaas
---
drivers/pci/hotplug/pci_hotplug_core.c | 10 +++---
1 file changed, 3 insertions(+),
All other AER-related log messages use the PCI device, e.g.,
"pci :00:1c.0", not the PCIe service device, e.g.,
"aer :00:1c.0:pcie02".
Change the probe error messages to match the rest and include a little
context.
Signed-off-by: Bjorn Helgaas
---
drivers/pci/pcie/aer/aerdrv.c |7 ++
On Sun, Nov 13, 2016 at 05:34:44PM +0800, Chen-Yu Tsai wrote:
> > +static struct ccu_nkmp pll_ve_clk = {
> > + .enable = BIT(31),
> > + .n = _SUNXI_CCU_MULT_OFFSET(8, 5, 0),
> > + .k = _SUNXI_CCU_MULT(4, 2),
> > + .m = _SUNXI_CC
It's not very enlightening to see
pci :07:00.0: [Firmware Bug]: VPD access disabled
in the dmesg log because there's no clue about what the firmware bug is.
Expand the message to explain why we're disabling VPD.
Signed-off-by: Bjorn Helgaas
---
drivers/pci/quirks.c |2 +-
1 file chan
Remove the "PCI Express Hot Plug Controller Driver" version message. I
don't think it contains any useful information. Remove unused #defines
and move the author information to a comment.
Signed-off-by: Bjorn Helgaas
---
drivers/pci/hotplug/pciehp_core.c |9 -
1 file changed, 4 ins
Add a log message when we enable AER on a Root Port and the hierarchy below
it.
Signed-off-by: Bjorn Helgaas
---
drivers/pci/pcie/aer/aerdrv.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/pci/pcie/aer/aerdrv.c b/drivers/pci/pcie/aer/aerdrv.c
index 60e63d6..d
On 11/21/2016 10:32 AM, Joerg Roedel wrote:
> On Fri, Nov 18, 2016 at 09:04:05AM -0500, Mark Hounschell wrote:
>> OK. It's attached.
>
>> [ 45.033715] WARNING: CPU: 0 PID: 0 at lib/dma-debug.c:1158
>> check_unmap+0x4ef/0x990
>> [ 45.037651] 3c59x :04:04.0: DMA-API: device driver failed to
Add myself as co-maintainer to fpga mgr framework.
Signed-off-by: Moritz Fischer
Cc: Alan Tull
Cc: Greg Kroah-Hartman
Cc: linux-kernel@vger.kernel.org
Cc: linux-f...@vger.kernel.org
---
Hi all,
Lately we've fallen behind a bit on reviewing patches lately.
'Behind the scenes', Alan has worked
In fs/cifs/smb2pdu.h, we have:
#define SMB2_SHARE_TYPE_DISK0x01
#define SMB2_SHARE_TYPE_PIPE0x02
#define SMB2_SHARE_TYPE_PRINT 0x03
Knowing that, with the current code, the SMB2_SHARE_TYPE_PRINT case can
never trigger and printer share would be interpreted as disk share.
So, test the Sh
On 11/21/2016 04:43 PM, Marc MERLIN wrote:
> Howdy,
>
> As a followup to https://plus.google.com/u/0/+MarcMERLIN/posts/A3FrLVo3kc6
>
> http://pastebin.com/yJybSHNq and http://pastebin.com/B6xEH4Dw
> show a system with plenty of RAM (24GB) falling over and killing inoccent
> user space apps, a few
Update the fpga-mgr framework entry with new linux-f...@vger.kernel.org
mailing list.
Signed-off-by: Moritz Fischer
Cc: Alan Tull
Cc: Greg Kroah-Hartman
Cc: Michal Simek
Cc: Sören Brinkmann
Cc: David S. Miller
Cc: Geert Uytterhoeven
Cc: Andrew Morton
Cc: linux-f...@vger.kernel.org
Cc: linu
Some TI Keystone family of SoCs contain a system controller (like the
Power Management Micro Controller (PMMC) on K2G SoCs) that manage the
low-level device control (like clocks, resets etc) for the various
hardware modules present on the SoC. These device control operations
are provided to the hos
On Mon, 21 Nov 2016, Guenter Roeck wrote:
> Just be aware that this patch is buggy.
Zapped it for now.
Thanks,
tglx
On Sun, Nov 13, 2016 at 11:01:27PM +0800, Chen-Yu Tsai wrote:
> > compatible = "allwinner,sun5i-a13-tcon";
> > reg = <0x01c0c000 0x1000>;
> > interrupts = <44>;
> > - resets = <&tcon_ch0_clk 1>;
> > +
Unlike monotonic clock, boot clock as a trace clock will account for
time spent in suspend useful for tracing suspend/resume. This uses
earlier introduced infrastructure for using the fast boot clock.
Cc: Steven Rostedt
Cc: Thomas Gleixner
Cc: John Stultz
Cc: Ingo Molnar
Signed-off-by: Joel Fe
On Mon, Nov 21, 2016 at 7:28 AM, Chris Metcalf wrote:
> On 11/21/2016 3:54 AM, Ingo Molnar wrote:
>>
>> * John Stultz wrote:
>>
>>> From: Chris Metcalf
>>>
>>> The "cycles" argument should not be an absolute clocksource cycle
>>> value, as the implementation's arithmetic will overflow relatively
Currently no trace clock can account for suspend time, using monotonic during
tracing in the suspend path means the trace times wont be advaced. Using the
boot clock with ktime_get_with_offset is not an option due to live locking
concerns in NMI context as suggested by Thomas [1].
These patches add
Introduce a fast boot clock. It accounts for suspend time and is based on the
fast monotonic clock so that its safe to use for tracing. Next patch adds the
clock to trace clock.
Cc: Steven Rostedt
Cc: Thomas Gleixner
Cc: John Stultz
Cc: Ingo Molnar
Signed-off-by: Joel Fernandes
---
kernel/ti
On Mon, Nov 21, 2016 at 2:04 PM, Joel Fernandes wrote:
> Currently no trace clock can account for suspend time, using monotonic during
> tracing in the suspend path means the trace times wont be advaced. Using the
> boot clock with ktime_get_with_offset is not an option due to live locking
> conce
On 11/21/2016 10:49 PM, Moritz Fischer wrote:
> Add myself as co-maintainer to fpga mgr framework.
>
> Signed-off-by: Moritz Fischer
> Cc: Alan Tull
> Cc: Greg Kroah-Hartman
> Cc: linux-kernel@vger.kernel.org
> Cc: linux-f...@vger.kernel.org
Acked-by: Marek Vasut
> ---
> Hi all,
>
> Lately
Currently no trace clock can account for suspend time, using monotonic during
tracing in the suspend path means the trace times wont be advaced. Using the
boot clock with ktime_get_with_offset is not an option due to live locking
concerns in NMI context as suggested by Thomas [1].
These patches add
Introduce a fast boot clock. It accounts for suspend time and is based on the
fast monotonic clock so that its safe to use for tracing. Next patch adds the
clock to trace clock.
Cc: Steven Rostedt
Cc: Thomas Gleixner
Cc: John Stultz
Cc: Ingo Molnar
Signed-off-by: Joel Fernandes
---
kernel/ti
Unlike monotonic clock, boot clock as a trace clock will account for
time spent in suspend useful for tracing suspend/resume. This uses
earlier introduced infrastructure for using the fast boot clock.
Cc: Steven Rostedt
Cc: Thomas Gleixner
Cc: John Stultz
Cc: Ingo Molnar
Signed-off-by: Joel Fe
The "perf_counter_reset" case has already been handled above.
Moreover "ORANGEFS_PARAM_REQUEST_OP_READAHEAD_COUNT_SIZE" is not a really
consistent.
It is likely that this (dead) code is a cut and paste left over.
Signed-off-by: Christophe JAILLET
---
fs/orangefs/orangefs-sysfs.c | 9 -
1
Just be aware that this patch is buggy.
Guenter
On Mon, Nov 21, 2016 at 07:56:02AM -0800, tip-bot for Sebastian Andrzej Siewior
wrote:
> Commit-ID: 73f4f6f5ab9a069037b8e98663193accaf18bd5c
> Gitweb: http://git.kernel.org/tip/73f4f6f5ab9a069037b8e98663193accaf18bd5c
> Author: Sebastian A
On Mon, Nov 21, 2016 at 10:50:20PM +0100, Vlastimil Babka wrote:
> > 4.9rc5 however seems to be doing better, and is still running after 18
> > hours. However, I got a few page allocation failures as per below, but the
> > system seems to recover.
> > Vlastimil, do you want me to continue the copy
On Monday, November 21, 2016 03:45:19 PM Bjorn Helgaas wrote:
> Since we register pcie_pme_driver only for PCI_EXP_TYPE_ROOT_PORT, the PME
> driver never claims Root Complex Event Collectors.
>
> Remove unused code related to Root Complex Event Collectors.
>
> Signed-off-by: Bjorn Helgaas
> ---
On Monday, November 21, 2016 03:45:26 PM Bjorn Helgaas wrote:
> We already log a "Signaling PME" whenever the PME service driver claims a
> Root Port. In fact, we also log the same message for every device in the
> hierarchy below the Root Port.
>
> Log the "Signaling PME" once (only for the Root
701 - 800 of 893 matches
Mail list logo
