Re: x86_64: MAX_LOCAL_APIC way too big?

On 09/25/2015 06:56 PM, Jiang Liu wrote: > On 2015/9/26 0:16, Denys Vlasenko wrote: >> 32 thousand APICs? That's a lot. Especially >> considering that event with CONFIG_MAXSMP=y, >> NR_CPUS is "only" 8096. >> >> After a quick glance through code, it looks like >> such a big value causes several

Re: [RFC PATCH] PM / Runtime: runtime: Add sysfs option for forcing runtime suspend

On Friday, September 25, 2015 10:29:55 AM Alan Stern wrote: > On Fri, 25 Sep 2015, Rafael J. Wysocki wrote: > > > We are missing the "no remote wakeup" bit now (well, there is a PM QoS flag, > > but it isn't very useful, so I'd prefer to replace it with a "no remote > > wakeup" > > bit in struct

Re: [PATCH V4 1/2] ACPI / EC: Fix broken 64bit big-endian users of 'global_lock'

On Friday, September 25, 2015 10:18:13 PM Rafael J. Wysocki wrote: > On Friday, September 25, 2015 09:41:37 AM Viresh Kumar wrote: > > global_lock is defined as an unsigned long and accessing only its lower > > 32 bits from sysfs is incorrect, as we need to consider other 32 bits > > for big

Re: [PATCH V4 1/2] ACPI / EC: Fix broken 64bit big-endian users of 'global_lock'

> Rafael wrote: > > Actually, what about adding a local u32 variable, say val, here and > > doing > > > > > if (!debugfs_create_x32("gpe", 0444, dev_dir, (u32 > > > *)_ec->gpe)) > > > goto error; > > > if (!debugfs_create_bool("use_global_lock", 0444, > > > dev_dir, > > > -

[PATCH] gpio: omap: fix static checker warning

This patch fixes below static checker warning by changing type of irq field in struct gpio_bank from u16 to int. drivers/gpio/gpio-omap.c:1191 omap_gpio_probe() warn: assigning (-6) to unsigned variable 'bank->irq' drivers/gpio/gpio-omap.c 1188 bank->irq =

[PATCH] Clk: tegra: Use module_platform_driver

Use module_platform_driver for drivers whose init and exit functions only register and unregister, respectively. Coccinelle patch used- @a@ identifier f, x; @@ -static f(...) { return platform_driver_register(); } @b depends on a@ identifier e, a.x; @@ -static e(...) {

Re: [PATCH 03/16] page-flags: introduce page flags policies wrt compound pages

t; >+page = compound_head(page); \ > >+page;}) > >+#define PF_NO_COMPOUND(page, enforce) ({ > >\ > >+if (enforce)\ > >+

[PATCH V2 2/3] RAS, mce_amd_inj: Add capability to trigger apic interrupts

With this extension to the flags attribute, deferred error interrupts and threshold interrupts can be triggered to test the apic interrupt handler functionality for these type of errors Update README section about the same too. Signed-off-by: Aravind Gopalakrishnan

Re: [PATCH] xen/pvhvm: add soft reset on kexec/kdump support

On 09/25/2015 03:01 PM, Konrad Rzeszutek Wilk wrote: On Fri, Sep 25, 2015 at 01:17:40PM -0400, Boris Ostrovsky wrote: On 09/25/2015 12:07 PM, Vitaly Kuznetsov wrote: Also, I am not sure I see how this new op will be used in the hypervisor --- currently AFAICS it is only processed under

Re: [PATCH 09/10] mm, page_alloc: Reserve pageblocks for high-order atomic allocations on demand

On Mon, Sep 21, 2015 at 11:52:41AM +0100, Mel Gorman wrote: > High-order watermark checking exists for two reasons -- kswapd high-order > awareness and protection for high-order atomic requests. Historically the > kernel depended on MIGRATE_RESERVE to preserve min_free_kbytes as high-order > free

[PATCH 0/2] convert to use generic irq handler

This patch series contains patches which fixes wrong APIs usage in atomic context on RT-kernel. The final goal is to make TI OMAP GPIO driver compatible with -RT kernel as much as possible. Patch 1: required to be compatible with -RT kernel, because PM runtime's irq_safe mode is incompatible with

[PATCH 2/2] gpio: omap: convert to use generic irq handler

This patch converts TI OMAP GPIO driver to use generic irq handler instead of chained IRQ handler. This way OMAP GPIO driver will be compatible with RT kernel where it will be forced thread IRQ handler while in non-RT kernel it still will be executed in HW IRQ context. As part of this change the

[PATCHv4 2/3] devicetree: Add new ANX7814 SlimPort transmitter binding.

The ANX7814 is an ultra-low power Full-HD (1080p60) SlimPort transmitter designed for portable devices. You can add support to your board with current binding. Example: anx7814: anx7814@38 { compatible = "analogix,anx7814"; reg = <0x38>;

[PATCHv4 0/3] Add initial support for slimport anx78xx

Hi all, This is the fouth version with fixes suggested by Nicolas Boichat and Dan Carpenter. See the changelog below for details. The following series add initial support for the Slimport ANX7814 transmitter, a ultra-low power Full-HD (1080p60) transmitter designed for portable device. The

Re: [PATCH net-next] net: remove unused argument of __netdev_find_adj()

From: Michal Kubecek Date: Thu, 24 Sep 2015 10:59:05 +0200 (CEST) > The __netdev_find_adj() helper does not use its first argument, only the > device to find and list to walk through. > > Signed-off-by: Michal Kubecek Applied, thank you. -- To unsubscribe

Re: [v3 2/8] dpaa_eth: add support for DPAA Ethernet

From: Madalin Bucur Date: Thu, 24 Sep 2015 18:00:13 +0300 > +#define DPA_NAPI_WEIGHT 64 This is just the default, so simply use "NAPI_POLL_WEIGHT" rather than defining your own macro unnecessarily for this. > +static int dpa_eth_priv_stop(struct

Re: [PATCH V4 1/2] ACPI / EC: Fix broken 64bit big-endian users of 'global_lock'

On Friday, September 25, 2015 09:41:37 AM Viresh Kumar wrote: > global_lock is defined as an unsigned long and accessing only its lower > 32 bits from sysfs is incorrect, as we need to consider other 32 bits > for big endian 64 bit systems. There are no such platforms yet, but the > code needs to

Re: [PATCH V4 1/2] ACPI / EC: Fix broken 64bit big-endian users of 'global_lock'

On Friday, September 25, 2015 11:52:56 AM Viresh Kumar wrote: > On 25-09-15, 20:49, Johannes Berg wrote: > > Ok, then, but that means Rafael is completely wrong ... > > debugfs_create_bool() takes a *pointer* and it needs to be long-lived, > > it can't be on the stack. You also don't get a call

Re: [PATCH V4 1/2] ACPI / EC: Fix broken 64bit big-endian users of 'global_lock'

On Friday, September 25, 2015 10:26:22 PM Rafael J. Wysocki wrote: > On Friday, September 25, 2015 11:52:56 AM Viresh Kumar wrote: > > On 25-09-15, 20:49, Johannes Berg wrote: > > > Ok, then, but that means Rafael is completely wrong ... > > > debugfs_create_bool() takes a *pointer* and it needs

Re: [Xen-devel] [PATCH] xen-blkback: free requests on disconnection

On Tue, Sep 22, 2015 at 12:10:18AM +0100, Julien Grall wrote: > Hi Konrad, > > On 09/09/2015 16:02, Konrad Rzeszutek Wilk wrote: > >>Konrad, would you like me to resend the patch with the modified commit > >>message, or do you plan to amend it yourself while committing? > > > >I will amend it.

Re: [RFC v7 31/41] nfsd: Add support for the v4.1 dacl attribute

2015-09-24 21:59 GMT+02:00 J. Bruce Fields : > I'd probably move this up top with the other ACL case. Okay. Thanks, Andreas -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info

[PATCH] platform: x86: PMC IPC depends on ACPI

This patch solves: on x86_64: when CONFIG_ACPI is not enabled: ../drivers/mfd/intel_soc_pmic_bxtwc.c: In function 'bxtwc_probe': ../drivers/mfd/intel_soc_pmic_bxtwc.c:342:2: error: implicit declaration of function 'acpi_evaluate_integer' [-Werror=implicit-function-declaration]

Re: [PATCH] gpio: ath79: Convert to the state container design pattern

On Tue, Sep 1, 2015 at 2:38 AM, Alban Bedel wrote: > Turn the ath79 driver into a true driver supporting multiple > instances. While at it also removed unneed includes and make use of > the BIT() macro. > > Signed-off-by: Alban Bedel > --- > > This patch apply on

Re: Voltage setting on chained regulators, how?

On Fri, Sep 25, 2015 at 11:07:24AM +0200, Sascha Hauer wrote: > Any idea how such a scenario could be implemented? The regulator > framework already has some idea of supply regulators, but it only takes > care of en/disabling the supplies and will not change the voltage on the > supplies. Should

Re: [PATCH] gpio:Fix error checking in the function device_pca957x_init

On Wed, Aug 26, 2015 at 2:52 PM, Nicholas Krause wrote: > This fixes error checking in the function device_pca957x_init > to properly check and return error code values from the calls > to the function pca953x_write_regs if they fail as to properly > signal callers when a

Re: [PATCH v3 1/1 RESEND] gpio: arizona: add support for WM8998 and WM1814

On Thu, Sep 10, 2015 at 8:59 AM, Richard Fitzgerald wrote: > Signed-off-by: Richard Fitzgerald > Acked-by: Linus Walleij OK dependencies are upstream, patch applied. Yours, Linus Walleij -- To

Re: [PATCH v4 3/7] fs: Verify access of user towards block device file when mounting

On Fri, Sep 25, 2015 at 12:16:59PM -0500, Eric W. Biederman wrote: > > Argh. This looks like morning person meets night owl. Indded :-) > Seth Forshee writes: > > > On Thu, Sep 24, 2015 at 04:53:11PM -0500, Eric W. Biederman wrote: > >> Seth Forshee

Re: [PATCH v2] gpio: mention in DT binding doc that -gpio is deprecated

On Mon, Sep 21, 2015 at 7:57 AM, Javier Martinez Canillas wrote: > The gpiolib supports parsing DT properties of the form -gpio but it > was only added for compatibility with older DT bindings that got it wrong > and should not be used in newer bindings. > > The commit

[PATCH] staging: fsl-mc: Fixed uintX_t CHECK checkpatch warnings

Replaced all uses of uintX_t types to uX types, to be checkpatch clean. Signed-off-by: J. German Rivera --- This patch depends on the patch posted at http://www.mail-archive.com/linux-kernel@vger.kernel.org/msg981518.html drivers/staging/fsl-mc/bus/dpbp.c

Re: [PATCH] richacl: Possible other write-through fix

2015-09-24 20:33 GMT+02:00 J. Bruce Fields : > On Sat, Sep 05, 2015 at 12:27:21PM +0200, Andreas Gruenbacher wrote: >> +int >> +richacl_apply_masks(struct richacl **acl, kuid_t owner) >> +{ >> + if ((*acl)->a_flags & RICHACL_MASKED) { >> + struct richacl_alloc

Re: [PATCH v3 2/5] mfd: tps65912: Remove old driver in preparation for new driver

On Thu, 24 Sep 2015, Andrew F. Davis wrote: > The old tps65912 driver is being replaced, delete old driver. > > Signed-off-by: Andrew F. Davis > --- > drivers/gpio/Kconfig | 6 - > drivers/gpio/Makefile | 1 - > drivers/gpio/gpio-tps65912.c

Re: [PATCH v4 06/22] gpio: Probe pinctrl devices on demand

On Mon, Sep 7, 2015 at 5:23 AM, Tomeu Vizoso wrote: Nit: prefix patch with "pinctrl:" > When looking up a pin controller through its OF node, probe it if it > hasn't already. > > The goal is to reduce deferred probes to a minimum, as it makes it very > cumbersome to

Re: [PATCH v4 05/22] gpio: Probe GPIO drivers on demand

On Mon, Sep 7, 2015 at 5:23 AM, Tomeu Vizoso wrote: > When looking up a gpiochip through its firmware node, probe it if it > hasn't already. > > The goal is to reduce deferred probes to a minimum, as it makes it very > cumbersome to find out why a device failed to

Re: [PATCH] gpio/pca953x: Add TI TCA9539 support

On Wed, Sep 9, 2015 at 8:23 AM, Thierry Reding wrote: > From: Thierry Reding > > The TCA9539 is almost identical to the PCA9555 and software-compatible > with this driver. It exposes 16 general purpose I/O pins in two 8-bit > configurations. > >

[PATCH 3/4] lib/vsprintf.c: Remove SPECIAL handling in pointer()

As a quick git grep -E '%[ +0#-]*#[ +0#-]*(\*|[0-9]+)?(\.(\*|[0-9]+)?)?p' shows, nobody uses the # flag with %p. Moreover, I think users are unlikely to show up since gcc will complain with warning: `#' flag used with ‘%p’ gnu_printf format [-Wformat] Since default_width is effectively

[PATCH 4/4] test_printf: test printf family at runtime

This adds a simple module for testing the kernel's printf facilities. Previously, some %p extensions have caused a wrong return value in case the entire output didn't fit and/or been unusable in kasprintf(). This should help catch such issues. Also, it should help ensure that changes to the

[PATCH] sched/fair: Skip wake_affine() for core siblings

We are not interested in actual target if both prev and curr cpus share CPU cache. select_idle_sibling() searches in top-down order; top level is the same for both of them, and the result will be the same. So, we can save a little CPU cycles and cache misses and skip wake_affine() calculations.

[PATCH v2 0/8] Improvements for SPI IMX driver for Freescale IMX53 and IMX6 families

A number of patches to impove or add the implementation for the spi-imx driver related to Freescale IMX53 and IMX6. It would also possible some of patches can be applied for other Freescale controllers using spi-imx driver but could not be tested due to lack of hardware. Anton Bondarenko (8):

Re: [PATCH] net: via/Kconfig: GENERIC_PCI_IOMAP required if PCI not selected

Hello. On 9/24/2015 1:16 PM, Sudip Mukherjee wrote: The builds of allmodconfig of avr32 is failing with: drivers/net/ethernet/via/via-rhine.c:1098:2: error: implicit declaration of function 'pci_iomap' [-Werror=implicit-function-declaration] drivers/net/ethernet/via/via-rhine.c:1119:2: error:

Re: [PATCH] arm64: Increase the max granular size

On 09/25/2015 07:45 AM, Robert Richter wrote: Will, On 22.09.15 19:29:02, Will Deacon wrote: On Tue, Sep 22, 2015 at 06:59:48PM +0100, Robert Richter wrote: From: Tirumalesh Chalamarla Increase the standard cacheline size to avoid having locks in the same

[PATCH 4/5] kernel/cpu.c: eliminate cpu_*_mask

Replace the variables cpu_possible_mask, cpu_online_mask, cpu_present_mask and cpu_active_mask with macros expanding to expressions of the same type and value, eliminating some indirection. Signed-off-by: Rasmus Villemoes --- include/linux/cpumask.h | 8

[PATCH 1/5] kernel/cpu.c: change type of cpu_possible_bits and friends

Change cpu_possible_bits and friends (online, present, active) from being bitmaps that happen to have the right size to actually being struct cpumasks. Also rename them to __cpu_xyz_mask. This is mostly a small cleanup in preparation for exporting them and, eventually, eliminating the extra

[PATCH 3/5] drivers/base/cpu.c: use __cpu_*_mask directly

The only user of the lvalue-ness of the cpu_*_mask variables is in drivers/base/cpu.c, and that is mostly a work-around for the fact that not even const variables can be used in static initialization. Now that the underlying struct cpumasks are exposed we can take their address. Signed-off-by:

[PATCH V1 2/6] ASoC: tlv320aic26: Fix module autoload

Add the missing MODULE_DEVICE_TABLE() for OF and SPI to export the information so modules have the correct aliases built-in and autoloading works correctly. A longer explanation by Javier Canillas can be found here: https://lkml.org/lkml/2015/7/30/519 https://lkml.org/lkml/2014/9/11/458

[PATCH V1 1/6] ASoC: tlv320aic26: Add device tree binding

Signed-off-by: Cormier, Jonathan --- .../devicetree/bindings/sound/tlv320aic26.txt | 65 ++ sound/soc/codecs/tlv320aic26.c | 6 ++ 2 files changed, 71 insertions(+) create mode 100644

[PATCH V1 6/6] ASoC: tlv320aic26: Change Capture Mute to Capture Switch to match alsa documentation.

Signed-off-by: Cormier, Jonathan --- sound/soc/codecs/tlv320aic26.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sound/soc/codecs/tlv320aic26.c b/sound/soc/codecs/tlv320aic26.c index 7d2fbca068d0..f7629b17ee5b 100644 ---

[PATCH V1 5/6] ASoC: tlv320aic26: hw_params was unintentionally clearing AIC26 master mode

Commit: 5b0959d472c2 "ASoC: tlv320aic26: Use snd_soc_update_bits()" broke setting AIC26_REG_AUDIO_CTRL3 in master mode when fsref happens to be 48000. The master mode bit was getting cleared. Also fix setting AIC26_REG_DAC_GAIN and AIC26_REG_AUDIO_CTRL2 which was broke by same commit. Fixes:

[PATCH V1 4/6] ASoC: tlv320aic26: Fix regmap by setting reg_defaults and reg_stride

tlv320aic26 codec wasn't being setup correctly on bootup due to misconfigured regmap cache. Fixes: b7e9f3973279 "ASoC: tlv320aic26: Convert to direct regmap API usage" Signed-off-by: Cormier, Jonathan --- sound/soc/codecs/tlv320aic26.c | 28

[PATCH V1 3/6] ASoC: tlv320aic26: Make SND_SOC_TLV320AIC26 user-visible

Allow SND_SOC_TLV320AIC26 to be built. Based on commit: http://mailman.alsa-project.org/pipermail/alsa-devel/2008-October/011287.html Signed-off-by: Cormier, Jonathan --- sound/soc/codecs/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH V4 2/2] debugfs: Pass bool pointer to debugfs_create_bool()

Its a bit odd that debugfs_create_bool() takes 'u32 *' as an argument, when all it needs is a boolean pointer. It would be better to update this API to make it accept 'bool *' instead, as that will make it more consistent and often more convenient. Over that bool takes just a byte (mostly). That

Re: [PATCH] xen/pvhvm: add soft reset on kexec/kdump support

Boris Ostrovsky writes: > On 09/25/2015 09:59 AM, Konrad Rzeszutek Wilk wrote: >> On Fri, Sep 25, 2015 at 11:59:52AM +0200, Vitaly Kuznetsov wrote: >>> Currently there is a number of issues preventing PVHVM Xen guests from >>> doing successful kexec/kdump: >>> - Bound

Re: [PATCH v5] mfd: tps6105x: Fix possible NULL pointer access.

On Fri, 25 Sep 2015, Grigoryev Denis wrote: > tps6105 driver provides two cells. One is for GPIO and another one is > for selected mode depending on platform data. When tps6105x is used in > GPIO-only mode, this driver calls mfd_add_devices() with mfd_cell > .name == NULL. This value causes an

Re: [RFC 0/2] VFIO: Add virtual MSI doorbell support.

On Tue, Sep 22, 2015 at 11:09:14PM +0100, Marc Zyngier wrote: > On Tue, 4 Aug 2015 06:52:01 +0100 > Bhushan Bharat wrote: > > > > > > > > -Original Message- > > > From: Pranavkumar Sawargaonkar [mailto:pranavku...@linaro.org] > > > Sent: Tuesday, August

Re: [PATCH] xen/pvhvm: add soft reset on kexec/kdump support

On 09/25/2015 12:07 PM, Vitaly Kuznetsov wrote: Also, I am not sure I see how this new op will be used in the hypervisor --- currently AFAICS it is only processed under is_hardware_domain(). Are there other patches that will support HVM guests? Please see my Xen series:

Re: [PATCH 4/4] dma-debug: Allow poisoning nonzero allocations

Hi Russell, On 25/09/15 13:44, Russell King - ARM Linux wrote: On Fri, Sep 25, 2015 at 01:15:46PM +0100, Robin Murphy wrote: Since some dma_alloc_coherent implementations return a zeroed buffer regardless of whether __GFP_ZERO is passed, there exist drivers which are implicitly dependent on

Re: [PATCH v4 1/7] fs: Add user namesapace member to struct super_block

Seth Forshee writes: > On Thu, Sep 24, 2015 at 04:14:33PM -0500, Eric W. Biederman wrote: >> Seth Forshee writes: >> >> > Initially this will be used to eliminate the implicit MNT_NODEV >> > flag for mounts from user namespaces. In the

Re: [PATCH 3/5] UBI: switch the UBI device in read-only mode when mtd returns -EROFS

Am 25.09.2015 um 17:09 schrieb Boris Brezillon: > The NAND layer is now able to forward power-cut emulation errors from > a NAND driver to the MTD user. > Check for this kind of errors in UBI and switch the UBI device in read-only > mode if such an error occurs. > The error will also be forwarded

[GIT PULL] Btrfs

Hi Linus, My for-linus-4.3 branch has a few fixes: git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus-4.3 This is an assorted set I've been queuing up: Jeff Mahoney tracked down a tricky one where we ended up starting IO on the wrong mapping for special files in

Re: [PATCH] arm64: Add support for PTE contiguous bit.

On 21 September 2015 at 09:44, David Woods wrote: > > Steve, Hi Dave, > > Thanks for your review and comments. I take your points about the 16k > granule - it's helpful to know that support is in the works. However, I'm > not sure I agree with your reading of section 4.4.2.

[PATCH v2 8/8] spi: imx: Add support for SPI Slave mode for imx53 and imx6 chips

Currently i.MX SPI controller only works in Master mode. This patch adds support to work also in Slave mode by adding "fsl,spi-slave-mode" in corresponding ecspi node in devicetree. Currently SPI Slave mode support patch has the following limitations: 1. The stale data in RXFIFO will be dropped

[PATCH v2 6/8] spi: imx: return error from dma channel request

On SDMA initialization return exactly the same error, which is reported by dma_request_slave_channel_reason(), it is a preceding change to defer SPI DMA initialization, if SDMA module is not yet available. Signed-off-by: Vladimir Zapolskiy Signed-off-by: Anton

[PATCH v2 1/8] spi: imx: Fix DMA transfer

RX DMA tail data handling doesn't work correctly in many cases with current implementation. It happens because SPI core was setup to generates both RX watermark level and RX DATA TAIL events incorrectly. SPI transfer triggering for DMA also done in wrong way. SPI client wants to transfer 70 words

[PATCH v2 3/8] spi: imx: add support for all SPI word width for DMA transfer

DMA transfer for SPI was limited to up to 8 bits word size until now. Sync in SPI burst size and DMA bus width is necessary to correctly support other BPW supported by HW. Signed-off-by: Anton Bondarenko --- drivers/spi/spi-imx.c | 121

Re: [PATCH v2 0/2] ASoC: atmel-classd: add driver for Atmel CLASSD

On Thu, Sep 24, 2015 at 01:41:25PM +0800, Songjun Wu wrote: > Songjun Wu (2): > ASoC: atmel-classd: add the Audio Class D Amplifier > ASoC: atmel-classd: DT binding for Class D audio amplifier driver I don't seem to have the second patch with the binding documentation. signature.asc

Re: [PATCH] richacl: Possible other write-through fix

2015-09-24 20:33 GMT+02:00 J. Bruce Fields : > On Sat, Sep 05, 2015 at 12:27:21PM +0200, Andreas Gruenbacher wrote: >> +int >> +richacl_apply_masks(struct richacl **acl, kuid_t owner) >> +{ >> + if ((*acl)->a_flags & RICHACL_MASKED) { >> + struct richacl_alloc

[PATCH V4 1/2] ACPI / EC: Fix broken 64bit big-endian users of 'global_lock'

global_lock is defined as an unsigned long and accessing only its lower 32 bits from sysfs is incorrect, as we need to consider other 32 bits for big endian 64 bit systems. There are no such platforms yet, but the code needs to be robust for such a case. Fix that by passing a local variable to

Re: [PATCH] pinctrl: mediatek: Consistently use the BIT() macro

On Fri, Aug 28, 2015 at 4:25 PM, Javier Martinez Canillas wrote: > The mediatek pinctrl driver uses the BIT() macro instead of open > coding 1 << n in all but one place. Replace this occurrence with > the BIT() macro for consistency. > > Signed-off-by: Javier Martinez

Re: [PATCH v3 3/5] mfd: tps65912: Add driver for the TPS65912 PMIC

On Thu, 24 Sep 2015, Andrew F. Davis wrote: > This patch adds support for TPS65912 mfd device. It provides > communication through the I2C and SPI interfaces. It contains > the following components: > > - Regulators > - GPIO controller > > Signed-off-by: Andrew F. Davis > --- >

[PATCH] MAINTAINERS: Remove Samuel Ortiz as MFD Maintainer

Signed-off-by: Lee Jones --- MAINTAINERS | 1 - 1 file changed, 1 deletion(-) diff --git a/MAINTAINERS b/MAINTAINERS index 274f854..fb2ba3d 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -7038,7 +7038,6 @@ F:drivers/media/i2c/mt9v032.c F:

Re: [PATCH v4 1/2] pinctrl: Add driver for Alphascale asm9260 pinctrl

On Tue, Sep 8, 2015 at 10:55 PM, Oleksij Rempel wrote: > [Me] >> Why is it necessary for the driver to copy one description of >> the pin into another? > > If i understand it correctly, pinctrl_pin_desc is essential part of > pinmux framework. Theoretically i should define

Re: [PATCH v4 3/7] fs: Verify access of user towards block device file when mounting

Argh. This looks like morning person meets night owl. Seth Forshee writes: > On Thu, Sep 24, 2015 at 04:53:11PM -0500, Eric W. Biederman wrote: >> Seth Forshee writes: >> >> > When mounting a filesystem on a block device there is

Re: [PATCH] pinctrl: core: handle pinctrl_get failure

On Thu, Sep 10, 2015 at 6:38 AM, Peng Fan wrote: > Need to do error handling path when pinctrl_get fails. Also when > pinctrl_get success, insert 'pctldev->node' to pinctrldev_list. > > Signed-off-by: Peng Fan > Cc: Linus Walleij

Re: [PATCH 12/12] mtd: nand-bbt: move nand_bbt.c to mtd folder

Hi Peter, First of all, thanks for taking the time to try to address my long-delayed comments. I hope to give this a proper look soon. (I also hope you can fix the email threading soon! I know that's a pain...) But first, a simpler comment: On Fri, Sep 25, 2015 at 06:48:05AM +, Peter Pan 潘栋

Re: [PATCH 1/3] Documentation: dt: keystone: provide SoC specific compatible flags

On 09/25/2015 11:15 AM, santosh shilimkar wrote: > 9/25/2015 9:01 AM, Nishanth Menon wrote: >> On 09/25/2015 10:18 AM, santosh shilimkar wrote: >>> On 9/25/2015 7:50 AM, Nishanth Menon wrote: >> [...] But, how about userspace needing to know which SoC they are on, without needing to

Re: [PATCH v4 3/7] fs: Verify access of user towards block device file when mounting

Seth Forshee writes: > On Fri, Sep 25, 2015 at 12:16:59PM -0500, Eric W. Biederman wrote: >> >> Argh. This looks like morning person meets night owl. > > Indded :-) > >> Seth Forshee writes: >> >> > On Thu, Sep 24, 2015 at 04:53:11PM

[PATCH v2 2/8] spi: imx: replace fixed timeout with calculated one

Fixed timeout value can fire while transaction is ongoing. This may happen because there are no strict requirements on SPI transaction duration. Dynamic timeout value is generated based on SCLK and transaction size. There is also 4 * SCLK delay between TX bursts related to CS change.

Re: [PATCH] dax: fix deadlock in __dax_fault

On Fri, Sep 25, 2015 at 12:53:57PM +1000, Dave Chinner wrote: <> > We've already got block allocation serialisation at the filesystem > level, and the issue is the unserialised block zeroing being done by > the dax code. That can be fixed by moving the zeroing into the > filesystem code when it

[PATCH 2/5] kernel/cpu.c: export __cpu_*_mask

Exporting the cpumasks __cpu_possible_mask and friends will allow us to remove the extra indirection through the cpu_*_mask variables. It will also allow the set_cpu_* functions to become static inlines, which will give a .text reduction. Signed-off-by: Rasmus Villemoes

[PATCH 0/5] kernel/cpu.c: eliminate some indirection

Maybe third time's the charm... The four cpumasks cpu_{possible,online,present,active}_bits are exposed readonly via the corresponding const variables cpu_xyz_mask. But they are also accessible for arbitrary writing via the exposed functions set_cpu_xyz. There's quite a bit of code throughout the

[PATCH 5/5] kernel/cpu.c: make set_cpu_* static inlines

Almost all callers of the set_cpu_* functions pass an explicit true or false. Making them static inline thus replaces the function calls with a simple set_bit/clear_bit, saving some .text. Signed-off-by: Rasmus Villemoes --- include/linux/cpumask.h | 43

Re: No more new fbdev drivers, please

On Fri, Sep 25, 2015 at 04:09:46PM +0300, Tomi Valkeinen wrote: > > > On 25/09/15 13:41, Kamil Lulko wrote: > > Hi, > > > >> fbdev is (more or less) maintained, but it's a deprecated framework. All > >> new Linux display drivers should be done on DRM. > > > > What about no-mmu platforms? DRM

consignment

  Contact us for your compensation consignment box -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

Re: [RFC PATCH] PM / Runtime: runtime: Add sysfs option for forcing runtime suspend

On Friday, September 25, 2015 11:52:23 PM Rafael J. Wysocki wrote: > On Friday, September 25, 2015 05:13:04 PM Alan Stern wrote: > > On Fri, 25 Sep 2015, Rafael J. Wysocki wrote: > > > > > On Friday, September 25, 2015 10:29:55 AM Alan Stern wrote: > > > > On Fri, 25 Sep 2015, Rafael J. Wysocki

[PATCH 4/5] selinux: use kstrdup() in security_get_bools()

This is much simpler. Signed-off-by: Rasmus Villemoes --- security/selinux/ss/services.c | 8 +--- 1 file changed, 1 insertion(+), 7 deletions(-) diff --git a/security/selinux/ss/services.c b/security/selinux/ss/services.c index 994c824a34c6..aa2bdcb20848 100644

[PATCH 2/5] selinux: remove pointless cast in selinux_inode_setsecurity()

security_context_to_sid() expects a const char* argument, so there's no point in casting away the const qualifier of value. Signed-off-by: Rasmus Villemoes --- security/selinux/hooks.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

Re: [PATCH v4 0/2] pwm: Broadcom BCM7038 PWM controller (v4)

On 14/09/15 16:47, Florian Fainelli wrote: > Hi, > > This patch series add PWM support for the Broadcom BCM7xxx > chips which feature one or more PWM controllers capable of > output periods from 148ns to ~622ms using a combination of > variable and fixed frequency settings. Thierry, are you

Re: PIDs Controller Limit

> On Thu, Sep 24, 2015 at 09:42:38AM +1000, Aleksa Sarai wrote: >> Does it make sense for the PIDs controller to allow a user to set a >> limit of 0? Since we don't cancel attaches, a limit of 0 doesn't >> affect anything (nothing stops attaches, and you need to have a >> process in the PIDs

Re: [PATCH v2 0/5] ACPI probing infrastructure

On Sunday, September 13, 2015 03:02:18 PM Marc Zyngier wrote: > IRQ controllers and timers are the two types of device the kernel > requires before being able to use the device driver model. > > The Device Tree infrastructure makes it very easy to make these > discoverable by the rest of the

Re: [PATCH v2 1/5] acpi: Add basic device probing infrastructure

On Sunday, September 13, 2015 03:02:19 PM Marc Zyngier wrote: The subject is slightly confusing IMO (there is a device probing infrastructure in the ACPI subsystem, but not for the kind of devices in question here). > IRQ controllers and timers are the two types of device the kernel > requires

Re: [PATCH 1/1] PCI/MSI: X-Gene: Remove msi_controller assignment in X-Gene PCIe driver

On Fri, Sep 18, 2015 at 09:59:56AM +0100, Marc Zyngier wrote: > On Wed, 16 Sep 2015 17:31:40 -0700 > Duc Dang wrote: > > > With commit 8d63bc7beaee ("PCI/MSI: pci-xgene-msi: Get rid of > > struct msi_controller"), it is no longer required to assign > > msi_controller for X-Gene

Re: Glibc recvmsg from kernel netlink socket hangs forever

On Sep 25, 2015, at 2:37 PM, Steven Schlansker wrote: > > On Sep 24, 2015, at 10:34 PM, Guenter Roeck wrote: > >> Herbert, >> >> On 09/24/2015 09:58 PM, Herbert Xu wrote: >>> On Thu, Sep 24, 2015 at 09:36:53PM -0700, Guenter Roeck wrote:

Re: First kernel patch (optimization)

Hi Erik, > > Yeah, I'm still reading this email thread and learned lots from it. > I'm working on something more meaningful, but it's not going to be > ground breaking of course, there is a led on my capslock key on a new > machine I won at work that does not switch off properly after it is >

[PATCH 5/5] selinux: use sprintf return value

sprintf returns the number of characters printed (excluding '\0'), so we can use that and avoid duplicating the length computation. Signed-off-by: Rasmus Villemoes --- security/selinux/ss/services.c | 5 + 1 file changed, 1 insertion(+), 4 deletions(-) diff --git

[PATCH 3/5] selinux: use kmemdup in security_sid_to_context_core()

Signed-off-by: Rasmus Villemoes --- security/selinux/ss/services.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/security/selinux/ss/services.c b/security/selinux/ss/services.c index c550df0e0ff1..994c824a34c6 100644 ---

[PATCH 0/5] selinux: minor cleanup suggestions

A few random things I stumbled on. While I'm pretty sure of the change in 1/5, I'm also confused, because the doc for the reverse security_sid_to_context state that @scontext_len is set to "the length of the string", which one would normally interpret as being what strlen() would give (i.e.,

[PATCH 1/5] selinux: introduce security_context_str_to_sid

There seems to be a little confusion as to whether the scontext_len parameter of security_context_to_sid() includes the nul-byte or not. Reading security_context_to_sid_core(), it seems that the expectation is that it does not (both the string copying and the test for scontext_len being zero hint

Re: [PATCH 10/26] x86, pkeys: notify userspace about protection key faults

On 09/25/2015 12:11 AM, Ingo Molnar wrote: >>> > > Btw., how does pkey support interact with hugepages? >> > >> > Surprisingly little. I've made sure that everything works with huge pages >> > and >> > that the (huge) PTEs and VMAs get set up correctly, but I'm not sure I had >> > to >> >

Re: [PATCH 0/8] Broadcom iProc PCIe fixes and outbound mapping support

On Tue, Sep 15, 2015 at 05:39:14PM -0700, Ray Jui wrote: > This patch series contains various fixes and outbound mapping support for > the Broadcom iProc PCIe driver. Some of the critical fixes include 1) fix of > PCIe core reset logic and therefore remove its dependency on the bootloader; > 2)

[PATCH 1/2] x86/efi: Map EFI memmap entries in-order at runtime

From: Matt Fleming Beginning with UEFI v2.5 EFI_PROPERTIES_TABLE was introduced that signals that the firmware PE/COFF loader supports splitting code and data sections of PE/COFF images into separate EFI memory map entries. This allows the kernel to map those regions with

[GIT PULL 0/2] EFI urgent fixes

From: Matt Fleming Folks, The patches in this pull request fix kernel crashes when booting Linux on UEFI v2.5 machines with the Properties Table feature enabled. Essentially, when this feature is enabled the firmware allocates separate entries in the EFI memory map for

<    4   5   6   7   8   9   10   11   12   >