On 22/08/17 11:41 AM, Andy Shevchenko wrote:
@@ -59,6 +59,7 @@
#include
#include
#include
+#include
I would rather try to squeeze to most alpabetiacelly ordered part of this block.
Otherwise it's a pretty nice clean up!
I don't understand. The includes were not alphabetically in
On Tue, 22 Aug 2017 20:03:50 +0200,
SF Markus Elfring wrote:
>
> From: Markus Elfring
> Date: Tue, 22 Aug 2017 19:58:30 +0200
>
> Add a jump target so that a bit of exception handling can be better reused
> at the end of this function.
>
> This issue was detected
On Tue, 2017-08-08 at 14:18 -0400, Dennis Dalessandro wrote:
> On 8/5/2017 9:11 AM, Colin King wrote:
> > From: Colin Ian King
> >
> > Trivial fix to spelling mistake in pr_warn_ratelimited warning
> > message
> >
> > Signed-off-by: Colin Ian King
Hi Anup,
We should add default (as below).
On 17-08-22 03:00 AM, Anup Patel wrote:
This patch adds Broadcom FlexRM low-level reset for
VFIO platform.
It will do the following:
1. Disable/Deactivate each FlexRM ring
2. Flush each FlexRM ring
The cleanup sequence for FlexRM rings is adapted
From: Andi Kleen
Only show the Intel format attributes in sysfs when the feature is actually
supported with the current model numbers. This allows programs to probe
what format attributes are available, and give a sensible error message
to users if they are not.
This
Some improvements for the sysfs enumeration for the cpu pmu to make
it easier for user programs to discover what is supported.
-Andi
On Tue, Aug 22, 2017 at 11:56 AM, Peter Zijlstra wrote:
>
> Won't we now prematurely terminate the wait when we get a spurious
> wakeup?
I think there's two answers to that:
(a) do we even care?
(b) what spurious wakeup?
The "do we even care" quesiton is because
4.12-stable review patch. If anyone has any objections, please let me know.
--
From: KT Liao
commit 76988690402dde2880bfe06ecccf381d48ba8e1c upstream.
Add 2 new IDs (ELAN0609 and ELAN060B) to the list of ACPI IDs that should
be handled by the driver.
4.12-stable review patch. If anyone has any objections, please let me know.
--
From: Vladimir Davydov
commit f6ba488073fe8159851fe398cc3c5ee383bb4c7a upstream.
To avoid a possible deadlock, sysfs_slab_remove() schedules an
asynchronous work to delete
4.12-stable review patch. If anyone has any objections, please let me know.
--
From: Pavel Tatashin
commit 3010f876500f9ba921afaeccec30c45ca6584dc8 upstream.
There is existing use after free bug when deferred struct pages are
enabled:
The
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Linus Torvalds
commit 197e7e521384a23b9e585178f3f11c9fa08274b9 upstream.
The 'move_paghes()' system call was introduced long long ago with the
same permission
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Munehisa Kamata
commit b15bd8cb37598afb2963f7eb9e2de468d2d60a2f upstream.
Since commit d05d7f40791c ("Merge branch 'for-4.8/core' of
git://git.kernel.dk/linux-block") and
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Thomas Bogendoerfer
commit 4098116039911e8870d84c975e2ec22dab65a909 upstream.
For 64bit kernels the lmmio_space_offset of the host bridge window
isn't set correctly
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Alexey Dobriyan
commit 8fbbe2d7cc478d1544f41f2271787c993c23a4f6 upstream.
Valid CPU ids are [0, nr_cpu_ids-1] inclusive.
Fixes: 3b8e29a82dd1 ("genirq: Implement
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
commit a8e800fe0f68bc28ce309914f47e432742b865ed upstream.
A Senheisser headset requires the typical sample-rate quirk for
avoiding spurious errors from inquiring
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Liping Zhang
commit 9c3f3794926a997b1cab6c42480ff300efa2d162 upstream.
If one cpu is doing nf_ct_extend_unregister while another cpu is doing
__nf_ct_ext_add_length, then
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Boris Brezillon
commit 277867ade8262583f4280cadbe90e0031a3706a7 upstream.
of_find_compatible_node() is calling of_node_put() on its first argument
thus
From: Markus Elfring
Date: Tue, 22 Aug 2017 21:45:42 +0200
Add a jump target so that a bit of exception handling can be better reused
at the end of this function.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
>> @@ -1121,30 +1121,27 @@ static int snd_via82xx_create(struct snd_card *card,
>>
>> if ((err = pci_request_regions(pci, card->driver)) < 0) {
>> kfree(chip);
>> -pci_disable_device(pci);
>> -return err;
>> +goto disable_device;
>> }
>
Hi,
On Tue, Aug 22, 2017 at 02:43:13PM +0300, Stefan Mavrodiev wrote:
> Rename dts file for A20-OLinuXino-LIME2-eMMC to match Olimex Ltd.
> naming convention.
>
> -exGB - option with GB eMMC chip
> -nxGB - option with GB NAND chip
> -sxMB - option with MB SPI FLASH chip
>
> For example:
>
On Tue, Aug 22, 2017 at 10:29:35AM +0530, Kishon Vijay Abraham I wrote:
> Hi Greg,
>
> Stephen Rothwell reported a issue with my previous pull request
> w.r.t missing Signed-off-by committer. I've fixed that in this pull
> request.
>
> It adds a new USB phy driver for Ralink SoC, add support for
On Fri, Aug 18, 2017 at 08:17:15AM +0300, Alexey Budankov wrote:
> Hi,
Please don't post new versions in reply to old versions, that gets them
lost in thread sorted views.
> This patch set v7 moves event groups into rb trees and implements
> skipping to the current CPU's list on hrtimer
On Tue, Aug 22, 2017 at 02:43:12PM +0300, Stefan Mavrodiev wrote:
> A20-OLinuXino-MICRO has option with onboard eMMC chip. For
> now it's only shipped with 4BG chip, but in the future this
> may change.
>
> Currently the board is called "A20-OLinuXino-MICRO-e4GB".
> The dts is named "-exGB" to
On 8/21/2017 3:37 PM, Sinan Kaya wrote:
> bool pci_bus_crs_pending(struct pci_dev *dev, u32 l)
> {
> if !pci_bus_crs_vis_supported(dev->parent)
> return false;
Apparently, I can't do this. By the time, we come to here from vendor id read
function, the topology has not been set
On Tue, Aug 22, 2017 at 9:16 PM, Theodore Ts'o wrote:
>
> Theodore Ts'o (1):
> ext4: fix clang build regression
Tssk. The authorship attribution here looks wrong, and the authorship
(Arnd) ended up being in the commit log rather than the author field.
Please be more careful
On Tue, Aug 22, 2017 at 07:33:45PM -0700, Joe Perches wrote:
> On Tue, 2017-08-22 at 18:40 -0700, Greg KH wrote:
> > On Thu, Aug 17, 2017 at 02:55:04PM +0300, laurentiu.tu...@nxp.com wrote:
> > > From: Laurentiu Tudor
> > >
> > > Throughout the driver we use == 0 / != 0
This adds support for reading and writing date/time from/to ds1314 chip.
Other functionality (alarms, inout clock, output clock) is not added
yet, because availability of that depends on chip connections.
Signed-off-by: Nikita Yushchenko
---
drivers/rtc/Kconfig
On Tue, Aug 22, 2017 at 10:55:36PM -0400, Nick Fox wrote:
> Remove extra blank line (reported by checkpatch.pl)
>
> Signed-off-by: Nick Fox
> ---
> drivers/staging/android/ion/ion_cma_heap.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git
于 2017年8月23日 GMT+08:00 上午4:12:15, Maxime Ripard
写到:
>On Tue, Aug 22, 2017 at 02:17:42PM +0800, Icenowy Zheng wrote:
>> +_vcc5v0 {
>> +gpio = < 7 23 GPIO_ACTIVE_HIGH>; /* PH23 */
>> +enable-active-high;
>> +};
>
>Same thing here, you're not using that
On Wed, Aug 9, 2017 at 9:44 AM, Ming Lei wrote:
> Hi David,
>
> On Wed, Aug 9, 2017 at 2:13 AM, David Jeffery wrote:
>> On 08/07/2017 07:53 PM, Ming Lei wrote:
>>> On Tue, Aug 8, 2017 at 3:38 AM, David Jeffery wrote:
>>
Hi jeffy,
On Wed, 23 Aug 2017 11:21:40 +0800 jeffy <jeffy.c...@rock-chips.com> wrote:
>
> I was testing a arm64 based device(chromebook bob), and the kernel hang
> a lot(during booting or suspending) on for-next(next-20170822) with this
> commit:
> 71acb768f5b3 (
Hi Viresh,
2017-08-16 14:37 GMT+09:00 Viresh Kumar :
> Drop few ARM (32 and 64 bit) platforms from the whitelist which always
> use "operating-points-v2" property from their DT. They should continue
> to work after this patch.
>
> Tested on Hikey platform (only the
Himanshu Jha writes:
> Check memory allocation failure and return -ENOMEM if failure
> occurs.
>
> Signed-off-by: Himanshu Jha
The title prefix is wrong:
On (08/23/17 12:38), Boqun Feng wrote:
[..]
> diff --git a/kernel/locking/lockdep.c b/kernel/locking/lockdep.c
> index 642fb5362507..a3709e15f609 100644
> --- a/kernel/locking/lockdep.c
> +++ b/kernel/locking/lockdep.c
> @@ -1156,6 +1156,23 @@ print_circular_lock_scenario(struct held_lock *src,
>
From: Madalin-cristian Bucur
Date: Wed, 23 Aug 2017 04:36:56 +
> The struct fman is only visible in the fman file, the fman port
> module uses struct fman as an opaque pointer, thus this export.
Don't use that programming model.
Export the datastructure properly to
Sergey Senozhatsky wrote:
> > > > ==
> > > > WARNING: possible circular locking dependency detected
> > > > 4.13.0-rc6-next-20170822-dbg-00020-g39758ed8aae0-dirty #1746 Not tainted
> > > > --
Am 23.08.2017 02:29 schrieb Harinath Nampally:
If rising: use transient OR ff_mt device-dependent like before. But
now save it in a simple flag,
whether transient registers are available.
Ok, is it good idea to add the flag to struct mma_chip_info like below?
* @mma_scales:
M +, Bart Van Assche wrote:
> > > > On Tue, 2017-08-22 at 19:47 +0900, Sergey Senozhatsky wrote:
> > > > > ==
> > > > > WARNING: possible circular locking dependency detected
> > > > &
On Tue, Aug 22, 2017 at 08:14:10PM -0700, John Stultz wrote:
> On Tue, Aug 22, 2017 at 8:01 PM, Jisheng Zhang wrote:
> > On Tue, 22 Aug 2017 19:57:04 -0700 John Stultz wrote:
> >
> >> On Tue, Aug 22, 2017 at 7:56 PM, John Stultz
> >> wrote:
> >> > On
On Tue, Aug 22, 2017 at 10:55:37PM -0400, Nick Fox wrote:
> Change argument to kmalloc() to fix style issue, reported by checkpatch
>
> Signed-off-by: Nick Fox
> ---
> drivers/staging/android/ion/ion_cma_heap.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
There is a problem that when counting the pages for creating
the hibernation snapshot will take significant amount of
time, especially on system with large memory. Since the counting
job is performed with irq disabled, this might lead to NMI lockup.
The following warning were found on a system
This commit provides similar cleanups as commit 83eacdfa2529 ("mmc:
sdhci: disable the clock in sdhci_pltfm_unregister()") did for
unregister hooks.
sdhci-brcmstb.c and sdhci-sirf.c implement their own suspend/resume
hooks to handle pltfm_host->clk. Move clock handling to sdhci_pltfm.c
so that
> From: Jorgen S. Hansen [mailto:jhan...@vmware.com]
> > On Aug 22, 2017, at 11:54 AM, Stefan Hajnoczi
> wrote:
> > ...
> > We *can* by looking at the destination CID. Please take a look at
> > drivers/misc/vmw_vmci/vmci_route.c:vmci_route() to see how VMCI
> handles
> >
On 8/22/2017 7:46 PM, Sricharan R wrote:
Hi,
+ /* Take it off the tree of receive intents */
+ if (!intent->reuse) {
+ spin_lock(>intent_lock);
+ idr_remove(>liids, intent->id);
+ spin_unlock(>intent_lock);
+ }
+
+ /* Schedule the sending of a rx_done
On Mon, Aug 14, 2017 at 02:08:07PM +0200, Heiko Carstens wrote:
> > Now, I would like to avoid going down that road to pull
> > in kernel internal headers into test_verifier.c, could
> > we instead add a bpf_ptregs.h helper in tools/testing/selftests/bpf/,
> > where s390 and arm64 would put a
On Wed, Aug 23, 2017 at 12:38:13PM +0800, Boqun Feng wrote:
> From: Boqun Feng
> Date: Wed, 23 Aug 2017 12:12:16 +0800
> Subject: [PATCH] lockdep: Print proper scenario if cross deadlock detected at
> acquisition time
>
> For a potential deadlock about CROSSRELEASE as
On (08/23/17 13:35), Boqun Feng wrote:
[..]
> > > printk(KERN_CONT ");\n");
> >
> > KERN_CONT and "\n" should not be together. "\n" flushes the cont
> > buffer immediately.
> >
>
> Hmm.. Not quite familiar with printk() stuffs, but I could see several
> usages of printk(KERN_CONT
On (08/23/17 13:35), Boqun Feng wrote:
> > KERN_CONT and "\n" should not be together. "\n" flushes the cont
> > buffer immediately.
> >
>
> Hmm.. Not quite familiar with printk() stuffs, but I could see several
> usages of printk(KERN_CONT "...\n") in kernel.
>
> Did a bit research myself, and
> > WARNING: possible circular locking dependency detected
> > > 4.13.0-rc6-next-20170822-dbg-00020-g39758ed8aae0-dirty #1746 Not tainted
> > > --
> > > fsck.ext4/148 is trying to acquire lock:
> > > (>bd_
+ linux-wireless
Stanislav Yakovlev writes:
> On 22 August 2017 at 07:47, Romain Perier wrote:
>> The PCI pool API is deprecated. This commit replaces the PCI pool old
>> API by the appropriate function with the DMA pool API.
>>
>>
From: Vallish Vaidyeshwara
Date: Wed, 23 Aug 2017 00:10:25 +
> I am submitting 2 patch series to enable hires timer to timeout
> datagram sockets (AF_UNIX & AF_INET domain) and test code to test
> timeout accuracy on these sockets.
This is not reasonable.
If you want
Sergey Senozhatsky wrote:
> > > > ==
> > > > WARNING: possible circular locking dependency detected
> > > > 4.13.0-rc6-next-20170822-dbg-00020-g39758ed8aae0-dirty #1746 Not tainted
> > > > --
> -Original Message-
> From: netdev-ow...@vger.kernel.org [mailto:netdev-ow...@vger.kernel.org]
> On Behalf Of David Miller
> Sent: Wednesday, August 23, 2017 12:35 AM
> Subject: Re: [PATCH v2 1/6] fsl/fman: enable FMan Keygen
>
> From: Madalin Bucur
> Date: Tue,
Add a print statement in pci_bus_wait_crs() so that user observes the
progress of device polling instead of silently waiting for timeout to be
reached.
Signed-off-by: Sinan Kaya
[bhelgaas: check for timeout first so we don't print "waiting, giving up",
always print time
Sporadic reset issues have been observed with Intel 750 NVMe drive while
assigning the physical function to the guest machine. The sequence of
events observed is as follows:
- perform a Function Level Reset (FLR)
- sleep up to 1000ms total
- read ~0 from PCI_COMMAND
- warn that the
We need a wrapper function to determine when a particular device is
returning Configuration Request Retry Status (CRS) response. This will only
happen if the root port supports CRS visibility.
Signed-off-by: Sinan Kaya
---
drivers/pci/pci.h | 4
1 file changed, 4
From: Bjorn Helgaas
While waiting for a device to become ready (i.e., to return a non-CRS
completion to a read of its Vendor ID), if we got a valid response to the
very last read before timing out, we printed a warning and gave up on the
device even though it was actually
On Wed, Aug 23, 2017 at 01:06:52PM +0800, Shurong Zhang wrote:
> Replace hard-coded function names in strings with "%s", __func__
> in the olpc_dcon.c file. Issue found by checkpatch.pl.
What is up with the odd indentation?
And why did you send this twice? Which patch should I use? I'll
On Tue, Aug 22, 2017 at 02:55:39PM +0200, Rafael J. Wysocki wrote:
> On Tuesday, August 22, 2017 5:20:02 AM CEST Chen Yu wrote:
> > There is a problem that when counting the pages for creating
> > the hibernation snapshot will take significant amount of
> > time, especially on system with large
Hi,
> From: linux-acpi-ow...@vger.kernel.org
> [mailto:linux-acpi-ow...@vger.kernel.org] On Behalf Of Chao Fan
> Subject: [PATCH] actbl1.h: use tab instead of seven spaces as the indentation
>
> The indentation of these two lines is seven spaces, but not tab.
> So fix it.
>
> Signed-off-by:
Currently, the probe function initializes the PHY, but PHY settings
are lost during the sleep state. Restore the PHY registers when
resuming.
To facilitate this, split sdhci_cdns_phy_init() into the DT parse
part and PHY update part so that the latter can be invoked from the
resume hook.
The difference between sdhci_pxav2_remove() and sdhci_pltfm_unregister()
is clk_put(). It will go away by using the managed resource clk, then
sdhci_pltfm_unregister() can be reused.
Also, rename the jump labels to say what the goto does. (Coding style
suggested by
Hi,
> From: Rafael J. Wysocki [mailto:r...@rjwysocki.net]
> Subject: Re: [PATCH v3 1/4] ACPI / EC: Cleanup EC GPE mask flag
>
> On Friday, August 11, 2017 8:36:28 AM CEST Lv Zheng wrote:
> > EC_FLAGS_COMMAND_STORM is actually used to mask GPE during IRQ processing.
> > This patch cleans it up
On Wed, Aug 23, 2017 at 10:34:20AM +0800, Jisheng Zhang wrote:
> On Tue, 22 Aug 2017 18:51:08 -0700 Greg KH wrote:
>
> > On Tue, Aug 08, 2017 at 07:03:05PM +0800, Jisheng Zhang wrote:
> > > As noted in commit d0bdff0db809 ("staging: Fix build issues with new
> > > binder API"), we can add back
On Wed, Aug 23, 2017 at 01:46:48PM +0900, Sergey Senozhatsky wrote:
> On (08/23/17 12:38), Boqun Feng wrote:
> [..]
> > diff --git a/kernel/locking/lockdep.c b/kernel/locking/lockdep.c
> > index 642fb5362507..a3709e15f609 100644
> > --- a/kernel/locking/lockdep.c
> > +++ b/kernel/locking/lockdep.c
Add binding for the TI's sdhci-omap controller. This now includes only
a subset of properties documented in ti-omap-hsmmc.txt but will eventually
include all the properties.
Signed-off-by: Kishon Vijay Abraham I
---
Changes from v2:
*) Fixed example to use the updated compatible
On Wed, Aug 23, 2017 at 03:43:33AM +, Zheng, Lv wrote:
>Hi,
>
>> From: linux-acpi-ow...@vger.kernel.org
>> [mailto:linux-acpi-ow...@vger.kernel.org] On Behalf Of Chao Fan
>> Subject: [PATCH] actbl1.h: use tab instead of seven spaces as the indentation
>>
>> The indentation of these two lines
2017-08-21 22:17 GMT+09:00 Simon Horman :
> On Wed, Aug 16, 2017 at 11:07:27AM +0530, Viresh Kumar wrote:
>> The initial idea of creating the cpufreq-dt-platdev.c file was to keep a
>> list of platforms that use the "operating-points" (V1) bindings and
>> create cpufreq device
This will be useful when drivers want to reuse either suspend or
resume callback instead of whole of sdhci_pltfm_pmops.
Signed-off-by: Masahiro Yamada
---
Changes in v4: None
Changes in v3: None
Changes in v2: None
drivers/mmc/host/sdhci-cadence.c | 20
[1] implements suspend / resume for sdhci-cadence.c
[2] refactor sdhci-pxav2
[3] add clk handling for suspend/resume hooks of sdhci-pltfm.
This also cleans up sdhci-brcmstb.c and sdhci-sirf.c
[4] export sdhci_pltfm_suspend/resume to reduce code duplication
Masahiro Yamada (4):
mmc:
The following changes since commit aae4e7a8bc44722fe70d58920a36916b1043195e:
Linux 4.13-rc4 (2017-08-06 18:44:49 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git
tags/ext4_for_linus_stable
for you to fetch changes up to
Hyper-V Sockets (hv_sock) supplies a byte-stream based communication
mechanism between the host and the guest. It uses VMBus ringbuffer as the
transportation layer.
With hv_sock, applications between the host (Windows 10, Windows Server
2016 or newer) and the guest can talk with each other using
Configuration Request Retry Status (CRS) was previously hidden inside
pci_bus_read_dev_vendor_id(). We want to add support for CRS in other
situations, such as waiting for a device to become ready after a Function
Level Reset.
Move CRS handling into pci_bus_wait_crs() so it can be called from
On 08/22/2017 06:14 PM, kemi wrote:
> when performance is not important and when you want all tooling to work, you
> set:
>
> sysctl vm.strict_stats=1
>
> but if you can tolerate some possible tool breakage and some decreased
> counter precision, you can do:
>
> sysctl
> -Original Message-
> From: David Miller [mailto:da...@davemloft.net]
> Sent: Wednesday, August 23, 2017 7:47 AM
> To: Madalin-cristian Bucur
> Cc: net...@vger.kernel.org; linuxppc-...@lists.ozlabs.org; linux-
> ker...@vger.kernel.org
> Subject: Re: [PATCH v2 1/6]
On Tue, 22 Aug 2017 21:12:02 +0200,
SF Markus Elfring wrote:
>
> From: Markus Elfring
> Date: Tue, 22 Aug 2017 21:01:01 +0200
>
> Add jump targets so that a bit of exception handling can be better reused
> at the end of these functions.
>
> This issue was
On Wed, Aug 23, 2017 at 11:31:05AM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the net-next tree got a conflict in:
>
> net/ipv6/ip6_fib.c
>
> between commit:
>
> c5cff8561d2d ("ipv6: add rcu grace period before freeing fib6_node")
>
> from the net tree and
On Wed, Aug 09, 2017 at 11:16:03AM -0500, Gustavo A. R. Silva wrote:
> platform_get_irq() returns an error code, but the pci-dra7xx driver
> ignores it and always returns -EINVAL. This is not correct and,
> prevents -EPROBE_DEFER from being propagated properly.
>
> Print and propagate the return
On 08/14/2017 09:12 AM, Eugeniy Paltsev wrote:
We set AXS103 cpu frequency in arch/arc/plat-axs10x/axs10x.c
via direct writing to pll registers for historical reasons.
So get rid of AXS103 platform specific cpu clock configuration as
we have driver for AXS103 core pll (AXS103 pll driver is
On 08/14/2017 09:12 AM, Eugeniy Paltsev wrote:
Add core pll node (core_clk) to manage cpu frequency.
core_clk represents pll itself.
input_clk represents clock signal source (basically xtal) which
comes to pll input.
Signed-off-by: Eugeniy Paltsev
---
Changes since v7
spi-nor.h
- Fix comment style
spi-nor.c
- Fix condition check to set_4byte() when nor->addr_width == 4 in spi_nor_init()
- Bring back quad_enable logic to spi_nor_setup() and remove it from
spi_nor_scan()
- Remove duplicate comment section in spi_nor_scan()
- Leave dev_info()
This patch extracts some chunks from spi_nor_init_params and spi_nor_scan()
and moves them into a new spi_nor_init() function.
Indeed, spi_nor_init() regroups all the required SPI flash commands to be
sent to the SPI flash memory before performing any runtime operations
(Fast Read, Page Program,
On Thu, Aug 10, 2017 at 04:54:55PM +0530, Faiz Abbas wrote:
> If the interrupt status is cleared before it is handled, it is possible
> that another interrupt will trigger while servicing the previous one.
> This is causing timeouts in some wireless lan cards which use pcie.
> Therefore, clear MSI
Hello,
On Tuesday, 22 August 2017 23:17:31 EEST Maxime Ripard wrote:
> On Tue, Aug 22, 2017 at 08:43:35AM +0200, Hans Verkuil wrote:
> +static int sun6i_video_link_setup(struct media_entity *entity,
> + const struct media_pad *local,
> +
On Tue, Aug 22, 2017 at 1:53 PM, Peter Zijlstra wrote:
>
> So _the_ problem with yield() is when you hit this with a RT task it
> will busy spin and possibly not allow the task that actually has the
> lock to make progress at all.
I thought we had explicitly defined yield()
On Tue, Aug 22, 2017 at 8:55 PM, Logan Gunthorpe wrote:
> On 22/08/17 11:40 AM, Andy Shevchenko wrote:
>> Recomendation is kinda arguable. I doubt modern architectures make
>> difference between IO operations and MMIO.
>> Does, for example, PCI requires some special signal
Can we simple get rid of the stats or make then configurable (off by
defaut)? I agree they are rarely used and have been rarely used in the past.
Maybe some instrumentation for perf etc will allow
similar statistics these days? Thus its possible to drop them?
The space in the pcp pageset is
Priit reported that stmmac was crashing with the trace below. This is because
phy_attached_print() is called too early right after the PHY device has been
found, but before it has a driver attached, since that is only done in
phy_probe() which occurs later.
Fix this by dealing with a possibly
Hi Eames,
[auto build test WARNING on staging/staging-testing]
[also build test WARNING on v4.13-rc6 next-20170822]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Eames-Trinh/Staging-greybus
On 21/08/2017 02:09, Mickaël Salaün wrote:
> Handle 33 filesystem-related LSM hooks for the Landlock filesystem
> event: LANDLOCK_SUBTYPE_EVENT_FS.
>
> A Landlock event wrap LSM hooks for similar kernel object types (e.g.
> struct file, struct path...). Multiple LSM hooks can trigger the same
>
In DAX there are two separate places where the 2MiB range of a PMD is
defined.
The first is in the page tables, where a PMD mapping inserted for a given
address spans from (vmf->address & PMD_MASK) to
((vmf->address & PMD_MASK) + PMD_SIZE - 1). That is, from the 2MiB
boundary below the address
Use ~PG_PMD_COLOUR in dax_entry_waitqueue() instead of open coding an
equivalent page offset mask.
Signed-off-by: Ross Zwisler
---
fs/dax.c | 11 ---
1 file changed, 4 insertions(+), 7 deletions(-)
diff --git a/fs/dax.c b/fs/dax.c
index 865d42c..0e2a1fd
On 08/14/2017 09:12 AM, Eugeniy Paltsev wrote:
Add core pll node (core_clk) to manage cpu frequency.
core_clk represents pll itself.
input_clk represents clock signal source (basically xtal) which
comes to pll input.
Signed-off-by: Eugeniy Paltsev
---
> also if I put 'cycles' instead of the l2_rqsts.all_code_rd,
> I get clean open but 'not counted' as result.. I wonder
> there's some counter scheduling issue
>
> [root@krava perf]# ./perf stat -v -e
> '{branches,branch-misses,l1d.replacement,l2_lines_in.all,cycles}:W' -a sleep 1
> Using CPUID
> I still don't feel my questions have been well answered. Its really
> not clear to me why, in order to allow the level-2 guest to use a vdso
> that the answer is to export more data through the entire stack rather
> then to make the kvmclock to be usable from the vsyscall.
Thanks, this helps.
On Tue, Aug 22, 2017 at 11:06:03AM +0200, Peter Zijlstra wrote:
> On Tue, Aug 22, 2017 at 03:46:03PM +1000, Dave Chinner wrote:
> > Even if I ignore the fact that buffer completions are run on
> > different workqueues, there seems to be a bigger problem with this
> > sort of completion checking.
>
On Tue, Aug 22, 2017 at 04:08:52PM -0500, Christopher Lameter wrote:
> On Tue, 22 Aug 2017, Andi Kleen wrote:
>
> > We only see it on 4S+ today. But systems are always getting larger,
> > so what's a large system today, will be a normal medium scale system
> > tomorrow.
> >
> > BTW we also
From: Bhumika Goyal
Date: Tue, 22 Aug 2017 13:45:59 +0530
> Make this const as it is only stored in a const field of a
> mdiobb_ctrl structure.
>
> Signed-off-by: Bhumika Goyal
Applied.
From: Bhumika Goyal
Date: Tue, 22 Aug 2017 13:43:29 +0530
> Make this const as it is only stored in a const field of a
> mdiobb_ctrl structure.
>
> Signed-off-by: Bhumika Goyal
Applied.
On 08/22/2017 02:44 PM, David Miller wrote:
> From: Florian Fainelli
> Date: Tue, 22 Aug 2017 14:26:47 -0700
>
>> Priit reported that stmmac was crashing with the trace below. This is because
>> phy_attached_print() is called too early right after the PHY device has been
>>
501 - 600 of 2098 matches
Mail list logo