Hi,
Commit e82e0561(mm: vmscan: obey proportional scanning requirements for
kswapd) caused a big performance regression(73%) for vm-scalability/
lru-file-readonce testcase on a system with 256G memory without swap.
That testcase simply looks like this:
truncate -s 1T /tmp/vm-scalability.img
Around Tue 18 Feb 2014 14:09:20 +1100 or thereabout, Stephen Rothwell wrote:
Hello Stephen,
Today's linux-next merge of the tip tree got a conflict in
arch/avr32/include/asm/Kbuild between commit d7668f9d448a (avr32: add
generic vga.h to Kbuild) from the tree and commit b119fa61d440
On Tue, 2014-02-18 at 09:35 +0900, Mark Brown wrote:
On Mon, Feb 17, 2014 at 09:07:34AM +0100, Krzysztof Kozlowski wrote:
The low power maps to REGULATOR_MODE_IDLE or REGULATOR_MODE_STANDBY
(depending on the understanding of more efficient and most efficient
for light loads). However the
On Saturday 15 February 2014 01:51 AM, Mark Brown wrote:
On Thu, Feb 06, 2014 at 11:20:13AM +0530, Keerthy wrote:
This patch adds support for TPS65218 PMIC regulators.
The regulators set consists of 6 DCDCs and 1 LDO. The output
voltages are configurable and are meant to supply power to the
+static const struct resource lm3633_effect_resources[] = {
+ {
+ .name = LM3633_EFFECT_BL0_RAMPUP,
+ .flags = IORESOURCE_REG,
+ .start = LM3633_EFFECT_REGISTER(BL0_RAMPUP),
+ },
snip
+ {
+ .name = LM3633_EFFECT_PTN_HIGHBRT,
+
On Tue, Feb 18, 2014 at 05:26:20AM +0400, z...@ioremap.net wrote:
Hi
14.02.2014, 02:05, Uwe Kleine-König u.kleine-koe...@pengutronix.de:
of_get_gpio() might return -EPROBE_DEFER meaning that the driver
providing the gpio isn't ready yet. If that happens for the first gpio
the resulting
--
Vážení: Webmail odberateľ
Oznamujeme vám, že váš e-mailový účet bol prekročený
skladovacie kapacity. Nebudete môcť odosielať a prijímať e-maily a vaše
e-mailový účet bude vymazaný z nášho servera. Ak sa chcete tomuto
problému vyhnúť,
Kliknite na odkaz nižšie pre aktualizáciu pokynov
On 04/02/14 3:17 AM, Alexander Gordeev agord...@redhat.com wrote:
As result of deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range() and pci_enable_msix_range()
Ok, let's try a simpler thing. Only build-tested here:
---
diff --git a/drivers/edac/mce_amd.c b/drivers/edac/mce_amd.c
index 30f7309446a6..30592838f1da 100644
--- a/drivers/edac/mce_amd.c
+++ b/drivers/edac/mce_amd.c
@@ -738,6 +738,9 @@ int amd_decode_mce(struct notifier_block *nb, unsigned long
On 2014-2-18 9:13, Rafael J. Wysocki wrote:
On Saturday, February 08, 2014 09:10:16 PM Hanjun Guo wrote:
idle_boot_override depends on x86 and ia64 now, and we can not
foresee it will be used on ARM or ARM64,so move the code into
CONFIG_X86 and CONFIG_IA64 #ifdefs to make processor_core.c
can
Good morning,
We have developed a patch for the perf Python scripting interface to
provide additional information about the pid, tid, and cpu of generic
events as well as information about the call-stack and resolved symbol
names. This provides scripts with a greater level of detail. The
Hi Ingo, Peter, Thomas,
The CPU hotplug core pieces in this patchset have been Acked by Oleg Nesterov
and Gautham Shenoy. A majority of the remaining patches that do the tree-wide
conversions have been Acked by the various subsystem maintainers. Since those
patches have a build dependency on the
On Mon, Feb 17, 2014 at 10:45 PM, Kent Overstreet k...@daterainc.com wrote:
*swears* Actually, I'm just going to cast this to unsigned (that's definitely
safe here):
commit 70bc49d421c793f73a772ae1f50622a39c6136d9
Author: Kent Overstreet k...@daterainc.com
Date: Mon Feb 17 13:44:06 2014
Below is the list of build error/warning regressions/improvements in
v3.14-rc3[1] compared to v3.13[2].
Summarized:
- build errors: +21/-31
- build warnings: +188/-74
JFYI, when comparing v3.14-rc3[1] to v3.14-rc2[3], the summaries are:
- build errors: +17/-6
- build warnings: +114/-57
On Tue, Feb 18, 2014 at 09:30:30AM +0900, Mark Brown wrote:
On Mon, Feb 17, 2014 at 06:06:03PM +0100, Lars-Peter Clausen wrote:
Hm, this is a bit confusing. For other functions in ASoC when we
have a pair of functions with the _locked suffix and without the one
with _locked takes the
On Wed, 12 Feb 2014, Namjae Jeon wrote:
Date: Wed, 12 Feb 2014 11:28:35 +0900
From: Namjae Jeon linkinj...@gmail.com
To: Lukáš Czerner lczer...@redhat.com
Cc: v...@zeniv.linux.org.uk, da...@fromorbit.com, b...@sgi.com, ty...@mit.edu,
adilger.ker...@dilger.ca, j...@suse.cz,
On Tue, Feb 18, 2014 at 10:02 AM, Geert Uytterhoeven
ge...@linux-m68k.org wrote:
JFYI, when comparing v3.14-rc3[1] to v3.14-rc2[3], the summaries are:
- build errors: +17/-6
+ /scratch/kisskb/src/arch/powerpc/include/asm/floppy.h: error:
'isa_bridge_pcidev' undeclared (first use in this
Hi,
I have just noticed that ppc has RECLAIM_DISTANCE reduced to 10 set by
56608209d34b (powerpc/numa: Set a smaller value for RECLAIM_DISTANCE to
enable zone reclaim). The commit message suggests that the zone reclaim
is desirable for all NUMA configurations.
History has shown that the zone
Hello,
The Project is about the exportation of 100,000 barrels of Light CrudeOil daily
out from Iraq to Turkey through my client's company in Iraq
at the rate of $92.00 a barrel. This amount to $9,200,000 daily. I ask for your
support as a foreigner to handle this business project with my
On 02/17/2014 06:36 AM, Rafael J. Wysocki wrote:
From: Rafael J. Wysocki rafael.j.wyso...@intel.com
Reduce the rampant usage of goto and the indentation level in
cpufreq_set_policy() to improve the readability of that code.
No functional changes should result from that.
Signed-off-by:
Il 17/01/2014 20:52, Radim Krčmář ha scritto:
We should open NMI window right after an iret, but SVM exits before it.
We wanted to single step using the trap flag and then open it.
(or we could emulate the iret instead)
We don't do it since commit 3842d135ff2 (likely), because the iret exit
Il 22/01/2014 13:03, Paolo Bonzini ha scritto:
Il 22/01/2014 06:29, Liu, Jinsong ha scritto:
These patches are version 3 to enalbe Intel MPX for KVM.
Version 1:
* Add some Intel MPX definiation
* Fix a cpuid(0x0d, 0) exposing bug, dynamic per XCR0 features
enable/disable
* vmx and msr
Hello,
On (02/18/14 15:04), Minchan Kim wrote:
Hello Sergey,
On Thu, Feb 13, 2014 at 08:43:18PM +0300, Sergey Senozhatsky wrote:
This patchset introduces zcomp compression backend abstraction
adding ability to support compression algorithms other than LZO;
support for multi compression
On Tue, Feb 18, 2014 at 09:47:29AM +0900, Mark Brown wrote:
On Mon, Feb 17, 2014 at 04:51:32PM +, Charles Keepax wrote:
+ snd_soc_dapm_force_enable_pin_locked(codec-dapm, CP2);
+ snd_soc_dapm_force_enable_pin_locked(codec-dapm, SYSCLK);
+
+
Hello,
On (02/18/14 05:10), Minchan Kim wrote:
On Thu, Feb 13, 2014 at 08:43:19PM +0300, Sergey Senozhatsky wrote:
ZRAM performs direct LZO compression algorithm calls, making it the one and
only option. Introduce compressing backend abstraction zcomp in order to
support multiple
On Mon, 17 Feb 2014 16:29:40 +, Ben Dooks ben.do...@codethink.co.uk wrote:
The of_mdiobus_register_phy() is not setting phy-irq this causing
some drivers to incorrectly assume that the PHY does not have an
IRQ associated with it or install an interrupt handler for the
PHY.
Simplify the
Paolo Bonzini wrote:
Il 22/01/2014 13:03, Paolo Bonzini ha scritto:
Il 22/01/2014 06:29, Liu, Jinsong ha scritto:
These patches are version 3 to enalbe Intel MPX for KVM.
Version 1:
* Add some Intel MPX definiation
* Fix a cpuid(0x0d, 0) exposing bug, dynamic per XCR0 features
Hi,
setserial has low_latency option which should minimize receive latency
(scheduler delay). AFAICT it is used if someone talk to external device
via RS-485/RS-232 and need to have quick requests and responses . On
kernel this feature was implemented by direct tty processing from
interrupt
On Mon, 17 Feb 2014 17:13:07 +0100, Arnd Bergmann a...@arndb.de wrote:
On Monday 17 February 2014 15:54:19 Grant Likely wrote:
On Wed, 12 Feb 2014 11:20:00 -0700, Jason Gunthorpe
jguntho...@obsidianresearch.com wrote:
On Wed, Feb 12, 2014 at 12:45:54PM -0500, Jason Cooper wrote:
On 18/02/14 09:30, Grant Likely wrote:
On Mon, 17 Feb 2014 16:29:40 +, Ben Dooks ben.do...@codethink.co.uk wrote:
The of_mdiobus_register_phy() is not setting phy-irq this causing
some drivers to incorrectly assume that the PHY does not have an
IRQ associated with it or install an interrupt
Hi Sudeep,
Please have a look at these two commits which should describe why things
are as they are on s390:
881730ad365130f64b5c70c40904b04eb3b79de3
s390/cache: expose cpu cache topology via sysfs
6668022c7bde3fdc96d3d257294a7216c7a46829
s390/cache: add cpu cache information to
On Tue, Feb 18, 2014 at 10:05:49AM +0100, Lukáš Czerner wrote:
On Wed, 12 Feb 2014, Namjae Jeon wrote:
Date: Wed, 12 Feb 2014 11:28:35 +0900
From: Namjae Jeon linkinj...@gmail.com
To: Lukáš Czerner lczer...@redhat.com
Cc: v...@zeniv.linux.org.uk, da...@fromorbit.com, b...@sgi.com,
On 17/02/2014 19:19, Ezequiel Garcia wrote:
On Mon, Feb 17, 2014 at 04:59:01PM +0100, Gregory CLEMENT wrote:
[..]
Right. If you think it adds a regression, then that's a perfectly valid
reasons
for nacking.
However, I'd like to double-check we have such a regression. I guess you're
On Tue 18-02-14 12:55:38, Raghavendra K T wrote:
Currently max_sane_readahead() returns zero on the cpu having no local memory
node
which leads to readahead failure. Fix the readahead failure by returning
minimum of (requested pages, 512). Users running application on a memory-less
cpu
2014-02-18 18:05 GMT+09:00, Lukáš Czerner lczer...@redhat.com:
On Wed, 12 Feb 2014, Namjae Jeon wrote:
Date: Wed, 12 Feb 2014 11:28:35 +0900
From: Namjae Jeon linkinj...@gmail.com
To: Lukáš Czerner lczer...@redhat.com
Cc: v...@zeniv.linux.org.uk, da...@fromorbit.com, b...@sgi.com,
Nothing cares about ACPI_PROCFS. This has been the case since v2.6.38.
This Kconfig symbol serves no purpose and its help text is now
misleading. It can safely be removed. If this symbol would be needed
again in the future it can be readded in a commit that adds code that
actually uses it.
spin_lock's there. Maybe we can create WQ_HIGHPRI workqueue and schedule
flush_to_ldisc() work there. Or perhaps users that need to low latency,
should switch to thread irq and prioritize serial irq to meat
retirements. Anyway setserial low_latency is now broken and all who use
this feature
As result of deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range() and pci_enable_msix_range()
interfaces.
Signed-off-by: Alexander Gordeev agord...@redhat.com
Cc:
As result of deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range() and pci_enable_msix_range()
interfaces.
Signed-off-by: Alexander Gordeev agord...@redhat.com
Cc:
As result of deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range() and pci_enable_msix_range()
interfaces.
Signed-off-by: Alexander Gordeev agord...@redhat.com
Cc:
There is no need to call pci_disable_msix() in case
the previous call to pci_enable_msix() failed
Signed-off-by: Alexander Gordeev agord...@redhat.com
Cc: Casey Leedom lee...@chelsio.com
Cc: net...@vger.kernel.org
Cc: linux-...@vger.kernel.org
---
.../net/ethernet/chelsio/cxgb4vf/cxgb4vf_main.c
From: Sagar Kamble sagar.a.kam...@intel.com
With this patch we allow larger cursor planes of sizes 128x128
and 256x256. Planning to extend kms_cursor_crc test for verifying
these larger planes.
Cc: Daniel Vetter daniel.vet...@ffwll.ch
Cc: Jani Nikula jani.nik...@linux.intel.com
Cc: David Airlie
As result of deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range() and pci_enable_msix_range()
interfaces.
Signed-off-by: Alexander Gordeev agord...@redhat.com
Cc:
As result of deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range() and pci_enable_msix_range()
interfaces.
Signed-off-by: Alexander Gordeev agord...@redhat.com
Cc:
On Fri, 2014-02-14 at 11:11 -0800, Yinghai Lu wrote:
On Fri, Feb 14, 2014 at 7:46 AM, Steven Newbury st...@snewbury.org.uk wrote:
Oh, never mind! I didn't notice pref_bar has been renamed to
assign_pref_bars. It's working now! :)
There's no pci bridge/bus hotplug though. Docking doesn't
As result of deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range() and pci_enable_msix_range()
interfaces.
Signed-off-by: Alexander Gordeev agord...@redhat.com
Cc:
As result of deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range() and pci_enable_msix_range()
interfaces.
Cc: e1000-de...@lists.sourceforge.net
Cc:
As result of deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range() and pci_enable_msix_range()
interfaces.
Signed-off-by: Alexander Gordeev agord...@redhat.com
Cc:
As result of deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range() and pci_enable_msix_range()
interfaces.
Signed-off-by: Alexander Gordeev agord...@redhat.com
Cc:
As result of deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range() and pci_enable_msix_range()
interfaces.
Signed-off-by: Alexander Gordeev agord...@redhat.com
Cc:
As result of deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range() and pci_enable_msix_range()
interfaces.
Signed-off-by: Alexander Gordeev agord...@redhat.com
Cc:
As result of deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range() and pci_enable_msix_range()
interfaces.
Signed-off-by: Alexander Gordeev agord...@redhat.com
Cc:
As result of deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range() and pci_enable_msix_range()
interfaces.
Signed-off-by: Alexander Gordeev agord...@redhat.com
Cc:
As result of deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range() and pci_enable_msix_range()
interfaces.
Signed-off-by: Alexander Gordeev agord...@redhat.com
Cc:
As result of deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range() and pci_enable_msix_range()
interfaces.
Signed-off-by: Alexander Gordeev agord...@redhat.com
Cc:
As result of deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range() and pci_enable_msix_range()
interfaces.
Signed-off-by: Alexander Gordeev agord...@redhat.com
Cc:
Signed-off-by: Alexander Gordeev agord...@redhat.com
Cc: David S. Miller da...@davemloft.net
Cc: Patrick McHardy ka...@trash.net
Cc: net...@vger.kernel.org
Cc: linux-...@vger.kernel.org
---
drivers/net/ethernet/nvidia/forcedeth.c | 22 ++
1 files changed, 14 insertions(+), 8
Signed-off-by: Alexander Gordeev agord...@redhat.com
Cc: Shahed Shaikh shahed.sha...@qlogic.com
Cc: Jitendra Kalsaria jitendra.kalsa...@qlogic.com
Cc: Ron Mercer ron.mer...@qlogic.com
Cc: linux-dri...@qlogic.com
Cc: net...@vger.kernel.org
Cc: linux-...@vger.kernel.org
---
As result of deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range() and pci_enable_msix_range()
interfaces.
Signed-off-by: Alexander Gordeev agord...@redhat.com
Cc:
As result of deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range() and pci_enable_msix_range()
interfaces.
Signed-off-by: Alexander Gordeev agord...@redhat.com
Cc:
This update cleans up the MSI-X/MSI enablement code, fixes
vmxnet3_acquire_msix_vectors() invalid return values and
enables a dead code in case VMXNET3_LINUX_MIN_MSIX_VECT
MSI-X vectors were allocated.
Signed-off-by: Alexander Gordeev agord...@redhat.com
Cc: Shreyas Bhatewara
As result of deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range() and pci_enable_msix_range()
interfaces.
Signed-off-by: Alexander Gordeev agord...@redhat.com
Cc:
On Mon, 2014-02-17 at 09:43 -0500, Konrad Rzeszutek Wilk wrote:
On Mon, Feb 17, 2014 at 02:03:17PM +0100, Paul Bolle wrote:
On Mon, 2014-02-17 at 07:23 -0500, Konrad Rzeszutek Wilk wrote:
On Feb 16, 2014 3:07 PM, Paul Bolle pebo...@tiscali.nl wrote:
Please look in the grub git tree. They
As result of deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range() and pci_enable_msix_range()
interfaces.
Signed-off-by: Alexander Gordeev agord...@redhat.com
Cc:
As result of deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range() and pci_enable_msix_range()
interfaces.
Signed-off-by: Alexander Gordeev agord...@redhat.com
Cc:
On Tue, 18 Feb 2014, Alexander Gordeev wrote:
As result of deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range() and pci_enable_msix_range()
interfaces.
looks
Ahoy!
Debugging S3 aka suspend produces 'WARNINGS':
Steps to Reproduce:
# echo core /sys/power/pm_test
# cat /sys/power/pm_test
none [core] processors platform devices freezer
# echo mem /sys/power/state
Results:
- dmesg-3.14.0-0.rc3.git0.1.fc21.x86_64+debug-pm_test-core.diff
Signed-off-by: Alexander Gordeev agord...@redhat.com
Cc: Himanshu Madhani himanshu.madh...@qlogic.com
Cc: Rajesh Borundia rajesh.borun...@qlogic.com
Cc: Shahed Shaikh shahed.sha...@qlogic.com
Cc: linux-dri...@qlogic.com
Cc: net...@vger.kernel.org
Cc: linux-...@vger.kernel.org
---
As result of deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range() and pci_enable_msix_range()
interfaces.
Signed-off-by: Alexander Gordeev agord...@redhat.com
Cc:
As result of deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range() and pci_enable_msix_range()
interfaces.
Signed-off-by: Alexander Gordeev agord...@redhat.com
Cc:
On Mon, Feb 10, 2014 at 10:17:59PM +, Drew Richardson wrote:
While adding CPU on/offlining support during perf captures I get an
Oops both on ARM as well as my desktop x86_64. Below is a small
program that duplicates the issue.
[...]
FWIW I can reproduce this easily with -rc3 on my x86
As result of deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range() and pci_enable_msix_range()
interfaces.
Signed-off-by: Alexander Gordeev agord...@redhat.com
Cc:
As result of deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range() and pci_enable_msix_range()
interfaces.
Signed-off-by: Alexander Gordeev agord...@redhat.com
Cc:
As result of deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range() and pci_enable_msix_range()
interfaces.
Signed-off-by: Alexander Gordeev agord...@redhat.com
Cc:
As result of deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range() and pci_enable_msix_range()
interfaces.
Signed-off-by: Alexander Gordeev agord...@redhat.com
Cc:
As result of deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range() and pci_enable_msix_range()
interfaces.
Signed-off-by: Alexander Gordeev agord...@redhat.com
Cc:
Signed-off-by: Alexander Gordeev agord...@redhat.com
Cc: David S. Miller da...@davemloft.net
Cc: Patrick McHardy ka...@trash.net
Cc: net...@vger.kernel.org
Cc: linux-...@vger.kernel.org
---
drivers/net/ethernet/nvidia/forcedeth.c | 12 ++--
1 files changed, 6 insertions(+), 6
On 18.02.2014 02:02, Rafael J. Wysocki wrote:
On Monday, February 10, 2014 02:00:11 PM Tomasz Nowicki wrote:
Whenever we register ISA interrupt or not, we need to free the IRQ routing
table entry.
Signed-off-by: Tomasz Nowicki tomasz.nowi...@linaro.org
---
drivers/acpi/pci_irq.c |1 +
1
As result of deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range() and pci_enable_msix_range()
interfaces.
Signed-off-by: Alexander Gordeev agord...@redhat.com
Cc:
On Tue, 18 Feb 2014 08:50:13 +0900
Mark Brown broo...@kernel.org wrote:
On Mon, Feb 17, 2014 at 03:35:18PM +, One Thousand Gnomes wrote:
We've identified a correct working approach which is to simply add a
CONFIG entry to the ARM tree and a few ifdefs to the problem drivers to
make
From: Chew, Chiau Ee chiau.ee.c...@intel.com
Intel BayTrail LPSS consists of two PWM controllers which can
be enumerated from ACPI namespace. This change will cause
platform device objects to be created for Intel BayTrail PWM
controllers which will allow the pwm-lpss driver to bind to them
and
There is no need to call pci_disable_msix() in case
the previous call to pci_enable_msix() failed
Signed-off-by: Alexander Gordeev agord...@redhat.com
Cc: Santosh Raspatur sant...@chelsio.com
Cc: net...@vger.kernel.org
Cc: linux-...@vger.kernel.org
---
On Tue, Feb 18, 2014 at 01:54:20PM +0800, Aaron Lu wrote:
+ {
+ .callback = video_set_use_native_backlight,
+ .ident = HP EliteBook 2013 models,
+ .matches = {
+ DMI_MATCH(DMI_SYS_VENDOR, Hewlett-Packard),
+ DMI_MATCH(DMI_PRODUCT_NAME, HP EliteBook ),
On 17 February 2014 03:34, Xishi Qiu qiuxi...@huawei.com wrote:
If we want to debug the kernel memory, we should turn on CONFIG_KMEMCHECK
and rebuild the kernel. This always takes a long time and sometimes
impossible, e.g. users don't have the kernel source code or the code
is different from
Linus,
please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/jikos/hid.git for-linus
to receive:
- fixes for several bugs in incorrect allocations of buffers by David
Herrmann and Benjamin Tissoires.
- support for a few new device IDs by Archana Patni, Benjamin Tissoires,
Il 17/02/2014 21:24, Alex Williamson ha scritto:
VFIO now has support for using the IOMMU_CACHE flag and a mechanism
for an external user to test the current operating mode of the IOMMU.
Add support for this to the kvm-vfio pseudo device so that we only
register noncoherent DMA when necessary.
On 14/02/14 14:25, Marek Belisko wrote:
Signed-off-by: Marek Belisko ma...@goldelico.com
I wonder how this got missed. However, for those data elements to be useful,
you will
need to read them somewhere in the driver I think (if there is any magic
that puts this in the relevant i2c
2014-02-11 13:58 GMT+01:00 Daniel Lezcano daniel.lezc...@linaro.org:
On 02/10/2014 11:10 AM, Ivan Khoronzhuk wrote:
Add broadcast clock-event device for the Keystone arch.
The timer can be configured as a general-purpose 64-bit timer,
dual general-purpose 32-bit timers. When configured as
On 17/02/14 19:14, Grant Likely wrote:
On Tue, 11 Feb 2014 07:56:33 -0600, Rob Herring robherri...@gmail.com wrote:
On Tue, Feb 11, 2014 at 5:45 AM, Philipp Zabel p.za...@pengutronix.de
wrote:
From: Philipp Zabel philipp.za...@gmail.com
This patch moves the parsing helpers used to
Propagate the error value returned by the function instead.
Signed-off-by: Sachin Kamat sachin.ka...@linaro.org
---
drivers/regulator/ti-abb-regulator.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/regulator/ti-abb-regulator.c
kzalloc prints its own OOM message upon failure.
Signed-off-by: Sachin Kamat sachin.ka...@linaro.org
---
drivers/regulator/max8973-regulator.c |4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/regulator/max8973-regulator.c
b/drivers/regulator/max8973-regulator.c
Propagate the error value returned by the function instead.
Signed-off-by: Sachin Kamat sachin.ka...@linaro.org
---
drivers/regulator/wm8350-regulator.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/regulator/wm8350-regulator.c
This is a simple DM target supporting compression for SSD only. Under layer SSD
must support 512B sector size, the target only supports 4k sector size.
Disk layout:
|super|...meta...|..data...|
Store unit is 4k (a block). Super is 1 block, which stores meta and data size
and compression
Propagate the error value returned by the function instead.
Signed-off-by: Sachin Kamat sachin.ka...@linaro.org
---
drivers/regulator/lp3971.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/regulator/lp3971.c b/drivers/regulator/lp3971.c
index
kzalloc prints its own OOM message upon failure.
Signed-off-by: Sachin Kamat sachin.ka...@linaro.org
---
drivers/regulator/act8865-regulator.c |5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/drivers/regulator/act8865-regulator.c
b/drivers/regulator/act8865-regulator.c
kzalloc prints its own OOM message upon failure.
Signed-off-by: Sachin Kamat sachin.ka...@linaro.org
---
drivers/regulator/88pm800.c |4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/regulator/88pm800.c b/drivers/regulator/88pm800.c
index
kzalloc prints its own OOM message upon failure.
Signed-off-by: Sachin Kamat sachin.ka...@linaro.org
---
drivers/regulator/arizona-ldo1.c |4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/regulator/arizona-ldo1.c b/drivers/regulator/arizona-ldo1.c
index
kzalloc prints its own OOM message upon failure.
Signed-off-by: Sachin Kamat sachin.ka...@linaro.org
---
drivers/regulator/as3711-regulator.c |4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/regulator/as3711-regulator.c
b/drivers/regulator/as3711-regulator.c
Propagate the error value returned by the function instead.
Signed-off-by: Sachin Kamat sachin.ka...@linaro.org
---
drivers/regulator/da9055-regulator.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/regulator/da9055-regulator.c
Propagate the error values returned by the function instead.
Signed-off-by: Sachin Kamat sachin.ka...@linaro.org
---
drivers/regulator/da9063-regulator.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/regulator/da9063-regulator.c
1 - 100 of 2250 matches
Mail list logo
