Re: [PATCH] Staging:greybus:arche-apb-ctrl: fix trailing */ Block comments and 80 character line limit coding style issue

On Fri, 2016-10-07 at 13:23 -0700, Nadim Almas wrote: > Fixed coding style issue > diff --git a/drivers/staging/greybus/arche-apb-ctrl.c > b/drivers/staging/greybus/arche-apb-ctrl.c [] > @@ -168,7 +168,10 @@ static int standby_boot_seq(struct platform_device *pdev) > if (apb->init_disabled)

[PATCH net-next] nfnetlink_log: Use GFP_NOWARN for skb allocation

Since the code explicilty falls back to a smaller allocation when the large one fails, we shouldn't complain when that happens. Signed-off-by: Calvin Owens --- net/netfilter/nfnetlink_log.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

Re: [PATCH] fs: Assert on module file_operations without an owner

On Friday 10/07 at 21:48 +0100, Al Viro wrote: > On Fri, Oct 07, 2016 at 01:35:52PM -0700, Calvin Owens wrote: > > Omitting the owner field in file_operations declared in modules is an > > easy mistake to make, and can result in crashes when the module is > > unloaded while userspace is poking the

[PATCH V3 01/10] acpi: apei: read ack upon ghes record consumption

A RAS (Reliability, Availability, Serviceability) controller may be a separate processor running in parallel with OS execution, and may generate error records for consumption by the OS. If the RAS controller produces multiple error records, then they may be overwritten before the OS has consumed

[PATCH V3 00/10] Add UEFI 2.6 and ACPI 6.1 updates for RAS on ARM64

When a memory error, CPU error, PCIe error, or other type of hardware error that's covered by RAS occurs, firmware should populate the shared GHES memory location with the proper GHES structures to notify the OS of the error. For example, platforms that implement firmware first handling may

Re: [PATCH] ARC: [build] Support gz, lzma compressed uImage

On 10/04/2016 04:34 PM, Daniel Mentz wrote: > Add support for lzma compressed uImage. > > Support for gzip was already available but could not be enabled because > we were missing CONFIG_HAVE_KERNEL_GZIP in arch/arc/Kconfig. > > Signed-off-by: Daniel Mentz > Cc:

Re: [PATCH 00/14] libnvdimm: support sub-divisions of pmem for 4.9

On 10/7/2016 3:52 PM, Dan Williams wrote: > On Fri, Oct 7, 2016 at 11:19 AM, Linda Knippers > wrote: >> Hi Dan, >> >> A couple of general questions... >> >> On 10/7/2016 12:38 PM, Dan Williams wrote: >>> With the arrival of the device-dax facility in 4.7 a pmem

Re: [PATCH] [media] vb2: move dma-buf unmap from __vb2_dqbuf() to vb2_buffer_done()

Hi Javier, On Tue, Aug 16, 2016 at 05:26:31PM -0400, Javier Martinez Canillas wrote: > Hello Sakari, > > On 08/16/2016 05:13 PM, Sakari Ailus wrote: > > Hi Javier, > > > > Javier Martinez Canillas wrote: > >> Hello Sakari, > >> > >> On 08/16/2016 04:47 PM, Sakari Ailus wrote: > >>> Hi Javier, >

Re: [GIT PULL] trivial for 4.9

On Fri, 2016-10-07 at 14:06 -0700, Linus Torvalds wrote: > And btw, even without an explicit KERN_, you should still not > get any interleaving. Only an _explicit_ KERN_CONT should cause > interleaving, and dammit, if some interrupt does a KERN_CONT without > having had a non-cont printk before

Re: md-cluster: Delete unnecessary braces in unlock_all_bitmaps()

Am 07.10.2016 10:37, schrieb SF Markus Elfring: >>> Do not use curly brackets at one source code place >>> where a single statement should be sufficient. >> >> The original style was correct and this is wrong. I have explained this >> before. > > Did I change a bit too much in the proposed

Re: scripts/coccicheck: Update for a comment?

> Do I overlook any commit for the discussed source file anyhow? > https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/log/dev-tools/coccinelle.rst It seems that I missed this file also because an other path will be appropriate.

Re: Bogus "APIC: NR_CPUS/possible_cpus limit of 4 reached" messages

On 2016.10.06 at 13:52 +0200, Markus Trippelsdorf wrote: > On 2016.10.06 at 12:48 +0100, One Thousand Gnomes wrote: > > On Thu, 6 Oct 2016 13:27:37 +0200 > > Markus Trippelsdorf wrote: > > > > > On current trunk I get during boot: > > > > > > [0.00] APIC:

[tip:x86/urgent] arch/x86: Handle non enumerated CPU after physical hotplug

Commit-ID: 2a51fe083eba7f99cbda72f5ef90cdf2f4df882c Gitweb: http://git.kernel.org/tip/2a51fe083eba7f99cbda72f5ef90cdf2f4df882c Author: Prarit Bhargava AuthorDate: Mon, 3 Oct 2016 13:07:12 -0400 Committer: Thomas Gleixner CommitDate: Fri, 7 Oct

Re: [RESEND PATCH v2 -next 0/3] ARM64: amlogic: Add support for GXL SoC Family

Neil Armstrong writes: > This is a resend rebased on linux-next-20161004 tag. > > The new Amlogic GXL SoCs (S905X and S905D) are part of the Meson GX family and > share some common features that can be described in a common GX dtsi file used > by the Meson GXBB and Meson

Re: [patch 14/32] greybus: LED driver

On Fri 2016-09-16 16:10:14, Greg KH wrote: > > This driver implements the Greybus LED protocol. I guess this should be copied to LED mainainters? Havingstandartized phone hardware to work would be great. Is it possible to get device using this?

Re: xrandr fails after resume from hibernation in kernels 4.7.4 and 4.8.0

On Wed, Oct 05, 2016 at 07:23:23AM +0200, Greg KH wrote: > On Tue, Oct 04, 2016 at 08:43:03PM -0300, Gaston Gonzalez wrote: > > Hi, > > > > After hibernation I get the following error when I tried to connect to > > monitor > > through hdmi: > > > > $ xrandr --output LVDS1 --off --output HDMI1

Re: [patch 14/32] greybus: LED driver

On Fri, Oct 07, 2016 at 03:36:56PM +0200, Pavel Machek wrote: > On Fri 2016-09-16 16:10:14, Greg KH wrote: > > > > This driver implements the Greybus LED protocol. > > I guess this should be copied to LED mainainters? It will when it comes out of the staging directory. > Havingstandartized

Re: [patch 12/32] greybus: es2 host driver

On Fri 2016-09-16 15:25:25, Greg KH wrote: > This is a Greybus host driver for the ES2/3 bridge chip from Toshiba. > > Signed-off-by: Greg Kroah-Hartman > --- > +/* > + * @endpoint: bulk in endpoint for CPort data > + * @urb: array of urbs for the CPort in messages >

Re: [PATCH v2 0/2] ARM64: meson-gxbb: Add support for the Nexbox A95X Board

Neil Armstrong writes: > Add support for the Amlogic S905 (GXBB) version of the Nexbox A95X, an IPTV > set-top-box with Ethernet, SDCard, eMMC, USB, HDMI, IR, Led, Reset button and > Audio Jack. > > Changes since v1 at: >

[PATCH V3 1/3] perf intel-pt/bts: Tidy instruction buffer size usage

Tidy instruction buffer size usage in preparation for copying the instruction bytes onto samples. The instruction buffer is presently used for debugging, so rename its size macro from INTEL_PT_INSN_DBG_BUF_SZ to INTEL_PT_INSN_BUF_SZ, and use it everywhere. Note that the maximum instruction size

[PATCH V3 0/3] perf tools: Support insn and insnlen in perf script

Hi I tidied Intel PT / BTS instruction buffer size usage, and took the liberty of re-basing Andi's changes on top. Adrian Hunter (1): perf intel-pt/bts: Tidy instruction buffer size usage Andi Kleen (2): perf intel-pt/bts: Report instruction bytes and length in sample perf

[PATCH V3 2/3] perf intel-pt/bts: Report instruction bytes and length in sample

From: Andi Kleen Change Intel PT and BTS to pass up the length and the instruction bytes of the decoded or sampled instruction in the perf sample. The decoder already knows this information, we just need to pass it up. Since it is only a couple of movs it is not very

[PATCH V3 3/3] perf tools: Support insn and insnlen in perf script

From: Andi Kleen When looking at Intel PT traces with perf script it is useful to have some indication of the instruction. Dump the instruction bytes and instruction length, which can be used for simple pattern analysis in scripts. % perf record -e intel_pt// foo % perf

Re: [PATCH 1/2] perf intel-pt-decoder: Report instruction bytes and length in sample

On 05/10/16 14:36, Arnaldo Carvalho de Melo wrote: > Em Mon, Oct 03, 2016 at 05:30:32PM -0700, Andi Kleen escreveu: >> From: Andi Kleen >> >> Change the Intel PT decoder to pass up the length and the instruction >> bytes of the decoded or sampled instruction in the perf

Re: [patch 17/32] greybus: power supply driver

On Fri 2016-09-16 16:10:58, Greg KH wrote: > > This driver implements the Greybus power supply class protocol. Probably POWER SUPPLY CLASS/SUBSYSTEM and DRIVERS M: Sebastian Reichel M: Dmitry Eremin-Solenikov M: David Woodhouse

Re: [PATCH v2] cinergyT2-core: don't do DMA on stack

2016-10-06 20:29 GMT+02:00 Mauro Carvalho Chehab : > Em Thu, 6 Oct 2016 10:27:56 -0700 > Andy Lutomirski escreveu: > >> On Wed, Oct 5, 2016 at 11:58 AM, Mauro Carvalho Chehab >> wrote: >> > Sorry, forgot to C/C people that

Re: [PATCH 09/10] net: phy: Add MDIO driver for Juniper's SAM FPGA

On Fri, Oct 07, 2016 at 06:18:37PM +0300, Pantelis Antoniou wrote: > From: Georgi Vlaev > > Add driver for the MDIO IP block present in Juniper's > SAM FPGA. > > This driver supports only Clause 45 of the 802.3 spec. > > Note that due to the fact that there are no drivers

[PATCH v5 01/17] ext4: allow DAX writeback for hole punch

Currently when doing a DAX hole punch with ext4 we fail to do a writeback. This is because the logic around filemap_write_and_wait_range() in ext4_punch_hole() only looks for dirty page cache pages in the radix tree, not for dirty DAX exceptional entries. Signed-off-by: Ross Zwisler

[RFC v3 1/3] skge: Rename LED_OFF and LED_ON in marvel skge driver to avoid conflicts with leds namespace

Adding led support for phy causes namespace conflicts for some phy drivers. The marvel skge driver declared an enum for representing the states of Link LED Register. The enum contained constant LED_OFF which conflicted with declartation found in linux/leds.h. LED_OFF changed to LED_REG_OFF Also

Re: [PULL REQUEST] i2c for 4.9

On Fri, Oct 7, 2016 at 2:32 AM, Wolfram Sang wrote: > > here is the 4.9 pull request from I2C including: Would you mind double-checking my merge. It looked very trivial, but it would be good to have somebody else give that gpio-pca953x.c conflict a look to verify that I

[PATCH] arm64: defconfig: enable EEPROM_AT25 config option

Enable support for on board SPI EEPROM by turning on CONFIG_EEPROM_AT25. Signed-off-by: Scott Branden --- arch/arm64/configs/defconfig | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig index

Re: [GIT PULL] trivial for 4.9

On Fri, Oct 7, 2016 at 2:06 PM, Linus Torvalds wrote: > > And btw, even without an explicit KERN_, you should still not > get any interleaving. Only an _explicit_ KERN_CONT should cause > interleaving Btw, note the "should" there. Because we do seem to have broken

Re: [PATCH] fs: Assert on module file_operations without an owner

On Friday 10/07 at 17:18 -0400, Calvin Owens wrote: > On Friday 10/07 at 21:48 +0100, Al Viro wrote: > > On Fri, Oct 07, 2016 at 01:35:52PM -0700, Calvin Owens wrote: > > > Omitting the owner field in file_operations declared in modules is an > > > easy mistake to make, and can result in crashes

Re: [PATCH V3 09/10] trace, ras: add ARM processor error trace event

On Fri, 7 Oct 2016 15:31:21 -0600 Tyler Baicar wrote: > Currently there are trace events for the various RAS > errors with the exception of ARM processor type errors. > Add a new trace event for such errors so that the user > will know when they occur. These trace events

[RELEASE] LTTng modules 2.7.6 and 2.8.2 (Linux tracer timekeeping work-around)

Hi, LTTng modules 2.7.6 and 2.8.2 are bugfix releases which work around an upstream Linux kernel timekeeping bug. This bug has been introduced in the 4.8 kernel, and backported into Linux stable branches. It affects LTTng, perf, ftrace with "mono" clock source, and eBPF. All LTTng-modules 2.7.x

Re: [GIT PULL] trivial for 4.9

On Fri, 2016-10-07 at 13:25 -0700, Linus Torvalds wrote: > I find this noise to add '\n' characters completely pointless. It's > bogus stupid churn that doesn't actually make the source code better, > and it also doesn't actually seem to fix any behavioral issues. > > And if there are behavioral

Re: [PATCH v13 15/15] vfio/type1: Return the MSI geometry through VFIO_IOMMU_GET_INFO capability chains

On Fri, 7 Oct 2016 19:10:27 +0200 Auger Eric wrote: > Hi Alex, > > On 06/10/2016 22:42, Alex Williamson wrote: > > On Thu, 6 Oct 2016 14:20:40 -0600 > > Alex Williamson wrote: > > > >> On Thu, 6 Oct 2016 08:45:31 + > >> Eric Auger

Re: [PATCH 0/6] Introduce Juniper CBC FPGA

On Fri, Oct 07, 2016 at 09:53:29PM +0300, Pantelis Antoniou wrote: > Hi Greg, > > > On Oct 7, 2016, at 18:39 , Greg Kroah-Hartman > > wrote: > > > > On Fri, Oct 07, 2016 at 06:20:08PM +0300, Pantelis Antoniou wrote: > >> Add Juniper's PTX1K CBC FPGA driver. Those

Re: [v4.8-rc1 Regression] sched/fair: Apply more PELT fixes

On Fri, Oct 7, 2016 at 1:22 PM, Joseph Salisbury wrote: > > Yes, CONFIG_SCHED_AUTOGROUP is enabled in the Ubuntu kernel. However, > that config was also enable in the Ubuntu 4.4 kerrnels without seeing > this issue. I can try disabling the config in the 4.8

Re: [PULL REQUEST] i2c for 4.9

> I see you didn't pick up the follow-up patch ("gpio: pca953x: add a > comment explaining the need for a lockdep subclass"). Linus acked it This was planned for the following pull request. Didn't want to change what was successfully in linux-next for a while. signature.asc Description: PGP

Re: [PATCH][V2] nbd: add multi-connection support

On 10/07/2016 02:36 PM, Pavel Machek wrote: On Thu 2016-09-15 10:43:54, Josef Bacik wrote: NBD can become contended on its single connection. We have to serialize all writes and we can only process one read response at a time. Fix this by allowing userspace to provide multiple connections to

Re: [PATCH 4/10] MAINTAINERS: add entry for Marvell Xenon MMC Host Controller drivers

On Fri, 2016-10-07 at 17:22 +0200, Gregory CLEMENT wrote: > Add maintainer entry for Marvell Xenon eMMC/SD/SDIO Host > Controller drivers. [] > diff --git a/MAINTAINERS b/MAINTAINERS [] > @@ -7578,6 +7578,11 @@ M: Nicolas Pitre > S: Odd Fixes > F:

Re: [PATCH 1/3] fpga manager: Add cyclonespi driver for Altera fpgas

On 10/07/2016 11:21 AM, atull wrote: > On Fri, 7 Oct 2016, Moritz Fischer wrote: > >>> +static inline u32 revbit8x4(u32 n) >>> +{ >>> + n = ((n & 0xF0F0F0F0UL) >> 4) | ((n & 0x0F0F0F0FUL) << 4); >>> + n = ((n & 0xUL) >> 2) | ((n & 0xUL) << 2); >>> + n = ((n &

[PATCH v5 05/17] ext2: return -EIO on ext2_iomap_end() failure

Right now we just return 0 for success, but we really want to let callers know about this failure. Signed-off-by: Ross Zwisler --- fs/ext2/inode.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/fs/ext2/inode.c b/fs/ext2/inode.c index

Re: [PATCH] net: Reset skb to network header in neigh_hh_output

On Fri, 2016-10-07 at 16:14 +0200, Abdelrhman Ahmed wrote: > When hardware header is added without using cached one, neigh_resolve_output > and neigh_connected_output reset skb to network header before adding it. > When cached one is used, neigh_hh_output does not reset the skb to network >

[PATCH v5 11/17] dax: correct dax iomap code namespace

The recently added DAX functions that use the new struct iomap data structure were named iomap_dax_rw(), iomap_dax_fault() and iomap_dax_actor(). These are actually defined in fs/dax.c, though, so should be part of the "dax" namespace and not the "iomap" namespace. Rename them to dax_iomap_rw(),

[PATCH v5 09/17] dax: coordinate locking for offsets in PMD range

DAX radix tree locking currently locks entries based on the unique combination of the 'mapping' pointer and the pgoff_t 'index' for the entry. This works for PTEs, but as we move to PMDs we will need to have all the offsets within the range covered by the PMD to map to the same bit lock. To

[PATCH v5 10/17] dax: remove dax_pmd_fault()

dax_pmd_fault() is the old struct buffer_head + get_block_t based 2 MiB DAX fault handler. This fault handler has been disabled for several kernel releases, and support for PMDs will be reintroduced using the struct iomap interface instead. Signed-off-by: Ross Zwisler

[PATCH] coresight: reset "enable_sink" flag when need be

When using coresight from the perf interface sinks are specified as part of the perf command line. As such the sink needs to be disabled once it has been acknowledged by the coresight framework. Otherwise the sink stays enabled, which may interfere with other sessions. This patch removes the

[PATCH v5 13/17] dax: dax_iomap_fault() needs to call iomap_end()

Currently iomap_end() doesn't do anything for DAX page faults for both ext2 and XFS. ext2_iomap_end() just checks for a write underrun, and xfs_file_iomap_end() checks to see if it needs to finish a delayed allocation. However, in the future iomap_end() calls might be needed to make sure we have

[PATCH v5 16/17] xfs: use struct iomap based DAX PMD fault path

Switch xfs_filemap_pmd_fault() from using dax_pmd_fault() to the new and improved dax_iomap_pmd_fault(). Also, now that it has no more users, remove xfs_get_blocks_dax_fault(). Signed-off-by: Ross Zwisler --- fs/xfs/xfs_aops.c | 26 +-

[PATCH V3 08/10] ras: acpi / apei: generate trace event for unrecognized CPER section

UEFI spec allows for non-standard section in Common Platform Error Record. This is defined in section N.2.3 of UEFI version 2.5. Currently if the CPER section's type (UUID) does not match with any section type that the kernel knows how to parse, trace event is not generated for such section. And

Re: [PATCH -v4 1/8] locking/drm: Kill mutex trickery

On 10/07/2016 12:13 PM, Peter Zijlstra wrote: On Fri, Oct 07, 2016 at 08:58:43AM -0700, Linus Torvalds wrote: The other choice would be to just make the choices be negative (== recursive), zero (== failed) or positive (== got lock), which allows for the same value re-use for the non-recursive

Re: [PATCH] metag: Only define atomic_dec_if_positive conditionally

On Fri, Oct 07, 2016 at 10:40:59AM -0700, Guenter Roeck wrote: > The definition of atomic_dec_if_positive() assumes that > atomic_sub_if_positive() exists, which is only the case if > metag specific atomics are used. This results in the following > build error when trying to build

[PATCH] crypto: crypto4xx - Fix size used in dma_free_coherent()

The size used in 'dma_free_coherent()' looks un-initialized here. ctx->sa_len is set a few lines below and is apparently not set by the caller. So use 'size' as in the corresponding 'dma_alloc_coherent()' a few lines above. This has been spotted with coccinelle, using the following script:

Re: [PATCH 2/3] doc: dt: add cyclone-spi binding document

Moritz, thank you very much for the review. On 10/06/2016 07:53 PM, Moritz Fischer wrote: > Hi Joshua, > > On Thu, Oct 6, 2016 at 1:34 PM, Joshua Clayton > wrote: >> Describe a cyclonespi devicetree entry, required features >> >> Signed-off-by: Joshua Clayton

Re: [PATCH v13 12/15] vfio: Allow reserved msi iova registration

On Fri, 7 Oct 2016 19:11:43 +0200 Auger Eric wrote: > Hi Alex, > > On 06/10/2016 22:19, Alex Williamson wrote: > > On Thu, 6 Oct 2016 08:45:28 + > > Eric Auger wrote: > > > >> The user is allowed to register a reserved MSI IOVA range by

[PATCH] wan/fsl_ucc_hdlc: Fix size used in dma_free_coherent()

Size used with 'dma_alloc_coherent()' and 'dma_free_coherent()' should be consistent. Here, the size of a pointer is used in dma_alloc... and the size of the pointed structure is used in dma_free... This has been spotted with coccinelle, using the following script: @r@

Re: [GIT PULL] trivial for 4.9

On Fri, Oct 7, 2016 at 1:33 PM, Joe Perches wrote: >> >> And if there are behavioral issues, they should (a) be pointed out and >> (b) be fixed. >> >> In *no* case does it make sense to randomly just add newline >> characters without even having a reason for it. > > It prevents

[PATCH v2 1/2] Staging:greybus:arche-apb-ctrl: fix trailing */ Block comments and 80 character line limit coding style issue

Fixed coding style issue Signed-off-by: Nadim Almas --- Changes in v2: - Used space after leading * in block comments. drivers/staging/greybus/arche-apb-ctrl.c | 10 +++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git

[PATCH v5 17/17] dax: remove "depends on BROKEN" from FS_DAX_PMD

Now that DAX PMD faults are once again working and are now participating in DAX's radix tree locking scheme, allow their config option to be enabled. Signed-off-by: Ross Zwisler --- fs/Kconfig | 1 - 1 file changed, 1 deletion(-) diff --git a/fs/Kconfig

[PATCH v5 06/17] dax: make 'wait_table' global variable static

The global 'wait_table' variable is only used within fs/dax.c, and generates the following sparse warning: fs/dax.c:39:19: warning: symbol 'wait_table' was not declared. Should it be static? Make it static so it has scope local to fs/dax.c, and to make sparse happy. Signed-off-by: Ross Zwisler

[PATCH v5 00/17] re-enable DAX PMD support

DAX PMDs have been disabled since Jan Kara introduced DAX radix tree based locking. This series allows DAX PMDs to participate in the DAX radix tree based locking scheme so that they can be re-enabled. Dave, can you please take this through the XFS tree as we discussed during the v4 review?

[PATCH v5 07/17] dax: remove the last BUG_ON() from fs/dax.c

Don't take down the kernel if we get an invalid 'from' and 'length' argument pair. Just warn once and return an error. Signed-off-by: Ross Zwisler --- fs/dax.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/fs/dax.c b/fs/dax.c index

[PATCH v5 08/17] dax: consistent variable naming for DAX entries

No functional change. Consistently use the variable name 'entry' instead of 'ret' for DAX radix tree entries. This was already happening in most of the code, so update get_unlocked_mapping_entry(), grab_mapping_entry() and dax_unlock_mapping_entry(). Signed-off-by: Ross Zwisler

[PATCH V3 02/10] ras: acpi/apei: cper: generic error data entry v3 per ACPI 6.1

Currently when a RAS error is reported it is not timestamped. The ACPI 6.1 spec adds the timestamp field to the generic error data entry v3 structure. The timestamp of when the firmware generated the error is now being reported. Signed-off-by: Jonathan (Zhixiong) Zhang

[PATCH V3 03/10] efi: parse ARMv8 processor error

Add support for ARMv8 Common Platform Error Record (CPER). UEFI 2.6 specification adds support for ARMv8 specific processor error information to be reported as part of the CPER records. This provides more detail on for processor error logs. Signed-off-by: Jonathan (Zhixiong) Zhang

[PATCH V3 09/10] trace, ras: add ARM processor error trace event

Currently there are trace events for the various RAS errors with the exception of ARM processor type errors. Add a new trace event for such errors so that the user will know when they occur. These trace events are consistent with the ARM processor error section type defined in UEFI 2.6 spec

[PATCH V3 05/10] acpi: apei: handle SEA notification type for ARMv8

ARM APEI extension proposal added SEA (Synchrounous External Abort) notification type for ARMv8. Add a new GHES error source handling function for SEA. If an error source's notification type is SEA, then this function can be registered into the SEA exception handler. That way GHES will parse and

[PATCH V3 06/10] acpi: apei: panic OS with fatal error status block

From: "Jonathan (Zhixiong) Zhang" Even if an error status block's severity is fatal, the kernel does not honor the severity level and panic. With the firmware first model, the platform could inform the OS about a fatal hardware error through the non-NMI GHES notification

[PATCH V3 07/10] efi: print unrecognized CPER section

UEFI spec allows for non-standard section in Common Platform Error Record. This is defined in section N.2.3 of UEFI version 2.5. Currently if the CPER section's type (UUID) does not match with one of the section types that the kernel knows how to parse, the section is skipped. Therefore, user is

[PATCH V3 04/10] arm64: exception: handle Synchronous External Abort

SEA exceptions are often caused by an uncorrected hardware error, and are handled when data abort and instruction abort exception classes have specific values for their Fault Status Code. When SEA occurs, before killing the process, go through the handlers registered in the notification list.

[PATCH V3 10/10] arm64: KVM: add guest SEA support

Currently external aborts are unsupported by the guest abort handling. Add handling for SEAs so that the host kernel reports SEAs which occur in the guest kernel. Signed-off-by: Tyler Baicar --- arch/arm/include/asm/kvm_arm.h | 1 +

Re: [PATCH] ARCv2: intc: untangle SMP, MCIP and IDU

On 10/07/2016 10:31 AM, Alexey Brodkin wrote: >> They are ugly I agree - but not portable - really ? The whole point is to >> make >> > this work on BE w/o changing the src code - this details remains hidden in >> > an >> > obscure header. > That's what I learned the hard way. > At least I was

Re: [PATCH v4] Adding missing features of Coresight PTM components

On 7 October 2016 at 06:16, Muhammad Abdul WAHAB wrote: > In the current driver for Coresight components, two features of PTM > components are missing: > > 1. Branch Broadcasting (present also in ETM but called Branch Output) > 2. Return Stack (only present

Re: [RFC PATCH-tip v4 02/10] locking/rwsem: Stop active read lock ASAP

On 10/06/2016 05:47 PM, Dave Chinner wrote: On Thu, Oct 06, 2016 at 11:17:18AM -0700, Davidlohr Bueso wrote: On Thu, 18 Aug 2016, Waiman Long wrote: Currently, when down_read() fails, the active read locking isn't undone until the rwsem_down_read_failed() function grabs the wait_lock. If the

Re: Zram for FreeBSD

Cool, I am starting to get a good grasp on what is going on (I’ll probably need to use FreeBSD’s archive.h as opposed to Linux’s crypto.h). I am trying to get a hold on what exactly I need to port to FreeBSD. I see that (as Nitin suggested) zsmalloc is the main brains of handling the objects

[git pull] vfs pile 1 (splice)

splice stuff. There are conflicts in lustre; proposed resolution is in #merge-candidate (same as it is in linux-next). There's a bunch of branches this cycle, both mine and from other folks and I'd rather send pull requests separately. This one is the conversion of ->splice_read() to

Re: [PATCH] net: macb: NULL out phydev after removing mdio bus

Le 07/10/2016 à 17:13, Xander Huff a écrit : > From: Nathan Sullivan > > To ensure the dev->phydev pointer is not used after becoming invalid in > mdiobus_unregister, set it to NULL. This happens when removing the macb > driver without first taking its interface down,

Re: [PATCH] mm: check VMA flags to avoid invalid PROT_NONE NUMA balancing

On Fri, Oct 07, 2016 at 08:34:15AM -0700, Linus Torvalds wrote: > Would you be willing to look at doing that kind of purely syntactic, > non-semantic cleanup first? Sure, more than happy to do that! I'll work on a patch for this. > I think that if we end up having the FOLL_FORCE semantics, we're

Re: [PATCH 3/3] mtd: s3c2410: parse the device configuration from OF node

On Wed, Oct 05, 2016 at 08:46:57PM -0300, Sergio Prado wrote: > Allows configuring Samsung's s3c2410 memory controller using a > devicetree. > > Signed-off-by: Sergio Prado > --- > drivers/mtd/nand/s3c2410.c | 171 > ++--- >

Re: [PATCH V2 2/2] fs/super.c: don't fool lockdep in freeze_super() and thaw_super() paths

On 10/06, Johannes Weiner wrote: > > On Tue, Oct 04, 2016 at 01:48:00PM +0200, Michal Hocko wrote: > > Johannes is already looking into this > > http://lkml.kernel.org/r/20161004093216.ga21...@cmpxchg.org > > > > On Tue 04-10-16 13:43:43, Oleg Nesterov wrote: > > > because of kernel bug: > > > > >

[PATCH 3/3] Staging: i4l: Error "open brace { should be on the previous line" fixed.

Error "open brace { should be on the previous line" caught by checkpatch.pl fixed. Signed-off-by: Harman Kalra --- drivers/staging/i4l/icn/icn.c |3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/drivers/staging/i4l/icn/icn.c

Re: [PATCH v2 2/4] ACPI / gpio: Add support for naming GPIOs

On Thu, Sep 29, 2016 at 4:39 PM, Mika Westerberg wrote: > DT has property 'gpio-line-names' to name GPIO lines the controller has if > present. Use this very same property in ACPI as well to provide nice names > for the GPIOS. One nit below. > @@ -835,6 +875,9

Re: [PATCH v13 03/15] iommu/dma: Allow MSI-only cookies

Hi Alex, On 06/10/2016 22:17, Alex Williamson wrote: > On Thu, 6 Oct 2016 08:45:19 + > Eric Auger wrote: > >> From: Robin Murphy >> >> IOMMU domain users such as VFIO face a similar problem to DMA API ops >> with regard to mapping MSI messages

Re: [PATCH v13 04/15] genirq/msi: Introduce the MSI doorbell API

Hi Alex, On 06/10/2016 22:17, Alex Williamson wrote: > On Thu, 6 Oct 2016 08:45:20 + > Eric Auger wrote: > >> We introduce a new msi-doorbell API that allows msi controllers >> to allocate and register their doorbells. This is useful when >> those doorbells are

[PATCH 2/3] Staging: i4l: Error "open brace { should be on the previous line" fixed.

Errors "open brace { should be on the previous line" caught by checkpatch.pl fixed. Signed-off-by: Harman Kalra --- drivers/staging/i4l/icn/icn.h |3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/drivers/staging/i4l/icn/icn.h

[PATCH 21/26] pctv452e: don't call BUG_ON() on non-fatal error

There are some conditions on this driver that are tested with BUG_ON() with are not serious enough to hang a machine. So, just return an error if this happens. Signed-off-by: Mauro Carvalho Chehab --- drivers/media/usb/dvb-usb/pctv452e.c | 8 +--- 1 file changed,

[PATCH 02/26] cinergyT2-core: don't do DMA on stack

The USB control messages require DMA to work. We cannot pass a stack-allocated buffer, as it is not warranted that the stack would be into a DMA enabled area. Signed-off-by: Mauro Carvalho Chehab --- drivers/media/usb/dvb-usb/cinergyT2-core.c | 45

[PATCH 00/26] Don't use stack for DMA transers on dvb-usb drivers

Sending URB control messages from stack was never supported. Yet, on x86, the stack was usually at a memory region that allows DMA transfer. So, several drivers got it wrong. On Kernel 4.9, if VMAP_STACK=y, none of those drivers will work, as the stack won't be on a DMA-able area anymore. So,

[PATCH 20/26] pctv452e: don't do DMA on stack

The USB control messages require DMA to work. We cannot pass a stack-allocated buffer, as it is not warranted that the stack would be into a DMA enabled area. Signed-off-by: Mauro Carvalho Chehab --- drivers/media/usb/dvb-usb/pctv452e.c | 110

[PATCH 09/26] dibusb: don't do DMA on stack

The USB control messages require DMA to work. We cannot pass a stack-allocated buffer, as it is not warranted that the stack would be into a DMA enabled area. Signed-off-by: Mauro Carvalho Chehab --- drivers/media/usb/dvb-usb/dibusb-common.c | 106

[PATCH 13/26] dtt200u-fe: handle errors on USB control messages

If something goes wrong, return an error code, instead of assuming that everything went fine. Signed-off-by: Mauro Carvalho Chehab --- drivers/media/usb/dvb-usb/dtt200u-fe.c | 38 +++--- 1 file changed, 30 insertions(+), 8 deletions(-) diff

[PATCH 06/26] cxusb: don't do DMA on stack

The USB control messages require DMA to work. We cannot pass a stack-allocated buffer, as it is not warranted that the stack would be into a DMA enabled area. Signed-off-by: Mauro Carvalho Chehab --- drivers/media/usb/dvb-usb/cxusb.c | 20 +++-

[PATCH 04/26] cinergyT2-fe: cache stats at cinergyt2_fe_read_status()

Instead of sending USB commands for every stats call, collect them once, when status is updated. As the frontend kthread will call it on every few seconds, the stats will still be collected. Besides reducing the amount of USB/I2C transfers, this also warrants that all stats will be collected at

[PATCH 12/26] dtt200u-fe: don't do DMA on stack

The USB control messages require DMA to work. We cannot pass a stack-allocated buffer, as it is not warranted that the stack would be into a DMA enabled area. Signed-off-by: Mauro Carvalho Chehab --- drivers/media/usb/dvb-usb/dtt200u-fe.c | 66

[PATCH 03/26] cinergyT2-core:: handle error code on RC query

There's no sense on decoding and generating a RC key code if there was an error on the URB control message. Signed-off-by: Mauro Carvalho Chehab --- drivers/media/usb/dvb-usb/cinergyT2-core.c | 9 ++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git

[PATCH 25/26] dw2102: return error if su3000_power_ctrl() fails

Instead of silently ignoring the error, return it. Signed-off-by: Mauro Carvalho Chehab --- drivers/media/usb/dvb-usb/dw2102.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/media/usb/dvb-usb/dw2102.c b/drivers/media/usb/dvb-usb/dw2102.c

[PATCH 08/26] dib0700_core: don't use stack on I2C reads

Be sure that I2C reads won't use stack by passing a pointer to the state buffer, that we know it was allocated via kmalloc, instead of relying on the buffer allocated by an I2C client. Signed-off-by: Mauro Carvalho Chehab --- drivers/media/usb/dvb-usb/dib0700_core.c |

[PATCH 14/26] dtt200u: don't do DMA on stack

From: Mauro Carvalho Chehab The USB control messages require DMA to work. We cannot pass a stack-allocated buffer, as it is not warranted that the stack would be into a DMA enabled area. Signed-off-by: Mauro Carvalho Chehab Signed-off-by: Mauro

  1   2   3   4   5   6   7   8   9   10   >