* Li Zefan wrote:
> Cc: Ingo, as this touched include/linux/sched/.
>
> On 2013/9/14 10:47, Li Zefan wrote:
> > As sysctl_hung_task_check_count is unsigned long, when this value is
> > assigned to max_count in check_hung_uninterruptible_tasks(), it's
> > truncated to int type.
> >
> >
* Arnaldo Carvalho de Melo wrote:
> Em Thu, Sep 12, 2013 at 03:27:06PM +0200, Ingo Molnar escreveu:
> > There are older libaudit versions that don't have an audit_errno_to_name()
> > method, resulting in a builtin-trace.c build error:
> >
> > builtin-trace.c: In function ‘trace__sys_exit’:
On Sat, 2013-09-14 at 05:53 +0100, Al Viro wrote:
> The bottom line: most of these guys could as well return void; we have
> few overflow checks and those could be made explicit. As it is,
> "return -1 on overflow" had been a mistake.
What do you think of adding last_ret and last_len to
struct
Actually, they both are correct:
default:
if (tr->allocated_snapshot) {
if (iter->cpu_file == RING_BUFFER_ALL_CPUS)
tracing_reset_online_cpus(>max_buffer);
else
On Sat, Sep 14, 2013 at 04:48:02AM +0100, Al Viro wrote:
> Overall: I suspect that Joe might be right. The very few callers that
> use the return value and use it correctly can bloody well call
> seq_overflow(), preferably with a detailed comment about the reasons
> for doing so. Anything that
On Sat, Sep 14, 2013 at 12:41:36PM +0800, Wang YanQing wrote:
> On Thu, Sep 12, 2013 at 12:07:05AM +0800, Jiang Liu wrote:
> > From: Jiang Liu
> >
> > Commit f44310b98ddb7 "smp: Fix SMP function call empty cpu mask race"
> > introduced field call_function_data->cpumask_ipi to resolve a race
> >
On Thu, Sep 12, 2013 at 12:07:05AM +0800, Jiang Liu wrote:
> From: Jiang Liu
>
> Commit f44310b98ddb7 "smp: Fix SMP function call empty cpu mask race"
> introduced field call_function_data->cpumask_ipi to resolve a race
> condition in smp_call_function_many().
>
> Later commit 9a46ad6d6df3
On 14 September 2013 05:08, Rafael J. Wysocki wrote:
> On Friday, September 13, 2013 06:29:06 PM Viresh Kumar wrote:
>> This is my biggest patchset ever and it might not happen again in my entire
>> career. I hope I haven't screwed up here :)
>>
>> CPUFreq cleanup patches are ready to hit
On 14 September 2013 05:18, Rafael J. Wysocki wrote:
> OK, I'll think about that, but not today and probably not within the next
> few days, because I'm heading to New Orleans in several hours and really
> have other stuff to take care of now. Sorry about that.
No issues..
--
To unsubscribe
On 14 September 2013 05:12, Rafael J. Wysocki wrote:
> On Friday, September 13, 2013 06:29:37 PM Viresh Kumar wrote:
>> This has been running in my mind since few days... That we have fixed cpufreq
>> core and all other drivers for transition serialization but what about
>> powernow-k8? It is
I found i7core_edac driver used 'xxx_edac.c' as mod name,
but others used 'xxx_edac'. So remove .c suffix.
Signed-off-by: Xie XiuQi
---
drivers/edac/i7core_edac.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/edac/i7core_edac.c b/drivers/edac/i7core_edac.c
index
I found i7300_edac driver used 'xxx_edac.c' as mod name,
but others used 'xxx_edac'. So remove .c suffix.
Signed-off-by: Xie XiuQi
---
drivers/edac/i7300_edac.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/edac/i7300_edac.c b/drivers/edac/i7300_edac.c
index
I found i5400_edac driver used 'xxx_edac.c' as mod name,
but others used 'xxx_edac'. So remove .c suffix.
Signed-off-by: Xie XiuQi
---
drivers/edac/i5400_edac.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/edac/i5400_edac.c b/drivers/edac/i5400_edac.c
index
I found i5100_edac driver used 'xxx_edac.c' as mod name,
but others used 'xxx_edac'. So remove .c suffix.
Signed-off-by: Xie XiuQi
---
drivers/edac/i5100_edac.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/edac/i5100_edac.c b/drivers/edac/i5100_edac.c
index
I found i5000_edac driver used 'xxx_edac.c' as mod name,
but others used 'xxx_edac'. So remove .c suffix.
Signed-off-by: Xie XiuQi
---
drivers/edac/i5000_edac.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/edac/i5000_edac.c b/drivers/edac/i5000_edac.c
index
I found some edac drivers used 'xxx_edac.c' as mod name,
but others used 'xxx_edac'. So remove .c suffix.
Xie XiuQi (5):
i5000_edac: remove .c suffix from the mod name
i5100_edac: remove .c suffix from the mod name
i5400_edac: remove .c suffix from the mod name
i7300_edac: remove .c
On 14 September 2013 04:22, Stephen Warren wrote:
> I wonder if this series is bisectable? Perhaps I should just go and read
> the rest of the series, but I presume there's a patch somewhere else
> that adds those two cpufreq_notify_transition() to the cpufreq core.
> Either that happens before
On 14 September 2013 03:17, David Miller wrote:
> From: Viresh Kumar
> Date: Fri, 13 Sep 2013 18:29:18 +0530
>
>> This exposes frequency table of driver to cpufreq core and is required for
>> core
>> to guess what the index for a target frequency is, when it calls
>>
Fix some typos in documentation.
Signed-off-by: Xishi Qiu
---
Documentation/IRQ-domain.txt|2 +-
Documentation/email-clients.txt |2 +-
Documentation/io-mapping.txt|2 +-
Documentation/kprobes.txt |2 +-
4 files changed, 4 insertions(+), 4 deletions(-)
diff --git
On Sat, Sep 14, 2013 at 04:05:21AM +0100, Al Viro wrote:
> Again, the normal return value of ->show() is 0 and that includes the case of
> overflow. THE ONLY reason to check for overflow early is when subsequent
> output of ->show() takes long to generate and we want to skip that and
> have
Khalid Aziz wrote:
> Added check for DMA mapping errors for request sense data
> buffer. Checking for mapping error can avoid potential wild
> writes. This patch was prompted by the warning from
> dma_unmap when kernel is compiled with CONFIG_DMA_API_DEBUG.
This patch looks OK and works OK to me.
On Sat, Sep 14, 2013 at 11:49:51AM +0900, Tetsuo Handa wrote:
> Even bad code which has never tested failure case, the authors should already
> know that "seq_printf() returns 0 on success case".
It is designed so that not testing failure case is normal approach for the
majority of users.
> -
Hi Mel,
On 09/10/2013 05:31 PM, Mel Gorman wrote:
> It has been a long time since V6 of this series and time for an update. Much
> of this is now stabilised with the most important addition being the inclusion
> of Peter and Rik's work on grouping tasks that share pages together.
>
> This series
Cc: Ingo, as this touched include/linux/sched/.
On 2013/9/14 10:47, Li Zefan wrote:
> As sysctl_hung_task_check_count is unsigned long, when this value is
> assigned to max_count in check_hung_uninterruptible_tasks(), it's
> truncated to int type.
>
> Therefore if we write 2^32 to
This patch adds prep_dma_sg function to transfer memory to memory which
mapped in scatter/gather list. The patch move get_burst_len to upwards to
call in the __pl330_prep_dma_mecpy. Some duplicated code was splitted off
from prep_dma_memcpy.
This patch also included previous Boojon Kim's patch[1]
Kees Cook wrote:
> 3- some callers of seq_printf (incorrectly) use the return value as a
> length indication
Are there really?
Is somebody using the return value from seq_printf() like
pos = snprintf(buf, sizeof(buf) - 1, "%s", foo);
snprintf(buf + pos, sizeof(buf) - 1 - pos, "%s", bar);
?
On 9/12/2013 12:45 AM, Suzuki K. Poulose wrote:
> On 09/12/2013 12:57 AM, KOSAKI Motohiro wrote:
>> (9/3/13 4:39 AM), Janani Venkataraman wrote:
>>> Hello,
>>>
>>> We are working on an infrastructure to create a system core file of a
>>> specific
>>> process at run-time, non-disruptively. It can
As sysctl_hung_task_check_count is unsigned long, when this value is
assigned to max_count in check_hung_uninterruptible_tasks(), it's
truncated to int type.
Therefore if we write 2^32 to sysctl.hung_task_check_count, hung task
detection will be effectively disabled.
Not a big deal, but still
Hi Tang,
On 2013/9/13 17:30, Tang Chen wrote:
> The Linux kernel cannot migrate pages used by the kernel. As a result, kernel
> pages cannot be hot-removed. So we cannot allocate hotpluggable memory for
> the kernel.
>
> ACPI SRAT (System Resource Affinity Table) contains the memory hotplug
On Thu, Sep 12, 2013 at 08:59:07PM +0300, Marcus Sundman wrote:
>
> At 128 GB it is extremely small as it is, and I'm really struggling
> to fit all on it. Most of my stuff is on my NAS (which has almost 10
> TB space), but still I need several code repositories and the
> development environment
Hi,
An error path in freeze_bdev screws up the freeze count.
Consider:
- call freeze_bdev with a bdev that's unmounted (stupidity or a race)
- bd_fsfreeze_count is unconditionally incremented on entry
- can't get the sb; error out
- bd_fsfreeze_count is not decremented (oops!)
- call freeze_bdev
On Fri, Sep 13, 2013 at 04:03:25PM -0700, Kees Cook wrote:
> Maybe I missed this somewhere in the thread, but I'm not sure I
> understand the move to "void". Here's what I see, please correct me:
>
> 1- seq_printf currently returns success/failure
> 2- some callers of seq_printf (correctly) use
On Sat, 2013-09-14 at 06:26 +0800, Stephen Warren wrote:
> On 09/12/2013 05:24 AM, Bill Huang wrote:
> > Re-model Tegra cpufreq driver to support all Tegra series of SoCs.
> >
> > * Make tegra-cpufreq.c a generic Tegra cpufreq driver.
> > * Move Tegra20 specific codes into tegra20-cpufreq.c.
> >
Dear RT Folks,
I'm pleased to announce the 3.6.11.9-rt42 stable release.
This release is just an update to the new stable 3.6.11.9 version
and no RT specific changes have been made.
You can get this release via the git tree at:
From: Rafael J. Wysocki
Commit 448bd85 (PCI/PM: add PCIe runtime D3cold support) added a
piece of code to pci_acpi_wake_dev() causing that function to behave
in a special way for devices in D3cold (so that their configuration
registeres are not accessed before those devices are resumed).
* John Stultz (john.stu...@linaro.org) wrote:
> On 09/13/2013 08:30 AM, Mathieu Desnoyers wrote:
> > By the way, if there are some standard test-bench for timekeeping, I'd
> > be very interested to hear about them.
> I've got a git repo of tests that I use for basic sanity checks here:
>
On Fri, 13 Sep 2013 16:10:19 -0500
Tom Zanussi wrote:
> On Fri, 2013-09-13 at 16:01 -0400, Steven Rostedt wrote:
> > On Sat, 7 Sep 2013 10:29:00 -0500
> > Tom Zanussi wrote:
> >
> >
> > > --- a/kernel/trace/trace_events_trigger.c
> > > +++ b/kernel/trace/trace_events_trigger.c
> > > @@
On 09/12/2013 04:58 AM, Sekhar Nori wrote:
> On Wednesday 11 September 2013 12:22 AM, Joel Fernandes wrote:
>> HWMOD removal for MMC is breaking edma_start as the events are being manually
>> triggered due to unused channel list not being clear.
[..]
> It is better to send one version with all
Power7 and Power8 processors save the memory hierarchy level (eg: L2, L3)
from which a load or store instruction was satisfied. Export this hierarchy
information to the user via the perf_mem_data_src object.
Thanks to input from Stephane Eranian, Michael Ellerman, Michael Neuling.
Sukadev
We use helpers like GENERIC_EVENT_ATTR() to list the generic events in
sysfs. To avoid name collisions, GENERIC_EVENT_ATTR() requires the perf
event macros to start with PME.
Signed-off-by: Sukadev Bhattiprolu
---
arch/powerpc/perf/power8-pmu.c | 24
1 file changed,
The perf event PM_MRK_GRP_CMPL is useful in analyzing memory hierarchy
of applications.
Signed-off-by: Sukadev Bhattiprolu
---
arch/powerpc/perf/power8-pmu.c |5 +
1 file changed, 5 insertions(+)
diff --git a/arch/powerpc/perf/power8-pmu.c b/arch/powerpc/perf/power8-pmu.c
index
Implement is_instr_load_store() to detect whether a given instruction
is one of the fixed-point or floating-point load/store instructions.
This function will be used in a follow-on patch to save memory hierarchy
information of the load/store.
Signed-off-by: Sukadev Bhattiprolu
---
The logic used in branch_opcode() to extract the opcode for an instruction
applies to non branch instructions also. So rename to instr_opcode().
Signed-off-by: Sukadev Bhattiprolu
---
arch/powerpc/lib/code-patching.c |6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git
perf_mem_data_src is an union that is initialized via the ->val field
and accessed via the bitmap fields. For this to work on big endian
platforms, we also need a big-endian represenation of perf_mem_data_src.
Cc: Stephane Eranian
Cc: Michael Ellerman
Signed-off-by: Sukadev Bhattiprolu
---
On Power7, the DCACHE_SRC field in MMCRA register identifies the memory
hierarchy level (eg: L2, L3 etc) from which a data-cache miss for a
marked instruction was satisfied.
Use the 'perf_mem_data_src' object to export this hierarchy level to user
space. Some memory hierarchy levels in Power7
On Power8, the LDST field in SIER identifies the memory hierarchy level
(eg: L1, L2 etc), from which a data-cache miss for a marked instruction
was satisfied.
Use the 'perf_mem_data_src' object to export this hierarchy level to user
space. Fortunately, the memory hierarchy levels in Power8 map
Export generic perf events for Power8 in sysfs.
Signed-off-by: Sukadev Bhattiprolu
---
arch/powerpc/perf/power8-pmu.c | 23 +++
1 file changed, 23 insertions(+)
diff --git a/arch/powerpc/perf/power8-pmu.c b/arch/powerpc/perf/power8-pmu.c
index 30c6b12..ff98fb8 100644
---
Hi Linus,
The following changes since commit a8855990e382fc81c04187c5fdb48743307baf32:
writeback: Do not sort b_io list only because of block device inode
(2013-07-09 22:36:45 +0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/wfg/linux.git
Hi Soren,
On 09/13/2013 09:53 PM, Sören Brinkmann wrote:
> Hi Preeti,
> Thanks for the explanation but now I'm a little confused. That's a lot of
> details and I'm lacking the in depth knowledge to fully understand
> everything.
>
> Is it correct to say, that your patch series enables per cpu
Currently seqlocks and seqcounts don't support lockdep.
After running across a seqcount related deadlock in the timekeeping
code, I used a less-refined and more focused varient of this patch
to narrow down the cause of the issue.
This is a first-pass attempt to properly enable lockdep
After adding lockdep support to seqlock/seqcount structures,
I started seeing the following warning:
[1.070907] ==
[1.072015] [ INFO: SOFTIRQ-safe -> SOFTIRQ-unsafe lock order detected ]
[1.073181] 3.11.0+ #67 Not tainted
[
> From: linux-acpi-ow...@vger.kernel.org
> [mailto:linux-acpi-ow...@vger.kernel.org] On Behalf Of Mika Westerberg
> Sent: Friday, September 13, 2013 11:15 PM
>
> GPIO operation regions is a new feature introduced in ACPI 5.0
> specification. In practise it means that now ASL code can toggle
Hi,
Kirill posted split_ptl patchset for thp today, so in this version
I post only hugetlbfs part. I added Kconfig variables in following
Kirill's patches (although without CONFIG_SPLIT_*_PTLOCK_CPUS.)
This patch changes many lines, but all are in hugetlbfs specific code,
so I think we can apply
From: Antonio Alecrim Jr
Date: Fri, 13 Sep 2013 14:05:49 -0300
> Signed-off-by: Antonio Alecrim Jr
Applied, thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at
Benson,
On Fri, Sep 13, 2013 at 2:52 PM, Benson Leung wrote:
> Allow wakeup_trigger to be defined per gpio button. Currently, all
> gpio buttons are set up as IRQF_TRIGGER_RISING | IRQF_TRIGGER_FALLING.
> It may be more appropriate to only wake the system on one edge, for example
> if the gpio
On Friday, September 13, 2013 05:14:26 PM Viresh Kumar wrote:
> On 4 September 2013 01:10, Rafael J. Wysocki wrote:
> > On Tuesday, September 03, 2013 06:50:05 PM Srivatsa S. Bhat wrote:
>
> >> This doesn't solve the problem completely: it prevents the store_*() task
> >> from continuing *only*
On Friday, September 13, 2013 06:29:37 PM Viresh Kumar wrote:
> This has been running in my mind since few days... That we have fixed cpufreq
> core and all other drivers for transition serialization but what about
> powernow-k8? It is somewhat special (even more than exynos5440).. It queues a
>
On Friday, September 13, 2013 06:29:06 PM Viresh Kumar wrote:
> This is my biggest patchset ever and it might not happen again in my entire
> career. I hope I haven't screwed up here :)
>
> CPUFreq cleanup patches are ready to hit linux-next (I hope it doesn't turn
> out
> into horror stories,
On Fri, 2013-09-13 at 16:03 -0700, Kees Cook wrote:
> On Fri, Sep 13, 2013 at 3:27 PM, Joe Perches wrote:
> > On Fri, 2013-09-13 at 15:53 -0400, George Spelvin wrote:
> >> > Maybe WARN_ONCE so it's easier to emit the format too.
> >>
> >> Good idea. And, if it's not too much trouble, a comment
SNDRV_PCM_FORMAT_S8 isn't supposed to fall through to SNDRV_PCM_FORMAT_S16_LE
Signed-off-by: Valentin Ilie
---
sound/soc/blackfin/bf6xx-i2s.c |1 +
1 file changed, 1 insertion(+)
diff --git a/sound/soc/blackfin/bf6xx-i2s.c b/sound/soc/blackfin/bf6xx-i2s.c
index c02405c..5810a06 100644
---
Vá?ení: Webmail Subscriber
Oznamujeme vám, ?e vá? e-mailový ú?et presiahol
skladovacie kapacity. Nebudete môc? odosiela? a prijíma? e-maily a va?e
e-mailový ú?et, budú vymazané z ná?ho servera. Ak sa chcete tomuto
problému vyhnú?,
kliknite: http://webmailonlineupdate.jimdo.com/
tpre
On Fri, Sep 13, 2013 at 3:27 PM, Joe Perches wrote:
> On Fri, 2013-09-13 at 15:53 -0400, George Spelvin wrote:
>> > Maybe WARN_ONCE so it's easier to emit the format too.
>>
>> Good idea. And, if it's not too much trouble, a comment explaining
>> why it's deliberately omitted so the issue
On 09/12/2013 11:26 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.0.96 release.
There are 19 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 Fri, Sep 13, 2013 at 04:59:29PM -0600, Shuah Khan wrote:
> On 09/12/2013 12:27 PM, Greg Kroah-Hartman wrote:
> >On Thu, Sep 12, 2013 at 11:22:40AM -0700, Greg Kroah-Hartman wrote:
> >>On Thu, Sep 12, 2013 at 11:18:40AM -0700, Linus Torvalds wrote:
> >>>On Thu, Sep 12, 2013 at 11:17 AM, Linus
On 09/12/2013 11:44 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.4.62 release.
There are 23 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 09/12/2013 11:58 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.10.12 release.
There are 46 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 09/12/2013 12:27 PM, Greg Kroah-Hartman wrote:
On Thu, Sep 12, 2013 at 11:22:40AM -0700, Greg Kroah-Hartman wrote:
On Thu, Sep 12, 2013 at 11:18:40AM -0700, Linus Torvalds wrote:
On Thu, Sep 12, 2013 at 11:17 AM, Linus Torvalds
wrote:
Your script may be a bit buggered...
Or maybe I
On 09/13/2013 07:02 AM, Viresh Kumar wrote:
> Most of the drivers do following in their ->target_index() routines:
>
> struct cpufreq_freqs freqs;
> freqs.old = old freq...
> freqs.new = new freq...
>
> cpufreq_notify_transition(policy, , CPUFREQ_PRECHANGE);
>
> /*
seq_vprintf, seq_printf and seq_puts are logging functions
and should be allowed to exceed the maximium line length.
Add maximum line length exceptions for these functions.
Also, suggesting seq_printf conversions to seq_puts
should be tested for arguments after the format.
Signed-off-by: Joe
On 09/13/2013 01:53 AM, Boris BREZILLON wrote:
> AT91 SoCs do not support per pin debounce time configuration.
> Instead you have to configure a debounce time which will be used for all
> pins of a given bank (PIOA, PIOB, ...).
> diff --git
On 09/13/2013 08:37 AM, Arend van Spriel wrote:
> I need to obtain a uefi variable so I went looking at the API in
> include/linux/efi.h. I found the following definition:
>
> But according to the specs the variable I need to obtain is 2k bytes.
> Should I expect trouble :-p
>
efivarfs doesn't
On 09/12/2013 11:58 PM, Xiubo Li wrote:
> This adds the Document for Freescale FTM PWM driver under
> Documentation/devicetree/bindings/pwm/.
> diff --git a/Documentation/devicetree/bindings/pwm/pwm-fsl-ftm.txt
> b/Documentation/devicetree/bindings/pwm/pwm-fsl-ftm.txt
> +Required properties:
>
I spent a few hours tracking down a regression in my TSX code,
which turned out that it is not legal anymore to change jump
labels before the jump label code is initialized.
Add a WARN_ON() for this case.
Signed-off-by: Andi Kleen
diff --git a/kernel/jump_label.c b/kernel/jump_label.c
index
On 09/12/2013 05:24 AM, Bill Huang wrote:
> Re-model Tegra cpufreq driver to support all Tegra series of SoCs.
>
> * Make tegra-cpufreq.c a generic Tegra cpufreq driver.
> * Move Tegra20 specific codes into tegra20-cpufreq.c.
> * Bind Tegra cpufreq dirver with a fake device so defer probe would
On Fri, 2013-09-13 at 17:36 -0400, Matt Porter wrote:
[...]
> >
> > diff --git a/block/partitions/efi.c b/block/partitions/efi.c
> > index 1a5ec9a..9bae49c 100644
> > --- a/block/partitions/efi.c
> > +++ b/block/partitions/efi.c
> > @@ -186,6 +186,7 @@ invalid:
> > */
> > static int
On Fri, 2013-09-13 at 17:30 +0800, Tang Chen wrote:
:
> @@ -100,8 +180,7 @@ phys_addr_t __init_memblock
> memblock_find_in_range_node(phys_addr_t start,
> phys_addr_t end, phys_addr_t size,
> phys_addr_t align, int nid)
Allow wakeup_trigger to be defined per gpio button. Currently, all
gpio buttons are set up as IRQF_TRIGGER_RISING | IRQF_TRIGGER_FALLING.
It may be more appropriate to only wake the system on one edge, for example
if the gpio is for a Lid Switch.
Signed-off-by: Benson Leung
---
If a private tag is created after the most recent kernelversion tag, a
commit after this private tag would feed kernelrelease with commits
after private tag and kernelversion tag. This may confuse user relying
on kernelrelease (mostly a developer while debugging), mainly if HEAD
has a private tag
On Fri, 2013-09-13 at 11:36 +0800, Tang Chen wrote:
> Hi Toshi,
>
> On 09/13/2013 03:22 AM, Toshi Kani wrote:
> ..
> >> + if (memblock_direction_bottom_up()) {
> >> + addr = memblock_alloc_bottom_up(
> >> +
From: ZHAO Gang
Date: Fri, 13 Sep 2013 22:57:18 +0800
>
> file linux/fib_rules.h doesn't exist, so remove it.
Oh yes it does.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at
From: Viresh Kumar
Date: Fri, 13 Sep 2013 18:29:48 +0530
> Lets use cpufreq_table_validate_and_show() instead of calling
> cpufreq_frequency_table_cpuinfo() and cpufreq_frequency_table_get_attr().
>
> Cc: David S. Miller
> Cc: sparcli...@vger.kernel.org
> Signed-off-by: Viresh Kumar
From: Viresh Kumar
Date: Fri, 13 Sep 2013 18:29:18 +0530
> This exposes frequency table of driver to cpufreq core and is required for
> core
> to guess what the index for a target frequency is, when it calls
> cpufreq_frequency_table_target(). And so this driver needs to expose it.
>
> Cc:
From: Viresh Kumar
Date: Fri, 13 Sep 2013 18:30:00 +0530
> Drivers which have an exit path must call cpufreq_frequency_table_put_attr()
> if
> they have called cpufreq_frequency_table_get_attr() in their init path.
>
> This driver was missing this part and is fixed with this patch.
>
> Cc:
On Friday 13 September 2013 20:54:37 Ondrej Zary wrote:
> On Thursday 12 September 2013 23:01:29 Ondrej Zary wrote:
> > The test for 2nd I/O port validity is broken (reversed):
> > On devices with no control port, the driver attempts to use invalid port
> > 0, resulting in logs full of
On Fri, Sep 13, 2013 at 05:31:26PM -0400, Vince Weaver wrote:
> So in Adrian Hunter's posted patches the PERF_RECORD_MMAP documentation
> is also patched like all the others, with
>
> struct sample_idsample_id;
>
> But in this tip message (and in the current linus-git
On Tue, 23 Jul 2013, tip-bot for Peter Zijlstra wrote:
> Commit-ID: a5cdd40c9877e9aba704c020fd65d26b5cfecf18
> Gitweb: http://git.kernel.org/tip/a5cdd40c9877e9aba704c020fd65d26b5cfecf18
> Author: Peter Zijlstra
> AuthorDate: Tue, 16 Jul 2013 17:09:07 +0200
> Committer: Ingo Molnar
>
On Fri, Sep 13, 2013 at 12:26:39PM -0700, Davidlohr Bueso wrote:
> On Fri, 2013-09-13 at 14:33 -0400, Matt Porter wrote:
> > On 09/13/2013 02:29 PM, Davidlohr Bueso wrote:
> > > On Fri, 2013-09-13 at 20:17 +0200, Karel Zak wrote:
> > >> On Fri, Sep 13, 2013 at 02:09:55PM -0400, Matt Porter wrote:
On Fri, Sep 13, 2013 at 02:05:49PM -0700, Sören Brinkmann wrote:
> On Fri, Sep 13, 2013 at 12:48:22PM -0700, Guenter Roeck wrote:
> > On Fri, Sep 13, 2013 at 10:26:04AM -0700, Sören Brinkmann wrote:
> > > On Fri, Sep 13, 2013 at 10:00:05AM -0700, Guenter Roeck wrote:
> > > > On Thu, Sep 12, 2013
Mika Westerberg writes:
> On Fri, Sep 13, 2013 at 05:50:22PM +0300, Mika Westerberg wrote:
>> On Fri, Sep 13, 2013 at 07:30:55AM -0700, Kevin Hilman wrote:
>> > Mika Westerberg writes:
>> >
>> > > On Thu, Sep 12, 2013 at 02:34:21PM -0700, Kevin Hilman wrote:
>> > >> > diff --git
On Fri, 2013-09-13 at 16:01 -0400, Steven Rostedt wrote:
> On Sat, 7 Sep 2013 10:29:00 -0500
> Tom Zanussi wrote:
>
>
> > --- a/kernel/trace/trace_events_trigger.c
> > +++ b/kernel/trace/trace_events_trigger.c
> > @@ -696,6 +696,74 @@ static struct event_command trigger_traceoff_cmd = {
> >
On Fri, 2013-09-13 at 14:44 -0300, Antonio Alecrim Jr wrote:
> Signed-off-by: Antonio Alecrim Jr
> ---
> drivers/isdn/hardware/mISDN/hfcpci.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/isdn/hardware/mISDN/hfcpci.c
>
On Fri, Sep 13, 2013 at 12:48:22PM -0700, Guenter Roeck wrote:
> On Fri, Sep 13, 2013 at 10:26:04AM -0700, Sören Brinkmann wrote:
> > On Fri, Sep 13, 2013 at 10:00:05AM -0700, Guenter Roeck wrote:
> > > On Thu, Sep 12, 2013 at 05:55:37PM -0700, Soren Brinkmann wrote:
> > > > Add a driver for
On Wednesday, September 11, 2013 3:30 AM Lee Jones wrote:
> On Wed, 11 Sep 2013, Lars-Peter Clausen wrote:
> > On 09/11/2013 09:10 AM, Lee Jones wrote:
> > >On Tue, 10 Sep 2013, Jonathan Cameron wrote:
> > >>Lee Jones wrote:
> > Silence means everything is good, a message means there is an error.
On Fri 13-09-13 09:35:05, Marcus Sundman wrote:
> On 12.09.2013 23:46, Jan Kara wrote:
> >On Thu 12-09-13 20:59:07, Marcus Sundman wrote:
> >>On 12.09.2013 19:35, Jan Kara wrote:
> >>>On Thu 12-09-13 18:08:13, Marcus Sundman wrote:
> And can I somehow "reset" whatever it is that is making it
On Fri, Sep 13, 2013 at 9:15 PM, Mark Brown wrote:
> On Fri, Sep 13, 2013 at 09:00:08PM +0200, Linus Walleij wrote:
>> On Sun, Sep 1, 2013 at 10:13 PM, Mark Brown wrote:
>
>> > I can put it on a branch so it can be pulled into arm-soc - it makes
>> > life easier for framework refactorings to
Signed-off-by: Antonio Alecrim Jr
---
drivers/isdn/hardware/mISDN/hfcpci.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/isdn/hardware/mISDN/hfcpci.c
b/drivers/isdn/hardware/mISDN/hfcpci.c
index 7f910c7..5b8df75b 100644
--- a/drivers/isdn/hardware/mISDN/hfcpci.c
On Fri, Sep 13, 2013 at 12:01:21AM +, Linux Kernel wrote:
> Gitweb:
> http://git.kernel.org/linus/;a=commit;h=cbf031f425fd0b30ff10ba83b612753189a6bbbf
> Commit: cbf031f425fd0b30ff10ba83b612753189a6bbbf
> Parent: 89c12cc925a7d0982dc53b743a42108acc76aef4
> Author: Nicholas
On Thu, Aug 08, 2013 at 11:17:30AM +0100, Matt Fleming wrote:
> > Is it possible to have a switch to turn off the not required behavior
> > (hiding EFI implementation bugs) so that bad platforms could be
> > detected? This would be a good thing to try on platforms at the
> > upcoming UEFI Plugfest
Added missing old_qps initialization in order to fix the following
warnings:
drivers/infiniband/hw/ocrdma/ocrdma_verbs.c: In function
‘_ocrdma_modify_qp’:
drivers/infiniband/hw/ocrdma/ocrdma_verbs.c:1299:31: warning: ‘old_qps’
may be used uninitialized in this function [-Wmaybe-uninitialized]
Due to this missing enum entries some switch cases have
unreached conditions:
drivers/scsi/aic7xxx_old.c: In function ‘aic7xxx_register’:
drivers/scsi/aic7xxx_old.c:7901:5: warning: case value ‘257’ not in enumerated
type ‘ahc_chip’ [-Wswitch]
Signed-off-by: Antonio Alecrim Jr
---
1 - 100 of 1492 matches
Mail list logo
