On Fri, 2015-07-31 at 17:38 -0400, Mike Snitzer wrote:
> On Fri, Jul 31 2015 at 5:19pm -0400,
> Ming Lin wrote:
>
> > On Fri, Jul 31, 2015 at 12:23 PM, Mike Snitzer wrote:
> > > On Mon, Jul 06 2015 at 3:44P -0400,
> > > Ming Lin wrote:
> > >
> > >> From: Kent Overstreet
> > >>
> > >> The way
2015-08-01 15:21 GMT+09:00 Masahiro Yamada :
> 2015-07-31 23:31 GMT+09:00 Ian Campbell :
>> Commit 9ccd608070b6 "arm64: dts: add device tree for ARM SMM-A53x2 on
>> LogicTile Express 20MG" added a new dts file to arch/arm64 which
>> included "../../../../arm/boot/dts/vexpress-v2m-rs1.dtsi", i.e. a
Desnoyers ,"linux-...@vger.kernel.org"
,"linux-kernel@vger.kernel.org"
,Peter Zijlstra
Message-ID:
Let me see if I can unbury it - probably not until Monday, though.
On July 31, 2015 11:18:06 PM PDT, Josh Triplett wrote:
>On Fri, Jul 31, 2015 at 09:56:46PM -0700, H. Peter Anvin wrote:
>> On
2015-07-31 23:31 GMT+09:00 Ian Campbell :
> Commit 9ccd608070b6 "arm64: dts: add device tree for ARM SMM-A53x2 on
> LogicTile Express 20MG" added a new dts file to arch/arm64 which
> included "../../../../arm/boot/dts/vexpress-v2m-rs1.dtsi", i.e. a
> .dtsi supplied by arch/arm.
>
> Unfortunately th
On Fri, Jul 31, 2015 at 09:56:46PM -0700, H. Peter Anvin wrote:
> On 07/31/2015 09:32 PM, Josh Triplett wrote:
> >
> > Sure, agreed. But I really hope we don't create new kernel ABIs that
> > involve constructs like that.
> >
>
> It's worth noting I have pushed for auto-marshalling in general f
On Fri, Jul 31, 2015 at 12:37:31PM -0700, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.1.4 release.
> There are 267 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
Hugh Dickins wrote on Fri, Jul 31, 2015:
> On Fri, 31 Jul 2015, Linus Torvalds wrote:
>> I'd be more suspicious about other effects. For example, iot's not at
>> all obvious that the commit in question just changes the order of the
>> flags/inode field accesses, there are potentialy bigger changes
FYI, we noticed the below changes on
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/asm
commit b2c51106c7581866c37ffc77c5d739f3d4b7cbc9 ("x86/build: Fix detection of
GCC -mpreferred-stack-boundary support")
=
FYI, we noticed the below changes on
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
commit a46ad0f13bc32a9601f3c5dff43fafdc2c598814 ("Add WMI driver for
controlling AlienFX features on some Alienware products")
The following new message in kernel log may make end user c
FYI, we noticed the below changes on
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
commit 68905a14e49c97bf49dacd753e40ddd5b254e2ad ("staging: unisys: Add s-Par
visornic ethernet driver")
+--++-
These objects can be referenced concurrently throughout the driver, we
need a way to make sure threads can't delete them out from under each
other. This patch adds the refcount, and refactors the code to use it.
Additionally, we cannot iterate over the sas_device_list without
holding the lock, or
The fw_event_work struct is concurrently referenced at shutdown, so
add a refcount to protect it, and refactor the code to use it.
Additionally, refactor _scsih_fw_event_cleanup_queue() such that it
no longer iterates over the list without holding the lock, since
_firmware_event_work() concurrentl
Hello all,
This patchset attempts to address problems we've been having with
panics due to memory corruption from the mpt2sas driver.
Changes are noted in the individual patches, I realized putting them in the
cover was probably a bit confusing.
Thanks,
Calvin
Patches in this series:
[PATCH v
On 07/31/2015 09:32 PM, Josh Triplett wrote:
>
> Sure, agreed. But I really hope we don't create new kernel ABIs that
> involve constructs like that.
>
It's worth noting I have pushed for auto-marshalling in general for a
long time, not the least to get rid of the awful syscall(3) wrapper. I
e
On Fri, Jul 31, 2015 at 01:52:13PM -0700, Greg Kroah-Hartman wrote:
> On Fri, Jul 31, 2015 at 11:08:47AM +0530, Shraddha Barke wrote:
> > This patch fixes the following checkpatch.pl warning:
> >
> > WARNING: do not add new typedefs
> >
> > Signed-off-by: Shraddha Barke
> > ---
> > -typedef enu
On Fri, Jul 31, 2015 at 03:54:56PM -0700, Andy Lutomirski wrote:
> On Fri, Jul 31, 2015 at 3:08 PM, wrote:
> > On Fri, Jul 31, 2015 at 02:19:29PM -0700, Andy Lutomirski wrote:
> >> On Fri, Jul 31, 2015 at 1:59 PM, wrote:
> >> > Agreed. I think the proposal above would be a net improvement, but
On Fri, 31 Jul 2015, Hugh Dickins wrote:
> On Fri, 31 Jul 2015, Linus Torvalds wrote:
> >
> > So leave it running a while longer, but maybe it's 4bf46a272647 like
> > Dominique suspects. Although I don't see how that could trigger
> > anything either..
>
> I restarted with a slightly different ve
This patch refactors the return value of the driver *{get, set}
functions, since the driver default error value is -EIO.
All the functions now check for TOS_FAILURE, TOS_NOT_SUPPORTED and
TOS_SUCCESS.
On TOS_FAILURE a pr_err message is printed informing the user of the
error (no change was made t
Given that some features were added (/dev/toshiba_acpi device), some
clean-ups and minor (cosmetic) changes all over the driver code, bump
the driver version to 0.23 to reflect these overall changes.
Signed-off-by: Azael Avalos
---
drivers/platform/x86/toshiba_acpi.c | 2 +-
1 file changed, 1 in
A previous patch added explicit feature checks for support, *SUCCESS*
and *FAILURE to the HCI/SCI *{get, set} functions.
This patch removes some unnedded checks to the driver HCI/SCI
functions given that the default error return value is now set to
-EIO, there is no need to check for other error v
Currently the driver prints "*not supported" if any of the features
queried are in fact not supported, let us print the available
features instead.
This patch removes all instances pr_info printing "*not supported",
and add a new function called "print_supported_features", which will
print the ava
This patch changes the *available functions return type from int to
void.
The checks for support of their respective features are done inside
such functions and there was no need to return anything as we can
flag the queried feature as supported inside these functions.
The code was adapted accord
These patches changes the *{get, set} and *available functions default
return type, changes the printed messages of the supported features,
removes some unnedded checks and bumps the driver version to 0.23.
Changes since v2:
- Introduced a new patch to remove unnecessary checks instead of
crammi
On Fri, Jul 31, 2015 at 11:28:56AM +0200, Lukasz Pawelczyk wrote:
> On czw, 2015-07-30 at 16:30 -0500, Serge E. Hallyn wrote:
> > On Fri, Jul 24, 2015 at 12:04:35PM +0200, Lukasz Pawelczyk wrote:
> > > @@ -969,6 +982,7 @@ static int userns_install(struct nsproxy
> > > *nsproxy, struct ns_common *n
hi,
On Fri, 2015-07-31 at 14:37 +0100, Mark Rutland wrote:
> Hi,
>
> > > > + - mediatek,usb-wakeup: to access usb wakeup control register
> > >
> > > What exactly does this property imply?
> > >
> > There are some control registers for usb wakeup which are put in another
> > module, here to get
The initial version of this driver missed to add I2C ch6 pin-muxing.
Signed-off-by: Masahiro Yamada
---
drivers/pinctrl/uniphier/pinctrl-ph1-pro5.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/drivers/pinctrl/uniphier/pinctrl-ph1-pro5.c
b/drivers/pinctrl/uniphier/pinctrl-ph1-pro5.c
On Fri, 2015-07-24 at 20:46 +0800, Chenhui Zhao wrote:
> +static void mpc85xx_pmc_set_wake(struct device *dev, void *enable)
> {
> int ret;
> + u32 value[2];
> +
> + if (!device_may_wakeup(dev))
> + return;
> +
> + if (!pmc_regs) {
> + dev_err(dev, "%s: PM
On Fri, 2015-07-31 at 20:53 +0800, Chenhui Zhao wrote:
> diff --git a/arch/powerpc/kernel/fsl_booke_entry_mapping.S
> b/arch/powerpc/kernel/fsl_booke_entry_mapping.S
> index f22e7e4..32ec426f 100644
> --- a/arch/powerpc/kernel/fsl_booke_entry_mapping.S
> +++ b/arch/powerpc/kernel/fsl_booke_entry_m
On Fri, 2015-07-31 at 19:48 +0530, Kishon Vijay Abraham I wrote:
> Hi,
>
> On Friday 31 July 2015 05:55 PM, chunfeng yun wrote:
> > hi,
> > On Tue, 2015-07-28 at 11:17 +0530, Kishon Vijay Abraham I wrote:
> >> Hi,
> >>
> >> On Sunday 26 July 2015 08:21 AM, chunfeng yun wrote:
> >>> hi,
> >>> On We
Commit 3cc2dac5be3f ("drivers/video/fbdev/atyfb: Replace MTRR UC hole
with strong UC") introduces calls to ioremap_wc and ioremap_uc. This
causes build failures with ia64:allmodconfig. Map the missing
functions to ioremap_nocache.
Fixes: 3cc2dac5be3f ("drivers/video/fbdev/atyfb:
Replace MT
Commit 3cc2dac5be3f ("drivers/video/fbdev/atyfb: Replace MTRR UC hole
with strong UC") introduces calls to ioremap_wc and ioremap_uc. This
causes build failures with parisc:allmodconfig. Map the missing
functions to ioremap_nocache.
Fixes: 3cc2dac5be3f ("drivers/video/fbdev/atyfb:
Replace
Commit 3cc2dac5be3f ("drivers/video/fbdev/atyfb: Replace MTRR UC hole
with strong UC") introduces calls to ioremap_wc and ioremap_uc. This
causes build failures with alpha:allmodconfig. Map the missing functions
to ioremap_nocache.
Fixes: 3cc2dac5be3f ("drivers/video/fbdev/atyfb:
Replace M
The smp_store_release() is not a full barrier. In order to avoid missed
wakeup, we may need to add memory barrier around locked and cpu state
variables adding to complexity. As the chance of spurious wakeup is very
low, it is easier and safer to just do an unconditional kick at unlock
time.
Signed
Frequent CPU halting (vmexit) and CPU kicking (vmenter) lengthens
critical section and block forward progress. This patch implements
a kick-ahead mechanism where the unlocker will kick the queue head
vCPUs as well as up to four additional vCPUs next to the queue head
if they were halted. The kick
Like the native qspinlock, using the pending bit when it is lightly
loaded to acquire the lock is faster than going through the PV queuing
process which is even slower than the native queuing process. It also
avoids loading two additional cachelines (the MCS and PV nodes).
This patch adds the pend
The unlock function in queued spinlocks was optimized for better
performance on bare metal systems at the expense of virtualized guests.
For x86-64 systems, the unlock call needs to go through a
PV_CALLEE_SAVE_REGS_THUNK() which saves and restores 8 64-bit
registers before calling the real __pv_qu
v3->v4:
- Patch 1: add comment about possible racing condition in PV unlock.
- Patch 2: simplified the pv_pending_lock() function as suggested by
Davidlohr.
- Move PV unlock optimization patch forward to patch 4 & rerun
performance test.
v2->v3:
- Moved deferred kicking enablement patch
This patch enables the accumulation of kicking and waiting related
PV qspinlock statistics when the new QUEUED_LOCK_STAT configuration
option is selected. It also enables the collection of kicking and
wakeup latencies which have a heavy dependency on the CPUs being used.
The measured latencies for
In an overcommitted guest where some vCPUs have to be halted to make
forward progress in other areas, it is highly likely that a vCPU later
in the spinlock queue will be spinning while the ones earlier in the
queue would have been halted. The spinning in the later vCPUs is then
just a waste of prec
Most of the vCPU kickings are done on the locking side where the new
lock holder wake up the queue head vCPU to spin on the lock. However,
there are situations where it may be advantageous to defer the vCPU
kicking to when the lock holder releases the lock.
This patch enables the deferment of vCPU
On 07/31/2015 12:37 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.1.4 release.
There are 267 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be ma
On Thu, Jul 30, 2015 at 11:12 AM, Joe Stringer wrote:
> Expose the kernel connection tracker via OVS. Userspace components can
> make use of the "ct()" action, followed by "recirculate", to populate
> the conntracking state in the OVS flow key, and subsequently match on
> that state.
>
> Example O
On 07/31/2015 12:40 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.14.49 release.
There are 125 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be
On 07/31/2015 12:40 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.10.85 release.
There are 89 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be m
2015-08-01 5:15 GMT+08:00 Andy Lutomirski :
> On Fri, Jul 31, 2015 at 9:25 AM, cee1 wrote:
>> 2015-07-31 2:12 GMT+08:00 Andy Lutomirski :
>>>
>>> I find myself wondering whether an in-kernel *bus* is a good idea at
>>> all. Creating a bus that unprivileged programs are allowed to
>>> broadcast on
On Sat, Aug 01, 2015 at 02:28:06AM +0200, Stefan Agner wrote:
> Did the measurement:
>
> As is:
> ...
> [ 30.955675] mtd_speedtest: testing eraseblock write speed
> [ 143.349572] mtd_speedtest: eraseblock write speed is 4641 KiB/s
> [ 143.355606] mtd_speedtest: testing eraseblock read speed
>
Uses the gpiolib irqchip helpers. For this to work, the irq setup
function is called once per bank instead of once per device. Note
that all known uses of this block have a BCM7120 L2 interrupt
controller as a parent. Supports interrupts for all GPIOs.
In the IRQ handler, we check for raised IR
Some brcmstb GPIO controllers can be used to wake from suspend, so use
the de facto standard property 'wakeup-source' to mark the nodes of
controllers with that capability.
Also document interrupts-extended, which will be used for wakeup
handling because the interrupt parent for the wake IRQ is di
For wake from S5, we need to:
- register a reboot handler
- set wakeup capability before requesting IRQ so wakeup count is
incremented
- mask all GPIO IRQs and clear any pending interrupts during driver
probe to since no driver will yet be registered to handle any IRQs
carried over from boot
Need the aon_pm_l2_intc and irq0_aon_intc descriptions, so included
those as well.
Signed-off-by: Gregory Fong
---
New in v4.
arch/arm/boot/dts/bcm7445.dtsi | 50 ++
1 file changed, 50 insertions(+)
diff --git a/arch/arm/boot/dts/bcm7445.dtsi b/arch/arm/
Adds interrupt support for the GPIO controller (UPG GIO) used on Broadcom's
various BRCMSTB SoCs (BCM7XXX and others). For all existing hardware, this
block hooks up to the BCM7120 L2 IRQ controller and so will require
CONFIG_BCM7120_L2_IRQ=y.
New in v4:
- add nodes for the BRCMSTB GPIO controlle
Hi Scott,
On Jul 29, 2015, at 5:17 PM, Scott Feldman sfel...@gmail.com wrote:
> On Wed, Jul 29, 2015 at 12:14 PM, Vivien Didelot
> wrote:
>> Hi Scott, David,
>>
>> On Jul 29, 2015, at 2:28 PM, David da...@davemloft.net wrote:
>>
>>> From: Scott Feldman
>>> Date: Wed, 29 Jul 2015 00:31:44 -0700
On 07/31/2015 05:38 PM, Luis R. Rodriguez wrote:
From: "Luis R. Rodriguez"
Since alpha does not include asm-generic/io.h it would mean
alpha folks have to always carefully monitor asm-generic patches
and before they get merged make sure their own arch implementation
solution gets added. By usin
On Thursday, July 30, 2015 12:54:39 PM Mika Westerberg wrote:
> On Tue, Jul 14, 2015 at 01:16:12AM +0200, Rafael J. Wysocki wrote:
> > Hi,
> >
> > The size and complexity of drivers/acpi/scan.c has bothered me for quite
> > a while and since I'm working on a feature that will benefit from exposing
On Fri, 2015-06-26 at 15:44 +0800, yuantian.t...@freescale.com wrote:
> +static void rcpm_v1_set_ip_power(bool enable, u32 *mask)
> +{
> + if (enable)
> + setbits32(&rcpm_v1_regs->ippdexpcr, *mask);
> + else
> + clrbits32(&rcpm_v1_regs->ippdexpcr, *mask);
> +}
> +
>
On Fri, 2015-07-31 at 20:53 +0800, Chenhui Zhao wrote:
> In the last stage of deep sleep, software will trigger a Finite
> State Machine (FSM) to control the hardware precedure, such as
> board isolation, killing PLLs, removing power, and so on.
>
> When the system is waked up by an interrupt, the
From: "Luis R. Rodriguez"
Since alpha does not include asm-generic/io.h it would mean
alpha folks have to always carefully monitor asm-generic patches
and before they get merged make sure their own arch implementation
solution gets added. By using asm-generic/io.h alpha gets sensible
defaults, in
Hi Constantine,
On 07/31/2015 03:00 PM, Constantine Shulyupin wrote:
Please add a description of what you are doing here.
Signed-off-by: Constantine Shulyupin
---
The first trial.
Question: how to configure local temp4 (EnLTD)?
Allow "temp4_type = <3>" (EnLTD=3-2=1) or "temp4_enable = <1>" or
On 2015-08-01 01:47, Brian Norris wrote:
> On Sat, Aug 01, 2015 at 01:35:52AM +0200, Stefan Agner wrote:
>> On 2015-08-01 01:09, Brian Norris wrote:
>
>> >> +static int vf610_nfc_read_page(struct mtd_info *mtd, struct nand_chip
>> >> *chip,
>> >> + uint8_t *buf, int oob_re
On Fri, 2015-07-31 at 17:20 +0800, b29...@freescale.com wrote:
> From: Tang Yuantian
>
> Freescale E500MC and E5500 core-based platforms, like P4080, T1040,
> support disabling/enabling CPU dynamically.
> This patch adds this feature on those platforms.
>
> Signed-off-by: Chenhui Zhao
> Signed-
On Fri, 2015-07-31 at 17:20 +0800, b29...@freescale.com wrote:
> diff --git a/arch/powerpc/platforms/85xx/smp.c
> b/arch/powerpc/platforms/85xx/smp.c
> index 7f0dadb..8652a49 100644
> --- a/arch/powerpc/platforms/85xx/smp.c
> +++ b/arch/powerpc/platforms/85xx/smp.c
> @@ -189,15 +189,22 @@ static i
On Fri, 31 Jul 2015, Linus Torvalds wrote:
>
> I'd be more suspicious about other effects. For example, iot's not at
> all obvious that the commit in question just changes the order of the
> flags/inode field accesses, there are potentialy bigger changes there.
> For example, this part (in __d_obt
On Fri, Jul 31, 2015 at 04:28:02PM +0900, Chanwoo Choi wrote:
> Dear Greg,
>
> This is extcon-fixes pull request for v4.2-rc5. I added detailed description
> of this pull request on below. Please pull extcon with following fixes.
>
> Best Regards,
> Chanwoo Choi
>
> The following changes since c
Hello,
Here is another warning that was reported while I was retesting the SRP
initiator driver in kernel v4.2-rc4. Has anyone seen this before ?
Thanks,
Bart.
Jul 31 15:22:42 srp-ini multipathd: 66:32: mark as failed
Jul 31 15:22:42 srp-ini multipathd: mpatha: remaining active paths: 0
Jul 31
On Friday, July 31, 2015 5:00:43 PM PDT, Daniel Phillips wrote:
Note: Hirofumi's email is clear, logical and speaks to the
question. This branch of the thread is largely pointless, though
it essentially says the same thing in non-technical terms. Perhaps
your next response should be to Hirofumi,
From: Rafael J. Wysocki
After merging commit 712e960f0ee9 (ACPI / PM: Attach ACPI power
domain only once) with commit 1dcc3d3362b0 (ACPI / bus: Move ACPI
bus type registration) there is some duplicate code in
acpi_device_is_first_physical_node() and acpi_companion_match()
that can be moved to a s
On Fri, 31 Jul 2015, Dominique Martinet wrote:
> Hugh Dickins wrote on Fri, Jul 31, 2015:
> > It will indeed be weird and odd if it confirms that DCACHE_DISCONNECTED
> > revert is good. I agree that Dominique's 4bf46a272647 seems now more
> > likely, if still unlikely; but that was included in v4.
+ Rui
On Fri, 31 Jul 2015 08:07:45 -0700
Radivoje Jovanovic wrote:
> From: Radivoje Jovanovic
>
> Add support for Intel Skylake H/S
>
> Signed-off-by: Radivoje Jovanovic
> ---
> drivers/thermal/intel_powerclamp.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/thermal/inte
+Rui
On Fri, 31 Jul 2015 08:07:54 -0700
Radivoje Jovanovic wrote:
> From: Radivoje Jovanovic
>
> Add support for Intel Skylake u/y
>
> Signed-off-by: Radivoje Jovanovic
> ---
> drivers/thermal/intel_powerclamp.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/thermal/intel
On Friday, July 31, 2015 04:48:38 PM Radivoje Jovanovic wrote:
> On Sat, 01 Aug 2015 02:12:18 +0200
> Hi Rafael,
>
> "Rafael J. Wysocki" wrote:
> > On Friday, July 31, 2015 08:07:10 AM Radivoje Jovanovic wrote:
> > > From: Radivoje Jovanovic
> > >
> > > This patche enabled RAPL to support Intel
On Mon, Jul 20, 2015 at 02:29:58PM -0700, Dave Hansen wrote:
>
> (sorry for the spam, I screwed up the stable@ address).
>
> BTW, thanks to Kirill for doing this patch! He posted it to LKML
> but we need to ensure it is picked up for 4.2 and any -stable
> kernels where this commit is applied:
>
On Friday, July 31, 2015 3:27:12 PM PDT, David Lang wrote:
On Fri, 31 Jul 2015, Daniel Phillips wrote:
On Friday, July 31, 2015 11:29:51 AM PDT, David Lang wrote: ...
you weren't asking about any particular feature of Tux, you
were asking if we were still willing to push out stuff that
brea
On Fri, 2015-07-31 at 17:20 +0800, b29...@freescale.com wrote:
> @@ -71,7 +56,7 @@ static void mpc85xx_give_timebase(void)
> barrier();
> tb_req = 0;
>
> - mpc85xx_timebase_freeze(1);
> + qoriq_pm_ops->freeze_time_base(1);
freeze_time_base() takes a bool. Use true/fa
On Sat, 01 Aug 2015 02:12:18 +0200
Hi Rafael,
"Rafael J. Wysocki" wrote:
> On Friday, July 31, 2015 08:07:10 AM Radivoje Jovanovic wrote:
> > From: Radivoje Jovanovic
> >
> > This patche enabled RAPL to support Intel Skylake H/S
> >
> > Signed-off-by: Radivoje Jovanovic
>
> Jacob, is this se
On Sat, Aug 01, 2015 at 01:35:52AM +0200, Stefan Agner wrote:
> On 2015-08-01 01:09, Brian Norris wrote:
> >> +static int vf610_nfc_read_page(struct mtd_info *mtd, struct nand_chip
> >> *chip,
> >> + uint8_t *buf, int oob_required, int page)
> >> +{
> >> + int eccsize =
The sp810 clk driver is calling the clk consumer APIs from
clk_prepare ops to change the parent to a 1 MHz fixed rate clock
for each of the clocks that the driver provides. Use
assigned-clock-parents for this instead of doing it in the driver
to avoid using the consumer API in provider code. This a
The sp810 clk driver is calling the clk consumer APIs from
clk_prepare ops to change the parent to a 1 MHz fixed rate clock
for each of the clocks that the driver provides. Use
assigned-clock-parents for this instead of doing it in the driver
to avoid using the consumer API in provider code. This a
On Friday, July 31, 2015 08:07:10 AM Radivoje Jovanovic wrote:
> From: Radivoje Jovanovic
>
> This patche enabled RAPL to support Intel Skylake H/S
>
> Signed-off-by: Radivoje Jovanovic
Jacob, is this series fine by you?
> ---
> drivers/powercap/intel_rapl.c | 1 +
> 1 file changed, 1 insert
We're removing struct clk from the clk provider API. This code is
calling the consumer APIs to change the parent to a 1 MHz fixed
rate clock for each of the clocks that the driver provides. Move
to using the assigned-clock-parents DT property for this instead.
Because this is an ABI break, detect i
From: Oleg Drokin
These primitives are long deprecated and unused.
Signed-off-by: Oleg Drokin
---
drivers/staging/lustre/lustre/include/linux/lustre_compat25.h | 5 -
drivers/staging/lustre/lustre/llite/llite_lib.c | 5 +
drivers/staging/lustre/lustre/llite/vvp_io.c
From: Oleg Drokin
It's not really used anywhere.
Signed-off-by: Oleg Drokin
---
drivers/staging/lustre/lustre/include/linux/lustre_compat25.h | 4
1 file changed, 4 deletions(-)
diff --git a/drivers/staging/lustre/lustre/include/linux/lustre_compat25.h
b/drivers/staging/lustre/lustre/in
This patch set converts this code to use the assigned-clock-parents
property instead of doing some interesting stuff in the .prepare
op. I can route the dts patches through arm-soc but I'd like to take
the clk patch through clk tree because it removes some usage of the
struct clk based provider API
From: Oleg Drokin
SEEK_DATA and SEEK_HOLE are always defined in the kernel,
drop the definition checks
Signed-off-by: Oleg Drokin
---
drivers/staging/lustre/lustre/include/linux/lustre_compat25.h | 7 ---
1 file changed, 7 deletions(-)
diff --git a/drivers/staging/lustre/lustre/include/li
From: Oleg Drokin
They are not used anywhere, so safe to drop.
Signed-off-by: Oleg Drokin
---
.../lustre/lustre/include/linux/lustre_compat25.h | 31 --
1 file changed, 31 deletions(-)
diff --git a/drivers/staging/lustre/lustre/include/linux/lustre_compat25.h
b/drivers/s
From: Oleg Drokin
Get rid of ll_d_hlist* compat defines.
Signed-off-by: Oleg Drokin
---
drivers/staging/lustre/lustre/include/linux/lustre_compat25.h | 9 -
drivers/staging/lustre/lustre/llite/dcache.c | 3 +--
drivers/staging/lustre/lustre/llite/namei.c
From: Oleg Drokin
They are noop anyways.
Signed-off-by: Oleg Drokin
---
drivers/staging/lustre/lustre/include/linux/lustre_compat25.h | 5 -
drivers/staging/lustre/lustre/llite/dir.c | 4
2 files changed, 9 deletions(-)
diff --git a/drivers/staging/lustre/lustre/i
From: Oleg Drokin
This is take two for the compat stuff removal.
Oleg Drokin (6):
staging/lustre: Drop SEEK_* definition checks
staging/lustre: remove unused ll_quota_on and ll_quota_off
staging/lustre: Drop FMODE_UNSIGNED_OFFSET define
staging/lustre: Use hlist primitives directly
sta
Hello,
The warning below was triggered while I was testing SRP initiator changes on
top of v4.2-rc4. I don't think that this warning was triggered by my changes.
Has anyone seen this before ?
Thanks,
Bart.
Jul 31 16:02:37 srp-ini multipathd: mpatha: load table [0 5859375088 multipath
3 queue_i
[Added KVM lists and a couple relevant people]
On Fri, 2015-07-31 at 14:25 +0530, Hemant Kumar wrote:
> On 07/30/2015 03:52 AM, Scott Wood wrote:
> > On Wed, 2015-07-29 at 16:07 +0530, Hemant Kumar wrote:
> > > Hi Scott,
> > >
> > > On 07/17/2015 01:40 AM, Scott Wood wrote:
> > > > On Thu, 2015-0
Hi Brian,
On 2015-08-01 01:09, Brian Norris wrote:
>> +static inline int vf610_nfc_correct_data(struct mtd_info *mtd, uint8_t *dat)
>> +{
>> +struct vf610_nfc *nfc = mtd_to_nfc(mtd);
>> +u8 ecc_status;
>> +u8 ecc_count;
>> +int flip;
>> +
>> +ecc_status = __raw_readb(nfc->regs
On Jul 31, 2015, at 7:00 PM, Greg Kroah-Hartman wrote:
> On Thu, Jul 30, 2015 at 06:27:57PM -0400, gr...@linuxhacker.ru wrote:
>> From: Oleg Drokin
>>
>> SEEK_DATA and SEEK_HOLE are always defined in the kernel,
>> drop the definition checks
> This code removal doesn't match up with the changel
On Friday, July 31, 2015 12:46:17 PM Len Brown wrote:
> From: Len Brown
>
> The Linux kernel suspend path has traditionally invoked sys_sync()
> before freezing user threads.
>
> But sys_sync() can be expensive, and some user-space OS's do not want
> the kernel to pay the cost of sys_sync() on e
On Friday, July 31, 2015 12:02:36 PM Len Brown wrote:
> On Wed, Jul 22, 2015 at 4:55 AM, Oliver Neukum wrote:
> > On Wed, 2015-07-22 at 03:25 +0200, Rafael J. Wysocki wrote:
> >> And it is more pain for me to change the user space on each of them to
> >> write to the new sysfs file on every boot t
On Thu, Jul 30, 2015 at 06:03:12PM +0100, David Vrabel wrote:
> Pages returned by alloc_xenballooned_pages() will be used for grant
> mapping which will call set_phys_to_machine() (in PV guests).
>
> Ballooned pages are set as INVALID_P2M_ENTRY in the p2m and thus may
> be using the (shared) missin
On 07/31/2015 02:30 AM, Xishi Qiu wrote:
> __free_one_page() will judge whether the the next-highest order is free,
> then add the block to the tail or not. So when we split large order block,
> add the small block to the tail, it will reduce fragment.
It's an interesting idea, but what does it d
On Thu, Jul 30, 2015 at 06:03:11PM +0100, David Vrabel wrote:
> Rename alloc_p2m() to xen_alloc_p2m_entry() and export it.
>
> This is useful for ensuring that a p2m entry is allocated (i.e., not a
> shared missing or identity entry) so that subsequent set_phys_to_machine()
> calls will require no
On Wed, 29 Jul 2015, Peter Zijlstra wrote:
On Wed, Jul 01, 2015 at 03:21:09PM -0700, Vikas Shivappa wrote:
+/*
+ * cbm_update_msrs() - Updates all the existing IA32_L3_MASK_n MSRs
+ * which are one per CLOSid except IA32_L3_MASK_0 on the current package.
+ */
+static void cbm_update_msrs(void
On Thu, Jul 30, 2015 at 06:03:10PM +0100, David Vrabel wrote:
> alloc_xenballooned_pages() is used to get ballooned pages to back
> foreign mappings etc. Instead of having to balloon out real pages,
> use (if supported) hotplugged memory.
>
> This makes more memory available to the guest and reduc
On Wed, 29 Jul 2015, Peter Zijlstra wrote:
On Wed, Jul 01, 2015 at 03:21:02PM -0700, Vikas Shivappa wrote:
+/*
+ * Temporary cpumask used during hot cpu notificaiton handling. The usage
+ * is serialized by hot cpu locks.
+ */
+static cpumask_t tmp_cpumask;
So the problem with this is that
On Thu, Jul 30, 2015 at 06:03:08PM +0100, David Vrabel wrote:
> Now that we track the total number of pages (included hotplugged
> regions), it is easy to determine if more memory needs to be
> hotplugged.
>
> Add a new BP_WAIT state to signal that the balloon process needs to
> wait until kicked b
1 - 100 of 1341 matches
Mail list logo
