Re: [PATCH 2/5] zram: partial IO refactoring

On 04/03/2017 09:12 AM, Minchan Kim wrote: > Hi Mika, > > On Mon, Apr 03, 2017 at 08:52:33AM +0300, Mika Penttilä wrote: >> >> Hi! >> >> On 04/03/2017 08:17 AM, Minchan Kim wrote: >>> For architecture(PAGE_SIZE > 4K), zram have supported partial IO. >>> However, the mixed code for handling normal/

Re: [PATCH] avr32/time: set ->min_delta_ticks and ->max_delta_ticks

Around Thu 30 Mar 2017 21:39:33 +0200 or thereabout, Nicolai Stange wrote: > In preparation for making the clockevents core NTP correction aware, > all clockevent device drivers must set ->min_delta_ticks and > ->max_delta_ticks rather than ->min_delta_ns and ->max_delta_ns: a > clockevent device's

Re: [RFC PATCH v2 4/4] ARM: sun8i: h3: add support for the thermal sensor in H3

On Sun, Apr 02, 2017 at 04:34:55PM +0200, Quentin Schulz wrote: > Hi Icenowy, > > On 02/04/2017 15:33, Icenowy Zheng wrote: > > As we have gained the support for the thermal sensor in H3, we can now > > add its device nodes to the device tree. > > > > Add them to the H3 device tree. > > > > The

[PATCH v2 0/1] fix perf build issue when ARCH=x86_64

From: Jiada Wang Jiada Wang (1): tools build: transform ARCH to supported values Changes from v2: added function purify-arch, transforms both HOSTARCH and ARCH to supported values tools/scripts/Makefile.arch |6 +- 1 file changed, 5 insertions(+), 1 deletion(-) -- 1.7.9.5

[PATCH v2 1/1] tools build: transform ARCH to supported values

From: Jiada Wang with commit: 0a943cb10ce7 (tools build: Add HOSTARCH Makefile variable) the following build failure is seen with ARCH=x86_84 In file included from util/event.c:2:0: tools/include/uapi/linux/mman.h:4:27: fatal error: uapi/asm/mman.h: No such file or directory compilation termina

Re: [Regression] Changes to i2c-piix4.c initialisation prevent loading of sp5100_tco watchdog driver on AMD SB800 chipset

Dear Zoltán, Am Samstag, den 01.04.2017, 12:13 +0200 schrieb Boszormenyi Zoltan: […] > and have split the patch into three pieces now (USB quirks, i2c-piix4 > and sp5100_tco) and they were sent to the relevant mailing lists. Could you please add me to the receiver list of these patches, so th

Re: [PATCH 3/5] zram: use zram_slot_lock instead of raw bit_spin_lock op

Hi Sergey, On Mon, Apr 03, 2017 at 03:08:58PM +0900, Sergey Senozhatsky wrote: > Hello Minchan, > > On (04/03/17 14:17), Minchan Kim wrote: > > With this clean-up phase, I want to use zram's wrapper function > > to lock table access which is more consistent with other zram's > > functions. > > w

Re: [PATCH] arm64: dts: uniphier: add input-delay properties to Cadence eMMC node

MTD developers, Please ignore this patch. I accidentally sent this patch to a wrong ML. Sorry for the noise. 2017-03-31 13:20 GMT+09:00 Masahiro Yamada : > Since commit a04e2b383401 ("mmc: sdhci-cadence: Update PHY delay > configuration"), PHY parameters must be specified by DT. > > The hard-c

Re: [PATCH 2/2] spi: spi-ti-qspi: Use bounce buffer if read buffer is not DMA'ble

On Monday 03 April 2017 05:03 AM, kbuild test robot wrote: > Hi Vignesh, > > [auto build test WARNING on spi/for-next] > [also build test WARNING on v4.11-rc4 next-20170331] > [if your patch is applied to the wrong git tree, please drop us a note to > help improve the system] > > url: > ht

Re: linux-next: build failure after merge of the vhost tree

Hi Michael, On Thu, 30 Mar 2017 15:25:58 +1100 Stephen Rothwell wrote: > > After merging the vhost tree, today's linux-next build (arm > multi_v7_defconfig) failed like this: > > drivers/remoteproc/remoteproc_virtio.c: In function 'rproc_virtio_find_vqs': > drivers/remoteproc/remoteproc_virtio.

Re: [Patch v3 10/11] [media] s5p-mfc: Add support for HEVC encoder (fwd)

On Mon, 2017-04-03 at 08:00 +0200, Julia Lawall wrote: > See line 2101 > > julia > Thank you for bringing it to my notice, I had not checked on this git. I will upload the next version of patches soon corresponding to this git. Thanks, Smitha > - Forwarded message -- > Date: Mon,

[no subject]

£1.5 Million Has Been Granted To You As A Donation Visit www.bbc.co.uk/news/uk-england-19254228 Sendname Address Phone for more info

[PATCH v2] staging: rtl8712: fixed multiple line derefence issue

Checkpatch emits WARNING: Avoid multiple line dereference. Checkpatch warning is fixed by: * Trivial indentation improvement and * Using += instead of + helps shortening the statement. Signed-off-by: Prasant Jalan --- v2: * Used += instead of + (pointed out by Joe Perches) * Rebased t

Re: [Patch v3 00/11] Add MFC v10.10 support

On Fri, 2017-03-31 at 15:29 +0200, Andrzej Hajda wrote: > Hi Smitha, > > On 31.03.2017 11:06, Smitha T Murthy wrote: > > This patch series adds MFC v10.10 support. MFC v10.10 is used in some > > of Exynos7 variants. > > Patch does not apply, please rebase on top of: > > > git://linuxtv.org/s

Re: [PATCH 2/5] zram: partial IO refactoring

Hi Mika, On Mon, Apr 03, 2017 at 08:52:33AM +0300, Mika Penttilä wrote: > > Hi! > > On 04/03/2017 08:17 AM, Minchan Kim wrote: > > For architecture(PAGE_SIZE > 4K), zram have supported partial IO. > > However, the mixed code for handling normal/partial IO is too mess, > > error-prone to modify I

Re: [PATCH 3/5] zram: use zram_slot_lock instead of raw bit_spin_lock op

Hello Minchan, On (04/03/17 14:17), Minchan Kim wrote: > With this clean-up phase, I want to use zram's wrapper function > to lock table access which is more consistent with other zram's > functions. which reminds me of... there was a discussion a long time ago, -rt people absolutely hate bit sp

Re: [PATCH] staging: rtl8712: fixed multiple line derefence issue

On Mon, Apr 3, 2017 at 10:27 AM, Joe Perches wrote: > On Mon, 2017-04-03 at 09:43 +0530, Prasant Jalan wrote: >> On Thu, Mar 30, 2017 at 12:03 AM, Prasant Jalan >> wrote: >> > Checkpatch emits WARNING: Avoid multiple line dereference. >> > >> > Trivial indentation improvement helps fix the check

Re: [git pull] vfs fixes

Al Viro writes: > On Sun, Apr 02, 2017 at 05:58:41PM -0700, Linus Torvalds wrote: > >> I had to go and double-check that "DCACHE_DIRECTORY_TYPE" is what >> d_can_lookup() actually checks, so _that_ part is perhaps a bit >> subtle, and might be worth noting in that comment that you edited. >> >>

Re: [Patch v3 10/11] [media] s5p-mfc: Add support for HEVC encoder (fwd)

See line 2101 julia - Forwarded message -- Date: Mon, 3 Apr 2017 05:04:39 +0800 From: kbuild test robot To: kbu...@01.org Cc: Julia Lawall Subject: Re: [Patch v3 10/11] [media] s5p-mfc: Add support for HEVC encoder Hi Smitha, [auto build test WARNING on linuxtv-media/master] [

Re: [PATCH 2/5] zram: partial IO refactoring

Hi! On 04/03/2017 08:17 AM, Minchan Kim wrote: > For architecture(PAGE_SIZE > 4K), zram have supported partial IO. > However, the mixed code for handling normal/partial IO is too mess, > error-prone to modify IO handler functions with upcoming feature > so this patch aims for cleaning up zram's I

Re: [RFC] mm/crypto: add tunable compression algorithm for zswap

On Sat, Apr 01, 2017 at 11:18:13PM +0200, Vlastimil Babka wrote: > Zswap (and zram) save memory by compressing pages instead of swapping them > out. This is nice, but with traditional compression algorithms such as LZO, > one cannot know, how well the data will compress, so the overal savings are >

Re: [PATCH] dwc2: gadget: Fix in control write transfers

Hi, On 3/30/2017 2:42 PM, Felipe Balbi wrote: > > Hi, > > Minas Harutyunyan writes: >> After data out stage gadget driver should not initate ZLP on control EP, >> because it is up to function driver. > > not true always, depends on return value from ->setup(). Which problem > did you have? Which

Re: [PATCH v2 3/4] usb: dwc3: add dual-role support

On 03/30/2017 02:27 AM, Felipe Balbi wrote: > > Hi > > Roger Quadros writes: > For something that simple, we wouldn't even need to use OTG FSM layer > because that brings no benefit for such a simple requirement. no no. I think you got it wrong. I'm not using the OTG FSM layer at

[PATCH v2 1/2] regulator: hi655x: Describe consumed platform device

The hi655x-regulator driver consumes a similarly named platform device. Adding that to the module device table, allows modprobe to locate this driver once the device is created. Signed-off-by: Jeremy Linton --- drivers/regulator/hi655x-regulator.c | 7 +++ 1 file changed, 7 insertions(+) di

[PATCH v2 0/2] Hi655x: mfd/pmic: regulator: Correct dependencies

In an environment where the hi655x pmic is being built as a standalone module, it fails to automatically load resulting in boot failures, machine hangs, etc. First we correct this by setting an appropriate module dependency. Then we bump the module use count on the mfd/pmic driver so that it canno

[PATCH v2 2/2] regulator: hi655x: Bump parent pmic module use count

The hi655x-regulator driver depends on the parent pmic/mfc device driver but doesn't increase its use count. This results in system crashes if the parent module is unloaded while the regulators are still in use. Add explicit module get/put calls to keep the parent from being unloaded. example cras

Re: dwc2_hc_chhltd_intr_dma - ChHltd set errors?

On 03/31/2017 04:04 PM, John Stultz wrote: > On Thu, Mar 2, 2017 at 12:00 PM, John Stultz wrote: >> Hey John, >> We've noticed that when using usb ethernet adapters on HiKey, we >> occasionally see errors like: >> >> dwc2 f72c.usb: dwc2_hc_chhltd_intr_dma: Channel 0 - ChHltd set, >> but reas

Re: [PATCH RFC] remove custom Michael MIC implementation

+ linux-wireless "Tobin C. Harding" writes: > On Fri, Mar 31, 2017 at 09:58:51AM +0200, Wolfram Sang wrote: >> >> > The code is untested, I have hardware in the mail. >> >> Cool! > > The card I have is a Spectec FCC ID: S2Y-WLAN-11B-G which I believe is > a SDW-823 and should use the ks7010 dr

[PATCH 0/5] zram clean up

This patchset aims zram clean-up. [1] clean up multiple pages's bvec handling. [2] clean up partial IO handling [3-5] clean up zram via using accessor and removing pointless structure. With [2-5] applied, we can get a few hundred bytes as well as huge readibility enhance. This patchset is based

Re: [PATCH] nios2: reserve boot memory for device tree

On Fri, 2017-03-31 at 11:40 +0200, Tobias Klauser wrote: > Make sure to reserve the boot memory for the flattened device tree. > Otherwise it might get overwritten, e.g. when initial_boot_params is > copied, leading to a corrupted FDT and a boot hang/crash: > >   bootconsole [early0] enabled >   E

[PATCH 3/5] zram: use zram_slot_lock instead of raw bit_spin_lock op

With this clean-up phase, I want to use zram's wrapper function to lock table access which is more consistent with other zram's functions. Signed-off-by: Minchan Kim --- drivers/block/zram/zram_drv.c | 42 -- 1 file changed, 28 insertions(+), 14 deletions(

[PATCH 1/5] zram: handle multiple pages attached bio's bvec

Johannes Thumshirn reported system goes the panic when using NVMe over Fabrics loopback target with zram. The reason is zram expects each bvec in bio contains a single page but nvme can attach a huge bulk of pages attached to the bio's bvec so that zram's index arithmetic could be wrong so that ou

[PATCH 4/5] zram: remove zram_meta structure

It's redundant now. Instead, remove it and use zram structure directly. Signed-off-by: Minchan Kim --- drivers/block/zram/zram_drv.c | 163 +- drivers/block/zram/zram_drv.h | 6 +- 2 files changed, 65 insertions(+), 104 deletions(-) diff --git a/drivers

[PATCH 2/5] zram: partial IO refactoring

For architecture(PAGE_SIZE > 4K), zram have supported partial IO. However, the mixed code for handling normal/partial IO is too mess, error-prone to modify IO handler functions with upcoming feature so this patch aims for cleaning up zram's IO handling functions. Signed-off-by: Minchan Kim --- d

[PATCH 5/5] zram: introduce zram data accessor

With element, sometime I got confused handle and element access. It might be my bad but I think it's time to introduce accessor to prevent future idiot like me. This patch is just clean-up patch so it shouldn't change any behavior. Signed-off-by: Minchan Kim --- drivers/block/zram/zram_drv.c | 3

Re: + zram-factor-out-partial-io-routine.patch added to -mm tree

Hi Andrew, Could you drop this patchset because I will send new patchset to replace this. Thanks. On Wed, Mar 29, 2017 at 03:25:32PM -0700, a...@linux-foundation.org wrote: > > The patch titled > Subject: zram: factor out partial IO routine > has been added to the -mm tree. Its filename i

Re: [PATCH] zram: set physical queue limits to avoid array out of bounds accesses

Hi Jens, On Thu, Mar 30, 2017 at 07:38:26PM -0600, Jens Axboe wrote: > On 03/30/2017 05:45 PM, Minchan Kim wrote: > > On Thu, Mar 30, 2017 at 09:35:56AM -0600, Jens Axboe wrote: > >> On 03/30/2017 09:08 AM, Minchan Kim wrote: > >>> Hi Jens, > >>> > >>> It seems you miss this. > >>> Could you handl

Re: [PATCH net-next v3 5/5] net-next: dsa: add dsa support for Mediatek MT7530 switch

Hi Sean, [auto build test ERROR on net-next/master] url: https://github.com/0day-ci/linux/commits/sean-wang-mediatek-com/net-next-dsa-add-Mediatek-MT7530-support/20170330-135532 config: m68k-allmodconfig (attached as .config) compiler: m68k-linux-gcc (GCC) 4.9.0 reproduce: wget https

Re: [PATCH] staging: rtl8712: fixed multiple line derefence issue

On Mon, 2017-04-03 at 09:43 +0530, Prasant Jalan wrote: > On Thu, Mar 30, 2017 at 12:03 AM, Prasant Jalan > wrote: > > Checkpatch emits WARNING: Avoid multiple line dereference. > > > > Trivial indentation improvement helps fix the checkpatch warning. [] > > diff --git a/drivers/staging/rtl8712/

Re: [RFC 1/8] Introduce Peer-to-Peer memory (p2pmem) device

On 02/04/17 03:03 PM, Sinan Kaya wrote: > Push the decision all the way to the user. Let them decide whether they > want this feature to work on a root port connected port or under the > switch. Yes, I prefer this too. If other folks agree with that I'd be very happy to go back to user chooses.

Re: [RFC PATCH 0/4] fs: introduce new writeback error tracking infrastructure and convert ext4 to use it

On Fri, Mar 31 2017, Jeff Layton wrote: > During LSF/MM this year, we had a discussion about the current sorry > state of writeback error reporting, and what could be done to improve > the situation. This patchset represents a first pass at the proposal > I made there. > > It first adds a new set

Re: [RFCv2] arm64: support HAVE_ARCH_RARE_WRITE and HAVE_ARCH_RARE_WRITE_MEMCPY

> On 31 Mar 2017, at 6:25 PM, Ard Biesheuvel wrote: > > On 30 March 2017 at 15:39, Hoeun Ryu wrote: >> This patch might be a part of Kees Cook's rare_write infrastructure series >> for [1] for arm64 architecture. >> >> This implementation is based on Mark Rutland's suggestions [2], which is >>

Re: [PATCH] staging: rtl8712: fixed multiple line derefence issue

On Thu, Mar 30, 2017 at 12:03 AM, Prasant Jalan wrote: > Checkpatch emits WARNING: Avoid multiple line dereference. > > Trivial indentation improvement helps fix the checkpatch warning. > > Signed-off-by: Prasant Jalan > --- > drivers/staging/rtl8712/rtl871x_xmit.c | 12 ++-- > 1 file ch

arch/x86/kernel/ftrace.c:35:3: error: #error The following combination is not supported: ((compiler missing -mfentry) || (CONFIG_X86_32 and !CONFIG_DYNAMIC_FTRACE)) && CONFIG_FUNCTION_GRAPH_TRACER &&

tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: a71c9a1c779f2499fb2afc0553e543f18aff6edf commit: 3f135e57a4f76d24ae8d8a490314331f0ced40c5 x86/build: Mostly disable '-maccumulate-outgoing-args' date: 4 days ago config: x86_64-randconfig-a0-04031038 (atta

Re: [PATCH] mm: Add additional consistency check

Kees Cook writes: > On Fri, Mar 31, 2017 at 2:33 PM, Andrew Morton > wrote: >> On Fri, 31 Mar 2017 09:40:28 -0700 Kees Cook wrote: >> >>> As found in PaX, this adds a cheap check on heap consistency, just to >>> notice if things have gotten corrupted in the page lookup. >> >> "As found in PaX"

linux-next: build failure after merge of the drm-misc tree

Hi all, After merging the drm-misc tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/gpu/drm/vmwgfx/vmwgfx_scrn.c: In function 'vmw_sou_crtc_page_flip': drivers/gpu/drm/vmwgfx/vmwgfx_scrn.c:327:8: error: too few arguments to function 'drm_atomic_helper_page_flip' r

Re: [PATCH v6 0/4] phy: USB and PCIe phy drivers for Qcom chipsets

On 03/20/2017 07:24 PM, Vivek Gautam wrote: This patch series adds couple of PHY drivers for Qualcomm chipsets. a) qcom-qusb2 phy driver: that provides High Speed USB functionality. b) qcom-qmp phy driver: that is a combo phy providing support for USB3, PCIe, UFS and few other controllers.

Re: [RFCv2] arm64: support HAVE_ARCH_RARE_WRITE and HAVE_ARCH_RARE_WRITE_MEMCPY

> On Mar 31, 2017, at 4:38 AM, Kees Cook wrote: > >> On Thu, Mar 30, 2017 at 7:39 AM, Hoeun Ryu wrote: >> This patch might be a part of Kees Cook's rare_write infrastructure series >> for [1] for arm64 architecture. >> >> This implementation is based on Mark Rutland's suggestions [2], which is

linux-next: manual merge of the drm-misc tree with the drm tree

Hi all, Today's linux-next merge of the drm-misc tree got conflicts in: drivers/gpu/drm/vmwgfx/vmwgfx_stdu.c drivers/gpu/drm/vmwgfx/vmwgfx_scrn.c drivers/gpu/drm/vmwgfx/vmwgfx_ldu.c between commits: 904bb5e5817f ("drm/vmwgfx: Switch over to internal atomic API for STDU") b0119cb9229d

Re: [PATCH v3 14/37] mtd: nand: denali: support "nand-ecc-strength" DT property

Hi Boris, 2017-03-31 18:46 GMT+09:00 Boris Brezillon : > You can try something like that when no explicit ecc.strength and > ecc.size has been set in the DT and when ECC_MAXIMIZE was not passed. > > static int > denali_get_closest_ecc_strength(struct denali_nand_info *denali, >

Re: [PATCH] phy: bcm-ns-usb3: split all writes into reg & val pairs

On Sun, Apr 2, 2017 at 12:55 PM, Rafał Miłecki wrote: > From: Rafał Miłecki > > So far all the PHY initialization was implemented using some totally > magic values. There was some pattern there but it wasn't clear what is > it about. > > Thanks to the patch submitted by Broadcom: > [PATCH 5/6] ph

Re: [kbuild-all] [PATCH] net: hns: fix boolreturn.cocci warnings

Hi David, On Sun, Apr 02, 2017 at 07:44:02PM -0700, David Miller wrote: From: kbuild test robot Date: Sat, 1 Apr 2017 07:50:55 +0800 drivers/net/ethernet/hisilicon/hns/hns_enet.c:1548:8-9: WARNING: return of 0/1 in function 'hns_enable_serdes_lb' with return type bool Return statements in

Re: [PATCH] net: hns: fix boolreturn.cocci warnings

From: kbuild test robot Date: Sat, 1 Apr 2017 07:50:55 +0800 > drivers/net/ethernet/hisilicon/hns/hns_enet.c:1548:8-9: WARNING: return of > 0/1 in function 'hns_enable_serdes_lb' with return type bool > > Return statements in functions returning bool should use > true/false instead of 1/0. >

Re: [PATCH] phy/ethtool: Add missing SPEED_ strings

On Sun, 2017-04-02 at 15:29 -0700, Florian Fainelli wrote: > Le 04/02/17 à 14:30, Joe Perches a écrit : > > Add all the currently available SPEED_ strings. > > > > Signed-off-by: Joe Perches > > Considering that PHYLIB does not support anything > 10Gbs at the moment, > I am not sure how useful t

Re: [PATCH] net: ethernet: ti: cpsw: wake tx queues on ndo_tx_timeout

From: Grygorii Strashko Date: Fri, 31 Mar 2017 18:41:23 -0500 > In case, if TX watchdog is fired some or all netdev TX queues will be > stopped and as part of recovery it is required not only to drain and > reinitailize CPSW TX channeles, but also wake up stoppted TX queues what > doesn't happen

Re: linux-next: build warning after merge of the nfsd tree

On Mon, Apr 03, 2017 at 11:09:48AM +1000, Stephen Rothwell wrote: > Hi, > > After merging the nfsd tree, today's linux-next build (powerpc > ppc64_defconfig) produced this warning: > > fs/nfsd/nfs4state.c: In function 'copy_cred': > fs/nfsd/nfs4state.c:1917:6: warning: unused variable 'ret' [-Wun

Re: [git pull] vfs fixes

On Sun, Apr 02, 2017 at 05:58:41PM -0700, Linus Torvalds wrote: > I had to go and double-check that "DCACHE_DIRECTORY_TYPE" is what > d_can_lookup() actually checks, so _that_ part is perhaps a bit > subtle, and might be worth noting in that comment that you edited. > > So the real "rule" ends up

linux-next: manual merge of the net-next tree with the net tree

Hi all, Today's linux-next merge of the net-next tree got conflicts in: tools/testing/selftests/bpf/Makefile tools/testing/selftests/bpf/test_verifier.c between commit: 02ea80b1850e ("bpf: add various verifier test cases for self-tests") from the net tree and commits: 6882804c916b ("s

Re: [PATCH v2] usb: dwc2: Make sure we disconnect the gadget state

On 03/29/2017 08:23 PM, John Stultz wrote: > I had seen some odd behavior with HiKey's usb-gadget interface > that I finally seemed to have chased down. Basically every other > time I plugged in the OTG port, the gadget interface would > properly initialize. The other times, I'd get a big WARN_ON >

Re: [PATCH v4 3/5] watchdog: iTCO_wdt: Add PMC specific noreboot update api

Hi, On Sun, Apr 2, 2017 at 7:04 AM, Andy Shevchenko wrote: > On Sat, Apr 1, 2017 at 2:27 AM, Kuppuswamy Sathyanarayanan > wrote: >> In some SOCs, setting noreboot bit needs modification to > > SoCs. > > Perhaps you can create a wikipage to share with your team what style > issues usually needs t

Re: [PATCH v4 4/5] platform/x86: intel_pmc_ipc: Fix iTCO GCS memory mapping failure

Hi Andy, On Sun, Apr 2, 2017 at 7:10 AM, Andy Shevchenko wrote: > On Sat, Apr 1, 2017 at 2:27 AM, Kuppuswamy Sathyanarayanan > wrote: >> iTCO watchdog driver need access to PMC_CFG GCR register to modify > > iTCO_wdt or use above in the rest of the series. > > So, choose one and use it everywh

Re: [PATCH v4 1/5] platform/x86: intel_pmc_ipc: fix gcr offset

Yes, just applying this patch will fix the existing offset issue. On Sun, Apr 2, 2017 at 7:11 AM, Andy Shevchenko wrote: > On Sat, Apr 1, 2017 at 2:27 AM, Kuppuswamy Sathyanarayanan > wrote: >> According to Broxton APL PMC spec, gcr mem region starts >> at offset 0x1000 from ipc mem base address

Re: [PATCH v4 2/5] platform/x86: intel_pmc_ipc: Add pmc gcr read/write/update api's

Hi Andy, Thanks for your comments. On Sun, Apr 2, 2017 at 6:58 AM, Andy Shevchenko wrote: > On Sat, Apr 1, 2017 at 2:27 AM, Kuppuswamy Sathyanarayanan > wrote: >> This patch adds API's to read/write/update PMC GC registers. >> PMC dependent devices like iTCO_WDT, Telemetry has requirement > > i

Linux 4.11-rc5

Ok, things have definitely started to calm down, let's hope it stays this way and it wasn't just a fluke this week. Things look fairly normal, with just under 60% of the changes in drivers (edac, sound, block, pci, etc), and about 30% in arch updates (some misc ptrace fixes, random stuff). The on

Re: Updating sunxi tree in linux-next

Hi Stephen, On Mon, Apr 3, 2017 at 7:56 AM, Stephen Rothwell wrote: > Hi Maxime, > > On Fri, 31 Mar 2017 09:57:29 +0200 Maxime Ripard > wrote: >> >> We've switched from my personal git tree for the Allwinner sunxi >> development to a shared tree: >> git://git.kernel.org/pub/scm/linux/kernel/git

[PATCH] loop: Add PF_LESS_THROTTLE to block/loop device thread.

When a filesystem is mounted from a loop device, writes are throttled by balance_dirty_pages() twice: once when writing to the filesystem and once when the loop_handle_cmd() writes to the backing file. This double-throttling can trigger positive feedback loops that create significant delays. The

Re: [PATCH net-next v3 5/5] net-next: dsa: add dsa support for Mediatek MT7530 switch

Hi Sean, [auto build test ERROR on net-next/master] url: https://github.com/0day-ci/linux/commits/sean-wang-mediatek-com/net-next-dsa-add-Mediatek-MT7530-support/20170330-135532 config: arm-allmodconfig (attached as .config) compiler: arm-linux-gnueabi-gcc (Debian 6.1.1-9) 6.1.1 20160705 repr

Re: [PATCH] i2c: use void pointers for supplying data for reads and writes

Hi Dmitry, [auto build test ERROR on wsa/i2c/for-next] [also build test ERROR on v4.11-rc4 next-20170331] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Dmitry-Torokhov/i2c-use-void-pointers-for

linux-next: build warning after merge of the nfsd tree

Hi, After merging the nfsd tree, today's linux-next build (powerpc ppc64_defconfig) produced this warning: fs/nfsd/nfs4state.c: In function 'copy_cred': fs/nfsd/nfs4state.c:1917:6: warning: unused variable 'ret' [-Wunused-variable] int ret; ^ Introduced by commit d39662236bf8 ("nfsd4:

Re: [PATCH v2 0/5] minitty: a minimal TTY layer alternative for embedded systems

On Mon, 3 Apr 2017, Stuart Longland wrote: > On 03/04/17 07:41, Nicolas Pitre wrote: > >> No PTYs seems like a big limitation. This means no sshd? > > Again, my ultimate system target is in the sub-megabyte of RAM. I > > really doubt you'll be able to fit an SSH server in there even if PTYs > >

Re: [PATCH] i2c: use void pointers for supplying data for reads and writes

Hi Dmitry, [auto build test WARNING on wsa/i2c/for-next] [also build test WARNING on v4.11-rc4 next-20170331] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Dmitry-Torokhov/i2c-use-void-pointers

Re: [git pull] vfs fixes

On Sun, Apr 2, 2017 at 5:43 PM, Al Viro wrote: > > Do you have any objections against the following (still untested) variant? > I don't see any point in checking for flags & LOOKUP_RCU in case of !*s - > flags is in register at that point, so... Looks sane to me. I had to go and double-check tha

Re: [git pull] vfs fixes

On Mon, Apr 03, 2017 at 01:30:45AM +0100, Al Viro wrote: > Currently true and almost certainly will remain so. Point taken, what you > are suggesting is better. Actually, the invariant to watch for is > "no d_can_lookup() withtout DCACHE_RCUACCESS" and that we can trivially > enforce by one-line

Re: [git pull] vfs fixes

On Sun, Apr 02, 2017 at 05:10:08PM -0700, Linus Torvalds wrote: > On Sun, Apr 2, 2017 at 4:59 PM, Linus Torvalds > wrote: > > On Sun, Apr 2, 2017 at 10:01 AM, Al Viro wrote: > >> statx followup fixes, fix for a nasty corner case in path_init() > >> leaving path.dentry in RCU mode pointing

Re: [git pull] vfs fixes

On Sun, Apr 02, 2017 at 04:59:10PM -0700, Linus Torvalds wrote: > On Sun, Apr 2, 2017 at 10:01 AM, Al Viro wrote: > > statx followup fixes, fix for a nasty corner case in path_init() > > leaving path.dentry in RCU mode pointing to a dentry without > > DCACHE_RCUACCESS > > and a fix for st

Re: Patch for drivers/usb/serial/ch341.c enabling parity

On Sun, Apr 2, 2017 at 3:00 PM, Leif Neland wrote: > There is a patch > > https://github.com/karlp/ch341-linux/blob/master/0001-usb-serial-ch341-Add-parity-support.patch > > which enables parity selection for the ch341 USB-RS485 adapter. > > From: Karl Palsson > Date: Tue, 18 Mar 2014 23:33:27 +0

Re: [git pull] vfs fixes

On Sun, Apr 2, 2017 at 4:59 PM, Linus Torvalds wrote: > On Sun, Apr 2, 2017 at 10:01 AM, Al Viro wrote: >> statx followup fixes, fix for a nasty corner case in path_init() >> leaving path.dentry in RCU mode pointing to a dentry without DCACHE_RCUACCESS >> and a fix for stack-smashing on a

Re: [git pull] vfs fixes

On Sun, Apr 2, 2017 at 10:01 AM, Al Viro wrote: > statx followup fixes, fix for a nasty corner case in path_init() > leaving path.dentry in RCU mode pointing to a dentry without DCACHE_RCUACCESS > and a fix for stack-smashing on alpha. These were apparently committed minutes before sendin

Re: Updating sunxi tree in linux-next

Hi Maxime, On Fri, 31 Mar 2017 09:57:29 +0200 Maxime Ripard wrote: > > We've switched from my personal git tree for the Allwinner sunxi > development to a shared tree: > git://git.kernel.org/pub/scm/linux/kernel/git/sunxi/linux.git > > The branch to be included in linux-next will still be calle

Re: sun50i-a64-pinctrl WARN_ON drivers/base/dd.c:349

Hi, On 17/03/17 14:44, Tejun Heo wrote: > On Fri, Mar 17, 2017 at 10:28:34PM +0800, Icenowy Zheng wrote: >>> It's warning that the device has resources associated with it on >>> probe. There gotta be something fishy going on with the probing >>> sequence. How reproducible is the problem? >> >> Do

Re: [PATCH] x86/lguest/timer: set ->min_delta_ticks and ->max_delta_ticks

Nicolai Stange writes: > In preparation for making the clockevents core NTP correction aware, > all clockevent device drivers must set ->min_delta_ticks and > ->max_delta_ticks rather than ->min_delta_ns and ->max_delta_ns: a > clockevent device's rate is going to change dynamically and thus, the

Re: [PATCH 2/2] spi: spi-ti-qspi: Use bounce buffer if read buffer is not DMA'ble

Hi Vignesh, [auto build test WARNING on spi/for-next] [also build test WARNING on v4.11-rc4 next-20170331] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Vignesh-R/spi-ti-qspi-Handle-vmalloc-d-b

[tip:x86/platform 1/1] platform_bt.c:undefined reference to `gpiod_add_lookup_table'

tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/platform head: d4d969909bef4c1e103eec0fc2c820773811fb72 commit: d4d969909bef4c1e103eec0fc2c820773811fb72 [1/1] x86/platform/intel-mid: Enable Bluetooth support on Intel Edison config: x86_64-randconfig-s4-04030434 (attached

Re: [PATCH] tcmu: Skip Data-Out blocks before gathering Data-In buffer for BIDI case

On Fri, 2017-03-31 at 10:35 +0800, lixi...@cmss.chinamobile.com wrote: > From: Xiubo Li > > For the bidirectional case, the Data-Out buffer blocks will always at > the head of the tcmu_cmd's bitmap, and before gathering the Data-In > buffer, first of all it should skip the Data-Out ones, or the d

4.10.8 OOPS - BUG: unable to handle kernel NULL pointer dereference; IP: _raw_spin_lock+0x13/0x30

I'm running kernel 4.10.8-3.gea9dcd4 (from Opensuse's Kernel:Stable repo) on an Atom D525 box. I just noticed an OOPS on *shutdown*; Since it autoreboots, *boots* without problem, and I hadn't been paying attention until now, I can't say how long this has been occurring. On this box I follow

[RFC][PATCH v2 5/5] signal: Don't allow accessing signal_struct by old threads after exec

Add exec_id to signal_struct and compare it at a few choice moments. I believe this closes the security holes that letting the zombie threads linger after exec opens up. The problem is that old threads may have different creds after a setuid exec, and then formerly shared resources may change.

[RFC][PATCH v2 4/5] exec: If possible don't wait for ptraced threads to be reaped

Take advantage of the situation when sighand->count == 1 to only wait for threads to reach EXIT_ZOMBIE instead of EXIT_DEAD in de_thread. Only old old linux threading libraries use CLONE_SIGHAND without CLONE_THREAD. So this situation should be present most of the time. This allows ptracing thro

[RFC][PATCH v2 3/5] clone: Disallown CLONE_THREAD with a shared sighand_struct

Old threading libraries used CLONE_SIGHAND without clone thread. Modern threadding libraries always use CLONE_SIGHAND | CLONE_THREAD. Therefore let's simplify our lives and stop supporting a case no one cares about. Signed-off-by: "Eric W. Biederman" --- kernel/fork.c | 7 +++ 1 file chan

[RFC][PATCH v2 2/5] sighand: Count each thread group once in sighand_struct

In practice either a thread group is either using a sighand_struct or it isn't. Therefore simplify things a bit and only increment the count in sighand_struct when a new thread group is created that uses the existing sighand_struct, and only decrement the count in sighand_struct when a thread gro

[RFC][PATCH v2 1/5] ptrace: Don't wait in PTRACE_O_TRACEEXIT for exec or coredump

Take advantage of the fact that no ptrace stop will wait for a debugger if another process sends SIGKILL to the waiting task. In the case of exec and coredump which have many interesting deadlock opportunities and no one tests the what happens if you are ptraced during exec or coredump act like a

[RFC][PATCH v2 0/5] exec: Fixing ptrace'd mulit-threaded hang

Oleg your comment about kill being able to send signal was an important dimension I had missed thank you. This patchset just denies the case of SIGHAND between different multi-threaded processes as I don't think anyone cares. I can fix that if anyone cares but I am not certain we actally do. I

Re: [PATCH v2 0/5] minitty: a minimal TTY layer alternative for embedded systems

On 03/04/17 07:41, Nicolas Pitre wrote: >> No PTYs seems like a big limitation. This means no sshd? > Again, my ultimate system target is in the sub-megabyte of RAM. I > really doubt you'll be able to fit an SSH server in there even if PTYs > were supported, unless sshd (or dropbear) can be made

Re: [PATCH 1/2] iscsi-target: Fix TMR reference leak during session shutdown

On Thu, 2017-03-30 at 17:08 +, Bart Van Assche wrote: > On Thu, 2017-03-30 at 08:29 +, Nicholas A. Bellinger wrote: > > diff --git a/drivers/target/iscsi/iscsi_target_util.c > > b/drivers/target/iscsi/iscsi_target_util.c > > index 5041a9c..b464033 100644 > > --- a/drivers/target/iscsi/iscs

Re: [PATCH] arm64: dts: hi6220: enable DMA in spi0

Hi Wang, [auto build test ERROR on robh/for-next] [also build test ERROR on v4.11-rc4] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Guodong-Xu/arm64-dts-hi6220-enable-DMA-in-spi0/20170323-1001

Re: [PATCH] phy/ethtool: Add missing SPEED_ strings

Le 04/02/17 à 14:30, Joe Perches a écrit : > Add all the currently available SPEED_ strings. > > Signed-off-by: Joe Perches Considering that PHYLIB does not support anything > 10Gbs at the moment, I am not sure how useful that is except if we wanted to re-use phy_speed_to_str() in other places o

Re: [PATCH] phy/ethtool: Add missing SPEED_ strings

On Sun, 2017-04-02 at 23:40 +0200, Andrew Lunn wrote: > On Sun, Apr 02, 2017 at 02:30:06PM -0700, Joe Perches wrote: > > Add all the currently available SPEED_ strings. [] > > diff --git a/include/uapi/linux/ethtool.h b/include/uapi/linux/ethtool.h [] > > @@ -1487,6 +1487,7 @@ enum ethtool_link_mod

Re: [PATCH] kbuild, LLVMLinux: Add -Werror to cc-option to support clang

Hi Arnd, 2017-04-01 5:38 GMT+09:00 Arnd Bergmann : > From: Mark Charlebois > > Clang will warn about unknown warnings but will not return false > unless -Werror is set. GCC will return false if an unknown > warning is passed. > > Adding -Werror make both compiler behave the same. > > [arnd: it t

Re: [PATCH v2 0/5] minitty: a minimal TTY layer alternative for embedded systems

On Sun, 2 Apr 2017, Andi Kleen wrote: > Nicolas Pitre writes: > > > > Of course, making it "mini" means there are limitations to what it does: > > > > - This supports serial ports only. No VT's, no PTY's. > > No PTYs seems like a big limitation. This means no sshd? Again, my ultimate system tar

Re: [PATCH] phy/ethtool: Add missing SPEED_ strings

On Sun, Apr 02, 2017 at 02:30:06PM -0700, Joe Perches wrote: > Add all the currently available SPEED_ strings. > > Signed-off-by: Joe Perches > --- > drivers/net/phy/phy.c| 14 ++ > include/uapi/linux/ethtool.h | 1 + > 2 files changed, 15 insertions(+) > > diff --git a/dri

`iwlist scan` fails with many networks available

I've spent the past few days in a large hotel and noticed that `iwlist scan` fails with the error message "Argument list too long". This seems to be because there are a great many wireless networks in my vicinity. See: https://bugzilla.kernel.org/show_bug.cgi?id=16384 Using `iw` as recommended

  1   2   3   >