Dne 16.8.2016 v 07:48 Michal Marek napsal(a):
> Dne 2.8.2016 v 16:01 Michal Marek napsal(a):
>> On 2016-02-03 22:19, Al Viro wrote:
>>> Shortlog:
>>> Al Viro (13):
>>> [kbuild] handle exports in lib-y objects reliably
>>> EXPORT_SYMBOL() for asm
>>> x86: move exports to actual
Hello,
On Mon, 2016-07-11 at 06:15 +, Alexey Brodkin wrote:
> Hi Russel,
>
> On Sun, 2016-07-10 at 00:19 -0700, Russell Senior wrote:
> >
> > > > > > > "Alexey" == Alexey Brodkin writes:
> > Alexey> Hi Aaron,
> > Alexey> On Sat, 2016-07-09 at 07:47 -0400, Aaron
On Fri, Aug 12, 2016 at 9:43 PM, Axel Lin wrote:
> By setting phy_set_drvdata(phy, mdiodev), struct ns2_pci_phy can be
> removed.
>
> Signed-off-by: Axel Lin
This patch and the following one work on my NS2, and generally look
acceptable to me
In ACPI bases systems, in order to be able to create platform
devices and initialize them for ARM SMMU v3 components, the IORT
kernel implementation requires a set of static functions to be
used by the IORT kernel layer to configure platform devices for
ARM SMMU v3 components.
Add static
DT based systems have a generic kernel API to configure IOMMUs
for devices (ie of_iommu_configure()).
On ARM based ACPI systems, the of_iommu_configure() equivalent can
be implemented atop ACPI IORT kernel API, with the corresponding
functions to map device identifiers to IOMMUs and retrieve the
In ARM ACPI systems, IOMMU components are specified through static
IORT table entries. In order to create platform devices for the
corresponding ARM SMMU components, IORT kernel code should be made
able to parse IORT table entries and create platform devices
dynamically.
This patch adds the
The current IORT id mapping API requires components to provide
an input requester ID (a Bus-Device-Function (BDF) identifier for
PCI devices) to translate an input identifier to an output
identifier through an IORT range mapping.
Named components do not have an identifiable source ID therefore
On systems booting with ACPI that enable the ARM SMMU components
in the kernel config options, the ARM SMMU v3 init function
(ie arm_smmu_init(), that registers the driver and sets-up bus
iommu operations) does not run only because the device tree interface
(of_find_matching_node()) fails to find
On 08/14/16 20:26, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20160812:
>
on i386:
when CONFIG_SYSFS is not enabled:
mm/built-in.o: In function `khugepaged_defrag_store':
khugepaged.c:(.text+0x47a37): undefined reference to
`single_hugepage_flag_store'
mm/built-in.o: In function
On Mon 15-08-16 17:22:36, Greg KH wrote:
> On Mon, Aug 15, 2016 at 05:06:44PM +0200, Michal Hocko wrote:
[...]
> > diff --git a/mm/slab_common.c b/mm/slab_common.c
> > index 3c6a86b4ec25..312ef6f7b7b1 100644
> > --- a/mm/slab_common.c
> > +++ b/mm/slab_common.c
> > @@ -522,7 +522,7 @@ void
On Mon, 15 Aug 2016 10:49:36 -0400
David Long wrote:
> On 08/15/2016 10:25 AM, Jonathan Corbet wrote:
> > On Fri, 12 Aug 2016 16:24:44 -0400
> > David Long wrote:
> >
> >> Some architectures (i.e.: sparc64 and arm64) make reasonable partial stack
>
On Sun, Aug 14, 2016 at 12:45:35AM -0700, Andy Lutomirski wrote:
> On Fri, Aug 12, 2016 at 7:28 AM, Josh Poimboeuf wrote:
> > show_stack_log_lvl() and dump_trace() are already preemption safe:
> >
> > - If they're running in interrupt context, preemption is already
> >
It was well-known that PGP is vulnerable to short-ID collisions,
and many experiments were done to demonstrate that. [0]
Nevertheless, real attacks started in June, some developers found
their fake keys with same name, email, and even "same" fake signatures
by more fake keys in the wild, on the
From: Colin Ian King
map is being already checked if it is null at the start of
do_zoom_dso, so the second subsequent check is superfluous
and can be removed.
Signed-off-by: Colin Ian King
---
tools/perf/ui/browsers/hists.c | 2 --
1 file
On 08/08/16 19:14, Alison Schofield wrote:
> Replace the i2c_smbus_read_byte commmands used to retrieve the sensor
> data with an i2c_master_recv command.
>
> The smbus read byte method fails because the device does not expect a
> stop condition after sending the first byte. When we issue the
On Mon, 2016-08-15 at 15:28 +0800, yuantian.t...@nxp.com wrote:
> From: Tang Yuantian
>
> The offset of Core Cluster clock control/status register
> on cluster group V3 version is different from others, and
> should be plus 0x7.
>
> Signed-off-by: Tang Yuantian
On 15.08.16 19:05, Yuval Mintz wrote:
Currently the tx channels share same pool of descriptors. Thus one channel can
block another if pool is emptied by one. But, the shaper should decide which
channel is allowed to send packets. To avoid such impact of one channel on
another, let every
On 04/08/16 14:29, Ksenija Stanojevic wrote:
> Add support for sixteen-channel 12-bit resolution ADC and its functions,
> which include general-purpose ADC readings, battery voltage measurement,
> and die temperature measurement.
>
> Signed-off-by: Ksenija Stanojevic
On 08/15/2016 06:35 AM, 河合英宏 / KAWAI,HIDEHIRO wrote:
Hi Corey,
From: Corey Minyard [mailto:cminy...@mvista.com]
Sent: Friday, August 12, 2016 10:56 PM
I'll try to test this, but I have one comment inline...
Thank you very much!
On 08/11/2016 10:17 PM, Dave Young wrote:
On 08/10/16 at
The cpsw h/w supports up to 8 tx and 8 rx channels. This patch adds
multi-queue support to the driver only, shaper configuration will
be added with separate patch series. Default shaper mode, as
before, priority mode, but with corrected priority order, 0 - is
highest priority, 7 - lowest.
The
These ops allow to control number of channels driver is allowed to
work with at cpdma level. The maximum number of channels is 8 for
rx and 8 for tx. In dual_emac mode the h/w channels are shared
between two interfaces and changing number on one interface changes
number of channels on another.
The ACPI IORT table provide entries for IOMMU (aka SMMU in ARM world)
components that allow creating the kernel data structures required to
probe and initialize the IOMMU devices.
This patch provides support in the IORT kernel code to register IOMMU
components and their respective fwnode.
Current ARM SMMUv3 probe functions intermingle HW and DT probing in the
initialization functions to detect and programme the ARM SMMU v3 driver
features. In order to allow probing the ARM SMMUv3 with other firmwares
than DT, this patch splits the ARM SMMUv3 init functions into DT and HW
specific
Device drivers (eg ARM SMMU) need to know if a specific component
is part of the IORT table, so that kernel data structures are not
initialized at initcalls time if the respective component is not
part of the IORT table.
To this end, this patch adds a trivial function that allows detecting
if a
The platform device kernel API does not provide functions to
retrieve a platform device through the corresponding struct
device fwnode pointer.
Implement the fwnode platform_device look-up in drivers core
code by using the bus_find_device() API and a corresponding
matching function. The OF
Bonding driver sets IFF_BONDING on both master (the bonding device) and
slave (the real NIC) devices and in netvsc_netdev_event() we want to skip
master devices only. Currently, there is an uncertainty when a slave
interface is removed: if bonding module comes first in netdev_chain it
clears
Here is a deadlock scenario:
- netvsc_vf_up() schedules netvsc_notify_peers() work and quits.
- netvsc_vf_down() runs before netvsc_notify_peers() gets executed. As it
is being executed from netdev notifier chain we hold rtnl lock when we
get here.
- we enter while
struct netvsc_device is not suitable for storing VF information as this
structure is being destroyed on MTU change / set channel operation (see
rndis_filter_device_remove()). Move all VF related stuff to struct
net_device_context which is persistent.
Signed-off-by: Vitaly Kuznetsov
We reset vf_inject on VF going down (netvsc_vf_down()) but we don't on
VF removal (netvsc_unregister_vf()) so vf_inject stays 'true' while
vf_netdev is already NULL and we're trying to inject packets into NULL
net device in netvsc_recv_callback() causing kernel to crash.
Signed-off-by: Vitaly
On 08/15/2016 11:06 AM, David Vrabel wrote:
> On 15/08/16 15:46, Boris Ostrovsky wrote:
>> From: Sebastian Andrzej Siewior
>>
>> Install the callbacks via the state machine.
> [...]
>> +static int xen_evtchn_cpu_dead(unsigned int cpu)
>> +{
>> +
Hi Vladimir,
On 2016-08-15 15:55, Vladimir Zapolskiy wrote:
> Hi Peter,
>
> On 08/15/2016 04:40 PM, Peter Rosin wrote:
>> Backwards compatibility is preserved; the subnodes are in practice
>> optional.
>>
>> However, the mux core needs to know what subnode it should examine, so add
>> a couple
From: Colin Ian King
The current check for associatedsta being set to -1 to indicate it has
not been found is not working because associatedsta is initialized to
zero and will never be -1. Fix this by initializing it to ~0 and checking
for ~0 instead.
Signed-off-by:
On Sun, Aug 14, 2016 at 01:13:54AM -0700, Andy Lutomirski wrote:
> On Fri, Aug 12, 2016 at 7:28 AM, Josh Poimboeuf wrote:
> > Convert show_trace_log_lvl() to use the new unwinder. dump_trace() has
> > been deprecated.
>
> >
> > Another change here is that callers of
On 2016/08/15 03:13PM, Wang Nan wrote:
>
>
> On 2016/8/13 9:55, Anton Blanchard wrote:
> > From: Anton Blanchard
> >
> > Commit 73cdf0c6ea9c ("perf symbols: Record text offset in dso
> > to calculate objdump address") started storing the offset of
> > the text section for all
On Sun, Jul 10, 2016 at 11:24 AM, Neil Armstrong
wrote:
> Add support for the PWM controller found in the Amlogic SoCs.
> This driver supports the Meson8b and GXBB SoCs.
>
> Signed-off-by: Neil Armstrong
> ---
> drivers/pwm/Kconfig | 9 +
>
> On 15 August 2016 at 17:05 Arnd Bergmann wrote:
>
>
> On Friday 12 August 2016, Fabian Frederick wrote:
> > We can directly depend on SOC_IMX31 since
> > commit c9ee94965dce
> > ("ARM: imx: deconstruct mxc_rnga initialization")
> >
> > Signed-off-by: Fabian Frederick
Change my email address to kernel.org account instead of Samsung one.
Also switch Maxim MUIC charger drivers from supported to maintained
mode.
Signed-off-by: Krzysztof Kozlowski
Cc: Kukjin Kim
Cc: linux-samsung-...@vger.kernel.org
---
Affected
Provide a translation table between Ethernet and FC port speeds so odd
speeds (from a Ethernet POV) like 8 Gbit are correctly mapped to sysfs
and open-fcoe's fcoeadm.
Before:
Description: BCM57840 NetXtreme II 10/20-Gigabit Ethernet
Revision: 11
Manufacturer: Broadcom
IORT tables provide data that allow the kernel to carry out
device ID mappings between endpoints and system components
(eg interrupt controllers, IOMMUs). When the mapping for a
given device ID is carried out, the translation mechanism
is done on a per-subsystem basis rather than a component
On 01/08/16 10:54, Enric Balletbo i Serra wrote:
> Hi,
>
> This is the four patchset to add support for the sensors behind the ChromeOS
> Embedded Controller.
>
> This version has only the patches to support common functions and 3d
> contiguous sensors like Accelerometers, Gyroscope and
On Mon, Aug 15, 2016 at 05:10:06PM +0200, Peter Zijlstra wrote:
> On Mon, Aug 15, 2016 at 04:01:34PM +0100, Morten Rasmussen wrote:
> > On Mon, Aug 15, 2016 at 03:39:49PM +0200, Peter Zijlstra wrote:
> > > > +static int wake_cap(struct task_struct *p, int cpu, int prev_cpu)
> > > > +{
> > > > +
On Mon 15-08-16 11:16:04, Johannes Weiner wrote:
> On Mon, Aug 15, 2016 at 05:06:44PM +0200, Michal Hocko wrote:
> > @@ -4173,11 +4213,17 @@ static struct mem_cgroup *mem_cgroup_alloc(void)
> >
> > memcg->stat = alloc_percpu(struct mem_cgroup_stat_cpu);
> > if (!memcg->stat)
> > -
Rendering operations to the dma-buf are tracked implicitly via the
reservation_object (dmabuf->resv). This is used to allow poll() to
wait upon outstanding rendering (or just query the current status of
rendering). The dma-buf sync ioctl allows userspace to prepare the
dma-buf for CPU access,
We're not guaranteed to see NETDEV_REGISTER/NETDEV_UNREGISTER notifications
only once per VF but we increase/decrease module refcount unconditionally.
Check vf_netdev to make sure we don't take/release it twice. We presume
that only one VF per netvsc device may exist.
Signed-off-by: Vitaly
On Mon, Aug 15, 2016 at 04:42:18PM +0100, Chris Wilson wrote:
> Rendering operations to the dma-buf are tracked implicitly via the
> reservation_object (dmabuf->resv). This is used to allow poll() to
> wait upon outstanding rendering (or just query the current status of
> rendering). The dma-buf
On 27/07/16 09:12, Gregor Boirie wrote:
>
> On 07/27/2016 05:17 AM, Alison Schofield wrote:
>> Uninitialized channel pointer causes segmentation fault when we
>> call free(channel) during cleanup() with no channels initialized.
>> This happens when you exit early for usage errors. Initialize
>>
* Roger Quadros [160803 02:56]:
> On 03/08/16 11:01, Johan Hovold wrote:
> > On Wed, Aug 03, 2016 at 10:46:24AM +0300, Roger Quadros wrote:
> >> On 02/08/16 13:35, Tony Lindgren wrote:
> >>> * Johan Hovold [160724 05:11]:
> Networking is currently broken for
On 08/08/16 14:52, Alexandre Belloni wrote:
> On 08/08/2016 at 14:42:16 +0200, Anders Darander wrote :
>> The driver always assumes that an input device has been created when
>> reading channel 3. This causes a kernel panic when dereferencing
>> st->ts_input.
>>
>> The change was introduced in
>>
The nohz_stamp member of struct rq has been unused since 2010,
when this commit removed the code that referenced it:
396e894d289d ("sched: Revert nohz_ratelimit() for now")
Signed-off-by: Rik van Riel
---
kernel/sched/sched.h | 1 -
1 file changed, 1 deletion(-)
diff --git
On Sun, 14 Aug 2016, Michal Hocko wrote:
> On Sat 13-08-16 13:34:29, Mikulas Patocka wrote:
> >
> >
> > On Fri, 12 Aug 2016, Michal Hocko wrote:
> >
> > > On Thu 04-08-16 14:49:41, Mikulas Patocka wrote:
> > >
> > > > On Wed, 3 Aug 2016, Michal Hocko wrote:
> > > >
> > > > > But the device
From: Markus Elfring
Date: Mon, 15 Aug 2016 18:06:46 +0200
The field "owner" is set by the core.
Thus delete an unneeded initialisation.
Generated by: scripts/coccinelle/api/platform_no_drv_owner.cocci
Signed-off-by: Markus Elfring
On Mon, Aug 15, 2016 at 1:50 AM, Dongpo Li wrote:
> Hi Rob,
> Many thanks for your review.
>
> On 2016/8/13 2:43, Rob Herring wrote:
>> On Thu, Aug 11, 2016 at 05:01:52PM +0800, Dongpo Li wrote:
>>> From: Li Dongpo
>>>
>>> The "hix5hd2" is SoC
On Sun, Aug 14, 2016 at 01:23:11AM -0700, Andy Lutomirski wrote:
> On Fri, Aug 12, 2016 at 7:29 AM, Josh Poimboeuf wrote:
> > The entry code doesn't encode pt_regs for syscalls. But they're always
> > at the same location, so we can add a manual check for them.
>
> At first
On 04/08/16 14:07, Daniel Wagner wrote:
> From: Daniel Wagner
>
> There is only one waiter for the completion, therefore there
> is no need to use complete_all(). Let's make that clear by
> using complete() instead of complete_all().
>
> The usage pattern of the
On 04/08/16 14:07, Daniel Wagner wrote:
> From: Daniel Wagner
>
> There is only one waiter for the completion, therefore there
> is no need to use complete_all(). Let's make that clear by
> using complete() instead of complete_all().
>
> The usage pattern of the
From: Markus Elfring
Date: Mon, 15 Aug 2016 19:09:41 +0200
The field "owner" is set by the core.
Thus delete an unneeded initialisation.
Generated by: scripts/coccinelle/api/platform_no_drv_owner.cocci
Signed-off-by: Markus Elfring
On Mon, Aug 15, 2016 at 10:05:58AM -0500, Josh Poimboeuf wrote:
> On Sun, Aug 14, 2016 at 12:26:29AM -0700, Andy Lutomirski wrote:
> > On Fri, Aug 12, 2016 at 7:28 AM, Josh Poimboeuf wrote:
> > > On x86_32, when an interrupt happens from kernel space, SS and SP aren't
> > >
Hi, Chinner,
Dave Chinner writes:
> On Wed, Aug 10, 2016 at 06:00:24PM -0700, Linus Torvalds wrote:
>> On Wed, Aug 10, 2016 at 5:33 PM, Huang, Ying wrote:
>> >
>> > Here it is,
>>
>> Thanks.
>>
>> Appended is a munged "after" list, with the "before"
This series is intended to allow cpsw driver to use cpdma ability of
h/w shaper to send/receive data with up to 8 tx and 8 rx queues. This
series doesn't contain interface to configure h/w shaper itself, it
contains only multi-queue support part and ability to configure number
of tx/rx queues with
Keep the driver internals in C file. Currently it's not required for
drivers to know rx or tx a channel is, except create function.
So correct "channel create" function, and use all channel struct
macroses only for internal use.
Signed-off-by: Ivan Khoronzhuk
---
Signed-off-by: Eric Engestrom
---
drivers/gpu/drm/amd/amdgpu/dce_v10_0.c | 2 +-
drivers/gpu/drm/amd/amdgpu/dce_v11_0.c | 2 +-
drivers/gpu/drm/amd/amdgpu/dce_v8_0.c | 2 +-
drivers/gpu/drm/drm_atomic.c| 2 +-
On Sun, Aug 14, 2016 at 12:40:03AM -0700, Andy Lutomirski wrote:
> On Fri, Aug 12, 2016 at 7:28 AM, Josh Poimboeuf wrote:
> > The 'error_code' label is awkwardly named, especially when it shows up
> > in a stack trace. Move it to its own local function and rename it to
> >
On 01/08/16 10:54, Enric Balletbo i Serra wrote:
> Check whether the ChromeOS Embedded Controller is a sensor hub and in
> such case issue a command to get the number of sensors and register them
> all.
>
> Signed-off-by: Gwendal Grignou
> Signed-off-by: Enric Balletbo i
On Tue, May 24, 2016 at 03:35:44PM -0700, David Daney wrote:
> diff --git a/arch/arm64/include/asm/acpi.h b/arch/arm64/include/asm/acpi.h
> index aee323b..4b13ecd 100644
> --- a/arch/arm64/include/asm/acpi.h
> +++ b/arch/arm64/include/asm/acpi.h
> @@ -113,4 +113,12 @@ static inline const char
On 26/07/16 10:33, Quentin Schulz wrote:
> On 26/07/2016 11:05, Alexander Stein wrote:
>> On Tuesday 26 July 2016 10:24:48, Quentin Schulz wrote:
>>> On 26/07/2016 10:21, Alexander Stein wrote:
On Tuesday 26 July 2016 09:43:44, Quentin Schulz wrote:
> iio_channel_get_all returns -ENODEV
On Mon, Aug 15, 2016 at 09:32:43AM -0600, Jonathan Corbet wrote:
> On Mon, 15 Aug 2016 10:49:36 -0400
> David Long wrote:
>
> > On 08/15/2016 10:25 AM, Jonathan Corbet wrote:
> > > On Fri, 12 Aug 2016 16:24:44 -0400
> > > David Long wrote:
> > >
> >
On 08/08/16 12:05, Vignesh R wrote:
> Now that open delay and sample delay for each channel is configurable
> via DT, the default IDLE_TIMEOUT value is not enough as this is
> calculated based on hardcoded macros. This results in driver returning
> EBUSY sometimes. Fix this by increasing the
I made a hash of LKML email in the previous mail. Re-sending with the
address corrected.
Apologies for the duplicate.
Punit Agrawal writes:
> Hi,
>
> While trying out v4.8-rc2 on Juno r2 (arm64), I ran into the following
> crash when probing the nvidia graphics card
On 09/08/16 01:19, Brian Norris wrote:
> When using CONFIG_DEBUG_ATOMIC_SLEEP, the scheduler nicely points out
> that we're calling sleeping primitives within the wait_event loop, which
> means we might clobber the task state:
>
> [ 10.831289] do not call blocking ops when !TASK_RUNNING;
On Sun, Aug 14, 2016 at 12:56:40AM -0700, Andy Lutomirski wrote:
> On Fri, Aug 12, 2016 at 7:29 AM, Josh Poimboeuf wrote:
> > Add a sanity check to ensure the stack only grows down, and print a
> > warning if the check fails.
> >
> > Signed-off-by: Josh Poimboeuf
On 2016-08-15 09:42 AM, Michal Hocko wrote:
On Mon 15-08-16 09:00:04, Robert Foss wrote:
On 2016-08-14 05:04 AM, Michal Hocko wrote:
On Fri 12-08-16 18:04:19, robert.f...@collabora.com wrote:
From: Robert Foss
This series implements /proc/PID/totmaps, a tool
On Sun, Aug 14, 2016 at 01:10:42AM -0700, Andy Lutomirski wrote:
> On Fri, Aug 12, 2016 at 7:29 AM, Josh Poimboeuf wrote:
> > With frame pointers, when a task is interrupted, its stack is no longer
> > completely reliable because the function could have been interrupted
> >
On Mon, Aug 15, 2016 at 9:07 AM, Adrian Hunter wrote:
> Commit 288dab8a35a0 ("block: add a separate operation type for secure
> erase") split REQ_OP_SECURE_ERASE from REQ_OP_DISCARD without considering
> all the places REQ_OP_DISCARD was being used to mean either. Fix
* Javier Martinez Canillas [160801 09:47]:
> Hello Tony,
>
> This is yet another series with fixes for DTC warnings caused by mismatches
> between device nodes' unit names and reg properties.
>
> The patches should not cause a functional change but were only build
On Mon, Jun 27, 2016 at 2:32 PM, Rafael J. Wysocki wrote:
>
> On Monday, June 27, 2016 11:27:42 AM Hoan Tran wrote:
> > Hi Jassi and Rafael,
> >
> > On Wed, Jun 15, 2016 at 9:19 AM, Prakash, Prashanth
> > wrote:
> > >
> > >
> > > On 6/9/2016 4:43 PM,
On 8/11/2016 11:25 AM, Petr Mladek wrote:
On Mon 2016-08-08 12:03:38, Chris Metcalf wrote:
When doing an nmi backtrace of many cores, most of which are idle,
the output is a little overwhelming and very uninformative. Suppress
messages for cpus that are idling when they are interrupted and
Re:Good day David,
I am confirming if you received my previous email regarding you having the
same Surname with my late client, leaving in your name in his last
will of testament the sum of ( 8 . 5 M ) Please email me for
more information.
Mr.Ebunie Johnson.
On Mon, 2016-08-15 at 17:12 +0200, Johannes Thumshirn wrote:
> +static inline u64 sas_get_address(struct scsi_device *sdev)
> +{
> + return 0;
> +}
To be honest, we don't want this. We do want the code to fail to
compile if you ever use sas_get_address where you shouldn't because the
code
On 04/08/16 09:35, Florian Lobmaier wrote:
> Hello Peter,
>
> Thanks again for your valuable feedback. We use now IIO_EV_THRESH to
> set high and low limits for temperature. Also removed all the custom
> ABI as this are mainly settings which will be set one-time only. For
> the removed custom ABI
On Thu, 11 Aug, at 06:41:50PM, Borislav Petkov wrote:
> Drop stable from CC.
>
> On Thu, Aug 11, 2016 at 04:21:42PM +0100, Matt Fleming wrote:
> > While the Intel PMU monitors the LLC when perf enables the
> > HW_CACHE_REFERENCES and HW_CACHE_MISSES events, these events monitor
> > L1 instruction
On Mon, 15 Aug 2016 10:47:39 +0300
Roger Quadros wrote:
> dma_request_chan() can fail returning an error pointer. In this case
> prevent calling dma_release_channel() to prevent a ERR_PTR() dereference.
>
> As error path can be called even with no DMA configuration, info->dma can
On Mon, Aug 15, 2016 at 05:06:44PM +0200, Michal Hocko wrote:
> From: Johannes Weiner
>
> commit 73f576c04b9410ed19660f74f97521bee6e1c546 upstream.
>
> The memory controller has quite a bit of state that usually outlives the
> cgroup and pins its CSS until said state
Hi Zubair,
On Mon, Aug 15, 2016 at 02:55:27PM +0100, Zubair Lutfullah Kakakhel wrote:
> The Xilinx AXI Interrupt Controller IP block is used by the MIPS
> based xilfpga platform.
>
> Move the interrupt controller code out of arch/microblaze so that
> it can be used by everyone
>
>
On 01/08/16 10:54, Enric Balletbo i Serra wrote:
> Add the core functions to be able to support the sensors attached behind
> the ChromeOS Embedded Controller and used by other IIO cros-ec sensor
> drivers.
>
> The cros_ec_sensor_core driver matches with current driver in ChromeOS
> 4.4 tree, so
On 01/08/16 10:54, Enric Balletbo i Serra wrote:
> Handle 3d contiguous sensors like Accelerometers, Gyroscope and
> Magnetometer that are presented by the ChromeOS EC Sensor hub.
>
> Signed-off-by: Guenter Roeck
> Signed-off-by: Enric Balletbo i Serra
On 26/07/16 17:04, Guenter Roeck wrote:
> On Tue, Jul 26, 2016 at 12:00:33PM +0200, Alexander Stein wrote:
>> On Tuesday 26 July 2016 11:33:59, Quentin Schulz wrote:
>>> On 26/07/2016 11:05, Alexander Stein wrote:
On Tuesday 26 July 2016 10:24:48, Quentin Schulz wrote:
> On 26/07/2016
On 08/15/2016 11:32 AM, Jonathan Corbet wrote:
On Mon, 15 Aug 2016 10:49:36 -0400
David Long wrote:
On 08/15/2016 10:25 AM, Jonathan Corbet wrote:
On Fri, 12 Aug 2016 16:24:44 -0400
David Long wrote:
Some architectures (i.e.: sparc64 and arm64)
On Mon, Aug 15, 2016 at 05:06:43PM +0200, Michal Hocko wrote:
> This is the second version which addresses review feedback from Johannes [1]
With the final 1/3, this looks good to me. Thanks for doing the
backport, Michal.
Kernel crash is reported after VF is removed and detached from netvsc
device. Turns out we have multiple different (but related) issues on the
VF removal path which I'm trying to address with PATCHes 2-5 of this
series. PATCH1 is required to support the change.
Changes since v1:
- Re-arrange
Em Mon, Aug 15, 2016 at 06:25:15PM +0800, Hekuang escreveu:
> ping.
Thanks, tested and applied both patches.
- Arnaldo
> 在 2016/8/4 19:25, He Kuang 写道:
> > Because perf data from pipe do not have a header with evsel attr, we
> > should not check that and disable symbol_conf.use_callchain.
Em Wed, Aug 10, 2016 at 04:49:08PM +0800, Rui Teng escreveu:
> It is a requirement from the perf todo list:
> The feature tests should be performed only when a file that needs those tests,
> or at least only when some .c or .h file will be rebuilt
> An initial step would be for 'make
On Fri, Jul 29, 2016 at 08:22:44AM -0700, Nadim almas wrote:
> From: Nadim Almas
>
> Fixed a coding style issue.
What coding style issue?
And where are the 31 other patches in this series?
thanks,
greg k-h
On Mon, Aug 15, 2016 at 12:59:13PM +0200, Mickaël Salaün wrote:
>
> On 15/08/2016 05:09, Sargun Dhillon wrote:
> > On Mon, Aug 15, 2016 at 12:57:44AM +0200, Mickaël Salaün wrote:
> >> Our approaches have some common points (i.e. use eBPF in an LSM, stacked
> >> filters like seccomp) but I'm
The iommu fwspec configuration mechanism currently relies on
the arch specific struct dev_archdata.iommu member to stash
the struct iommu_fwspec pointer set-up for streamid translation.
The struct dev_archdata.iommu member is arch specific and is not present
on all arches that make use of the
Since commit e647b532275b ("ACPI: Add early device probing
infrastructure") the kernel has gained the infrastructure that allows
adding linker script section entries to execute ACPI driver callbacks
(ie probe routines) for all subsystems that register a table entry
in the respective kernel section
On DT based systems, the of_dma_configure() API implements DMA
configuration for a given device. On ACPI systems an API equivalent to
of_dma_configure() is missing which implies that it is currently not
possible to set-up DMA operations for devices through the ACPI generic
kernel layer.
This
The iommu_fwspec structure, used to hold per device iommu configuration
data is not OF specific and therefore can be moved to a generic
and OF independent compilation unit.
In particular, the iommu_fwspec handling hinges on the device_node
pointer to identify the IOMMU device associated with the
This patch series is v4 of a previous posting:
https://lkml.org/lkml/2016/7/20/248
v3 -> v4
- Added single mapping API (for IORT named components)
- Fixed arm_smmu_iort_xlate() return value
- Reworked fwnode registration and platform device creation
ordering to
On systems booting with a device tree, every struct device is
associated with a struct device_node, that represents its DT
representation. The device node can be used in generic kernel
contexts (eg IRQ translation, IOMMU streamid mapping), to
retrieve the properties associated with the device and
On Sun, Aug 14, 2016 at 12:48:15AM -0700, Andy Lutomirski wrote:
> On Fri, Aug 12, 2016 at 7:28 AM, Josh Poimboeuf wrote:
> > in_exception_stack() does some bad, bad things just so the unwinder can
> > print different values for different areas of the debug exception stack.
>
401 - 500 of 1842 matches
Mail list logo