> Semicolon is not necessary after the while statement.
>
> Signed-off-by: Sachin Kamat
> ---
> drivers/mfd/stmpe.c |3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/mfd/stmpe.c b/drivers/mfd/stmpe.c
> index 42ccd0544513..7145a89364fb 100644
> --- a/drivers/m
On Tue, Feb 4, 2014 at 1:40 PM, Stephan Mueller wrote:
> +CFLAGS_jitterentropy-base.o= -O0
Why? if really needed, this deserves a comment.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conver
On 02/04/2014 02:30 PM, Mark Brown wrote:
[...]
What does this actually do? No information is being passed in to the
core function here, not even any information on if it's starting or
stopping. Looking at the rest of the code I can't help thinking it
might be clearer to inline this possibly w
On Tue, Feb 04, 2014 at 01:22:12PM +0100, Peter Zijlstra wrote:
>
> The IA64 SDM V1-4.4.7 describes the memory ordering rules of IA64.
>
> It states that the cmpxchg.{rel,acq} really have release and acquire
> semantics and that xchg has acquire semantics.
>
> Despite this the ia64 atomic_t code
The current core of memcg charging is wild to say the least.
__mem_cgroup_try_charge which is in the center tries to be too clever
and it handles two independent cases
* when the memcg to be charged is known in advance
* when the given mm_struct is charged
The resulting callchains a
The current charge path might race with memcg offlining because holding
css reference doesn't neither prevent from task move to a different
group nor stop css offline. When a charging task is the last one in the
group and it is moved to a different group in the middle of the charge
the old memcg mi
An ancient comment tries to explain that a given mm might be NULL when a
task is migrated. It has been introduced by 8a9f3ccd (Memory controller:
memory accounting) along with other bigger changes so it is not much
more specific about the conditions.
Anyway, Even if the task is migrated to another
Hi Greg,
Patch 1 fixes SuperSpeed hub enumeration on beaglebone.
Patch 2 fixes remote-wakeup resume on beaglebone.
Felipe has Acked the 1st patch but still needs to Ack the 2nd one.
Patches are based on 3.14-rc1
cheers,
-roger
Ajay Kumar Gupta (1):
usb: musb: host: Fix SuperSpeed hub enumera
Johannes Weiner has pointed out that __mem_cgroup_try_charge duplicates
try_get_mem_cgroup_from_mm for charges which came without a memcg. The
only reason seems to be a tiny optimization when css_tryget is not
called if the charge can be consumed from the stock. Nevertheless
css_tryget is very chea
On Sun, Jan 26, 2014 at 07:45:36PM +0100, Jean-Francois Moine wrote:
> + /* load the optional CODEC */
> + of_platform_populate(np, NULL, NULL, &client->dev);
> +
Why is this using of_platform_populate()? That's a very odd way of
doing things.
> +config SND_SOC_TDA998X
> + tristate
memcg_kmem_newpage_charge doesn't always set the given memcg parameter.
Some early escape paths skip setting *memcg while
__memcg_kmem_newpage_charge down the call chain sets *memcg even if no
memcg is charged due to other escape paths.
The current code is correct because the memcg is initialized
This reverts commit 96f1c58d853497a757463e0b57fed140d6858f3a
because it is no longer needed after "memcg: make sure that memcg is not
offline when charging" which makes sure that no charges will be accepted
after mem_cgroup_reparent_charges has started.
Signed-off-by: Michal Hocko
---
mm/memcont
> Add a driver for the BCM59056 PMU multi-function device. The driver
> initially supports regmap initialization and instantiation of the
> voltage regulator device function of the PMU.
>
> Signed-off-by: Matt Porter
> Reviewed-by: Tim Kryger
> Reviewed-by: Markus Mayer
> ---
> drivers/mfd/Kco
During resume don't touch SUSPENDM/RESUME bits of POWER register
while restoring controller context. These bits might be changed
by the controller during resume operation and so will be different
than what they were during suspend.
e.g. SUSPENDM bit is set by software during USB global suspend but
(2014/02/04 21:07), Chen Gang wrote:
> On 02/04/2014 03:17 PM, Masami Hiramatsu wrote:
>> (2014/02/04 14:16), Chen Gang wrote:
>>> When CONFIG_KRETPROBES disabled, all *kretprobe* generic implementation
>>> are useless, so need move them to CONFIG_KPROBES enabled area.
>>>
>>> Now, *kretprobe* gene
Hi,
this is a second version of the series previously posted here:
http://marc.info/?l=linux-mm&m=138729515304263&w=2. It is based on
3.14-rc1 and I am still testing it but having another eyes on it would
be great because this piece of code is really tricky.
The first four patches are an attempt t
From: Ajay Kumar Gupta
Disables PING on status phase of control transfer.
PING token is not mandatory in status phase of control transfer
and so some high speed USB devices don't support it. If such devices
are connected to MUSB then they would not respond to PING token
causing delayed or failed
On 4 February 2014 12:29, Liviu Dudau wrote:
> On Mon, Feb 03, 2014 at 10:34:40PM +, Andrew Murray wrote:
>> On 3 February 2014 18:43, Liviu Dudau wrote:
>> > diff --git a/arch/arm64/include/asm/io.h b/arch/arm64/include/asm/io.h
>> > index 4cc813e..ce5bad2 100644
>> > --- a/arch/arm64/includ
On Tue, 04 Feb 2014 11:19:03 -0200
Mauro Carvalho Chehab wrote:
> Alan/Greg/Andrew/Rob,
>
> Not sure who is currently maintaining Documentation/devices.txt.
>
> We're needing to add support of a new type of V4L2 devices there.
>
> Could you please ack with the following patch? If this one is o
On Wed, Jan 29, 2014 at 01:47:54PM -0800, Bin Gao wrote:
> On Tue, Jan 28, 2014 at 02:04:07PM +0200, Mika Westerberg wrote:
> > Actually it does not work. I had the fallback path still in the patch when
> > I tried.
>
> Let's merge the ptach v2 then(continue on msr calibration retuning 0).
> All s
Hi Satish,
On 01/20/2014 06:33 AM, Satish Patel wrote:
> TI-USIM driver is a platform driver that provides a character
> driver interface to user applications.
>
> It allows user applications to call IOCTL's to
> perform smart card operations.
>
> Driver currently supports
> - ATR
> - T=0 & T=1
Hi Georgi,
On 01/30/2014 01:45 PM, Georgi Djakov wrote:
> This patchset adds basic support of the Secure Digital Host Controller
> Interface compliant controller found in Qualcomm chipsets.
>
> Tested with eMMC and various micro SD cards on APQ8074 Dragonboard.
[...]
> .../devicetree/bindings/
Alan/Greg/Andrew/Rob,
Not sure who is currently maintaining Documentation/devices.txt.
We're needing to add support of a new type of V4L2 devices there.
Could you please ack with the following patch? If this one is ok, I intend
to send via my tree together with the patch series that implements s
On Mon, Feb 03, 2014 at 06:45:04PM +0530, Manish Badarkhe wrote:
> Are there any review comments on this series?
Don't send contentless pings, especially not less than a week after you
sent the original patch. That's just more mail to read. You need to
allow a reasonable time for review, for no
On Tue, Feb 04, 2014 at 02:47:07PM +0200, Ville Syrjälä wrote:
> Hi x86 folks,
>
> Ping on getting the gen2 stolen memory early quirk patches into the x86
> tree.
>
> From our side Daniel and Chris both seemed happy with them, so I'd like
> to get them in at some point.
Yup, I think this is read
On Tue, 2014-02-04 at 08:03 +0100, Holger Schurig wrote:
> The macro udelay
> cannot handle large values because of lost-of-precision.
>
> IMHO udelay on ARM is broken, because it also cannot work with fast
> ARM processors (where bogomips >= 3355, which is in sight now). It's
> just not broken en
In some compilations the LM3630A and LP855X backlight drivers
fail like this:
drivers/built-in.o: In function `lm3630a_pwm_ctrl':
drivers/video/backlight/lm3630a_bl.c:168: undefined reference to `pwm_config'
drivers/video/backlight/lm3630a_bl.c:172: undefined reference to `pwm_disable'
drivers/vid
Hi,
with the previous release of the CPU Jitter RNG ([1]), concerns were raised on
the presence of entropy in the CPU execution timing. With this new version of
the CPU Jitter RNG, a new noise source based on memory access timings is now
added and the concerns raised before are addressed with a
The jitterentropy-base.c file implements the CPU Jitter RNG as
documented at http://www.chronox.de/jent/doc/CPU-Jitter-NPTRNG.html.
The associated header file makes the RNG available to the remainder
of the kernel.
The CPU Jitter RNG delivers entropy on demand. Therefore, it only
causes system ov
After successful initialization of the CPU Jitter RNG as part of the
Linux RNG, the two variables defining the memory size of the memory
chunk used for measuring memory access times are set. In case the Jitter
RNG does not successfully initialize, these variables are set to zero.
These two variab
The CPU Jitter RNG is included into random.c as a new noise source.
The noise source, however, works differently than all other noise
sources. The CPU Jitter RNG provides entropy on demand and thus, the
callback to obtain new data is implemented as a pull operation.
The pull operation is only exe
Hi x86 folks,
Ping on getting the gen2 stolen memory early quirk patches into the x86
tree.
>From our side Daniel and Chris both seemed happy with them, so I'd like
to get them in at some point.
--
Ville Syrjälä
Intel OTC
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel
Amend Makefile to allow the CPU Jitter RNG code to be statically
compiled.
Signed-off-by: Stephan Mueller
---
drivers/char/Makefile | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/char/Makefile b/drivers/char/Makefile
index 290fe5b..480c8f6 100644
--- a/drivers/cha
The two added sysctls are read/writable to allow administrators to
tweak the behavior of the CPU Jitter RNG. Normally, no tweaking is
neccessary. Though, some overly cautious users may set the default
to higher values.
The sysctls are found under /proc/sys/kernel/random with the following
files:
On 02/03/2014 06:10 AM, One Thousand Gnomes wrote:
On Sat, 01 Feb 2014 10:09:03 -0500
Peter Hurley wrote:
On 01/14/2014 11:24 AM, Pavel Roskin wrote:
Hi Alan,
Quoting One Thousand Gnomes :
Maybe we should unset the low_latency flag as soon as DMA fails? There
are two flags, one is state->
From: Jason Cooper
Unlike other build products in the Linux kernel, there is no 'make
*install' mechanism to put devicetree blobs in a standard place.
This commit adds a new 'dtbs_install' make target which copies all of
the dtbs into the INSTALL_DTBS_PATH directory. INSTALL_DTBS_PATH can be
set
The PCI part of the DesignWare I2C driver does a lot of things that are not
required anymore. For example drivers aren't supposed to handle PCI state
transitions themselves. This is all provided by the PCI bus core already.
In addition to that there is no point scheduling RPM suspend on driver's
i
On Friday 24 January 2014 10:21 PM, Balaji T K wrote:
To Resolve build failure seen with sh-allmodconfig:
include/linux/omap-dma.h:171:8: error: expected identifier before numeric
constant
make[4]: *** [drivers/mmc/host/omap_hsmmc.o] Error 1
due to CCR redefinition, move dmaengine cons
Commit c65c1877bd68 ("slub: use lockdep_assert_held") requires
remove_partial() to be called with n->list_lock held, but free_partial()
called from kmem_cache_close() on cache destruction does not follow this
rule, leading to a warning:
WARNING: CPU: 0 PID: 2787 at mm/slub.c:1536
__kmem_cache_s
Thanks!
On Tue, Feb 4, 2014 at 4:25 AM, Hugh Dickins wrote:
> On Tue, 4 Feb 2014, Kent Overstreet wrote:
>
>> Immutable biovecs changed the way biovecs are interpreted - drivers no
>> longer use bi_vcnt, they have to go by bi_iter.bi_size (to allow for
>> using part of an existing segment without
On Mon, Feb 03, 2014 at 10:34:40PM +, Andrew Murray wrote:
> On 3 February 2014 18:43, Liviu Dudau wrote:
> > diff --git a/arch/arm64/include/asm/io.h b/arch/arm64/include/asm/io.h
> > index 4cc813e..ce5bad2 100644
> > --- a/arch/arm64/include/asm/io.h
> > +++ b/arch/arm64/include/asm/io.h
> >
On Tue, 4 Feb 2014, Kent Overstreet wrote:
> Immutable biovecs changed the way biovecs are interpreted - drivers no
> longer use bi_vcnt, they have to go by bi_iter.bi_size (to allow for
> using part of an existing segment without modifying it).
>
> This breaks with discards and write_same bios,
The IA64 SDM V1-4.4.7 describes the memory ordering rules of IA64.
It states that the cmpxchg.{rel,acq} really have release and acquire
semantics and that xchg has acquire semantics.
Despite this the ia64 atomic_t code says that all atomic ops are fully
serialized, and its smp_mb__{before,after}
Voltage regulators are needed very early due to deferred probe
being incompatible with built-in USB gadget drivers. In order to
have the PMU driver available before USB UDC, make i2c available
during subsys_initcall.
Signed-off-by: Matt Porter
Reviewed-by: Tim Kryger
Reviewed-by: Markus Mayer
-
On Tue, 4 Feb 2014 16:03:14 +0400
Pavel Shilovsky wrote:
> 2014-02-01 Jeff Layton :
> > On Fri, 17 Jan 2014 14:07:06 +0400
> > Pavel Shilovsky wrote:
> >
> >> This patch adds 3 flags:
> >> 1) O_DENYREAD that doesn't permit read access,
> >> 2) O_DENYWRITE that doesn't permit write access,
> >> 3
Add a DT binding for the BCM59056 PMU. The binding inherits from
the generic regulator bindings.
Signed-off-by: Matt Porter
Reviewed-by: Tim Kryger
Reviewed-by: Markus Mayer
---
.../devicetree/bindings/regulator/bcm59056.txt | 37 ++
1 file changed, 37 insertions(+)
cr
Enable BCM59056 MFD and regulator drivers to manage voltage
regulators on BCM281xx platforms.
Signed-off-by: Tim Kryger
Signed-off-by: Matt Porter
Reviewed-by: Markus Mayer
---
arch/arm/configs/bcm_defconfig | 7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/arm/configs/bcm_defcon
Add a dtsi to support the BCM59056 PMU used by the BCM281xx family
of SoCs. Enable regulators for use with the dwc2 and sdhci on
bcm28155-ap.
Signed-off-by: Tim Kryger
Signed-off-by: Matt Porter
Reviewed-by: Markus Mayer
---
arch/arm/boot/dts/bcm28155-ap.dts | 41 ++
arch/arm/boot/dts
Add a driver for the BCM59056 PMU multi-function device. The driver
initially supports regmap initialization and instantiation of the
voltage regulator device function of the PMU.
Signed-off-by: Matt Porter
Reviewed-by: Tim Kryger
Reviewed-by: Markus Mayer
---
drivers/mfd/Kconfig |
The BCM59056 is a multi-function power management unit used with the
BCM281xx family of SoCs. This series adds an MFD and voltage regulator
driver to support the BCM59056. The bcm28155-ap DT support is updated
to enable use of regulators on the otg and sdhci peripherals.
Matt Porter (6):
i2c: bc
Add a regulator driver for the BCM59056 PMU voltage regulators.
The driver supports LDOs and DCDCs in normal mode only. There is
no support for low-power mode or power sequencing.
Signed-off-by: Matt Porter
Reviewed-by: Tim Kryger
Reviewed-by: Markus Mayer
---
drivers/regulator/Kconfig
On 02/04/2014 09:19 AM, Andreas Larsson wrote:
> On 2014-01-31 14:50, Andreas Larsson wrote:
>> On 2014-01-31 14:40, Marc Kleine-Budde wrote:
>>> On 01/31/2014 02:34 PM, Florian Vaussard wrote:
Hello,
(could someone with a SJA1000 on SPARC perform a functional test
to see if int
From: Josh Cartwright
Add support for handling 'shared-dma-pool' reserved-memory nodes using
dma exclusive driver (dma_alloc_coherent()).
Cc: Benjamin Herrenschmidt
Cc: Laura Abbott
Signed-off-by: Josh Cartwright
Signed-off-by: Marek Szyprowski
---
drivers/of/Kconfig |7 ++
Enable reserved memory initialization from device tree.
Cc: Benjamin Herrenschmidt
Cc: Laura Abbott
Signed-off-by: Marek Szyprowski
---
arch/arm/mm/init.c |3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/arm/mm/init.c b/arch/arm/mm/init.c
index 804d61566a53..ebafdb479410 100644
-
From: Josh Cartwright
Add support for handling 'shared-dma-pool' reserved-memory nodes using
Contiguous Memory Allocator driver.
Cc: Benjamin Herrenschmidt
Cc: Laura Abbott
Signed-off-by: Josh Cartwright
Signed-off-by: Marek Szyprowski
---
drivers/of/Kconfig |7
drive
From: Grant Likely
Reserved memory nodes allow for the reservation of static (fixed
address) regions, or dynamically allocated regions for a specific
purpose.
[joshc: Based on binding document proposed (in non-patch form) here:
http://lkml.kernel.org/g/20131030134702.19b57c40...@trevor.secretla
This patch adds device tree support for contiguous and reserved memory
regions defined in device tree.
Large memory blocks can be reliably reserved only during early boot.
This must happen before the whole memory management subsystem is
initialized, because we need to ensure that the given contigu
Hi all!
This is an updated version of the second attempt to add basic support
for dynamic allocation of memory reserved regions defined in device
tree.
The initial code for this feature were posted here [1], merged as commit
9d8eab7af79cb4ce2de5de39f82c455b1f796963 ("drivers: of: add
initializati
On Tue, Feb 04, 2014 at 10:09:44AM +, Arnd Bergmann wrote:
> On Monday 03 February 2014 22:17:44 Liviu Dudau wrote:
> > On Mon, Feb 03, 2014 at 07:31:31PM +, Arnd Bergmann wrote:
> > > Let's try to come up with nomenclature so we can talk about this better
> > >
> > > The ioport_resource is
On 02/04/2014 03:17 PM, Masami Hiramatsu wrote:
> (2014/02/04 14:16), Chen Gang wrote:
>> When CONFIG_KRETPROBES disabled, all *kretprobe* generic implementation
>> are useless, so need move them to CONFIG_KPROBES enabled area.
>>
>> Now, *kretprobe* generic implementation are all implemented in 2
On 02/04/2014 12:17 PM, 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.
On 02/04/2014 03:17 PM, Masami Hiramatsu wrote:
> (2014/02/04 14:16), Chen Gang wrote:
>> When CONFIG_KRETPROBES disabled, all *kretprobe* generic implementation
>> are useless, so need move them to CONFIG_KPROBES enabled area.
>>
>> Now, *kretprobe* generic implementation are all implemented in 2
2014-02-01 Jeff Layton :
> On Fri, 17 Jan 2014 14:07:06 +0400
> Pavel Shilovsky wrote:
>
>> This patch adds 3 flags:
>> 1) O_DENYREAD that doesn't permit read access,
>> 2) O_DENYWRITE that doesn't permit write access,
>> 3) O_DENYDELETE that doesn't permit delete or rename.
>>
>> Network filesyst
On 02/04/2014 12:17 PM, Alexander Gordeev wrote:
> When enabling MSI-X if a call to request_irq() failed
> pm8001_setup_msix() still returns success. This udate
> fixes the described misbehaviour.
>
> Signed-off-by: Alexander Gordeev
> Cc: xjtu...@gmail.com
> Cc: lindar_...@usish.com
> Cc: linux-
On 02/04/2014 12:04 AM, Andy Gross wrote:
[...]
+static int bam_dma_remove(struct platform_device *pdev)
+{
+ struct bam_device *bdev = platform_get_drvdata(pdev);
+ u32 i;
+
+ dma_async_device_unregister(&bdev->common);
+ of_dma_controller_free(pdev->dev.of_node);
The c
On Tuesday 04 February 2014 11:09:22 Liviu Dudau wrote:
> On Tue, Feb 04, 2014 at 08:44:36AM +, Arnd Bergmann wrote:
> > Well, I/O space never starts at physical zero in reality, so it is
> > broken in practice. The CONFIG_GENERIC_IOMAP option tries to solve
> > the problem of I/O spaces that
On 04/02/14 11:44, Mel Gorman wrote:
> Steven Noonan forwarded a users report where they had a problem starting
> vsftpd on a Xen paravirtualized guest, with this in dmesg:
>
[...]
>
> The issue could not be reproduced under an HVM instance with the same kernel,
> so it appears to be exclusive to
Sorry I forgot to add
Acked-by: Santosh Shilimkar
On 02/04/2014 01:30 PM, Ivan Khoronzhuk wrote:
This patch provides bindings for the 64-bit timer in the KeyStone
architecture devices. The timer can be configured as a general-purpose 64-bit
timer, dual general-purpose 32-bit timers. When config
Steven Noonan forwarded a users report where they had a problem starting
vsftpd on a Xen paravirtualized guest, with this in dmesg:
[ 60.654862] BUG: Bad page map in process vsftpd pte:800493b88165
pmd:e9cc01067
[ 60.654876] page:ea00124ee200 count:0 mapcount:-1 mapping: (null)
Reviewed-by: Stephen Boyd
Acked-by: Santosh shilimkar
On 02/04/2014 01:30 PM, 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 dual 32-bit
timers
Hi!
> --- a/drivers/power/Kconfig
> +++ b/drivers/power/Kconfig
> @@ -22,6 +22,19 @@ config POWER_SUPPLY_CHARGER
> drivers to keep the charging logic outside and the charger driver
> just need to abstract the charger hardware.
>
> +config POWER_SUPPLY_CHARGING_ALGO_PSE
> + bo
Hi!
> +Throttling configuration example:
> +
> +struct psy_throttle_state my_throttle_states[] = {
> +
> + /* Level 0: Limit charge current to 1500mA. Normal Level */
> + {
> + .throttle_action = PSY_THROTTLE_CC_LIMIT,
> + .throttle_val = 1500,
> + },
> +
> +
Hi!
> +#define DEV_MANUFACTURER "TI"
> +#define DEV_MANUFACTURER_NAME_SIZE 4
This is unneccessarily complicated for no reason. You copy "TI" to
struct, just so that ou can return pointer to the field on
get_property.
What about simply returning "TI" from get_property, without defines
and copyin
On Mon, 2014-02-03 at 22:40 +, Al Viro wrote:
> > >> +static int gfs2_vfs_permission(struct dentry *dentry, struct inode
> > >> *inode, int mask)
> > >> +{
> > >> + return gfs2_permission(inode, mask);
> > >> +}
> > >
> > > Er... You do realize that callers of gfs2_permission() tend to ha
This patch provides bindings for the 64-bit timer in the KeyStone
architecture devices. The timer can be configured as a general-purpose 64-bit
timer, dual general-purpose 32-bit timers. When configured as dual 32-bit
timers, each half can operate in conjunction (chain mode) or independently
(uncha
Add keystone timer entry to keystone device tree.
This 64-bit timer is used as backup clock event device.
Signed-off-by: Ivan Khoronzhuk
---
arch/arm/boot/dts/keystone-clocks.dtsi | 10 ++
arch/arm/boot/dts/keystone.dtsi| 7 +++
2 files changed, 17 insertions(+)
diff --git
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 dual 32-bit
timers, each half can operate in conjunction (chain mode) or
independently (unchained mode) of each other.
Sign
Add a broadcast timer64 based clockevent driver for keystone arch.
This driver uses timer in 64-bit general purpose mode as clock event
device.
Documentation:
http://www.ti.com/lit/ug/sprugv5a/sprugv5a.pdf
Based on
git://git.kernel.org/pub/scm/linux/kernel/git/ssantosh/linux-keystone.git
keys
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
Cc: Hiral Patel
Cc: Sum
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
Cc: Anil Gurumurthy
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
Cc: Naresh Kumar Inna
C
Signed-off-by: Alexander Gordeev
Cc: Anil Gurumurthy
Cc: Vijaya Mohan Guvva
Cc: linux-s...@vger.kernel.org
Cc: linux-...@vger.kernel.org
---
drivers/scsi/bfa/bfad.c | 18 --
1 files changed, 8 insertions(+), 10 deletions(-)
diff --git a/drivers/scsi/bfa/bfad.c b/drivers/scsi/
Signed-off-by: Alexander Gordeev
Cc: Naresh Kumar Inna
Cc: Arvind Bhushan
Cc: linux-s...@vger.kernel.org
Cc: linux-...@vger.kernel.org
---
drivers/scsi/csiostor/csio_isr.c |4 +---
1 files changed, 1 insertions(+), 3 deletions(-)
diff --git a/drivers/scsi/csiostor/csio_isr.c b/drivers/scsi
Signed-off-by: Alexander Gordeev
Cc: James Smart
Cc: linux-s...@vger.kernel.org
Cc: linux-...@vger.kernel.org
---
drivers/scsi/lpfc/lpfc_init.c |9 ++---
1 files changed, 6 insertions(+), 3 deletions(-)
diff --git a/drivers/scsi/lpfc/lpfc_init.c b/drivers/scsi/lpfc/lpfc_init.c
index 68c
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
Cc: xjtu...@gmail.com
Cc
Signed-off-by: Alexander Gordeev
Cc: Anil Ravindranath
Cc: linux-s...@vger.kernel.org
Cc: linux-...@vger.kernel.org
---
drivers/scsi/pmcraid.c |1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/drivers/scsi/pmcraid.c b/drivers/scsi/pmcraid.c
index be8ce54..c06af7f 100644
--
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
Cc: Lukasz Dorau
Cc: Ma
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
Cc: James Smart
Cc: lin
When enabling MSI-X if a call to request_irq() failed
pm8001_setup_msix() still returns success. This udate
fixes the described misbehaviour.
Signed-off-by: Alexander Gordeev
Cc: xjtu...@gmail.com
Cc: lindar_...@usish.com
Cc: linux-s...@vger.kernel.org
Cc: linux-...@vger.kernel.org
---
drivers/s
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.
Log message code 0x00c6 preserved, although it is reported
On Tue, Feb 04, 2014 at 03:58:09PM +0900, SeongJae Park wrote:
> Fix the pointer-integer size mismatch warning below:
> drivers/spi/spi-gpio.c: In function ‘spi_gpio_setup’:
> drivers/spi/spi-gpio.c:252:8: warning: cast from pointer to integer of
> different size [
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
Cc: Anil Ravindranath
C
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
Cc: Arvind Kumar
Cc: pv
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
Cc: Nagalakshmi Nandigam
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
Cc: Neela Syam Kolli
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
Cc: Vikas Chaudhary
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
Cc: Nagalakshmi Nandigam
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
Cc: "Stephen M. Cameron"
Signed-off-by: Alexander Gordeev
Cc: "Stephen M. Cameron"
Cc: iss_storage...@hp.com
Cc: linux-s...@vger.kernel.org
Cc: linux-...@vger.kernel.org
---
drivers/scsi/hpsa.c |5 +++--
1 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/scsi/hpsa.c b/drivers/scsi/hpsa.c
index 86
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: pv-driv...@vmware.com
Cc: iscsi-dri...@qlogic.com
Cc:
901 - 1000 of 1097 matches
Mail list logo
