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
---
drivers/input/keyboard/hil_kbd.c |6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/input/ke
From: Fred Chou
Use rt2x00_has_cap_flag macro to check rt2x00dev->cap_flags.
Signed-off-by: Fred Chou
---
drivers/net/wireless/rt2x00/rt2x00config.c | 4 ++--
drivers/net/wireless/rt2x00/rt2x00dev.c | 18 +-
drivers/net/wireless/rt2x00/rt2x00firmware.c | 2 +-
drivers
Hello Bjorn,
I'm running this patch and the corresponding "[PATCH 3/4] PCI: Allow
device quirks to exclude bus reset" patch meanwhile since a month w/
kernel 3.14.x and couldn't find any problem. Would it be possible to
apply these patches to main kernel? Or even to lt-kernel 3.14?
Thanks.
kind
Hi all,
There will only be intermittent releases of linux-next between now and
Jan 5.
Changes since 20141221:
New trees: omap, omap-pending and livepatching
The rcu tree regained a build failure for which I reverted a commit.
Non-merge commits (relative to Linus' tree): 835
853 files changed,
The gpio4 and gpio5 are in 0xf7fc apb which is located in the SM domain.
This patch moves gpio4 and gpio5 to the correct location. This patch also
renames them as the following to match the names we internally used in
marvell:
gpio4 -> sm_gpio1
gpio5 -> sm_gpio0
porte ->
This patch adds the pmu node, enabling the PMU unit on Marvell BG2Q and
BG2CD SoCs.
Signed-off-by: Jisheng Zhang
---
arch/arm/boot/dts/berlin2cd.dtsi | 5 +
arch/arm/boot/dts/berlin2q.dtsi | 8
2 files changed, 13 insertions(+)
diff --git a/arch/arm/boot/dts/berlin2cd.dtsi b/arch/
These patches try to improve dts for berlin. One of them enables PMU support
to BG2Q and BG2CD SoCs. One of them adds the missing PPI cpu mask to twd timer
interrupts. The last one corrects the SM GPIOs' location for BG2Q SoC.
Changes since v1:
- Adds some text to the log of the second commit
-
According to the gic binding document, "bits[15:8] PPI interrupt cpu
mask. Each bit corresponds to each of the 8 possible cpus attached to
the GIC. A bit set to '1' indicated the interrupt is wired to that
CPU." This patch wants to add the PPI cpu mask for completeness.
Signed-off-by: Jisheng Zh
Hi,
This driver implements the reset controller for MediaTek SoC.
It adds support for MT8135 and MT8173 SoC in the patch set.
The reset controller uses syscon as its regmap and adopts syscon RFC in
https://lkml.org/lkml/2014/11/3/134.
This driver is based on 3.19-rc1.
Changes since v3
==
Add a driver in reset controller.
Signed-off-by: Flora Fu
---
drivers/reset/Makefile | 1 +
drivers/reset/reset-mtk.c | 130 +
.../dt-bindings/reset-controller/mt8135-resets.h | 64 ++
.../dt-bindings/reset-con
Add device tree bindings.
Acked-by: Philipp Zabel
Signed-off-by: Flora Fu
---
.../devicetree/bindings/reset/mediatek,reset.txt | 52 ++
1 file changed, 52 insertions(+)
create mode 100644 Documentation/devicetree/bindings/reset/mediatek,reset.txt
diff --git a/Documentati
Add reset controller to MT8135.dtsi.
Acked-by: Philipp Zabel
Signed-off-by: Flora Fu
---
arch/arm/boot/dts/mt8135.dtsi | 29 +
1 file changed, 29 insertions(+)
diff --git a/arch/arm/boot/dts/mt8135.dtsi b/arch/arm/boot/dts/mt8135.dtsi
index ec83e69..989e488 100644
-
This patch add a new quirk to add a s/w timer to notify the driver
to terminate current transfer and report a data timeout to the core,
if DTO interrupt does NOT come within the given time.
dw_mmc call mmc_request_done func to finish transfer depends on
DTO interrupt. If DTO interrupt does not com
Hi Thierry,
On Thursday 25 December 2014 14:20:59 Thierry Reding wrote:
> On Mon, Dec 22, 2014 at 01:07:13PM +0200, Oded Gabbay wrote:
> > This small patch-set, was created to solve the bug described at
> > https://bugzilla.kernel.org/show_bug.cgi?id=89661 (Kernel panic when
> > trying use amdkfd
On 24 December 2014 at 08:20, Kalle Valo wrote:
> Oscar Forner Martinez writes:
>
>> 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 | 10 +++---
>> 1 file changed,
Hi, Boris
On 12/5/2014 6:30 AM, Boris Brezillon wrote:
mtd: nand: atmel: Update DT documentation after splitting NFC and NAND
The NAND and NFC (NAND Flash Controller) were linked together with a
parent <-> child relationship.
This model has several drawbacks:
- it does not allow for multiple N
Hi, Boris
Thanks for the patch.
You need to rebase on the top of current mtd-l2 git tree. As I had some
change on the binding document.
Best Regards,
Josh Wu
On 12/5/2014 6:30 AM, Boris Brezillon wrote:
The NAND and NFC (NAND Flash Controller) were linked together with a
parent <-> child re
Hi All,
I encountered the following crash in 3.10.24.
The panic log is as following.
The strange thing is that the nr_running change to NULL after pass the
check in the beginning of pick_next_task_fair.
So it seems there are race condition in the code.
Seems no related patch to fix it in the mainl
Hi experts,
The existing driver has compatibility issues with my devices, and
there're other devices depend on the old driver.
I want to replace the existing I2C driver with my own driver while not
affect the other I2C devices.
How can I do it?
Thanks.
BRs.
Nick Yao
--
To unsubscribe from th
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 __tun_file_get function that returns the container_of
> private_data appropr
Hi Philipp,
Thank you for the patch.
On Tuesday 23 December 2014 14:09:16 Philipp Zabel wrote:
> Decrementing the reference count of the previous endpoint node allows to
> use the of_graph_get_next_endpoint function in a for_each_... style macro.
> All current users of this function that pass a n
Hi, Boris
On 12/5/2014 6:30 AM, Boris Brezillon wrote:
sama5d3 and sama5d4 SoCs provides several CS to interface with external
memories, and in particular NAND chips.
The NAND flash controller embedded in the these SoCs can connect to any of
the available CS (each CS is assigned a memory range,
On 12/26/2014 02:50 PM, 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
> two-line patch.
>
> S
3.19-rc1 contains Joe's MT8135 & MT8127 basic support and sysirq driver patch.
But still can not boot to shell due to lack UART device node in device tree.
This patch enables MTK UART driver in multi_v7_defconfig and UART device node.
This patch base on 3.19-rc1, and Joe's sysirq dts patch [1]
[1
Add mediatek SoC UART support in multi_v7_defconfig
Signed-off-by: Eddie Huang
---
arch/arm/configs/multi_v7_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/configs/multi_v7_defconfig
b/arch/arm/configs/multi_v7_defconfig
index 2328fe7..fd0ff95 100644
--- a/arch/arm/confi
This add dts support for mt8127 and mt8135 SoC UART
Signed-off-by: Eddie Huang
---
arch/arm/boot/dts/mt8127.dtsi | 34 ++
arch/arm/boot/dts/mt8135.dtsi | 34 ++
2 files changed, 68 insertions(+)
diff --git a/arch/arm/boot/dts/mt812
On 23/12/14 13:22, Daniel Baluta wrote:
> This is a series of cleanups after Hartmut's review:
>
> * http://marc.info/?l=linux-iio&m=141859700810393&w=2
> * http://marc.info/?l=linux-iio&m=141859774010580&w=2
> * http://marc.info/?l=linux-iio&m=141859828910703&w=2
> * http:
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
>> ---
>> drivers/staging/iio/accel/adis16203.h | 41
>> ++-
>> 1 file changed, 31 insert
On 12/26/2014 10:53 AM, Jason Wang wrote:
> This patch try to reduce the number of MSIX irqs required for
> virtio-net by sharing a MSIX irq for each TX/RX queue pair through
> channels. If transport support channel, about half of the MSIX irqs
> were reduced.
>
> Cc: Rusty Russell
> Cc: Michael
Signed-off-by: Pavel Machek
diff --git a/drivers/hwmon/Kconfig b/drivers/hwmon/Kconfig
index 6529c09..9007ca9 100644
--- a/drivers/hwmon/Kconfig
+++ b/drivers/hwmon/Kconfig
@@ -28,6 +28,10 @@ config HWMON_VID
tristate
default n
+config SENSORS_OMAP34XX
+ bool "TI OMAP34xx
On 21/12/14 12:42, Mohammad Jamal wrote:
> This patch solves the space before , coding style issue found by
> checkpatch in ade7759.c
>
> Signed-off-by: Mohammad Jamal
Fixed by Zachery Warren back in November. I'm a bit behind with
sending stuff upstream so won't have hit anything other than the
On 21/12/14 12:35, Mohammad Jamal wrote:
> This patch solves the space before , error of the checkpatch.pl
>
> Signed-off-by: Mohammad Jamal
Also fixed in that earlier patch from Zachery.
> ---
> drivers/staging/iio/adc/ad7192.c |2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> dif
Hello Sebastian,
On Thu, Dec 25, 2014 at 02:08:12PM +0100, Sebastian Hesselbarth wrote:
> On 22.12.2014 13:57, Evgeni Dobrev wrote:
> >This patch adds support for Seagate BlackArmor NAS220.
> >
> >The Seagate BlackArmor NAS 220 is a NAS system based on Marvell 88f6192. It
> >has
> >32MB NAND and
On 18/12/14 16:51, Lars-Peter Clausen wrote:
> Adding V4L folks to Cc for more input.
Thanks Lars - we definitely would need the v4l guys to agree to a driver like
this going in IIO. (not that I'm convinced it should!)
>
> On 12/08/2014 03:10 PM, Baluta, Teodora wrote:
>> Hello,
>>
>> On Vi, 2014-
At Thu, 25 Dec 2014 11:48:37 +0100,
Alexandre Belloni wrote:
>
> Hi,
>
> On 25/12/2014 at 11:19:04 +0100, Takashi Iwai wrote :
> > At Sun, 21 Dec 2014 12:18:09 +0100,
> > Alexandre Belloni wrote:
> > >
> > > From: Arnd Bergmann
> > >
> > > at91 will no longer export the mach/cpu.h and mach/har
Fixed a coding style issue
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 6aa0d46..5d87934 100644
--- a/drivers/staging/line6/pcm.h
+++ b/drivers/
On 19/12/14 17:39, Karol Wrona wrote:
> indio_dev was unused in function body plus some small style fix - add new
> lines after "if(sth) return sth" and before the last return statement.
>
> The argument was removed also in its client.
>
> Signed-off-by: Karol Wrona
Good cleanup - some fuzz appl
On 19/12/14 17:39, Karol Wrona wrote:
> iio kfifo allocate/free gained their devm_ wrappers.
>
> Signed-off-by: Karol Wrona
> Suggested-by: Jonathan Cameron
Applied to the togreg branch of iio.git.
One addition - added to the list of devm functions in
Documentation/device-model/devres.txt
> -
On 19/12/14 17:39, Karol Wrona wrote:
> This comment did not fit here. It explains why devm_kmalloc
> uses dr_alloc. Generally is not needed at all.
>
A classic bit of cut and paste I guess. Anyhow, applied.
Jonathan
> Signed-off-by: Karol Wrona
> ---
> drivers/iio/industrialio-core.c |1
On 15/12/14 11:39, Nikolaus Schulz wrote:
> The TI DAC8554 is a quad-channel Digital-to-Analog Converter with an SPI
> interface.
>
> Changes in v3:
> * Small fixes in the documentation of struct dac8554_state
> * Replace some magic constants with macros
> * Replace memset on powerdown state array
This patch subtract sharedram from cached,
sharedram can only be swap into swap partitions,
they should be treated as swap pages, not as cached pages.
Signed-off-by: Yalin Wang
---
fs/proc/meminfo.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/proc/meminfo.c b/fs/proc/m
Hi Linus,
please pull one patch for the parisc architecture for kernel 3.19 from
git://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux.git
parisc-3.19-1
This patch unbreaks the kernel compilation on parisc with gcc-4.9.
Thanks,
Helge
Hi,
I creating Debian/Ubuntu packages using builddeb script ('make deb-pkg').
While I was doing a 'make distclean' and grep-ed for some patterns I
saw that my debian/*tmp dirs were not deleted.
$ ls debian/*tmp
debian/fwtmp:
DEBIAN lib usr
debian/hdrtmp:
DEBIAN lib usr
debian/headertmp:
DE
Hi Dave,
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 any problems.
Kalle
The following changes since commit
heap_end_ptr default value defined as _end+STACK_SZE-512, but
STACK_SIZE is already 512.
Signed-off-by: Alexander Kuleshov
---
arch/x86/boot/header.S | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/boot/header.S b/arch/x86/boot/header.S
index 16ef025..c69b870 100644
On 16/12/14 10:17, Karol Wrona wrote:
> On 12/06/2014 03:09 PM, Jonathan Cameron wrote:
>> On 05/12/14 19:54, Karol Wrona wrote:
>>> Sensorhub is MCU dedicated to collect data and manage several sensors.
>>> Sensorhub is a spi device which provides a layer for IIO devices. It
>>> provides
>>> som
On 16/12/14 07:30, Karol Wrona wrote:
> On 12/06/2014 03:29 PM, Jonathan Cameron wrote:
>> On 05/12/14 19:54, Karol Wrona wrote:
>>> Add sensorhub bindings for sensorhub on Galaxy Gear 2.
>>>
>>> Change-Id: I4ee25aef33c21a4662de230841de9a8684f2c26b
>>> Signed-off-by: Karol Wrona
>>> Acked-by: Kyun
On 08/12/14 10:41, Karol Wrona wrote:
> On 12/06/2014 03:52 PM, Jonathan Cameron wrote:
>> On 05/12/14 19:54, Karol Wrona wrote:
>>> This patch adds accelerometer iio driver which uses sensorhub as data
>>> provider.
>>>
>>> Change-Id: I4686741b7401ec5cbf4b5d0f2a5cc146fbe24d53
>>> Signed-off-by: Ka
Hi,
I've prepared an updated variant of the omap34xx temperature monitor driver.
It's based on the N9 driver instead of the N900 driver (and thus has omap36xx
support).
The differences compared to the original driver are:
* DT based
* No includes from arch, instead uses syscon DT node + regmap
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
---
.../bindings/hwmon/omap3-temperature.txt | 25
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 Schrijver for the Nokia N900 and N9.
Signed-off-by: Sebastian R
OMAP34xx and OMAP36xx processors contain a register in the
syscon area, which can be used to determine the SoCs temperature.
Signed-off-by: Sebastian Reichel
---
arch/arm/boot/dts/omap34xx.dtsi | 7 +++
arch/arm/boot/dts/omap36xx.dtsi | 7 +++
2 files changed, 14 insertions(+)
diff --gi
Signed-off-by: Alexander Kuleshov
---
arch/x86/boot/header.S | 15 ++-
1 file changed, 10 insertions(+), 5 deletions(-)
diff --git a/arch/x86/boot/header.S b/arch/x86/boot/header.S
index 16ef025..75f016b 100644
--- a/arch/x86/boot/header.S
+++ b/arch/x86/boot/header.S
@@ -211,7 +211,
On 20/12/14 14:53, Rickard Strandqvist wrote:
> Remove the function sca3000_check_status() that is not used anywhere.
>
> This was partially found by using a static code analysis program called
> cppcheck.
>
> Signed-off-by: Rickard Strandqvist
Applied to the togreg branch of iio.git - initiall
On Fri, Dec 26, 2014 at 1:02 PM, Sedat Dilek wrote:
[...]
>
> Any other make (PHONY) target I don't know?
>
I fell over "clean-dirs"...
scripts/package/Makefile:93:clean-dirs += $(objtree)/debian/
...but did not really understood how it works.
The main Makefile defines some clean-dirs PHONY#s.
Currently the underlay of zpool: zsmalloc/zbud, do not know
who creates them. There is not a method to let zsmalloc/zbud
find which caller they belogs to.
Now we want to add statistics collection in zsmalloc. We need
to name the debugfs dir for each pool created. The way suggested
by Minchan Kim i
Keeping fragmentation of zsmalloc in a low level is our target. But now
we still need to add the debug code in zsmalloc to get the quantitative data.
This patch adds a new configuration CONFIG_ZSMALLOC_STAT to enable the
statistics collection for developers. Currently only the objects statatitics
On Wed, Dec 24, 2014 at 05:18:15PM +, Catalin Marinas wrote:
> On Fri, Oct 17, 2014 at 02:37:14PM +0100, Hanjun Guo wrote:
> > +ACPI drivers should only look at one specific ASL object -- the _DSD object
> > +-- for device driver parameters (known in DT as "bindings", or "Device
> > +Propertie
On 19/12/14 22:57, Irina Tirdea wrote:
> Some devices compute the number of calories that the user has
> burnt since the last reset.
>
> One of this devices is Freescale's MMA9553L
> (http://www.freescale.com/files/sensors/doc/ref_manual/MMA9553LSWRM.pdf)
> that computes the number of calories bas
From: Arnd Bergmann
at91 will no longer export the mach/cpu.h and mach/hardware.h header files
in the future, which would break building the atmel ac97c driver.
Since the cpu_is_* check is only used to find out whether we are running
on avr32 or arm/at91, we can hardcode that check in the ARM ca
On 19/12/14 22:57, Irina Tirdea wrote:
> Some devices export the current speed value of the user.
>
> One of this devices is Freescale's MMA9553L
> (http://www.freescale.com/files/sensors/doc/ref_manual/MMA9553LSWRM.pdf)
> that computes the speed of the user based on the number of steps and
> stri
On 19/12/14 22:57, Irina Tirdea wrote:
> Some devices need the gender of the user to compute various
> parameters. One of this devices is Freescale's MMA9553L
> (http://www.freescale.com/files/sensors/doc/ref_manual/MMA9553LSWRM.pdf)
> that needs the gender of the user to compute distance, speed an
On 19/12/14 22:57, Irina Tirdea wrote:
> Some devices need the weight of the user to compute other
> parameters. One of this devices is Freescale's MMA9553L
> (http://www.freescale.com/files/sensors/doc/ref_manual/MMA9553LSWRM.pdf)
> that needs the weight of the user to compute the number of calori
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 processed and reported using multiple threads.
>
> Signed-off-by: Namhyung
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 look and play with it. Any comments are welcome! :)
very nice a
Alexander,
On Fri, Dec 26, 2014 at 06:38:59PM +0600, Alexander Kuleshov wrote:
Your description needs to be more specific than just "coding style
fixes". What type of problems did you fix? How did you find them?
(more inline...)
> Signed-off-by: Alexander Kuleshov
> ---
> arch/x86/boot/head
Alexander,
On Fri, Dec 26, 2014 at 06:22:42PM +0600, Alexander Kuleshov wrote:
> heap_end_ptr default value defined as _end+STACK_SZE-512, but
STACK_SIZE
> STACK_SIZE is already 512.
>
> Signed-off-by: Alexander Kuleshov
> ---
> arch/x86/boot/header
Add a function seq_print_stack_trace() which prints stacktraces to seq_files.
Signed-off-by: Stefan I. Strogin
---
include/linux/stacktrace.h | 4
kernel/stacktrace.c| 17 +
2 files changed, 21 insertions(+)
diff --git a/include/linux/stacktrace.h b/include/linux/s
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 ++
mm/cma.c| 34 +
Hello all,
Here is a patch set that adds /proc/cmainfo.
When compiled with CONFIG_CMA_DEBUG /proc/cmainfo will contain information
about about total, used, maximum free contiguous chunk and all currently
allocated contiguous buffers in CMA regions. The information about allocated
CMA buffers incl
/proc/cmainfo contains a list of currently allocated CMA buffers for every
CMA area when CONFIG_CMA_DEBUG is enabled.
Format is:
- ( kB), allocated by \
(), latency us
Signed-off-by: Stefan I. Strogin
---
mm/cma.c | 202 +
Convert a call to init_timer and accompanying intializations of
the timer's data and function fields to a call to setup_timer.
A simplified version of the semantic match that fixes this problem is as
follows: (http://coccinelle.lip6.fr/)
//
@@
expression t,f,d;
@@
-init_timer(&t);
+setup_timer(
Convert a call to init_timer and accompanying intializations of
the timer's data and function fields to a call to setup_timer.
A simplified version of the semantic match that fixes this problem is as
follows: (http://coccinelle.lip6.fr/)
//
@@
expression t,f,d;
@@
-init_timer(&t);
+setup_timer(
Convert a call to init_timer and accompanying intializations of
the timer's data and function fields to a call to setup_timer.
A simplified version of the semantic match that fixes this problem is as
follows: (http://coccinelle.lip6.fr/)
//
@@
expression t,f,d;
@@
-init_timer(&t);
+setup_timer(
Convert a call to init_timer and accompanying intializations of
the timer's data and function fields to a call to setup_timer.
A simplified version of the semantic match that fixes this problem is as
follows: (http://coccinelle.lip6.fr/)
//
@@
expression t,f,d;
@@
-init_timer(&t);
+setup_timer(
Convert a call to init_timer and accompanying intializations of
the timer's data and function fields to a call to setup_timer.
A simplified version of the semantic match that fixes this problem is as
follows: (http://coccinelle.lip6.fr/)
//
@@
expression t,f,d;
@@
-init_timer(&t);
+setup_timer(
Convert a call to init_timer and accompanying intializations of
the timer's data and function fields to a call to setup_timer.
A simplified version of the semantic match that fixes this problem is as
follows: (http://coccinelle.lip6.fr/)
//
@@
expression t,f,d;
@@
-init_timer(&t);
+setup_timer(
Convert a call to init_timer and accompanying intializations of
the timer's data and function fields to a call to setup_timer.
A simplified version of the semantic match that fixes this problem is as
follows: (http://coccinelle.lip6.fr/)
//
@@
expression t,f,d;
@@
-init_timer(&t);
+setup_timer(
Convert a call to init_timer and accompanying intializations of
the timer's data and function fields to a call to setup_timer.
A simplified version of the semantic match that fixes this problem is as
follows: (http://coccinelle.lip6.fr/)
//
@@
expression t,f,d;
@@
-init_timer(&t);
+setup_timer(
Convert a call to init_timer and accompanying intializations of
the timer's data and function fields to a call to setup_timer.
A simplified version of the semantic match that fixes this problem is as
follows: (http://coccinelle.lip6.fr/)
//
@@
expression t,f,d;
@@
-init_timer(&t);
+setup_timer(
Convert a call to init_timer and accompanying intializations of
the timer's data and function fields to a call to setup_timer.
A simplified version of the semantic match that fixes this problem is as
follows: (http://coccinelle.lip6.fr/)
//
@@
expression t,f,d;
@@
-init_timer(&t);
+setup_timer(
Convert a call to init_timer and accompanying intializations of
the timer's data and function fields to a call to setup_timer.
A simplified version of the semantic match that fixes this problem is as
follows: (http://coccinelle.lip6.fr/)
//
@@
expression t,f,d;
@@
-init_timer(&t);
+setup_timer(
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. to trigger it,
all an su needs to do is to step throug
Convert a call to init_timer and accompanying intializations of
the timer's data and function fields to a call to setup_timer.
A simplified version of the semantic match that fixes this problem is as
follows: (http://coccinelle.lip6.fr/)
//
@@
expression t,f,d;
@@
-init_timer(&t);
+setup_timer(
Convert a call to init_timer and accompanying intializations of
the timer's data and function fields to a call to setup_timer.
A simplified version of the semantic match that fixes this problem is as
follows: (http://coccinelle.lip6.fr/)
//
@@
expression t,f,d;
@@
-init_timer(&t);
+setup_timer(
Convert a call to init_timer and accompanying intializations of
the timer's data and function fields to a call to setup_timer.
A simplified version of the semantic match that fixes this problem is as
follows: (http://coccinelle.lip6.fr/)
//
@@
expression t,f,d;
@@
-init_timer(&t);
+setup_timer(
Convert a call to init_timer and accompanying intializations of
the timer's data and function fields to a call to setup_timer.
A simplified version of the semantic match that fixes this problem is as
follows: (http://coccinelle.lip6.fr/)
//
@@
expression t,f,d;
@@
-init_timer(&t);
+setup_timer(
Convert a call to init_timer and accompanying intializations of
the timer's data and function fields to a call to setup_timer.
A simplified version of the semantic match that fixes this problem is as
follows: (http://coccinelle.lip6.fr/)
//
@@
expression t,f,d;
@@
-init_timer(&t);
+setup_timer(
Convert a call to init_timer and accompanying intializations of
the timer's data and function fields to a call to setup_timer.
A simplified version of the semantic match that fixes this problem is as
follows: (http://coccinelle.lip6.fr/)
//
@@
expression t,f,d;
@@
-init_timer(&t);
+setup_timer(
Convert a call to init_timer and accompanying intializations of
the timer's data and function fields to a call to setup_timer.
A simplified version of the semantic match that fixes this problem is as
follows: (http://coccinelle.lip6.fr/)
//
@@
expression t,f,d;
@@
-init_timer(&t);
+setup_timer(
Convert a call to init_timer and accompanying intializations of
the timer's data and function fields to a call to setup_timer.
A simplified version of the semantic match that fixes this problem is as
follows: (http://coccinelle.lip6.fr/)
//
@@
expression t,f,d;
@@
-init_timer(&t);
+setup_timer(
Convert a call to init_timer and accompanying intializations of
the timer's data and function fields to a call to setup_timer.
A simplified version of the semantic match that fixes this problem is as
follows: (http://coccinelle.lip6.fr/)
//
@@
expression t,f,d;
@@
-init_timer(&t);
+setup_timer(
Convert a call to init_timer and accompanying intializations of
the timer's data and function fields to a call to setup_timer.
A simplified version of the semantic match that fixes this problem is as
follows: (http://coccinelle.lip6.fr/)
//
@@
expression t,f,d;
@@
-init_timer(&t);
+setup_timer(
Convert a call to init_timer and accompanying intializations of
the timer's data and function fields to a call to setup_timer.
A simplified version of the semantic match that fixes this problem is as
follows: (http://coccinelle.lip6.fr/)
//
@@
expression t,f,d;
@@
-init_timer(&t);
+setup_timer(
Convert a call to init_timer and accompanying intializations of
the timer's data and function fields to a call to setup_timer.
A simplified version of the semantic match that fixes this problem is as
follows: (http://coccinelle.lip6.fr/)
//
@@
expression t,f,d;
@@
-init_timer(&t);
+setup_timer(
On Wednesday, December 24, 2014 07:51:48 PM Pali Rohár wrote:
>
> --nextPart5943893.pKyMBm5Emp
> Content-Type: Text/Plain;
> charset="utf-8"
> Content-Transfer-Encoding: quoted-printable
>
> Hello!
>
> With new 3.19-rc1 kernel every time when I open LID on my laptop, kernel pr=
> ints these er
These patches group a call to init_timer and initialization of the function
and data fields into a call to setup_timer. Is there is no initialization
of the data field before add_timer is called, the the data value is set to
0UL. If the data value has a cast to something other than unsigned long,
Convert a call to init_timer and accompanying intializations of
the timer's data and function fields to a call to setup_timer.
A simplified version of the semantic match that fixes this problem is as
follows: (http://coccinelle.lip6.fr/)
//
@@
expression t,f,d;
@@
-init_timer(&t);
+setup_timer(
Convert a call to init_timer and accompanying intializations of
the timer's data and function fields to a call to setup_timer.
A simplified version of the semantic match that fixes this problem is as
follows: (http://coccinelle.lip6.fr/)
//
@@
expression t,f,d;
@@
-t.function = f;
-t.data = d;
Convert a call to init_timer and accompanying intializations of
the timer's data and function fields to a call to setup_timer.
A simplified version of the semantic match that fixes this problem is as
follows: (http://coccinelle.lip6.fr/)
//
@@
expression t,f,d;
@@
-init_timer(&t);
+setup_timer(
1 - 100 of 220 matches
Mail list logo
