[PATCH 14/31] lib: bch: use parity32

From: Zeng Zhaoxiu Signed-off-by: Zeng Zhaoxiu --- lib/bch.c | 14 +- 1 file changed, 1 insertion(+), 13 deletions(-) diff --git a/lib/bch.c b/lib/bch.c index bc89dfe4..6c6e8d4 100644 --- a/lib/bch.c +++ b/lib/bch.c @@ -278,18 +278,6 @@ static inline int deg(unsigned int poly)

[PATCH 15/31] media: use parity8 in vivid-vbi-gen.c

From: Zeng Zhaoxiu Signed-off-by: Zeng Zhaoxiu --- drivers/media/platform/vivid/vivid-vbi-gen.c | 9 ++--- 1 file changed, 2 insertions(+), 7 deletions(-) diff --git a/drivers/media/platform/vivid/vivid-vbi-gen.c b/drivers/media/platform/vivid/vivid-vbi-gen.c index a2159de..d5ba0fc 100644

[PATCH 16/31] media: saa7115: use parity functions

From: Zeng Zhaoxiu Signed-off-by: Zeng Zhaoxiu --- drivers/media/i2c/saa7115.c | 17 ++--- 1 file changed, 2 insertions(+), 15 deletions(-) diff --git a/drivers/media/i2c/saa7115.c b/drivers/media/i2c/saa7115.c index d2a1ce2..4c22df8 100644 --- a/drivers/media/i2c/saa7115.c +++ b/d

[PATCH 17/31] input: joystick: use parity32 in grip_mp.c

From: Zeng Zhaoxiu Signed-off-by: Zeng Zhaoxiu --- drivers/input/joystick/grip_mp.c | 16 +--- 1 file changed, 1 insertion(+), 15 deletions(-) diff --git a/drivers/input/joystick/grip_mp.c b/drivers/input/joystick/grip_mp.c index 573191d..3e29eb1 100644 --- a/drivers/input/joystick

[PATCH 18/31] input: joystick: use parity64 in sidewinder.c

From: Zeng Zhaoxiu Signed-off-by: Zeng Zhaoxiu --- drivers/input/joystick/sidewinder.c | 24 1 file changed, 4 insertions(+), 20 deletions(-) diff --git a/drivers/input/joystick/sidewinder.c b/drivers/input/joystick/sidewinder.c index 4a95b22..7ea486e 100644 --- a/dri

[PATCH 19/31] input: serio: use parity16 in ams_delta_serio.c

From: Zeng Zhaoxiu Signed-off-by: Zeng Zhaoxiu --- drivers/input/serio/ams_delta_serio.c | 8 ++-- 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/drivers/input/serio/ams_delta_serio.c b/drivers/input/serio/ams_delta_serio.c index 45887e3..85459b3 100644 --- a/drivers/input/s

[PATCH 20/31] scsi: use parity32 in isci/phy.c

From: Zeng Zhaoxiu Signed-off-by: Zeng Zhaoxiu --- drivers/scsi/isci/phy.c | 18 -- 1 file changed, 4 insertions(+), 14 deletions(-) diff --git a/drivers/scsi/isci/phy.c b/drivers/scsi/isci/phy.c index cb87b2e..0b87ff4 100644 --- a/drivers/scsi/isci/phy.c +++ b/drivers/scsi/isc

[PATCH 21/31] mtd: use parity16 in ssfdc.c

From: Zeng Zhaoxiu Signed-off-by: Zeng Zhaoxiu --- drivers/mtd/ssfdc.c | 20 ++-- 1 file changed, 2 insertions(+), 18 deletions(-) diff --git a/drivers/mtd/ssfdc.c b/drivers/mtd/ssfdc.c index daf82ba..b4d9144 100644 --- a/drivers/mtd/ssfdc.c +++ b/drivers/mtd/ssfdc.c @@ -182,24

[PATCH 22/31] mtd: use parity functions in inftlcore.c

From: Zeng Zhaoxiu Signed-off-by: Zeng Zhaoxiu --- drivers/mtd/inftlcore.c | 17 - 1 file changed, 4 insertions(+), 13 deletions(-) diff --git a/drivers/mtd/inftlcore.c b/drivers/mtd/inftlcore.c index b66b541..29567bb 100644 --- a/drivers/mtd/inftlcore.c +++ b/drivers/mtd/inftl

[PATCH 23/31] crypto: qat: use parity functions in qat_hal.c

From: Zeng Zhaoxiu Signed-off-by: Zeng Zhaoxiu --- drivers/crypto/qat/qat_common/qat_hal.c | 32 ++-- 1 file changed, 10 insertions(+), 22 deletions(-) diff --git a/drivers/crypto/qat/qat_common/qat_hal.c b/drivers/crypto/qat/qat_common/qat_hal.c index 1e480f1..318

[PATCH 24/31] mtd: use parity16 in sm_ftl.c

From: Zeng Zhaoxiu Signed-off-by: Zeng Zhaoxiu --- drivers/mtd/sm_ftl.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/mtd/sm_ftl.c b/drivers/mtd/sm_ftl.c index b096f8b..2244588 100644 --- a/drivers/mtd/sm_ftl.c +++ b/drivers/mtd/sm_ftl.c @@ -136,7 +136,7 @@ sta

[PATCH 25/31] ethernet: use parity8 in sun/niu.c

From: Zeng Zhaoxiu Signed-off-by: Zeng Zhaoxiu --- drivers/net/ethernet/sun/niu.c | 10 ++ 1 file changed, 2 insertions(+), 8 deletions(-) diff --git a/drivers/net/ethernet/sun/niu.c b/drivers/net/ethernet/sun/niu.c index 9cc4564..8c344ef 100644 --- a/drivers/net/ethernet/sun/niu.c +++

[PATCH 26/31] input: serio: use parity8 in pcips2.c

From: Zeng Zhaoxiu Signed-off-by: Zeng Zhaoxiu --- drivers/input/serio/pcips2.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/input/serio/pcips2.c b/drivers/input/serio/pcips2.c index e862c6e..a51e7f0 100644 --- a/drivers/input/serio/pcips2.c +++ b/drivers/input/se

[PATCH 27/31] input: serio: use parity8 in sa1111ps2.c

From: Zeng Zhaoxiu Signed-off-by: Zeng Zhaoxiu --- drivers/input/serio/saps2.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/input/serio/saps2.c b/drivers/input/serio/saps2.c index b3e6889..324b193 100644 --- a/drivers/input/serio/saps2.c +++ b/driv

[PATCH 28/31] iio: gyro: use parity32 in adxrs450.c

From: Zeng Zhaoxiu Signed-off-by: Zeng Zhaoxiu --- drivers/iio/gyro/adxrs450.c | 8 ++-- 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/drivers/iio/gyro/adxrs450.c b/drivers/iio/gyro/adxrs450.c index a330d42..f1f19fc20 100644 --- a/drivers/iio/gyro/adxrs450.c +++ b/drivers/ii

Re: Warnings for invalid VDD (sdhci-s3c)

Hi All, On 24 March 2016 at 20:04, Adrian Hunter wrote: > On 24/03/16 16:03, Ludovic Desroches wrote: >> Hi, >> >> On Thu, Mar 24, 2016 at 03:11:25PM +0200, Adrian Hunter wrote: >>> On 24/03/16 10:42, Krzysztof Kozlowski wrote: On 24.03.2016 17:24, Jisheng Zhang wrote: > Hi, > >

[PATCH 29/31] serial: use parity32 in max3100.c

From: Zeng Zhaoxiu Signed-off-by: Zeng Zhaoxiu --- drivers/tty/serial/max3100.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/tty/serial/max3100.c b/drivers/tty/serial/max3100.c index 5c4c280..a0cc84a 100644 --- a/drivers/tty/serial/max3100.c +++ b/drivers/tty/seri

[PATCH 30/31] input: mouse: use parity8 in elantech

From: Zeng Zhaoxiu Signed-off-by: Zeng Zhaoxiu --- drivers/input/mouse/elantech.c | 10 +++--- drivers/input/mouse/elantech.h | 1 - 2 files changed, 3 insertions(+), 8 deletions(-) diff --git a/drivers/input/mouse/elantech.c b/drivers/input/mouse/elantech.c index 78f93cf..778b5d1 100644

[PATCH 31/31] ethernet: broadcom: use parity8 in tg3.c

From: Zeng Zhaoxiu Signed-off-by: Zeng Zhaoxiu --- drivers/net/ethernet/broadcom/tg3.c | 6 +- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/drivers/net/ethernet/broadcom/tg3.c b/drivers/net/ethernet/broadcom/tg3.c index 3010080..802a429 100644 --- a/drivers/net/ethernet/bro

Re: [PATCH 01/31] bitops: add parity functions

On 2016/3/27 6:08, Martin Kepplinger wrote: > We do. > > Am 24. März 2016 23:28:15 MEZ, schrieb Andrew Morton > : >> On Thu, 24 Mar 2016 09:38:21 +0100 Denys Vlasenko >> wrote: >> >>> On 03/24/2016 04:03 AM, Zhaoxiu Zeng wrote: +/* + * Type invariant interface to the compile time const

Re: [PATCH] net: sxgbe: fix error paths in sxgbe_platform_probe()

Rasmus Villemoes : > We need to use post-decrement to ensure that irq_dispose_mapping is > also called on priv->rxq[0]->irq_no; moreover, if one of the above for > loops failed already at i==0 (so we reach one of these labels with > that value of i), we'll enter an essentially infinite loop of > o

Re: [PATCH v8 4/4] power: wm831x_power: Support USB charger current limit management

On Thu, Mar 24, 2016 at 1:35 PM, Baolin Wang wrote: > --- a/drivers/power/wm831x_power.c > +++ b/drivers/power/wm831x_power.c > @@ -13,6 +13,7 @@ > #include > #include > #include > +#include > > #include > #include > @@ -31,6 +32,8 @@ struct wm831x_power { > char usb_name[20]; >

Re: [PATCH 0/2] x86/microcode/amd: Do not overwrite specific patch levels

On Sat, Mar 26, 2016 at 08:31:57PM -0300, Henrique de Moraes Holschuh wrote: > This patchset looks like it is pretty much a requirement for any distro that > ships AMD microcode updates... Maybe the two commits should be sent to > -stable, now that they have seen lots of testing in mainline 4.4.x

Re: [PATCH 2/2] regulator: core: Ensure we are at least in bounds for our constraints

On Sat, Mar 26, 2016 at 04:50:41PM -0700, Bjorn Andersson wrote: > Reinstating the following snippet in of_get_regulation_constraints() > sort this out: > if (constraints->min_uV && constraints->max_uV) >constraints->apply_uV = true; The existing check in

linux-next: build failure after merge of the nvdimm tree

Hi Dan, After merging the nvdimm tree, today's linux-next build (powerpc allyesconfig) failed like this: In file included from /home/sfr/next/next/fs/dax.c:28:0: include/linux/pmem.h: In function 'memcpy_from_pmem': include/linux/pmem.h:79:9: error: implicit declaration of function 'arch_memcpy_

drivers/infiniband/hw/i40iw/i40iw_cm.c:2206:52: warning: 'arpindex' may be used uninitialized in this function

tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: f55532a0c0b8bb6148f4e07853b876ef73bc69ca commit: 520a07bff6fbb23cac905007d74c67058b189acb Merge branches 'i40iw', 'sriov' and 'hfi1' into k.o/for-4.6 date: 6 days ago config: x86_64-randconfig-s5-03271744

linux-next: Tree for Mar 27

Hi all, Changes since 20160324: Undropped tree: overlayfs The overlayfs lost its conflicts against the ext4 tree. The nvdimm tree gained a build failure so I used the version from next-20160324. Non-merge commits (relative to Linus' tree): 520 452 files changed, 10923 insertions(+), 3613 dele

Business Proposal

Greeting, My name is SONOU Mark, a Chartered Accountant, can you work with me to make a partnership investment in the areas of school, hotel or estate in your country? in a business proposal. The fund is 100% legitimate. Kindly get back to ON: rsdfcgvhb...@gmail.com; me for more details. You c

Re: [PATCH 3/4] perf, tools, script: Add support for printing assembler

On Fri, Mar 25, 2016 at 04:02:37PM -0700, Andi Kleen wrote: > From: Andi Kleen > > When dumping PT traces with perf script it is very useful to see the > assembler for each sample, so that it is easily possible to follow > the control flow. > > As using objdump is difficult and inefficient from

Re: [PATCH] perf config: Tidy up the code setting buildid dir

On Thu, Mar 24, 2016 at 04:49:33PM +0900, Taeung Song wrote: > Add new perf_buildid_config() into perf_default_config, > bring set_buildid_dir() next to perf_default_config, > rename some variable name as more readable name and etc > in order to clean up code about buildid dir. > > Cc: Jiri Olsa

Re: [PATCH 1/1] perf tools: Fix build break on powerpc

On Sat, Mar 26, 2016 at 11:01:47AM -0700, Sukadev Bhattiprolu wrote: > From 502e8236082412db1d33abfad95aaf14b539502e Mon Sep 17 00:00:00 2001 > From: Sukadev Bhattiprolu > Date: Sat, 26 Mar 2016 17:31:39 -0400 > Subject: [PATCH 1/1] perf tools: Fix build break on powerpc > MIME-Version: 1.0 > Cont

Re: [PATCH 2/4] perf, tools: Add probing for udev86

On Fri, Mar 25, 2016 at 04:02:36PM -0700, Andi Kleen wrote: > From: Andi Kleen > > Add autoprobing for the udev86 disassembler library. > > Signed-off-by: Andi Kleen Acked-by: Jiri Olsa thanks, jirka

Re: Add top down metrics to perf stat

On Tue, Mar 22, 2016 at 04:08:46PM -0700, Andi Kleen wrote: SNIP > In this case perf stat automatically enables --per-core mode and also requires > global mode (-a) and avoiding other filters (no cgroup mode) > > When Hyper Threading is off this can be overriden with the --single-thread > option

Re: [PATCH 1/2] perf, tools: Document event specifications better

On Tue, Mar 22, 2016 at 11:09:30AM -0700, Andi Kleen wrote: > From: Andi Kleen > > Document some undocumented features for specifying events in the perf > list manpage: > > - Event groups > - Leader sampling > - How to specify raw PMU events in the new syntax > - Global versus per process PMUs.

Can You Partner With Me

Hello My Dearest, My name is Mark Kosonou, I got your contact through internet directory and felt that you might be straight forward fellow and reliable to do business with in areas of investment and financial partnering, I am writing to acquaint you of a transaction and monetary transfer of (

Re: [PATCH] drivers : Remove unnecessary void pointer conversions

Hello. On 3/27/2016 6:42 AM, Bhaskar Jupudi wrote: Explicit void pointer conversion is unnecessary because the conversions to and from a void pointer are always implicit in 'C'. Changed two instances of such conversions. Signed-off-by: Bhaskar Jupudi --- This patch is based on Kernel Janitor

Re: [Linux-v4.6-rc1] ext4: WARNING: CPU: 2 PID: 2692 at kernel/locking/lockdep.c:2017 __lock_acquire+0x180e/0x2260

On Sun, Mar 27, 2016 at 1:57 AM, Sedat Dilek wrote: > > I pulled ext4.git#dev on top of Linux v4.6-rc1... > > ... and did not see the call-trace. Unless you're using overlayfs or per-file encryption, I'm not seeing that any of that should make any difference (but it's entirely possible I'm missin

[PATCH] Staging: vt6655: defined some arrays as const arrays since they are not changed anywhere in code

This patch defines byVT3253B0_AGC4_RFMD2959[], byVT3253B0_AIROHA2230[], byVT3253B0_UW2451[] and byVT3253B0_AGC[] arrays as const arrays since they are not change anywhere in code. After this change some lines broke the 80 characters per line rule. To fix this, some changed lines were splited on two

Re: [PATCH v5 00/21] PM / devferq: Add generic exynos bus frequency driver and new passive governor

Hi Chanwoo Choi, On 24 March 2016 at 10:00, Chanwoo Choi wrote: > Dear Anand and Tobias, > > To Anand, > First of all, thanks to your test on previous patchset. > I removed the your tested-by tag from this version > because I modified the devfreq core using DEVFREQ_TRANSITION_NOTIFIER > notifier

Re: [PATCH 0/2] x86/microcode/amd: Do not overwrite specific patch levels

On Sun, 27 Mar 2016, Borislav Petkov wrote: > On Sat, Mar 26, 2016 at 08:31:57PM -0300, Henrique de Moraes Holschuh wrote: > > This patchset looks like it is pretty much a requirement for any distro that > > ships AMD microcode updates... Maybe the two commits should be sent to > > -stable, now th

Build regressions/improvements in v4.6-rc1

Below is the list of build error/warning regressions/improvements in v4.6-rc1[1] compared to v4.5[2]. Summarized: - build errors: +9/-6 - build warnings: +148/-165 As I haven't mastered kup yet, there's no verbose summary at http://www.kernel.org/pub/linux/kernel/people/geert/linux-log/v4.6-r

Re: Build regressions/improvements in v4.6-rc1

On Sun, Mar 27, 2016 at 2:39 PM, Geert Uytterhoeven wrote: > Below is the list of build error/warning regressions/improvements in > v4.6-rc1[1] compared to v4.5[2]. > > Summarized: > - build errors: +9/-6 > [1] http://kisskb.ellerman.id.au/kisskb/head/10114/ (all 262 configs) > [2] http://kissk

Re: [PATCH 01/31] bitops: add parity functions

Hi Zeng. Looking through the arch specific implementations of __arch_parity(). Some architectures uses #defines, other uses inline static functions. Any particular reason that you select one approach over the other in the different cases? ia64: +#define __arch_parity32(x) ((unsigned int) __arch_

Re: Build regressions/improvements in v4.6-rc1

On Sun, Mar 27, 2016 at 02:43:24PM +0200, Geert Uytterhoeven wrote: > On Sun, Mar 27, 2016 at 2:39 PM, Geert Uytterhoeven > wrote: > > Below is the list of build error/warning regressions/improvements in > > v4.6-rc1[1] compared to v4.5[2]. > > > > Summarized: > > - build errors: +9/-6 > > > [1

Re: [Linux-v4.6-rc1] ext4: WARNING: CPU: 2 PID: 2692 at kernel/locking/lockdep.c:2017 __lock_acquire+0x180e/0x2260

On Sun, Mar 27, 2016 at 05:03:44AM -0700, Linus Torvalds wrote: > On Sun, Mar 27, 2016 at 1:57 AM, Sedat Dilek wrote: > > > > I pulled ext4.git#dev on top of Linux v4.6-rc1... > > > > ... and did not see the call-trace. > > Unless you're using overlayfs or per-file encryption, I'm not seeing > th

Re: [PATCH 01/31] bitops: add parity functions

On 2016/3/27 20:44, Sam Ravnborg wrote: > Hi Zeng. > > Looking through the arch specific implementations of __arch_parity(). > Some architectures uses #defines, other uses inline static functions. > > Any particular reason that you select one approach over the other > in the different cases? > >

Re: rcu_preempt self-detected stall on CPU from 4.5-rc3, since 3.17

- On Mar 26, 2016, at 9:34 PM, Paul E. McKenney paul...@linux.vnet.ibm.com wrote: > On Sat, Mar 26, 2016 at 10:22:57PM +, Mathieu Desnoyers wrote: >> - On Mar 26, 2016, at 2:49 PM, Paul E. McKenney >> paul...@linux.vnet.ibm.com >> wrote: >> >> > On Sat, Mar 26, 2016 at 08:28:16AM -0

Darlehen Angebot

Sie benötigen ein Darlehen niedrige Rate? Altanlage gibt aus Darlehen in günstigen Preis gilt jetzt: legacyassetgro...@hotmail.com

Re: [PATCH v5 00/21] PM / devferq: Add generic exynos bus frequency driver and new passive governor

Hi Anand, On Sun, Mar 27, 2016 at 9:28 PM, Anand Moon wrote: > Hi Chanwoo Choi, > > On 24 March 2016 at 10:00, Chanwoo Choi wrote: >> Dear Anand and Tobias, >> >> To Anand, >> First of all, thanks to your test on previous patchset. >> I removed the your tested-by tag from this version >> because

平时最多联系3000，还有十几万如何去开发？

你好 有打算开发国外客户吗？ 不参加展会也不上B2B平台，但照样可以开发优质海外客户。方法很简单，一天帮您做出效果 您只需要提供一个产品关键词，花费十分钟时间，就可以体验客户开发搜索软件带给您的惊喜。 咨询qq: 1286754208

Re: [PATCH] i.MX6 PCIe: Fix imx6_pcie_deassert_core_reset() polarity

On Fri, Mar 25, 2016 at 10:32 AM, Krzysztof Hałasa wrote: > A recent commit 5c5fb40de8f14391a1238db05cef88754faf9229 stated: > Follows: linus/v4.4-rc2 > Precedes: linus/v4.5-rc1 > > PCI: imx6: Add support for active-low reset GPIO > > We previously used of_get_named_gpio(), which ignores t

Re: [PATCH 3/5] perf core: Prepare writing into ring buffer from end

On Fri, Mar 25, 2016 at 10:14:36PM +0800, Wangnan (F) wrote: > >>I think you enabled some unusual config options? x86_64-defconfig > >You must enabled CONFIG_OPTIMIZE_INLINING. Now I get similar result: It has that indeed. > After enabling CONFIG_OPTIMIZE_INLINING: > > Test its performance by

Re: Add top down metrics to perf stat

> can't see this one (-16): > > [jolsa@krava perf]$ git remote update ak > Fetching ak > [jolsa@krava perf]$ git branch -r | grep top-down > ak/perf/top-down-10 > ak/perf/top-down-11 > ak/perf/top-down-13 > ak/perf/top-down-2 Please try again, I pushed it again. -Andi

Re: [PATCH V2 2/3] vfio, platform: make reset driver a requirement

Hi Sinan, On 03/16/2016 03:27 PM, Sinan Kaya wrote: > Hi Baptiste, > >>> I couldn't see a reset function for AMBA devices. >>> >>> Is there anyway to write reset function for it? I have no experience with >>> AMBA devices. >> To my knowledge only the PL330 DMA controller (drivers/dma/pl330.c) was

Re: [PATCH] ntb: test: fix pointer size warning

On Mon, Mar 21, 2016 at 8:31 PM, Brian Norris wrote: > On Mon, Mar 21, 2016 at 07:52:38PM -0400, Jon Mason wrote: >> On Fri, Mar 18, 2016 at 10:11:20AM -0700, Brian Norris wrote: >> > drivers/ntb/test/ntb_perf.c: In function ‘perf_copy’: >> > drivers/ntb/test/ntb_perf.c:213:10: warning: cast from

Re: [PATCH 3/5] perf core: Prepare writing into ring buffer from end

发自我的 iPhone > 在 2016年3月27日，下午11:20，Peter Zijlstra 写道： > > On Fri, Mar 25, 2016 at 10:14:36PM +0800, Wangnan (F) wrote: I think you enabled some unusual config options? > > x86_64-defconfig > >>> You must enabled CONFIG_OPTIMIZE_INLINING. Now I get similar result: > > It has that indeed

Re: [PATCH 3/4] perf, tools, script: Add support for printing assembler

> > Current issues: > > - Some jump references do not get resolved to symbols. > > - udis86 release does not support STAC/CLAC, which are used in the kernel, > > but there is a pending patch for it. > > can't apply this on latest Arnaldo's tree: This is due to which is only in Arnaldo's tree com

Re: rcu_preempt self-detected stall on CPU from 4.5-rc3, since 3.17

On Sun, Mar 27, 2016 at 01:48:55PM +, Mathieu Desnoyers wrote: > - On Mar 26, 2016, at 9:34 PM, Paul E. McKenney > paul...@linux.vnet.ibm.com wrote: > > > On Sat, Mar 26, 2016 at 10:22:57PM +, Mathieu Desnoyers wrote: > >> - On Mar 26, 2016, at 2:49 PM, Paul E. McKenney > >> paul

Re: [PATCH] perf config: Tidy up the code setting buildid dir

Hi, jirka Thank you for your review :-) On 03/27/2016 08:16 PM, Jiri Olsa wrote: On Thu, Mar 24, 2016 at 04:49:33PM +0900, Taeung Song wrote: Add new perf_buildid_config() into perf_default_config, bring set_buildid_dir() next to perf_default_config, rename some variable name as more readable

[PATCH 1/9] drivers/gpio: make gpio-bcm-kona.c explicitly non-modular

The Kconfig currently controlling compilation of this code is: config GPIO_BCM_KONA bool "Broadcom Kona GPIO" ...meaning that it currently is not being built as a module by anyone. Lets remove the couple traces of modularity so that when reading the driver there is no doubt it is builtin

[PATCH 5/9] drivers/gpio: make gpio-mvebu.c explicitly non-modular

The Kconfig currently controlling compilation of this code is: drivers/gpio/Kconfig:config GPIO_MVEBU drivers/gpio/Kconfig: def_bool y ...meaning that it currently is not being built as a module by anyone. Lets remove the couple traces of modularity so that when reading the driver there is no

[PATCH 3/9] drivers/gpio: make gpio-mc9s08dz60.c explicitly non-modular

The Kconfig currently controlling compilation of this code is: drivers/gpio/Kconfig:config GPIO_MC9S08DZ60 drivers/gpio/Kconfig: bool "MX35 3DS BOARD MC9S08DZ60 GPIO functions" ...meaning that it currently is not being built as a module by anyone. Lets remove the modular code that is essential

[PATCH 8/9] drivers/gpio: make gpio-xgene.c explicitly non-modular

The Kconfig currently controlling compilation of this code is: drivers/gpio/Kconfig:config GPIO_XGENE drivers/gpio/Kconfig: bool "APM X-Gene GPIO controller support" ...meaning that it currently is not being built as a module by anyone. Lets remove the modular code that is essentially orphaned

[PATCH 0/9] gpio: batch #1: remove modular usage from non-modular drivers

For GPIO, I've divided up the the audit of modular usage in non-modular drivers into three categories to ease review and limit the batch size. The breakdown of the three groups is as follows: 1) just replacement of modular macros with their non-modular equivalents that CPP would have inserted a

[PATCH 4/9] drivers/gpio: make gpio-moxart.c explicitly non-modular

The Kconfig currently controlling compilation of this code is: drivers/gpio/Kconfig:config GPIO_MOXART drivers/gpio/Kconfig: bool "MOXART GPIO support" ...meaning that it currently is not being built as a module by anyone. Lets remove the couple traces of modular references so that when readin

[PATCH 7/9] drivers/gpio: make gpio-sta2x11.c explicitly non-modular

The Kconfig currently controlling compilation of this code is: drivers/gpio/Kconfig:config GPIO_STA2X11 drivers/gpio/Kconfig: bool "STA2x11/ConneXt GPIO support" ...meaning that it currently is not being built as a module by anyone. Lets remove the couple traces of modularity, so that when rea

[PATCH 6/9] drivers/gpio: make gpio-pl061.c explicitly non-modular

The Kconfig for this driver is currently: config GPIO_PL061 bool "PrimeCell PL061 GPIO support" ...meaning that it currently is not being built as a module by anyone. Lets remove the couple traces of modularity, so that when reading the driver there is no doubt it is builtin-only. Since

[PATCH 2/9] drivers/gpio: make gpio-mb86s7x.c driver explicitly non-modular

The Kconfig for this driver is currently: config GPIO_MB86S7X bool "GPIO support for Fujitsu MB86S7x Platforms" ...meaning that it currently is not being built as a module by anyone. Lets remove the couple traces of modularity, so that when reading the driver there is no doubt it is built

[PATCH 9/9] drivers/gpio: make gpio-zx.c explicitly non-modular

The Kconfig currently controlling compilation of this code is: config GPIO_ZX bool "ZTE ZX GPIO support" ...meaning that it currently is not being built as a module by anyone. Lets remove the couple traces of modularity so that when reading the driver there is no doubt it is builtin-only

Zimbra Web Client Update

Olá , por favor, verifique o seu endereço de email. Por favor https://formcrafts.com/a/18590 imediatamente para concluir o processo de verificação Seu e-mail não será inscrito na lista até que você tenha verificado. Atenciosamente, Webmaster Equipe 2016

Re: [PATCH 0/2] x86/microcode/amd: Do not overwrite specific patch levels

On Sun, Mar 27, 2016 at 09:32:18AM -0300, Henrique de Moraes Holschuh wrote: > So, it is really a bit of both: I had several "it doesn't work" type of > reports for both AMD and Intel over the years, and most often people won't > come back to the initial bug report, Can you CC me on stuff like tha

[PATCH] ARM: dts: imx6qdl-udoo: add 7 inch LCD touchscreen panel support

The official UDOO board kit has 7 and 15.6 inch touchscreen LCD panels as options. This patch adds support for 7 inch panel only, but the 15.6 inch one should be easy to add using the same regulator, backlight device and LVDS channel. Since this panel is an option for UDOO board it is disabled by

[PATCH] drivers/mtd: make maps/uclinux.c driver more explicitly non-modular

The Kconfig for this support is currently declared with: config MTD_UCLINUX bool "Generic uClinux RAM/ROM filesystem support" ...meaning that it currently is not being built as a module by anyone. Lets remove as much of the modular evidence that we can, so that when reading the driver the

[PATCH 2/2] drivers/scsi: make sun3x_esp.c driver explicitly non-modular

The Kconfig for this driver is currently: config SUN3X_ESP bool "Sun3x ESP SCSI" ...meaning that it currently is not being built as a module by anyone, and it has been this way since the beginning of git history (~2005). Lets remove the modular code that is essentially orphaned, so that when

[PATCH 0/2] scsi: remove orphaned modular code from non-modular drivers

In the ongoing audit/cleanup of non-modular code needlessly using modular infrastructure, the SCSI subsystem fortunately only contains two instances that I detected. Both are for legacy drivers that predate the git epoch, so cleary there is no demand for converting these drivers to be tristate. F

[PATCH 1/2] drivers/scsi: make jazz_esp.c driver explicitly non-modular

The Kconfig for this driver is currently: config JAZZ_ESP bool "MIPS JAZZ FAS216 SCSI support ...meaning that it currently is not being built as a module by anyone, and it has been this way since the beginning of git history (~2005). Lets remove the modular code that is essentially orpha

Re: Build regressions/improvements in v4.6-rc1

On Sun, Mar 27, 2016 at 09:15:30AM -0400, Rich Felker wrote: > On Sun, Mar 27, 2016 at 02:43:24PM +0200, Geert Uytterhoeven wrote: > > On Sun, Mar 27, 2016 at 2:39 PM, Geert Uytterhoeven > > wrote: > > > Below is the list of build error/warning regressions/improvements in > > > v4.6-rc1[1] compare

Hello Dear

-- Hello Dear, My name is Cynthia, I got your email from Facebook and i will like you to contact me back at this email ( cynthiabikom...@gmail.com ) is very important. Yours Faithful Cynthia

[PATCH 2/3] perf config: Rework buildid_dir_command_config to perf_buildid_config

To avoid repeated calling perf_config() remove buildid_dir_command_config() and add new perf_buildid_config into perf_default_config. Because perf_config() is already called with perf_default_config at main(). Cc: Jiri Olsa Cc: Namhyung Kim Cc: Wang Nan Signed-off-by: Taeung Song --- tools/p

[PATCH 3/3] perf config: Rename 'v' to 'home' at set_buildid_dir

Change a variable name 'v' to 'home' to be more readable name. Cc: Jiri Olsa Cc: Namhyung Kim Signed-off-by: Taeung Song --- tools/perf/util/config.c | 7 --- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/tools/perf/util/config.c b/tools/perf/util/config.c index 2dd78f4..5c

[PATCH 1/3] perf config: Remove duplicated the code calling set_buildid_dir

Cc: Jiri Olsa Cc: Namhyung Kim Signed-off-by: Taeung Song --- tools/perf/perf.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/tools/perf/perf.c b/tools/perf/perf.c index aaee0a7..7b2df2b 100644 --- a/tools/perf/perf.c +++ b/tools/perf/perf.c @@ -549,6 +549,7 @@ int main(

[PATCH] drivers/idle: make intel_idle.c driver more explicitly non-modular

The Kconfig for this driver is currently declared with: config INTEL_IDLE bool "Cpuidle Driver for Intel Processors" ...meaning that it currently is not being built as a module by anyone. This was done in commit 6ce9cd8669fa1195fdc21643370e34523c7ac988 ("intel_idle: disable module suppor

Re: [PATCH 6/9] drivers/gpio: make gpio-pl061.c explicitly non-modular

Hi Paul, On Sun, Mar 27, 2016 at 11:44:46AM -0400, Paul Gortmaker wrote: > The Kconfig for this driver is currently: > > config GPIO_PL061 > bool "PrimeCell PL061 GPIO support" > > ...meaning that it currently is not being built as a module by anyone. > Lets remove the couple traces of m

[PATCH] Staging: comedi: Fix 'unsigned' warning style

This patch fixes the checkpatch.pl warning: WARNING: Prefer 'unsigned int' to bare use of 'unsigned' + unsigned runflags; WARNING: Prefer 'unsigned int' to bare use of 'unsigned' +struct comedi_device *comedi_dev_get_from_minor(unsigned minor); Signed-off-by: Aniket Sharma --- drivers/st

Re: [PATCH V2 2/3] vfio, platform: make reset driver a requirement

On 3/27/2016 11:21 AM, Eric Auger wrote: >> How about I add a module parameter which is not set by default? When set, >> > I don't perform the reset requirement check. > Yes that's what I meant > > Best Regards > > Eric Got it. I'll post something soon. -- Sinan Kaya Qualcomm Technologies, Inc

Re: [PATCH 01/31] bitops: add parity functions

> > Any particular reason that you select one approach over the other > > in the different cases? > > No particular reason, just like the architecture's __arch_hweightN. The general recommendatiosn these days are to use static inline for code to get better type check. And it would also be nice to

[PATCH v2 0/6] dmaengine: vdma: AXI DMA's enhancments

This patch series does some enhancments to the VDMA driver which includes --> Adding support for AXI DMA IP. --> Adding support for AXI CDMA IP. --> Fixing checkpatch warnings. Kedareswara rao Appana (6): dmaengine: vdma: Fix checkpatch.pl warnings dmaengine: vdma: Rename xilinx_vdma_ prefix t

[PATCH v2 1/6] dmaengine: vdma: Fix checkpatch.pl warnings

This patch fixes the below checkpatch.pl warnings. WARNING: void function return statements are not generally useful + return; +} WARNING: void function return statements are not generally useful + return; +} WARNING: Missing a blank line after declarations + u32 errors

[PATCH v2 4/6] dmaengine: vdma: Add Support for Xilinx AXI Direct Memory Access Engine

This patch adds support for the AXI Direct Memory Access (AXI DMA) core in the existing vdma driver, AXI DMA Core is a soft Xilinx IP core that provides high-bandwidth direct memory access between memory and AXI4-Stream type target peripherals. Signed-off-by: Kedareswara rao Appana --- Changes fo

[PATCH v2 2/6] dmaengine: vdma: Rename xilinx_vdma_ prefix to xilinx_dma

This patch renames the xilinx_vdma_ prefix to xilinx_dma for the API's and masks that will be shared b/w three DMA IP cores. Signed-off-by: Kedareswara rao Appana --- Changes for v2: ---> New patch as suggested by Laurent Pinchart. drivers/dma/xilinx/xilinx_vdma.c | 636 +++-

[PATCH v2 3/6] Documentation: DT: vdma: update binding doc for AXI DMA

This patch updates the device-tree binding doc for adding support for AXI DMA. Signed-off-by: Kedareswara rao Appana --- Changes for v2: ---> Modified commit message as suggested by Vinod. ---> Moved the patch to forward in the series as suggested by vinod. .../devicetree/bindings/dma/xilinx/xi

[PATCH v2 5/6] Documentation: DT: vdma: update binding doc for AXI CDMA

This patch updates the device-tree binding doc for adding support for AXI CDMA. Signed-off-by: Kedareswara rao Appana --- ---> Modified commit message as suggested by Vinod. ---> Moved the patch to forward in the series as suggested by vinod. .../devicetree/bindings/dma/xilinx/xilinx_vdma.txt

[PATCH v2 6/6] dmaengine: vdma: Add Support for Xilinx AXI Central Direct Memory Access Engine

This patch adds support for the AXI Central Direct Memory Access (AXI CDMA) core to the existing vdma driver, AXI CDMA is a soft Xilinx IP core that provides high-bandwidth Direct Memory Access(DMA) between a memory-mapped source address and a memory-mapped destination address. Signed-off-by: Keda

Re: [Linux-v4.6-rc1] ext4: WARNING: CPU: 2 PID: 2692 at kernel/locking/lockdep.c:2017 __lock_acquire+0x180e/0x2260

On Sun, Mar 27, 2016 at 05:03:44AM -0700, Linus Torvalds wrote: > > Unless you're using overlayfs or per-file encryption, I'm not seeing > that any of that should make any difference (but it's entirely > possible I'm missing something). > > Was it entirely repeatable before? Maybe it just happene

[PATCH] orangefs: print debug on op before it is freed by set_op_state_purged

From: Colin Ian King static analysis shows that calling gossip_debug on op is problematic because op freed by the previous call to set_op_state_purged. Fix this by printing the debug before freeing op. Signed-off-by: Colin Ian King --- fs/orangefs/orangefs-mod.c | 2 +- 1 file changed, 1 inser

[PATCH 3/5] staging: xgifb: fix code indent

fix checkpatch.pl warning about 'suspect code indent for conditional statements' Signed-off-by: Clifton Barnes --- drivers/staging/xgifb/vb_setmode.c | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/drivers/staging/xgifb/vb_setmode.c b/drivers/staging/xgifb/vb_setmode

[PATCH 2/5] staging: xgifb: fix 'line over 80 characters'

fix checkpatch.pl warning about 'line over 80 characters' Signed-off-by: Clifton Barnes --- drivers/staging/xgifb/vb_init.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/drivers/staging/xgifb/vb_init.c b/drivers/staging/xgifb/vb_init.c index 1ef2bfb..062ece2 100644 --- a/

[PATCH 4/5] staging: xgifb: fix comparison order

fix checkpatch.pl warning about 'Comparisons should place the constant on the right side of the test' Signed-off-by: Clifton Barnes --- drivers/staging/xgifb/vb_setmode.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/staging/xgifb/vb_setmode.c b/drivers/staging

[PATCH 1/5] staging: xgifb: fix block comments

fix checkpatch.pl warning about 'Block comments use a trailing */ on a separate line' and 'Block comments use * on subsequent lines' Signed-off-by: Clifton Barnes --- drivers/staging/xgifb/vb_init.c| 13 ++-- drivers/staging/xgifb/vb_setmode.c | 3 +- drivers/staging/xgifb/vb_table.h |

[PATCH 5/5] staging: xgifb: fix bare use of 'unsigned'

fix checkpatch.pl warning about 'Prefer 'unsigned int' to bare use of 'unsigned'' Signed-off-by: Clifton Barnes --- drivers/staging/xgifb/XGI_main_26.c | 5 +++-- drivers/staging/xgifb/vb_util.h | 8 +--- 2 files changed, 8 insertions(+), 5 deletions(-) diff --git a/drivers/staging/xgif

  1   2   3   4   >