[PATCH 28/31] x86, fpu: allow setting of XSAVE state

From: Dave Hansen We want to modify the Protection Key rights inside the kernel, so we need to change PKRU's contents. But, if we do a plain 'wrpkru', when we return to userspace we might do an XRSTOR and wipe out the kernel's 'wrpkru'. So, we need to go after

[PATCH 24/31] x86, pkeys: actually enable Memory Protection Keys in CPU

From: Dave Hansen This sets the bit in 'cr4' to actually enable the protection keys feature. We also include a boot-time disable for the feature "nopku". Seting X86_CR4_PKE will cause the X86_FEATURE_OSPKE cpuid bit to appear set. At this point in boot,

[PATCH 23/31] x86, pkeys: add Kconfig prompt to existing config option

From: Dave Hansen I don't have a strong opinion on whether we need this or not. Protection Keys has relatively little code associated with it, and it is not a heavyweight feature to keep enabled. However, I can imagine that folks would still appreciate being able

[PATCH 30/31] x86, pkeys: create an x86 arch_calc_vm_prot_bits() for VMA flags

From: Dave Hansen calc_vm_prot_bits() takes PROT_{READ,WRITE,EXECUTE} bits and turns them in to the vma->vm_flags/VM_* bits. We need to do a similar thing for protection keys. We take a protection key (4 bits) and encode it in to the 4 VM_PKEY_* bits. Note: this

Re: [PATCH] X.509: Partially revert patch to add validation against IMA MOK keyring

David Howells wrote: > Partially revert commit 41c89b64d7184a780f12f2cccdabe65cb2408893: > > Author: Petko Manolov > Date: Wed Dec 2 17:47:55 2015 +0200 > IMA: create machine owner and blacklist keyrings > > The problem is that

Re: [PATCH] thinkpad_acpi: don't yell on unsupported brightness interfaces

On 6 November 2015 at 17:57, Darren Hart wrote: > > On Fri, Nov 06, 2015 at 03:19:43PM +0100, David Herrmann wrote: > > Hi Darren! > > > > On Wed, Oct 21, 2015 at 4:44 PM, Darren Hart wrote: > > > On Wed, Oct 21, 2015 at 12:33:52PM -0200, Henrique de

Re: [PATCH 1/3] driver-core: platform: Add platform_irq_count()

On Wed, Jan 6, 2016 at 7:12 PM, Stephen Boyd wrote: > A recent patch added calls to of_irq_count() in the qcom pinctrl > drivers and that caused module build failures because > of_irq_count() is not an exported symbol. We shouldn't export > of_irq_count() to modules because

Re: dm ioctl: Access user-land memory through safe functions.

On Wed, Jan 06 2016 at 8:22pm -0500, Scotty Bauer wrote: > > > On 01/05/2016 02:13 PM, Mike Snitzer wrote: > > On Tue, Jan 05 2016 at 3:16pm -0500, > > Mike Snitzer wrote: > > > >> On Tue, Dec 08 2015 at 1:26pm -0500, > >> Scotty Bauer

[PATCH 1/2] ARM: exynos_defconfig: Enable NEON, accelerated crypto and cpufreq stats

Enable the kernel NEON mode and asm/NEON accelerated crypto algorithms which should bring performance benefits on Exynos SoCs. Enable these as modules because they are optional, not essential anyhow for platform booting nor related directly to Exynos Soc. All accelerated algorithms pass booting

[PATCH 2/2] ARM: exynos_defconfig: Enable s5p-secss driver

The Exynos SoC provides a Security SubSystem block for accelerating some cryptographic operations. Enable the driver for it - s5p-secss to utilize the hardware acceleration. Currently the s5p-secss driver supports AES in CBC and ECB modes. However on Odroid XU4 (Exynos5422) and Trats2

RE: [PATCH V2 2/3] NTB: Add AMD NTB support in Kconfig and Makefile

> > drivers/ntb/hw/Kconfig | 1 + > > drivers/ntb/hw/Makefile | 1 + > > 2 files changed, 2 insertions(+) > > > > diff --git a/drivers/ntb/hw/Kconfig b/drivers/ntb/hw/Kconfig index > > 4d5535c..0c5c2a6 100644 > > --- a/drivers/ntb/hw/Kconfig > > +++ b/drivers/ntb/hw/Kconfig > > @@ -1 +1,2 @@ > >

[PATCH 0/4] perf/x86/power: Introduce AMD accumlated power reporting mechanism

Hi, This series of patches introduces the perf implementation of accumulated power reporting algorithm. It will calculate the average power consumption for the processor. The CPU feature flag is CPUID.8000_0007H:EDX[12]. Simple example: root@hr-zp:/home/ray/tip# ./tools/perf/perf stat -a -e

[GIT PULL] Last MTD fixes for v4.4

Hi Linus, The following changes since commit e488ca9f8d4f62c2dc36bfa5c32f68e7f05ab381: doc: dt: mtd: partitions: add compatible property to "partitions" node (2015-12-08 17:10:20 -0800) are available in the git repository at: git://git.infradead.org/linux-mtd.git tags/for-linu

Re: [PATCH] trace: correct start_index in find_next

On 2015/12/31 13:11, Qiu, PeiyangX wrote: > From: Qiu Peiyang > > When we do cat /sys/kernel/debug/tracing/printk_formats, we hit kernel > panic at t_show. > > general protection fault: [#1] PREEMPT SMP > CPU: 0 PID: 2957 Comm: sh Tainted: G W O

Re: [PATCH v4 4/5] regulator: add regulator driver of hi655x pmic

On 2016/1/5 23:44, Mark Brown wrote: > On Mon, Jan 04, 2016 at 08:27:51PM +0800, Chen Feng wrote: > >> +/*LDO 2 & LDO 14*/ > > Please use the normal kernel coding style for comments, I'm surprised > checkpatch didn't warn you about this. > ok,thanks! >> +static const unsigned int

Re: [PATCH v4 2/5] doc: bindings: Document for hi655x regulator driver

On 2016/1/5 23:47, Mark Brown wrote: > On Mon, Jan 04, 2016 at 08:27:49PM +0800, Chen Feng wrote: >> Add Document for hi655x pmic regulator driver > > As indicated in the driver review this seems to be a bit of an unusual > binding that I think needs reworking, also it needs a bit more detail -

Re: [PATCH] trace: correct start_index in find_next

On Thu, 07 Jan 2016 10:56:56 +0800 "Zhang, Yanmin" wrote: > How is this patch? It fixes a kernel panic. > Linus already pulled it. It's also marked for stable. See commit: f36d1be2930ede0a1947686e1126ffda5d5ee1bb in Linus's tree. I renamed the subject slightly

Re: [PATCH] trace: correct start_index in find_next

On 2016/1/7 11:50, Steven Rostedt wrote: > On Thu, 07 Jan 2016 10:56:56 +0800 > "Zhang, Yanmin" wrote: > >> How is this patch? It fixes a kernel panic. >> > Linus already pulled it. It's also marked for stable. See commit: > f36d1be2930ede0a1947686e1126ffda5d5ee1bb

[PATCH] PCI: designware: comment the condition of programming ATU in host init

Some platforms don't support ATU, e.g pci-keystone.c, these platforms use their own address translation component rather than ATU, and they provide the rd_other_conf and wr_other_conf to programming the translation component then do the required access, so we ignore the ATU programming for these

Re: [PATCH v11 1/3] dt-bindings: binding for jz4780-{nand,bch}

On Mon, Jan 04, 2016 at 12:34:42PM +, Harvey Hunt wrote: > From: Alex Smith > > Add DT bindings for NAND devices connected to the NEMC on JZ4780 SoCs, > as well as the hardware BCH controller, used by the jz4780_{nand,bch} > drivers. > > Signed-off-by: Alex Smith

Re: [PATCH 00/35 v2] separate operations from flags in the bio/request structs

> "Mike" == mchristi writes: Mike> The following patches begin to cleanup the request->cmd_flags and bio-> bi_rw mess. We currently use cmd_flags to specify the operation, Mike> attributes and state of the request. For bi_rw we use it for Mike> similar info and also the

Re: [PATCH] X.509: Partially revert patch to add validation against IMA MOK keyring

On Thu, 2016-01-07 at 00:34 +, David Howells wrote: > David Howells wrote: > > > Partially revert commit 41c89b64d7184a780f12f2cccdabe65cb2408893: > > > > Author: Petko Manolov > > Date: Wed Dec 2 17:47:55 2015 +0200 > > IMA: create

Re: [PATCH v2 2/2] kexec: Provide arch_kexec_protect(unprotect)_crashkres()

On 01/07/2016 at 01:08 AM, Minfei Huang wrote: > On 01/06/16 at 05:50pm, Xunlei Pang wrote: >> diff --git a/arch/x86/kernel/machine_kexec_64.c >> b/arch/x86/kernel/machine_kexec_64.c >> index 819ab3f..cda867d 100644 >> --- a/arch/x86/kernel/machine_kexec_64.c >> +++

[PATCH 2/4] x86/amd: add accessor for number of cores per compute unit

Add an accessor function amd_get_cores_per_cu() which returns the number of cores per compute unit. In a subsequent patch, we will use this function in both x86 perf and fam15h driver. Signed-off-by: Huang Rui --- arch/x86/include/asm/processor.h | 1 +

[PATCH 4/4] perf/x86/amd/power: Add AMD accumulated power reporting mechanism

Introduce an AMD accumlated power reporting mechanism for Carrizo (Family 15h, Model 60h) processor that should be used to calculate the average power consumed by a processor during a measurement interval. The feature of accumulated power mechanism is indicated by CPUID Fn8000_0007_EDX[12].

[PATCH 1/4] x86/amd: move nodes_per_socket into bsp_init_amd

nodes_per_socket is static and it needn't be initialized many times during every cpu core init. So move nodes_per_socket initialization into bsp_init_amd. Signed-off-by: Huang Rui --- arch/x86/kernel/cpu/amd.c | 14 -- 1 file changed, 12 insertions(+), 2

[PATCH 3/4] x86/cpufeature: add AMD Accumulated Power Mechanism feature flag

AMD CPU family 15h model 0x60 introduces accumulated power mechanism. It is used to report the processor power consumption and indicated by CPUID Fn8000_0007_EDX[12]. Signed-off-by: Huang Rui --- arch/x86/include/asm/cpufeature.h | 2 +- arch/x86/kernel/cpu/amd.c | 4

RE: [PATCH V2 1/3] NTB: Add AMD PCI-Express NTB driver

> > + > > +#definePCI_DEVICE_ID_AMD_NTB 0x145B > > This looks like a tab and not a space I'll update it. > > > +#define AMD_LINK_HB_TIMEOUTmsecs_to_jiffies(1000) > > +#define AMD_LINK_STATUS_OFFSET 0x68 > > +#define NTB_LIN_STA_ACTIVE_BIT 0x0002 > > +#define

Re: [PATCH v4 2/5] mtd: nand: use nand_check_erased_ecc_chunk in default ECC read functions

On Wed, Dec 30, 2015 at 08:32:04PM +0100, Boris Brezillon wrote: > The default NAND read functions are relying on the underlying controller > driver to correct bitflips, but some of those controllers cannot properly > fix bitflips in erased pages. > Check for bitflips in erased pages in default

[PATCH RESEND] perf tools: bug fix, an error of parsing 'man..*' config variable.

To add new man viewer, configs like 'man..cmd', 'man..path' can be set into config file (~/.perfconfig). But parsing config file is stopped because the config variable contains '.' character i.e. If setting 'man.xman.cmd' into config file, [man] gman.cmd = gman when launching perf an

[PATCH 1/5] x86, memhp, numa: Online memory-less nodes at boot time.

For now, x86 does not support memory-less node. A node without memory will not be onlined, and the cpus on it will be mapped to the other online nodes with memory in init_cpu_to_node(). The reason of doing this is to ensure each cpu has mapped to a node with memory, so that it will be able to

[PATCH 3/5] x86, acpi, cpu-hotplug: Introduce cpuid_to_apicid[] array to store persistent cpuid <-> apicid mapping.

From: Gu Zheng This patch finishes step 2. In this patch, we introduce a new static array named cpuid_to_apicid[], which is large enough to store info for all possible cpus. And then, we modify the cpuid calculation. In generic_processor_info(), it simply finds the

[RFC PATCH v1 1/2] drm: rockchip: hdmi: add RK3229 HDMI support

RK3229 integrate an DesignedWare HDMI2.0 controller and an INNO HDMI2.0 phy, the max output resolution is 4K. Signed-off-by: Yakir Yang --- drivers/gpu/drm/bridge/dw-hdmi.c| 33 ++- drivers/gpu/drm/rockchip/dw_hdmi-rockchip.c | 380 +---

[RFC PATCH v1 0/2] Add RK3229 HDMI support

RK3229 have integrated an DesignedWare HDMI controller and an INNO HDMI phy, so we can still reuse the dw-hdmi driver for RK3229 HDMI controller, but we need to create an separate driver for RK3229 HDMI PHY. Yakir Yang (2): drm: rockchip: hdmi: add RK3229 HDMI support dt-bindings: add

Kexec_file_load failed with "Missing required AuthAttr"

Hi, I saw the warning "Missing required AuthAttr" when testing kexec, known issue? Idea about how to fix it? The kernel is latest linus tree plus sevral patches from Toshi to cleanup io resource structure. in function pkcs7_sig_note_set_of_authattrs(): if

[RFC 08/15] fs: Enable 64 bit time

64 bit time support is in place for all filesystems. Enable CONFIG_USES_64BIT_TIME to start using 64 bit time everywhere. Signed-off-by: Deepa Dinamani --- fs/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fs/Kconfig b/fs/Kconfig index

[RFC 00/15] Add 64 bit timestamp support

This is an update to Arnd Bergmann's RFC patch series: https://lkml.org/lkml/2014/5/30/669 . The syscalls and runtime libraries will be handled in separate patch series. The filling of max and min timestamps for individual filesystems can be leveraged from the patch series:

[RFC 02/15] vfs: Change all structures to support 64 bit time

The current representation of inode times in struct inode, struct iattr, and struct kstat use struct timespec. timespec is not y2038 safe. Use scalar data types (seconds and nanoseconds stored separately) to represent timestamps in struct inode in order to maintain same size for times across 32

[RFC 07/15] fs: ext4: convert to use 64 bit time

struct timespec is not y2038 safe. The ext4 uses time_extra fields to extend {a,c,m,cr} times until 2446. Use struct inode_timespec to replace timespec. inode_timespec will eventually be replaced by struct timespec64 when CONFIG_FS_USES_64BIT_TIME is enabled. Signed-off-by: Deepa Dinamani

[RFC 09/15] fs: cifs: replace inode_timespec with timespec64

Substitute inode_timespec aliases with timespec64. Since CONFIG_FS_USES_64BIT_TIME is enabled, internally all inode_timespec references are using timespec64 already. Signed-off-by: Deepa Dinamani --- fs/cifs/cache.c | 4 ++-- fs/cifs/cifsglob.h | 6 +++---

linux-next: manual merge of the target-updates tree with the rdma tree

Hi Nicholas, Today's linux-next merge of the target-updates tree got conflicts in: drivers/infiniband/ulp/iser/iscsi_iser.h drivers/infiniband/ulp/iser/iser_initiator.c drivers/infiniband/ulp/iser/iser_memory.c drivers/infiniband/ulp/iser/iser_verbs.c

Re: Nokia N900: u-SD card in v4.2+

Hi, On Thursday 07 January 2016 02:16 AM, Pavel Machek wrote: > Hi! > > In v4.1, both internal MMC and u-SD cards work ok. > > In v4.2, only the internal MMC is detected. In v4.3, not even internal > MMC works. In v4.4, only the internal MMC is detected. > > Does it work for you? Any patches?

Re: [RFC PATCH v1 1/2] drm: rockchip: hdmi: add RK3229 HDMI support

Thanks for "Kbuild test robot" reminding, I forget to update "mode_valid" function define in imx-hdmi side, would send new version out, -- drivers/gpu/drm/imx/dw_hdmi-imx.c:181:2: warning: initialization from incompatible pointer type .mode_valid = imx6q_hdmi_mode_valid, ^

Re: [PATCH 2/2] pci: host: pci-dra7xx: Enable x2 mode support

Hi, On Wednesday 06 January 2016 07:43 PM, Rob Herring wrote: > On Wed, Jan 06, 2016 at 04:19:53PM +0530, Kishon Vijay Abraham I wrote: >> Perform syscon configurations to get x2 mode to working in DRA74x and >> DRA72x. Also add a new compatible string to dfferentiate >> DRA72x and DRA74x, since

Re: dm ioctl: Access user-land memory through safe functions.

On 01/05/2016 02:13 PM, Mike Snitzer wrote: > On Tue, Jan 05 2016 at 3:16pm -0500, > Mike Snitzer wrote: > >> On Tue, Dec 08 2015 at 1:26pm -0500, >> Scotty Bauer wrote: >> >>> Friendly ping, is anyone interested in this? >> >> The passed @user

Re: [RFC v5 5/6] Add PTP_SYS_OFFSET_PRECISE for driver crosstimestamping

Hi Richard, This all sounds fine. Thanks for the feedback. I'll roll this into the next patchset. Chris On Tue, 05 Jan 2016 07:27:32 -0800, Richard Cochran wrote: On Mon, Jan 04, 2016 at 04:45:22AM -0800, Christopher S. Hall wrote: + case

Re: [Xen-devel] patch about "don't reset vcpu_info on a cancelled suspend"

On 2016/1/4 19:54, David Vrabel wrote: > On 29/12/15 05:49, Ouyangzhaowei (Charles) wrote: >> Hi David, >> >> This patch has been applied to for-linus-4.1b, and we wonder if this patch >> will be applied to linux kernel, or does >> it still needs more test to apply to linux kernel? > > Sorry,

Re: [PATCH v2 2/2] kexec: Provide arch_kexec_protect(unprotect)_crashkres()

On 01/07/2016 at 10:14 AM, Xunlei Pang wrote: > On 01/07/2016 at 01:08 AM, Minfei Huang wrote: >> On 01/06/16 at 05:50pm, Xunlei Pang wrote: >>> diff --git a/arch/x86/kernel/machine_kexec_64.c >>> b/arch/x86/kernel/machine_kexec_64.c >>> index 819ab3f..cda867d 100644 >>> ---

Re: [PATCH 00/35 v2] separate operations from flags in the bio/request structs

On Wed, Jan 06, 2016 at 08:40:09PM -0500, Martin K. Petersen wrote: > > "Mike" == mchristi writes: > > Mike> The following patches begin to cleanup the request->cmd_flags and > bio-> bi_rw mess. We currently use cmd_flags to specify the operation, > Mike> attributes and

Re: [PATCH] X.509: Partially revert patch to add validation against IMA MOK keyring

On Wed, 2016-01-06 at 21:13 -0500, Mimi Zohar wrote: > On Thu, 2016-01-07 at 00:34 +, David Howells wrote: > > David Howells wrote: > > > > > Partially revert commit 41c89b64d7184a780f12f2cccdabe65cb2408893: > > > > > > Author: Petko Manolov > >

[PATCH v5 5/5] misc: eeprom_93xx46: Add support for a GPIO 'select' line.

This commit adds support to the eeprom_93x46 driver allowing a GPIO line to function as a 'select' or 'enable' signal prior to accessing the EEPROM. Signed-off-by: Cory Tusar Tested-by: Chris Healy Reviewed-by: Vladimir Zapolskiy

[PATCH v5 4/5] misc: eeprom_93xx46: Add quirks to support Atmel AT93C46D device.

Atmel devices in this family have some quirks not found in other similar chips - they do not support a sequential read of the entire EEPROM contents, and the control word sent at the start of each operation varies in bit length. This commit adds quirk support to the driver and modifies the read

[PATCH v5 3/5] misc: eeprom_93xx46: Implement eeprom_93xx46 DT bindings.

This commit implements bindings in the eeprom_93xx46 driver allowing device word size and read-only attributes to be specified via devicetree. Signed-off-by: Cory Tusar Tested-by: Chris Healy Reviewed-by: Vladimir Zapolskiy

[PATCH v5 1/5] misc: eeprom_93xx46: Fix 16-bit read and write accesses.

Compatible at93xx46 devices from both Microchip and Atmel expect a word-based address, regardless of whether the device is strapped for 8- or 16-bit operation. However, the offset parameter passed in when reading or writing at a specific location is always specified in terms of bytes. This

[PATCH v5 0/5] Devicetree support for misc/eeprom/eeprom_93xx46.

This series of patches adds an initial set of devicetree bindings to the eeprom_93xx46 driver which mirror the configuration options previously available as a platform device. These bindings are then extended to include support for specific Atmel devices in this family and also to support

[PATCH v5 2/5] Documentation: devicetree: Add DT bindings to eeprom_93xx46 driver.

This commit documents bindings to be added to the eeprom_93xx46 driver which will allow: - Device word size and read-only attributes to be specified. - A device-specific compatible string for use with Atmel AT93C46D EEPROMs. - Specifying a GPIO line to function as a 'select' or 'enable'

Re: [Patch-V2 1/6] INPUT: xpad: Add minimal support for Logitech G920 Wheel

On Wed, January 6, 2016 6:47 pm, Dmitry Torokhov wrote: > It is wrong. Aside form the fact that IMO xpad.c is the wrong place for > this code to be in, why are we waiting for the input device to be opened by > userspace before we do the switch instead of doing it immediately? The 'send magic'

Re: [PATCH v2 3/5] clk: qcom: Add MSM8996 Global Clock Control (GCC) driver

Stephen, On 12/01/2015 07:01 AM, Stephen Boyd wrote: > Add support for the global clock controller found on MSM8996 > based devices. This should allow most non-multimedia device > drivers to probe and control their clocks. On my 8096 board I see the following orphan clocks,

Re: [PATCH v11 2/3] mtd: nand: jz4780: driver for NAND devices on JZ4780 SoCs

Hi Harvey, On Mon, Jan 04, 2016 at 12:34:43PM +, Harvey Hunt wrote: > From: Alex Smith > > Add a driver for NAND devices connected to the NEMC on JZ4780 SoCs, as > well as the hardware BCH controller. DMA is not currently implemented. > > While older 47xx SoCs also

Re: [PATCH] mfd: qcom-spmi-pmic: Don't access non-existing registers

On 11/17/15 16:06, Stephen Boyd wrote: > From: "Ivan T. Ivanov" > > Revision ID registers are available only on devices with > Slave IDs that are even, so don't make access to unavailable > registers. > > Signed-off-by: Ivan T. Ivanov >

Re: [PATCH 1/3] driver-core: platform: Add platform_irq_count()

On Wed, Jan 06, 2016 at 05:12:47PM -0800, Stephen Boyd wrote: > A recent patch added calls to of_irq_count() in the qcom pinctrl > drivers and that caused module build failures because > of_irq_count() is not an exported symbol. We shouldn't export > of_irq_count() to modules because it's an

Re: [PATCH v4 1/5] mtd: nand: return consistent error codes in ecc.correct() implementations

On Wed, Dec 30, 2015 at 08:32:03PM +0100, Boris Brezillon wrote: > The error code returned by the ecc.correct() are not consistent over the > all implementations. > > Document the expected behavior in include/linux/mtd/nand.h and fix > offending implementations. > > Signed-off-by: Boris

Re: [PATCH v4 3/5] mtd: nand: davinci: remove custom 'erased check' implementation

On Wed, Dec 30, 2015 at 08:32:05PM +0100, Boris Brezillon wrote: > The davinci drivers is manually checking for 'erased pages' while > correcting ECC bytes. > This logic can now done by the core infrastructure, and can thus be removed > from this drivers. > > Signed-off-by: Boris Brezillon

Re: [PATCH v4] i2c: designware: Do not require clock when SSCN and FFCN are provided

Hi, On 01/06/2016 06:31 PM, Loc Ho wrote: Hi All, The current driver uses input clock source frequency to calculate values for [SS|FS]_[HC|LC] registers. However, when booting ACPI, we do not currently have a good way to provide the frequency information. Instead, we can leverage the SSCN and

[RFC 15/15] fs: Drop CONFIG_FS_USES_64BIT_TIME

All file system code is using 64 bit time already and this config is no longer required. Signed-off-by: Deepa Dinamani --- fs/Kconfig | 10 -- 1 file changed, 10 deletions(-) diff --git a/fs/Kconfig b/fs/Kconfig index bfeefce..922893f 100644 --- a/fs/Kconfig +++

[RFC 05/15] fs: cifs: Add support for cifs to use 64 bit time

Change all struct timespec references to struct inode_timespec. Use inode timestamp accessors to access inode time fields. This will help the switch to struct timespec64 when CONFIG_FS_USES_64BIT_TIME is enabled. Use current_fs_time() instead of CURRENT_TIME macros to help range and precision

[RFC 14/15] vfs: Remove inode_timespec aliases

Now that CONFIG_FS_USES_64BIT_TIME is enabled, the aliases for inode_timespec are no longer used and can be removed. Signed-off-by: Deepa Dinamani --- include/linux/time64.h | 21 - 1 file changed, 21 deletions(-) diff --git a/include/linux/time64.h

[RFC 06/15] fs: fat: convert fat to 64 bit time

FAT filesystem supports timestamps until the year 2099 even though the theoretical max is 2107. But, the struct timespec overflows in the year 2038 on 32 bit systems. Use inode_timespec throughout the file system code so that the timestamps can switch to y2038 safe struct timespec64 when

[RFC 12/15] vfs: remove inode_timespec and timespec references

Substitute inode_timespec aliases with timespec64. Since CONFIG_FS_USES_64BIT_TIME is enabled, internally all inode_timespec references are using timespec64 already. Signed-off-by: Deepa Dinamani --- fs/attr.c| 2 +- fs/bad_inode.c | 2 +-

[RFC 13/15] kernel: time: change inode_timespec to timespec64

Substitute inode_timespec aliases with timespec64. Since CONFIG_FS_USES_64BIT_TIME is enabled, internally all inode_timespec references are using timespec64 already. Signed-off-by: Deepa Dinamani Conflicts: kernel/time/time.c Conflicts:

Re: [PATCH] dmaengine: xgene-dma: Fix double IRQ issue by setting IRQ_DISABLE_UNLAZY flag

On Wed, Dec 23, 2015 at 06:28:15PM +0530, Rameshswar Prasad Sahu wrote: > From: Rameshwar Prasad Sahu > > For interrupt controller that doesn't support irq_disable and hardware > with level interrupt, an extra interrupt can be pending. This patch fixes > the issue by setting

[RFC 01/15] fs: add Kconfig entry CONFIG_FS_USES_64BIT_TIME

This config will be used to #ifdef code that will be required for switching over all file systems to use 64 bit time. The config should remain turned off until all the support in vfs and other file systems has been added. Signed-off-by: Deepa Dinamani --- fs/Kconfig |

[PATCH] MAINTAINERS: update for Freescale DCU DRM driver

Promote myself as new maintainer of the Freescale DCU DRM driver. Signed-off-by: Stefan Agner --- This has been previously discussed privately. The original driver author and maintainer Jianwei does not work for Freescale anymore and can not carve out spare time to maintain the

Re: [PATCH 2/3] pinctrl: qcom: Use platform_irq_count() instead of of_irq_count()

On Wed, Jan 6, 2016 at 5:12 PM, Stephen Boyd wrote: > of_irq_count() is not an exported symbol (and it shouldn't be > used by platform drivers anyway) so use platform_irq_count() > instead. This allows us to make the qcom pinctrl drivers modular > again. > [..] > diff --git

Re: [PATCH v11 3/3] MIPS: dts: jz4780/ci20: Add NEMC, BCH and NAND device tree nodes

On Mon, Jan 04, 2016 at 12:34:44PM +, Harvey Hunt wrote: > diff --git a/arch/mips/boot/dts/ingenic/ci20.dts > b/arch/mips/boot/dts/ingenic/ci20.dts > index 9fcb9e7..782258c 100644 > --- a/arch/mips/boot/dts/ingenic/ci20.dts > +++ b/arch/mips/boot/dts/ingenic/ci20.dts As I noted on patch 1,

Re: [PATCH 2/3] pinctrl: qcom: Use platform_irq_count() instead of of_irq_count()

On 01/06/16 17:19, Bjorn Andersson wrote: > On Wed, Jan 6, 2016 at 5:12 PM, Stephen Boyd wrote: >> of_irq_count() is not an exported symbol (and it shouldn't be >> used by platform drivers anyway) so use platform_irq_count() >> instead. This allows us to make the qcom

[PATCH v2 2/3] pinctrl: qcom: Use platform_irq_count() instead of of_irq_count()

of_irq_count() is not an exported symbol (and it shouldn't be used by platform drivers anyway) so use platform_irq_count() instead. This allows us to make the qcom pinctrl drivers modular again. Cc: Rob Herring Cc: Andy Gross Cc: Bjorn Andersson

Re: [Patch-V2 1/6] INPUT: xpad: Add minimal support for Logitech G920 Wheel

On Wed, Jan 06, 2016 at 03:36:57PM +0100, Jiri Kosina wrote: > On Mon, 4 Jan 2016, Benjamin Tissoires wrote: > > > Jiri, I *think* this commit still is in your next pull request for > > Linus. We might want to drop it before it hits Linus' tree. > > What exactly would be the reasoning for

Re: [PATCH v2 1/5] devicetree: bindings: Document qcom board compatible format

On 11/23/15 16:47, Stephen Boyd wrote: > On 11/22, Rob Herring wrote: >> >> Much more reasonable now. I do find the '/' in it a bit strange though. > I can remove the backslash if you like. Is a dash more preferred? > >> Acked-by: Rob Herring >> > and if so can I keep the ack?

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

On Thu, Jan 07, 2016 at 11:42:53AM +1100, Stephen Rothwell wrote: > > This patch now looks like this (after changes to the orangefs tree): > > Guys, just set inode->i_link to ORANGEFS_I(dentry->d_inode)->link_target and have ->get_link = simple_get_link. Killing orangefs_{follow,get}_link()

Re: [PATCH v2 2/2] kexec: Provide arch_kexec_protect(unprotect)_crashkres()

On 01/07/16 at 10:14am, Xunlei Pang wrote: > >> +static int > >> +kexec_mark_range(unsigned long start, unsigned long end, bool protect) > >> +{ > >> + struct page *page; > >> + unsigned int nr_pages; > >> + > >> + /* For physical range: [start, end] */ > >> + if (!start || !end || start >

RE: [PATCH V2 1/3] NTB: Add AMD PCI-Express NTB driver

> > > >> > +#define ndev_pdev(ndev) ((ndev)->ntb.pdev) #define > ndev_name(ndev) > >> > +pci_name(ndev_pdev(ndev)) #define ndev_dev(ndev) > >> > +(_pdev(ndev)->dev) #define ntb_ndev(ntb) container_of(ntb, > >> > +struct amd_ntb_dev, ntb) #define hb_ndev(work) container_of(work, > >> > +struct

RE: [PATCH V2 0/3] Change notes of V2

> From: Xiangliang Yu : > > Main changes in V2: > > 1. Fixed compiler warning; > > 2. Add marcro argument of ndev in NTB_READ_REG/NTB_WRITE_REG; 3. > Add > > notes for flush and wakeup interfaces; > > > > Xiangliang Yu (3): > > NTB: Add AMD PCI-Express NTB driver > >

Re: [PATCH v2 2/2] kexec: Provide arch_kexec_protect(unprotect)_crashkres()

On 01/07/2016 at 10:36 AM, Minfei Huang wrote: > On 01/07/16 at 10:14am, Xunlei Pang wrote: +static int +kexec_mark_range(unsigned long start, unsigned long end, bool protect) +{ + struct page *page; + unsigned int nr_pages; + + /* For physical range: [start,

[RFC 04/15] vfs: Add support for vfs code to use 64 bit time

VFS currently uses struct timespec timestamps which are not y2038 safe. Change all the struct inode timestamps accesses through accessor macros only. This will help the switch over to 64 bit times seamlessly. Use struct inode_timespec aliases everywhere. This will change timestamp data types to

[RFC 03/15] kernel: time: Add macros and functions to support 64 bit time

The current_fs_time function is not y2038 safe because of the use of struct timespec. The macros CURRENT_TIME and CURRENT_TIME_SEC do not represent file system times correctly as they cannnot perform range checks or truncations. These are also not y2038 safe. Add 64 bit versions of the above

[RFC 10/15] fs: fat: replace inode_timespec with timespec64

Substitute inode_timespec aliases with timespec64. Since CONFIG_FS_USES_64BIT_TIME is enabled, internally all inode_timespec references are using timespec64 already. Signed-off-by: Deepa Dinamani --- fs/fat/dir.c | 4 ++-- fs/fat/fat.h | 6 +++---

[RFC 11/15] fs: ext4: replace inode_timespec with timespec64

Substitute inode_timespec aliases with timespec64. Since CONFIG_FS_USES_64BIT_TIME is enabled, internally all inode_timespec references are using timespec64 already. Signed-off-by: Deepa Dinamani --- fs/ext4/ext4.h| 14 +++--- fs/ext4/extents.c | 6 +++---

Re: [PATCH v2 00/12] mtd: nand_bbt: introduce independent nand BBT

Hi Boris, On Wed, Jan 6, 2016 at 10:29 PM, Boris Brezillon wrote: > On Wed, 30 Dec 2015 09:31:06 +0100 > Boris Brezillon wrote: > >> Hi Peter, >> >> On Wed, 30 Dec 2015 15:18:39 +0800 >> 潘栋 wrote:

[PATCH 0/3] Make qcom pinctrl drivers tristate again

One of my recent changes to the qcom pinctrl drivers introduced a module build failure due to of_irq_count() missing an export. Rob doesn't want us to export that API though, so this series introduces platform_irq_count() and uses it in the pinctrl drivers. Linus changed the Kconfig to bool so

[PATCH 2/3] pinctrl: qcom: Use platform_irq_count() instead of of_irq_count()

of_irq_count() is not an exported symbol (and it shouldn't be used by platform drivers anyway) so use platform_irq_count() instead. This allows us to make the qcom pinctrl drivers modular again. Cc: Rob Herring Cc: Andy Gross Signed-off-by: Stephen

[PATCH 1/3] driver-core: platform: Add platform_irq_count()

A recent patch added calls to of_irq_count() in the qcom pinctrl drivers and that caused module build failures because of_irq_count() is not an exported symbol. We shouldn't export of_irq_count() to modules because it's an internal OF API that shouldn't be used by drivers. Platform drivers should

[PATCH 3/3] Revert "pinctrl: qcom: make PMIC drivers bool"

This reverts commit bda7c4c2b9767ce2af4394754498662d62079af5. These drivers build as modules now that we use platform_irq_count() instead of of_irq_count(). Cc: Rob Herring Cc: Andy Gross Signed-off-by: Stephen Boyd ---

Re: [PATCH] mtd: fixing memory leak and handling failed kmalloc

On Tue, Dec 29, 2015 at 01:45:09PM -0500, Insu Yun wrote: > kmalloc needs to be handled when failing in memory pressure. > Also, it has memory leak in error routine. > > Signed-off-by: Insu Yun Applied to l2-mtd.git -- To unsubscribe from this list: send the line "unsubscribe

Re: [PATCH] mmc: host: arasan: sdhci-of-arasan: Remove no-hispd and no-cmd23 quirks for sdhci-arasan4.9a

Hi, On 01/05/2016 07:25 PM, Rameshwar Sahu wrote: > Hi Ulf, > > On Wed, Dec 23, 2015 at 6:59 PM, Rameshswar Prasad Sahu wrote: >> From: Rameshwar Prasad Sahu >> >> The Arason SD host controller supports set block count command (cmd23) >> and high speed mode. This

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

Hi all, On Thu, 31 Dec 2015 21:31:24 +1100 Stephen Rothwell wrote: > > After merging the drm tree, today's linux-next build (powerpc > allyesconfig) failed like this: > > drivers/gpu/drm/amd/amdgpu/../powerplay/hwmgr/tonga_thermal.c: In function >

Re: [PATCH v4 0/5] mtd: nand: properly handle bitflips in erased pages

Hi Boris, On Wed, Dec 30, 2015 at 08:32:02PM +0100, Boris Brezillon wrote: > Hi, > > This patch series aims at providing a common logic to check for bitflips > in erased pages. > > Currently each driver is implementing its own logic to check for bitflips > in erased pages. Not only this create

Re: [PATCH 4/4] perf/x86/amd/power: Add AMD accumulated power reporting mechanism

Hi Huang, [auto build test ERROR on bp/for-next] [also build test ERROR on v4.4-rc8 next-20160106] [cannot apply to tip/x86/core] [if your patch is applied to the wrong git tree, please drop us a note to help improving the system] url: https://github.com/0day-ci/linux/commits/Huang-Rui/perf

Re: [PATCH] dmaengine: xgene-dma: Fix double IRQ issue by setting IRQ_DISABLE_UNLAZY flag

On Wed, Jan 06, 2016 at 11:05:02AM +0100, Thomas Gleixner wrote: > On Wed, 6 Jan 2016, Vinod Koul wrote: > > On Wed, Jan 06, 2016 at 02:51:07PM +0530, Rameshwar Sahu wrote: > > > >> @@ -1610,6 +1611,7 @@ static int xgene_dma_request_irqs(struct > > > >> xgene_dma *pdma) > > > >> /* Register

[PATCH] arm: dts: qcom: Add more board clocks

These clocks are fixed rate board sources that should be in DT. Add them. Cc: Georgi Djakov Signed-off-by: Stephen Boyd --- It seems that I never sent out the updated version of this patch to cover all the SoCs we have. This is on top of

<    3   4   5   6   7   8   9   10   11   12   >