(2014/07/18 3:41), Steven Rostedt wrote:
> On Tue, 15 Jul 2014 06:00:28 +
> Masami Hiramatsu wrote:
>
>> Introduce FTRACE_OPS_FL_IPMODIFY to avoid conflict among
>> ftrace users who may modify regs->ip to change the execution
>> path. This also adds the flag to kprobe_ftrace_ops, since
>> ftr
(2014/07/18 14:32), Namhyung Kim wrote:
> Hi Masami,
>
> On Tue, 15 Jul 2014 06:00:35 +, Masami Hiramatsu wrote:
>> +static int __ftrace_add_filter_ip(struct ftrace_ops *ops, unsigned long ip,
>> + int *ref)
>> +{
>> +int ret;
>> +
>> +/* Try to set given i
On Thu, 17 Jul 2014, Felipe Balbi wrote:
> Hi,
>
> On Thu, Jul 17, 2014 at 06:13:33PM +0100, Lee Jones wrote:
> > This patch provides mechanism for subordinate devices to check
> > whether the DWC3 core probed successfully or otherwise. Useful
> > if PHYs are required to configure controllers, b
This patch adds device tree binding documentation for the SATA
controller found on NVIDIA Tegra SoCs.
Signed-off-by: Mikko Perttunen
---
v5: remove ordering requirement again
.../devicetree/bindings/ata/tegra-sata.txt | 30 ++
1 file changed, 30 insertions(+)
create
On Tue 15-07-14 14:19:35, Michal Hocko wrote:
> [...]
> > +/**
> > + * mem_cgroup_migrate - migrate a charge to another page
> > + * @oldpage: currently charged page
> > + * @newpage: page to transfer the charge to
> > + * @lrucare: page might be on LRU already
>
> which one? I guess the newpage?
This adds support for the integrated AHCI-compliant Serial ATA
controller present on the NVIDIA Tegra124 system-on-chip.
Signed-off-by: Mikko Perttunen
---
v5: let ahci_platform handle sata clock and also handle it ourselves.
this allows use of ahci_platform while having a special sequence
fo
From: "Matwey V. Kornilov"
Hi,
The following patch series is to deal with the issue on false-positives
of Intel EPP bug check [1].
More than a decade ago, the check was introduced in order to prevent EPP
operation on the some Intel LPT chipsets. The main issue to defence from
was CPU hang at EP
From: "Matwey V. Kornilov"
The code in intel_bug_present is known to produce much false-positives.
It is believed that the affected by the bug hardware are used with either Intel
80486 or Pentium.
Perform the check only when the kernel configured as CONFIG_X86_32,
then use cpuinfo_x86 of the fi
From: "Matwey V. Kornilov"
Put the code to check present of the Intel bug from parport_EPP_supported
into new intel_bug_present function. The later also return ECR register
to the state it has before function call.
Suggested-by: One Thousand Gnomes
Tested-by: Heiko Andreas Sommer
Signed-off-by
On Thu, Jul 17, 2014 at 04:33:36PM -0700, H. Peter Anvin wrote:
>
> I just want to make sure we don't negatively impact the real security of
> users because of "optics". We already have a lot of problems with
> people extracting long-living keys from /dev/urandom because /dev/random
> is too slow
So here's v5: this time, as suggested, I handle the sata clock myself
and let ahci_platform handle it too, leading it to be prepared+enabled
twice. This works fine, and allows us to remove the DT ordering requirement.
I also have in the works a patchset that adds the name-based
ahci_platform_g
On Thu, 17 Jul 2014, Andreas Werner wrote:
> On Thu, Jul 17, 2014 at 01:41:56PM +0100, Lee Jones wrote:
> > On Thu, 17 Jul 2014, Andreas Werner wrote:
> > > The MEN 14F021P00 Board Management Controller provides an
> > > I2C interface to the host to access the feature implemented in the BMC.
> > >
From: Alex Smith
This patch has been added to the 3.12 stable tree. If you have any
objections, please let us know.
===
commit 91ad11d7cc6f4472ebf177a6252fbf0fd100d798 upstream.
On MIPS calls to _mcount in modules generate 2 instructions to load
the _mcount address (and therefore 2
From: Mateusz Guzik
This patch has been added to the 3.12 stable tree. If you have any
objections, please let us know.
===
commit a914722f333b3359d2f4f12919380a334176bb89 upstream.
Otherwise the kernel oopses when remounting with IPv6 server because
net is dereferenced in dev_get_b
The current rq->avg is not made use of anywhere, and the code is in fair
scheduler's critical path, so remove it.
Signed-off-by: Yuyang Du
---
kernel/sched/debug.c |8
kernel/sched/fair.c | 24
kernel/sched/sched.h |2 --
3 files changed, 4 insertions
Chris, Ulf,
Sorry for the delay, things have been hectic.
The following changes since commit cd3de83f147601356395b57a8673e9c5ff1e59d1:
Linux 3.16-rc4 (2014-07-06 12:37:51 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git tags/mfd-mmc-v
Thanks to Morten, Ben, and Fengguang.
v4 changes:
- Insert memory barrier before writing cfs_rq->load_last_update_copy.
- Fix typos.
We carried out some performance tests (thanks to Fengguang and his LKP). The
results are shown
as follows. The patchset (including two patches) is on top of mainl
The idea of per entity runnable load average (let runnable time contribute to
load
weight) was proposed by Paul Turner, and it is still followed by this rewrite.
This
rewrite is done due to the following ends:
1. cfs_rq's load average (namely runnable_load_avg and blocked_load_avg) is
updated
On Friday 18 July 2014, mat...@sai.msu.ru wrote:
> From: "Matwey V. Kornilov"
>
> The code in intel_bug_present is known to produce much false-positives.
> It is believed that the affected by the bug hardware are used with either
> Intel 80486 or Pentium.
>
> Perform the check only when the kernel
Hello,
On 2014-07-18 00:06, Andrew Morton wrote:
On Thu, 17 Jul 2014 11:36:07 +0200 Marek Szyprowski
wrote:
MAX_CMA_AREAS is used by other subsystems (i.e. arch/arm/mm/dma-mapping.c),
so we need to provide correct definition even if CMA is disabled.
This patch fixes this issue.
Reported-by:
Various drivers implement architecture and/or device specific means
to restart (reset) the system. Various mechanisms have been implemented
to support those schemes. The best known mechanism is arm_pm_restart,
which is a function pointer to be set either from platform specific code
or from drivers.
The kernel core now provides an API to trigger a system restart.
Register with it to restart the system instead of misusing the
reboot notifier.
Signed-off-by: Guenter Roeck
---
v5: Function and variable renames: *notifier -> *handler
v4: Set restart notifier priority to 128.
v3: No change
v2: No
The kernel now provides an API to trigger a system restart.
Register with it instead of setting arm_pm_restart.
Signed-off-by: Guenter Roeck
---
v5: Functions and variables renamed: *notifier -> *handler
v4: Set notifier priority to 128.
v3: Move struct notifier_block into struct moxart_wdt_dev.
The kernel core now supports a restart handler call chain to restart
the system. Call it if arm_pm_restart is not set.
Signed-off-by: Guenter Roeck
---
v5: Renamed restart function to do_kernel_restart
v4: No change.
v3: Use wrapper function to execute notifier call chain.
v2: Only call notifier
Implementing a restart handler in a module don't make sense
as there would be no guarantee that the module is loaded when
a restart is needed. Unexport arm_pm_restart to ensure that
no one gets the idea to do it anyway.
Signed-off-by: Guenter Roeck
---
v5: No change
v4: No change
v3: No change
v2
machine_restart is supported on non-ARM platforms, and and ultimately calls
arm_pm_restart, so dont call arm_pm_restart directly but use the more
generic function.
Cc: Russell King
Signed-off-by: Guenter Roeck
---
v5: No change.
v4: No change.
v3: No change.
v2: Added patch.
drivers/power/rese
Am 18.07.2014 02:36, schrieb Chen Gang:
>
> On 07/18/2014 02:09 AM, Richard Weinberger wrote:
>> Am 17.07.2014 12:48, schrieb Arnd Bergmann:
>>> AFAICT, NO_IOMEM only has a real purpose on UML these days. Could we take
>>> a shortcut here and make COMPILE_TEST depend on !UML? Getting random stuff
You attempted to send a message that contained an executable file. Our company
policy prohibits the sending of executable files via email. The message was not
delivered.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.or
On Fri 11-07-14 15:37:26, Jiang Liu wrote:
> When CONFIG_HAVE_MEMORYLESS_NODES is enabled, cpu_to_node()/numa_node_id()
> may return a node without memory, and later cause system failure/panic
> when calling kmalloc_node() and friends with returned node id.
> So use cpu_to_mem()/numa_mem_id() inste
The kernel core now supports a restart handler call chain for system
restart functions.
With this change, the arm_pm_restart callback is now optional, so check
if it is set before calling it. Only call the kernel restart handler
if arm_pm_restart is not set.
Signed-off-by: Guenter Roeck
---
v5:
Various drivers implement architecture and/or device specific means
to restart (reset) the system. Various mechanisms have been implemented
to support those schemes. The best known mechanism is arm_pm_restart,
which is a function pointer to be set either from platform specific code
or from drivers.
On Thu, Jul 17, 2014 at 11:05:12PM -0400, Nick Krause wrote:
> On Thu, Jul 17, 2014 at 1:38 PM, Nick Krause wrote:
> > On Thu, Jul 17, 2014 at 3:52 AM, Sam Ravnborg wrote:
> >> On Wed, Jul 16, 2014 at 10:25:30PM -0400, Nick Krause wrote:
> >>> I am hitting three Fix mes in this file and am wonder
On Fri, Jul 18, 2014 at 12:21:04AM -0400, Nick Krause wrote:
> The build for sparc allmodconfig is still failing for the main branch
> of the linux kernel.
> I would recommend fixing these issues. I am attaching my build
> warnings and errors
> logs for the failing build test I did today.
Did you
On 07/16/2014 02:31 PM, Jiang Liu wrote:
> Hi Aaron,
> Thanks for reporting this issue. Yinghai has already posted
> a patch to fix the issue by disabling freeing of irq in case of system
> shutdown. Please refer to:
> https://lkml.org/lkml/2014/6/26/619
>
> Or could you please help to try f
Hi Andrew,
Today's linux-next merge of the akpm-current tree got a conflict in
arch/x86/syscalls/syscall_64.tbl between commit 69d7b7939c24 ("random:
introduce getrandom(2) system call") from the random tree and commit
f5e74a5d7743 ("kexec: new syscall kexec_file_load() declaration") from
the akpm
On Fri, Jul 18, 2014 at 12:34 AM, David Cohen
wrote:
> Hi Andy,
>
> Thanks for the patch.
>
> On Thu, Jul 17, 2014 at 05:59:41PM +0300, Andy Shevchenko wrote:
>> The patch "x86, irq: Count legacy IRQs by legacy_pic->nr_legacy_irqs instead
>> of
>> NR_IRQS_LEGACY" (linux-next commit 95d76acc7518d5
On Tue, Jul 15, 2014 at 07:16:06PM -0700, Kuninori Morimoto wrote:
>
> Hi
>
> > > > The documentation only mentioned the generic fallback compatible
> > > > property.
> > > > Add the missing SoC-specific compatible properties, some of which are
> > > > already in use.
> > > >
> > > > Signed-off
Hello,
On 2014-07-18 08:45, Gioh Kim wrote:
For page migration of CMA, buffer-heads of lru should be dropped.
Please refer to https://lkml.org/lkml/2014/7/4/101 for the history.
I have two solution to drop bhs.
One is invalidating entire lru.
Another is searching the lru and dropping only one b
Hi!
> > I suggest to add features supported by charger-manager to power supply
> > charging
> > driver and convert users of charger-manager to the improved driver.
> >
> > I CC'd MyungJoo Ham, who wrote the charger-manager, so that he can also give
> > feedback.
>
> We are back to the initial d
On Tue, Jul 15, 2014 at 10:45 AM, Ley Foon Tan wrote:
> This patch adds support for signal handling.
>
> Signed-off-by: Ley Foon Tan
> ---
> arch/nios2/include/asm/signal.h | 22 +++
> arch/nios2/include/asm/ucontext.h| 34
> arch/nios2/include/uapi/asm/sigcontext.h | 30
On 07/18/2014 01:34 AM, Hugh Dickins wrote:
> On Thu, 17 Jul 2014, Vlastimil Babka wrote:
>> On 07/15/2014 12:28 PM, Hugh Dickins wrote:
>> > In the end I decided that we had better look at it as two problems,
>> > the trinity faulting starvation, and the indefinite punching loop,
>> > so 1/2 and 2
This patch add new memory to ZONE_MOVABLE if movable zone is setup
and lower than newly added memory for powerpc.
Signed-off-by: Wang Nan
---
arch/powerpc/mm/mem.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/powerpc/mm/mem.c b/arch/powerpc/mm/mem.c
index 2c8e90f..2d869ef 10064
This patch add new memory to ZONE_MOVABLE if movable zone is setup
and lower than newly added memory for sh.
Signed-off-by: Wang Nan
---
arch/sh/mm/init.c | 13 -
1 file changed, 8 insertions(+), 5 deletions(-)
diff --git a/arch/sh/mm/init.c b/arch/sh/mm/init.c
index 2d089fe..ff9dec
This patch add new memory to ZONE_MOVABLE if movable zone is setup
and lower than newly added memory for x86_64.
Signed-off-by: Wang Nan
---
arch/x86/mm/init_64.c | 10 --
1 file changed, 8 insertions(+), 2 deletions(-)
diff --git a/arch/x86/mm/init_64.c b/arch/x86/mm/init_64.c
index df
This patch add new memory to ZONE_MOVABLE if movable zone is setup
and lower than newly added memory for x86_32.
Signed-off-by: Wang Nan
---
arch/x86/mm/init_32.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/x86/mm/init_32.c b/arch/x86/mm/init_32.c
index e395048..dd69833 100644
This series of patches fix a problem when adding memory in bad manner.
For example: for a x86_64 machine booted with "mem=400M" and with 2GiB
memory installed, following commands cause problem:
# echo 0x4000 > /sys/devices/system/memory/probe
[ 28.613895] init_memory_mapping: [mem 0x400
Hi,
I'm curious about what will it happen when alloc_pages_node(memoryless_node).
If the memory is allocated from the most preferable node for the
@memoryless_node,
why we need to bother and use cpu_to_mem() in the caller site?
If not, why the memory allocation subsystem refuses to find a prefe
This patch add new memory to ZONE_MOVABLE if movable zone is setup
and lower than newly added memory for ia64.
Signed-off-by: Wang Nan
---
arch/ia64/mm/init.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/ia64/mm/init.c b/arch/ia64/mm/init.c
index 25c3502..d81c916 100644
--- a/
On 07/18/2014 04:53 AM, Sam Bobroff wrote:
> On 17/07/14 21:14, Michael Neuling wrote:
>>
>> On Jul 17, 2014 9:11 PM, "Benjamin Herrenschmidt"
>> mailto:b...@kernel.crashing.org>> wrote:
>>>
>
>> Outstanding Issues
>> ==
>> (1) Running DSCR register value inside a tr
On Fri, Jul 18, 2014 at 07:48:49AM +0800, kbuild test robot wrote:
> All warnings:
>
>:1229:2: warning: #warning syscall sched_setattr not implemented
> [-Wcpp]
>:1232:2: warning: #warning syscall sched_getattr not implemented
> [-Wcpp]
>:1235:2: warning: #warning syscall renameat2 n
On 07/17/2014 08:34 AM, Richard Weinberger wrote:
checkpatch.pl is a nice tool to find issues in patches.
Sadly this tool gets more and more abused by various people to create
style cleanups for source files within the kernel.
In order to deal with that bad habit let's remove the --file option
a
> By using the generic IRQ support in the Register map API, it
> is possible to get rid max77686-irq.c and simplify the code.
>
> Suggested-by: Krzysztof Kozlowski
> Signed-off-by: Javier Martinez Canillas
> Acked-by: Lee Jones
> Reviewed-by: Doug Anderson
> Tested-by: Doug Anderson
Applied
On Fri, 04 Jul 2014, Javier Martinez Canillas wrote:
> When the CONFIG_OF option was not enabled, a dummy function
> max77686_i2c_parse_dt_pdata() was defined since this is called
> unconditionally on probe(). Just always define the real function
> and conditionally call it if CONFIG_OF is enabled
On Fri, 04 Jul 2014, Javier Martinez Canillas wrote:
> The driver doesn't have PM operations defined so add a suspend
> and resume function handlers to allow the PMIC IRQ to wakeup
> the system when it is put into a sleep state.
>
> Signed-off-by: Javier Martinez Canillas
> Reviewed-by: Krzyszto
Hi Steve,
On 07/15/2014 11:51 PM, Steven Rostedt wrote:
> Michal,
>
> Can you please test and ack this and patch 6 of this series. Otherwise I
> may have to stip it out of the series which will break the build on
> microblaze.
>
> You can test my branch at:
>
> git://git.kernel.org/pub/scm/li
On Fri, 04 Jul 2014, Javier Martinez Canillas wrote:
> Error checking across the driver is mostly consistent besides
> a few exceptions, so change these exceptions for consistency.
>
> Signed-off-by: Javier Martinez Canillas
> Reviewed-by: Krzysztof Kozlowski
> ---
> drivers/mfd/max77686.c | 1
On Fri, 04 Jul 2014, Javier Martinez Canillas wrote:
> There is no need to print out-of-memory errors since this is already
> done by the memory management subsystem which even calls dump_stack().
>
> Signed-off-by: Javier Martinez Canillas
> ---
> drivers/mfd/max77686.c | 4 +---
> 1 file chan
On Thu, Jul 17, 2014 at 04:19:31PM -0700, David Miller wrote:
> From: Tom Gundersen
> Date: Thu, 17 Jul 2014 10:06:04 +0200
>
> > @@ -192,8 +193,10 @@ int ieee802154_add_iface(struct sk_buff *skb, struct
> > genl_info *info)
> > if (devname[nla_len(info->attrs[IEEE802154_ATTR_DEV_NAM
Hi Steve,
On 07/09/2014 04:03 PM, Steven Rostedt wrote:
> Michal,
>
> Can you ack this please?
>
> -- Steve
>
>
> On Thu, 26 Jun 2014 12:52:27 -0400
> Steven Rostedt wrote:
>
>> From: "Steven Rostedt (Red Hat)"
>>
>> ftrace_stop() is going away as it disables parts of function tracing
>> th
On Fri, 04 Jul 2014, Javier Martinez Canillas wrote:
> When platform data is not found an -EIO (I/O error) code is returned.
> This doesn't seem to be the correct error so better return -EINVAL
> (Invalid argument) which is what most drivers do in this case.
>
> Signed-off-by: Javier Martinez Can
On Fri, 04 Jul 2014, Javier Martinez Canillas wrote:
> The function max77802_i2c_parse_dt_pdata() should only be called
> if there isn't already platform data for the device.
>
> Signed-off-by: Javier Martinez Canillas
> ---
> drivers/mfd/max77686.c | 2 +-
> 1 file changed, 1 insertion(+), 1 d
On Fri, Jul 18, 2014 at 12:29:37AM -0700, Guenter Roeck wrote:
> First, 'abuse' is a relative term. It describes a use you
> (and possibly many others) may find objectionable, but that
> does not mean all uses are objectionable.
Do you actually have a valid use case for keeping the cmdline switch
2014-07-18 오후 4:50, Marek Szyprowski 쓴 글:
Hello,
On 2014-07-18 08:45, Gioh Kim wrote:
For page migration of CMA, buffer-heads of lru should be dropped.
Please refer to https://lkml.org/lkml/2014/7/4/101 for the history.
I have two solution to drop bhs.
One is invalidating entire lru.
Another
Dne 18.7.2014 06:40, Masahiro Yamada napsal(a):
> The specification of Python 3 is largely different from that of
> Python 2.
>
> For example, arch/ia64/scripts/unwcheck.py seems to be written
> in Python 2, not compatible with Python 3.
>
> It is not a good idea to invoke python scripts with the
From: David Miller
> From: Tom Gundersen
> Date: Thu, 17 Jul 2014 10:06:04 +0200
>
> > @@ -192,8 +193,10 @@ int ieee802154_add_iface(struct sk_buff *skb, struct
> > genl_info *info)
> > if (devname[nla_len(info->attrs[IEEE802154_ATTR_DEV_NAME]) - 1]
> > !=
Hi all,
Changes since 20140717:
The net-next tree gained a build failure so I used the version from
next-20140717.
The irqchip tree gained conflicts against the arm64 and trivial trees.
The akpm-current tree gained a conflict against the random tree.
Non-merge commits (relative to Linus' tree)
On Fri, Jul 18, 2014 at 01:55:22PM +0800, Lan Tianyu wrote:
> Date: Fri, 18 Jul 2014 13:55:22 +0800
> From: Lan Tianyu
> To: r...@rjwysocki.net, l...@kernel.org
> Cc: Lan Tianyu , linux-a...@vger.kernel.org,
> linux-kernel@vger.kernel.org
> Subject: [PATCH] ACPI/NVS: Not save NVS region for new m
Hi Khalid.
Looks better now - thanks.
A few nits remaining.
Please fix and submit a v3 - then we will see if David approves.
Sam
> +/* mdesc_open() - Grab a reference to mdesc_handle when /dev/mdesc is
> + * opened. Hold this reference until /dev/mdesc is closed to ensure
> + * mdes
On 07/17/2014 06:18 PM, Felipe Balbi wrote:
>> No, this is okay. If you look, it checks for "up->ier &
>> UART_IER_THRI". On the second invocation it will see that this
>> bit is already set and therefore won't call get_sync() for the
>> second time. That bit is removed in the _stop_tx() path.
>
On Fri, Jul 18, 2014 at 1:19 AM, David Miller wrote:
> From: Tom Gundersen
> Date: Thu, 17 Jul 2014 10:06:04 +0200
>
>> @@ -192,8 +193,10 @@ int ieee802154_add_iface(struct sk_buff *skb, struct
>> genl_info *info)
>> if (devname[nla_len(info->attrs[IEEE802154_ATTR_DEV_NAME]) - 1]
>
On Fri, Jul 18, 2014 at 06:47:22AM +0100, Z Lim wrote:
> (resending this email in case the first one got caught in your spam
> filter. sorry.)
>
> On Thu, Jul 17, 2014 at 10:41:02AM +0100, Will Deacon wrote:
> > On Wed, Jul 16, 2014 at 11:04:22PM +0100, Zi Shen Lim wrote:
> > > On Wed, Jul 16, 201
On Thu, 17 Jul 2014, Frank Haverkamp wrote:
> Hi Bjorn and Sebastian,
>
> Am Mittwoch, den 16.07.2014, 15:10 -0600 schrieb Bjorn Helgaas:
> > [+cc linux-pci]
> >
> > On Wed, Jul 09, 2014 at 12:46:39PM +0200, Sebastian Ott wrote:
> > > GenWQE used to call pci_enable_msi_block to allocate a desired
On Thu 2014-07-17 11:19:15, Alex Elder wrote:
> On 07/17/2014 09:46 AM, Petr Mládek wrote:
> > On Thu 2014-07-17 07:11:39, Alex Elder wrote:
> >> On 07/17/2014 03:39 AM, Petr Mládek wrote:
> >>> On Wed 2014-07-16 12:26:57, Alex Elder wrote:
> Two log record flags--LOG_CONT and LOG_NEWLINE--are
On Fri, Jul 18, 2014 at 07:53:04AM +0100, Minchan Kim wrote:
> MADV_FREE needs pmd_dirty and pmd_mkclean for detecting recent
> overwrite of the contents since MADV_FREE syscall is called for
> THP page.
>
> This patch adds pmd_dirty and pmd_mkclean for THP page MADV_FREE
> support.
>
> Cc: Catal
> On Tue, 8 Jul 2014 16:02:28 +0200 (CEST), Lukáš Czerner
> wrote:
> Non-text part: MULTIPART/MIXED
> > On Tue, 8 Jul 2014, Namjae Jeon wrote:
> >
> > > Date: Tue, 08 Jul 2014 21:00:02 +0900
> > > From: Namjae Jeon
> > > To: Dave Chinner , Theodore Ts'o
> > > Cc: linux-ext4 ,
> > > linux-fsde.
On Thu, Jul 17, 2014 at 11:24:45PM -0400, Nick Krause wrote:
> > Nick, are you human?
> >
> Yes I am human.
It doesn't look like it. *Every-f*ckin-body* is telling you to stop
doing this FIXME bullshit but you continue like a bot which cannot parse
answer mails.
Just answer me one thing: why are
On Fri, 2014-07-11 at 16:59 -0700, Andi Kleen wrote:
> All feedback addressed. Hopefully ready for merge now.
...
> The JSON format and perf parser has some minor Intelisms, but they
> are simple and small and optional. It's easy to extend, so it would be
> possible to use it for other CPUs too, a
On (Mon) 14 Jul 2014 [18:12:46], Amit Shah wrote:
> On (Mon) 14 Jul 2014 [08:37:00], Jason Cooper wrote:
> > On Mon, Jul 14, 2014 at 10:05:19AM +0530, Amit Shah wrote:
> > > Some RNG devices may not be ready to give early randomness at probe()
> > > time, and hence lose out on the opportunity to co
On Fri, Jul 18, 2014 at 1:20 AM, David Miller wrote:
> From: Tom Gundersen
> Date: Thu, 17 Jul 2014 10:06:05 +0200
>
>> @@ -2787,10 +2788,13 @@ static int gsm_create_network(struct gsm_dlci *dlci,
>> struct gsm_netconfig *nc)
>> pr_debug("create network interface");
>>
>> netname = "
On Thu, Jul 17, 2014 at 03:12:35PM +0100, Jason Cooper wrote:
> On Thu, Jul 17, 2014 at 02:55:34PM +0100, Mark Rutland wrote:
> > Hi Jason,
> >
> > On Thu, Jul 17, 2014 at 02:18:54PM +0100, Jason Cooper wrote:
> > > On Wed, Jul 09, 2014 at 06:05:00PM -0500, suravee.suthikulpa...@amd.com
> > > wro
On Thu 2014-07-17 12:59:10, Alex Elder wrote:
> If log_store() gets flags containing LOG_PREFIX, it indicates the
> record getting stored should implicitly complete the previous log
> record and start a new one.
>
> We can also ensure the previous record is completed by keeping
> track of the prev
Hi Gleb,
On 07/17/2014 09:57 PM, Gleb Natapov wrote:
On Thu, Jul 17, 2014 at 09:34:20PM +0800, Tang Chen wrote:
Hi Gleb,
On 07/15/2014 08:40 PM, Gleb Natapov wrote:
..
And yes, we have the problem you said here. We can migrate the page while L2
vm is running.
So I think we should enforce
On Thu, Jul 17, 2014 at 03:48:29PM +0100, Suravee Suthikulanit wrote:
> On 7/17/2014 8:55 AM, Mark Rutland wrote:
> > Hi Jason,
> >
> > On Thu, Jul 17, 2014 at 02:18:54PM +0100, Jason Cooper wrote:
> >> On Wed, Jul 09, 2014 at 06:05:00PM -0500, suravee.suthikulpa...@amd.com
> >> wrote:
> >>> From:
On a system with low memory extracting the initramfs may fail. If this
happens the user gets "Failed to execute /init" instead of an initramfs
error.
Check return value of sys_write and call error() when the write was
incomplete or failed.
Signed-off-by: David Engraf
diff --git a/init/init
On Friday 18 July 2014 14:07:42 Ley Foon Tan wrote:
> On Thu, Jul 17, 2014 at 7:07 PM, Arnd Bergmann wrote:
> > The get_user/put_user functions really need to be annotated might_fault(),
> > because that's what they do.
> >
> > The whole point of get_user() is to access an unchecked user space
> >
On Wed, 16 Jul 2014, Rui Xiang wrote:
> Date: Wed, 16 Jul 2014 17:28:10 +0800
> From: Rui Xiang
> To: Lukáš Czerner
> Cc: Dave Kleikamp , linux-e...@vger.kernel.org,
> linux-fsde...@vger.kernel.org, linux-kernel@vger.kernel.org,
> Li Zefan
> Subject: Re: testing result of loop-aio patch
Hi Simon
> 1. That the (in this case thermal) IP on the SoC's listed is known
>to work with the driver using the generic (in this case
>renesas,rcar-thermal) compatibility string.
>
> 2. That if some incompatibility is subsequently found such that the
>IP on SoC does function correct
Replace the VDBG and DBG macro with the kernels "proper" debug macros
(dev_vdbg and dev_dbg) in f_acm.c, f_obex.c & f_serial.c
Signed-off-by: Richard Leitner
---
drivers/usb/gadget/f_acm.c| 41 -
drivers/usb/gadget/f_obex.c | 22 ++---
On Fri, Jul 18, 2014 at 02:26:26PM +0530, Amit Shah wrote:
>
> > Sounds like a good idea to me. Though, changes in core.c that
> > increase the time in hwrng_register() or hwrng_init() may not get
> > noticed by rng drivers and they may suddenly start failing for no
> > apparent reason. Seems lik
Hello,
On 07/18/2014 03:55 PM, Wang Nan wrote:
> This series of patches fix a problem when adding memory in bad manner.
> For example: for a x86_64 machine booted with "mem=400M" and with 2GiB
> memory installed, following commands cause problem:
>
> # echo 0x4000 > /sys/devices/system/memor
On Friday 18 July 2014 14:15:07 Chung-Lin Tang wrote:
> Hi Arnd,
> Considering two other kernel interface issues that appeared earlier in
> the context of nios2 glibc/kernel upstreaming:
>
> (1) The 64-bit time_t/timespec issue.
> (2) Dropping renameat by default in favor of renameat2
>
> What's
Hello Marek and Dr. H. Nikolaus,
On Fri, Jul 18, 2014 at 8:55 AM, Joachim Eastwood wrote:
> On 16 July 2014 09:17, Dr. H. Nikolaus Schaller wrote:
>> Am 15.07.2014 um 14:45 schrieb Joachim Eastwood:
>>
>>> Hi Marek,
>>>
>>> You seem to add some DT nodes for hw that doesn't have drivers in
>>> ma
On Thu 2014-07-17 20:54:35, Alex Elder wrote:
> On 07/17/2014 08:37 PM, Kay Sievers wrote:
> > On Thu, Jul 17, 2014 at 7:59 PM, Alex Elder wrote:
> >> This series rearranges the log code in such a way that the LOG_CONT
> >> and LOG_PREFIX log record flags can be eliminated entirely. The
> >> resu
On 2014-7-18 0:58, Luck, Tony wrote:
>> Tony, if it is ok with you, I will modify the patch and will not select
>> ACPI_LEGACY_TABLES_LOOKUP on IA64, I'm waiting for your final confirmation.
>
> Confirmed. Thanks Peter for catching this.
Great, I will update the patch and send out soon.
Thanks
On 18/07/14 07:34, Bruno Wolff III wrote:
On Thu, Jul 17, 2014 at 14:35:02 +0200,
Peter Zijlstra wrote:
In any case, can someone who can trigger this run with the below; its
'clean' for me, but supposedly you'll trigger a FAIL somewhere.
I got a couple of fail messages.
dmesg output is a
On (Fri) 18 Jul 2014 [17:14:08], Herbert Xu wrote:
> On Fri, Jul 18, 2014 at 02:26:26PM +0530, Amit Shah wrote:
> >
> > > Sounds like a good idea to me. Though, changes in core.c that
> > > increase the time in hwrng_register() or hwrng_init() may not get
> > > noticed by rng drivers and they may
On Mon, Jul 14, 2014 at 06:54:11PM +0100, Dietmar Eggemann wrote:
> __update_entity_runnable_avg() has an additional parameter 'running' so
> that it can be called for
>
> a) sched_entities in update_entity_load_avg():
>
> __update_entity_runnable_avg(..., se->on_rq, cfs_rq->curr == se))
>
>
On 17.07.2014 16:58, Peter Zijlstra wrote:
> On Thu, Jul 17, 2014 at 04:31:04PM +0900, Michel Dänzer wrote:
>>
>> I've been running into the panic captured in the attached picture (hope
>> it's legible) randomly while running 3.16-rc4 and -rc5. I haven't
>> noticed any pattern as to when it happens
Hello,
On 07/18/2014 04:23 PM, Gioh Kim wrote:
>
>
> 2014-07-18 오후 4:50, Marek Szyprowski 쓴 글:
>> Hello,
>>
>> On 2014-07-18 08:45, Gioh Kim wrote:
>>> For page migration of CMA, buffer-heads of lru should be dropped.
>>> Please refer to https://lkml.org/lkml/2014/7/4/101 for the history.
>>>
>>
- remove comma after end of list delimiter
The empty entry must always be the last item in the list, thus there
is no point in having a trailing comma to facilitate adding
succeding entries.
Remove the comma, so that inadvertedly adding an entry after the end
of list sentinel will produce
1 - 100 of 992 matches
Mail list logo
