Hello,
On Wed, Dec 18, 2013 at 04:21:17PM +0900, Joonsoo Kim wrote:
> On Mon, Dec 16, 2013 at 03:43:43PM +0100, Ludovic Desroches wrote:
> > Hello,
> >
> > On Fri, Dec 13, 2013 at 10:59:09AM +0900, Joonsoo Kim wrote:
> > > On Thu, Dec 12, 2013 at 03:36:19PM +0100, Ludovic Desroches wrote:
> > > >
From: Rongjun Ying
After system resume, need send extcon uevent to userspace
Change-Id: I32a9e1c6646035f95765bba79a7acaccb8ce45a7
Signed-off-by: Rongjun Ying
---
drivers/extcon/extcon-gpio.c | 17 +
1 files changed, 17 insertions(+), 0 deletions(-)
diff --git a/drivers/extc
* Namhyung Kim wrote:
> Hello,
>
> I was playing with TUI code and added two new windows. One for
> showing log messages and another for showing header information.
> (Maybe they can be implemented on the GTK code too someday.)
>
> * changes from v1)
> - fix segfault on perf top (Ingo)
>
On Fri, Dec 20, 2013 at 03:13:16PM +0800, Wenliang Fan wrote:
> The checking condition in 'validateFlash2xReadWrite()' is not sufficient.
> A large number invalid would cause an integer overflow and pass
> the condition, which could cause further integer overflows in
> 'Bcmchar.c:bcm_char_ioctl()'.
* Darren Hart wrote:
> On Thu, 2013-12-19 at 15:05 -0800, Randy Dunlap wrote:
> > On 12/19/13 13:07, Darren Hart wrote:
> > > On Thu, 2013-12-19 at 13:00 -0800, Davidlohr Bueso wrote:
> > >> On Thu, 2013-12-19 at 12:51 -0800, Randy Dunlap wrote:
> > >>> On 12/19/13 12:45, Davidlohr Bueso wrote:
* Masami Hiramatsu wrote:
> > But a closer look indicates that the insertion of kprobes is
> > taking about three (!!) orders of magnitude longer than before, as
> > judged by the rate of increase of 'wc -l
> > /sys/kernel/debug/kprobes/list'.
>
> Right, because kprobes are not designed for
On Fri, 2013-12-20 at 15:46 +0800, Wenliang Fan wrote:
> The local variable 'pos' comes from userspace. If a large number was
> passed, there would be an integer overflow in the following line:
> pos += n;
>
What about check before enter into the cycle? If you are talking about
possible hug
On Fri, Dec 20, 2013 at 12:42 PM, Masami Hiramatsu
wrote:
> (2013/12/20 12:07), Jovi Zhangwei wrote:
>> On Fri, Dec 20, 2013 at 10:37 AM, Masami Hiramatsu
>> wrote:
>>> Hi Jovi,
>>>
>>> (2013/12/19 18:37), Jovi Zhangwei wrote:
Hi Masami,
On Thu, Dec 19, 2013 at 5:04 PM, Masami Hira
CONFIG_ACPI dependent code should include instead of
directly including . This patch cleans up such wrong
inclusions for Thinkpad ACPI users.
Cc: Henrique de Moraes Holschuh
Cc: Jaroslav Kysela
Cc: Takashi Iwai
Cc: alsa-de...@alsa-project.org
Cc: ibm-acpi-de...@lists.sourceforge.net
Cc: platf
On Friday 20 December 2013 08:27 AM, Axel Lin wrote:
These settings are not used when using linear_ranges and it makes the code
looks confusing. Thus remove them.
Looks fine.
Acked-by: Laxman Dewangan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
On Thu, 2013-12-19 at 23:56 -0800, Josh Triplett wrote:
> On Thu, Dec 19, 2013 at 02:15:48PM -0800, Joe Perches wrote:
> > On Thu, 2013-12-19 at 13:01 -0800, Ravi Patel wrote:
> > > My name is Ravi Patel and I am working for AppliedMicro.
> > > I am planning to submit APM X-Gene SoC QMTM drivers to
* Chunwei Chen wrote:
> From 362201bf3259cc01c99531766395fdba0c0f3789 Mon Sep 17 00:00:00 2001
> From: Chunwei Chen
> Date: Thu, 19 Dec 2013 15:41:22 +0800
> Subject: [PATCH] perf config: ignore generated files in feature-checks
>
> 1. Rename the test-* binary files to test-*.bin for easier pa
On 10 December 2013 14:37, Ulf Hansson wrote:
> To put devices into low power state during system suspend, it is convenient
> for some runtime PM supported power domains, subsystems and drivers to have
> the option of re-using and invoking the runtime PM callbacks from their system
> PM callbacks.
On 12/19/2013 10:11 PM, Apelete Seketeli wrote:
> The platform data already available in tree for JZ4740 USB Device
> Controller was previously used by an out-of-tree USB gadget driver
> which was not relying on the musb driver and was written by Ingenic
> and the Qi-Hardware community.
>
> Update
On 19/12/2013 20:13, Gerhard Sittig wrote:
On Thu, Dec 19, 2013 at 15:21 +0100, Boris BREZILLON wrote:
Signed-off-by: Boris BREZILLON
---
Documentation/devicetree/bindings/gpio/gpio.txt |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/g
* Peter Zijlstra wrote:
> On Thu, Dec 19, 2013 at 09:40:51PM +0100, Ingo Molnar wrote:
> > > + if (static_cpu_has(X86_FEATURE_CLFLUSH_MONITOR)) {
> > > + mb();
> > > clflush((void *)¤t_thread_info()->flags);
> > > + mb();
> > > +
* David Cohen wrote:
> Prevent sfi_handle_*_dev() to register device in case
> intel_mid_sfi_get_pdata() failed to execute.
>
> Since 'NULL' is a valid return value, this patch makes
> sfi_handle_*_dev() functions to use IS_ERR() to validate returned pdata.
Is this bug triggering in practice?
There is a structure named context_entry used by intel iommu, and there
are some bit operations on it. Use bit structure may make these operations
easy.
Also the function context_set_address_root may cause problem because it uses
|= operation, not set the new value. And this patch can fix it.
Sig
On Thu, Dec 19, 2013 at 07:13:09PM -0800, Linus Torvalds wrote:
> I think we might have to order the two reads with an smp_rmb - making
> sure that we check the lock state first - but I think it should be
> otherwise pretty solid.
> Yeah, I said "spin_contended()" myself initially, but it needs to
On Thu, Dec 19, 2013 at 11:48:26PM -0500, Richard Guy Briggs wrote:
> On 13/12/17, Peter Zijlstra wrote:
> > On Mon, Dec 16, 2013 at 04:03:38PM -0500, Richard Guy Briggs wrote:
> > > task->pid is only ever assigned once (well ok, twice). For system health
> > > and
> > > secure logging confidence
Hi,
2013-12-19 (목), 17:30 +0800, Gu Zheng:
> Move all the bio initialization into __bio_alloc, and some minor cleanups are
> also added.
>
> v2:
> Use 'is_read' rather than 'rw' as Yu Chao suggested.
> Remove the needless initialization of bio->bi_private.
>
> Signed-off-by: Gu Zheng
> ---
Hi Alessandro,
On Thu, Dec 19, 2013 at 06:49:24PM +0100, Alessandro Zummo wrote:
> On Thu, 19 Dec 2013 18:46:18 +0100
> a...@natisbad.org (Arnaud Ebalard) wrote:
>
> > > I don't mind routing it though mvebu/arm-soc since the only consumers
> > > are currently mvebu boards, but I'd like to hear fr
On Thu, Dec 19, 2013 at 02:35:17PM -0800, Joe Perches wrote:
> On Thu, 2013-12-19 at 20:42 +0100, Ingo Molnar wrote:
> > * Davidlohr Bueso wrote:
> >
> > > On Thu, 2013-12-19 at 20:25 +0100, Ingo Molnar wrote:
> > > > * Davidlohr Bueso wrote:
> > > >
> > > > > Signed-off-by: Davidlohr Bueso
>
On Fri, Dec 20, 2013 at 04:51:45PM +0800, Wenliang Fan wrote:
> Thanks for your advice.
> But the variable 'psFlash2xReadWrite->offset' in '
> *drivers/staging/bcm/nvm.c*:validateFlash2xReadWrite()' is also comes from
> user space, which would cause an integer overflow in the following line:
>
> i
On Fri, Dec 13, 2013 at 10:37 AM, Linus Walleij
wrote:
> On Fri, Dec 13, 2013 at 10:24 AM, wrote:
>> José Miguel Gonçalves wrote:
> (..)
>>> Was this patch forgotten?
>>>
>> Hi Jose,
>>
>> Sorry about missing your patch. It's my fault :( and as you know, at this
>> moment the file will be remove
On Fri, Dec 13, 2013 at 2:35 PM, Axel Lin wrote:
> Set g->out_bit bit for gpio output high, clear g->out_bit bit for gpio output
> low.
>
> Signed-off-by: Axel Lin
> ---
> Hi Bjorn,
> I don't have the datasheet, just found current code does not make sense
> because current code unconditionally s
At Fri, 20 Dec 2013 16:30:42 +0800,
Lv Zheng wrote:
>
> CONFIG_ACPI dependent code should include instead of
> directly including . This patch cleans up such wrong
> inclusions for Thinkpad ACPI users.
>
> Cc: Henrique de Moraes Holschuh
> Cc: Jaroslav Kysela
> Cc: Takashi Iwai
> Cc: alsa-de
On Fri, Dec 20, 2013 at 12:37:10AM -0800, Joe Perches wrote:
> On Thu, 2013-12-19 at 23:56 -0800, Josh Triplett wrote:
> > On Thu, Dec 19, 2013 at 02:15:48PM -0800, Joe Perches wrote:
> > > On Thu, 2013-12-19 at 13:01 -0800, Ravi Patel wrote:
> > > > My name is Ravi Patel and I am working for Appli
On Fri, 2013-12-20 at 01:16 -0800, Josh Triplett wrote:
> Duplicating the regex seems awful. Could you put it in a variable?
awful is a strong word and I don't have any
issue with the duplication. Using a variable
is just as confusing as any duplication.
Using a separate test and message for th
Hi,
2013-12-20 (금), 10:14 +0800, Chao Yu:
> Hi Kim,
>
> One comment as following:
>
> > -Original Message-
> > From: Jaegeuk Kim [mailto:jaegeuk@samsung.com]
> > Sent: Wednesday, December 18, 2013 8:12 AM
> > To: linux-fsde...@vger.kernel.org
> > Cc: linux-kernel@vger.kernel.org; lin
Remove sched_clock from the driver and use setup_check_clock
function.
Signed-off-by: Michal Simek
---
Thomas: Can you please review this patch?
I would like to be sure that I have done it correctly.
Thanks,
Michal
---
arch/microblaze/Kconfig| 1 +
arch/microblaze/kernel/timer.c | 27
Sort the exception table at build-time rather than during boot.
Microblaze is the same case as AARCH64 that's why
EM_MICROBLAZE conditional check was added to allow
cross-compilation on machines which are not running
the latest libc-dev.
Inspired by AARCH64 commit:
"arm64: extable: sort the excep
The annual Linux Storage, Filesystem and Memory Management Summit for
2014 will be held on March 24th and 25th before the Linux Foundation
Collaboration summit at The Meritage Resort, Napa Valley, CA.
http://events.linuxfoundation.org/events/linux-storage-filesystem-and-mm-summit
On 19 December 2013 16:48, Bill Huang wrote:
> diff --git a/drivers/cpufreq/Kconfig.arm b/drivers/cpufreq/Kconfig.arm
> index ce52ed9..22dfc43 100644
> --- a/drivers/cpufreq/Kconfig.arm
> +++ b/drivers/cpufreq/Kconfig.arm
> @@ -225,6 +225,18 @@ config ARM_TEGRA_CPUFREQ
> help
> T
On 20/12/13 01:44, Chen Gang wrote:
> On 12/19/2013 09:47 PM, James Hogan wrote:
>> No, I believe there shouldn't be any use of the C 64bit division/modulo
>> operations in generic kernel code in the first place, so like I said
>> before the code in question should be fixed to use the proper functi
On Mon, Dec 16, 2013 at 11:42 AM, Dan Carpenter
wrote:
> This should be ">= ARRAY_SIZE()" instead of "> ARRAY_SIZE()".
>
> Fixes: f365be092572 ('pinctrl: Add Qualcomm TLMM driver')
> Signed-off-by: Dan Carpenter
This appears to be fixed already by one of Björn's follow-up
patches, so dropping t
The regmap used by max77686 MFD driver was not freed with regmap_exit()
on driver exit. This lead to leak of resources.
Replace regmap_init_i2c() call in driver probe with initialization of
managed register map so the regmap will be properly freed by the device
management code.
Signed-off-by: Krz
(2013/12/20 17:20), Ingo Molnar wrote:
>
> * Masami Hiramatsu wrote:
>
>>> But a closer look indicates that the insertion of kprobes is
>>> taking about three (!!) orders of magnitude longer than before, as
>>> judged by the rate of increase of 'wc -l
>>> /sys/kernel/debug/kprobes/list'.
>>
The MUIC block in max77693 has different I2C address than PMIC. The
driver allocated two regmaps: for PMIC and MUIC. However it used the
same regmap_config (with max_register field) for both regmaps. Actual
maximum address of register for MUIC is different than for PMIC.
Define another regmap_conf
On Tue, Dec 17, 2013 at 1:18 AM, Bjorn Andersson
wrote:
> No matter how we build the individual pinctrl drivers we will always
> need the pinctrl framework in a multi-soc zImage; so I can't see that
> we gain anything from being able to compile PINCTRL as a module.
I discussed this matter with C
> -Original Message-
> From: netdev-ow...@vger.kernel.org [mailto:netdev-
> ow...@vger.kernel.org] On Behalf Of David Miller
> Sent: 19 December 2013 23:53
> To: rashika.khe...@gmail.com
> Cc: Ian Campbell; Wei Liu; xen-de...@lists.xenproject.org;
> net...@vger.kernel.org; linux-kernel@vger
On Mon, Dec 16, 2013 at 5:39 PM, Santosh Shilimkar
wrote:
> On Monday 16 December 2013 10:09 AM, Santosh Shilimkar wrote:
>> The $subject series (2 patches) don't seems to be on your branch.
>>
> Ofcourse Linus needs to ack them before they can be considered.
> I have couple of comments as well s
On Wed, Dec 18, 2013 at 11:07 AM, Grygorii Strashko
wrote:
> This series is intended to update Davinci GPIO driver and reuse
> it for Keystone SoCs, because Keystone uses the similar GPIO IP like Davinci.
> Keystone GPIO IP: supports:
> - up to 32 GPIO lines;
> - only unbanked irqs;
>
> See Docum
> From: Josh Triplett
> On Thu, Dec 19, 2013 at 05:33:09PM -, David Laight wrote:
> > OTOH just including extra headers isn't ideal - it can considerably
> > slow down the compilation time. There are many subsystems that don't
> > really separate their internal headers from their external ones.
Add dictionary information in structure cont.
Dictionary information is added when a driver uses structured printk, and the
information is shown in /dev/kmsg. Current kernel directly stores the
information to log_buf. This patch stores the dict information in structure cont
first, then the informat
On 12/20/13, Prarit Bhargava wrote:
>
>
> On 12/19/2013 01:05 PM, Tony Luck wrote:
>> On Wed, Dec 18, 2013 at 11:50 AM, Tony Luck wrote:
>>> Looks good to me.
>>
>> Though now I've been confused by an offline question about affinity.
>
> Heh :) I'm pursuing it now. Rui has asked a pretty good q
Delete LOG_NEWLINE flag for structured printk.
When structured printk is used, the next printk message is output in a new line
from patch c313af145b9bc4fb8e8e0c83b8cfc10e1b894a50. However, in a following
pseudo SCSI error test, the device information and the detail information are
divided:
-- Pseu
Hi,
This patch set fixes message continuation breakage involved with structured
printk. A SCSI driver may output two continuation error messages like
scmd_printk("foo");
printf("bar\n");
Here, scmd_printk() is structured printk with key/value dictionary information.
Structured printk becam
Move all the bio initialization into __bio_alloc, and some minor cleanups are
also added.
v3:
Use 'bool' rather than 'int' as Kim suggested.
v2:
Use 'is_read' rather than 'rw' as Yu Chao suggested.
Remove the needless initialization of bio->bi_private.
Signed-off-by: Gu Zheng
---
fs/f2fs
there is an overflow in the code :
cyz_polling_cycle = (arg * HZ) / 1000,
the multiplicator arg comes from user, so it may be an overflow if
arg is a big number. And the value of cyc_polling_cycle will be
wrong when it is used next time.
Reported-by: Qixue Xiao
Suggested-by: Yongjian Xu
Suggeste
There are a lot of sparse warnings for early_memremap and early_ioummap
in arch/x86/platform/efi/efi.c and drivers/firmware/efi/efi.c.
early_memremap is for mapping kernel memory instead of io memory, but
the early_memremap returns void __iomem pointer and early_iounmap accepts
__iomem pointer as
There's a lot of sparse warnings for code like below:
void *a = early_memremap(phys_addr, size);
early_memremap intend to map kernel memory with ioremap facility, the return
pointer should be a kernel ram pointer instead of iomem one.
For making the function clearer and supressing sparse warnings
Here is the V7 patchset for supporting kexec kernel efi runtime.
Per pervious discussion I pass the 1st kernel efi runtime mapping
via setup_data to 2nd kernel. Besides of the runtime mapping
info I also pass the fw_vendor, runtime, config table, smbios
physical address in setup_data. EFI spec ment
Export fw_vendor, runtime and config table physical addresses to
/sys/firmware/efi/{fw_vendor,runtime,config_table} because kexec kernel
need them.
>From EFI spec these 3 variables will be updated to
virtual address after entering virtual mode. But
kernel startup code will need the physical addres
Kexec kernel will use saved runtime virtual mapping, so add a
new function efi_map_region_fixed for directly mapping a md
to md->virt.
The md is passed in from 1st kernel, the virtual addr is
saved in md->virt_addr.
Matt: coding style
reuse __map_region
Boris: Strenthen comment lines to 80
Add two small functions:
efi_merge_regions and efi_map_regions, efi_enter_virtual_mode
calls them instead of embedding two long for loop.
v1->v2:
refresh; coding style fixes.
v2->v3:
Toshi Kani:
remove unused variable
Matt: check return value of krealloc.
v3->v4:
Boris: Stretch comment to 80 cols
Add a new setup_data type SETUP_EFI for kexec use.
Passing the saved fw_vendor, runtime, config tables and efi runtime mappings.
When entering virtual mode, directly mapping the efi runtime ragions which
we passed in previously. And skip the step to call SetVirtualAddressMap.
Specially for HP z42
kexec-tools use boot_params for getting the 1st kernel hardware_subarch,
the kexec kernel efi runtime support also need read the old efi_info from
boot_params. Currently it exists in debugfs which is not a good place for
such infomation. Per HPA, we should avoid of "sploit debugfs".
In this patch
Currently e820_reserve_setup_data is called before parsing early params,
it works in normal case. But for memmap=exactmap, the final memory ranges
are created after parsing memmap= cmdline params, so the previous
e820_reserve_setup_data has no effect. For example, setup_data ranges
will still be ma
kexec kernel will need exactly same mapping for
efi runtime memory ranges. Thus here export the
runtime ranges mapping to sysfs, kexec-tools
will assemble them and pass to 2nd kernel via
setup_data.
Introducing a new directory /sys/firmware/efi/runtime-map
Just like /sys/firmware/memmap. Containin
Old kexec-tools can not load new kernel. The reason is kexec-tools do not fill
efi_info in x86 setup header previously, thus efi failed to initialize.
In new kexec-tools it will by default fill efi_info and pass other efi required
infomation to 2nd kernel so kexec kernel efi initialization can succ
variables size and end is useless in this function, thus remove them.
Reported-by: Toshi Kani
Signed-off-by: Dave Young
Acked-by: Borislav Petkov
---
arch/x86/platform/efi/efi_64.c | 6 +-
1 file changed, 1 insertion(+), 5 deletions(-)
diff --git a/arch/x86/platform/efi/efi_64.c b/arch/x8
Current code check boot service region with kernel text region by:
start+size >= __pa_symbol(_text)
The end of the above region should be start + size - 1 instead.
I see this problem in ovmf + Fedora 19 grub boot:
text start: 100 md start: 80 md size: 80
Signed-off-by: Dave Young
Ack
Hi,
Here is the series of perf-probe patches which adds
dwarf(debuginfo) support for uprobes.
Currently perf-probe doesn't support debuginfo for uprobes.
The lack of the debuginfo support for uprobes sometimes
confuses users (or makes them cry) because they can't use
perf-probe as for kprobes ca
Use the actual address of tracepoint as a hint to find
different local symbols. Since sometimes there are local
symbols which have same name, it is impossible to determine
which symbol should be used. This saves the actual address
from debuginfo and use it as a hint later.
The reason why we don't
Support dwarf(debuginfo) based operations for uprobe events.
With this change, perf probe can analyze debuginfo of user
application binary to set up new uprobe event.
This allows perf-probe --add/--line works with -x option.
(Actually, --vars has already accepted -x option)
Signed-off-by: Masami H
Expand given path to absolute path in option parser,
except for a module name. Instead of expanding it later,
this get the absolute path in early stage.
Signed-off-by: Masami Hiramatsu
---
tools/perf/builtin-probe.c|9 +
tools/perf/util/probe-event.c | 11 ++-
2 files c
On 12/10/2013 11:39 AM, Anshuman Khandual wrote:
> On 12/09/2013 11:51 AM, Michael Ellerman wrote:
>> On Wed, 2013-04-12 at 10:32:39 UTC, Anshuman Khandual wrote:
>>> Generic powerpc branch instruction analysis support added in the code
>>> patching library which will help the subsequent patch on S
The checking condition in 'validateFlash2xReadWrite()' is not
sufficient. A large number invalid would cause an integer overflow and
pass the condition, which could cause further integer overflows in
'Bcmchar.c:bcm_char_ioctl()'.
Signed-off-by: Wenliang Fan
---
drivers/staging/bcm/nvm.c | 5
On 12/20/2013 05:30 PM, James Hogan wrote:
> On 20/12/13 01:44, Chen Gang wrote:
>> On 12/19/2013 09:47 PM, James Hogan wrote:
>>> No, I believe there shouldn't be any use of the C 64bit division/modulo
>>> operations in generic kernel code in the first place, so like I said
>>> before the code in
This patch add a --series option to git-quiltimport to allow users to
select the name of series file. This option is an analog of quilt's
QUILT_SERIES environment variable.
Signed-off-by: Wang Nan
---
Documentation/git-quiltimport.txt | 5 +
git-quiltimport.sh| 21 ++
On 12/20/2013 05:31 PM, Viresh Kumar wrote:
On 19 December 2013 16:48, Bill Huang wrote:
diff --git a/drivers/cpufreq/Kconfig.arm b/drivers/cpufreq/Kconfig.arm
index ce52ed9..22dfc43 100644
--- a/drivers/cpufreq/Kconfig.arm
+++ b/drivers/cpufreq/Kconfig.arm
@@ -225,6 +225,18 @@ config ARM_TEGRA
When using the f2fs_io_info in the low level, we still need to merge the
rw and rw_flag, so use the rw to hold all the io flags directly,
and remove the rw_flag field.
ps.It is based on the previous patch:
f2fs: move all the bio initialization into __bio_alloc
Signed-off-by: Gu Zheng
---
fs/f2f
On Tue, Dec 17, 2013 at 05:30:02PM -0700, Bjorn Helgaas wrote:
> After this patch, we would have:
>
> pci_enable_msi() # existing (1 vector)
> pci_enable_msi_block(nvec)# existing
> pci_enable_msi_block_auto(maxvec) # existing (r
* Peter Zijlstra wrote:
> On Thu, Dec 19, 2013 at 02:35:17PM -0800, Joe Perches wrote:
> > On Thu, 2013-12-19 at 20:42 +0100, Ingo Molnar wrote:
> > > * Davidlohr Bueso wrote:
> > >
> > > > On Thu, 2013-12-19 at 20:25 +0100, Ingo Molnar wrote:
> > > > > * Davidlohr Bueso wrote:
> > > > >
> >
On 20 December 2013 15:55, bilhuang wrote:
> Don't you think it worth creating a file here so this can be shared to
> arm64?
We will see how to handle virtual devices when we will start getting
arm64 SoCs. Probably we might end up writing a single file in cpufreq,
if required, that will create vi
We fixed checkpatch errors in the rtl8192e driver and noticed that some
macros that produced errors in checkpatch are unused, so we removed them.
There are no functional changes in this patch.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to ma
Checkpatch mentioned that these macros should be defined with a 'do {...}
while(0)' statement.
So we used grep to find all files using these macros and we found out that
these macros were only used
in rtl819x_Qos.h, in the defines we removed before.
Since the macros are not used anywhere else we
On Thu, Dec 19, 2013 at 08:30:48PM -0800, H. Peter Anvin wrote:
> On 12/19/2013 08:24 PM, joeyli wrote:
> > I agreed, but userspace application should not be too often to access
> > RTC. Maybe only when system boot and set timezone.
>
> This is, quite frankly, an idiotic argument.
TBH, I've been s
This patch fixes the following checkpatch errors from rtllib_endianfree.h:
- ERROR: Macros with complex values should be enclosed in parenthesis
Signed-off-by: Andreas Frembs
Signed-off-by: Matthias Schoepe
---
drivers/staging/rtl8192e/rtllib_endianfree.h | 6 +++---
1 file changed, 3 insertio
On Thu, Dec 19, 2013 at 02:37:22PM -0700, Bjorn Helgaas wrote:
> On Thu, Dec 19, 2013 at 6:42 AM, Alexander Gordeev
> wrote:
> > On Wed, Dec 18, 2013 at 11:58:47AM -0700, Bjorn Helgaas wrote:
> >> If rc == 13 and the device can only use 8, the extra 5 would be
> >> ignored and wasted.
> >>
> >> I
> Also, which kernel are you experiencing this issue on? In 3.12, I
> queued a separate patch to deal with spurious reboot issues on Lynx
> Point:
>
> commit 638298dc66ea36623dbc2757a24fc2c4ab41b016
> Author: Takashi Iwai
> Date: Thu Sep 12 08:11:06 2013 +0200
>
> xhci: Fix spurious wakeu
On 12/20/2013 06:33 PM, Viresh Kumar wrote:
On 20 December 2013 15:55, bilhuang wrote:
Don't you think it worth creating a file here so this can be shared to
arm64?
We will see how to handle virtual devices when we will start getting
arm64 SoCs. Probably we might end up writing a single file
In rtl819x_Qos.h there were several macros defined but never used.
So we removed this macros.
Signed-off-by: Andreas Frembs
Signed-off-by: Matthias Schoepe
---
drivers/staging/rtl8192e/rtl819x_Qos.h | 37 --
1 file changed, 37 deletions(-)
diff --git a/drivers/
From: Benedikt Spranger
Setup and remove the interrupt handler in clock event mode selection.
This avoids calling the (shared) interrupt handler when the device is
not used.
Signed-off-by: Benedikt Spranger
Signed-off-by: Thomas Gleixner
[bigeasy: redo the patch with NR_IRQS_LEGACY which is pr
From: Benedikt Spranger
As default the TCLIB uses the 32KiHz base clock rate for clock events.
Add a compile time selection to allow higher clock resulution.
(fixed up by Sami Pietikäinen around v3.12)
Signed-off-by: Benedikt Spranger
Signed-off-by: Thomas Gleixner
[bigeasy: update against v
* Masami Hiramatsu wrote:
> (2013/12/20 17:20), Ingo Molnar wrote:
> >
> > * Masami Hiramatsu wrote:
> >
> >>> But a closer look indicates that the insertion of kprobes is
> >>> taking about three (!!) orders of magnitude longer than before, as
> >>> judged by the rate of increase of 'wc -
Hi,
these two patches have been sitting in the -RT tree for quite some time
now. Many thanks to Sami Pietikäinen who fixed them while they got broken
somewhere between v3.2 and v3.8. I ported them to v3.13-rc4 and compile
tested but I have no HW to do more testing.
Sebastian
--
To unsubscribe fr
On Fri, Dec 20, 2013 at 06:19:56PM +0800, Wenliang Fan wrote:
> The checking condition in 'validateFlash2xReadWrite()' is not
> sufficient. A large number invalid would cause an integer overflow and
> pass the condition, which could cause further integer overflows in
> 'Bcmchar.c:bcm_char_ioctl()'.
On 20/12/13 10:20, Chen Gang wrote:
> Hmm... but do you know why we need some 64-bit functions which are
> implemented under "arch/metag/lib/*.S"? can we use
> instead of them? (e.g 64-bit '/').
If you look at linux/math64.h you'll see it only implements division
operations. The other 64 bit oper
Adds a resource managed version of snd_soc_register_codec() which makes
it possible to simplify the remove function as well as the error path
for codec drivers.
Signed-off-by: Xiubo Li
---
include/sound/soc.h| 3 +++
sound/soc/soc-devres.c | 38 ++
2 file
On 12/20/2013 04:41 AM, rui wang wrote:
> On 12/20/13, Prarit Bhargava wrote:
>>
>>
>> On 12/19/2013 01:05 PM, Tony Luck wrote:
>>> On Wed, Dec 18, 2013 at 11:50 AM, Tony Luck wrote:
Looks good to me.
>>>
>>> Though now I've been confused by an offline question about affinity.
>>
>> Heh :)
On Thursday, December 19, 2013 08:22:08 PM H. Peter Anvin wrote:
> On 12/19/2013 08:05 PM, joeyli wrote:
> > Then that means the priority of PNP0B0x is higher then "CMOS RTC Not
> > Present" flag. ACPI spec doesn't have clear definition on this.
>
> According to the Microsoft requirements document
On 12/09/2013 11:51 AM, Michael Ellerman wrote:
> On Wed, 2013-04-12 at 10:32:40 UTC, Anshuman Khandual wrote:
>> This patch enables SW based post processing of BHRB captured branches
>> to be able to meet more user defined branch filtration criteria in perf
>> branch stack sampling framework. Thes
Signed-off-by: Philipp Zabel
---
include/linux/reset.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/linux/reset.h b/include/linux/reset.h
index 6082247..9b32334 100644
--- a/include/linux/reset.h
+++ b/include/linux/reset.h
@@ -11,6 +11,7 @@ int reset_control_deassert(struct reset_
From: Rashika Kheria
This patch marks the function of_reset_simple_xlate() as static in
core.c because it is not used outside this file.
Thus, it also eliminate the following warning in core.c:
drivers/reset/core.c:46:5: warning: no previous prototype for
‘of_reset_simple_xlate’ [-Wmissing-prot
The checking condition in 'validateFlash2xReadWrite()' is not
sufficient. A large number invalid would cause an integer overflow and
pass the condition, which could cause further integer overflows in
'Bcmchar.c:bcm_char_ioctl()'.
Signed-off-by: Wenliang Fan
---
drivers/staging/bcm/nvm.c | 9
On 12/09/2013 11:51 AM, Michael Ellerman wrote:
> On Wed, 2013-04-12 at 10:32:42 UTC, Anshuman Khandual wrote:
>> This patch adds enumeration for all available SW branch filters
>> in powerpc book3s code and also streamlines the look for the
>> SW branch filter entries while trying to figure out wh
On Fri, Dec 20, 2013 at 09:03:05AM +0800, Xiubo Li wrote:
> This patch adds the SAI's edma mux Tx and Rx support.
DTS changes should be merged via arm-soc.
signature.asc
Description: Digital signature
> Subject: Re: [PATCHv4 2/4] ARM: dts: Add Freescale SAI ALSA SoC Digital Audio
> Interface node for VF610.
>
> On Fri, Dec 20, 2013 at 09:03:05AM +0800, Xiubo Li wrote:
> > This patch adds the SAI's edma mux Tx and Rx support.
>
> DTS changes should be merged via arm-soc.
Okey, Got it.
Thanks
1 - 100 of 530 matches
Mail list logo
