The perf-completion.sh uses a predefined string '--help --version
--exec-path --html-path --paginate --no-pager --perf-dir --work-tree
--debugfs-dir' for the bash completion of 'perf --*', which has two
problems:
Problem 1: If the options of perf are changed (see handle_options() in
perf.c), the
Do not need print_events_type or __print_events_type for listing hw/sw
events, let print_symbol_events do its job instead. Moreover,
print_symbol_events can also handle event_glob and name_only.
Signed-off-by: Yunlong Song
---
tools/perf/builtin-list.c | 6 ++--
tools/perf/util/parse-event
Hi,
Found some functions to improve and bugs to fix in perf.
This patchset is based on:
https://git.kernel.org/cgit/linux/kernel/git/acme/linux.git/ perf/core
For [PATCH v3 4/7] and [PATCH v3 5/7], I have checked that these
patches do not break shell autocompletion. Besides, for [PAT
On Fri, Feb 27, 2015 at 11:28:50AM +0800, Wang Nan wrote:
> As early_trap_init() doesn't use IST, replace set_intr_gate_ist(..., 0)
> and set_system_intr_gate_ist(..., 0) with their standard counterparts.
>
> set_intr_gate() requires a trace_debug symbol which we don't have and
> won't use. Use a
When build with ARCH=x86_64/i386, perf failed to compile with following
error:
tests/builtin-test.o:(.data+0x158): undefined reference to
`test__perf_time_to_tsc'
collect2: error: ld returned 1 exit status
Makefile.perf:632: recipe for target 'perf' failed
...
Which is caused commit c6e5e9fbc3ea
On Fri, Feb 27, 2015 at 05:46:55AM +, Pranith Kumar wrote:
> In cmpxchg(), we do a load exclusive on an address and upon a comparison fail,
> we skip the store exclusive instruction. This can result in the exclusive bit
> still set. If there was a store exclusive after this to the same address,
> -Original Message-
> From: Andrew Morton [mailto:a...@linux-foundation.org]
> Sent: Tuesday, February 24, 2015 5:02 AM
> To: Chen, Hanxiao/陈 晗霄
> Cc: Eric W. Biederman; contain...@lists.linux-foundation.org;
> linux-kernel@vger.kernel.org; linux-...@vger.kernel.org; Serge Hallyn;
> Jon
On Thu, Feb 26, 2015 at 11:41:44AM -0800, Paul E. McKenney wrote:
> > As per the above argument; without doing the whole READ/WRITE_ONCE for
> > the rb tree primitives, I think we're fine. We don't actually need the
> > read_barrier_depends() I think.
> >
> > I think this because raw_read_seqcount
[CC'ed Preeti]
On Thu, Feb 26, 2015 at 11:37:54PM +, Rafael J. Wysocki wrote:
> Me versions of the two $subject patches follow.
Thank you. I am testing them and I have run into the following issue.
Starting with:
3810631 ("PM / sleep: Re-implement suspend-to-idle handling")
the suspend-to-
ping..
在 2015/2/15 10:33, He Kuang 写道:
When perf.data file be abtained by using 'perf record -b', perf report
should use branch stack mode to generate output. But this function is
broken by improper comparison between boolean and constant -1.
before this patch:
$perf report -b -i perf.data
Sampl
Thanks for the patch.
On 27/02/15 00:00, Stephen Boyd wrote:
The RPM regulators are not individual devices. Creating platform
devices for each regulator bloats the kernel's runtime memory
footprint by ~12k. Let's rework this driver to be a single
platform device for all the RPM regulators. This
cp_payload is introduced for sit bitmap to support large volume, and it is
just after the block of f2fs_checkpoint + nat bitmap, so the first segment
should include F2FS_CP_PACKS + NR_CURSEG_TYPE + cp_payload + orphan blocks.
However, current max orphan inodes calculation don't consider cp_payload,
On Friday 27 February 2015 14:54:17 Vignesh R wrote:
> +- compatible : should be "ti,omap3-1w" or "ti,am43xx-hdq"
>
Do not use wildcards in the compatible string, use real part numbers
if you don't know the actual name of the device.
Arnd
--
To unsubscribe from this list: send the line "
On Thu, Feb 05, 2015 at 10:29:35AM +, Lad Prabhakar wrote:
> From: "Lad, Prabhakar"
>
> this patch fixes following sparse warning:
>
> sha1_mb_mgr_init_avx2.c:59:31: warning: constant 0xF76543210 is so big it is
> long
>
> Signed-off-by: Lad, Prabhakar
Applied.
--
Email: Herbert Xu
Hom
On Mon, Feb 16, 2015 at 09:13:36PM +0100, Oleg Nesterov wrote:
> diff --git a/kernel/futex.c b/kernel/futex.c
> index b101381..c1104a8 100644
> +++ b/kernel/futex.c
> @@ -716,11 +716,13 @@ void exit_pi_state_list(struct task_struct *curr)
>
> if (!futex_cmpxchg_enabled)
> ret
On Thu, Feb 05, 2015 at 04:10:58PM +0100, Stephan Mueller wrote:
> Am Donnerstag, 29. Januar 2015, 21:24:45 schrieb Stephan Mueller:
>
> Hi Herbert,
>
> > This patch adds the AEAD support for AF_ALG.
> >
> > The implementation is based on algif_skcipher, but contains heavy
> > modifications to s
Some of the kvm_hv exits are due to hcalls. So, this patch adds necessary
support to display the number of hcalls grouped according to their type
(H_IPI, H_CONFER, etc) with "perf kvm stat report --event=syscall".
The patch defines the reasons in "kvm_trace_symbol_hcall". It adds
kvm_hv:kvm_hcall_
Hi Chao,
On Fri, Feb 27, 2015 at 05:39:39PM +0800, Chao Yu wrote:
>Hi Wanpeng,
>
>> -Original Message-
>> From: Wanpeng Li [mailto:wanpeng...@linux.intel.com]
>> Sent: Friday, February 27, 2015 3:05 PM
>> To: Jaegeuk Kim
>> Cc: Wanpeng Li; linux-kernel@vger.kernel.org;
>> linux-f2fs-de...@
From: Srikar Dronamraju
perf kvm stat record/report isn't supported on powerpc.
This patch enables perf to record kvm events (kvm_hv:kvm_guest_entry and exit)
and to display the stats related to the events.
When "perf kvm stat record -a" is invoked, the kvm_hv related tracepoints
kvm_hv:kvm_guest
perf kvm stat record/report which can be used to analyze KVM related statistics
isn't enabled on powerpc. This patchset enables "perf kvm stat" on powerpc.
The first patch enables perf kvm stat record and report to report kvm exits.
"record" enables recording of the tracepoints: kvm_hv:kvm_guest_e
On Fri, Feb 27, 2015 at 10:27 AM, DaeSeok Youn wrote:
> Hi,
>
> I think this patch was already queued. Can I send this patch again
> after update changelog?
One thing that is much more important, how did you test this patch? Did you?
--
Thanks,
//richard
--
To unsubscribe from this list: send t
Hi Wanpeng,
> -Original Message-
> From: Wanpeng Li [mailto:wanpeng...@linux.intel.com]
> Sent: Friday, February 27, 2015 3:05 PM
> To: Jaegeuk Kim
> Cc: Wanpeng Li; linux-kernel@vger.kernel.org;
> linux-f2fs-de...@lists.sourceforge.net
> Subject: [f2fs-dev] [PATCH] f2fs: fix max orphan i
The minus operator has higher precedence than ?:
Add parentheses around ?: fix this.
---
tools/perf/util/probe-event.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/perf/util/probe-event.c b/tools/perf/util/probe-event.c
index 919937e..bed8d0f 100644
--- a/tools/perf/ut
2015-02-27 16:06 GMT+09:00 Joseph Qi :
> We can only free conn->cc_private if error occurs. Otherwise it will
> trigger a bug in o2cb_cluster_disconnect since conn->cc_private has
> already been freed.
> So please drop this patch, thanks.
Yes. right..
Sorry for noise.
Thanks.
Daeseok Youn.
>
> On
On Wed, Feb 25, 2015 at 11:38:07AM -0500, r...@redhat.com wrote:
> From: Rik van Riel
>
> Ensure that cpus specified with the isolcpus= boot commandline
> option stay outside of the load balancing in the kernel scheduler.
>
> Operations like load balancing can introduce unwanted latencies,
> whi
Hi Chao,
On Thu, Feb 26, 2015 at 09:33:55AM +0800, Chao Yu wrote:
>Hi Wanpeng,
>
>> -Original Message-
>> From: Wanpeng Li [mailto:wanpeng...@linux.intel.com]
>> Sent: Thursday, February 26, 2015 7:57 AM
>> To: Jaegeuk Kim
>> Cc: Wanpeng Li; linux-kernel@vger.kernel.org;
>> linux-f2fs-de..
Hi,
I think this patch was already queued. Can I send this patch again
after update changelog?
Thanks.
Regards,
Daeseok Youn
2015-02-27 6:33 GMT+09:00 Andrew Morton :
> On Mon, 23 Feb 2015 19:38:10 +0900 Daeseok Youn
> wrote:
>
>> Use 'retval' instead of 'status'.
>>
>
> The patch does a lot
This patches makes following changes to omap_hdq driver
- Enable 1-wire mode.
- Implement w1_triplet callback to facilitate search ROM
procedure and auto detection of 1-wire slaves.
- Proper enabling and disabling of interrupt.
- Cleanups (formatting and return value checks).
HDQ mode remai
From: "Poddar, Sourav"
This patch adds hwmod data for hdq/1w driver on AM43xx.
Signed-off-by: Sourav Poddar
[vigne...@ti.com: Ported patch to v4.0-rc1]
Signed-off-by: Vignesh R
---
arch/arm/mach-omap2/omap_hwmod_43xx_data.c | 36 ++
arch/arm/mach-omap2/prcm43xx.h
Cc Rongrong,
On Fri, Feb 27, 2015 at 04:56:06PM +0800, Wincy Van wrote:
>On Sun, Feb 15, 2015 at 2:27 PM, Yong Wang wrote:
>>
>> Wincy, our QA found regressions with this patch that 64bit L2 linux guest
>> fails to boot up when running nested kvm on kvm.
>>
>> Environment:
>>
>> Host
Hi Alex,
On 26/02/15 20:04, Alex Smith wrote:
> Hi Zubair,
>
> On 26 February 2015 at 12:43, Zubair Lutfullah Kakakhel
> wrote:
>> From: Alex Smith
>>
>> Add device tree bindings for the DMA controller on JZ4780 SoCs, used by
>> the dma-jz4780 driver.
>>
>> Signed-off-by: Alex Smith
>> Signed-
Hi,
This patch series adds support for HDQ-1W interface on AM43XX.
The first patch adds hwmod entries for HDQ-1W on AM43xx.
The existing omap_hdq driver does not support 1-wire operations.
The second patch enables 1-wire support in the omap_hdq driver. Support
to Search ROM addresses and automati
On Thursday 26 February 2015 14:26:02 Scott Branden wrote:
> On 15-02-26 12:15 PM, Arnd Bergmann wrote:
> >> On 15-02-25 11:17 AM, Arnd Bergmann wrote:
> >>> On Wednesday 25 February 2015 10:16:24 Scott Branden wrote:
> >> This code was following examples of other open source drivers - bcm2835
> >>
Please ignore this one which w/o patch description.
On Fri, Feb 27, 2015 at 04:49:37PM +0800, Wanpeng Li wrote:
>Signed-off-by: Wanpeng Li
>---
> fs/f2fs/segment.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
>diff --git a/fs/f2fs/segment.c b/fs/f2fs/segment.c
>index daee4ab..e7b
Don't need to collect dirty sit entries and flush sit journal to sit
entries when there's no dirty sit entries. This patch check dirty_sentries
earlier just like flush_nat_entries.
Signed-off-by: Wanpeng Li
---
fs/f2fs/segment.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
d
On 02/27/15 08:53, Fu, Zhonghui wrote:
On 2015/2/16 17:35, Arend van Spriel wrote:
On 02/16/15 08:34, Fu, Zhonghui wrote:
On 2015/2/15 22:54, Kalle Valo wrote:
Arend van Spriel writes:
On 02/15/15 04:27, Pat Erley wrote:
On 02/14/2015 08:40 PM, Fu, Zhonghui wrote:
Any comments to this
On Thu, Feb 26, 2015 at 11:26:35AM -0500, Steven Rostedt wrote:
> Index: linux-rt.git/kernel/sched/rt.c
> ===
> --- linux-rt.git.orig/kernel/sched/rt.c 2015-02-26 10:55:26.107945935
> -0500
> +++ linux-rt.git/kernel/sched/rt.c
Signed-off-by: Wanpeng Li
---
fs/f2fs/segment.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/fs/f2fs/segment.c b/fs/f2fs/segment.c
index daee4ab..e7b83b6 100644
--- a/fs/f2fs/segment.c
+++ b/fs/f2fs/segment.c
@@ -1730,6 +1730,9 @@ void flush_sit_entries(struct f2fs_sb
On Fri, Feb 27, 2015 at 09:58:38AM +0100, Oliver Neukum wrote:
> On Fri, 2015-02-27 at 15:42 +0900, gyun...@gmail.com wrote:
> > +static ssize_t sky81452_bl_store_enable(struct device *dev,
> > + struct device_attribute *attr, const char *buf, size_t
> > count)
> > +{
> > + stru
Use timer API functions setup_timer and mod_timer instead
of structure assignments as they are standard way to set
the timer and to update the expire field of an active timer
respectively.
This is done using Coccinelle and semantic patch used for
this is as follows:
//
@@
expression x,y,z,a,b;
@
On Fri, 2015-02-27 at 15:42 +0900, gyun...@gmail.com wrote:
> +static ssize_t sky81452_bl_store_enable(struct device *dev,
> + struct device_attribute *attr, const char *buf, size_t
> count)
> +{
> + struct regmap *regmap = bl_get_data(to_backlight_device(dev));
> + unsign
On 15/2/25 10:07 PM, Arnd Bergmann wrote:
> On Wednesday 25 February 2015 08:33:16 Ezequiel Garcia wrote:
>>
>> /me is more confused now
>>
>> In arch/nios2/include/asm/ucontext.h
>>
>> struct ucontext {
>> unsigned long uc_flags;
>> struct ucontext *uc_link;
>> stack_t
On Sun, Feb 15, 2015 at 2:27 PM, Yong Wang wrote:
>
> Wincy, our QA found regressions with this patch that 64bit L2 linux guest
> fails to boot up when running nested kvm on kvm.
>
> Environment:
>
> Host OS (ia32/ia32e/IA64):ia32e
> Guest OS (ia32/ia32e/IA64):ia32e
> Guest OS Type (L
On 27 February 2015 at 03:20, Timur Tabi wrote:
> On 02/25/2015 02:39 AM, Hanjun Guo wrote:
>>
>> Changes since v8:
>
>
> I'm still debugging it, but v9 on the 4.0-rc1 kernel crashes after calling
> the UEFI boot time services exit function. That is, this line:
>
> status = sys_table->boottime->e
On 02/26/2015 11:01 AM, Preeti U Murthy wrote:
> On 02/23/2015 11:03 PM, Nicolas Pitre wrote:
>> On Mon, 23 Feb 2015, Nicolas Pitre wrote:
>>
>>> On Mon, 23 Feb 2015, Peter Zijlstra wrote:
>>>
The reported function that fails: bL_switcher_restore_cpus() is called
in the error paths of the
Use timer API functions setup_timer and mod_timer instead
of structure assignments as they are standard way to set
the timer and to update the expire field of an active timer
respectively.
This is done using Coccinelle and semantic patch used for
this is as follows:
//
@@
expression x,y,z,a,b;
@
w1_slave_show unlocks the bus while waiting for the sensor
to convert the temperature. If the sensor gets disconnected
during that time, sl->family_data could get NULL.
Note: the w1_slave pointer inside w1_slave_show is protected by
sysfs-mutex
---
drivers/w1/slaves/w1_therm.c | 6 ++
1 file c
Hi Ingi,
On 02/27/2015 02:01 AM, Ingi Kim wrote:
This patch supports KTD2692 flash LED driver
Ingi Kim (3):
of: Add vendor prefix for Kinetic technologies
leds: ktd2692: add device tree bindings for ktd2692
leds: Add ktd2692 flash LED driver
.../devicetree/bindings/leds/leds-ktd2692
On Fri, Feb 27, 2015 at 12:37:54AM +0100, Rafael J. Wysocki wrote:
> Me versions of the two $subject patches follow.
Acked-by: Peter Zijlstra (Intel)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo inf
On Fri, Feb 27, 2015 at 12:07:55AM +0100, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> It currently is required that all users of NO_SUSPEND interrupt
> lines pass the IRQF_NO_SUSPEND flag when requesting the IRQ or the
> WARN_ON_ONCE() in irq_pm_install_action() will trigger. That is
Use timer API functions setup_timer and mod_timer instead
of structure assignments as they are standard way to set
the timer and to update the expire field of an active timer
respectively.
This is done using Coccinelle and semantic patch used for
this is as follows:
//
@@
expression x,y,z,a,b;
@
Hi Timur,
On 2015年02月27日 11:20, Timur Tabi wrote:
On 02/25/2015 02:39 AM, Hanjun Guo wrote:
Changes since v8:
I'm still debugging it, but v9 on the 4.0-rc1 kernel crashes after
calling the UEFI boot time services exit function. That is, this line:
status = sys_table->boottime->exit_boot_ser
Use timer API functions setup_timer and mod_timer instead
of structure assignments as they are standard way to set
the timer and to update the expire field of an active timer
respectively.
This is done using Coccinelle and semantic patch used for
this is as follows:
//
@@
expression x,y,z,a,b;
@
Hi,
The patchset fixes invalid memory accesses in certain race scenarios by
moving ownership of struct power_supply to the core. All drivers are
modified.
TLDR for driver and subsystem maintainers
=
Two patches of patchset change power_supply_register() f
Allow drivers to store private data inside power_supply structure for
later usage in power supply operations.
Usage of driver private data is necessary to access driver's state
container object from power supply calls (like get_property()) if struct
'power_supply' is a stored there as a pointer, f
Add new structure 'power_supply_config' for holding run-time
initialization data like of_node, supplies and private driver data.
The power_supply_register() function is changed so all power supply
drivers need updating.
When registering the power supply this new 'power_supply_config' should be
us
(2015/02/27 15:38), David Long wrote:
> On 02/18/15 09:59, Masami Hiramatsu wrote:
>> Hi,
>>
>> (2015/02/18 8:11), David Long wrote:
>>> From: Sandeepa Prabhu
>>>
>>> Add support for basic kernel probes(kprobes) and jump probes
>>> (jprobes) for ARM64.
>>>
>>> Kprobes will utilize software breakpo
Add simple wrappers for accessing power supply's function attributes:
- get_property -> power_supply_get_property
- set_property -> power_supply_set_property
- property_is_writeable -> power_supply_property_is_writeable
- external_power_changed -> power_supply_external_power_changed
This API a
Replace direct calls to power supply function attributes with wrappers.
Wrappers provide safe access in case of unregistering the power
supply (e.g. by removing the driver). Replace:
- get_property -> power_supply_get_property
Signed-off-by: Krzysztof Kozlowski
Acked-by: Jonghwa Lee
Acked-by: P
Replace direct calls to power supply function attributes with wrappers.
Wrappers provide safe access in case of unregistering the power
supply (e.g. by removing the driver). Replace:
- get_property -> power_supply_get_property
Signed-off-by: Krzysztof Kozlowski
Acked-by: Jonghwa Lee
Acked-by: P
Replace direct calls to power supply function attributes with wrappers.
Wrappers provide safe access in case of unregistering the power
supply (e.g. by removing the driver). Replace:
- get_property -> power_supply_get_property
Signed-off-by: Krzysztof Kozlowski
Acked-by: Jonghwa Lee
Acked-by: P
Am 26.02.2015 um 23:16 schrieb Yannick Guerrini:
> Change 'architecuture' to 'architecture'
>
> Signed-off-by: Yannick Guerrini
Thanks, applied.
> ---
> arch/s390/kvm/gaccess.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/s390/kvm/gaccess.c b/arch/s390/kvm/ga
Replace direct calls to power supply function attributes with wrappers.
Wrappers provide safe access in case of unregistering the power
supply (e.g. by removing the driver). Replace:
- get_property -> power_supply_get_property
- set_property -> power_supply_set_property
- property_is_writeable -
Replace direct calls to power supply function attributes with wrappers.
Wrappers provide safe access in case of unregistering the power
supply (e.g. by removing the driver). Replace:
- get_property -> power_supply_get_property
Signed-off-by: Krzysztof Kozlowski
Acked-by: Jonghwa Lee
Acked-by: P
Replace direct calls to power supply function attributes with wrappers.
Wrappers provide safe access in case of unregistering the power
supply (e.g. by removing the driver). Replace:
- get_property -> power_supply_get_property
Signed-off-by: Krzysztof Kozlowski
Acked-by: Jonghwa Lee
Acked-by: P
Increment the power_supply.use_cnt usage counter on:
- power_supply_get_by_phandle()
- power_supply_get_by_name()
and decrement it on power_supply_put() call.
This helps tracking of valid usage of power supply instance by
consumers. The usage counter itself also allows safe calling of
power_supp
Replace direct usage of put_device() with new API: power_supply_put().
Signed-off-by: Krzysztof Kozlowski
Acked-by: Pavel Machek
Reviewed-by: Bartlomiej Zolnierkiewicz
Reviewed-by: Sebastian Reichel
---
arch/x86/platform/olpc/olpc-xo1-sci.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletio
Replace direct calls to power supply function attributes with wrappers.
Wrappers provide safe access in case of unregistering the power
supply (e.g. by removing the driver). Replace:
- get_property -> power_supply_get_property
- set_property -> power_supply_set_property
Signed-off-by: Krzysztof
Use power_supply_put() to decrement the power supply's device reference
counter.
Signed-off-by: Krzysztof Kozlowski
Acked-by: Pavel Machek
Reviewed-by: Bartlomiej Zolnierkiewicz
Reviewed-by: Sebastian Reichel
---
drivers/power/charger-manager.c | 70 +++--
Use power_supply_put() to decrement the power supply's device reference
counter (increased by power_supply_get_by_name() or
power_supply_get_by_phandle()).
Signed-off-by: Krzysztof Kozlowski
Acked-by: Pavel Machek
Reviewed-by: Bartlomiej Zolnierkiewicz
Reviewed-by: Sebastian Reichel
---
drive
Use power_supply_put() to decrement the power supply's device reference
counter.
Signed-off-by: Krzysztof Kozlowski
Acked-by: Pavel Machek
Reviewed-by: Bartlomiej Zolnierkiewicz
Reviewed-by: Sebastian Reichel
---
drivers/power/88pm860x_charger.c | 11 +--
1 file changed, 9 insertions(
On Thu 26-02-15 14:49:08, Andrew Morton wrote:
> On Mon, 23 Feb 2015 21:17:01 +0100 Michal Hocko wrote:
>
> > ping on this one? Should I just resend (your way Andrew)? Or are there
> > any objections to the patch as is.
>
> Were Eric's concerns all addressed?
I hope so. I didn't touch pid names
Use power_supply_put() to decrement the power supply's device reference
counter.
Signed-off-by: Krzysztof Kozlowski
Acked-by: Pavel Machek
Acked-by: Linus Walleij
Acked-by: Lee Jones
Reviewed-by: Bartlomiej Zolnierkiewicz
Reviewed-by: Sebastian Reichel
---
drivers/mfd/ab8500-sysctrl.c | 2 +
Replace direct usage of put_device() with new API: power_supply_put().
Signed-off-by: Krzysztof Kozlowski
Acked-by: Pavel Machek
Reviewed-by: Bartlomiej Zolnierkiewicz
Reviewed-by: Sebastian Reichel
---
arch/x86/platform/olpc/olpc-xo15-sci.c | 4 ++--
1 file changed, 2 insertions(+), 2 deleti
The power_supply_get_by_phandle() and power_supply_get_by_name() use
function class_find_device() for obtaining the reference to power
supply. Each use of class_find_device() increases the power supply's
device reference counter.
However the reference counter was not decreased by users of this API
Use power_supply_put() to decrement the power supply's device reference
counter.
Signed-off-by: Krzysztof Kozlowski
Reviewed-by: Bartlomiej Zolnierkiewicz
Reviewed-by: Sebastian Reichel
Acked-by: Robert Jarzmik
---
arch/arm/mach-pxa/raumfeld.c | 4 +++-
1 file changed, 3 insertions(+), 1 dele
block operations is used to flush all dirty node and dentry blocks in
the page cache and suspend ordinary writing activities, however, there
are some facts such like cp error or mount read-only etc which lead to
block operations can't be invoked. Current trace point print block_ops
start prematu
The tasklet may be scheduled and executed after serial port
was shutdown, for example, DMA rx callback will schedule the
tasklet while serial port is shutting down, especially serial
port is sending and receiving data in a higher baud rate and
it's killed by external program. In this case, tasklet_
The property in device tree will be reading each time when tty is opened,
so the ops of serial port should be set after that instead of setting once
in probe. Otherwise, the ops of serial port is inconsistent with the state
of serial work manner. For example, the atmel serial driver can't work when
The function of atmel_init_property is to set the work manner of
atmel serial ports according to the property in device trees.
If DMA or PDC is not set or something goes wrong in getting property,
the work manner will switch to general PIO mode, thus there will
not be any failure case in this funct
The buffer size set in DMA is inconsistent with its allocation.
So keep them consistent here. The structure atmel_uart_char is
used in PIO mode with its meaning. But here in DMA, all of the
buffer is treated as general char.
Signed-off-by: Leilei Zhao
Acked-by: Nicolas Ferre
---
drivers/tty/ser
We only use buf of ring In DMA rx function while using buf of xmit
in DMA tx function. So in DMA rx we need definitively to check the
buf of ring which is corresponding to DMA rx function. And use macro
PAGE_ALIGNED to simplify the expression.
Signed-off-by: Leilei Zhao
Acked-by: Nicolas Ferre
-
The series of patches fix bugs when using multiple serial ports at the same
time:
- The using rx ring buffer in DMA is inconsistent with its allocation.
- The serial port can't send and receive data when it's opened the second time
and the later if it switches to PIO when DMA channel is not a
> Debugfs_remove will check for error or NULL for us, so it is not
> necessary to do this here.
>
> Signed-off-by: Bas Peters
Thanks, applied to wireless-drivers-next.git.
Kalle Valo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord..
(2015/02/27 1:13), Petr Mladek wrote:
> Also disarm_kprobe_ftrace() could fail, for example if there is an internal
> error in the Kprobe code and we try to unregister some Kprobe that is not
> registered.
No, no registered kprobes are rejected at the beginning of __disable_kprobe.
And I'm not su
601 - 685 of 685 matches
Mail list logo
