This patch fixes a bug introduced by:
commit c05199e5a57a579fea1e8fa65e2b511ceb524ffc
Author: Kan Liang
Date: Tue Jan 20 04:54:25 2015 +
perf/x86/intel/uncore: Move uncore_box_init() out of driver initialization
It moves uncore_box_init() out of place but this meant that for desktop
* Elliott, Robert (Server Storage) wrote:
> > -Original Message-
> > From: Linux-nvdimm [mailto:linux-nvdimm-boun...@lists.01.org] On Behalf Of
> > Dan Williams
> > Sent: Friday, April 17, 2015 8:35 PM
> > To: linux-nvd...@lists.01.org
> > Subject: [Linux-nvdimm] [PATCH 00/21] ND:
On Wed, Apr 22, 2015 at 5:48 PM, Linus Torvalds
wrote:
>
> Conditional byte order is worse than silly - it's terminally stupid.
>
Hey, usually I write a long rant myself, but I was trying to keep it
to one bullet point for once in my life. Way to ruin it, geez.
Havoc
--
To unsubscribe from this
On Tue, Apr 21, 2015 at 10:50:15PM -0700, Christoph Hellwig wrote:
> On Mon, Apr 20, 2015 at 05:55:07PM +0200, Jan Kara wrote:
> > > Is that a good idea to export these symbols, given that lustre may be
> > > the only user?
> > Yes, it is a good idea.
>
> It was if lustre was in core code and
On Tue, Apr 21, 2015 at 10:20:07PM +0100, Al Viro wrote:
> I agree that unlazy_walk() attempted when walking a symlink ought to fail
> with -ECHILD; we can't legitimize the symlink itself, so once we are out
> of RCU mode, there's nothing to hold the inode of symlink (and its body)
> from getting
On Tue, Apr 21, 2015 at 01:33:38PM -0600, Jason Gunthorpe wrote:
> On Tue, Apr 21, 2015 at 09:30:55PM +0300, Jarkko Sakkinen wrote:
> > Enabled PPI interface to the character device sysfs directory accessible
> > both for 1.x and 2.0 devices.
> >
> > The ppi group is moved from the platform
Hi all,
Please do not add any v4.2 material to your linux-next included trees
until after v4.1-rc1 is released.
Changes since 20150422:
Removed tree: exec-domain (merged)
Non-merge commits (relative to Linus' tree): 1466
1311 files changed, 78501 insertions(+), 20869 deletions
Hi Linus,
Please pull.
Thx,
-Vineet
-->
he following changes since commit e42391cd048809d903291d07f86ed3934ce138e9:
Linux 4.0-rc6 (2015-03-29 15:26:31 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/vgupta/arc.git/
Hi,
On Wed, 2015-04-22 at 22:42 +0200, Jiri Kosina wrote:
> Hi,
>
> I've been running current Linus' tree and have been getting system lockups
> frequently. After a few "silent" lockups, I was able to obtain a dmesg
> before the machine turned dead again (wifi stopped working shortly before
AFAIK the PAPR document which defines the virtual device interface used by
the ibmveth driver doesn't specify a specific maximum MTU. So, in the
ibmveth driver, the maximum allowed MTU is determined by the maximum
allocated buffer size of 64k (corresponding to one page in the common case)
minus
Any suggestions on this?
On Thursday 16 April 2015 04:28 PM, Shreyas B. Prabhu wrote:
> kvm_no_guest function calls power7_wakeup_loss to put the thread into
> the deepest supported idle state. power7_wakeup_loss is defined in
> arch/powerpc/kernel/idle_power7.S, which is compiled only when
On (04/23/15 11:23), Minchan Kim wrote:
[..]
> > +static int zram_exit_cb(int id, void *ptr, void *data)
>
> trivial: I prefer remove to exit.
>
ok.
> > +{
> > + zram_remove(ptr);
> > + return 0;
> > +}
> >
> > - kfree(zram_devices);
> > +static void destroy_devices(void)
> > +{
> > +
--
Dear Valued Customer,
Apply for personal and business loans with EC finance today on a fixed
interest rate of 3.9%.You can as well consolidate your debts within maximum 24
working hours.Open attached file for details.
Regards,
EC Finance Pty Ltd
(Online Application Center).
Welcome To
On (04/23/15 11:29), Minchan Kim wrote:
> On Thu, Apr 16, 2015 at 08:55:50PM +0900, Sergey Senozhatsky wrote:
> > Device reset currently includes two steps:
> > a) holding ->bd_mutex we ensure that there are no device users
> > (bdev->bd_openers)
> >
> > b) and "internal" part (executed under
On (04/23/15 11:36), Minchan Kim wrote:
> Date: Thu, 23 Apr 2015 11:36:36 +0900
> From: Minchan Kim
> To: Sergey Senozhatsky
> Cc: Andrew Morton , Nitin Gupta
> , linux-kernel@vger.kernel.org, Sergey Senozhatsky
>
> Subject: Re: [PATCHv2 06/10] zram: remove max_num_devices limitation
>
On (04/23/15 11:38), Minchan Kim wrote:
> > +
> > + pr_info("Removed device: %s\n", zram->disk->disk_name);
>
> trivial:
>
> why did you add the info in the middle of logic functions?
> Without special reason, let's add it top of the zram_remove.
>
ok.
-ss
> Acked-by: Minchan Kim
On (04/23/15 12:06), Minchan Kim wrote:
> > +Example:
> > + cat /sys/class/zram-control/zram_add
>
> Why do we put zram-contol there rather than /sys/block/zram
that's what clsss_register() does.
[..]
> > @@ -1168,8 +1172,15 @@ static int zram_add(int device_id)
>
> Why do zram_add need
On Mon, Apr 20, 2015 at 10:37 AM, Guenter Roeck wrote:
> These functions are used in various drivers, including the latest
> version of the 8250 driver. The latter causes the following build failure.
>
> drivers/tty/serial/8250/8250_core.c: In function 'mem32be_serial_out':
>
On Mon, Apr 20, 2015 at 10:36 AM, Guenter Roeck wrote:
> These functions are used in various drivers, including the latest
> version of the 8250 driver. The latter causes the following build
> failure.
>
> drivers/tty/serial/8250/8250_core.c: In function 'mem32be_serial_out':
>
On Mon, Apr 20, 2015 at 9:55 AM, wrote:
> From: Dinh Nguyen
>
> Document "altr,socfpga-cyclone5", "altr,socfpga-arria5", and
> "altr,socfpga-arria10".
>
> Signed-off-by: Dinh Nguyen
Applied for 4.1. Thanks.
Rob
> ---
> Documentation/devicetree/bindings/arm/altera.txt | 14 ++
>
Hi LInus,
As Grant mentioned, here is the 2nd batch of DT changes for 4.1. The
main remaining item here is the endianness bindings and related 8250
driver support. Please pull.
Rob
The following changes since commit 01218bf14ee60d4a2d6c667ebdbba3ae9a7a1d66:
of: Explicitly include
input_dev may be NULL if mxt_initialize_input_device fails. But pm ops is still
available and suspend/resume assume
input_dev is not NULL. To fix this issue, we add a check if (!input_dev).
Signed-off-by: xinhui.pan
---
drivers/input/touchscreen/atmel_mxt_ts.c | 6 ++
1 file changed, 6
Hi Heiko,
2015-04-21 23:56 GMT+09:00 Heiko Stübner :
> Am Dienstag, 21. April 2015, 16:21:27 schrieb Masahiro Yamada:
>> Initial commit for a new SoC family, UniPhier, developed by
>> Socionext Inc. (formerly, System LSI Business Division of
>> Panasonic Corporation).
>>
>> This commit includes
Add UniPhier, a new citizen in the ARM multi platform.
Signed-off-by: Masahiro Yamada
---
Changes in v5: None
Changes in v4: None
Changes in v3: None
Changes in v2: None
arch/arm/configs/multi_v7_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/configs/multi_v7_defconfig
Signed-off-by: Masahiro Yamada
---
Changes in v5: None
Changes in v4: None
Changes in v3: None
Changes in v2: None
MAINTAINERS | 7 +++
1 file changed, 7 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index ea00017..c0cfc14 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -1525,6
This is an initial series for supporting Socionext UniPhier SoCs,
based on ARM Cortex-A9, mainly used for digital TVs, video recorders, etc.
Masahiro Yamada (4):
ARM: UniPhier: add basic support for UniPhier architecture
ARM: multi_v7_defconfig: enable UniPhier SoC family
ARM: dts:
Initial device trees for UniPhier SoCs: PH1-sLD3, PH1-LD4, PH1-Pro4,
and PH1-sLD8.
Signed-off-by: Masahiro Yamada
---
Changes in v5: None
Changes in v4:
- Add system-bus-controller-misc node instead of uniphier-smp-reg node
Changes in v3:
- License under GPL/X11
- Drop "earlyprintk"
Initial commit for a new SoC family, UniPhier, developed by
Socionext Inc. (formerly, System LSI Business Division of
Panasonic Corporation).
This commit includes a minimal set of components for booting the
kernel, including SMP support.
Signed-off-by: Masahiro Yamada
---
Changes in v5:
-
ping...
On 04/17/2015 08:48 PM, Gu Zheng wrote:
> Yasuaki Ishimatsu found that with node online/offline, cpu<->node relationship
> is established. Because workqueue uses a info which was established at boot
> time, but it may be changed by node hotpluging.
>
> Once pool->node points to a
"Luis R. Rodriguez" writes:
> From: "Luis R. Rodriguez"
>
> This adds a couple of bool module_param_config_*() helpers
> which are designed to let us easily associate a boolean
> module parameter with an associated kernel configuration
> option.
OK.
> Folks can use this to avoid what typically
On Thu, 23 Apr 2015 11:10:40 +0800 Gavin Guo wrote:
> >> for (i = KMALLOC_SHIFT_LOW; i <= KMALLOC_SHIFT_HIGH; i++) {
> >> if (!kmalloc_caches[i]) {
> >> - kmalloc_caches[i] = create_kmalloc_cache(NULL,
> >> + kmalloc_caches[i] =
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm announcing the release of the 3.18.12 kernel.
All users of the 3.18 kernel series must upgrade.
The updated 3.18.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-3.18.y
and can be
Get rid of some unused definitions.
Signed-off-by: K. Y. Srinivasan
---
include/linux/hyperv.h | 19 ---
1 files changed, 0 insertions(+), 19 deletions(-)
diff --git a/include/linux/hyperv.h b/include/linux/hyperv.h
index 1744148..e29ccdd 100644
--- a/include/linux/hyperv.h
From: Vitaly Kuznetsov
In case we do request_resource() in vmbus_acpi_add() we need to tear it down
to be able to load the driver again. Otherwise the following crash in observed
when hv_vmbus unload/load sequence is performed on a Generation2 instance:
[ 38.165701] BUG: unable to handle
From: Vitaly Kuznetsov
Commit 96c1d0581d00f7abe033350edb021a9d947d8d81 ("Drivers: hv: vmbus: Add
support for VMBus panic notifier handler") introduced
atomic_notifier_chain_register() call on module load. We also need to call
atomic_notifier_chain_unregister() on module unload as otherwise the
From: Dexuan Cui
free_channel() has been invoked in
vmbus_remove() -> hv_process_channel_removal(), or vmbus_remove() ->
... -> vmbus_close_internal() -> hv_process_channel_removal().
We also change to use list_for_each_entry_safe(), because the entry
is removed in hv_process_channel_removal().
This patch-set have several fixes to enable the clean unload of the vmbus.
Typically, vmbus will not be unloadable when Linux is hosted on
Hyper-V since the driver managing the root device needs the vmbus driver.
In this version of the patch-set, the patch Drivers: hv: vmbus: Implement
the
Implement the protocol for tearing down the monitor state established with
the host.
Signed-off-by: K. Y. Srinivasan
Tested-by: Vitaly Kuznetsov
---
Changes in V2: Call vmbus_disconnect earlier - Vitaly Kuznetsov
drivers/hv/channel_mgmt.c | 25 +
On Thu, Apr 23, 2015 at 12:06 PM, Minchan Kim wrote:
> On Thu, Apr 16, 2015 at 08:55:56PM +0900, Sergey Senozhatsky wrote:
>> We currently don't support on-demand device creation. The one and only way
>> to have N zram devices is to specify num_devices module parameter (default
>> value 1). That
On Thu, Apr 23, 2015 at 5:00 AM, Andrew Morton
wrote:
> On Wed, 22 Apr 2015 16:33:38 +0800 Gavin Guo wrote:
>
>> The slub_debug=PU,kmalloc-xx cannot work because in the
>> create_kmalloc_caches() the s->name is created after the
>> create_kmalloc_cache() is called. The name is NULL in the
>>
On 15/04/20, Eric W. Biederman wrote:
> Richard Guy Briggs writes:
>
> > The purpose is to track namespace instances in use by logged processes from
> > the
> > perspective of init_*_ns by logging the namespace IDs (device ID and
> > namespace
> > inode - offset).
>
> In broad strokes the
On Thu, Apr 16, 2015 at 08:55:56PM +0900, Sergey Senozhatsky wrote:
> We currently don't support on-demand device creation. The one and only way
> to have N zram devices is to specify num_devices module parameter (default
> value 1). That means that if, for some reason, at some point, user wants
>
Hi Alban,
after several months I'm finally back. I already did this patch, but I
had no time to submit. Thanks to your support it is ok for me!
We need to propagate also the patch to fix previous kernel versions...
Acked-by: Denis Ciocca
Denis
On 04/20/2015 07:57 PM, Alban Bedel wrote:
Signed-off-by: Brian Norris
---
v2: no change
.../devicetree/bindings/ata/brcm,sata-brcmstb.txt | 35 ++
1 file changed, 35 insertions(+)
create mode 100644 Documentation/devicetree/bindings/ata/brcm,sata-brcmstb.txt
diff --git
Signed-off-by: Brian Norris
---
v2:
- fix up some typos
- account for binding changes in previous patches
arch/arm/boot/dts/bcm7445.dtsi | 37 +
1 file changed, 37 insertions(+)
diff --git a/arch/arm/boot/dts/bcm7445.dtsi b/arch/arm/boot/dts/bcm7445.dtsi
Supports up to two ports which can each be powered on/off and configured
independently.
Signed-off-by: Brian Norris
---
v2:
- stop sharing SATA_TOP_CTRL registers with SATA driver
- kill custom xlate function
drivers/phy/Kconfig| 9 ++
drivers/phy/Makefile | 1 +
On Thu, 23 Apr 2015 09:35:12 +0800
pang.xun...@zte.com.cn wrote:
> Hi Steve, Peter,
>
> Steven Rostedt wrote 2015-04-21 AM 01:48:03:
> > On Mon, 20 Apr 2015 19:20:48 +0200
> > Peter Zijlstra wrote:
> >
> > > > > + */
> > > > > + if (preempt_count() & PREEMPT_ACTIVE)
> > > > > +
For 28nm STB chips, based on BCM7445.
Signed-off-by: Brian Norris
---
v2:
- make each subnode into a provider, so we can use direct phandle references
to them
- drop the 'port-ctrl' register range, since this was shared with the SATA
node
.../bindings/phy/brcm,brcmstb-sata-phy.txt
Pretty straightforward driver, using the nice library-ization of the
generic ahci_platform driver.
Signed-off-by: Brian Norris
---
v2:
- move port enabling into this driver, since the affected registers are in
the SATA_TOP_CTRL block. This means we need to check for the implemented
Hi,
Here are my updates based on everyone's feedback. I'll try to include most of
the changelog info in each patch, but a few summary points for v1 -> v2:
- reworked the PHY DT binding so that we don't need do any custom xlate in the
PHY driver
- moved all handling of the 'SATA_TOP_CTRL'
On Wed, Apr 22, 2015 at 12:05 AM, Adam Goode wrote:
> (resending in plain text)
> (please CC me on replies, I am not on LKML)
>
> Hi,
>
> I have a new Mac Mini (MacMini7,1). This model supports hotplugging of
> Thunderbolt on Windows 8 and above. Unfortunately hotplug does not
> seem to be
On Thu, 23 Apr 2015 03:29:44 +1000
Ben Shelton wrote:
> We'd like to upstream our patch, but my concern is that UBIFS behaves
> differently when it knows that the flash device supports subpages. I
> have a couple of questions related to that:
>
> - I know from experience that bad things happen
On Wed, Apr 22, 2015 at 10:32 PM, Chen Gang wrote:
> On 4/22/15 17:00, Steven Miao wrote:
>> Hi,
>>
>> On Thu, Apr 9, 2015 at 5:03 AM, Chen Gang
>> wrote:
>>> l1_text is at L1_CODE_START (e.g. for bf533, 0xff80). If the kernel
>>> is too big, it may be overwritten, the related issue:
>>>
On Wed, 22 Apr 2015 17:40:51 -0700
Stephen Hemminger wrote:
> The syscall should just return 0.
> Let the application not worry about how many CPU's are present
+1
-- Steve
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On Thu, Apr 16, 2015 at 08:55:55PM +0900, Sergey Senozhatsky wrote:
> zram_add requires valid device_id to be provided, that can be a bit
> inconvenient. Change zram_add() to return negative value upon new device
> creation failure, and device_id (>= 0) value otherwise.
>
> This prepares
On Thu, Apr 16, 2015 at 08:55:54PM +0900, Sergey Senozhatsky wrote:
> We don't have meta->tb_lock anymore and use meta table entry bit_spin_lock
> instead. update corresponding comment.
>
> Signed-off-by: Sergey Senozhatsky
Acked-by: Minchan Kim
--
Kind regards,
Minchan Kim
--
To unsubscribe
On Thu, Apr 16, 2015 at 08:55:53PM +0900, Sergey Senozhatsky wrote:
> With dynamic device creation/removal (which will be introduced later in the
> series) printing num_devices in zram_init() will not make a lot of sense, as
> well as printing the number of destroyed devices in destroy_devices().
On Wed, 2015-04-22 at 13:17 -0500, Christoph Lameter wrote:
>
> > But again let me stress that application that want to be in control will
> > stay in control. If you want to make the decission yourself about where
> > things should end up then nothing in all we are proposing will preclude
> >
On Thu, Apr 16, 2015 at 08:55:52PM +0900, Sergey Senozhatsky wrote:
> Limiting the number of zram devices to 32 (default max_num_devices value)
> is confusing, let's drop it. A user with 2TB or 4TB of RAM, for example,
> can request as many devices as he can handle.
>
> Signed-off-by: Sergey
On Wed, 2015-04-22 at 12:14 -0500, Christoph Lameter wrote:
>
> > Bottom line is we want today anonymous, share or file mapped memory
> > to stay the only kind of memory that exist and we want to choose the
> > backing store of each of those kind for better placement depending
> > on how memory
On Wed, 2015-04-22 at 15:46 -0700, Andrew Morton wrote:
> On Fri, 17 Apr 2015 00:17:50 -0700 Joe Perches wrote:
>
> > Using a function for __mlog_printk instead of a macro
> > reduces the object size of built-in.o more than 120KB, or
> > ~10% overall (x86-64 defconfig with all ocfs2 options)
> >
On Tue, Apr 21, 2015 at 12:11:01PM +0100, Stefano Stabellini wrote:
> Chen,
> could you please try the patch below in your repro scenario?
> I have only build tested it.
>
> ---
>
> xen: Add __GFP_DMA flag when xen_swiotlb_init gets free pages on ARM
>
> From: Chen Baozi
>
> Make sure that
On Thu, Apr 16, 2015 at 08:55:51PM +0900, Sergey Senozhatsky wrote:
> This patch looks big, but basically it just moves code blocks.
> No functional changes.
>
> Our current code layout looks like a sandwitch.
>
> For example,
> a) between read/write handlers, we have update_used_max() helper
On Wed, 2015-04-22 at 11:16 -0500, Christoph Lameter wrote:
> On Wed, 22 Apr 2015, Paul E. McKenney wrote:
>
> > I completely agree that some critically important use cases, such as
> > yours, will absolutely require that the application explicitly choose
> > memory placement and have the memory
On Thu, Apr 16, 2015 at 08:55:50PM +0900, Sergey Senozhatsky wrote:
> Device reset currently includes two steps:
> a) holding ->bd_mutex we ensure that there are no device users
> (bdev->bd_openers)
>
> b) and "internal" part (executed under bdev->bd_mutex and partially
> under zram->init_lock)
On Wed, 2015-04-22 at 10:25 -0500, Christoph Lameter wrote:
> On Wed, 22 Apr 2015, Benjamin Herrenschmidt wrote:
>
> > Right, it doesn't look at all like what we want.
>
> Its definitely a way to map memory that is outside of the kernel managed
> pool into a user space process. For that matter
On Thu, Apr 16, 2015 at 08:55:49PM +0900, Sergey Senozhatsky wrote:
> This patch makes some preparations for on-demand device add/remove
> functionality.
>
> Remove `zram_devices' array and switch to id-to-pointer translation (idr).
> idr doesn't bloat zram struct with additional members, f.e.
On Thu, Apr 16, 2015 at 08:55:48PM +0900, Sergey Senozhatsky wrote:
> Fix a misplaced backslash.
>
> Signed-off-by: Sergey Senozhatsky
Acked-by: Minchan Kim
--
Kind regards,
Minchan Kim
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
start_next_msg() issues a message placed in smi_info->waiting_msg
if it is non-NULL. However, sender() sets a message to
smi_info->curr_msg and NULL to smi_info->waiting_msg in the context
of run_to_completion mode. As the result, it leads an infinite
loop by waiting the completion of unissued
> On Apr 21, 2015, at 07:38, Richard Fitzgerald
> wrote:
>
> Signed-off-by: Richard Fitzgerald
> ---
> Documentation/devicetree/bindings/mfd/arizona.txt |3 +++
> 1 files changed, 3 insertions(+), 0 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/mfd/arizona.txt
>
Hi Linus,
Can you please pull the XFS updates from the tag below? The changes
are detailed in the tag message, so I won't go over them again here.
The only thing of note is the direct IO fixes that we merged last
week after the window opened. Even though a little late, they fix a
user reported
On Wed, Apr 22, 2015 at 03:42:32PM +0300, Roger Quadros wrote:
> > So we will have a separate drd fsm file, and the CONFIG_USB_OTG
> > and CONFIG_USB_OTG_FSM are not needed to be defined, right?
> >
>
> for drd case CONFIG_USB_OTG_FSM is definitely not needed.
> I'm not sure if we can operate
hi, Mike
These patches are bug fix and enhancement patches for mmp clock.
If it does not have any problem, can you help to merge it?
Thanks.
At 2015-04-07 14:17:01, "Chao Xie" wrote:
>From: Chao Xie
>
>There are three patches
>First two are fix patches.
>The last one will add the
On Wed, 2015-04-22 at 12:06 +0200, Christophe Leroy wrote:
> diff --git a/arch/powerpc/include/asm/mmu-8xx.h
> b/arch/powerpc/include/asm/mmu-8xx.h
> index d41200c..1407034 100644
> --- a/arch/powerpc/include/asm/mmu-8xx.h
> +++ b/arch/powerpc/include/asm/mmu-8xx.h
> @@ -27,6 +27,19 @@
> #define
FYI, we found performance increasement, which is expected as commit patch says,
on `fsmark.files_per_sec' by c9dc4c6578502c2085705347375b82089aad18d0:
> commit c9dc4c6578502c2085705347375b82089aad18d0
> Author: Chris Mason
> AuthorDate: Sat Apr 4 17:14:42 2015 -0700
> Commit:
Hi, Joseph.
2015-04-23 9:49 GMT+09:00 Joseph Qi :
> On 2015/4/19 13:43, Daeseok Youn wrote:
>> The use of 'status' in __ocfs2_add_entry() can return wrong
>> value. Some functions' return value in __ocfs2_add_entry(),
>> i.e ocfs2_journal_access_di() is saved to 'status'.
>> But 'status' is not
On Mon, Apr 20, 2015 at 02:41:04PM +0100, Peter Griffin wrote:
> Brian - I'm not sure of the correct patch etiquette here. Currently I have
> taken authorship of the patch and added a "Suggested-by" tag on the V2.
> Maybe I should have also kept your "Signed-off-by" or done something else?
>
user-space aborts suspend attempt if writing wakeup_count failed.
Count the write failure towards wakeup_count.
Signed-off-by: Jin Qian
---
drivers/base/power/wakeup.c | 17 +
1 file changed, 17 insertions(+)
diff --git a/drivers/base/power/wakeup.c
After a wakeup_source is destroyed, we lost all information such as how
long this wakeup_source has been active. Add a dummy wakeup_source to
record such info.
Signed-off-by: Jin Qian
---
drivers/base/power/wakeup.c | 35 +++
1 file changed, 35 insertions(+)
A rogue wakeup source not registered in wakeup_sources list is not visible
from wakeup_sources_stats_show. Check if the wakeup source is registered
properly by looking at the timer function.
Signed-off-by: Jin Qian
---
drivers/base/power/wakeup.c | 19 +++
1 file changed, 19
On 2015/4/19 13:43, Daeseok Youn wrote:
> The use of 'status' in __ocfs2_add_entry() can return wrong
> value. Some functions' return value in __ocfs2_add_entry(),
> i.e ocfs2_journal_access_di() is saved to 'status'.
> But 'status' is not used in 'bail' label for returning result
> of
Hi Tejun,
>> + rcu_read_lock();
>> + css = task_css(current, pids_cgrp_id);
>> + if (!css_tryget_online(css)) {
>> + retval = -EBUSY;
>> + goto err_rcu_unlock;
>> + }
>> + rcu_read_unlock();
>
> Hmmm... so, the above is guaranteed to succeed in finite
On Wed, 22 Apr 2015 20:37:08 -0400
Pranith Kumar wrote:
> >> I understand why this syscall makes sense on SMP only, but you are
> >> anyways checking num_online_cpus() and returning if it is only one. Is
> >> this limitation necessary then? How do !SMP systems handle this
> >> syscall? (I am
On Wed, Apr 22, 2015 at 4:40 PM, Mathieu Desnoyers
wrote:
> - Original Message -
>> On Fri, Apr 17, 2015 at 11:06 AM, Mathieu Desnoyers
>> wrote:
>> > diff --git a/init/Kconfig b/init/Kconfig
>> > index f5dbc6d..89bad6a 100644
>> > --- a/init/Kconfig
>> > +++ b/init/Kconfig
>> > @@
On 04/22/2015 05:06 PM, Yu, Fenghua wrote:
> We need to copy ALL of supported xstates to user. Using xstate_bv only copies
> partial xstates that are in non-init status.
>
> Xstate_bv only has xstates that are in non-init status. The xstates that are
> in
> init status will not be copied to user
On Thu, Apr 23, 2015 at 01:51:27PM +, Brian Norris wrote:
>
> On Thu, Apr 16, 2015 at 02:11:24AM +, Peter Pan 潘栋 (peterpandong)
> wrote:
> > The diskonchip driver almost uses the default nand_base hooks as-is,
> > except that it provides custom on-flash BBT descriptors and avoids
> using
On Wed, 2015-04-22 at 15:06 +0300, Purcareata Bogdan wrote:
> On 21.04.2015 03:52, Scott Wood wrote:
> > On Mon, 2015-04-20 at 13:53 +0300, Purcareata Bogdan wrote:
> >> There was a weird situation for .kvmppc_mpic_set_epr - its corresponding
> >> inner
> >> function is kvmppc_set_epr, which is a
> From: Hansen, Dave
> Sent: Wednesday, April 22, 2015 5:21 PM
> To: Yu, Fenghua; H. Peter Anvin; Ingo Molnar; Thomas Gleixner; Mallick, Asit
> K; Williamson, Glenn P
> Cc: linux-kernel; x86
> Subject: Re: [PATCH Bugfix v2 2/4] x86/xsaves: Define and use
> user_xstate_size for xstate size in
On 04/22/2015 05:06 PM, Yu, Fenghua wrote:
> Xsave->xsave_hdr.xstate_bv is equal to pcntxt_mask (see
> setup_init_fpu_buf()).
This is going to be a long thread. But, let's take it a step at a time.
Do you agree that this earlier statement is incorrect?
--
To unsubscribe from this list: send the
> From: Hansen, Dave
> Sent: Wednesday, April 22, 2015 12:34 PM
> To: Yu, Fenghua; H. Peter Anvin; Ingo Molnar; Thomas Gleixner; Mallick, Asit
> K; Williamson, Glenn P
> Cc: linux-kernel; x86
> Subject: Re: [PATCH Bugfix v2 2/4] x86/xsaves: Define and use
> user_xstate_size for xstate size in
On 04/22/2015 06:30 AM, Alexandre Belloni wrote:
Apologies on a tardy response, got dragged into another issue and got
cooped up in lab whole day.
> On 21/04/2015 at 20:59:15 -0500, Nishanth Menon wrote :
Why is that so? when set alarm is requested for time X, you want
interrupt at
On 04/22/2015 08:26 AM, grygorii.stras...@linaro.org wrote:
> Hi,
>
> On 04/21/2015 03:51 AM, Nishanth Menon wrote:
>> Alarm interrupt enable register is at offset 0x7, while the time
>> registers for the alarm follow that. When we program Alarm interrupt
>> enable prior to programming the time,
> Am I doing something wrong? Are there good alternatives for when
> we want to trace something that's done in a header?
I had to out of line multiple inlines too to trace them.
Like the MSR tracing.
The trace includes just have too many dependencies. Most of it
comes from RCU i believe.
It
bert/pubkey.txt
>
> Hello, Herbert.
>
> Sorry for my ignorance but which tree and branch does this commit come from?
>
> --
> Murilo
I tried next-20150422 (that contained Herbert's patch) and it worked just fine.
Thank you, guys.
--
Murilo
--
To unsubscribe from this list:
This patch just fix a typo (s/witch/which)
Signed-off-by: Wang Long
---
Documentation/kasan.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/kasan.txt b/Documentation/kasan.txt
index 092fc10..063095a 100644
--- a/Documentation/kasan.txt
+++
On Wed, 22 Apr 2015 18:07:50 +0100 Mel Gorman wrote:
> --- a/arch/x86/Kconfig
> +++ b/arch/x86/Kconfig
> @@ -32,6 +32,7 @@ config X86
> select HAVE_UNSTABLE_SCHED_CLOCK
> select ARCH_SUPPORTS_NUMA_BALANCING if X86_64
> select ARCH_SUPPORTS_INT128 if X86_64
> + select
There has been a glut of tough debug issues lately that all come
back to the xsave code. This trace point helped us find and fix
a long-lived bug today, just from the data it showed.
But, the xsave operations are in a header and they're inlined all
over the place. Including a tracepoint header
Bartlomiej Zolnierkiewicz writes:
[...]
>> However, with the default governor set to userspace it boots fine until
>> my userspace (ubuntu) tries to enable the ondemand governor, and then it
>> hangs.
>>
>> For it to boot, I have to disable the ondemand governor, and set the
>> default
Hi
Looks good to me. Greg, please pull it into your tree.
Acked-by: Evgeniy Polyakov
23.04.2015, 00:56, "Dmitry Khromov" :
> Signed-off-by: Dmitry Khromov
> ---
> drivers/w1/w1.c | 17 -
> 1 file changed, 16 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/w1/w1.c
Reviewed-by: Scott Branden
Tested-by: Scott Branden
Signed-off-by: Jonathan Richardson
---
.../bindings/arm/bcm/brcm,cygnus-dte.txt | 24
1 file changed, 24 insertions(+)
create mode 100644
Documentation/devicetree/bindings/arm/bcm/brcm,cygnus-dte.txt
diff
1 - 100 of 1484 matches
Mail list logo
