Hi Ming,
On Thu, Jun 06, 2013 at 08:01:48PM +0800, Ming Lei wrote:
> module reference doesn't cover direct loading path, so this patch
> simply holds the module in the whole life time of request_firmware()
> to fix the problem.
This does not make sense to me. If request_firmware() is executing
On 26 December 2013 21:55, Viresh Kumar wrote:
> On 26 December 2013 20:59, Frederic Weisbecker wrote:
>> Please post your config, I'll try to at least narrow down the issue
>> to the faulting instruction.
>
> Sure. Please find attached.
Ping!!
--
To unsubscribe from this list: send the line
On 23 December 2013 13:48, Viresh Kumar wrote:
> Wrong time, probably many people on vacation now. But I am working, so
> will continue reporting my problems, in case somebody is around :)
Ping!! (Probably many people would be back from their vacations.)
--
To unsubscribe from this list: send
Use devm_kcalloc instead of kzalloc to free automatically and make
the cleanup paths simpler and the code slightly shorter.
Signed-off-by: Xiubo Li
---
Changed in v2:
- Use devm_kcalloc instead of devm_kzalloc.
Changed in v1:
- Use devm_kzalloc instead of kzalloc.
drivers/pwm/core.c | 4
> > Use devm_kzalloc instead of kzalloc to free automatically and make
> > the cleanup paths simpler and the code slightly shorter.
> []
> > diff --git a/drivers/pwm/core.c b/drivers/pwm/core.c
> []
> > @@ -245,7 +244,9 @@ int pwmchip_add(struct pwm_chip *chip)
> > if (ret < 0)
> >
[...]
Unfortunately not. This commit has a side effect that it in fact
disables the multiqueue macvtap transmission. Since all macvtap queues
will contend on a single qdisc lock.
They will only contend on a single qdisc lock if the lower device has
1 queue.
I think we are talking about
On 01/07/2014 02:36 AM, Darrick J. Wong wrote:
> On Fri, Jan 03, 2014 at 03:03:42PM -0500, Martin K. Petersen wrote:
>>> "Hannes" == Hannes Reinecke writes:
>>
>> Hannes> Personally, I doubt it's a good idea to kill it off, but a
>> Hannes> proper (userland) API for it has been a long time
On Tue, 2014-01-07 at 14:05 +0800, Xiubo Li wrote:
> Use devm_kzalloc instead of kzalloc to free automatically and make
> the cleanup paths simpler and the code slightly shorter.
[]
> diff --git a/drivers/pwm/core.c b/drivers/pwm/core.c
[]
> @@ -245,7 +244,9 @@ int pwmchip_add(struct pwm_chip
On Fri, Jan 03, 2014 at 09:41:33PM -0800, Dmitry Torokhov wrote:
> On Fri, Jan 03, 2014 at 09:03:11PM -0800, Andrey Smirnov wrote:
> > On Fri, Jan 3, 2014 at 8:44 PM, Dmitry Torokhov
> > wrote:
> > > On Fri, Jan 03, 2014 at 08:24:17PM -0800, Andrey Smirnov wrote:
> > >> On Fri, Jan 3, 2014 at
> -Original Message-
> From: David Miller [mailto:da...@davemloft.net]
> Sent: Tuesday, January 07, 2014 1:56 PM
> To: shh@gmail.com
> Cc: jg1@samsung.com; mugunthan...@ti.com; f.faine...@gmail.com;
> net...@vger.kernel.org; linux-kernel@vger.kernel.org; Xie Shaohui-B21989;
>
Use devm_kzalloc instead of kzalloc to free automatically and make
the cleanup paths simpler and the code slightly shorter.
Signed-off-by: Xiubo Li
---
drivers/pwm/core.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/pwm/core.c b/drivers/pwm/core.c
index
Hi Rafael,
> This patch series introduces support for CPU overclocking technique
> called Boost.
>
> It is a follow up of a LAB governor proposal. Boost is a LAB
> component:
> http://thread.gmane.org/gmane.linux.kernel/1484746/match=cpufreq
>
> Boost unifies hardware based solution (e.g. Intel
Could you also fix this Smatch warning?
drivers/misc/genwqe/card_dev.c:658 do_flash_update() warn: maybe return -EFAULT
instead of the bytes remaining?
Also we shouldn't be doing dev_err() on copy_to/from_user() problems.
The user can trigger those and flood dmesg. It is a DoS (annoying).
Hi all,
This tree fails (more than usual) the powerpc allyesconfig build.
Changes since 20140106:
Dropped tree: sh (complex merge conflicts against very old commits)
The powerpc tree still had its build failure.
The net-next tree lost its build failure.
The bluetooth tree gained a conflict
On Tue, Jan 7, 2014 at 11:53 AM, Greg KH wrote:
> On Tue, Jan 07, 2014 at 11:35:50AM +0800, 沈光 wrote:
>> On Tue, Jan 7, 2014 at 10:40 AM, Greg KH wrote:
>> > On Tue, Jan 07, 2014 at 10:33:14AM +0800, 沈光 wrote:
>> >> set hub->change_bits when we plug in a device which causes
>> >> over-current
On 1/6/2014 9:00 PM, Mark Rutland wrote:
> On Mon, Jan 06, 2014 at 12:07:39PM +, Satish Patel wrote:
>> TDA8026 is a SmartCard PHY from NXP.
>>
>> The PHY interfaces with the main processor over the
>> I2C interface and acts as a slave device.
>>
>> The driver also exposes the phy interface
On 01/07/2014 02:00 PM, Stephen Rothwell wrote:
Hi Andrew,
Today's linux-next merge of the akpm-current tree got a conflict in
arch/x86/mm/numa.c between commit f3d815cb854b ("x86/mm/numa: Fix 32-bit
kernel NUMA boot") from the tip tree and commit 1459be89954e ("x86: get
pg_data_t's memory from
On 01/07/2014 01:15 PM, John Fastabend wrote:
> On 01/06/2014 07:10 PM, Jason Wang wrote:
>> On 01/06/2014 08:26 PM, Neil Horman wrote:
>>> On Mon, Jan 06, 2014 at 03:54:21PM +0800, Jason Wang wrote:
On 01/06/2014 03:35 PM, John Fastabend wrote:
> On 01/05/2014 07:21 PM, Jason Wang wrote:
Hi Andrew,
Today's linux-next merge of the akpm-current tree got a conflict in
arch/x86/mm/numa.c between commit f3d815cb854b ("x86/mm/numa: Fix 32-bit
kernel NUMA boot") from the tip tree and commit 1459be89954e ("x86: get
pg_data_t's memory from other node") from the akpm-current tree.
These
Hi RongJun,
On 01/07/2014 01:56 PM, RongJun Ying wrote:
> From: Rongjun Ying
>
> When system on the suspend state, Some SoC can't get gpio interrupt.
> After system resume, need send extcon uevent to userspace.
>
> Signed-off-by: Rongjun Ying
> Reviewed-by: Barry Song
> ---
> -v3:
>
This patch has conflict as following:
You have to implement extcon patch based mainline extcon-next branch.
Applying: extcon: gpio: Add power resume support
error: patch failed: drivers/extcon/extcon-gpio.c:103
error: drivers/extcon/extcon-gpio.c: patch does not apply
Patch failed at 0001 extcon:
On Mon, Jan 06, 2014 at 12:47:07PM -0800, Josh Triplett wrote:
> [CCing build-system folks and others likely to know about potential
> issues.]
>
> Does anyone have any objection to the use of "#pragma once" instead of
> the usual #ifndef-#define-...-#endif include guard? GCC, LLVM/clang,
> and
From: Jason Wang
Date: Tue, 07 Jan 2014 11:17:06 +0800
> On 01/07/2014 04:47 AM, David Miller wrote:
>> From: Jason Wang
>> Date: Mon, 6 Jan 2014 11:21:06 +0800
>>
>>> L2 fowarding offload will bypass the rx handler of real device. This will
>>> make
>>> the packet could not be forwarded to
From:
Date: Tue, 7 Jan 2014 10:14:25 +0800
> -static int phy_attach_direct(struct net_device *dev, struct phy_device
> *phydev,
> +int phy_attach_direct(struct net_device *dev, struct phy_device *phydev,
>u32 flags, phy_interface_t interface)
Since you are changing
On Mon, Jan 06, 2014 at 04:47:38PM -0800, Muthu Kumar wrote:
> OK, after a bit more staring I believe the correct fix is the following.
>
> Fengguang, Please try this one?
Yes, it runs fine now!
Tested-by: Fengguang Wu
Thanks,
Fengguang
>
> In btrfs_end_bio(), we increment
> From: Rongjun Ying
>
> When system on the suspend state, Some SoC can't get gpio interrupt.
> After system resume, need send extcon uevent to userspace.
>
> Signed-off-by: Rongjun Ying
> Reviewed-by: Barry Song
Acked-by: MyungJoo Ham
Thanks!
> ---
> -v3:
> 'check_on_resume' instead of
From: Hayes Wang
Date: Tue, 7 Jan 2014 11:18:22 +0800
> - Replace pr_warn_ratelimited() with net_ratelimit() and netdev_warn().
> - Adjust the algnment of some messages.
> - Remove the peroid.
> - Fix some messages don't have terminating newline.
>
> Signed-off-by: Hayes Wang
I only want
On 01/06/2014 12:58 AM, joeyli wrote:
> 於 二，2013-12-31 於 16:42 -0800，H. Peter Anvin 提到：
>> On 12/19/2013 09:41 PM, joeyli wrote:
What platform do you have that has TAD support? I am wondering how this
was tested.
>>>
>>> It's a testing platform that's only support get/set time
On Mon, Jan 6, 2014 at 10:18 PM, Michal Hocko wrote:
> On Mon 06-01-14 20:45:54, Bob Liu wrote:
> [...]
>> 544 if (PageAnon(page)) {
>> 545 struct anon_vma *page__anon_vma = page_anon_vma(page);
>> 546 /*
>> 547 * Note: swapoff's
Commit-ID: 663b55b9b39fa9c848cca273ca4e12bf29b32c71
Gitweb: http://git.kernel.org/tip/663b55b9b39fa9c848cca273ca4e12bf29b32c71
Author: Paul Gortmaker
AuthorDate: Mon, 6 Jan 2014 19:20:26 -0500
Committer: H. Peter Anvin
CommitDate: Mon, 6 Jan 2014 21:25:18 -0800
x86: Delete
This looks completely broken to me. You do a "kobject_put()" and then
after you've dropped that last use, you wait for the completion of
something that may already have been free'd.
Wtf? Am I missing something?
Linus
On Tue, Jan 7, 2014 at 12:01 PM, Mikulas Patocka wrote:
>
>
>
On 01/06/2014 04:20 PM, Paul Gortmaker wrote:
> None of these files are actually using any __init type directives
> and hence don't need to include . Most are just a
> left over from __devinit and __cpuinit removal, or simply due to
> code getting copied from one driver to the next.
>
>
On Tue, 2014-01-07 at 00:54 +, Zhang, Yang Z wrote:
> Alex Williamson wrote on 2013-12-24:
> > David,
> >
> > Any comments on this patch? Thanks,
> >
>
> Hi Alex,
>
> There do have some IOMMUs will treat SNP bit in the PTE as reserved
> (0) and will cause a reserved field violation fault
On 01/06/2014 07:10 PM, Jason Wang wrote:
On 01/06/2014 08:26 PM, Neil Horman wrote:
On Mon, Jan 06, 2014 at 03:54:21PM +0800, Jason Wang wrote:
On 01/06/2014 03:35 PM, John Fastabend wrote:
On 01/05/2014 07:21 PM, Jason Wang wrote:
L2 fowarding offload will bypass the rx handler of real
On 01/06/2014 07:10 PM, Jason Wang wrote:
On 01/06/2014 08:26 PM, Neil Horman wrote:
On Mon, Jan 06, 2014 at 03:54:21PM +0800, Jason Wang wrote:
On 01/06/2014 03:35 PM, John Fastabend wrote:
On 01/05/2014 07:21 PM, Jason Wang wrote:
L2 fowarding offload will bypass the rx handler of real
Commit-ID: 0262b6690132600c6e77534a639519be3f36f8f5
Gitweb: http://git.kernel.org/tip/0262b6690132600c6e77534a639519be3f36f8f5
Author: Paul Gortmaker
AuthorDate: Mon, 6 Jan 2014 19:20:26 -0500
Committer: H. Peter Anvin
CommitDate: Mon, 6 Jan 2014 21:14:15 -0800
x86: Delete
On 01/06/2014 02:36 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.12.7 release.
There are 144 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 01/06/2014 02:37 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.10.26 release.
There are 129 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 01/06/2014 02:39 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.4.76 release.
There are 43 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
From: Rongjun Ying
When system on the suspend state, Some SoC can't get gpio interrupt.
After system resume, need send extcon uevent to userspace.
Signed-off-by: Rongjun Ying
Reviewed-by: Barry Song
---
-v3:
'check_on_resume' instead of 'load_sleep_irq' as Chanwoo Choi's proposal.
On 01/06/2014 07:50 PM, Rafael J. Wysocki wrote:
On Monday, January 06, 2014 04:47:59 PM Tang Chen wrote:
The comment about return value of acpi_table_parse() is incorrect.
This patch fix it.
Since all callers only check if the function succeeded or not, this
patch simplifies the semantics by
Hi all,
Today's linux-next merge of the xen-tip tree got a conflict in
arch/arm/include/asm/xen/page.h between commit 0a5ccc86507f ("ARM:
7933/1: rename ioremap_cached to ioremap_cache") from the tree and
commit 02bcf053e9c5 ("asm/xen/page.h: remove redundant semicolon") from
the xen-tip tree.
On 01/06/2014 01:33 PM, Josh Boyer wrote:
> On Thu, Jan 2, 2014 at 3:56 PM, H. Peter Anvin wrote:
>> On 01/02/2014 12:39 PM, Vivek Goyal wrote:
>>>
>>> If secureboot is enabled, it enforces module signature verification. I
>>> think similar will happen for kexec too. How would kernel know that on
Hi all,
Today's linux-next merge of the tip tree got a conflict in
drivers/acpi/processor_idle.c between commit 6cb85b2b9df9 ("ACPI /
cpuidle: fix max idle state handling with hotplug CPU support") from the
pm tree and commit 16824255394f ("x86, acpi, idle: Restructure the mwait
idle routines")
Fixed a coding style issue in ke_counter.c
Signed-off-by: Aruna Hewapathirane
---
drivers/staging/comedi/drivers/ke_counter.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/comedi/drivers/ke_counter.c
b/drivers/staging/comedi/drivers/ke_counter.c
On Mon, 6 Jan 2014, Mike Snitzer wrote:
> On Mon, Jan 06 2014 at 1:55pm -0500,
> Mikulas Patocka wrote:
>
> >
> >
> > On Sun, 5 Jan 2014, Greg Kroah-Hartman wrote:
> >
> > > On Sun, Jan 05, 2014 at 05:43:56PM +0100, Bart Van Assche wrote:
> > > > On 01/04/14 19:06, Mikulas Patocka wrote:
Got a few cycles to take another look at this, and tried to address
Miroslav's latest comments. Please let me know if you have further
thoughts!
thanks
-john
The existing timekeeping_adjust logic has always been complicated
to understand. Further, since it was developed prior to NOHZ becoming
On Tue, Jan 07, 2014 at 11:35:50AM +0800, 沈光 wrote:
> On Tue, Jan 7, 2014 at 10:40 AM, Greg KH wrote:
> > On Tue, Jan 07, 2014 at 10:33:14AM +0800, 沈光 wrote:
> >> set hub->change_bits when we plug in a device which causes
> >> over-current condition, so that hub_events() will check it.
> >
> >
Hi James,
Today's linux-next merge of the security tree got a conflict in
drivers/char/tpm/tpm_ppi.c between commits df45c712d1f4 ("ACPI / TPM: fix
memory leak when walking ACPI namespace"), 84b1667dea23 ("ACPI / TPM:
replace open-coded _DSM code with helper functions") and 1569a4c4ceba
("ACPI /
From: Shaohui Xie
Then other generic phy driver such as generic 10g phy driver can join it.
Signed-off-by: Shaohui Xie
---
resend for v4.
drivers/net/phy/phy_device.c | 29 +
1 file changed, 21 insertions(+), 8 deletions(-)
diff --git
On 01/06/2014 08:42 PM, Neil Horman wrote:
> On Mon, Jan 06, 2014 at 11:21:07AM +0800, Jason Wang wrote:
>> Currently, the tx queue were selected implicitly in ndo_dfwd_start_xmit().
>> The
>> will cause several issues:
>>
>> - NETIF_F_LLTX was forced for macvlan device in this case which lead
From: Andy Fleming
10G PHYs don't currently support running the state machine, which
is implicitly setup via of_phy_connect(). Therefore, it is necessary
to implement an OF version of phy_attach(), which does everything
except start the state machine.
Signed-off-by: Andy Fleming
Signed-off-by:
From: Andy Fleming
Very incomplete, but will allow for binding an ethernet controller
to it.
Signed-off-by: Andy Fleming
Signed-off-by: Shaohui Xie
---
resend for v4.
drivers/net/phy/phy_device.c | 80
1 file changed, 80 insertions(+)
diff --git
From: Andy Fleming
phy_attach_direct() may now attach to a generic 10G driver. It can
also be used exactly as phy_connect_direct(), which will be useful
when using of_mdio, as phy_connect (and therefore of_phy_connect)
start the PHY state machine, which is currently irrelevant for 10G
PHYs.
From: Andy Fleming
Signed-off-by: Andy Fleming
Signed-off-by: Shaohui Xie
Acked-by: Florian Fainelli
---
resend for v4.
drivers/of/of_net.c | 1 +
include/linux/phy.h | 1 +
2 files changed, 2 insertions(+)
diff --git a/drivers/of/of_net.c b/drivers/of/of_net.c
index 8f9be2e..a208a45
On 2014/1/6 23:11, Johannes Berg wrote:
> On Thu, 2013-12-26 at 19:40 +0800, Ding Tianhong wrote:
>> Use the possibly more efficient ether_addr_equal
>> to instead of memcmp.
>
> This is a slow-path, I don't think that's really worth it. It kinda
> makes sense, but relies on the struct
From: Andy Fleming
Need an extra parameter to read or write Clause 45 PHYs, so
need a different API with the extra parameter.
Signed-off-by: Andy Fleming
Signed-off-by: Shaohui Xie
---
resend for v4.
include/linux/phy.h | 39 +++
1 file changed, 39
On Tue, Jan 7, 2014 at 10:40 AM, Greg KH wrote:
> On Tue, Jan 07, 2014 at 10:33:14AM +0800, 沈光 wrote:
>> set hub->change_bits when we plug in a device which causes
>> over-current condition, so that hub_events() will check it.
>
> Why?
>
> What does this solve? Is this a bug with existing
On Tuesday, January 07, 2014 11:45 AM, Tanmay Inamdar wrote:
> On Sun, Jan 5, 2014 at 5:47 PM, Jingoo Han wrote:
> > On Monday, December 23, 2013 5:02 PM, Tanmay Inamdar wrote:
> >>
> >> This patch adds the AppliedMicro X-gene SOC PCIe controller driver.
> >> APM X-Gene PCIe controller supports
On Mon, 06 Jan 2014 20:51:09 -0600
Tom Zanussi wrote:
> I'll run the next version through my 'testsuite', which unfortunately is
> still manual (one of the many things on my todo list is automate it)..
I have some basic tests, attached is one. Which failed. Here's the
patch that fixes it:
--
On Mon, 2014-01-06 at 12:52 -0800, Darren Hart wrote:
> On Thu, 2014-01-02 at 07:05 -0800, Davidlohr Bueso wrote:
> > From: Davidlohr Bueso
> >
> > In futex_wake() there is clearly no point in taking the hb->lock if we know
> > beforehand that there are no tasks to be woken. While the hash
Hi Shawn,
On Mon, 6 Jan 2014 14:44:08 +0800 Shawn Guo wrote:
>
> Okay, I missed your point. The resolution needs the additional changes
> as below.
Thanks, I applied the following as a merge fix patch today and will carry
it as necessary.
From: Stephen Rothwell
Date: Tue, 7 Jan 2014 14:20:53
On Mon, 06 Jan 2014 20:51:09 -0600
Tom Zanussi wrote:
> > Hmm, OK, I think you may have convinced me. I'll swap the return values.
> >
>
> Sounds great, thanks!
New patch.
-- Steve
tracing: Consolidate event trigger code
The event trigger code that checks for callback triggers before and
On Tue, 7 Jan 2014 12:00:12 +0900
Namhyung Kim wrote:
> Now all of its users were gone. :)
>
Die die!
;-)
-- Steve
--
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
- Replace pr_warn_ratelimited() with net_ratelimit() and netdev_warn().
- Adjust the algnment of some messages.
- Remove the peroid.
- Fix some messages don't have terminating newline.
Signed-off-by: Hayes Wang
---
drivers/net/usb/r8152.c | 23 +--
1 file changed, 13
On 01/07/2014 04:47 AM, David Miller wrote:
> From: Jason Wang
> Date: Mon, 6 Jan 2014 11:21:06 +0800
>
>> L2 fowarding offload will bypass the rx handler of real device. This will
>> make
>> the packet could not be forwarded to macvtap device. Another problem is the
>> dev_hard_start_xmit()
On 01/06/2014 08:26 PM, Neil Horman wrote:
> On Mon, Jan 06, 2014 at 03:54:21PM +0800, Jason Wang wrote:
>> On 01/06/2014 03:35 PM, John Fastabend wrote:
>>> On 01/05/2014 07:21 PM, Jason Wang wrote:
L2 fowarding offload will bypass the rx handler of real device. This
will make
the
This driver adds support for elan i2c/smbus touchpad found on some laptops PC
Signed-off-by: Duson Lin
---
drivers/input/mouse/Kconfig| 10 +
drivers/input/mouse/Makefile |1 +
drivers/input/mouse/elan_i2c.c | 890
3 files changed, 901
On Fri, Jan 3, 2014 at 1:49 AM, Arnd Bergmann wrote:
> On Monday 23 December 2013, Tanmay Inamdar wrote:
>> This patch adds the bindings for X-Gene PCIe driver. The driver resides
>> under 'drivers/pci/host/pcie-xgene.c' file.
>>
>> Signed-off-by: Tanmay Inamdar
>> ---
>>
On Tue, 2014-01-07 at 10:55 +0800, Linus Torvalds wrote:
> On Mon, Jan 6, 2014 at 9:38 AM, Davidlohr Bueso wrote:
> > {
> > int lock_taken, ret, force_take = 0;
> > - u32 uval, newval, curval, vpid = task_pid_vnr(task);
> > + u32 uval, newval, uninitialized_var(curval), vpid
They're copied from the perf code and will be used to print error
message during trace_seq_printf() and friends.
Suggested-by: Jiri Olsa
Signed-off-by: Namhyung Kim
---
tools/lib/traceevent/event-utils.h | 22 ++
1 file changed, 22 insertions(+)
diff --git
Now all of its users were gone. :)
Signed-off-by: Namhyung Kim
---
tools/lib/traceevent/event-utils.h | 4
tools/lib/traceevent/parse-utils.c | 44 --
2 files changed, 48 deletions(-)
diff --git a/tools/lib/traceevent/event-utils.h
Hello,
I've added WARN_ONCE in TRACE_SEQ_CHECK() as Jiri said. Other patches
are same as the privous version.
You can also get this on my 'libtraceevent/die-removal-v5' branch in my tree
git://git.kernel.org/pub/scm/linux/kernel/git/namhyung/linux-perf.git
Thanks,
Namhyung
Namhyung Kim
Use plain malloc() and check its return value.
Signed-off-by: Namhyung Kim
---
tools/lib/traceevent/trace-seq.c | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/tools/lib/traceevent/trace-seq.c b/tools/lib/traceevent/trace-seq.c
index b139d55a6bf9..e858bfd3b104 100644
If realloc() fails, it'll leak the buffer. Also increate buffer size
only if the allocation succeeded.
Signed-off-by: Namhyung Kim
---
tools/lib/traceevent/trace-seq.c | 12 +---
1 file changed, 9 insertions(+), 3 deletions(-)
diff --git a/tools/lib/traceevent/trace-seq.c
The trace_seq->state is for tracking errors during the use of
trace_seq APIs and getting rid of die() in it.
Signed-off-by: Namhyung Kim
---
tools/lib/traceevent/event-parse.h | 7 +++
tools/lib/traceevent/trace-seq.c | 42 ++
2 files changed, 45
This is a proof of concept interface for replacing the contentious
FS_IOC_[GS]ETFLAGS interface with one that presents itself as the
xattr 'system.iflags'. Instead of using integer inode flags, this
interface uses a comma-separated string of words, such as
"extents,immutable" to describe the
When CONFIG_PCI and CONFIG_PM are not selected, xhci.c gets this
warning:
drivers/usb/host/xhci.c:409:13: warning: ‘xhci_msix_sync_irqs’ defined
but not used [-Wunused-function]
It happens due to lack of __maybe_unused flag on xhci_msix_sync_irqs()
function in case of !CONFIG_PCI.
Signed-off-by:
On Thu, Jan 2, 2014 at 4:52 PM, Jason Gunthorpe
wrote:
> On Thu, Jan 02, 2014 at 01:56:51PM -0800, Tanmay Inamdar wrote:
>> On Mon, Dec 23, 2013 at 9:46 AM, Jason Gunthorpe
>> wrote:
>> > On Mon, Dec 23, 2013 at 01:32:03PM +0530, Tanmay Inamdar wrote:
>> >> This patch adds the device tree nodes
On Mon, Jan 6, 2014 at 9:38 AM, Davidlohr Bueso wrote:
> {
> int lock_taken, ret, force_take = 0;
> - u32 uval, newval, curval, vpid = task_pid_vnr(task);
> + u32 uval, newval, uninitialized_var(curval), vpid =
> task_pid_vnr(task);
Do you have some broken compiler? I
On 12/27/2013 02:40 PM, rjying wrote:
> From: Rongjun Ying
>
> When system on the suspend state, Some SoC can't get gpio interrupt.
> After system resume, need send extcon uevent to userspace.
>
> Signed-off-by: Rongjun Ying
> ---
> -v2: Add lost_sleep_irq flags.
>
>
On Mon, Jan 06, 2014 at 04:47:38PM -0800, Muthu Kumar wrote:
> OK, after a bit more staring I believe the correct fix is the following.
This code still confuses me but I think you're correct, the fix certainly
matches the evidence we have.
> Fengguang, Please try this one?
>
> Regards,
> Muthu
>
> > > + enum event_trigger_type tt = ETT_NONE;
> > > +
> > > + if (__event_trigger_test_discard(file, buffer, event, entry, ))
> > > + trace_buffer_unlock_commit(buffer, event, irq_flags, pc);
> >
> > The logic is correct overall, but the way it reads is the opposite of
> > what it
Hi Steve and Jiri,
2014-01-06 PM 11:45, Steven Rostedt wrote:
On Mon, 6 Jan 2014 15:38:28 +0100
Jiri Olsa wrote:
I just thought that it's not so important to print message so keeps the
error internally until it gets printed. But I can be wrong as usual...
I think that if she manages to
On Mon, 6 Jan 2014, Dave Hansen wrote:
> This patch moves stat(s, ALLOC_SLOWPATH) to be called from the
> same place that __slab_alloc() is. This makes it much less
> likely that ALLOC_SLOWPATH will get botched again in the
> spaghetti-code inside __slab_alloc().
Acked-by: Christoph Lameter
Hi, Eduardo
Will you consider my comments :)
Thanks.
Wei.
On 12/31/2013 06:17 PM, Wei Ni wrote:
> On 11/13/2013 03:46 AM, Eduardo Valentin wrote:
>> This patch introduces a device tree bindings for
>> describing the hardware thermal behavior and limits.
>> Also a parser to read and interpret the
On Sun, Jan 5, 2014 at 5:47 PM, Jingoo Han wrote:
> On Monday, December 23, 2013 5:02 PM, Tanmay Inamdar wrote:
>>
>> This patch adds the AppliedMicro X-gene SOC PCIe controller driver.
>> APM X-Gene PCIe controller supports maximum upto 8 lanes and
>> GEN3 speed. X-Gene has maximum 5 PCIe ports
On 01/06/2014 10:54 PM, Eduardo Valentin wrote:
> * PGP Signed by an unknown key
>
> On 06-01-2014 09:51, Mark Rutland wrote:
>> On Thu, Jan 02, 2014 at 05:50:06PM +, Matthew Longnecker wrote:
>>>
I think the platform driver may set governor for the thermal zone,
so how about to add
Thanks for your comments. Please see some inline replies.
On Fri, Jan 3, 2014 at 4:07 AM, Arnd Bergmann wrote:
> On Monday 23 December 2013, Tanmay Inamdar wrote:
>> This patch adds the AppliedMicro X-gene SOC PCIe controller driver.
>> APM X-Gene PCIe controller supports maximum upto 8 lanes
On Wed, 2013-12-18 at 15:53 +0900, Joonsoo Kim wrote:
> There is a race condition if we map a same file on different processes.
> Region tracking is protected by mmap_sem and hugetlb_instantiation_mutex.
> When we do mmap, we don't grab a hugetlb_instantiation_mutex, but,
> grab a mmap_sem. This
On Tue, Jan 07, 2014 at 10:33:14AM +0800, 沈光 wrote:
> set hub->change_bits when we plug in a device which causes
> over-current condition, so that hub_events() will check it.
Why?
What does this solve? Is this a bug with existing devices that needs to
be backported to older kernels?
thanks,
On Wed, 2013-12-18 at 15:53 +0900, Joonsoo Kim wrote:
> To change a protection method for region tracking to find grained one,
> we pass the resv_map, instead of list_head, to region manipulation
> functions. This doesn't introduce any functional change, and it is just
> for preparing a next step.
On Wed, 2013-12-18 at 15:53 +0900, Joonsoo Kim wrote:
> Currently, to track a reserved and allocated region, we use two different
> ways for MAP_SHARED and MAP_PRIVATE. For MAP_SHARED, we use
> address_mapping's private_list and, for MAP_PRIVATE, we use a resv_map.
> Now, we are preparing to
On Tue, 2014-01-07 at 10:57 +0900, Joonsoo Kim wrote:
> On Mon, Jan 06, 2014 at 04:19:05AM -0800, Davidlohr Bueso wrote:
> > On Mon, 2014-01-06 at 09:19 +0900, Joonsoo Kim wrote:
> > > On Fri, Jan 03, 2014 at 11:55:45AM -0800, Davidlohr Bueso wrote:
> > > > Hi Joonsoo,
> > > >
> > > > Sorry about
This patch uses the generic early_ioremap code to implement
early_ioremap for ARM. The ARM-specific bits come mostly from
an earlier patch from Leif Lindholm
here:
https://lkml.org/lkml/2013/10/3/279
Signed-off-by: Mark Salter
Tested-by: Leif Lindholm
CC:
This patch creates a generic implementation of early_ioremap() support
based on the existing x86 implementation. early_ioremp() is useful for
early boot code which needs to temporarily map I/O or memory regions
before normal mapping functions such as ioremap() are available.
There is one
Add support for early IO or memory mappings which are needed
before the normal ioremap() is usable. This also adds fixmap
support for permanent fixed mappings such as that used by the
earlyprintk device register region.
Signed-off-by: Mark Salter
CC: linux-arm-ker...@lists.infradead.org
CC:
This patch series takes the common bits from the x86 early ioremap
implementation and creates a generic implementation which may be used
by other architectures. The early ioremap interfaces are intended for
situations where boot code needs to make temporary virtual mappings
before the normal
Presently, paging_init() calls init_mem_pgprot() to initialize pgprot
values used by macros such as PAGE_KERNEL, PAGE_KERNEL_EXEC, etc. The
new fixmap and early_ioremap support also needs to use these macros
before paging_init() is called. This patch moves the init_mem_pgprot()
call out of
Move x86 over to the generic early ioremap implementation. The
generic implementation is functionally the same except that the
early_memremap() function returns a normal pointer instead of an
__iomem pointer. This is in line with sparse warning cleanups in
this patch series:
1 - 100 of 2140 matches
Mail list logo
