This patch prohibits probing instructions for which the stack
requirements are unable to be determined statically. Some test cases
are found not work again after the modification, this patch also
removes them.
Signed-off-by: Wang Nan
Reviewed-by: Jon Medhurst
---
arch/arm/include/asm/kprobes.h
From: "Jon Medhurst (Tixy)"
For the instruction 'mrs Rn, cpsr' the resulting value of Rn can vary due to
external factors we can't control. So get the test code to mask out these
indeterminate bits.
Signed-off-by: Jon Medhurst
---
arch/arm/probes/kprobes/test-arm.c | 6 +++---
This patch introdces 'checker' to decoding phase, and calls checkers
when instruction decoding. This allows further decoding for specific
instructions. This patch introduces a stub call of checkers in kprobe
arch_prepare_kprobe() as an example and for further expansion.
Signed-off-by: Wang Nan
This patch utilizes previous introduced checker to check register usage
for probed ARM instruction and saves it in a mask. Futher patch will
use such information to avoid simuation or emulation.
Signed-off-by: Wang Nan
---
arch/arm/include/asm/probes.h | 9 +++
This patch introduce kprobeopt for ARM 32.
Limitations:
- Currently only kernel compiled with ARM ISA is supported.
- Offset between probe point and optinsn slot must not larger than
32MiB. Masami Hiramatsu suggests replacing 2 words, it will make
things complex. Futher patch can make
This patch removes software emulation or simulation for most of probed
instructions. If the instruction doesn't use PC relative addressing,
it will be translated into following instructions in the restore code
in code template:
ldmia {r0 - r14} // restore all instruction except PC
//
From: Masami Hiramatsu
Pass the original kprobe for preparing an optimized kprobe arch-dep
part, since for some architecture (e.g. ARM32) requires the information
in original kprobe.
Signed-off-by: Masami Hiramatsu
Signed-off-by: Wang Nan
---
arch/x86/kernel/kprobes/opt.c | 3 ++-
From: "Jon Medhurst (Tixy)"
These have extra 'checker' functions associated with them so lets make
sure those get covered by testing. As they may create uninitialised
space on the stack we also update the test code to ensure such space is
consistent between test runs. This is done by disabling
This patch uses the previously introduced checker functionality on
store instructions to record their stack consumption information to
arch_probes_insn.
Signed-off-by: Wang Nan
Signed-off-by: Jon Medhurst
Reviewed-by: Jon Medhurst
---
arch/arm/include/asm/probes.h | 1 +
There are 3 actions which is never used:
PROBES_MOV_HALFWORD,
PROBES_SEV,
PROBES_WFE,
This patch removes them.
Signed-off-by: Wang Nan
---
arch/arm/probes/decode-arm.h | 3 ---
arch/arm/probes/kprobes/actions-arm.c | 3 ---
arch/arm/probes/uprobes/actions-arm.c | 3 ---
3 files
In discussion on LKML (https://lkml.org/lkml/2014/11/28/158), Russell
King suggests to move all probe related code to arch/arm/probes. This
patch does the work. Due to dependency on 'arch/arm/kernel/patch.h', this
patch also moves patch.h to 'arch/arm/include/asm/patch.h', and related
'#include'
This is v17 patch series of kprobeopt. The main change in this version
are:
1. Patch 02/11 remove 3 useless ARM decode actions.
2. Patch 10/11 collects register usage of probed instructions.
3. Patch 11/11 use register usage information to decide whether
the probed instruction needs
Fixing typo for MeshConnect IDs. The original PID (0x8875) is not in production
and is not needed. Instead it has been changed to the official production PID
(0x8857).
Signed-off-by: Preston Fick
---
drivers/usb/serial/cp210x.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On Fri, Dec 26, 2014 at 10:00:00AM +, Jonathan Cameron wrote:
> On 22/12/14 13:48, Sudip Mukherjee wrote:
> > On Mon, Dec 22, 2014 at 02:23:42AM +0100, Helene Gsaenger wrote:
> >> Signed-off-by: Helene Gsaenger
> >> Signed-off-by: Simone Weiss
> >> ---
> >>
Hello,
On Fri, 26 Dec 2014, Stefan I. Strogin wrote:
From: Dmitry Safonov
Here are two functions that provide interface to compute/get used size
and size of biggest free chunk in cma region.
Added that information in cmainfo.
Signed-off-by: Dmitry Safonov
---
include/linux/cma.h | 2 ++
On Fri, 26 Dec 2014, Stefan I. Strogin wrote:
Add a function seq_print_stack_trace() which prints stacktraces to seq_files.
Signed-off-by: Stefan I. Strogin
Reviewed-by: SeongJae Park
---
include/linux/stacktrace.h | 4
kernel/stacktrace.c| 17 +
2 files
On Thu, Dec 25, 2014 at 12:28:28PM -0800, David Decotigny wrote:
> Before:
> 1 ERROR: code indent should use tabs where possible
> 1 WARNING: please, no spaces at the start of a line
>
> After:
> (none)
>
> Signed-off-by: David Decotigny
> ---
>
Fixed a coding style issue reported by checkpatch surrounding the
spacing of comma's
Signed-off-by: Damon Swayn
---
drivers/staging/line6/pcm.h | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/staging/line6/pcm.h b/drivers/staging/line6/pcm.h
index
On Sat, Dec 27, 2014 at 2:14 AM, David Ahern wrote:
> On 12/25/14 7:26 PM, Namhyung Kim wrote:
diff --git a/tools/perf/util/thread.h b/tools/perf/util/thread.h
index 0b6dcd70bc8b..413f28cf689b 100644
--- a/tools/perf/util/thread.h
+++ b/tools/perf/util/thread.h
@@
On Sat, Dec 27, 2014 at 2:00 AM, David Ahern wrote:
> On 12/24/14 12:15 AM, Namhyung Kim wrote:
>>
>> @@ -139,6 +161,16 @@ const char *thread__comm_str(const struct thread
>> *thread)
>> return comm__str(comm);
>> }
>>
>> +const char *thread__comm_time_str(const struct thread *thread,
On Sat, Dec 27, 2014 at 1:51 AM, David Ahern wrote:
> On 12/24/14 12:15 AM, Namhyung Kim wrote:
>>
>> When multi file support is enabled, a dummy tracking event will be
>> used to track metadata (like task, comm and mmap events) for a session
>> and actual samples will be recorded in separate
On Sat, Dec 27, 2014 at 1:30 AM, David Ahern wrote:
> On 12/24/14 12:14 AM, Namhyung Kim wrote:
>
>> diff --git a/tools/perf/builtin-inject.c b/tools/perf/builtin-inject.c
>> index 84df2deed988..d8b13407594d 100644
>> --- a/tools/perf/builtin-inject.c
>> +++ b/tools/perf/builtin-inject.c
>> @@
Hi David,
On Sat, Dec 27, 2014 at 1:27 AM, David Ahern wrote:
> On 12/24/14 12:14 AM, Namhyung Kim wrote:
>>
>> Prepend a software dummy event into evlist to track task/comm/mmap
>> events separately. This is a preparation of multi-file/thread support
>> which will come later.
>
>
> Are you are
On Fri, Dec 26, 2014 at 11:02 PM, Jiri Olsa wrote:
> On Wed, Dec 24, 2014 at 04:14:56PM +0900, Namhyung Kim wrote:
>
> SNIP
>
>>
>>
>> You can get it from 'perf/threaded-v1' branch on my tree at:
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/namhyung/linux-perf.git
>>
>> Please take a
Hi Jiri,
On Fri, Dec 26, 2014 at 10:59 PM, Jiri Olsa wrote:
> On Wed, Dec 24, 2014 at 04:15:33PM +0900, Namhyung Kim wrote:
>> The perf data split command is for splitting a (large) single data
>> file into multiple files under a directory (perf.data.dir by default)
>> so that it can be
Current perf diff result is somewhat confusing since it sometimes hide
small result and sometimes there's no result. So do not hide small
result (less than 0.01%) and print "N/A" if baseline is not
recorded (for ratio and wdiff only). Blank means the baseline is
available but its pairs are not.
When perf diff prints output, it sorts the entries using baseline field
by default, but entries which don't have baseline are not sorted
properly. This patch makes it sorted by values of next column.
Before:
# Baseline/0 Delta/1 Delta/2 Shared Object Symbol
# .. ...
The prior change fixes default output ordering with each column but it
breaks -o/--order option. This patch prepends a new hpp fmt struct to
sort list but not to output field list so that it can affect ordering
without adding a new output column.
The new hpp fmt uses its own compare functions
The hists__compute_resort() is to sort output fields based on the
given field/criteria. This was done without the sort list but as we
added the field to the sort list, we can do it with normal
hists__output_resort() using the ->sort callback.
Signed-off-by: Namhyung Kim
---
The currently perf diff didn't add the baseline and delta (or other
compute) fields to the sort list so output will be sorted by other
fields like alphabetical order of DSO or symbol as below example.
Fix it by adding hpp formats for the fields and provides default
compare functions.
Before:
Currently, 'perf list --raw-dump' requires extra arguments
(e.g., hw) to invoke, which breaks bash/zsh completion
(perf-completion.sh).
$ perf list --raw-dump
Error: unknown option `raw-dump'
usage: perf list [hw|sw|cache|tracepoint|pmu|event_glob]
After,
$ perf list --raw-dump
On Fri, Dec 26, 2014 at 4:36 PM, Dave Jones wrote:
> >
> > Oh - and have you actually seen the "TSC unstable (delta = xyz)" +
> > "switched to hpet" messages there yet?
>
> not yet. 3 hrs in.
Ok, so then the
INFO: rcu_preempt detected stalls on CPUs/tasks:
has nothing to do with HPET,
On Fri, Dec 26, 2014 at 03:30:20PM -0800, Linus Torvalds wrote:
> On Fri, Dec 26, 2014 at 2:57 PM, Dave Jones wrote:
> >
> > still running though..
>
> Btw, did you ever boot with "tsc=reliable" as a kernel command line option?
I'll check it again in the morning, but before I turn in for
ACPI's P-states will report the acpi_processor_px *states to acpi-cpufreq.
When the states likes these:
[index:freq, 0:2400 1:2400 2:2000 3:1600...],
we will initialize the freq_tables to those:
[index:driver_data:freq, 0:0:2400, 1:2:2000 2:3,1600 ... CPUFREQ_TABLE_END]
So when set the freqs
When build with 'make ARCH=x86' and dwarf unwind is on, there is a
compiling error:
CC /home/wn/perf/arch/x86/util/unwind-libdw.o
CC /home/wn/perf/arch/x86/tests/regs_load.o
arch/x86/tests/regs_load.S: Assembler messages:
arch/x86/tests/regs_load.S:65: Error: operand type
Update: I errously assumed that git add, while writing the commit
message, would be added to the commit.
Based on net-next f96fe225. Compiles and checkpatch clean.
Jumping between chains doesn't mix well with flush ruleset,
since nft_flush_table doesn't handle chains referencing chains.
This way
On Fri, Dec 26, 2014 at 03:30:20PM -0800, Linus Torvalds wrote:
> On Fri, Dec 26, 2014 at 2:57 PM, Dave Jones wrote:
> >
> > still running though..
>
> Btw, did you ever boot with "tsc=reliable" as a kernel command line option?
I don't think so.
> For the last night, can you see if you
On Fri, Dec 26, 2014 at 03:16:41PM -0800, Linus Torvalds wrote:
> On Fri, Dec 26, 2014 at 2:57 PM, Dave Jones wrote:
> >
> > hm.
>
> So with the previous patch that had the false positives, you never saw
> this? You saw the false positives instead?
correct.
> I'm wondering if the added
On Fri, Dec 5, 2014 at 2:12 PM, Jeff Kirsher
wrote:
> On Fri, 2014-12-05 at 10:41 -0800, Joe Stringer wrote:
>> ndo_gso_check() was recently introduced to allow NICs to report the
>> offloading support that they have on a per-skb basis. Add an
>> implementation for this driver which checks for
Ilia,
On Fri, Dec 26, 2014 at 04:39:08PM -0500, Ilia Mirkin wrote:
> On Fri, Dec 26, 2014 at 4:26 PM, Jeremiah Mahler wrote:
> > If a display supports backlight control using the nouveau driver, and
> > also supports standard ACPI backlight control, there will be two sets of
> > controls.
> >
>
Hi Pavel,
On Fri, Dec 26, 2014 at 06:19:44PM +0100, Pavel Machek wrote:
> On Fri 2014-12-26 13:34:52, Sebastian Reichel wrote:
> > OMAP34xx and OMAP36xx processors contain a register in the syscon area,
> > which can be used to determine the SoCs temperature. This provides a
> > DT binding
hi pavel---I do a complete fresh install on ubuntu 64-bit 14.10 in a
vmware virtual machine. the gcc version is 4.9.1. this way I cannot
have made a mistake. ;-)
the compile is gcc -g -o testfa testfa.c .
the gdb and program must run with root privilege. without it, it will
just abort on the
On Fri, Dec 26, 2014 at 09:06:10AM +0100, Nicholas Mc Guire wrote:
> The successive init_completion calls should be reinit_completion calls.
>
> patch against 3.19.0-rc1 linux-next
>
> Acked-by: Helge Deller
> Signed-off-by: Nicholas Mc Guire
Applied, thank you.
> ---
>
On 06/22/2014 07:46 AM, Thomas Gleixner wrote:
>> +for (i = 0; i < HRTIMER_MAX_CLOCK_BASES; i++) {
>> +ktime_t expires;
> So this adds the third incarnation of finding the next expiring timer
> to the code. Not really helpful.
>
> Untested patch which addresses the issues below.
This permits to reassign input LEDs to something else than keyboard "leds"
state, by adding a trigger and a led for each input leds, the former being
triggered by EV_LED events, and the latter being by default triggered by the
former. The user can then make the LED use another trigger, including
On Fri, Dec 26, 2014 at 2:57 PM, Dave Jones wrote:
>
> still running though..
Btw, did you ever boot with "tsc=reliable" as a kernel command line option?
For the last night, can you see if you can just run it with that, and
things work? Because by now, my gut feel is that we should start
obd_class_open() ignores error code of try_module_get(),
while it can lead to race with module unload.
Found by Linux Driver Verification project (linuxtesting.org).
Signed-off-by: Alexey Khoroshilov
---
drivers/staging/lustre/lustre/obdclass/linux/linux-module.c | 3 +--
1 file changed, 1
This permits to change which modifier triggers which keyboard LEDs, by adding
modifier triggers, and a series of evled LEDs.
This permits to fix #7063 from userland by using a modifier to implement proper
CapsLock behavior and have the keyboard caps lock led show that modifier state.
Here is v5 coming, with separate patches for the kbd and the input
parts.
Samuel
--
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 http://vger.kernel.org/majordomo-info.html
Please read the FAQ
On Fri, Dec 26, 2014 at 2:57 PM, Dave Jones wrote:
>
> hm.
So with the previous patch that had the false positives, you never saw
this? You saw the false positives instead?
I'm wondering if the added debug noise just ended up helping. Doing a
printk() will automatically cause some scheduler
From: Kalle Valo
Date: Fri, 26 Dec 2014 14:09:42 +0200
> here's my first wireless-drivers pull request after John's "retirement".
> I'll start this with few fixes for 3.19, changelog below.
>
> I used a signed tag to create this pull request, I hope that's ok.
> Please let me know if there are
drivers/iio/imu/kmx61.c:543:1-4: WARNING: end returns can be simpified
drivers/iio/imu/kmx61.c:480:1-4: WARNING: end returns can be simpified if
negative or 0 value
Simplify a trivial if-return sequence. Possibly combine with a
preceding function call.
Generated by:
Jumping between chains doesn't mix well with flush ruleset,
since nft_flush_table doesn't handle chains referencing chains.
This way it will take one to two loops, to settle.
Alternatively it can be solved by always having two loops,
[ 353.373791] [ cut here ]
[
On Fri, Dec 26, 2014 at 12:57:07PM -0800, Linus Torvalds wrote:
> I have a newer version of the patch that gets rid of the false
> positives with some ordering rules instead, and just for you I hacked
> it up to say where the problem happens too, but it's likely too late.
hm.
[
No objection to the addition of -? if you find it useful.
Acked-by: Darren Hart
--
Darren Hart
Intel Open Source Technology Center
On 12/11/14, 12:55 PM, "Olof Johansson" wrote:
>It's usual enough for help text that it makes sense to support it.
>
>Signed-off-by: Olof Johansson
>---
>
New Genius MousePen i608X devices have a new id 0x501a instead of the
old 0x5011 so add a new #define with "_2" appended and change required
places.
The remaining two checkpatch warnings about line length
being over 80 characters are present in the original files too and this
patch was made in
On Fri 2014-12-26 22:45:38, ivo welch wrote:
> I am not a kernel developer, so forgive the intrusion.
Good bug reports are always welcome.
> I suspect I have found either a bug in gdb (less likely) or a bug in
> fanotify (more likely). it is replicable, and the code is almost
> unchanged from
Hello, Nicholas.
On Fri, Dec 26, 2014 at 04:55:59PM -0500, Nicholas Krause wrote:
> Removes a unneed fix me comment for the function,mv_print_info in sata_mv.c.
> This function is correctly completed due to printing out needed info about
> hardware to the kernel log buffer. The needed
From: Nicholas Mc Guire
Date: Tue, 23 Dec 2014 18:47:50 +0100
> The second init_completion call should be a reinit_completion here.
>
> patch is against 3.18.0 linux-next
>
> Signed-off-by: Nicholas Mc Guire
Applied, thanks.
--
To unsubscribe from this list: send the line "unsubscribe
From: Kedareswara rao Appana
Date: Tue, 23 Dec 2014 18:07:55 +0530
> This property is no longer used in the code yet the code looks for it in the
> device tree.
> It does not cause an error if it's not in the tree.
>
> Signed-off-by: Kedareswara rao Appana
Applied, thanks.
--
To unsubscribe
On Fri, Dec 26, 2014 at 04:39:57PM -0500, Nicholas Krause wrote:
> Removes a unneed fix me comment for the function,mv_print_info in sata_mv.c.
> This comment is no longer needed as this function has been completed correctly
> to print out hardware info to the kernel log buffer and therefore this
On Fri, Dec 26, 2014 at 4:26 PM, Jeremiah Mahler wrote:
> If a display supports backlight control using the nouveau driver, and
> also supports standard ACPI backlight control, there will be two sets of
> controls.
>
> /sys/class/backlight/acpi_video0
> /sys/class/backlight/nv_backlight
>
> This
If a display supports backlight control using the nouveau driver, and
also supports standard ACPI backlight control, there will be two sets of
controls.
/sys/class/backlight/acpi_video0
/sys/class/backlight/nv_backlight
This creates ambiguity because these controls can be out of sync with
each
On 26 December 2014 at 19:33, Oscar Forner Martinez
wrote:
> - /* 4706 CC and PMU watchdogs are clocked at 1/4 of
> ALP clock */
> + /* 4706 CC and PMU watchdogs are clocked
> +* at 1/4 of ALP clock
> +*/
On Thu, Dec 18, 2014 at 2:33 AM, Eddie Huang wrote:
> Mediatek UART has highspeed register, but 8250_early.c doesn't
> support this, so add earlycon in 8250_mtk.c
I don't see any highspeed register setup here. More generically,
aren't you just skipping any UART setup? That may be useful on other
From: Johan Hovold
Date: Tue, 23 Dec 2014 12:59:17 +0100
> Use generic config_init callback also for KSZ8021 and KSZ8031.
>
> This has been avoided this far due to commit b838b4aced99 ("phy/micrel:
> KSZ8031RNL RMII clock reconfiguration bug"), which claims that the PHY
> becomes unresponsive
On Fri, Dec 26, 2014 at 12:57:07PM -0800, Linus Torvalds wrote:
> I have a newer version of the patch that gets rid of the false
> positives with some ordering rules instead, and just for you I hacked
> it up to say where the problem happens too, but it's likely too late.
I'll give it a spin
On Wed, Dec 24, 2014 at 02:22:08PM +0200, Kirill A. Shutemov wrote:
> We have remap_file_pages(2) emulation in -mm tree for few release cycles
> and we plan to have it mainline in v3.20. This patchset removes rest of
> VM_NONLINEAR infrastructure.
>
> Patches 1-8 take care about generic code.
Hello, Nick.
On Fri, Dec 26, 2014 at 04:06:11PM -0500, nick wrote:
> I am assuming after reading this function's code, that this function is
> completed and no longer
> needs a fix me comment above it to be completed.
I do appreciate that you're studying the FIXME comments but at this
point I'm
I fixed the merged patch directly.
Changman,
The patch was initially made by you, so let me know, if you have objection.
Thanks,
On Fri, Dec 26, 2014 at 11:17:15AM -0800, Randy Dunlap wrote:
> On 12/26/14 00:30, Stephen Rothwell wrote:
> > Hi all,
> >
> > There will only be intermittent
On Fri, Dec 26, 2014 at 10:12 AM, Dave Jones wrote:
> On Fri, Dec 26, 2014 at 11:34:10AM -0500, Dave Jones wrote:
>
> > One thing I think I'll try is to try and narrow down which
> > syscalls are triggering those "Clocksource hpet had cycles off"
> > messages. I'm still unclear on exactly
On Mon, Dec 22, 2014 at 10:04 PM, nick wrote:
> Greetings Tejuin,Grant and Rob,
> Hope you are having a good holidays. I am wondering if there is
> anything we need to add to this function as stated in a fix me above it.I am
> pretty certain
> there isn't but as the maintainers, I am double
On Fri, Dec 26, 2014 at 2:33 PM, Pavel Machek wrote:
> Hi!
>
>> > We are moving to device tree support on OMAP3, but that currently
>> > breaks ADP1653 driver. This adds device tree support, plus required
>> > documentation.
>> >
>> > Signed-off-by: Pavel Machek
>> >
>> > ---
>> >
>> > Changed
From: Rob Herring
Per Grant, secretlab.ca is defunct and he has no plans to resurect it,
so update the DT website and git tree. devicetree.org needs work, but
is better than "Internal Server Error" that secretlab.ca returns.
Cc: Grant Likely
Signed-off-by: Rob Herring
---
MAINTAINERS | 4
From: Rob Herring
The regex matching on of_get_property and of_match_table cause Grant and
me to be copied on loads of drivers as well as be listed as maintainers
of those drivers. I believe the intent here was to check for documenting
of properties, but that has proven horribly ineffective.
Hi!
> > We are moving to device tree support on OMAP3, but that currently
> > breaks ADP1653 driver. This adds device tree support, plus required
> > documentation.
> >
> > Signed-off-by: Pavel Machek
> >
> > ---
> >
> > Changed -microsec to -us, as requested by devicetree people.
> >
> > Fixed
On Mon, Dec 22, 2014 at 2:50 AM, Paul Bolle wrote:
> Hi Bjorn,
>
Hi Paul
[..]
>
> The Qualcomm RPM regulator driver (see Kconfig symbol
> REGULATOR_QCOM_RPM) was added in v3.18. It depends on the above symbol,
> so it has not yet gotten build coverage. Even manual hacks like
> make -C ../..
Hello Al,
On 12/26/14 2:56 PM, Al Viro wrote:
On Thu, Dec 25, 2014 at 10:50:23PM -0800, Alex Gartrell wrote:
Currently the "is-socket" test for a file compares the ops table pointer,
which is static and local to the socket.c. Instead, this adds a flag for
private_data_is_socket. This is an
On Thu, Dec 25, 2014 at 10:50:23PM -0800, Alex Gartrell wrote:
> Currently the "is-socket" test for a file compares the ops table pointer,
> which is static and local to the socket.c. Instead, this adds a flag for
> private_data_is_socket. This is an exceptionally long commit message for a
>
On Wed, Dec 24, 2014 at 4:11 PM, Murali Karicheri wrote:
> Add of_pci_dma_configure() to allow updating the dma configuration
> of the pci device using the configuration from DT of the parent of
> the root bridge device.
>
> Signed-off-by: Murali Karicheri
> ---
> drivers/of/of_pci.c| 73
On Fri, Dec 26, 2014 at 03:45:25PM +0800, Leon Ma wrote:
> We encountered following panic. The scenario is the process is exiting and
> executing its
> task work. When closing dev node, the driver triggers a firmware reload
> according to device
> status. Because task->fs is set to NULL in
Hello Jason,
Thanks again for your comments.
On 12/26/14 4:45 AM, Jason Wang wrote:
@@ -388,6 +388,7 @@ struct file *sock_alloc_file(struct socket *sock, int
flags, const char *dname)
sock->file = file;
file->f_flags = O_RDWR | (flags & O_NONBLOCK);
file->private_data
On 12/26/14 00:30, Stephen Rothwell wrote:
> Hi all,
>
> There will only be intermittent releases of linux-next between now and
> Jan 5.
>
> Changes since 20141221:
>
on x86_64:
when CONFIG_F2FS_STAT_FS is not enabled:
../fs/f2fs/segment.c: In function 'rewrite_data_page':
Hello Jason,
Thanks for commenting.
On 12/26/14 4:43 AM, Jason Wang wrote:
On 12/26/2014 02:50 PM, Alex Gartrell wrote:
By setting private_data to a socket and private_data_is_socket to true, we
can use the socket syscalls. We also can't just blindly use private_data
anymore, so there's a
On 12/26/14 00:30, Stephen Rothwell wrote:
> Hi all,
>
> There will only be intermittent releases of linux-next between now and
> Jan 5.
>
> Changes since 20141221:
>
on i386:
sound/built-in.o: In function `hsw_pcm_complete':
sst-haswell-pcm.c:(.text+0x139a24): undefined reference to
On Wed, Dec 24, 2014 at 4:34 PM, Pavel Machek wrote:
>
> We are moving to device tree support on OMAP3, but that currently
> breaks ADP1653 driver. This adds device tree support, plus required
> documentation.
>
> Signed-off-by: Pavel Machek
>
> ---
>
> Changed -microsec to -us, as requested by
On 12/26, Damon Swayn wrote:
> Fixed a coding style issue
You need to be more specific here, describe what kind of issue this
patch is fixing. Keep in mind that this message, when formulated
properly, will end up as a comment to the Linux kernel source - it must,
therefore, contain valuable
Hello Ivo,
On 26.12.2014 15:45, ivo welch wrote:
I am not a kernel developer, so forgive the intrusion.
I suspect I have found either a bug in gdb (less likely) or a bug in
fanotify (more likely). it is replicable, and the code is almost
unchanged from the example in the fanotify man page.
Three lines with more than 80 characters per line have been split in several
lines.
Signed-off-by: Oscar Forner Martinez
---
drivers/bcma/driver_chipcommon.c | 11 ---
1 file changed, 8 insertions(+), 3 deletions(-)
diff --git a/drivers/bcma/driver_chipcommon.c
On Fri, Dec 26, 2014 at 11:34:10AM -0500, Dave Jones wrote:
> One thing I think I'll try is to try and narrow down which
> syscalls are triggering those "Clocksource hpet had cycles off"
> messages. I'm still unclear on exactly what is doing
> the stomping on the hpet.
First I ran trinity
Alexander,
On Fri, Dec 26, 2014 at 11:09:53PM +0600, Alexander Kuleshov wrote:
> Hello Jeremiah,
>
> Thank you for feedback. It is my first patches to kernel, so i have a
> some little questions:
>
I recommend checking out Greg Kroah Hartman's presentation on submitting
your first patch. It
On 12/26, Leon Ma wrote:
>
> We encountered following panic. The scenario is the process is exiting and
> executing its
> task work. When closing dev node, the driver triggers a firmware reload
> according to device
> status. Because task->fs is set to NULL in exit_fs(), panic happens.
I think
These two functions use the pointer passed in parameter without any
check. By adding a NULL pointer check, it allows using those functions
from a driver in a more generic way. It is useful especially for the
disable case if the regulator is optional.
Signed-off-by: Gregory CLEMENT
---
This patch adds the device tree version (of_) for each member of the
regulator_get family: normal, exclusive, optional and all of the
manageable version.
The of_regulator_get* functions allow using a device node to get the
regulator instead using the device object. It is needed for the
regulator
Subject: [PATCH 0/2] regulator: Add the device tree version to the
regulator_get family
Hi,
Currently it is not possible to associate a regulator to a child node
which is not a device. The several ports of an ahci controller are
represented as subnodes but they are not created as devices. In
On Fri 2014-12-26 13:34:53, Sebastian Reichel wrote:
> OMAP34xx and OMAP36xx processors contain a register in the syscon area,
> which can be used to determine the SoCs temperature. This patch provides
> a DT based driver for the temperature sensor based on an older driver
> written by Peter De
XTFPGA boards provides an audio subsystem that consists of TI CDCE706
clock synthesizer, I2S transmitter and TLV320AIC23 audio codec.
I2S transmitter has MMIO-based interface that resembles that of the
OpenCores I2S transmitter. I2S transmitter is always a master on I2S
bus. There's no
On Fri 2014-12-26 13:34:52, Sebastian Reichel wrote:
> OMAP34xx and OMAP36xx processors contain a register in the syscon area,
> which can be used to determine the SoCs temperature. This provides a
> DT binding specification for the temperature monitor.
>
> Signed-off-by: Sebastian Reichel
> ---
On 12/25/14 7:26 PM, Namhyung Kim wrote:
diff --git a/tools/perf/util/thread.h b/tools/perf/util/thread.h
index 0b6dcd70bc8b..413f28cf689b 100644
--- a/tools/perf/util/thread.h
+++ b/tools/perf/util/thread.h
@@ -11,10 +11,8 @@
struct thread_stack;
struct thread {
- union {
-
> Jeremiah Mahler :
If you are looking for things to fix I suggest looking in the
drivers/staging directory. There are lots of things that need to be
fixed in there.
Ah sorry, read it incorrectly.
2014-12-26 23:09 GMT+06:00 Alexander Kuleshov :
> Hello Jeremiah,
>
> Thank you for feedback. It
1 - 100 of 440 matches
Mail list logo
