On Thu, Jun 16, 2016 at 06:48:56PM -0300, Daniel Bristot de Oliveira wrote:
> On 06/07/2016 05:05 PM, Daniel Bristot de Oliveira wrote:
> > On 06/07/2016 04:30 PM, Tejun Heo wrote:
> >> Is this something in mainline? This forces all task free path to be
> >> irq-safe, which *could* be fine but it'
On Thu, Jun 16, 2016 at 06:03:15PM -0400, Tejun Heo wrote:
> On Thu, Jun 16, 2016 at 06:48:56PM -0300, Daniel Bristot de Oliveira wrote:
> > On 06/07/2016 05:05 PM, Daniel Bristot de Oliveira wrote:
> > > On 06/07/2016 04:30 PM, Tejun Heo wrote:
> > >> Is this something in mainline? This forces al
On Tue, Jun 14, 2016 at 04:24:04PM +0800, Po Liu wrote:
> NXP some platforms aer interrupt was not MSI/MSI-X/INTx
> but using interrupt line independently. This patch add a "aer"
> interrupt-names for aer interrupt.
Please put your explanation why this is okay to change in the commit
message.
>
On 06/15/16 01:50, Peter Zijlstra wrote:
>>
>> It seems to me that the sanest way to handle this is to add a new
>> interface with a fourth parameter, so:
>>
>> changed = cmpxchgx(ptr, old, new, out);
>
> See also:
>
>
> lkml.kernel.org/r/146358429016.8596.3381723959064491676.st...@wartho
On Tue, Jun 14, 2016 at 11:13:22AM +0200, Boris Brezillon wrote:
> Document the pwm-dutycycle-unit and pwm-dutycycle-range properties.
>
> Signed-off-by: Boris Brezillon
> Acked-by: Brian Norris
> ---
> .../devicetree/bindings/regulator/pwm-regulator.txt | 19
> +++
> 1 file
Hi guys,
This patch wasn't originally CCed to you (I'm fixing that now). Would
you consider taking this into the perf tree? It's been in active use
in both Debian and Android for a while now.
(If need be, I can resend it.)
Thanks!
-Kees
On Sat, Jun 4, 2016 at 1:49 PM, Jeffrey Vander Stoep wro
On Tue, Jun 14, 2016 at 08:00:20AM -0500, Bjorn Helgaas wrote:
> The convention in these files is to use lowercase for "0x" prefixes and for
> the hex constants themselves, but a few changes didn't follow that
> convention, which makes the file annoying to read.
>
> Use lowercase consistently for
On Tue, Jun 14, 2016 at 08:00:30AM -0500, Bjorn Helgaas wrote:
> Unit addresses should not have a leading '0x'. Remove them.
>
> Signed-off-by: Bjorn Helgaas
> ---
> arch/arm64/boot/dts/apm/apm-shadowcat.dtsi | 32
> ++--
> 1 file changed, 16 insertions(+), 16 deletio
Make use of the new Requires: tag to be able to specify coccinelle binary
version requirements. The cocci file device_node_continue.cocci requires at
least coccinelle 1.0.4.
Signed-off-by: Luis R. Rodriguez
---
scripts/coccinelle/iterators/device_node_continue.cocci | 3 +++
1 file changed, 3 in
Coccinelle has had parmap support since 1.0.2, this means
it supports --jobs, enabling built-in multithreaded functionality,
instead of needing one to script it out. Just look for --jobs
in the help output to determine if this is supported.
Also enable the load balancing to be dynamic, so that if
When debugging (using --profile or --show-trying) you want to
avoid supressing output, use --quiet instead. While at it, extend
documentation for SPFLAGS use.
For instance one can use:
$ export COCCI=scripts/coccinelle/misc/irqf_oneshot.cocci
$ make coccicheck DEBUG_FILE="poo.err" MODE=report SP
Glimpse is a tool you can use to index the kernel. The tool
was open sourced on 2014-09-26 [0] under the ISC license however
the original release still [1] does not compile. A fix for this
and a release that does compile is provided in a temporary
tree [2].
v2 changesl:
o simplify DIR in one line
Sprinkling *tons* of documentation on the script is not a good
idea, instead refer to a wiki for further coccicheck documentation:
https://bottest.wiki.kernel.org/coccicheck
This page shall always refer to the linux-next iteration of
scripts/coccicheck.
Signed-off-by: Luis R. Rodriguez
---
scr
This has no functional changes. This is being done
to enable us to later use spatch binary for some
flag checking for certain features early on.
Signed-off-by: Luis R. Rodriguez
---
scripts/coccicheck | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/scripts/cocciche
series, all of which you can find here:
https://git.kernel.org/cgit/linux/kernel/git/mcgrof/linux-next.git/log/?h=20160616-sysdata-v2
Since further development is done on top of this we may need to coordinate
with another maintainer for how these go in. The coccicheck changes will be
important to
Coccinelle has support to make use of its own enhanced "grep"
mechanisms instead of using regular grep for searching code,
it calls this 'coccigrep'. In lack of any indexing optimization
information it uses --use-coccigrep by default.
This patch enable indexing optimizations heuristics so that coc
Enable Coccinelle SmPL patches to require a specific version of
Coccinelle. In the event that the version does not match we just
inform the user, if the user asked to go through all SmPL patches
we just inform them of the need for a new version of coccinelle for
the SmPL patch and continue on with
On Thu, 2016-06-16 at 14:29 -0700, James Bottomley wrote:
> On Thu, 2016-06-16 at 23:24 +0200, Daniel Vetter wrote:
> > I guess we'll need the bisect on this one to make progress.
>
> Sigh, I was afraid that might be the next step.
OK, I have a curious data point. I assumed the problem would be
On Wed, Jun 15, 2016 at 01:39:21PM +0200, Joerg Roedel wrote:
>On Tue, May 24, 2016 at 11:06:55PM +, Wei Yang wrote:
>> Hi, Joerg
>>
>> Not sure whether you think this calculation is correct.
>>
>> If I missed something for this " + 1" in your formula, I am glad to hear your
>> explanation. S
Thou shalt not make firmware calls early on init or probe.
systemd already ripped support out for the usermode helper
a while ago, there are still users that require the usermode helper,
however systemd's use of the usermode helper exacerbated a long
lasting issue of the fact that we have many dri
I've been reviewing changes proactively, and plan on doing
more of this work. I'm doing this early as I should be getting
e-mailed about proposed changes.
Signed-off-by: Luis R. Rodriguez
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index d86978d9
We need to ensure no one else adds *anything* that requests the
usermode helper without really meaning it, to police it we now have
an SmPL script but no formal annotation is present to help us ensure
the call has been validated.
Add a dummy DECLARE_FW_LOADER_USER() which we can use to annotate
va
We've determined that very sadly we cannot nuke the usermode helper.
The firmware code is a bit hard to follow, and so is the history,
document the reasons for why we cannot remove the usermode helper and
the only thing we can do is compartamentalize it.
While it, add a Coccinelle SmPL patch to he
The firmware cache purposely kills all non-udev (usermode helper)
pending requests prior to suspend with kill_requests_without_uevent()
right before it calls out to request for firmware for the fw cache.
It is pointless to again run into the possible issue of queing up
further usermode helpers duri
-next.git/log/?h=20160616-sysdata-v2
Luis R. Rodriguez (5):
MAINTAINERS: extend firmware_class maintainer list
firmware: annotate thou shalt not request fw on init or probe
firmware: update usermode helper docs and add SmPL report
firmware: add usermode helper DECLARE_FW_LOADER_USER
On 16/06/2016 09:33, Pali Rohár wrote:
> On Wednesday 15 June 2016 20:19:58 Darren Hart wrote:
>> On Wed, Jun 15, 2016 at 09:49:09PM +0200, Pali Rohár wrote:
>>> First patch describe problem about 0xe045 code. Second and third are just
>>> cosmetic and last rework code which processing WMI events.
> > we see performance drop 30-40% for SPECjbb2005 and SPECjvm2008
> Blergh, of course I don't have those.. :/
SPECjvm2008 is publicly available.
https://www.spec.org/download.html
We will prepare a reproducer and attach it to the BZ.
> What kind of config and userspace setup? Do you run this cr
Unlike PIT based calibration which counts TSC cycles against another timer,
MSR or CPUID method has no calibration - it simply multiplies the known
frequency of a timer by a ratio. So TSC frequency computed by MSR or CPUID
is the final frequency and doesn't need the refined calibration process.
We
On Thu, 16 Jun 2016 23:26:13 +0200 Richard Weinberger wrote:
> While block oriented filesystems use buffer_migrate_page()
> as page migration function other filesystems which don't
> implement ->migratepage() will automatically get fallback_migrate_page()
> assigned. fallback_migrate_page() is no
Hi William,
Am Donnerstag, 2. Juni 2016, 20:34:56 schrieb William Wu:
> This patch adds the devicetree documentation required for Rockchip
> USB3.0 core wrapper consisting of USB3.0 IP from Synopsys.
>
> It supports DRD mode, and could operate in device mode (SS, HS, FS)
> and host mode (SS, HS,
Am Donnerstag, 12. Mai 2016, 15:43:03 schrieb Brian Norris:
> From: Shawn Lin
>
> According to the databook, 10.2us is the max time for dll to be ready to
> work. However in testing, some chips need 20us for dll to be ready. This
> patch adds some extra margin for dllrdy to be ready, fixing our
>
Am Freitag, 13. Mai 2016, 14:09:43 schrieb Brian Norris:
> From: Shawn Lin
>
> Signal integrity analysis has suggested we set these values. Do this in
> power_on(), so that they get reconfigured after suspend/resume.
>
> Signed-off-by: Shawn Lin
> Signed-off-by: Brian Norris
on my rk3399-evb
Am Donnerstag, 12. Mai 2016, 15:43:05 schrieb Brian Norris:
> The output tap delay controls helps maintain the hold requirements for
> eMMC. The exact value is dependent on the SoC and other factors, though
> it isn't really an exact science. But the default of 0 is not very good,
> as it doesn't g
Am Donnerstag, 12. Mai 2016, 15:43:06 schrieb Brian Norris:
> Some of the spacing was wrong (spaces instead of tabs), and due to
> longer entries added later, the columns weren't aligned. Let's get
> everything consistent.
>
> Signed-off-by: Brian Norris
Readability is always nice :-)
Reviewed-
Am Montag, 13. Juni 2016, 16:04:24 schrieb Douglas Anderson:
> The theme of this series of patches is to try to allow running the eMMC
> at 150 MHz on the rk3399 SoC, though the changes should still be correct
> and have merit on their own. The motivation for running at 150 MHz is
> that doing so
This patch adds fractional scale clock support.
Fractional scale clock is implemented for a single register field.
Output rate = parent_rate * scale / denominator
For example, for 1 / 8 fractional scale, denominator will be 8 and scale
will be computed and programmed accordingly.
Hoan Tran (2):
This patch adds fractional scale clock support.
Fractional scale clock is implemented for a single register field.
Output rate = parent_rate * scale / denominator
For example, for 1 / 8 fractional scale, denominator will be 8 and scale
will be computed and programmed accordingly.
Signed-off-by:
Add fractional scale clock DTS binding.
Signed-off-by: Hoan Tran
Signed-off-by: Loc Ho
---
.../bindings/clock/fractional-scale-clock.txt | 31 ++
1 file changed, 31 insertions(+)
create mode 100644
Documentation/devicetree/bindings/clock/fractional-scale-clock.txt
di
On Thu, 16 Jun 2016 11:29:06 -0300
Arnaldo Carvalho de Melo wrote:
> Em Thu, Jun 16, 2016 at 06:38:30AM +0900, Masami Hiramatsu escreveu:
> > On Wed, 15 Jun 2016 14:38:59 -0300
> > Arnaldo Carvalho de Melo wrote:
> >
> > > Em Wed, Jun 15, 2016 at 12:28:40PM +0900, Masami Hiramatsu escreveu:
> >
Am Mittwoch, 15. Juni 2016, 09:37:51 schrieb Douglas Anderson:
> Some SD/eMMC PHYs (like the PHY from Arasan that is designed to work
> with arasan,sdhci-5.1) need to know the card clock in order to function
> properly. Let's add the ability to expose this clock. Any PHY that
> needs to know the
[3]. If you wish you can get the changes
from my linux-next tree as well [4]. Please do note that all these series
are based on linux-next tag next-20160616, and I noticed that Andrew Morton
had picked up a patch by Stephen Boyd and Vikram Mulukutla to add yet-another
new old firmware API. This then
The firmware API has evolved over the years slowly, as it
grows we extend it by adding new routines or at times we extend
existing routines with more or less arguments. This doesn't scale
well, when new arguments are added to existing routines it means
we need to traverse the kernel with a slew of
Error that we expect should not be spilled to stdout.
Without this we get:
./fw_filesystem.sh: line 58: printf: write error: Invalid argument
./fw_filesystem.sh: line 63: printf: write error: No such device
./fw_filesystem.sh: line 69: echo: write error: No such file or directory
./fw_filesystem.
When expanding test coverage of firmware_class with the sysdata
API test driver we get a crash when CONFIG_TEST_FIRMWARE=y,
only a combination produces a panic however. This fixes it.
[ cut here ]
WARNING: CPU: 0 PID: 1 at lib/kobject.c:597 kobject_get+0x4d/0x80
kobject: '(
This adds a load tester driver test_sysdata a for the new
extensible sysdata file loader APIs, part of firmware_class.
Since the usermode helper is completely ignored by the sysdata
API the testing is much easier to do.
Contrary to the firmware_class tester which adds in-kernel
code for each and e
This adds an SmPL patch to let you help you convert
drivers over from the old firmware API to the new sysdata
API. Given the amount of changes for the sync case, and the
amount of manual revision needed these patches are kept out
of scripts/coccinelle/ to annotate required developer intervention
on
This uses the new flexible firmware API, since we don't
have to keep the firmware around the sysdata API does the
freeing for us safely.
Signed-off-by: Luis R. Rodriguez
---
arch/x86/kernel/cpu/microcode/amd.c | 56 +
1 file changed, 38 insertions(+), 18 delet
The Coccinelle sysdata patches were used to help with
this transition. The changes have been carefully manually
vetted for. With the conversion we modify the cases that do
not need the firmware to be kept so that the sysdata API
can release it for us. Using the new sysdata API also means
we can get
From: Jason Wang
Date: Wed, 15 Jun 2016 16:38:17 +0800
> We used to queue tx packets in sk_receive_queue, this is less
> efficient since it requires spinlocks to synchronize between producer
> and consumer.
>
> This patch tries to address this by:
>
> - introduce a new mode which will be only e
No need to load test_firmware if its already there.
Signed-off-by: Luis R. Rodriguez
---
tools/testing/selftests/firmware/fw_filesystem.sh | 11 +--
1 file changed, 9 insertions(+), 2 deletions(-)
diff --git a/tools/testing/selftests/firmware/fw_filesystem.sh
b/tools/testing/selftests/
From: Philippe Reynes
Date: Thu, 16 Jun 2016 00:12:48 +0200
> The private structure contain a pointer to phydev, but the structure
> net_device already contain such pointer. So we can remove the pointer
> phydev in the private structure, and update the driver to use the
> one contained in struct
From: Philippe Reynes
Date: Thu, 16 Jun 2016 00:12:49 +0200
> There are two generics functions phy_ethtool_{get|set}_link_ksettings,
> so we can use them instead of defining the same code in the driver.
>
> Signed-off-by: Philippe Reynes
Applied.
From: Hayes Wang
Date: Thu, 16 Jun 2016 14:08:29 +0800
> In set_speed(), BMCR_RESET would be set when the flag of PHY_RESET
> is set. Use BMCR_RESET to replace testing the flag of PHY_RESET.
>
> Signed-off-by: Hayes Wang
Applied, thanks.
Adds the cache nodes and next-level-cache property for the
cacheinfo to work.
Signed-off-by: Li Yang
---
arch/arm64/boot/dts/freescale/fsl-ls1043a.dtsi | 8
1 file changed, 8 insertions(+)
diff --git a/arch/arm64/boot/dts/freescale/fsl-ls1043a.dtsi
b/arch/arm64/boot/dts/freescale/fsl-
Adds the cache nodes and next-level-cache property for the
cacheinfo to work.
Signed-off-by: Li Yang
---
arch/arm64/boot/dts/freescale/fsl-ls2080a.dtsi | 24
1 file changed, 24 insertions(+)
diff --git a/arch/arm64/boot/dts/freescale/fsl-ls2080a.dtsi
b/arch/arm64/boot/
On 06/16/2016 07:14 PM, Tejun Heo wrote:
> Except that the patch seems to use irqsave/restore instead of plain
> irq ones in places. Care to update those?
Hi Tejun,
The use of the irq spin_(un)lock_irq() assumes that the code is always
called with IRQs enabled. But that is not always true in thi
From: Arnd Bergmann
Date: Thu, 16 Jun 2016 11:00:05 +0200
> The b53 dsa register access confusingly uses __raw register accessors
> when both the CPU and the device are big-endian, but it uses little-
> endian accessors when the same device is used from a little-endian
> CPU, which makes no sense
From: John Crispin
Date: Thu, 16 Jun 2016 11:44:44 +0200
>
>
> On 16/06/2016 07:20, David Miller wrote:
>> From: John Crispin
>> Date: Wed, 15 Jun 2016 16:58:46 +0200
>>
>>> This series contains 2 small code cleanups that are leftovers from the
>>> MIPS support. There is also a small fix that
From: Arnd Bergmann
Date: Thu, 16 Jun 2016 13:38:22 +0200
> We get a warning for qlcnic_83xx_get_mac_address when building with
> "make W=1":
>
> drivers/net/ethernet/qlogic/qlcnic/qlcnic_83xx_hw.c: In function
> 'qlcnic_83xx_get_mac_address':
> drivers/net/ethernet/qlogic/qlcnic/qlcnic_83xx_hw
From: Arnd Bergmann
Date: Thu, 16 Jun 2016 13:38:23 +0200
> We get a warning for tlan_handle_tx_eoc when building with "make W=1"
>
> drivers/net/ethernet/ti/tlan.c: In function 'tlan_handle_tx_eoc':
> drivers/net/ethernet/ti/tlan.c:1647:59: error: parameter 'host_int' set but
> not used [-Werr
These patches fix the iTCO watchdog for Apollo Lake.
I changed the watchdog memory io to only use 4 bytes rather
the whole region, I'm not sure if that is the correct way.
The previous 0x30h offset in intel_pmc_ipc.c was for based
on the earlier BXT-M platform. Apollo Lake has it at 0x40h.
Let me
The Apollo Lake Watchdog has the no_reboot flag in the 4th bit.
Signed-off-by: Yong, Jonathan
---
drivers/watchdog/iTCO_wdt.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/watchdog/iTCO_wdt.c b/drivers/watchdog/iTCO_wdt.c
index 0acc6c5..54cab18 100644
--- a/drivers/watchdog/iTCO_
The TCO I/O base is 40h rather than the usual 30h, and the re_reboot
bit is at ACPIBASE+8.
Signed-off-by: Yong, Jonathan
---
drivers/platform/x86/intel_pmc_ipc.c | 10 ++
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git a/drivers/platform/x86/intel_pmc_ipc.c
b/drivers/platfor
The Kconfig for this option is currently:
config ATMEL_SDRAMC
bool "Atmel (Multi-port DDR-)SDRAM Controller"
...meaning that it currently is not being built as a module by anyone.
Lets remove the couple traces of modularity, so that when reading the
driver there is no doubt it is builtin-
The Kconfig currently controlling compilation of this code is:
drivers/memory/Kconfig:config OMAP_GPMC
drivers/memory/Kconfig: bool
...meaning that it currently is not being built as a module by anyone.
Lets remove the modular code that is essentially orphaned, so that
when reading the driver t
The Kconfig currently controlling compilation of this code is:
drivers/memory/Kconfig:config TEGRA20_MC
drivers/memory/Kconfig: bool "Tegra20 Memory Controller(MC) driver"
...meaning that it currently is not being built as a module by anyone.
Lets remove the couple of traces of modular reference
The Kconfig currently controlling compilation of this code is:
memory/samsung/Kconfig:config EXYNOS_SROM
memory/samsung/Kconfig: bool "Exynos SROM controller driver" if COMPILE_TEST
...meaning that it currently is not being built as a module by anyone.
Lets remove the modular code that is essent
The Kconfig currently controlling compilation of this code is:
drivers/memory/Kconfig:config ATMEL_EBI
drivers/memory/Kconfig: bool "Atmel EBI driver"
...meaning that it currently is not being built as a module by anyone.
Lets remove the few remaining modular references, so that when reading
the
On 16-06-16 05:43 PM, Cong Wang wrote:
On Thu, Jun 16, 2016 at 1:50 PM, Alexey Khoroshilov
wrote:
tcf_ife_init() contains a big chunk of code executed with
ife->tcf_lock spinlock held. But that code contains several calls
to sleeping functions:
populate_metalist() and use_all_metadata()
From: "Hisashi Kanda"
I found a logical bug in SPARC code.
So, I send this patch. Please check it.
This bug may occur in the following.
user_rtt_fill_64bit <= If mna trap occurred, call do_mna
+-> do_mna <= Mistake storing registers for fault code and
address
+->
It seems that drivers/memory/ doesn't have a single maintainer, so please
feel free to pick up just one or two patches from this as appropriate.
For anyone new to the underlying goal of this cleanup, we are trying to
not use module support for code that can never be built as a module since:
(1)
Hi Stephan,
On 16 June 2016 at 17:38, Stephan Mueller wrote:
>> This isn't an issue with AF_ALG, I should have changed the subject
>> line perhaps. In this case it's an inconsistency between some
>> implementations and the documentation (header comment). It affects
>> users accessing the cipher
The Kconfig for this option is currently:
config MVEBU_DEVBUS
bool "Marvell EBU Device Bus Controller"
...meaning that it currently is not being built as a module by anyone.
Lets remove the couple traces of modularity, so that when reading the
driver there is no doubt it is builtin-only.
On Thu, Jun 16, 2016 at 08:14:02PM +0200, Peter Zijlstra wrote:
> On Thu, Jun 16, 2016 at 09:02:15AM -0700, Paul E. McKenney wrote:
> > > 2) When we do that right, we can make the tick frequency a command line
> > > option
> > >and just have a compiled in default.
> >
> > As long as there is
On Wed, Jun 15, 2016 at 04:38:17PM +0800, Jason Wang wrote:
> We used to queue tx packets in sk_receive_queue, this is less
> efficient since it requires spinlocks to synchronize between producer
> and consumer.
>
> This patch tries to address this by:
>
> - introduce a new mode which will be onl
From: Wei Tang
Date: Thu, 16 Jun 2016 21:30:12 +0800
> The space is missing after ',', and this will introduce much more
> noise when checking patch around.
>
> Signed-off-by: Wei Tang
Applied.
From: Wei Tang
Date: Thu, 16 Jun 2016 21:17:49 +0800
> This patch fixes the checkpatch.pl error to dev.c:
>
> ERROR: do not initialise statics to 0
>
> Signed-off-by: Wei Tang
Applied.
Hi Lars,
> > The spi_sync_single_transfer function calls spi_sync_transfer
> > with a single spi_transfer element, instead of an array.
>
> So, what's the advantage of using this as opposed to calling
> spi_sync_transfer with a 1 for the number of transfers?
Not much, but it keeps the code a bit
On Thu, Jun 16, 2016 at 05:35:54PM -0400, Waiman Long wrote:
> On 06/15/2016 10:19 PM, Boqun Feng wrote:
> > On Wed, Jun 15, 2016 at 03:01:19PM -0400, Waiman Long wrote:
> > > On 06/15/2016 04:04 AM, Boqun Feng wrote:
> > > > Hi Waiman,
> > > >
> > > > On Tue, Jun 14, 2016 at 06:48:04PM -0400, Wai
sprint_symbol_no_offset() returns the string "function_name [module_name]"
where [module_name] is not printed for built in kernel functions. This
means that the blacklisting code will fail when comparing module function
names with the extended string. This patch adds the functionality to
block a
Hi Hisashi,
On Fri, Jun 17, 2016 at 10:05 AM, 神田 尚 wrote:
> From: "Hisashi Kanda"
Could you please put your real email address here?
> I found a logical bug in SPARC code.
> So, I send this patch. Please check it.
Leave this part out, we only need the explanation of the potential
bug, if you'
On Thu, Jun 16, 2016 at 6:17 PM, Viresh Kumar wrote:
> On 08-06-16, 02:19, Rafael J. Wysocki wrote:
>> On Tuesday, June 07, 2016 03:55:13 PM Viresh Kumar wrote:
>> > Hi Rafael,
>> >
>> > I have spent some more time on this stuff and finally came out with a
>> > very simple solution. I hope you wil
Hi Guenter,
On 2016/6/16 21:12, Guenter Roeck wrote:
On 06/15/2016 06:47 PM, Frank Wang wrote:
Hi Guenter & Heiko,
On 2016/6/15 23:47, Guenter Roeck wrote:
On Tue, Jun 14, 2016 at 6:14 PM, Frank Wang
wrote:
Hi Heiko & Guenter,
On 2016/6/14 22:00, Heiko Stübner wrote:
Am Dienstag, 14. Jun
Applied, thanks!
Len Brown, Intel Open Source Technology Center
Applied, thanks!
Len Brown, Intel Open Source Technology Center
Applied, thanks!
Len Brown, Intel Open Source Technology Center
On 2016年06月16日 22:26, Daniel Lezcano wrote:
On 06/07/2016 06:54 AM, Caesar Wang wrote:
This series patches had been tested on rockchip inside kernel.
In order to support the rk3399 SoC timer and turn off interrupts and
IPIs to
save power in idle.
Okay, it still works bootup on rk3288/other So
On Thu, Jun 16, 2016 at 10:46:23PM +0200, Francois Romieu wrote:
> Netanel Belgazal :
> [...]
>
> Very limited review below.
I'll comment on the documentation (since I edited it heavily) but will
leave some the other parts for Netanel to answer.
> > diff --git a/Documentation/networking/ena.txt
On 06/16/16 11:55, Eduardo Habkost wrote:
> On Thu, Jun 16, 2016 at 12:04:50PM +0200, Paolo Bonzini wrote:
> > On 16/06/2016 08:05, Haozhong Zhang wrote:
> > > From: Ashok Raj
> > >
> > > On Intel platforms, this patch adds LMCE to KVM MCE supported
> > > capabilities and handles guest access to
On Wed, 15 Jun 2016, Peter Zijlstra wrote:
Yeah, see a few patches further in this series, where he guards a
variables with the osq_lock.
So one problem I have with all this is that if we are hardening
osq_lock/unlock()
because of some future use that is specific to rwsems, then we will immed
From 6a076cc00ec12c6f9cba58ee7e4c3dec49e1e7e5 Mon Sep 17 00:00:00 2001
From: Jim Gill
Date: Thu, 16 Jun 2016 14:10:43 -0700
Subject: [PATCH] VMW_PVSCSI: Change to update maintainer details (name, email)
Signed-off-by: Jim Gill
---
drivers/scsi/vmw_pvscsi.c | 2 +-
drivers/scsi/vmw_pvscsi.h | 2
Hi,
[auto build test ERROR on clk/clk-next]
[also build test ERROR on v4.7-rc3 next-20160616]
[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/Hoan-Tran/clk-Add-fractional-scale-clock-support
On 2016/6/13 20:46, Leon Romanovsky wrote:
On Sun, Jun 12, 2016 at 05:41:06PM +0800, Wei Hu (Xavier) wrote:
On 2016/6/9 14:26, Leon Romanovsky wrote:
On Wed, Jun 01, 2016 at 11:37:53PM +0800, Lijun Ou wrote:
This patch registered IB device when loaded, and unregistered
IB device when remove
Hi,
On 16 June 2016 at 18:46, Philipp Zabel wrote:
> Am Donnerstag, den 16.06.2016, 18:29 +0800 schrieb Xinliang Liu:
>> Add compatible for media reset controller.
>>
>> Signed-off-by: Xinliang Liu
>> ---
>> Documentation/devicetree/bindings/reset/hisilicon,hi6220-reset.txt | 4 +++-
>> 1 file
On 2016/6/9 15:10, Leon Romanovsky wrote:
On Wed, Jun 01, 2016 at 11:37:51PM +0800, Lijun Ou wrote:
This patch mainly setup hca for RoCE. It will do a series of
initial works, as follows:
1. init uar table, allocate uar resource
2. init pd table
3. init cq table
4. init mr
Hi Seung-Woo,
On 06/10/2016 10:29 AM, Seung-Woo Kim wrote:
> Hi Jaehoon,
>
> On 2016년 06월 09일 21:38, Jaehoon Chung wrote:
>> Hi Seung-Woo,
>>
>> On 06/08/2016 01:07 PM, Seung-Woo Kim wrote:
>>> This patch removes following UBSAN warnings in dw_mci_setup_bus().
>>> The warnings are caused because
On 2016/6/9 14:39, Leon Romanovsky wrote:
On Wed, Jun 01, 2016 at 11:37:45PM +0800, Lijun Ou wrote:
This patch mainly added the initial bare main driver. It
could get the relative configure information of net node.
Signed-off-by: Wei Hu
Signed-off-by: Nenglong Zhao
Signed-off-by: Lijun Ou
Looks fine to me.
Acked-by: Arvind Kumar (arvindku...@vmware.com)
Thanks!
Arvind
From: Jim Gill
Sent: Thursday, June 16, 2016 6:05 PM
To: j...@linux.vnet.ibm.com; martin.peter...@oracle.com
Cc: Arvind Kumar; pv-driv...@vmware.com; linux-s...@vger.kernel.o
On Thu, Jun 16, 2016 at 02:21:02PM -1000, Linus Torvalds wrote:
> So what is the advantage of this, since it needs to add more lines of code
> than it removes?
>
> It doesn't seem to be a simplification. Quite the reverse.
>
> Your diffstat of the whole automated conversion did that too.
A lot of
On Thu, Jun 16, 2016 at 02:02:37PM +0100, Ben Dooks wrote:
> On 14/06/16 12:08, Arnd Bergmann wrote:
> > On Wednesday, June 8, 2016 3:04:27 AM CEST kbuild test robot wrote:
> drivers/usb/core/of.c:32:21: error: redefinition of
> 'usb_of_get_child_node'
> >> struct device_node *usb_of
801 - 900 of 1044 matches
Mail list logo
