* Kees Cook wrote:
> If an overlapping memcpy() is ever attempted, we should at least report
> it, in case it might lead to problems, so it could be changed to a
> memmove() call instead.
>
> Suggested-by: Ingo Molnar
> Signed-off-by: Kees Cook
On Thu, Apr 28, 2016 at 11:43 PM, Ingo Molnar wrote:
>
> * Kees Cook wrote:
>
>> If an overlapping memcpy() is ever attempted, we should at least report
>> it, in case it might lead to problems, so it could be changed to a
>> memmove() call instead.
>>
>>
Hi All,
On Fri, 29 Apr 2016 16:45:43 +1000 Stephen Rothwell
wrote:
>
> After merging the akpm-current tree, today's linux-next build (x86_64
> allmodconfig) produced this warning:
>
> drivers/scsi/ipr.c: In function 'ipr_show_device_id':
> drivers/scsi/ipr.c:4462:34:
On Tue, Apr 26, 2016 at 05:38:18PM +0800, Rui Teng wrote:
> On 4/25/16 1:21 PM, js1...@gmail.com wrote:
> >From: Joonsoo Kim
> >
> >Attached cover-letter:
> >
> >This series try to solve problems of current CMA implementation.
> >
> >CMA is introduced to provide physically
On 29 April 2016 at 01:06, Douglas Anderson wrote:
> This series picks patches from various different places to produce what
> I consider the best solution to getting consistent mmc and mmcblk
> ordering.
>
> Why consistent ordering and why not just use UUIDs? IMHO
On 04/29/2016 09:15 AM, Pavel Machek wrote:
> Hi!
>
>> On n900, probe finishes ok (verified by adding printks), and the
>> device shows up in /sys, but I don't get /dev/video* or
>> /dev/v4l-subdev*.
>>
>> Other drivers (back and front camera) load ok, and actually work. Any
>> idea what could
On Thu, 28 Apr 2016, Josh Poimboeuf wrote:
> On Thu, Apr 28, 2016 at 02:21:31PM -0400, Jessica Yu wrote:
> > +++ Miroslav Benes [28/04/16 16:34 +0200]:
> > > Current object-walking helper checks the presence of obj->funcs to
> > > determine the end of objs array in klp_object structure. This is
>
On Fri, Apr 29, 2016 at 12:18 AM, Ingo Molnar wrote:
>
> * Kees Cook wrote:
>
>> From: Yinghai Lu
>>
>> This change makes later calculations about where the kernel is located
>> easier to reason about. To better understand this
Hi,
On 28 April 2016 at 23:28, Rob Clark wrote:
> On Wed, Apr 27, 2016 at 2:39 AM, Daniel Vetter wrote:
>> On Tue, Apr 26, 2016 at 01:48:02PM -0700, Greg Hackmann wrote:
>>> A (per-CRTC?) array of fences would be more flexible. And even in the cases
>>>
On Thu, Apr 28, 2016 at 11:26 AM, Maxime Ripard
wrote:
> Still, moving it to a "framework" that has been inactive for so long
> (and you even mention it in your PR) doesn't seem like the right move.
I still think sorting the driver into the right bucket has a
On Fri, Apr 29, 2016 at 3:17 AM, Bjorn Helgaas wrote:
> On Fri, Apr 15, 2016 at 07:06:42PM +0200, Tomasz Nowicki wrote:
>> From: Jayachandran C
>>
>> Add config option PCI_GENERIC_ECAM and file drivers/pci/ecam.c to
>> provide generic functions for
Am Freitag, 29. April 2016, 03:29:50 schrieb George Spelvin:
Hi George,
> > 1. the individual bits of a given 32 bit time stamp are independent
> >
> >(or IID in terms of NIST)
>
> They're not independent, nor are they identically distributed.
That is an interesting statement: you say
On Mi, 2016-04-27 at 20:16 +0200, Noralf Trønnes wrote:
> I have also added patches that converts qxl and udl to use this
> deferred io support. I have only compile tested it, no functional
> testing.
> I know that qxl is purely a software thing so I could actually test
> it, but
> I have never
On Thu, Apr 28, 2016 at 03:56:33PM -0700, Greg KH wrote:
> On Thu, Apr 28, 2016 at 11:18:33PM +0100, Richard W.M. Jones wrote:
> > Currently autoconf spends 25ms (on my laptop) testing if the UART
> > exported to it by KVM is an 8250 without FIFO and/or with strange
> > quirks, which it obviously
On Thursday 07 April 2016 03:17 PM, Kishon Vijay Abraham I wrote:
> Hi,
>
> On Friday 25 March 2016 07:39 AM, Simon Horman wrote:
>> On Mon, Mar 07, 2016 at 10:58:39AM +0900, Simon Horman wrote:
>>> Add fallback compatibility strings for rcar phy drivers.
>>>
>>> In the case of Renesas R-Car
On Mon, Apr 18, 2016 at 8:24 PM, Ray Jui wrote:
> On 4/17/2016 8:34 PM, Yendapally Reddy Dhananjaya Reddy wrote:
>>>
>>> /* not all Iproc GPIO pins can be muxed individually */
>>> if (!chip->pinmux_is_supported)
>>> return 0;
>
>
> NS2 does
On Tue, Apr 19, 2016 at 11:43 AM, Laxman Dewangan wrote:
> Use of_device_get_match_data() for getting matched data
> instead of implementing this locally.
>
> Signed-off-by: Laxman Dewangan
> Reviewed-by: Stephen Warren
Patch
This exports debugging helper pe_level_printk() and corresponding macroses
so they can be used in npu-dma.c.
Signed-off-by: Alexey Kardashevskiy
---
arch/powerpc/platforms/powernv/pci-ioda.c | 9 +
arch/powerpc/platforms/powernv/pci.h | 9 +
2 files changed,
On Mon, Apr 25, 2016 at 12:38 PM, Laxman Dewangan wrote:
> NVIDIA's Tegra210 support the HW debounce in the GPIO controller
> for all its GPIO pins.
>
> Add support for setting debounce timing by implementing the
> set_debounce callback of gpiochip.
>
> Signed-off-by:
The > here should be >= or we go beyond the end for the array.
Signed-off-by: Dan Carpenter
diff --git a/drivers/iio/dac/ad5592r-base.c b/drivers/iio/dac/ad5592r-base.c
index 948f600..69bde59 100644
--- a/drivers/iio/dac/ad5592r-base.c
+++
On 2016-04-29 09:16, Wolfram Sang wrote:
>> Yes, obviously... I'll make that change locally and wait for the rest.
> Another nit: You could use '--strict' with checkpatch and see if you
> want to fix the issues reported. I am not keen on those (except for
> 'space around operators'), it's a matter
On 04/28/2016 02:35 PM, Michal Hocko wrote:
On Thu 28-04-16 10:53:18, Vlastimil Babka wrote:
On 04/20/2016 09:47 PM, Michal Hocko wrote:
From: Michal Hocko
THP requests skip the direct reclaim if the compaction is either
deferred or contended to reduce stalls which wouldn't
Signed-off-by: Manav Batra
Removes multiple blank lines.
---
drivers/staging/sm750fb/ddk750_power.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/drivers/staging/sm750fb/ddk750_power.c
b/drivers/staging/sm750fb/ddk750_power.c
index b3c3791..5d92a09 100644
---
On 2016-04-28 12:39, Crestez Dan Leonard wrote:
> On 04/27/2016 11:39 AM, Peter Rosin wrote:
>> On 2016-04-23 23:32, Jonathan Cameron wrote:
>>> On 20/04/16 18:17, Crestez Dan Leonard wrote:
The MPU has an auxiliary I2C bus for connecting external
sensors. This bus has two operating
On Fri 29-04-16 16:59:37, Aaron Lu wrote:
> On Thu, Apr 28, 2016 at 01:21:35PM +0200, Michal Hocko wrote:
> > All of them are order-2 and this was a known problem for "mm, oom:
> > rework oom detection" commit and later should make it much more
> > resistant to failures for higher (!costly)
Kernel hang is observed when pci-hyperv module is release with device
drivers still attached. E.g. when I do 'rmmod pci_hyperv' with BCM5720
device pass-through-ed (tg3 module) I see the following:
NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [rmmod:2104]
...
Call Trace:
[]
In some Intel platforms, a single usb port is shared between USB host
and device controllers. The shared port is under control of a switch
which is defined in the Intel vendor defined extended capability for
xHCI.
This patch adds the support to detect and create the platform device
for the port
Several Intel PCHs and SOCs have an internal mux that is used to
share one USB port between device controller and host controller.
The mux is handled through the Dual Role Configuration Register.
Signed-off-by: Heikki Krogerus
Signed-off-by: Lu Baolu
In some Intel platforms, a single usb port is shared between USB host
and device controller. The shared port is under control of GPIO pins.
This patch adds the support for USB GPIO controlled port mux.
[baolu: removed .owner per platform_no_drv_owner.cocci]
Signed-off-by: David Cohen
Intel SOC chips are featured with USB dual role. The host role
is provided by Intel xHCI IP, and the gadget role is provided
by IP from designware. Tablet platform designs always share a
single port for both host and gadget controllers. There is a
mux to switch the port to the right controller
Add LRNG compilation support.
Signed-off-by: Stephan Mueller
---
crypto/Kconfig | 10 ++
crypto/Makefile | 1 +
2 files changed, 11 insertions(+)
diff --git a/crypto/Kconfig b/crypto/Kconfig
index 93a1fdc..938f2dc 100644
--- a/crypto/Kconfig
+++ b/crypto/Kconfig
Signed-off-by: Manav Batra
Improved comparison to NULL and removed some blank lines.
---
drivers/staging/sm750fb/ddk750_dvi.c | 7 +++
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/drivers/staging/sm750fb/ddk750_dvi.c
Ben Gamari writes:
> [ Unknown signature status ]
> Mika Westerberg writes:
>
>> On Tue, Apr 26, 2016 at 02:44:13AM +0200, Ben Gamari wrote:
>>>
> snip
>
>>> It looks very much like these are describing the same device. Perhaps
>>> the
On Thu, Apr 28, 2016 at 2:12 PM, wrote:
> From: Patrice Chotard
>
> This series cleans and fixes some bugs in MFD/GPIO STMPE drivers and prepare
> the ground to add new STMPE1600 support.
This series is finished and looking good from a GPIO
Hi Hans and Pavel,
On Fri, Apr 29, 2016 at 09:31:51AM +0200, Hans Verkuil wrote:
> On 04/29/2016 09:15 AM, Pavel Machek wrote:
> > Hi!
> >
> >> On n900, probe finishes ok (verified by adding printks), and the
> >> device shows up in /sys, but I don't get /dev/video* or
> >> /dev/v4l-subdev*.
>
* Kees Cook wrote:
> If an overlapping memcpy() is ever attempted, we should at least report
> it, in case it might lead to problems, so it could be changed to a
> memmove() call instead.
>
> Suggested-by: Ingo Molnar
> Signed-off-by: Kees Cook
Hi,
On 04/28/2016 02:42 PM, Arnd Bergmann wrote:
> With the addition of VUDC, the USBIP stack can now be used on
> configurations without USB host support, but trying to build
Not exactly. This is the goal but unfortunately for now this will not
work... Most of USB_IP common functions operates
On Tue, Apr 19, 2016 at 10:00 AM, Maxime Coquelin
wrote:
> 2016-04-08 11:38 GMT+02:00 Linus Walleij :
>> while ((stat = readl_relaxed(vic->base + VIC_IRQ_STATUS))) {
>> irq = ffs(stat) - 1;
>>
Hi Han,
On Tue, 23 Feb 2016 17:04:51 -0600
Han Xu wrote:
> i.MX6QP and i.MX7D BCH module integrated a new feature to detect the
> bitflip number for erased NAND page. So for these two platform, set the
> erase threshold to ecc_strength and if bitflip detected, GPMI driver will
>
>
> From: Gustavo Padovan
>
> Simplifies the API to only receive the fence it needs to add to the
> sync and create a name for the sync_file based on the fence context and
> seqno.
>
> Signed-off-by: Gustavo Padovan
>
IBM POWER8 NVlink systems come with Tesla K40-ish GPUs each of which
also has a couple of fast speed links (NVLink). The interface to links
is exposed as an emulated PCI bridge which is included into the same
IOMMU group as the corresponding GPU.
In the kernel, NPUs get a separate PHB of the
Hi Mark,
Can you give me some comments regarding this patch? Am I following the right
track? This is the first time that I am using ALSA SoC so pardon me if I am
making some mistake. I would appreciate some kind of input. I tested this only
on a ARC SDP and it is working.
On 27-04-2016 11:05,
On Thu, Apr 28, 2016 at 09:43:14PM -0700, David Carrillo-Cisneros wrote:
> Move code around, delete unnecesary code and do some renaming in
> in order to increase readibility of next patches. Create cqm.h file.
*sigh*, this is a royal pain in the backside to review.
Please just completely wipe
On Mon, Apr 11, 2016 at 7:37 AM, Prarit Bhargava wrote:
>
>
> On 03/31/2016 12:59 AM, Len Brown wrote:
>>> Len,
>>>
>>> Your patch does
>>>
>>> + skl_cstates[5].disabled = 1;/* C8-SKL */
>>> + skl_cstates[6].disabled = 1;/* C9-SKL */
>>>
>>> and I don't
Hi Andrew,
Today's linux-next merge of the akpm-current tree got a conflict in:
include/linux/efi.h
between commit:
2c23b73c2d02 ("Ard Biesheuvel ")
from the tip tree and commit:
9f2c36a7b097 ("include/linux/efi.h: redefine type, constant, macro from
generic
On Tue, Apr 26 2016, Michal Hocko wrote:
> Hi,
> we have discussed this topic at LSF/MM this year. There was a general
> interest in the scope GFP_NOFS allocation context among some FS
> developers. For those who are not aware of the discussion or the issue
> I am trying to sort out (or at least
Hi,
John Youn writes:
>> "Du, Changbin" writes:
>>> Hi, Balbi,
>>>
>>> The step to reproduce this issue is:
>>> 1) connect device to a host and wait its enumeration.
>>> 2) trigger software disconnect by calling function
>>>
On 04/28/2016 02:57 PM, Daniel Wagner wrote:
> Only one complete_all() user could been identified so far, which happens
> to be drivers/base/power/main.c. Several waiters appear when suspend
> to disk or mem is executed.
BTW, this is what I get when doing a 'echo "disk" > /sys/power/state' on
a 4
Hi Herbert, Ted, Andi,
The following patch set provides a different approach to /dev/random which
I call Linux Random Number Generator (LRNG) to collect entropy within the Linux
kernel. The main improvements compared to the legacy /dev/random is to provide
sufficient entropy during boot time as
When selecting the LRNG for compilation, disable the legacy /dev/random
implementation.
The LRNG is a drop-in replacement for the legacy /dev/random which
implements the same in-kernel and user space API. Only the hooks of
/dev/random into other parts of the kernel need to be disabled.
* Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the xen-tip tree got a conflict in:
>
> drivers/firmware/efi/arm-runtime.c
>
> between commit:
>
> 14c43be60166 ("efi/arm*: Drop writable mapping of the UEFI System table")
>
> from the tip tree
On Thu, Apr 28, 2016 at 3:32 PM, Rob Herring wrote:
> On Thu, Apr 28, 2016 at 4:46 PM, Frank Rowand wrote:
>> From: Frank Rowand
>>
>> Determining which kernel config options need to be enabled for a
>> given devicetree can
2016-04-29 1:18 GMT+03:00 Richard W.M. Jones :
> [This is an opinionated patch, mainly for discussion.]
>
> I'm trying to reduce the time taken in the kernel in initcalls, with
> my aim being to reduce the current ~700ms spent in initcalls before
> userspace, down to something
>From smuel...@chronox.de Fri Apr 29 04:56:49 2016
From: Stephan Mueller
To: George Spelvin
Cc: herb...@gondor.apana.org.au, linux-cry...@vger.kernel.org,
linux-kernel@vger.kernel.org, sandyinch...@gmail.com, ty...@mit.edu
Subject: Re: random(4) changes
On (04/29/16 14:44), Minchan Kim wrote:
[..]
> > @@ -1945,8 +1944,6 @@ struct zs_pool *zs_create_pool(const char *name,
> > gfp_t flags)
>
> So, we can remove flags parameter passing and comment about that.
good point; gfp_t is now unneeded there. will resubmit 0001 later.
> Other than that,
>
On Fri, Apr 29, 2016 at 08:39:36AM +0200, Ingo Molnar wrote:
> With considerable pain we just got rid of paravirt_enabled() in the
> x86 tree, and Xen is now reintroducing it in the EFI code.
I think Matt is working towards removing EFI_PARAVIRT but he'll comment
himself when he wakes up... :)
Hi Han,
On Wed, 13 Apr 2016 00:43:51 +0200
Boris Brezillon wrote:
> Hi Han,
>
> On Tue, 12 Apr 2016 17:06:33 -0500
> Han Xu wrote:
>
> > change the way to calculate pagesize to get correct free oob space for
> > legacy_set_geometry
Hi Han,
On Tue, 23 Feb 2016 17:04:50 -0600
Han Xu wrote:
> add the clocks and clock-names in DT property, gpmi-io clock is
> mandatory for all platforms, but some platforms, such as i.MX6Q may
> need more extra clocks for submodules. More details please refer to the
> SoC
On Thursday 14 April 2016 03:07 PM, Rafał Miłecki wrote:
> Northstar is a family of SoCs used in home routers. They have USB 2.0
> and 3.0 controllers with PHYs that need to be properly initialized.
> This driver provides PHY init support in a generic way and can be bound
> with an EHCI
The pnv_ioda_pe struct keeps an array of peers. At the moment it is only
used to link GPU and NPU for 2 purposes:
1. Access NPU quickly when configuring DMA for GPU - this was addressed
in the previos patch by removing use of it as DMA setup is not what
the kernel would constantly do.
2.
On 04/28/2016 05:47 PM, Javier González wrote:
Until now, the dma pool have been exclusively used to allocate the ppa
list being sent to the device. In pblk (upcoming), we use these pools to
allocate metadata too. Thus, we generalize the names of some variables
on the dma helper functions to
Hi everyone,
This is a repost from a different address as it seems the previous one ended in
Gmail junk due to a domain error..
I added more info found while blindly debugging the issue.
Short version:
I'm having an issue with direct DMA transfer from a device to host memory.
It seems some of
On Thursday 14 April 2016 03:07 PM, Rafał Miłecki wrote:
> Northstar is a family of SoCs used in home routers. They have USB 2.0
> and 3.0 controllers with PHYs that need to be properly initialized.
> This driver provides PHY init support in a generic way and can be bound
> with an EHCI
On Fri, Apr 29, 2016 at 03:51:45PM +0900, Joonsoo Kim wrote:
> Hello, Mel.
>
> IIUC, you may miss that alloc_contig_range() currently does linear
> reclaim/migration. Your comment is largely based on this
> misunderstanding so please keep it in your mind when reading the
> reply.
>
Ok, you're
On Fri 29-04-16 11:16:44, Vlastimil Babka wrote:
> On 04/28/2016 02:35 PM, Michal Hocko wrote:
[...]
> >My main point was to simplify the code and get rid of as much compaction
> >specific hacks as possible. We might very well drop this later on but it
> >would be at least less code to grasp
This isn't V2, but V3
On 29-04-16, 10:22, Sudeep Holla wrote:
> Functions dev_pm_opp_of_{cpumask_,}remove_table removes/frees all the
> static OPP entries associated with the device and/or all cpus(in case
> of cpumask) that are created from DT.
>
> However the OPP entries are populated reading
On Fri, Apr 29, 2016 at 8:39 AM, Gaurav Minocha
wrote:
> On Thu, Apr 28, 2016 at 3:32 PM, Rob Herring wrote:
>> On Thu, Apr 28, 2016 at 4:46 PM, Frank Rowand wrote:
>>> From: Frank Rowand
>>>
>>>
Hi Ezequiel,
Thanks for the update. It's indeed reasonable to have all the
switching infrastructure in ledtrig-panic.c.
I've noticed two minor issues below.
On 04/29/2016 12:03 AM, Ezequiel Garcia wrote:
This commit adds a new led_cdev flag LED_PANIC_INDICATOR, which
allows to mark a specific
* Kees Cook wrote:
> On Thu, Apr 28, 2016 at 11:43 PM, Ingo Molnar wrote:
> >
> > * Kees Cook wrote:
> >
> >> If an overlapping memcpy() is ever attempted, we should at least report
> >> it, in case it might lead to problems, so
After async atomic_commit callback, drm_atomic_clean_old_fb will
cleanup all old fb, but because async, the old fb may be also on
the vop hardware, dma will access the old fb buffer, clean old
fb will cause iommu page fault.
Fix the problem by reference the fb and unreference it when the fb
* Kees Cook wrote:
> I don't agree. We do still have embedded systems running x86 kernels, and we
> have cases where we're running multiple kernels in memory (like kdump). I
> think
> the memory savings is worth the complexity, especially since the complexity
> is
>
On Mon, Apr 18, 2016 at 9:30 PM, Ray Jui wrote:
> On 4/15/2016 1:24 AM, Linus Walleij wrote:
>>
>> On Wed, Apr 13, 2016 at 2:15 AM, Ray Jui wrote:
>>
>>> In some of the future iProc based SoCs, pinconf is handled by another
>>> block and the iProc GPIO
The introduction of switch_mm_irqs_off() brought back an old bug
regarding the use of preempt_enable_no_resched:
As part of 62b94a08da1b ("sched/preempt: Take away
preempt_enable_no_resched() from modules"), the definition of
preempt_enable_no_resched() is only available in built-in code,
not in
On Tue, Apr 19, 2016 at 11:04 AM, Maxime Coquelin
wrote:
> 2016-04-08 11:43 GMT+02:00 Linus Walleij :
>> On Thu, Mar 31, 2016 at 5:09 PM, Maxime Coquelin
>> wrote:
>>
>>> +static int stm32_gpio_to_irq(struct
On Mon, Apr 25, 2016 at 12:38 PM, Laxman Dewangan wrote:
> Move the file scoped multiple global variable from Tegra GPIO
> driver to the structure and make this as gpiochip data which
> can be referred from GPIO chip callbacks.
>
> Signed-off-by: Laxman Dewangan
On Tue, 23 Feb 2016 17:04:49 -0600
Han Xu wrote:
> From: Han Xu
>
> support GPMI NAND on i.MX7D
>
> Signed-off-by: Han Xu
> ---
> drivers/mtd/nand/gpmi-nand/bch-regs.h | 14 +++---
> drivers/mtd/nand/gpmi-nand/gpmi-lib.c
This replaces magic constants for TCE Kill IODA2 register with macros.
Signed-off-by: Alexey Kardashevskiy
Reviewed-by: David Gibson
---
arch/powerpc/platforms/powernv/pci-ioda.c | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff
On Wed, 27 Apr, at 10:41:32AM, Alex Thorlton wrote:
>
> From what I know, this works because the first PGD entry (the one
> containing the identity mappings) of the trampoline_pgd is shared with
> the main kernel PGD (init_level4_pgt), so when __map_region maps this
> stuff into the
This uses the page size from iommu_table instead of hard-coded 4K.
This should cause no change in behavior.
While we are here, move bits around to prepare for further rework
which will define and use iommu_table_group_ops.
Signed-off-by: Alexey Kardashevskiy
Reviewed-by: David
The upcoming NVLink passthrough support will require NPU code to cope
with two DMA windows.
This adds a pnv_npu_set_window() helper which programs 32bit window to
the hardware. This also adds multilevel TCE support.
This adds a pnv_npu_unset_window() helper which removes the DMA window
from the
(Note that we have two chains of e-mails crossing mid-stream. I'm in
the middle of working on a much longer reply to your previous e-mail.)
>> They're not independent, nor are they identically distributed.
> That is an interesting statement: you say that the time stamp has holes
> in it, i.e.
On 28 April 2016 at 23:30, Andrew Morton wrote:
> On Thu, 28 Apr 2016 21:04:18 +0200 Mathias Krause
> wrote:
>
>> If /proc//environ gets read before the envp[] array is fully set
>> up in create_{aout,elf,elf_fdpic,flat}_tables(), we might end
Signed-off-by: Manav Batra
Fixed alignment of parantheses.
---
drivers/staging/rts5208/ms.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/rts5208/ms.c b/drivers/staging/rts5208/ms.c
index 0f0cd4a..6c5ef29 100644
---
Hi Andrew,
After merging the akpm-current tree, today's linux-next build (x86_64
allmodconfig) produced this warning:
drivers/scsi/ipr.c: In function 'ipr_show_device_id':
drivers/scsi/ipr.c:4462:34: warning: format '%llx' expects argument of type
'long long unsigned int', but argument 4 has
Hi Linus,
Here are a two mmc fixes intended for v4.6 rc6. It's based on v4.6 rc4.
Details are as usual found in the signed tag. Please pull this in!
Kind regards
Ulf Hansson
The following changes since commit c3b46c73264b03000d1e18b22f5caf63332547c9:
Linux 4.6-rc4 (2016-04-17 19:13:32
* Kees Cook wrote:
> From: Yinghai Lu
>
> This change makes later calculations about where the kernel is located
> easier to reason about. To better understand this change, we must first
> clarify what VO and ZO are. They were introduced in commits
On Thu, Apr 28, 2016 at 6:56 AM, Bjorn Helgaas wrote:
> On Wed, Apr 27, 2016 at 09:55:45PM -0700, Yinghai Lu wrote:
>> On Fri, Apr 22, 2016 at 1:49 PM, Bjorn Helgaas wrote:
>> > [+cc Ben, Michael]
>> > I'm kind of confused here. There are two ways to mmap
On Wed, Apr 27, 2016 at 10:39:29AM -0500, Christoph Lameter wrote:
> On Tue, 26 Apr 2016, Andrew Morton wrote:
>
> > : CONFIG_FREELIST_RANDOM bugs me a bit - "freelist" is so vague.
> > : CONFIG_SLAB_FREELIST_RANDOM would be better. I mean, what Kconfig
> > : identifier could be used for
On Fri, Apr 29, 2016 at 09:30:27AM +0200, Ben Gamari wrote:
> Ben Gamari writes:
>
> > [ Unknown signature status ]
> > Mika Westerberg writes:
> >
> >> On Tue, Apr 26, 2016 at 02:44:13AM +0200, Ben Gamari wrote:
> >>>
> > snip
> >
> >>>
On Thu, Apr 28, 2016 at 2:13 PM, wrote:
> From: Patrice Chotard
>
> This update allows to use registers map as following :
> regs[reg_index + offset] instead of
> regs[reg_index] + offset
>
> This makes code clearer and will facilitate the
>
> From: Gustavo Padovan
>
> struct sync_merge_data already have documentation on top of the
> struct definition. No need to duplicate it.
>
> Signed-off-by: Gustavo Padovan
> Reviewed-by: Maarten Lankhorst
On Fri 29-04-16 13:47:04, Minfei Huang wrote:
> It's more convenient to use existing function helper to convert string
> "on/off" to boolean.
But kstrtobool in linux-next only does "This routine returns 0 iff the
first character is one of 'Yy1Nn0'" so it doesn't know about on/off.
Or am I missing
On Fri, 29 Apr 2016, Constantin Musca wrote:
> Minimal implementation of an IIO driver for the Freescale
> MMA7660FC 3-axis accelerometer. Datasheet:
> http://www.freescale.com.cn/files/sensors/doc/data_sheet/MMA7660FC.pdf
comments below
> Includes:
> - ACPI support;
> - read_raw for x,y,z
Commit-ID: 6f9af75faa1df61e1ee5bea8a787a90605bb528d
Gitweb: http://git.kernel.org/tip/6f9af75faa1df61e1ee5bea8a787a90605bb528d
Author: Baoquan He
AuthorDate: Thu, 28 Apr 2016 17:09:03 -0700
Committer: Ingo Molnar
CommitDate: Fri, 29 Apr 2016 09:58:26
On Fri, 29 Apr 2016, Ming Lei wrote:
> On Fri, Apr 29, 2016 at 12:59 AM, Mikulas Patocka wrote:
> >
> >
> > On Fri, 29 Apr 2016, Ming Lei wrote:
> >
> >> On Thu, Apr 28, 2016 at 11:58 PM, Mikulas Patocka
> >> wrote:
> >> >
> >> >
> >> > On Thu, 28
On Fri, 29 Apr, at 10:31:28AM, Ingo Molnar wrote:
>
> So this commit triggered the follwing build warning on x86 64-bit
> allyesconfig:
Doh! I wonder why the 0day bot didn't tell me about this?
> It's this initialization in drivers/xen/efi.c:
>
> static const struct efi efi_xen __initconst
As in fact pnv_pci_ioda2_tce_invalidate_entire() invalidates TCEs for
the specific PE rather than the entire cache, rename it to
pnv_pci_ioda2_tce_invalidate_pe(). In later patches we will add
a proper pnv_pci_ioda2_tce_invalidate_entire().
Signed-off-by: Alexey Kardashevskiy
NPU PHB TCE Kill register is exactly the same as in the rest of POWER8
so let's reuse the existing code for NPU. The only bit missing is
a helper to reset the entire TCE cache so this moves such a helper
from NPU code and renames it.
Since pnv_npu_tce_invalidate() does really invalidate the
IBM POWER8 NVlink systems contain usual Tesla K40-ish GPUs but also
contain a couple of really fast links between GPU and CPU. These links
are exposed to the userspace by the OPAL firmware as bridges.
In order to make these links work when GPU is passed to the guest,
these bridges need to be
NPU devices are emulated in firmware and mainly used for NPU NVLink
training; one NPU device is per a hardware link. Their DMA/TCE setup
must match the GPU which is connected via PCIe and NVLink so any changes
to the DMA/TCE setup on the GPU PCIe device need to be propagated to
the NVLink device
1 - 100 of 1642 matches
Mail list logo