Hello Maintainers:
Maybe... I still miss some important mail addresses? or this patch is
not suitable for applying?
Hmm... but I still want to try the last time: "please help check this
patch, when you have time".
And next, I should not send additional tracing mail again, that will be
really
(2013/08/30 22:15), Srivatsa S. Bhat wrote:
Given a page, we would like to have an efficient mechanism to find out
the node memory region and the zone memory region to which it belongs.
Since the node is assumed to be divided into equal-sized node memory
regions, the node memory region can be
On Mon, Sep 2, 2013 at 9:45 PM, Zhi Yong Wu wrote:
> On Mon, Sep 2, 2013 at 4:57 PM, Michel Lespinasse wrote:
>> Thanks for the link - I now better understand where you are coming
>> from with these fixes.
>>
>> Going back to the original message:
>>
>>> diff --git
* Arnaldo Carvalho de Melo wrote:
> From: Arnaldo Carvalho de Melo
>
> Hi Ingo,
>
> Please consider pulling,
>
> - Arnaldo
>
> The following changes since commit 7bfb7e6bdd906f11ee9e751b3fec4f4fc728e818:
>
> perf: Convert kmalloc_node(...GFP_ZERO...) to kzalloc_node() (2013-09-02
From: Hyeoncheol Lee
Move kprobes-specific fetch functions to the trace_kprobe.c file.
Also define kprobes_fetch_type_table in the .c file. This table is
shared with uprobes for now, but the uprobes will get its own table
in the later patch.
This is a preparation for supporting more fetch
From: Hyeoncheol Lee
The deref fetch methods access a memory region but it assumes that
it's a kernel memory since uprobes does not support them.
Add ->fetch and ->fetch_size member in order to provide a proper
access methods for supporting uprobes.
Acked-by: Masami Hiramatsu
Cc: Srikar
From: Namhyung Kim
The print format of s32 type was "ld" and it's casted to "long". So
it turned out to print 4294967295 for "-1" on 64-bit systems. Not
sure whether it worked well on 32-bit systems.
Anyway, it'd be better if we have exact format and type cast for each
types on both of 32-
From: Namhyung Kim
The uprobe syntax requires an offset after a file path not a symbol.
Reviewed-by: Masami Hiramatsu
Cc: Srikar Dronamraju
Cc: Oleg Nesterov
Cc: zhangwei(Jovi)
Cc: Arnaldo Carvalho de Melo
Signed-off-by: Namhyung Kim
---
Documentation/trace/uprobetracer.txt | 10
From: Namhyung Kim
Fetching from user space should be done in a non-atomic context. So
use a per-cpu buffer and copy its content to the ring buffer
atomically. Note that we can migrate during accessing user memory
thus use a per-cpu mutex to protect concurrent accesses.
This is needed since
From: Namhyung Kim
Those fetch functions need to be implemented differently for kprobes
and uprobes. Since the deref fetch functions don't call those
directly anymore, we can make them static and implement them
separately.
Acked-by: Masami Hiramatsu
Cc: Srikar Dronamraju
Cc: Oleg Nesterov
From: Namhyung Kim
This argument is for passing private data structure to each fetch
function and will be used by uprobes.
Acked-by: Masami Hiramatsu
Cc: Srikar Dronamraju
Cc: Oleg Nesterov
Cc: zhangwei(Jovi)
Cc: Arnaldo Carvalho de Melo
Signed-off-by: Namhyung Kim
---
Hello,
This patchset implements memory (address), stack[N], deference,
bitfield and retval (it needs uretprobe tho) fetch methods for
uprobes. It's based on the previous work [1] done by Hyeoncheol Lee.
Now kprobes and uprobes have their own fetch_type_tables and, in turn,
memory and stack
From: Namhyung Kim
Convert struct trace_uprobe to make use of the common trace_probe
structure.
Reviewed-by: Masami Hiramatsu
Cc: Srikar Dronamraju
Cc: Oleg Nesterov
Cc: zhangwei(Jovi)
Cc: Arnaldo Carvalho de Melo
Signed-off-by: Namhyung Kim
---
kernel/trace/trace_uprobe.c | 151
From: Namhyung Kim
Implement uprobe-specific stack and memory fetch functions and add
them to the uprobes_fetch_type_table. Other fetch fucntions will be
shared with kprobes.
Original-patch-by: Hyeoncheol Lee
Reviewed-by: Masami Hiramatsu
Cc: Srikar Dronamraju
Cc: Oleg Nesterov
Cc:
From: Namhyung Kim
Enable to fetch other types of argument for the uprobes. IOW, we can
access stack, memory, deref, bitfield and retval from uprobes now.
The format for the argument types are same as kprobes (but @SYMBOL
type is not supported for uprobes), i.e:
@ADDR : Fetch memory at
From: Namhyung Kim
There are functions that can be shared to both of kprobes and uprobes.
Separate common data structure to struct trace_probe and use it from
the shared functions.
Acked-by: Masami Hiramatsu
Cc: Srikar Dronamraju
Cc: Oleg Nesterov
Cc: zhangwei(Jovi)
Cc: Arnaldo Carvalho de
From: Namhyung Kim
The __get_data_size() and store_trace_args() will be used by uprobes
too. Move them to a common location.
Acked-by: Masami Hiramatsu
Cc: Srikar Dronamraju
Cc: Oleg Nesterov
Cc: zhangwei(Jovi)
Cc: Arnaldo Carvalho de Melo
Signed-off-by: Namhyung Kim
---
> > How about change the filter_fn to follow:
> > static bool fsl_edma_filter_fn(struct dma_chan *chan, void *fn_param)
> > {
> > struct fsl_edma_filter_param *fparam = fn_param;
> > struct fsl_edma_chan *fsl_chan = to_fsl_edma_chan(chan);
> > unsigned char val;
> >
> >
From: Namhyung Kim
The set_print_fmt() functions are implemented almost same for
[ku]probes. Move it to a common place and get rid of the duplication.
Acked-by: Masami Hiramatsu
Cc: Srikar Dronamraju
Cc: Oleg Nesterov
Cc: zhangwei(Jovi)
Cc: Arnaldo Carvalho de Melo
Signed-off-by: Namhyung
* Paul E. McKenney wrote:
> Hello, Ingo,
>
> The major changes for this series are:
>
> 1.Update RCU documentation. These were posted to LKML at
> https://lkml.org/lkml/2013/8/19/611.
>
> 2.Miscellaneous fixes. These were posted to LKML at
>
Hello Maintainers:
Is this issue finished ?
If need additional help from me (e.g. some test things, or others, if
you have no time, can let me try), please let me know, I should try.
Thanks.
On 08/26/2013 10:21 AM, Chen Gang F T wrote:
>
> Firstly, thank you for your reply with these
On 09/03/2013 11:00 AM, Wanpeng Li wrote:
> The VM_UNINITIALIZED/VM_UNLIST flag introduced by commit f5252e00(mm: avoid
> null pointer access in vm_struct via /proc/vmallocinfo) is used to avoid
> accessing the pages field with unallocated page when show_numa_info() is
> called. This patch move
On 09/03/2013 10:48 AM, Yinghai Lu wrote:
On Mon, Sep 2, 2013 at 6:06 PM, Tang Chen wrote:
Hi Yinghai,
On 09/03/2013 02:41 AM, Yinghai Lu wrote:
How about change the "for (from low to high)" in init_range_memory_mapping()
to
"for_rev(from high to low)" ?
Then we can update min_pfn_mapped
On 09/03/2013 11:00 AM, Wanpeng Li wrote:
> Don't warning twice in __vmalloc_area_node and __vmalloc_node_range if
> __vmalloc_area_node allocation failure.
>
> Signed-off-by: Wanpeng Li
OK, I missed the warning in __vmalloc_area_node(), so you are right.
You can just revert the commit
On 09/03/2013 11:00 AM, Wanpeng Li wrote:
> Changelog:
> * rebase against mmotm tree
>
> The caller address has already been set in set_vmalloc_vm(), there's no need
> to set it again in __vmalloc_area_node.
>
> Signed-off-by: Wanpeng Li
Reviewed-by: Zhang Yanfei
> ---
> mm/vmalloc.c |
Hello Maintainers:
Please help check this patch, when you have time.
If it need additional test, please let me know, I should try (better to
provide some suggestions for test).
Thanks.
On 08/22/2013 09:04 AM, Chen Gang wrote:
> mpol_to_str() may fail, and not fill the buffer (e.g. -EINVAL),
> Subject: Re: [PATCH 4/4] Documentation: Add device tree bindings for
> Freescale FTM PWM
>
> On 08/30/2013 01:19 PM, Kumar Gala wrote:
> > Should have at least something w/regards to a commit message.
> >
> > On Aug 20, 2013, at 10:07 PM, Xiubo Li wrote:
> >
> >> Signed-off-by: Xiubo Li
> >>
Hello Maintainers:
Please help check this patch, when you have time.
If need a related test, please let me know, I should try (better to
provide some suggestions for test).
Thanks.
On 08/20/2013 11:03 AM, Chen Gang wrote:
>
> If this patch is correct, also need modify the man page for the
Need check the return value of proc_put_char(), just like another have
done in __do_proc_doulongvec_minmax().
Signed-off-by: Chen Gang
---
kernel/sysctl.c |5 -
1 files changed, 4 insertions(+), 1 deletions(-)
diff --git a/kernel/sysctl.c b/kernel/sysctl.c
index b2f06f3..7453418 100644
On Sunday 18 of August 2013, Margarita Manterola wrote:
> Hi,
>
> On Sat, Aug 17, 2013 at 5:28 PM, Pavel Machek wrote:
> >> diff --git a/drivers/tty/n_tty.c b/drivers/tty/n_tty.c
> >> index 4bf0fc0..2ba7f4e 100644
> >> --- a/drivers/tty/n_tty.c
> >> +++ b/drivers/tty/n_tty.c
> >> @@ -149,7
Hello Maintainers:
Please help check this patch, when you have time.
Thanks.
On 08/21/2013 11:48 AM, Chen Gang wrote:
> On 08/21/2013 12:19 AM, Darren Hart wrote:
>> HopingOn Tue, 2013-08-20 at 11:07 +0800, Chen Gang wrote:
>>
>>
>> Hi Chen,
>>
>>> rt_mutex_finish_proxy_lock() can return
Hello maintainers:
Please help check this patch, when you have time.
Thanks.
On 08/20/2013 10:44 AM, Chen Gang wrote:
> When failure occurs between nla_nest_start() and nla_nest_end(), need
> call nla_nest_cancel() to clean up related things.
>
> Signed-off-by: Chen Gang
> ---
>
From: Namhyung Kim
The set_graph_notrace filter is analogous to set_ftrace_notrace and
can be used for eliminating uninteresting part of function graph trace
output. It also works with set_graph_function nicely.
# cd /sys/kernel/debug/tracing/
# echo do_page_fault > set_graph_function
#
The wrapper function delayacct_add_tsk() already checked 'tsk->delays',
and __delayacct_add_tsk() has no another direct callers, so can remove
the redundancy checking code.
And the label 'done' is also useless, so remove it, too.
Signed-off-by: Chen Gang
---
kernel/delayacct.c |7 ---
On Mon, 2013-09-02 at 12:10 +0200, Karel Zak wrote:
> On Mon, Aug 05, 2013 at 10:21:09PM -0700, Davidlohr Bueso wrote:
> >
> > +typedef struct _gpt_record {
> > +u8 boot_indicator; /* unused by EFI, set to 0x80 for bootable
> > */
> > +u8 start_head; /* unused by
(2013/09/03 2:43), Srivatsa S. Bhat wrote:
On 09/02/2013 11:50 AM, Yasuaki Ishimatsu wrote:
(2013/08/30 22:15), Srivatsa S. Bhat wrote:
Initialize the node's memory-regions structures with the information
about
the region-boundaries, at boot time.
Based-on-patch-by: Ankita Garg
On Thu, Aug 29, 2013 at 06:05:41PM -0500, Joel Fernandes wrote:
> Process SG-elements in batches of MAX_NR_SG if they are greater
> than MAX_NR_SG. Due to this, at any given time only those many
> slots will be used in the given channel no matter how long the
> scatter list is. We keep track of
From: Luiz capitulino
flush_hold_queue() first dequeues an SKB and then checks if
auditd exists. If auditd doesn't exist, the SKB is silently
dropped.
Avoid this by not dequeing an SKB when we detected that
auditd disappeared.
Signed-off-by: Luiz capitulino
---
kernel/audit.c | 19
The second patch fixes a softlockup which is fully described and now is
100% reproducible with simple steps. The first patch fixes a bug I found
while working on the second patch.
Chuck Anderson just posted a different solution for the same problem.
I was about to post this solution when he
From: Luiz capitulino
Try this:
1. Download the readahead-collector program and build it
2. Run it with:
# readahead-collector -f
3. From another terminal do:
# pkill -SIGSTOP readahead-collector
4. Keep using the system, run top -d1, vmstat -S 1, etc
5. Eventually, you'll get
On Mon, 02 Sep 2013 20:45:14 -0700
Chuck Anderson wrote:
> The two patches that follow in separate emails resolve soft lockups and
> udevd reported errors that prevented a large memory 3.8 system from booting.
>
> The patches are based on 3.11-rc7.
>
> I believe it is the same issue recently
On Mon, Sep 2, 2013 at 4:57 PM, Michel Lespinasse wrote:
> On Sun, Sep 1, 2013 at 11:30 PM, Zhi Yong Wu wrote:
>> In Tue, Aug 27, 2013 at 6:01 AM, Michel Lespinasse wrote:
>>> On Fri, Aug 23, 2013 at 7:45 AM, wrote:
From: Zhi Yong Wu
Signed-off-by: Zhi Yong Wu
---
> Subject: Re: [PATCHv2 1/4] pwm: Add Freescale FTM PWM driver support
>
> On Mon, Sep 02, 2013 at 03:33:37AM +, Xiubo Li-B47053 wrote:
> >
> > > > +static void fsl_pwm_free(struct pwm_chip *chip, struct pwm_device
> > > > +*pwm) {
> > > > + struct fsl_pwm_chip *fpc;
> > > > +
The original SOFT_DISABLE patches didn't add support for soft disable
of syscall events; this adds it and paves the way for future patches
allowing triggers to be added to syscall events, since triggers are
built on top of SOFT_DISABLE.
Add an array of ftrace_event_file pointers indexed by
Add a generic event_command.set_trigger_filter() op implementation and
have the current set of trigger commands use it - this essentially
gives them all support for filters.
Syntactically, filters are supported by adding 'if ' just
after the command, in which case only events matching the filter
The trace event filters are still tied to event calls rather than
event files, which means you don't get what you'd expect when using
filters in the multibuffer case:
Before:
# echo 'count > 65536' >
/sys/kernel/debug/tracing/events/syscalls/sys_enter_read/filter
# cat
Hi,
This is v8 of the trace event triggers patchset. This version
addresses the comments and feedback from Steve Rostedt on v7.
v8:
- changed rcu_dereference_raw() to rcu_dereference() and moved
synchronize_sched() out from under the syscall_trace_lock mutex.
- got rid of the various void
audit: Two efficiency fixes for audit mechanism
author: Dan Duval
These and similar errors were seen on a patched 3.8 kernel when the
audit subsystem was overrun during boot:
udevd[876]: worker [887] unexpectedly returned with status 0x0100
udevd[876]: worker [887] failed while handling
register/unregister_ftrace_command() are only ever called from __init
functions, so can themselves be made __init.
Also make register_snapshot_cmd() __init for the same reason.
Signed-off-by: Tom Zanussi
---
include/linux/ftrace.h | 4 ++--
kernel/trace/ftrace.c | 12 ++--
Add 'snapshot' event_command. snapshot event triggers are added by
the user via this command in a similar way and using practically the
same syntax as the analogous 'snapshot' ftrace function command, but
instead of writing to the set_ftrace_filter file, the snapshot event
trigger is written to
Add 'enable_event' and 'disable_event' event_command commands.
enable_event and disable_event event triggers are added by the user
via these commands in a similar way and using practically the same
syntax as the analagous 'enable_event' and 'disable_event' ftrace
function commands, but instead of
Add 'stacktrace' event_command. stacktrace event triggers are added
by the user via this command in a similar way and using practically
the same syntax as the analogous 'stacktrace' ftrace function command,
but instead of writing to the set_ftrace_filter file, the stacktrace
event trigger is
On 09/03/2013 11:26 AM, Guenter Roeck wrote:
> On 09/02/2013 07:53 PM, Chen Gang F T wrote:
>> Hello Guenter Roeck:
>>
>>
>> I don't care about whether I am in cc mailing list, but at least,
>> please help confirm 2 things:
>>
>>Is what I had done for h8300 just making wastes and noisy in
Provide a basic overview of trace event triggers and document the
available trigger commands, along with a few simple examples.
Signed-off-by: Tom Zanussi
---
Documentation/trace/events.txt | 207 +
1 file changed, 207 insertions(+)
diff --git
Add a 'trigger' file for each trace event, enabling 'trace event
triggers' to be set for trace events.
'trace event triggers' are patterned after the existing 'ftrace
function triggers' implementation except that triggers are written to
per-event 'trigger' files instead of to a single file such
Add 'traceon' and 'traceoff' event_command commands. traceon and
traceoff event triggers are added by the user via these commands in a
similar way and using practically the same syntax as the analagous
'traceon' and 'traceoff' ftrace function commands, but instead of
writing to the
audit: fix softlockups due to loop in audit_log_start() when
audit_backlog_limit exceeded
author: Dan Duval
This patch fixes a bug in kernel/audit that can cause many soft lockups
and prevent the boot of a large memory 3.8 system:
BUG: soft lockup - CPU#66 stuck for 22s! [udevd:9559]
The two patches that follow in separate emails resolve soft lockups and
udevd reported errors that prevented a large memory 3.8 system from booting.
The patches are based on 3.11-rc7.
I believe it is the same issue recently posted as:
[RFC] audit: avoid soft lockup in audit_log_start()
I tried applying this patch on linux-next and it applies well.
i used
git apply --apply
On Saturday 31 August 2013 11:02 PM, Kumar Gaurav wrote:
This patch redefine function xhci_readl. xhci_readl function doesn't use
xhci_hcd argument.
Hence there is no need of keeping it in the
From: David Howells
Date: Mon, 02 Sep 2013 22:35:06 +0100
> Would it be possible to use __thread annotations for per-CPU
> variables, I wonder?
Paul Mackerras tried it on powerpc and you can't do it.
The problem is that there is no way to tell the compiler that sched()
and similar
On Tue, Sep 03, 2013 at 07:36:44AM +0800, Wanpeng Li wrote:
> Date: Tue, 3 Sep 2013 07:36:44 +0800
> From: Wanpeng Li
> To: Andrew Morton
> Cc: Andi Kleen , Fengguang Wu
> , Naoya Horiguchi ,
> Tony Luck , gong.c...@linux.intel.com,
> linux...@kvack.org, linux-kernel@vger.kernel.org, Wanpeng
On 09/02/2013 07:53 PM, Chen Gang F T wrote:
> Hello Guenter Roeck:
>
>
> I don't care about whether I am in cc mailing list, but at least,
> please help confirm 2 things:
>
>Is what I had done for h8300 just making wastes and noisy in kernel and
> related sub-system mailing list ?
>
>
On Mon, Sep 02, 2013 at 08:16:45PM -0700, Josh Triplett wrote:
> On Tue, Sep 03, 2013 at 10:46:40AM +0800, Fengguang Wu wrote:
> > On Mon, Sep 02, 2013 at 06:52:45PM -0700, Joe Perches wrote:
> > > On Mon, 2013-09-02 at 18:34 -0700, Josh Triplett wrote:
> > > > CONFIG_EXPERIMENTAL
> > > >
Hello,
It seems like Sunil has fixed a similar issue against ocfs2-1.4
several years ago:
https://oss.oracle.com/git/?p=ocfs2-1.4.git;a=commitdiff_plain;h=2fd250839d0f5073af8d42e97f1db74beb621674;hp=e882faf84930431524f84598caea7d4e9a9529c5
On Tue, Sep 03, 2013 at 10:46:40AM +0800, Fengguang Wu wrote:
> On Mon, Sep 02, 2013 at 06:52:45PM -0700, Joe Perches wrote:
> > On Mon, 2013-09-02 at 18:34 -0700, Josh Triplett wrote:
> > > CONFIG_EXPERIMENTAL
> > > CVS_KEYWORD
> >
> > OK, but
[...]
> Thanks for both of your suggestions! I'll
Any more comments? Or this one is not proper?
On Thu, Aug 22, 2013 at 09:33:27PM -0600, Alex Williamson wrote:
>[+cc iommu]
>
>On Fri, 2013-08-23 at 09:55 +0800, Wei Yang wrote:
>> When removing a device from the system, iommu_group driver will try to
>> disconnect it from its group. While in
The VM_UNINITIALIZED/VM_UNLIST flag introduced by commit f5252e00(mm: avoid
null pointer access in vm_struct via /proc/vmallocinfo) is used to avoid
accessing the pages field with unallocated page when show_numa_info() is
called. This patch move the check just before show_numa_info in order that
Don't warning twice in __vmalloc_area_node and __vmalloc_node_range if
__vmalloc_area_node allocation failure.
Signed-off-by: Wanpeng Li
---
mm/vmalloc.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/mm/vmalloc.c b/mm/vmalloc.c
index d78d117..e3ec8b4 100644
---
Changelog:
* rebase against mmotm tree
The caller address has already been set in set_vmalloc_vm(), there's no need
to set it again in __vmalloc_area_node.
Signed-off-by: Wanpeng Li
---
mm/vmalloc.c |1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/mm/vmalloc.c
On 08/27/2013 09:06 PM, Guenter Roeck wrote:
xtansa allmodbuild fails with:
arch/xtensa/kernel/xtensa_ksyms.c:129:1: error: '_mcount' undeclared here (not
in a function)
make[2]: *** [arch/xtensa/kernel/xtensa_ksyms.o] Error 1
make[1]: *** [arch/xtensa/kernel] Error 2
The breakage is due to
Hello Guenter Roeck:
I don't care about whether I am in cc mailing list, but at least,
please help confirm 2 things:
Is what I had done for h8300 just making wastes and noisy in kernel and
related sub-system mailing list ?
and is the disccusion about h8300 between us also wastes and noisy
Hi Ted,
On Mon, 2013-09-02 at 22:17 -0400, Theodore Ts'o wrote:
> On Mon, Sep 02, 2013 at 04:46:18PM -0700, Guenter Roeck wrote:
> > I don't think it has anything to do with linux-iscsi.org.
> > Possibly Nicholas' e-mail provider is not hosted in the US, meaning e-mail
> > sent through it can not
On Mon, Sep 2, 2013 at 6:06 PM, Tang Chen wrote:
> Hi Yinghai,
>
> On 09/03/2013 02:41 AM, Yinghai Lu wrote:
> How about change the "for (from low to high)" in init_range_memory_mapping()
> to
> "for_rev(from high to low)" ?
> Then we can update min_pfn_mapped in add_pfn_range_mapped().
>
> And
On Mon, Sep 02, 2013 at 06:52:45PM -0700, Joe Perches wrote:
> On Mon, 2013-09-02 at 18:34 -0700, Josh Triplett wrote:
> > I'd suggest a couple more, which
> > *should* always make sense, and to the best of my knowledge don't tend
> > to generate false positives:
> >
> > C99_COMMENTS
>
> I don't
On Mon, 2013-09-02 at 19:12 -0700, Josh Triplett wrote:
> On Mon, Sep 02, 2013 at 06:52:45PM -0700, Joe Perches wrote:
> > On Mon, 2013-09-02 at 18:34 -0700, Josh Triplett wrote:
> > > I'd suggest a couple more, which
> > > *should* always make sense, and to the best of my knowledge don't tend
> >
On Mon, Sep 02, 2013 at 04:46:18PM -0700, Guenter Roeck wrote:
> I don't think it has anything to do with linux-iscsi.org.
> Possibly Nicholas' e-mail provider is not hosted in the US, meaning e-mail
> sent through it can not be logged and examined by a certain US government
> agency.
Hardly.
On Mon, Sep 02, 2013 at 06:52:45PM -0700, Joe Perches wrote:
> On Mon, 2013-09-02 at 18:34 -0700, Josh Triplett wrote:
> > I'd suggest a couple more, which
> > *should* always make sense, and to the best of my knowledge don't tend
> > to generate false positives:
> >
> > C99_COMMENTS
>
> I don't
On Mon, 2013-09-02 at 18:34 -0700, Josh Triplett wrote:
> I'd suggest a couple more, which
> *should* always make sense, and to the best of my knowledge don't tend
> to generate false positives:
>
> C99_COMMENTS
I don't have a problem with c99 comments.
As far as I know, Linus doesn't either.
On 09/02/2013 06:07 PM, Greg KH wrote:
On Mon, Sep 02, 2013 at 05:46:58PM -0500, Daniel Santos wrote:
Hello guys. I didn't get a response the last time so hopefully with
3.11 out I'll get one this time.
I need to be able to generate interrupts from a USB device driver while
servicing the
On Mon, Sep 02, 2013 at 05:47:54PM -0700, Joe Perches wrote:
> On Tue, 2013-09-03 at 08:39 +0800, Fengguang Wu wrote:
> > On Mon, Sep 02, 2013 at 02:11:36PM -0700, Joe Perches wrote:
> []
> > > Fengguang Wu's very useful build robot
> > > sends out emails on build failures.
> > > I think that's
On Tue, Sep 03, 2013 at 08:39:58AM +0800, Fengguang Wu wrote:
> On Mon, Sep 02, 2013 at 02:11:36PM -0700, Joe Perches wrote:
> > On Mon, 2013-09-02 at 21:50 +0100, David Howells wrote:
> > > Josh Triplett wrote:
> > >
> > > > > There are many checkpatch rules (like semicolons) that
> > > > > are
On Mon, Sep 02, 2013 at 05:36:03PM -0700, Josh Triplett wrote:
> On Tue, Sep 03, 2013 at 08:26:21AM +0800, Shilong Wang wrote:
> > 2013/9/3 Joe Perches :
> > > Wang Shilong
> > > sent me an automated checkpatch email I
> > > thought was not useful.
> >
> > I am sorry if i give you any trouble, i
Hi Yinghai,
On 09/03/2013 02:41 AM, Yinghai Lu wrote:
..
Nak, you can not move that.
min_pfn_mapped should not be updated before init_range_memory_mapping
is returned. as it need to refer old min_pfn_mapped.
and init_range_memory_mapping still init mapping from low to high locally.
On Tue, 2013-09-03 at 08:39 +0800, Fengguang Wu wrote:
> On Mon, Sep 02, 2013 at 02:11:36PM -0700, Joe Perches wrote:
[]
> > Fengguang Wu's very useful build robot
> > sends out emails on build failures.
> > I think that's great.
>
> Thanks! Yes I'm now running checkpatch these days because some
Hi Jin,
> [...]
> >
> > It seems that we can obtain the performance gain just by setting the
> > MAX_VICTIM_SEARCH to 4096, for example.
> > So, how about just adding an ending criteria like below?
> >
>
> I agree that we could get the performance improvement by simply
> enlarging the
On Mon, 2013-09-02 at 15:50 -0700, Linus Torvalds wrote:
> On Mon, Sep 2, 2013 at 3:30 PM, Nicholas A. Bellinger
> wrote:
> >
> > Unfortunately, this doesn't include the remaining target fixes for
> > v3.11:
> >
> > Re: [GIT PULL -v2] target fixes for v3.11
> >
On Mon, Sep 02, 2013 at 02:11:36PM -0700, Joe Perches wrote:
> On Mon, 2013-09-02 at 21:50 +0100, David Howells wrote:
> > Josh Triplett wrote:
> >
> > > > There are many checkpatch rules (like semicolons) that
> > > > are not in CodingStyle.
> > >
> > > It's a rule of thumb, not a mandate. In
On Tue, Sep 03, 2013 at 08:26:21AM +0800, Shilong Wang wrote:
> 2013/9/3 Joe Perches :
> > Wang Shilong
> > sent me an automated checkpatch email I
> > thought was not useful.
>
> I am sorry if i give you any trouble, i have disabled it(in fact, it
> only has run for a day!)
I would suggest
On Mon, Sep 02, 2013 at 04:54:25PM -0700, Joe Perches wrote:
> > would you mind looking at why
> > it gives a false positive for spaces around '*' on my recent patch at
> > http://mid.gmane.org/20130901234251.GB25057@leaf ? It appears to
> > mistake the '*' of a pointer for a multiply.
>
> Looks
I noticed that linux-iscsi.org isn't doing much to protect itself from being
used as a spam source. If you setup the following you should be less likely to
be marked as spam:
* SPF record (setup both spf and a txt spf record for compatibility)
* DMARC record to enforce SPF and allow servers to
2013/9/3 Joe Perches :
> On Mon, 2013-09-02 at 21:50 +0100, David Howells wrote:
>> Josh Triplett wrote:
>>
>> > > There are many checkpatch rules (like semicolons) that
>> > > are not in CodingStyle.
>> >
>> > It's a rule of thumb, not a mandate. In *general*, checkpatch.pl should
>> > not be
On Tue, Sep 03, 2013 at 07:36:44AM +0800, Wanpeng Li wrote:
> Changelog:
> *v1 -> v2: reverse PageTransHuge(page) && !PageHuge(page) check
>
> PageTransHuge() can't guarantee the page is transparent huge page since it
> return true for both transparent huge and hugetlbfs pages. This patch fix
Yoshihiro YUNOMAE writes:
> Hi Eric and Don,
>
> Sorry for the late reply.
>
> (2013/08/31 9:58), Eric W. Biederman wrote:
>> Don Zickus writes:
>>
>>> On Tue, Aug 27, 2013 at 12:41:51PM +0900, Yoshihiro YUNOMAE wrote:
Hi Don,
Sorry for the late reply.
(2013/08/22
Hi Wolfram
CC Morimoto
Please consider the following patch for the r8a7790 Soc.
This patch modify I2C driver of rcar-H1 to usable on both rcar-H1 and rcar-H2.
It was developed base on the renesas-devel-20130722 branch and
have tested on the Lager board.
Thanks,
Nguyen viet Dung
Nguyen Viet Dung
This patch modify I2C driver of rcar-H1 to usable on both rcar-H1 and rcar-H2.
Signed-off-by: Nguyen Viet Dung
---
drivers/i2c/busses/i2c-rcar.c | 35 +--
1 file changed, 33 insertions(+), 2 deletions(-)
diff --git a/drivers/i2c/busses/i2c-rcar.c
The following changes since commit c095ba7224d8edc71dcef0d655911399a8bd4a3f:
Linux 3.11-rc4 (2013-08-04 13:46:46 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git/
tags/tty-3.12-rc1
for you to fetch changes up to
The following changes since commit 5ae90d8e467e625e447000cb4335c4db973b1095:
Linux 3.11-rc3 (2013-07-28 20:53:33 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git/
tags/driver-core-3.12-rc1
for you to fetch changes up to
The following changes since commit b36f4be3de1b123d8601de062e7dbfc904f305fb:
Linux 3.11-rc6 (2013-08-18 14:36:53 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git/
tags/usb-3.12-rc1
for you to fetch changes up to
The following changes since commit b36f4be3de1b123d8601de062e7dbfc904f305fb:
Linux 3.11-rc6 (2013-08-18 14:36:53 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git/
tags/char-misc-3.12-rc1
for you to fetch changes up to
> would you mind looking at why
> it gives a false positive for spaces around '*' on my recent patch at
> http://mid.gmane.org/20130901234251.GB25057@leaf ? It appears to
> mistake the '*' of a pointer for a multiply.
Looks like checkpatch thinks this should be a multiplication.
Try this:
---
1 - 100 of 1018 matches
Mail list logo
