On Tue, Jan 10, 2017 at 12:45:31PM -0800, David Carrillo-Cisneros wrote:
> >> diff --git a/include/linux/perf_event.h b/include/linux/perf_event.h
> >> index 4741ecdb9817..3fa18f05c9b0 100644
> >> --- a/include/linux/perf_event.h
> >> +++ b/include/linux/perf_event.h
> >> @@ -573,6 +573,7 @@ struct
The lib/sort.c file gets included in the EFI stub for use outside
of the kernel address space, which now fails due to the addition
of a module_init() function:
R_ARM_ABS32 test_sort_init
drivers/firmware/efi/libstub/lib-sort.stub.o: absolute symbol references not
allowed in the EFI
On 2017/1/5 7:35, Jaegeuk Kim wrote:
> Change log from v1:
> - remove F2FS_OP
> - share single tracing structure, f2fs__bio
> - split f2fs_prepare_read/write_io and f2fs_submit_read/write_io
>
>>From f5c6ab0f19fb627ebf28ab6a18c0a32b4c8f914f Mon Sep 17 00:00:00 2001
> From: Jaegeuk Kim
> Date:
On 01/11/2017 05:46 PM, Michal Hocko wrote:
On Wed 11-01-17 21:52:29, Ganapatrao Kulkarni wrote:
[ 2398.169391] Node 1 Normal: 951*4kB (UME) 1308*8kB (UME) 1034*16kB (UME)
742*32kB (UME) 581*64kB (UME) 450*128kB (UME) 362*256kB (UME) 275*512kB (ME)
189*1024kB (UM) 117*2048kB (ME) 2742*4096kB
Hi Stephan,
On 01/11/2017 06:09 PM, Stephan Müller wrote:
Am Mittwoch, 11. Januar 2017, 16:58:17 CET schrieb George Cherian:
Hi George,
I will add a seperate function for xts setkey and make changes as following.
...
+
+struct crypto_alg algs[] = { {
+ .cra_flags = CRYPTO_ALG_TYPE_AB
> On 12 Jan 2017, at 10:51, David Laight wrote:
>
> From: Sun Paul [mailto:paul...@gmail.com]
>> Sent: 12 January 2017 09:31
>> Let me clear the understanding. below is the flow.
>>
>> 1. Client sends to Linux Router: 192.168.206.83 -> 192.168.206.56,
>> 2. Linux router sends to SERVER where the
On Thu, Jan 12, 2017 at 8:59 AM, Al Viro wrote:
> On Tue, Jan 10, 2017 at 07:57:31AM -0500, Jeff Layton wrote:
>> v2: fix bug in offset handling in iov_iter_pvec_size
>>
>> xfstest generic/095 triggers soft lockups in kcephfs. Basically it uses
>> fio to drive some I/O via vmsplice ane splice. Cep
When CONFIG_PM_SLEEP is not set, rtc_update_mbus_timing_params becomes
unused, now that armada38x_rtc_probe() no longer calls
rtc_update_mbus_timing_params on startup:
drivers/rtc/rtc-armada38x.c:79:13: error: 'rtc_update_mbus_timing_params'
defined but not used [-Werror=unused-function]
This ad
The tegra DRM driver is almost ok without an MMU, but there
is one small warning that I get:
drivers/gpu/drm/tegra/gem.c: In function 'tegra_drm_mmap':
drivers/gpu/drm/tegra/gem.c:508:12: unused variable 'prot'
This marks the variable as __maybe_unused instead.
Signed-off-by: Arnd Bergmann
---
Hi Dave,
On Thu, Jan 12 2017, Dave Young wrote:
> efi_mem_reserve cares only about boot services regions and maybe loader areas.
> So add a new argument to efi_memmap_insert for this purpose.
Please see below.
> --- linux-x86.orig/drivers/firmware/efi/memmap.c
> +++ linux-x86/drivers/firmware/
Most of the kernel-doc comments in regmap don't actually generate
correctly. This patch fixes up a few common issues, corrects some typos
and adds some missing argument descriptions.
The most common issues being using a : after the function name which
causes the short description to not render cor
On 2017/1/5 7:50, Jaegeuk Kim wrote:
> Chang log from v1:
> - move stat_dec_atomic_write(inode); into drop_inmem_pages()
>
>>From 5464f744fe28187b3d71ba6c3cf983659a569e9a Mon Sep 17 00:00:00 2001
> From: Jaegeuk Kim
> Date: Wed, 28 Dec 2016 13:55:09 -0800
> Subject: [PATCH] f2fs: show the max nu
On Sat 2016-12-24 16:20:31, Pavel Machek wrote:
>
> N900 contains front and back camera, with a switch between the
> two. This adds support for the switch component, and it is now
> possible to select between front and back cameras during runtime.
>
> Signed-off-by: Sebastian Reichel
> Signed-of
On 2017/1/5 7:44, Jaegeuk Kim wrote:
> On 01/04, Chao Yu wrote:
>> Hi Jaegeuk,
>>
>> On 2016/12/31 2:51, Jaegeuk Kim wrote:
>>> This patch implements IO alignment by filling dummy blocks in DATA and NODE
>>> write bios. If we can guarantee, for example, 32KB or 64KB for such the IOs,
>>> we can eli
On Wed, 2017-01-11 at 16:59 -0800, Joe Perches wrote:
> On Wed, 2017-01-11 at 15:57 -0800, Andrew Morton wrote:
> > On Wed, 11 Jan 2017 18:28:07 +0200 Andy Shevchenko > o...@linux.intel.com> wrote:
> >
> > > While resource_size_t is repeating phys_addr_t, allocate %par
> > > specifier for
> > > t
Am Donnerstag, 12. Januar 2017, 16:40:32 CET schrieb George Cherian:
Hi George,
> >
> > Sure, please do not forget to invoke xts_verify_key.
>
> Should I be using xts_check_key or xts_verify_key?
Both are identical except for the input parameter -- the one requires
crypto_skcipher, the other
Hi Stephan,
Thank you for the clarification.
Regards,
-George
On 01/12/2017 04:49 PM, Stephan Müller wrote:
Am Donnerstag, 12. Januar 2017, 16:40:32 CET schrieb George Cherian:
Hi George,
Sure, please do not forget to invoke xts_verify_key.
Should I be using xts_check_key or xts_verify_k
2017-01-11 16:39 GMT+01:00 Uwe Kleine-König :
> On Wed, Jan 11, 2017 at 02:58:44PM +0100, M'boumba Cedric Madianga wrote:
>> Hi Uwe,
>>
>> 2017-01-11 9:22 GMT+01:00 Uwe Kleine-König :
>> > Hello Cedric,
>> >
>> > On Thu, Jan 05, 2017 at 10:07:23AM +0100, M'boumba Cedric Madianga wrote:
>> >> +/*
>>
The Moorestown support was removed by commit 1a8359e411eb ("x86/mid: Remove
Intel Moorestown").
Remove this leftover.
Signed-off-by: Andy Shevchenko
---
arch/x86/platform/intel-mid/sfi.c | 1 -
drivers/platform/x86/Kconfig | 7 -
drivers/platform/x86/Makefile | 1 -
Marc Gonzalez writes:
>> So far we have a claim that a cast to a void * may somehow be different
>> to a cast to a different pointer, if used as function argument, and that
>> the behavior with such a cast may be undefined. In other words, you claim
>> that a function implemented as, say,
>>
>>
Hi Uwe,
2017-01-11 16:42 GMT+01:00 Uwe Kleine-König :
> Hello Cedric,
>
> On Wed, Jan 11, 2017 at 03:20:41PM +0100, M'boumba Cedric Madianga wrote:
>> >
>> >> + */
>> >> + reg = i2c_dev->base + STM32F4_I2C_CR1;
>> >> + stm32f4_i2c_clr_bits(reg, STM32F4_I2C_CR1_
On Thu, 2017-01-12 at 07:59 +, Al Viro wrote:
> On Tue, Jan 10, 2017 at 07:57:31AM -0500, Jeff Layton wrote:
> >
> > v2: fix bug in offset handling in iov_iter_pvec_size
> >
> > xfstest generic/095 triggers soft lockups in kcephfs. Basically it uses
> > fio to drive some I/O via vmsplice ane
Hi Joseph,
On 01/09/2017 10:13 AM, Eric Ren wrote:
So you are trying to fix it by making phase3 finish without really doing
Phase3 can go ahead because this node is already under protection of cluster
lock.
You said it was blocked...
Oh, sorry, I meant phase3 can go ahead if this patch set i
Hi Arnd,
On 11/01/2017 at 15:50:31 +0100, Arnd Bergmann wrote :
> The function is too complicated for gcc to realize that this variable
> does eventually get initialized, causing a harmless warning:
>
> drivers/rtc/rtc-armada38x.c: In function 'read_rtc_register_wa':
> drivers/rtc/rtc-armada38x.c
On 10/01/17 22:04, Kim Phillips wrote:
> On Tue, 3 Jan 2017 18:10:26 +
> Will Deacon wrote:
>
>> +#define DRVNAME "arm_spe_pmu"
>
> Based on Intel naming "intel_pt" and "intel_bts', I had expected
> "arm-spe" as the universal basename for SPE. I don't really care
I wrote a simple script to find new typo not in spelling.txt.
(https://github.com/jinb-park/find-linux-kernel-typo)
and get following result:
[ rank ]
63 paramaters
18 alignement
9 strucuture
The number means how many files include the typo.
This patc
On 17/1/12 19:24, Eric Ren wrote:
Hi Joseph,
On 01/09/2017 10:13 AM, Eric Ren wrote:
So you are trying to fix it by making phase3 finish without really
doing
Phase3 can go ahead because this node is already under protection
of cluster lock.
You said it was blocked...
Oh, sorry, I meant phas
On Thu, Jan 12, 2017 at 12:27 PM, Jeff Layton wrote:
> On Thu, 2017-01-12 at 07:59 +, Al Viro wrote:
>> On Tue, Jan 10, 2017 at 07:57:31AM -0500, Jeff Layton wrote:
>> >
>> > v2: fix bug in offset handling in iov_iter_pvec_size
>> >
>> > xfstest generic/095 triggers soft lockups in kcephfs. Ba
On Thu, Jan 12, 2017 at 12:13:31PM +0100, Ilya Dryomov wrote:
> It would be a significant and wide-reaching change, but I've been
> meaning to look into switching to iov_iter for a couple of releases
> now. There is a lot of ugly code in net/ceph/messenger.c to hangle
> iteration over "page vecto
Hi,
On 12/01/2017 at 12:13:08 +0100, Arnd Bergmann wrote :
> When CONFIG_PM_SLEEP is not set, rtc_update_mbus_timing_params becomes
> unused, now that armada38x_rtc_probe() no longer calls
> rtc_update_mbus_timing_params on startup:
>
> drivers/rtc/rtc-armada38x.c:79:13: error: 'rtc_update_mbus_t
On 01/12/2017 01:26 AM, Andy Lutomirski wrote:
On Wed, Jan 11, 2017 at 10:17 AM, Dmitry Safonov wrote:
During fixing CRIU bugs on ZDTM tests for 32-bit C/R, I found that
compatible ia32/x32 syscalls mmap() and mmap2() can return address
over 4Gb in x86_64 applications, which results in returnin
Reviewed-by: Sagi Grimberg
Hi Guenter,
On Tue, Jan 10, 2017 at 03:34:33PM -0800, Guenter Roeck wrote:
> Use device managed functions to simplify error handling, reduce
> source code size, improve readability, and reduce the likelyhood of bugs.
> Other improvements as listed below.
>
> The conversion was done automatically
On Thu, Jan 12, 2017 at 12:37 PM, Al Viro wrote:
> On Thu, Jan 12, 2017 at 12:13:31PM +0100, Ilya Dryomov wrote:
>
>> It would be a significant and wide-reaching change, but I've been
>> meaning to look into switching to iov_iter for a couple of releases
>> now. There is a lot of ugly code in net
On Tue, Jan 10, 2017 at 12:20:00PM -0800, David Carrillo-Cisneros wrote:
> On Tue, Jan 10, 2017 at 6:14 AM, Mark Rutland wrote:
> > On Tue, Jan 10, 2017 at 02:24:58AM -0800, David Carrillo-Cisneros wrote:
> > For example, on a big.LITTLE system, big and little CPU PMUs share the
> > same context,
-pointer-over-4Gb/20170112-185732
config: x86_64-randconfig-x016-201702 (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
arch/x86/
On Thu, Jan 12, 2017 at 12:46:42PM +0100, Ilya Dryomov wrote:
> On Thu, Jan 12, 2017 at 12:37 PM, Al Viro wrote:
> > On Thu, Jan 12, 2017 at 12:13:31PM +0100, Ilya Dryomov wrote:
> >
> >> It would be a significant and wide-reaching change, but I've been
> >> meaning to look into switching to iov_i
On Thu, Jan 12 2017, Dave Young wrote:
> -void __init efi_bgrt_init(void)
> +void __init efi_bgrt_init(struct acpi_table_header *table)
> {
> - acpi_status status;
> void *image;
> struct bmp_header bmp_header;
>
> if (acpi_disabled)
> return;
>
> - sta
From: Arnd Bergmann
AFS uses a time based UUID to identify the host itself. This requires
getting a timestamp which is currently done through the getnstimeofday()
interface that we want to eventually get rid of.
Instead of replacing it with a ktime-based interface, simply remove the
entire func
Move the afs_uuid struct to linux/uuid.h and rename it to uuid_v1.
Signed-off-by: David Howells
---
fs/afs/cmservice.c | 22 +++---
fs/afs/internal.h| 26 +-
fs/afs/main.c| 25 +
include/linux/uuid.h | 24
On Thursday, January 12, 2017 12:09:11 PM CET Sagi Grimberg wrote:
> >> Another workaround me might need is to limit amount of concurrent DMA
> >> in the NVMe driver based on some platform quirk. The way that NVMe works,
> >> it can have very large amounts of data that is concurrently mapped into
>
On Thu, 2017-01-12 at 12:46 +0100, Ilya Dryomov wrote:
> On Thu, Jan 12, 2017 at 12:37 PM, Al Viro wrote:
> >
> > On Thu, Jan 12, 2017 at 12:13:31PM +0100, Ilya Dryomov wrote:
> >
> > >
> > > It would be a significant and wide-reaching change, but I've been
> > > meaning to look into switching
Hi Fengguang, Masami,
On Thu, Jan 12, 2017 at 11:31:57AM +0800, Fengguang Wu wrote:
> On Wed, Jan 11, 2017 at 07:08:40PM +0900, Masami Hiramatsu wrote:
> >BTW, I found that the old toolchain is archived in release.linaro.org.
> >So I made a patch for that.
>
> So there are gcc 4.9, 5, 6 versions
This patch moves codec specific clock indices to card driver data.
Functions configuring clocks can be re-used for other codec chips with
similar features (viz. RT5660)
Signed-off-by: Shrirang Bagul
---
sound/soc/intel/boards/bytcr_rt5640.c | 29 +++--
1 file changed, 23
This work is based on for-next branch of:
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
These patches add basic audio support on new Dell Edge IoT Gateways.
RT5660 codec is connected to SSP2 port on Intel Atom Baytrail E3815 SoC.
The machine driver is based on bytcr_rt5640. These
On 8 January 2017 at 22:38, SF Markus Elfring
wrote:
> From: Markus Elfring
> Date: Sun, 8 Jan 2017 22:30:03 +0100
>
> Some update suggestions were taken into account
> from static source code analysis.
>
> Markus Elfring (8):
> Use kmalloc_array() in mmc_test_area_init()
> Fix a typo in a co
On Dell IoT Gateways, RT5660 codec is available with ACPI ID 10EC3277.
Also, GPIO's are only available by index, so we register mappings to allow
machine drivers to access them by name.
Signed-off-by: Shrirang Bagul
---
sound/soc/codecs/rt5660.c | 32
1 file chan
This patch adds support to toggle mute on 'line-out' pin on Dell Edge
IoT Gateways. A dedicated GPIO on the SoC is used to control the amplifier.
This GPIO is described in the BIOS DSD table.
Signed-off-by: Shrirang Bagul
---
sound/soc/intel/boards/bytcr_rt5640.c | 28 +++
rt5660 and rt5640 are similar codecs so reuse the bytcr_rt5640 driver.
RT5660 codec is used on Dell Edge IoT Gateways with ACPI ID 10EC3277.
These devices sport only Line-In and Line-Out jacks.
Signed-off-by: Shrirang Bagul
---
sound/soc/intel/Kconfig | 11 +--
sound/soc/intel/ato
Hello Cedric,
On Thu, Jan 12, 2017 at 12:23:12PM +0100, M'boumba Cedric Madianga wrote:
> 2017-01-11 16:39 GMT+01:00 Uwe Kleine-König :
> > On Wed, Jan 11, 2017 at 02:58:44PM +0100, M'boumba Cedric Madianga wrote:
> >> 2017-01-11 9:22 GMT+01:00 Uwe Kleine-König
> >> :
> >> > This is surprising. I
From: William wu
On some platforms(e.g. rk3399 board), we can call hcd_add/remove
consecutively without calling usb_put_hcd/usb_create_hcd in between,
so hcd->flags can be stale.
If the HC dies due to whatever reason then without this patch we get
the below error on next hcd_add.
[173.296154] x
On Thu, Jan 12 2017, Dave Young wrote:
> Signed-off-by: Dave Young
> ---
> arch/x86/platform/efi/efi.c | 16
> drivers/firmware/efi/memmap.c | 16
> 2 files changed, 16 insertions(+), 16 deletions(-)
>
> --- linux-x86.orig/arch/x86/platform/efi/efi.c
> +++
rt5640: change widget sequence for depop")
Signed-off-by: Nicholas Mc Guire
---
Problem located by coccinelle script
Patch was compile tested with: x86_64_defconfig + SND_SOC=m
SND_SOC_INTEL_BYTCR_RT5640_MACH=m (implies CONFIG_SND_SOC_RT5640)
Patch is aginast 4.10-rc3 (localversion-n
Hi Bjorn,
Às 9:10 PM de 1/11/2017, Bjorn Helgaas escreveu:
> Hi Joao,
>
> On Wed, Dec 28, 2016 at 04:05:11PM +, Joao Pinto wrote:
>> This patch fixes a typo in MAINTAINERS file.
>>
>> Signed-off-by: Joao Pinto
>> ---
>> MAINTAINERS | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
The RFC patch supports filtering container specific events
when perf tool is executed inside a container.
Unlike previous approaches, this approach lets the user
decide what is a container through a set of kernel configs.
The main reason for such an approach is the lack of
container-unique identif
On Wed, Jan 11, 2017 at 01:54:07PM -0800, Andi Kleen wrote:
> On Wed, Jan 11, 2017 at 10:47:32PM +0100, Jiri Olsa wrote:
> > On Wed, Jan 11, 2017 at 11:52:58AM -0800, Andi Kleen wrote:
> > > > > v1: Initial post
> > > > > v2: Address review feedback. See changelog in commits.
> > > > > v3: Repost.
On Thu, Jan 12, 2017 at 12:53 PM, Al Viro wrote:
> On Thu, Jan 12, 2017 at 12:46:42PM +0100, Ilya Dryomov wrote:
>> On Thu, Jan 12, 2017 at 12:37 PM, Al Viro wrote:
>> > On Thu, Jan 12, 2017 at 12:13:31PM +0100, Ilya Dryomov wrote:
>> >
>> >> It would be a significant and wide-reaching change, bu
On Thu, Jan 12, 2017 at 08:52:51AM +0300, Nikita Yushchenko wrote:
> >> diff --git a/drivers/staging/fsl-mc/bus/fsl-mc-bus.c
> >> b/drivers/staging/fsl-mc/bus/fsl-mc-bus.c
> >> index 5ac373c..480b644 100644
> >> --- a/drivers/staging/fsl-mc/bus/fsl-mc-bus.c
> >> +++ b/drivers/staging/fsl-mc/bus/fs
On 12/01/2017 12:24, Måns Rullgård wrote:
> Marc Gonzalez writes:
>
>>> So far we have a claim that a cast to a void * may somehow be different
>>> to a cast to a different pointer, if used as function argument, and that
>>> the behavior with such a cast may be undefined. In other words, you clai
On Tue, Jan 10, 2017 at 12:51:58PM -0800, David Carrillo-Cisneros wrote:
> On Tue, Jan 10, 2017 at 8:38 AM, Mark Rutland wrote:
> > Hi,
> >
> > On Tue, Jan 10, 2017 at 02:24:59AM -0800, David Carrillo-Cisneros wrote:
> >> During sched in, only events that match the current CPU and cgroup can
> >>
William,
On 12/01/17 14:03, William Wu wrote:
> From: William wu
>
> On some platforms(e.g. rk3399 board), we can call hcd_add/remove
> consecutively without calling usb_put_hcd/usb_create_hcd in between,
> so hcd->flags can be stale.
>
> If the HC dies due to whatever reason then without this
32-bit socketcalls were not being logged by audit on x86_64 systems.
Log them.
See: https://github.com/linux-audit/audit-kernel/issues/14
Signed-off-by: Richard Guy Briggs
---
net/compat.c | 18 --
1 files changed, 16 insertions(+), 2 deletions(-)
diff --git a/net/compat.c b/
-Support-for-Cavium-Cryptographic-Acceleration-Unit/20170112-192240
config: blackfin-allmodconfig (attached as .config)
compiler: bfin-uclinux-gcc (GCC) 6.2.0
reproduce:
wget
https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross
-O ~/bin/make.cross
Fix:
WARNING: drivers/video/fbdev/pmagb-b-fb.o(.text+0x6dc): Section mismatch in
reference from the function pmagbbfb_probe() to the function
.init.text:pmagbbfb_erase_cursor()
The function pmagbbfb_probe()
references the function __init pmagbbfb_erase_cursor().
This is often because pmagbbfb_p
John Crispin wrote:
> From: Felix Fietkau
>
> The sign-file tool failed to build against libressl. Fix this by extending
> the PKCS7 check and thus making sign-file link against libressl without an
> error.
>
> Signed-off-by: John Crispin
> Signed-off-by: Felix Fietkau
Applied.
David
Hi,
This is a pair of small cleanups for `__init' annotation issues in PMAG-B
and PMAGB-B frame buffer drivers discovered in a modular build, which is a
seldom used, but supported configuration.
Resending this series now that the framebuffer subsystem is looked after
again (thanks for your c
Fix:
WARNING: drivers/video/fbdev/pmag-ba-fb.o(.text+0x308): Section mismatch in
reference from the function pmagbafb_probe() to the function
.init.text:pmagbafb_erase_cursor()
The function pmagbafb_probe()
references the function __init pmagbafb_erase_cursor().
This is often because pmagbafb_pr
Le 12/01/2017 à 11:35, SF Markus Elfring a écrit :
> From: Markus Elfring
> Date: Thu, 12 Jan 2017 10:42:25 +0100
>
> * Multiplications for the size determination of memory allocations
> indicated that array data structures should be processed.
> Thus use the corresponding function "kmalloc_a
Removed checkpatch.pl warning 'line over 80 characters' by inserting a
linebreak in the comment line 50.
Signed-off-by: Philip Thiemann
Signed-off-by: Fabian Arnold
---
drivers/staging/vme/devices/vme_user.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/staging/v
On Thu, 2017-01-12 at 09:22 +0100, Oliver Hartkopp wrote:
>
> On 01/12/2017 07:33 AM, Liu ShuoX wrote:
> > From: Zhang Yanmin
> >
> > The patch is for fix the below kernel panic:
> > BUG: unable to handle kernel NULL pointer dereference at (null)
> > IP: [] selinux_socket_sock_rcv_skb+0x65/0x2a0
On 01/12/2017 02:40 AM, Rafael J. Wysocki wrote:
>> >
>> > Hi Greg,
>> >
>> > Thanks for comments!
>> >
>> > The function dev_pm_qos_expose_latency_limit() is null if no CONFIG_PM.
>> > So when CONFIG_PM enabled, may we could consider the cpu idle is also
>> > wanted. In this assumption the #ifde
On Mon 2016-12-26 20:34:07, Sergey Senozhatsky wrote:
> Cc Greg, Jiri,
>
> On (12/26/16 19:54), Tetsuo Handa wrote:
> [..]
> >
> > (3) I got below warning. (Though not reproducible.)
> > If fb_flashcursor() called console_trylock(), console_may_schedule is
> > set to 1?
>
> hmmm... it takes
On Tue, Jan 10, 2017 at 04:56:47PM -0800, Bart Van Assche wrote:
> This patch does not change any functionality.
>
> Signed-off-by: Bart Van Assche
> Cc: David S. Miller
> Cc: linux-r...@vger.kernel.org
> Cc: net...@vger.kernel.org
> Cc: rds-de...@oss.oracle.com
> ---
> include/rdma/ib_verbs.h |
/linux/commits/Janakarajan-Natarajan/perf-x86-amd-uncore-Update-AMD-uncore-driver/20170112-184113
coccinelle warnings: (new ones prefixed by >>)
>> arch/x86/events/amd/uncore.c:365:2-7: WARNING: NULL check before freeing
>> functions like kfree, debugfs_remove, debugfs_r
arch/x86/events/amd/uncore.c:365:2-7: WARNING: NULL check before freeing
functions like kfree, debugfs_remove, debugfs_remove_recursive or usb_free_urb
is not needed. Maybe consider reorganizing relevant code to avoid passing NULL
values.
NULL check before some freeing functions is not needed.
ng: symbol 'rt5659_i2c_driver' was not
declared. Should it be static?
Patch was compile tested with: x86_64_defconfig + CONFIG_COMPILE_TEST=y
SND_SOC=m + SND_SOC_ALL_CODECS=m (implies SND_SOC_RT5659=m)
Patch is aginast 4.10-rc3 (localversion-next is next-20170112)
sound/soc/codecs/rt5659.c | 2 +
roblem was found by cocinelle script.
Patch was compile tested with: x86_64_defconfig + CONFIG_COMPILE_TEST=y
SND_SOC=m + SND_SOC_ALL_CODECS=m (implies SND_SOC_RT5659=m)
(44 sparse warnings - fixed in a seperate patches)
Patch is aginast 4.10-rc3 (localversion-next is next-20170112)
sound/soc/codec
Mimi Zohar wrote:
> On Fri, 2016-12-16 at 12:08 +0300, Dan Carpenter wrote:
> > This function has two callers and neither are able to handle a NULL
> > return. Really, -EINVAL is the correct thing return here anyway. This
> > fixes some static checker warnings like:
> >
> > security/keys/e
On Tue, Jan 10, 2017 at 04:56:44PM -0800, Bart Van Assche wrote:
> The qib DMA mapping code is no longer built since commit eb636ac0e49e
> ("IB/qib: Remove dma.c and use rdmavt version of dma functions"). Hence
> remove it.
>
> Signed-off-by: Bart Van Assche
> Cc: Mike Marciniszyn
> Cc: Dennis Da
On Thu, Jan 12, 2017 at 10:52:56AM +0530, Kishon Vijay Abraham I wrote:
> Hi Bjorn,
>
> On Thursday 12 January 2017 02:51 AM, Bjorn Helgaas wrote:
> > On Fri, Dec 30, 2016 at 03:26:11PM +0530, Kishon Vijay Abraham I wrote:
> >> This series contains
> >> *) a patch to cleanup dra7xx probe
>
Drop the const qualifier as it is being added by SOC_ENUM_DOUBLE_DECL()
already which is called by SOC_ENUM_SINGLE_DECL() as well as the
double const by calls to SOC_VALUE_ENUM_SINGLE_DECL() via
SOC_VALUE_ENUM_DOUBLE_DECL).
Fixes: commit d3cb2de2479b ("ASoC: rt5659: add rt5659 codec driver")
Signe
On Thursday, January 12, 2017 11:56:34 AM CET David Howells wrote:
> Move the afs_uuid struct to linux/uuid.h and rename it to uuid_v1.
>
> Signed-off-by: David Howells
>
Looks good to me, but I wonder if this part:
r = call->request;
- r->time_low
On Tue, Jan 10, 2017 at 04:56:45PM -0800, Bart Van Assche wrote:
> Additionally, switch from struct ib_dma_mapping_ops to struct
> dma_mapping_ops. Update the comments that referred to the source
> files removed by this patch.
>
> This patch eliminates one branch from every ib_dma_map_*() call.
>
>
On Thu, Jan 12, 2017 at 12:56:07PM +0100, Arnd Bergmann wrote:
> That is an interesting question: We actually have the
> "DMA_ATTR_NO_KERNEL_MAPPING" for this case, and ARM implements
> it in the coherent interface, so that might be a good fit.
Yes. my WIP HMB patch uses DMA_ATTR_NO_KERNEL_MAPPING
On Sun, 2017-01-08 at 13:54 +0100, Jason A. Donenfeld wrote:
> SHA1 is slower and less secure than SipHash, and so replacing syncookie
> generation with SipHash makes natural sense. Some BSDs have been doing
> this for several years in fact.
>
> The speedup should be similar -- and even more impre
On Tue, Jan 10, 2017 at 04:56:48PM -0800, Bart Van Assche wrote:
> Almost all changes in this patch except the removal of local variables
> that became superfluous and the actual removal of the ib_dma_map_*()
> functions have been generated as follows:
>
> git grep -lE 'ib_(sg_|)dma_' |
> xargs -
On Tue, Jan 10, 2017 at 6:00 AM, Sudeep Holla wrote:
> It is useful to have helper function just to get the number of cache
> levels for a given logical cpu. This patch adds the support for the
> same.
>
> It will be used on ARM64 platform where the device tree provides the
> information for the a
On Thursday, January 12, 2017 12:16:24 PM CET Will Deacon wrote:
> On Thu, Jan 12, 2017 at 08:52:51AM +0300, Nikita Yushchenko wrote:
> > >> diff --git a/drivers/staging/fsl-mc/bus/fsl-mc-bus.c
> > >> b/drivers/staging/fsl-mc/bus/fsl-mc-bus.c
> > >> index 5ac373c..480b644 100644
> > >> --- a/drive
Kernel or user may have special requirement on cpu response time, like
if a interrupt is pinned to a cpu, we don't want the cpu goes too deep
sleep. This patch can prevent this thing happen by consider per cpu
resume_latency setting in cpu sleep state selection in menu governor.
The pm_qos_resume_
The obsolete commit 71abbbf85 want to introduce a dynamic cstates,
but it was removed for long time. Just left the nonsense deeper cstate
checking.
Since all target_residency and exit_latency are going longer in deeper
idle state, no needs to waste some cpu cycle on useless seeking.
Signed-off-by
V2 changes: remove #ifdef CONFIG_CPU_IDLE_GOV_MENU for func
dev_pm_qos_expose_latency_limit(), since we have CONFIG_PM.
---
cpu_dma_latency is designed to keep all cpu awake from deep c-state.
That is good keep system with short response latency. But sometime we
don't need all cpu power especially
The cpu-dma PM QoS constraint impacts all the cpus in the system. There
is no way to let the user to choose a PM QoS constraint per cpu.
The following patch exposes to the userspace a per cpu based sysfs file
in order to let the userspace to change the value of the PM QoS latency
constraint.
This
On Thursday, January 12, 2017 9:33:32 AM CET Nikita Yushchenko wrote:
> >> Hmm, I think when the dma-ranges are missing, we should either enforce
> >> a 32-bit mask, or disallow DMA completely. It's probably too late for
> >> the latter, I wish we had done this earlier in order to force everyone
>
> On Wed, Jan 11, 2017 at 08:31:11PM +, Liang, Kan wrote:
>
> > > Kan, in your per-cpu event list patch you mentioned that you saw a
> > > large overhead in perf_iterate_ctx() when skipping events for other
> CPUs.
> > > Which callers of perf_iterate_ctx() specifically was that
> > > problem
Em Sun, Jan 08, 2017 at 07:57:53PM +0100, Jiri Olsa escreveu:
> On Tue, Jan 03, 2017 at 07:08:23AM -0800, Andi Kleen wrote:
>
> SNIP
>
> > - goto error;
> > -
> > - if (scale[sret - 1] == '\n')
> > - scale[sret - 1] = '\0';
> > - else
> > - scale[sret] = '\0';
>
Em Sun, Jan 08, 2017 at 07:58:00PM +0100, Jiri Olsa escreveu:
> On Tue, Jan 03, 2017 at 07:08:25AM -0800, Andi Kleen wrote:
>
> SNIP
>
> > /*
> > diff --git a/tools/perf/util/pmu.c b/tools/perf/util/pmu.c
> > index 29c254dd7380..8bffe99d8e3f 100644
> > --- a/tools/perf/util/pmu.c
> > +++ b/tools
drivers/crypto/cavium/cpt/cptvf_reqmanager.c:312:2-8: WARNING: NULL check
before freeing functions like kfree, debugfs_remove, debugfs_remove_recursive
or usb_free_urb is not needed. Maybe consider reorganizing relevant code to
avoid passing NULL values.
drivers/crypto/cavium/cpt/cptvf_reqmanage
/Add-Support-for-Cavium-Cryptographic-Acceleration-Unit/20170112-192240
coccinelle warnings: (new ones prefixed by >>)
>> drivers/crypto/cavium/cpt/cptvf_reqmanager.c:312:2-8: WARNING: NULL check
>> before freeing functions like kfree, debugfs_remove,
>> debugfs_remove_r
On 12/01/17 13:25, Arnd Bergmann wrote:
> On Thursday, January 12, 2017 12:16:24 PM CET Will Deacon wrote:
>> On Thu, Jan 12, 2017 at 08:52:51AM +0300, Nikita Yushchenko wrote:
> diff --git a/drivers/staging/fsl-mc/bus/fsl-mc-bus.c
> b/drivers/staging/fsl-mc/bus/fsl-mc-bus.c
> index 5a
Hi Dexuan,
sorry for dropping the ball on the previous private report, I hoped
I could get my hands on a Hyper-V VM and reproduce it myself, but
that has obviously not happened.
Can you send me the output of the provisioning_mode file for the
scsi disk in question to get started?
401 - 500 of 986 matches
Mail list logo
