On Thu, Jan 1, 2015 at 10:23 PM, Sedat Dilek wrote:
> [ CC libaio Debian/Ubuntu maintainer ]
>
> Hi Jeff,
>
> I am playing with fio (manually compiled v2.2.3) and wanted to update
> also my libaio development package on Ubuntu/precise.
>
> Both dsc (description) files of Debian and Ubuntu libaio s
This is a patch to fix a space error found by the checkpatch.pl in
file gdm_mux.c.
Signed-off-by: Ning Zhou
---
drivers/staging/gdm724x/gdm_mux.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/gdm724x/gdm_mux.c
b/drivers/staging/gdm724x/gdm_mux.c
index b5b06
Hi Jaegeuk,
> -Original Message-
> From: Jaegeuk Kim [mailto:jaeg...@kernel.org]
> Sent: Wednesday, December 31, 2014 4:26 PM
> To: Chao Yu
> Cc: 'Changman Lee'; linux-f2fs-de...@lists.sourceforge.net;
> linux-kernel@vger.kernel.org
> Subject: Re: [RFC PATCH] f2fs: add extent cache base o
On 12/28/2014 03:52 PM, Michael S. Tsirkin wrote:
> On Fri, Dec 26, 2014 at 10:53:42AM +0800, Jason Wang wrote:
>> Hi all:
>>
>> This series try to share MSIX irq for each tx/rx queue pair. This is
>> done through:
>>
>> - introducing virtio pci channel which are group of virtqueues that
>> shar
On Sun, Jan 4, 2015 at 4:21 PM, Sedat Dilek wrote:
> I have also seen... with outdated material?
>
we can use syscall.h and aio_abi.h directly.
IMHO, I think libaio is of little value. It's just simple wrappers of
aio syscall and some useful macros. It will useful only when it
implement posix ai
Hi!
> Thanks for the patch! A few comments below.
>
> On Wed, Dec 24, 2014 at 11:34:34PM +0100, 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
This is a patch to fix "WARNING: line over 80 characters" found by
checkpatch.pl in gdm_lte.c.
Signed-off-by: Ning Zhou
---
drivers/staging/gdm724x/gdm_lte.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/staging/gdm724x/gdm_lte.c
b/drivers/staging/gdm724x/gdm_lte
On Tue, 2014-12-30 at 13:54 -0500, Pranith Kumar wrote:
> On Tue, Dec 30, 2014 at 1:50 PM, Peter Zijlstra wrote:
> > On Tue, Dec 30, 2014 at 12:46:22AM -0500, Pranith Kumar wrote:
> >> Isolate the SRCU functions and data structures within CONFIG_SRCU so that
> >> there
> >> is a compile time fail
On 2014年12月25日 01:18, Catalin Marinas wrote:
[...]
In addition to the above and _DSD requirements/banning, I would also add
some clear statements around:
_OSC: only global/published capabilities are allowed. For
device-specific _OSC we need a process or maybe we can ban them entirely
and rely o
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
---
Please apply,
Pavel
diff --git a/Documentation/devicetre
On Sun, Jan 4, 2015 at 9:55 AM, Dongsheng Song wrote:
> On Sun, Jan 4, 2015 at 4:21 PM, Sedat Dilek wrote:
>> I have also seen... with outdated material?
>>
>
> we can use syscall.h and aio_abi.h directly.
>
> IMHO, I think libaio is of little value. It's just simple wrappers of
> aio syscall and
Hi!
> > > +Optional child node:
> > > +- a platform device listed as a child node will be probed and
> > > + powered-on whenever the tty is in use (open).
> > > +
> > > Example:
> > >
> > > uart@8023 {
> >
> But some line disciplines don't really want the char_dev.
> N_MOUSE wants a se
On 01/01/15 13:45, Hartmut Knaack wrote:
> Daniel Baluta schrieb am 23.12.2014 um 14:22:
>> Signed-off-by: Daniel Baluta
> Reviewed-by: Hartmut Knaack
Applied to the togreg branch of iio.git - initially pushed out as testing
for the autobuilders to play.
>> ---
>> drivers/iio/imu/kmx61.c | 2 ++
On 01/01/15 13:45, Hartmut Knaack wrote:
> Daniel Baluta schrieb am 23.12.2014 um 14:22:
>> ..except while in an error handler, where there is nothing
>> to be done anyway.
>>
>> Signed-off-by: Daniel Baluta
> Reviewed-by: Hartmut Knaack
Applied
>> ---
>> drivers/iio/imu/kmx61.c | 11 +--
On 01/01/15 13:47, Hartmut Knaack wrote:
> Daniel Baluta schrieb am 23.12.2014 um 14:22:
>> This fixes parts of kmx61 error handling to make code easier to read and to
>> be
>> more consistent with IIO coding conventions:
>> * prefer as single point for error handling instead of duplicating c
On 01/01/15 13:47, Hartmut Knaack wrote:
> Daniel Baluta schrieb am 23.12.2014 um 14:22:
>> Signed-off-by: Daniel Baluta
> Acked-by: Hartmut Knaack
Applied.
>> ---
>> drivers/iio/imu/kmx61.c | 18 +-
>> 1 file changed, 9 insertions(+), 9 deletions(-)
>>
>> diff --git a/drivers/ii
On 01/01/15 13:50, Hartmut Knaack wrote:
> Daniel Baluta schrieb am 23.12.2014 um 14:22:
>> Signed-off-by: Daniel Baluta
> Acked-by: Hartmut Knaack
Applied
>> ---
>> drivers/iio/imu/kmx61.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/iio/imu/kmx61.c b/driv
On 01/01/15 13:51, Hartmut Knaack wrote:
> Daniel Baluta schrieb am 23.12.2014 um 14:22:
>> Signed-off-by: Daniel Baluta
> Acked-by: Hartmut Knaack
Applied
>> ---
>> drivers/iio/imu/kmx61.c | 3 +--
>> 1 file changed, 1 insertion(+), 2 deletions(-)
>>
>> diff --git a/drivers/iio/imu/kmx61.c b/dr
From: Borislav Petkov
It is superfluous now so remove it. No object file change before and
after.
Signed-off-by: Borislav Petkov
---
arch/x86/lib/copy_user_64.S | 5 -
1 file changed, 5 deletions(-)
diff --git a/arch/x86/lib/copy_user_64.S b/arch/x86/lib/copy_user_64.S
index dee945d55594.
On Fri, Jan 02, 2015 at 03:41:02PM +, James Hogan wrote:
> Hi,
>
> On 25/12/14 09:29, Michael S. Tsirkin wrote:
> > virtio wants to read bitwise types from userspace using get_user. At the
> > moment this triggers sparse errors, since the value is passed through an
> > integer.
> >
> > Fix t
On 01/01/15 13:51, Hartmut Knaack wrote:
> Daniel Baluta schrieb am 23.12.2014 um 14:22:
>> Useful in the debugging phase, not needed now.
>>
>> Signed-off-by: Daniel Baluta
> Acked-by: Hartmut Knaack
Applied.
>> ---
>> drivers/iio/imu/kmx61.c | 2 --
>> 1 file changed, 2 deletions(-)
>>
>> diff
From: Hanjun Guo
apic_id in MADT table is the CPU hardware id which identify
it self in the system for x86 and ia64, OSPM will use it for
SMP init to map APIC ID to logical cpu number in the early
boot, when the DSDT/SSDT (ACPI namespace) is scanned later, the
ACPI processor driver is probed and
From: Hanjun Guo
acpi_map_lsapic() will allocate a logical CPU number and map it to
physical CPU id (such as APIC id) for the hot-added CPU, it will also
do some mapping for NUMA node id and etc, acpi_unmap_lsapic() will
do the reverse.
We can see that the name of the function is a little bit co
On 01/01/15 13:53, Hartmut Knaack wrote:
> Daniel Baluta schrieb am 23.12.2014 um 14:22:
>> odr_bits values are between 0 and 11, so we can use the index
>> in kmx61_samp_freq_table instead of odr_bits structure member.
> Basically looking good, but I would feel more comfortable to check
> against
Introduce ACPI_IRQ_MODEL_GIC which is needed for ARM64 as GIC is
used, and then register device's gsi with the core IRQ subsystem.
acpi_register_gsi() is similar to DT based irq_of_parse_and_map(),
since gsi is unique in the system, so use hwirq number directly
for the mapping.
Originally-by: Ami
From: Graeme Gregory
ACPI 5.1 does not currently support S states for ARM64 hardware but
ACPI code will call acpi_target_system_state() for device power
managment, so introduce sleep-arm.c to allow other drivers to function
until S states are defined.
Tested-by: Suravee Suthikulpanit
Signed-off
From: Tomasz Nowicki
ACPI kernel uses MADT table for proper GIC initialization. It needs to
parse GIC related subtables, collect CPU interface and distributor
addresses and call driver initialization function (which is hardware
abstraction agnostic). In a similar way, FDT initialize GICv1/2.
NOT
MADT contains the information for MPIDR which is essential for
SMP initialization, parse the GIC cpu interface structures to
get the MPIDR value and map it to cpu_logical_map(), and add
enabled cpu with valid MPIDR into cpu_possible_map.
ACPI 5.1 only has two explicit methods to boot up SMP, PSCI
From: Al Stone
As we want to get ACPI tables to parse and then use the information
for system initialization, we should get the RSDP (Root System
Description Pointer) first, it then locates Extended Root Description
Table (XSDT) which contains all the 64-bit physical address that
pointer to other
Introduce a new function map_gicc_mpidr() to allow MPIDRs to be obtained
from the GICC Structure introduced by ACPI 5.1.
MPIDR is the CPU hardware ID as local APIC ID on x86 platform, so we use
MPIDR not the GIC CPU interface ID to identify CPUs.
Tested-by: Suravee Suthikulpanit
Signed-off-by: H
From: Al Stone
Introduce one early parameters "off" and "force" for "acpi", acpi=off
will be the default behavior for ARM64, so introduce acpi=force to
enable ACPI on ARM64.
Disable ACPI before early parameters parsed, and enable it to pass
"acpi=force" if people want use ACPI on ARM64. This ens
When MADT is parsed, print GIC information to make the boot
log look pretty:
ACPI: GICC (acpi_id[0x] address[e112f000] MPIDR[0x0] enabled)
ACPI: GICC (acpi_id[0x0001] address[e112f000] MPIDR[0x1] enabled)
...
ACPI: GICC (acpi_id[0x0201] address[e112f000] MPIDR[0x201] en
From: Al Stone
ACPI reduced hardware mode is disabled by default, but ARM64
can only run properly in ACPI hardware reduced mode, so select
ACPI_REDUCED_HARDWARE_ONLY if ACPI is enabled on ARM64.
Reviewed-by: Grant Likely
Tested-by: Suravee Suthikulpanit
Signed-off-by: Al Stone
Signed-off-by:
From: Graeme Gregory
Add documentation for the guidelines of how to use ACPI
on ARM64.
Reviewed-by: Suravee Suthikulpanit
Signed-off-by: Graeme Gregory
Signed-off-by: Al Stone
Signed-off-by: Hanjun Guo
---
Documentation/arm64/arm-acpi.txt | 327 +++
1 fil
Using the information presented by GTDT to initialize the arch
timer (not memory-mapped).
Originally-by: Amit Daniel Kachhap
Tested-by: Suravee Suthikulpanit
Signed-off-by: Hanjun Guo
---
arch/arm64/kernel/time.c | 7 ++
drivers/clocksource/arm_arch_timer.c | 132
From: Graeme Gregory
Add Kconfigs to build ACPI on ARM64, and make ACPI available on ARM64.
acpi_idle driver is x86/IA64 dependent now, so make CONFIG_ACPI_PROCESSOR
depend on X86 || IA64, and implement it on ARM64 in the future.
Reviewed-by: Grant Likely
Tested-by: Suravee Suthikulpanit
Sign
From: Graeme Gregory
If the early boot methods of acpi are happy that we have valid ACPI
tables and acpi=force has been passed, then do not unflat devicetree
effectively disabling further hardware probing from DT.
Tested-by: Suravee Suthikulpanit
Signed-off-by: Graeme Gregory
Signed-off-by: Ha
There are two flags: PSCI_COMPLIANT and PSCI_USE_HVC. When set,
the former signals to the OS that the firmware is PSCI compliant.
The latter selects the appropriate conduit for PSCI calls by
toggling between Hypervisor Calls (HVC) and Secure Monitor Calls
(SMC).
FADT table contains such informatio
Since PCI is not required in ACPI spec and ARM can run without
it, introduce some stub functions to make PCI optional for ACPI,
and make ACPI core run without CONFIG_PCI on ARM64.
When PCI is enabled on ARM64, ACPI core will need some PCI functions
to make it functional, so introduce some empty fu
Hi,
This is the sixth version of ACPI core patches for ARM64 based on ACPI
5.1.
updates from v5:
- fix the NULL pointer reference in cpu_get_ops() if PSCI is absent
and NULL will passed, which found by Suravee when he was testing
those patches on Seattle platform. I added his Tested-by
On 02/01/15 11:28, Richard Weinberger wrote:
> Am 01.01.2015 um 22:18 schrieb har...@ccbib.org:
>> Hi!
>>
>> On Thu, 01 Jan 2015 12:38:23 +, Jonathan Cameron
>> wrote:
>>> On 02/12/14 23:32, Richard Weinberger wrote:
Please see my current patches for your driver.
As discussed in an e
On Fri, Jan 02, 2015 at 02:47:39PM -0500, Sasha Levin wrote:
> Device VQs were getting freed twice: once in every devices removal functions,
> and then again in virtio_pci_legacy_remove().
>
> Signed-off-by: Sasha Levin
I see. This used to be harmless because it used to be idempotent,
and safe
On 31/12/14 08:59, Nicholas Mc Guire wrote:
> The timeout value to wait_for_completion_timeout is in jiffies but
> the value being passed seems like it was intended to by microseconds
> Note that the timeout was extremely long thus it might be too short
> now. In any case it probably should be pass
Jonathan Cameron schrieb am 04.01.2015 um 11:55:
> On 01/01/15 13:53, Hartmut Knaack wrote:
>> Daniel Baluta schrieb am 23.12.2014 um 14:22:
>>> odr_bits values are between 0 and 11, so we can use the index
>>> in kmx61_samp_freq_table instead of odr_bits structure member.
>> Basically looking good
On Fri, Jan 02, 2015 at 02:47:40PM -0500, Sasha Levin wrote:
> When releasing a virtio device, We can't free a struct virtio_device until the
> underlying struct device has been released, which might not happen immediately
> on device_unregister() even if that was the device's last reference.
>
>
It turns out we need to add device-specific code
in release callback. Move it to virtio_pci_legacy.c.
Reported-by: Sasha Levin
Signed-off-by: Michael S. Tsirkin
---
This is intended as dependency for Sasha's patch adding
code to release callback.
drivers/virtio/virtio_pci_common.h | 1 -
driv
On Sun, Jan 04, 2015 at 04:38:17PM +0800, Jason Wang wrote:
>
> On 12/28/2014 03:52 PM, Michael S. Tsirkin wrote:
> > On Fri, Dec 26, 2014 at 10:53:42AM +0800, Jason Wang wrote:
> >> Hi all:
> >>
> >> This series try to share MSIX irq for each tx/rx queue pair. This is
> >> done through:
> >>
> >>
Hello.
Richard Guy Briggs wrote:
> > Richard Guy Briggs wrote:
> > > On 14/09/28, Tetsuo Handa wrote:
> > > > (Q2) Does auxiliary record work with only type=SYSCALL case?
> > >
> > > Auxiliary records don't work with AUDIT_LOGIN because that record has a
> > > NULL context. Similarly for core du
Changed the whole algorithm for a call to mktime64 that takes
care of all that details.
Signed-off-by: Oscar Forner Martinez
---
fs/isofs/util.c | 14 ++
1 file changed, 2 insertions(+), 12 deletions(-)
diff --git a/fs/isofs/util.c b/fs/isofs/util.c
index 01e1ee7..a3f953a 100644
---
From: Markus Elfring
Date: Sun, 4 Jan 2015 11:50:12 +0100
Further update suggestions were taken into account after several patches
were applied from static source code analysis.
Markus Elfring (3):
seq: Deletion of unnecessary checks before the function call
"snd_midi_event_free"
oss: Delet
2015-01-04 7:21 GMT+01:00 Larry Finger :
> On 01/03/2015 06:47 PM, Rickard Strandqvist wrote:
>>
>> Removes some functions that are not used anywhere:
>> dma_txflush() dma_txsuspended()
>>
>> This was partially found by using a static code analysis program called
>> cppcheck.
>>
>> Signed-off-by: R
From: Markus Elfring
Date: Sat, 3 Jan 2015 14:54:56 +0100
The snd_midi_event_free() function tests whether its argument is NULL and then
returns immediately. Thus the test around the call is not needed.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
From: Markus Elfring
Date: Sat, 3 Jan 2015 15:10:52 +0100
The vfree() function performs also input parameter validation. Thus the test
around the call is not needed.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
sound/oss/pss.c | 2 +-
sound/oss/
From: Markus Elfring
Date: Sat, 3 Jan 2015 17:06:04 +0100
The kfree() function tests whether its argument is NULL and then
returns immediately. Thus the test around the call is not needed.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
sound/pci/em
From: Markus Elfring
Date: Sat, 3 Jan 2015 17:37:28 +0100
The snd_pcm_suspend() function tests whether its argument is NULL and then
returns immediately. Thus the test around the call is not needed.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
so
From: Markus Elfring
Date: Sat, 3 Jan 2015 18:28:21 +0100
The snd_sf_free() function tests whether its argument is NULL and then
returns immediately. Thus the test around the call is not needed.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
sound/
From: Markus Elfring
Date: Sat, 3 Jan 2015 19:03:55 +0100
The sst_dma_free() function tests whether its argument is NULL and then
returns immediately. Thus the test around the call is not needed.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
sound
From: Markus Elfring
Date: Sat, 3 Jan 2015 19:25:55 +0100
The clk_enable() function tests whether its argument is NULL and then
returns immediately. Thus the test around the call is not needed.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
sound/s
From: Markus Elfring
Date: Sat, 3 Jan 2015 19:49:37 +0100
The release_firmware() function tests whether its argument is NULL and then
returns immediately. Thus the test around the call is not needed.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
s
From: Markus Elfring
Date: Sat, 3 Jan 2015 20:43:01 +0100
The snd_pcm_suspend_all() function tests whether its argument is NULL and then
returns immediately. Thus the test around the call is not needed.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
From: Markus Elfring
Date: Sat, 3 Jan 2015 21:02:32 +0100
The snd_emux_free() function tests whether its argument is NULL and then
returns immediately. Thus the test around the call is not needed.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
soun
From: Markus Elfring
Date: Sat, 3 Jan 2015 22:55:54 +0100
The iounmap() function performs also input parameter validation.
Thus the test around the call is not needed.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
sound/aoa/soundbus/i2sbus/core.c
From: Markus Elfring
Date: Sun, 4 Jan 2015 11:00:11 +0100
The iounmap() function was called in one case by the snd_msnd_attach() function
even if a previous call of the ioremap_nocache() function failed.
This implementation detail could be improved by the introduction of another
jump label.
Sig
From: Markus Elfring
Date: Sun, 4 Jan 2015 11:47:17 +0100
Two return statements were used by the snd_msnd_attach() function at source
code places where the Linux coding style recommends an alternative approach.
Let us improve the affected implementation details with adjustments for
corresponding
On Friday 02 January 2015 10:53 PM, Oleg Nesterov wrote:
Hi Pratyush,
I'll try to actually read this patch (and the whole series) later, just
a couple of quick questions for now.
On 12/31, Pratyush Anand wrote:
--- a/arch/arm64/include/asm/ptrace.h
+++ b/arch/arm64/include/asm/ptrace.h
@@ -
On Friday 02 January 2015 11:13 PM, Oleg Nesterov wrote:
On 12/31, Pratyush Anand wrote:
Both ARM and ARM64 handle uprobe exceptions through their own hooks.So
nothing to be done in arch_uprobe_exception_notify except to return
NOTIFY_DONE. Implement this as weak default function and remove
d
On Friday 02 January 2015 11:49 PM, Oleg Nesterov wrote:
On 01/02, Oleg Nesterov wrote:
On 12/31, Pratyush Anand wrote:
Re-factor flush_ptrace_access to reuse vma independent part.
But for what? The changelog should explain this.
Signed-off-by: Pratyush Anand
---
arch/arm64/mm/flush.
At Sun, 04 Jan 2015 14:38:38 +0100,
SF Markus Elfring wrote:
>
> From: Markus Elfring
> Date: Sun, 4 Jan 2015 11:00:11 +0100
>
> The iounmap() function was called in one case by the snd_msnd_attach()
> function
> even if a previous call of the ioremap_nocache() function failed.
>
> This implem
At Sun, 04 Jan 2015 13:43:11 +0100,
SF Markus Elfring wrote:
>
> From: Markus Elfring
> Date: Sun, 4 Jan 2015 11:50:12 +0100
>
> Further update suggestions were taken into account after several patches
> were applied from static source code analysis.
>
> Markus Elfring (3):
> seq: Deletion of
Remove the function ci_wait_for_smc_inactive() that is not used anywhere.
This was partially found by using a static code analysis program called
cppcheck.
Signed-off-by: Rickard Strandqvist
---
drivers/gpu/drm/radeon/ci_dpm.h |1 -
drivers/gpu/drm/radeon/ci_smc.c | 18 --
On 01/04/2015 06:26 AM, Michael S. Tsirkin wrote:
> On Fri, Jan 02, 2015 at 02:47:40PM -0500, Sasha Levin wrote:
>> > When releasing a virtio device, We can't free a struct virtio_device until
>> > the
>> > underlying struct device has been released, which might not happen
>> > immediately
>> > o
These two patches fix unbalanced pm and clock issues. The clock unbalance
issue would cause power consumption regression because the clock will never
be gated at runtime PM suspend.
Jisheng Zhang (2):
mmc: sdhci-pxav3: fix unbalanced clock issues during probe
mmc: sdhci-pxav3: fix pm unbalance
This patch calls pm_runtime_put_noidle() to restore the device's usage
counter in the ->remove() implementation.
Signed-off-by: Jisheng Zhang
---
drivers/mmc/host/sdhci-pxav3.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/mmc/host/sdhci-pxav3.c b/drivers/mmc/hos
Commit 0dcaa2499b7d ("sdhci-pxav3: Fix runtime PM initialization") tries
to fix one hang issue caused by calling sdhci_add_host() on a suspended
device. The fix enables the clock twice, once by clk_prepare_enable() and
another by pm_runtime_get_sync(), meaning that the clock will never be
gated at
Removes some functions that are not used anywhere:
acpi_ut_get_resource_bit_width() acpi_ut_display_predefined_method()
acpi_ut_match_resource_name()
This was partially found by using a static code analysis program called
cppcheck.
Signed-off-by: Rickard Strandqvist
---
drivers/acpi/acpica/ac
Our code calls del_vqs multiple times, assuming
it's idempotent.
commit 3ec7a77bb3089bb01032fdbd958eb5c29da58b49
virtio_pci: free up vq->priv
broke this assumption, by adding kfree there,
so multiple calls cause double free.
Fix it up.
Fixes: 3ec7a77bb3089bb01032fdbd958eb5c29da58b49
Reported
Removes some functions that are not used anywhere:
s5p_jpeg_input_raw_y16() s5p_jpeg_timer_disable() s5p_jpeg_timer_enable()
This was partially found by using a static code analysis program called
cppcheck.
Signed-off-by: Rickard Strandqvist
---
drivers/media/platform/s5p-jpeg/jpeg-hw-s5p.c |
This is a patch to the dmm32at.c file that fixes up a code indent error found
by the checkpatch.pl tool.
Signed-off-by: Piotr Kubus
---
drivers/staging/comedi/drivers/dmm32at.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/comedi/drivers/dmm32at.c
b/driver
On Mon, 29 Dec 2014 11:00:03 -0400
Joe Howse wrote:
> Add support in the PS3 Eye driver for QVGA capture at higher
> frame rates: 187, 150, and 137 FPS. This functionality is valuable
> because the PS3 Eye is popular for computer vision projects and no
> other camera in its price range supports s
Remove the function wl1251_cmd_read_memory() that is not used anywhere.
This was partially found by using a static code analysis program called
cppcheck.
Signed-off-by: Rickard Strandqvist
---
drivers/net/wireless/ti/wl1251/cmd.c | 40 --
drivers/net/wireless/
On Sun, Jan 04, 2015 at 10:03:27AM -0500, Sasha Levin wrote:
> On 01/04/2015 06:26 AM, Michael S. Tsirkin wrote:
> > On Fri, Jan 02, 2015 at 02:47:40PM -0500, Sasha Levin wrote:
> >> > When releasing a virtio device, We can't free a struct virtio_device
> >> > until the
> >> > underlying struct de
At least on UML this identifiers clash with register names.
Use something less generic than Rx, Cx and Cx.
CC lib//jedec_ddr_data.o
In file included from ./arch/um/include/asm/ptrace-generic.h:11:0,
from ./arch/x86/um/asm/ptrace.h:8,
from ./arch/x86/include
On Fri, Jan 02, 2015 at 06:36:12PM +0100, Ingo Molnar wrote:
>
> * Jiri Olsa wrote:
>
> > [...] The basic idea is the same as in kbuild system, with some
> > minor changes to allow for multiple binaries build definitions.
>
> > tools/perf/Build| 48 ++
> > too
Remove the function hci_conn_change_link_key() that is not used anywhere.
This was partially found by using a static code analysis program called
cppcheck.
Signed-off-by: Rickard Strandqvist
---
include/net/bluetooth/hci_core.h |1 -
net/bluetooth/hci_conn.c | 15 ---
Chen,
Am 02.10.2014 um 15:34 schrieb Chen Gang:
> SH_TIMER_CMT will use IO memory features which needs HAS_IOMEM, so need
> depend on it. The related error (with allmodconfig under um):
>
> CC drivers/clocksource/sh_cmt.o
> drivers/clocksource/sh_cmt.c: In function 'sh_cmt_map_memory':
The reason we defer kfree until release function is because it's a
general rule for kobjects: kfree of the reference counter itself is only
legal in the release function.
Previous patch didn't make this clear, document this in code.
Cc: sta...@vger.kernel.org
Signed-off-by: Michael S. Tsirkin
--
It turns out we need to add device-specific code
in release callback.
In particular, we need to free memory allocated in probe.
Move it to virtio_pci_legacy.c.
Signed-off-by: Michael S. Tsirkin
---
drivers/virtio/virtio_pci_common.h | 1 -
drivers/virtio/virtio_pci_common.c | 9 -
drive
This is based on Sasha's patch, with some tweaks.
Michael S. Tsirkin (2):
virtio_pci: device-specific release callback
virtio_pci: document why we defer kfree
Sasha Levin (1):
virtio_pci: defer kfree until release callback
drivers/virtio/virtio_pci_common.h | 1 -
drivers/virtio/virtio_
From: Sasha Levin
A struct device which has just been unregistered can live on past the
point at which a driver decides to drop it's initial reference to the
kobject gained on allocation.
This implies that when releasing a virtio device, we can't free a struct
virtio_device until the underlying
Linus,
The following changes since commit d753856c9f9ae33a980192aa7b81d8b97d79dec2:
Merge tag 'scsi-fixes' of
git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi (2015-01-02 13:24:41
-0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/rw/uml.gi
2015-01-03 18:53 GMT+01:00 Nishanth Menon :
> On 16:58-20150103, Rickard Strandqvist wrote:
>> Remove the function sr_configure_minmax() that is not used anywhere.
>>
>> This was partially found by using a static code analysis program called
>> cppcheck.
>>
>> Signed-off-by: Rickard Strandqvist
>
On Tue, Dec 30, 2014 at 08:03:27PM +0100, Peter Zijlstra wrote:
> On Thu, Dec 25, 2014 at 07:48:28AM -0800, Andy Lutomirski wrote:
> > On a quick look, there are plenty of other bugs in there besides just
> > the stack pointer issue. The ABI check that uses TIF_IA32 in the perf
> > core is complet
On Sun, Jan 04, 2015 at 06:02:13PM +0200, Michael S. Tsirkin wrote:
> This is based on Sasha's patch, with some tweaks.
>
Sasha, I would appreciate it if you can send
a Tested-by tag to confirm this + the del_vqs
idempotent patches are sufficient to address
all issues you have with 3.19.
> Mi
On Sat, Dec 27, 2014 at 02:06:30PM +0900, Namhyung Kim wrote:
> 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 ->
On Saturday 03 January 2015 18:59:46 Sergey Dyasly wrote:
> Hi Arnd,
>
> First, some background information. We originally encountered high
> fragmentation
> issue in vmalloc area:
>
> 1. Total size of vmalloc area was 400 MB.
> 2. 200 MB of vmalloc area was consumed by ioremaps of v
On Fri, Dec 26, 2014 at 04:19:18PM +0800, Fred Chou wrote:
> From: Fred Chou
>
> Use rt2x00_has_cap_flag macro to check rt2x00dev->cap_flags.
>
> Signed-off-by: Fred Chou
Acked-by: Stanislaw Gruszka
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
On Sat, Dec 27, 2014 at 02:06:31PM +0900, Namhyung Kim wrote:
> 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
On Jan 4, 2015 8:11 AM, "Jiri Olsa" wrote:
>
> On Tue, Dec 30, 2014 at 08:03:27PM +0100, Peter Zijlstra wrote:
> > On Thu, Dec 25, 2014 at 07:48:28AM -0800, Andy Lutomirski wrote:
> > > On a quick look, there are plenty of other bugs in there besides just
> > > the stack pointer issue. The ABI ch
On 22/12/14 16:51, Adam Thomson wrote:
> This patch adds support for DA9150 Charger & Fuel-Gauge IC GPADC.
>
> Signed-off-by: Adam Thomson
One last query from me.
Using the extended channel names in IIO is only really appropriate when
they don't correspond to simple pins on the side of the chip.
On 22/12/14 16:51, Adam Thomson wrote:
> This patch adds support for DA9150 Charger & Fuel-Gauge IC Charger.
>
> Signed-off-by: Adam Thomson
The IIO bits look fine, but your use of devm_free * doesn't...
As a side note, looks like we could benefit from some array versions
of the IIO channel gett
1 - 100 of 251 matches
Mail list logo
