DesignWare MMC Controller's transfer mode should be decided
at runtime instead of compile-time. So we remove this config
option and read dw_mmc's register to select DMA master.
Signed-off-by: Shawn Lin
---
Changes in v7: None
Changes in v6: None
Changes in v5: None
Changes in v4: None
Changes
DesignWare MMC Controller's transfer mode should be decided
at runtime instead of compile-time. So we remove this config
option and read dw_mmc's register to select DMA master.
Signed-off-by: Shawn Lin
Acked-by: Wei Xu
---
Changes in v7: None
Changes in v6: None
Changes in v5: None
Changes in
synopsys-dw-mshc supports three types of transfer mode. We add
bindings and description for how to use them at runtime.
Signed-off-by: Shawn Lin
---
Changes in v7: None
Changes in v6: None
Changes in v5: None
Changes in v4: None
Changes in v3: None
Changes in v2: None
DesignWare MMC Controller's transfer mode should be decided
at runtime instead of compile-time. So we remove this config
option and read dw_mmc's register to select DMA master.
Signed-off-by: Shawn Lin
Acked-by: Vineet Gupta
---
Changes in v7: None
Changes in v6: None
Changes in v5: None
DesignWare MMC Controller's transfer mode should be decided
at runtime instead of compile-time. So we remove this config
option and read dw_mmc's register to select DMA master.
Signed-off-by: Shawn Lin
Acked-by: Govindraj Raja
Acked-by: Ralf Baechle
---
Changes in v7: None
Changes in v6: None
DesignWare MMC Controller's transfer mode should be decided
at runtime instead of compile-time. So we remove this config
option and read dw_mmc's register to select DMA master.
Signed-off-by: Shawn Lin
Acked-by: Krzysztof Kozlowski
---
Changes in v7: None
Changes in v6: None
Changes in v5:
This patch add some macros for HCON register operations
to make code more readable.
Signed-off-by: Shawn Lin
---
Changes in v7: None
Changes in v6: None
Changes in v5: None
Changes in v4: None
Changes in v3: None
Changes in v2: None
drivers/mmc/host/dw_mmc.c | 6 +++---
Synopsys DesignWare mobile storage host controller supports three
types of transfer mode: pio, internal dma and external dma. However,
dw_mmc can only supports pio and internal dma now. Thus some platforms
using dw-mshc integrated with generic dma can't work in dma mode. So we
submit this patch
DesignWare MMC Controller can supports two types of DMA
mode: external dma and internal dma. We get a RK312x platform
integrated dw_mmc and ARM pl330 dma controller. This patch add
edmac ops to support these platforms. I've tested it on RK31xx
platform with edmac mode and RK3288 platform with
Hi Sanchayan,
On Fri, Aug 21, 2015 at 06:56:32PM +0530, Sanchayan Maity wrote:
> The Colibri Vybrid VF50 module supports 4-wire touchscreens using
> FETs and ADC inputs. This driver uses the IIO consumer interface
> and relies on the vf610_adc driver based on the IIO framework.
>
Thank you for
poma writes:
>> Ref.
>> https://bugzilla.redhat.com/show_bug.cgi?id=1252167
>> https://bugzilla.kernel.org/show_bug.cgi?id=102631
>>
>
> You guys are really something.
Hi Poma,
I understand your frustration!
I got involved via the other thread which didn't mention your bug report
On Sat, Aug 22, 2015 at 12:46:09PM +0800, Eryu Guan wrote:
> On Sat, Aug 22, 2015 at 10:30:25AM +1000, Dave Chinner wrote:
> > On Fri, Aug 21, 2015 at 06:20:53PM +0800, Eryu Guan wrote:
> [snip]
> >
> > Eryu, can you try again, this time manually specifying the writeback
> > tracepoints so you
Hi Chris,
Today's linux-next merge of the xtensa tree got a conflict in:
arch/xtensa/include/asm/atomic.h
between commit:
2a3ed90f428c ("xtensa: Provide atomic_{or,xor,and}")
from the arm64 and tip trees and commit:
38fef73c21d1 ("xtensa: implement fake NMI")
from the xtensa tree.
I
First, an actual, albeit minor, bug: initializing both vmap_info_gen
and vmap_info_cache_gen to 0 marks the cache as valid, which it's not.
vmap_info_gen should be initialized to 1 to force an initial
cache update.
Second, I don't see why you need a 64-bit counter. Seqlocks consider
32 bits (31
This change is a more advanced use of detached freelist. The bulk
free array is scanned is a progressive manor with a limited look-ahead
facility.
To maintain the same performance level, as the previous simple
implementation, the look-ahead have been limited to only 3 objects.
This number have
This change focus on improving the speed of object freeing in the
"slowpath" of kmem_cache_free_bulk.
The slowpath call __slab_free() have been extended with support for
bulk free, which amortize the overhead of the locked cmpxchg_double_slab.
To use the new bulking feature of __slab_free(), we
REPOST:
* Only updated comment in patch01 per request of Christoph Lameter.
* No other objections have been made
* Prev post: http://thread.gmane.org/gmane.linux.kernel.mm/135704
NEW use-cases for this API is RCU-free (and still for network NICs).
Introducing what I call detached freelist,
Make it possible to free a freelist with several objects by extending
__slab_free() with two arguments: a freelist_head pointer and objects
counter (cnt). If freelist_head pointer is set, then the object must
be the freelist tail pointer.
This allows a freelist with several objects (all within
2015-08-24 8:23 GMT+09:00 Rob Herring :
> On Wed, Aug 19, 2015 at 9:50 AM, Yakir Yang wrote:
>> Analogix dp driver is split from exynos dp driver, so we just
>> make an copy of exynos_dp.txt, and then simplify exynos_dp.txt
>>
>> Beside update some exynos dtsi file with the latest change
>>
On Wed, 19 Aug 2015 12:21:45 +0300
"Kirill A. Shutemov" wrote:
> Hugh has pointed that compound_head() call can be unsafe in some
> context. There's one example:
>
[...]
> diff --git a/include/linux/mm.h b/include/linux/mm.h
> index 0735bc0a351a..a4c4b7d07473 100644
> --- a/include/linux/mm.h
On 21.08.2015 18:43, Joonyoung Shim wrote:
> According to datasheet, the S2MPS13X and S2MPS14X should update write
> buffer via setting WUDR bit to high after ctrl register is written.
>
> If not, ALARM interrupt of rtc-s5m doesn't happen first time when i use
>
Hi all,
Today's linux-next merge of the arm-soc tree got a conflict in:
drivers/cpufreq/exynos-cpufreq.c
between commit:
62c3f2fddd43 ("cpufreq: exynos: Fix for memory leak in case SoC name does not
match")
from Linus' tree and commits:
ac4c90c82e4d ("cpufreq: exynos: remove
On Sun, Aug 23, 2015 at 4:42 PM, Rob Herring wrote:
> On Sun, Aug 23, 2015 at 6:13 PM, Olof Johansson wrote:
>> On Fri, Aug 14, 2015 at 2:21 PM, Rob Herring wrote:
>>> +arm-soc
>>>
>>> On Tue, Aug 11, 2015 at 5:07 AM, Ian Campbell
>>> wrote:
On Mon, 2015-08-03 at 17:06 +0100, Ian
On Sun, Aug 23, 2015 at 6:13 PM, Olof Johansson wrote:
> On Fri, Aug 14, 2015 at 2:21 PM, Rob Herring wrote:
>> +arm-soc
>>
>> On Tue, Aug 11, 2015 at 5:07 AM, Ian Campbell
>> wrote:
>>> On Mon, 2015-08-03 at 17:06 +0100, Ian Campbell wrote:
Commit 9ccd608070b6 ("arm64: dts: add device
On Wed, Aug 19, 2015 at 9:50 AM, Yakir Yang wrote:
> Analogix dp driver is split from exynos dp driver, so we just
> make an copy of exynos_dp.txt, and then simplify exynos_dp.txt
>
> Beside update some exynos dtsi file with the latest change
> according to the devicetree binding documents.
You
Hi Trond,
On Tue, 18 Aug 2015 10:56:34 +1000 Stephen Rothwell
wrote:
>
> After merging the nfs tree, today's linux-next build (x86_64 allmodconfig)
> failed like this:
>
> drivers/staging/lustre/lnet/klnds/o2iblnd/o2iblnd.c: In function
> 'kiblnd_pmr_pool_map':
>
On 08/17/2015 08:59 PM, 河合英宏 / KAWAI，HIDEHIRO wrote:
> Hello Corey,
>
>> -Original Message-
>> From: Corey Minyard [mailto:tcminy...@gmail.com] On Behalf Of Corey Minyard
>> Sent: Wednesday, August 12, 2015 1:13 PM
>> To: 河合英宏 / KAWAI，HIDEHIRO
>> Cc:
On 08/17/2015 09:54 PM, 河合英宏 / KAWAI，HIDEHIRO wrote:
>> From: Corey Minyard [mailto:tcminy...@gmail.com] On Behalf Of Corey Minyard
>>
>> This patch will break ATN handling on the interfaces. So we can't do this.
> I understand. So how about doing like this:
>
> /* All states wait for ibf,
On Fri, Aug 14, 2015 at 2:21 PM, Rob Herring wrote:
> +arm-soc
>
> On Tue, Aug 11, 2015 at 5:07 AM, Ian Campbell wrote:
>> On Mon, 2015-08-03 at 17:06 +0100, Ian Campbell wrote:
>>> Commit 9ccd608070b6 ("arm64: dts: add device tree for ARM SMM-A53x2 on
>>> LogicTile Express 20MG") added a new
From: Noam Camus
Date: Thu, 20 Aug 2015 08:00:00 +0300
> Change v2
> TX done is handled back with NAPI poll.
>
> Change v1
> This patch set is a bunch of fixes to make nps_enet work correctly with
> all platforms, i.e. real device, emulation system, and simulation system.
> The main trigger for
From: Vivien Didelot
Date: Wed, 19 Aug 2015 18:54:55 -0400
> The current Secure port mode requires the port-based VLANs to also be
> valid in the 802.1Q VLAN Table Unit. The current hardware bridging
> support only configures the port-based VLANs, thus is broken.
>
> A new patchset is required
Hi Cassidy,
On Wed, Jul 29, 2015 at 11:40 PM, Cassidy Burden wrote:
> I changed the test module to now set the entire array to all 0/1s and
> only flip a few bits. There appears to be a performance benefit, but
> it's only 2-3% better (if that). If the main benefit of the original
> patch was
cgroup currently does not support removing a cgroup directory if it has
children.
Adds a api cgroup_destroy_children which destroys all the children in
the cgroup hierarchy starting from the bottom. After each cgroup node is
destroyed we wait till the css is offlined and freed.
Signed-off-by:
Add subsystem APIs css_mount and css_umount which will be called during
cgroup_mount and umount respectively. This will let the subsystem
perform any specific setup during mount/umount.
This will be used in code data prioritization code later.
Signed-off-by: Vikas Shivappa
---
Add support to manage CLOSid(class of service id) for code data
prioritization(CDP). Includes allocating, freeing closid and closid_get
and closid_put.
During mount if the mode is changed between cdp and cache allocation
only, all the CLOSids are freed. When a new cgroup is created it
inherits its
This patchset has some preparatory patches to cgroup to add a wrapper to
to cgroup_rmdir to destroy the cgroup directories recursively, new mount
and umount interfaces for ss. It then has patches to support Intel code
data prioritization which is an extension of cache allocation and lets
allocate
This patch adds enumeration support for code data prioritization(CDP)
feature found in future Intel Xeon processors.
CDP is an extension to Cache Allocation and lets threads allocate subset
of L3 cache for code and data separately. The allocation is represented
by the code or data cache mask
Add support to read and write the per cgroup data and instruction cache
masks.
- When a new cgroup directory is created it inherits the parents dcache
and icache mask. So a mkdir never fails.
- When user changes the mask, we look to see if we can reuse an
existing CLOSid or else allocate a new
At any time the intel_rdt cgroup operates in 2 modes (legacy cache
allocation mode/default or code data prioritization mode).
When CDP is enabled the number of available CLOSids is halved and its
doubled when CDP is disabled. When CDP is enabled each CLOSid
maps to a data cache mask and
Hi Alim,
On Fri, Aug 21, 2015 at 12:27 PM, Alim Akhtar wrote:
> From: Seungwon Jeon
>
> This patch introduces Exynos UFS PHY driver. This driver
> supports to deal with phy calibration and power control
> according to UFS host driver's behavior.
>
> Signed-off-by: Seungwon Jeon
>
On Tue, Aug 18, 2015 at 11:20 PM, Chen-Yu Tsai wrote:
> Reduced Serial Bus is a proprietary 2-line push-pull serial bus
> supporting multiple slave devices.
>
> It was developed by Allwinner, Inc. and used by Allwinner and X-Powers,
> Inc. for their line of PMICs and other peripheral ICs.
>
>
is_extcon_changed should only check the idx-th bit of new, not
the entirety of new when setting attached.
This fixes extcon sending notifications that a cable was inserted when
it gets removed while another cable is still connected.
Cc: sta...@vger.kernel.org
Signed-off-by: Hans de Goede
---
On Thu, Aug 20, 2015 at 2:38 PM, Vladimir Barinov
wrote:
> Add Holt Integrated Circuits, Inc. to the list of device tree vendor
> prefixes
>
> Signed-off-by: Vladimir Barinov
Acked-by: Rob Herring
> ---
> Changes in version 2:
> - none
> Changes in version 3:
> - none
> Changes in version 4:
On Sat, Aug 22, 2015 at 12:48 PM, Jonathan Cameron wrote:
> On 20/08/15 23:48, Javier Martinez Canillas wrote:
>> Hello Michael,
>>
>> On 08/21/2015 12:29 AM, Michael Welling wrote:
>>> On Fri, Aug 21, 2015 at 12:02:40AM +0200, Javier Martinez Canillas wrote:
Hello Michael,
On
On Fri, Aug 21, 2015 at 08:25:24PM +, Liang, Kan wrote:
SNIP
> >
> > we need global topology information in perf.data and use the mapping
> > from there, we can't use current server info
> >
> > we currently store core_siblings_list and thread_siblings_list, in topology
> > FEATURE, which
thanks!
Please, remember that we need to push it also to stable :)
On Sun, Aug 23, 2015 at 11:52 PM, Rob Herring wrote:
> On Thu, Jul 16, 2015 at 3:33 PM, Ricardo Ribalda Delgado
> wrote:
>> ping?
>>
>> Hello Grant, Hello Greg
>>
>> Is there any planned timeframe for applying this patch into
I was curious why these fields were ever added to /proc/meminfo, and dug
up this:
commit d262ee3ee6ba4f5f6125571d93d9d63191d2ef76
Author: Andrew Morton
Date: Sat Apr 12 12:59:04 2003 -0700
[PATCH] vmalloc stats in /proc/meminfo
From: Matt Porter
There was a thread a
On Thu, Jul 16, 2015 at 3:33 PM, Ricardo Ribalda Delgado
wrote:
> ping?
>
> Hello Grant, Hello Greg
>
> Is there any planned timeframe for applying this patch into someones tree?
Greg is out ATM. I'll pick this up for 4.3.
Rob
>
>
> Thanks!
>
> On Tue, Jun 23, 2015 at 7:12 PM, Ricardo Ribalda
On Aug 21, 2015 3:10 PM, "Yaniv Gardi" wrote:
>
> Add a write memory barrier to make sure descriptors prepared are actually
> written to memory before ringing the doorbell. We have also added the
> write memory barrier after ringing the doorbell register so that
> controller sees the new request
On Aug 21, 2015 3:10 PM, "Yaniv Gardi" wrote:
>
> Sometimes queries from the device might return a failure so it is
> recommended to retry sending the query, before giving up.
> This change adds a wrapper to retry sending a query attribute,
> in cases where we need to wait longer, before we
Now that IP1000A chips are supported by dl2k driver, the buggy ipg driver
can be removed.
---
drivers/net/ethernet/Kconfig |1 -
drivers/net/ethernet/Makefile|1 -
drivers/net/ethernet/icplus/Kconfig | 13 -
drivers/net/ethernet/icplus/Makefile |5 -
Add support for IP1000A chips to dl2k driver.
IP1000A chip looks like a TC9020 with integrated PHY.
Tested with Asus NX1101.
---
drivers/net/ethernet/dlink/Kconfig |5 ++--
drivers/net/ethernet/dlink/dl2k.c | 51 +---
drivers/net/ethernet/dlink/dl2k.h |
O
n Aug 20, 2015 6:59 AM, "Yaniv Gardi" wrote:
>
> This change turns the UFS variant (SCSI_UFS_QCOM) into a UFS
> a platform device.
> In order to do so a few additional changes are required:
> 1. The ufshcd-pltfrm is no longer serves as a platform device.
>Now it only serves as a group of
On Sun, Aug 23 2015, Ingo Molnar wrote:
> Ok, fair enough - so how about the attached approach instead, which
> uses a 64-bit generation counter to track changes to the vmalloc
> state.
How does this invalidation approach compare to the jiffies approach? In
other words, how often does the
Frank has agreed to step up and help with DT core code maintainership.
At the same time, Grant is taking a step back from active maintainership
responsibilities. Add Frank to the device tree core code entry and
shuffle Grant to the end of the list. In a few releases time Grant will
be removed
On Sun, 21 Jun 2015 21:44:30 +0200
, Stefan Agner
wrote:
> On 2015-06-21 01:49, Peter Stuge wrote:
> > Stefan Agner wrote:
> >> libftdi requires to detach the kernel driver to get access to the device
> >
> > Control transfers ought to be possible without a detach.
>
> Good to know, thanks for
On 08/23/2015 04:45 AM, tip-bot for Andy Lutomirski wrote:
> Commit-ID: 47edb65178cb7056c2eea0b6c41a7d8c84547192
> Gitweb: http://git.kernel.org/tip/47edb65178cb7056c2eea0b6c41a7d8c84547192
> Author: Andy Lutomirski
> AuthorDate: Thu, 23 Jul 2015 12:14:40 -0700
> Committer: Ingo Molnar
After the conversion of pxa architecture to common clock framework, the
NAND clock can be disabled on startup if no nand driver claims it.
In this case, it happens that if the bootloader used the NAND and set
the DFI arbitration bit, the next access to a static memory controller
area, such as an
Robert Jarzmik writes:
> Ezequiel Garcia writes:
>
>> On 11 Aug 09:57 PM, Robert Jarzmik wrote:
>>> Add verbose debug for register accesses. This enables easier debugging
>>> by following where and how hardware is stimulated, and how it answers.
>>>
>>
>> I really don't see why we want this
After the conversion of pxa architecture to common clock framework, the
NAND clock can be disabled on driver exit.
In this case, it happens that if the driver used the NAND and set the
DFI arbitration bit, the next access to a static memory controller area,
such as an ethernet card, will stall
On Mon, 2015-08-24 at 00:18 +0530, Muhammad Falak R Wani wrote:
> This patch introduces the use of function kmalloc_array(), instead
> of using kmalloc(), for allocating memory for an array and removes
> the corresponding call to kmalloc().
[]
> diff --git a/drivers/usb/core/driver.c
+Tony and acknowledging him..
On Sun, 23 Aug 2015, Vikas Shivappa wrote:
This document tries to propose alternative interface for the Intel cache
allocation compared to the cgroup interface in the current patchset -
http://marc.info/?l=linux-kernel=143889814520578
More info about cache
Sun, Aug 23, 2015 at 02:11:16AM CEST, julia.law...@lip6.fr wrote:
>Return a negative error code on failure.
>
>A simplified version of the semantic match that finds this problem is as
>follows: (http://coccinelle.lip6.fr/)
>
>//
>@@
>identifier ret; expression e1,e2;
>@@
>(
>if (\(ret < 0\|ret !=
On Fri, 21 Aug 2015, Marcelo Tosatti wrote:
On Thu, Aug 20, 2015 at 05:06:51PM -0700, Vikas Shivappa wrote:
On Mon, 17 Aug 2015, Marcelo Tosatti wrote:
Vikas, Tejun,
This is an updated interface. It addresses all comments made
so far and also covers all use-cases the cgroup interface
This patch introduces the use of function kmalloc_array(), instead
of using kmalloc(), for allocating memory for an array and removes
the corresponding call to kmalloc().
Signed-off-by: Muhammad Falak R Wani
---
drivers/usb/core/driver.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
This document tries to propose alternative interface for the Intel cache
allocation compared to the cgroup interface in the current patchset -
http://marc.info/?l=linux-kernel=143889814520578
More info about cache allocation can be found in Intel SDM june 2015
volume 3, section 17.16.
Design
> From: xili_gchen_5...@hotmail.com
> To: mho...@kernel.org
> CC: a...@linux-foundation.org; linux-kernel@vger.kernel.org;
> kirill.shute...@linux.intel.com; r...@redhat.com; sasha.le...@oracle.com;
> linux...@kvack.org
> Subject: Re: [PATCH] mm: mmap:
When failure occurs and return, vma->vm_pgoff is already set, which is
not a good idea.
Signed-off-by: Chen Gang
---
mm/mmap.c | 13 +++--
1 file changed, 7 insertions(+), 6 deletions(-)
diff --git a/mm/mmap.c b/mm/mmap.c
index 8e0366e..b5a6f09 100644
--- a/mm/mmap.c
+++ b/mm/mmap.c
@@
In pfm_smpl_buffer_alloc, insert_vm_struct may also return -ENOMEM, so
need check it too.
And insert_vm_struct needn't consider about pfm_remap_buffer in failure
process ("goto error" is enough):
- pfm_remap_buffer doen't consider about remap_pfn_range.
- It is about the relationship between
This patch fixes a coding style issue by adding parenthesis
to the sizeof operator, which is the preferred way of using it.
Signed-off-by: Muhammad Falak R Wani
---
drivers/usb/core/buffer.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/usb/core/buffer.c
The commit below adds hot-added memory range to memblock, after
creating pgdat for new node.
commit f9126ab9241f66562debf69c2c9d8fee32ddcc53
Author: Xishi Qiu
Date: Fri Aug 14 15:35:16 2015 -0700
memory-hotplug: fix wrong edge when hot add a new node
But there is a problem:
add_memory()
This patch introduces a blank line after declarations, which
fix the checkpatch.pl warnings at 3 places.
Signed-off-by: Muhammad Falak R Wani
---
drivers/cpufreq/cpufreq.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/cpufreq/cpufreq.c b/drivers/cpufreq/cpufreq.c
index
On 15-08-22 18:36:54, Stefan Agner wrote:
> On 2015-08-21 06:26, Sanchayan Maity wrote:
> > This adds device tree binding documentation for the Colibri VF50
> > touchscreen driver.
> >
> > Signed-off-by: Sanchayan Maity
> > ---
> > .../bindings/input/touchscreen/colibri-vf50-ts.txt | 36
> >
Only compile-tested.
Signed-off-by: Denys Vlasenko
CC: Ingo Molnar
CC: Borislav Petkov
CC: "H. Peter Anvin"
CC: Andy Lutomirski
CC: Kees Cook
CC: x...@kernel.org
CC: linux-kernel@vger.kernel.org
---
arch/x86/math-emu/load_store.c | 63 ++
1 file
On Sun, Aug 23, 2015 at 07:40:32AM +0200, Ingo Molnar wrote:
>
> * Frederic Weisbecker wrote:
>
> > From: Vatika Harlalka
> >
> > The problem addressed in this patch is about affining unpinned timers.
> > Adaptive or Full Dynticks CPUs are currently disturbed by unnecessary
> > jitter due to
A couple of major (hang and deadlock) fixes with fortunately fairly rare
triggering conditions. The PM oops is only really triggered by people
using enclosure services (rare) and the fnic driver is mostly used in
enterprise environments.
The patch is available here:
On 08/23/2015 08:15 AM, Ingo Molnar wrote:
>
> * Denys Vlasenko wrote:
>
>>> static FUNC const st_instr_table[64] = {
>>> - fadd__, fld_i_, fcmovb, fcmovnb, fadd_i, ffree_, faddp_,
>>> _df_c0_,
>>> - fmul__, fxch_i, fcmove, fcmovne, fmul_i, _dd_c8_, fmulp_,
>>> _df_c8_,
On 20/08/15 01:23, Matt Porter wrote:
> On Sat, Aug 08, 2015 at 12:39:40PM +0100, Jonathan Cameron wrote:
>> On 06/08/15 18:38, Matt Porter wrote:
>>> On Mon, Aug 03, 2015 at 11:26:12PM +0200, Peter Meerwald wrote:
On Mon, 3 Aug 2015, Matt Porter wrote:
>>>
>>> ...
>>>
> +static int
On Sun, Aug 23, 2015 at 4:26 AM, Ingo Molnar wrote:
>
> * Andy Lutomirski wrote:
>
>> It's statically initialized, so we don't need to dynamically
>> initialize it too.
>>
>> Reported-by: Brian Gerst
>> Signed-off-by: Andy Lutomirski
>> ---
>>
>> Changes since v1: Delete the code :)
>>
>>
Hi,
This patch fixes issues in coding style, of a missing blank line after
declarations.
Best,
mfrw
Signed-off-by: Muhammad Falak R Wani
---
drivers/cpufreq/cpufreq.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/cpufreq/cpufreq.c b/drivers/cpufreq/cpufreq.c
index
On 15-08-22 18:52:28, Stefan Agner wrote:
> Hi Sanchayan,
>
> On 2015-08-21 06:26, Sanchayan Maity wrote:
> > +static int vf50_ts_probe(struct platform_device *pdev)
> > +{
> > + struct input_dev *input;
> > + struct iio_channel *channels;
> > + struct device *dev = >dev;
> > + struct
On 15-08-22 18:54:28, Stefan Agner wrote:
> On 2015-08-21 06:26, Sanchayan Maity wrote:
> > Add device tree node for touchscreen support on Colibri VF50. The
> > touchscreen functionality on VF50 uses the ADC channels of Vybrid
> > and some GPIOs. Also add pinctrl nodes for proper pinmux.
> >
> >
On Sun, Aug 23, 2015 at 7:38 PM, Vinod Koul wrote:
> On Thu, Aug 20, 2015 at 12:01:27PM +0530, punnaiah choudary kalluri wrote:
>> On Thu, Aug 20, 2015 at 11:43 AM, Vinod Koul wrote:
>> > On Thu, Aug 06, 2015 at 08:49:33AM +0530, Punnaiah Choudary Kalluri wrote:
>> >
>> >> +
On Tue, Aug 18, 2015 at 02:49:15PM +0100, Jon Hunter wrote:
> +#define AHUB_TO_MEMORY 2
> +#define MEMORY_TO_AHUB 4
namespace this aptly as well
> +static void tegra_adma_stop(struct tegra_dma_channel
On Tue, Aug 18, 2015 at 02:49:09PM +0100, Jon Hunter wrote:
> @@ -1543,7 +1531,7 @@ static int tegra_dma_pm_suspend(struct device *dev)
> int ret;
>
> /* Enable clock before accessing register */
> - ret = tegra_dma_runtime_resume(dev);
> + ret = pm_runtime_get_sync(dev);
On Thu, Aug 20, 2015 at 12:01:27PM +0530, punnaiah choudary kalluri wrote:
> On Thu, Aug 20, 2015 at 11:43 AM, Vinod Koul wrote:
> > On Thu, Aug 06, 2015 at 08:49:33AM +0530, Punnaiah Choudary Kalluri wrote:
> >
> >> + list_for_each_entry_safe(desc, next, >done_list, node) {
> >> +
On Sunday 23 August 2015 19:09:33 Vinod Koul wrote:
> On Fri, Aug 21, 2015 at 02:01:59AM +0300, Laurent Pinchart wrote:
> > > > How is 64 bit DMA addressing implemented ? Can you use a 64-bit VDMA on
> > > > a 32- bit platform with LPAE ? Can you use a 32-bit VDMA on a 64-bit
> > > > platform ?
On Fri, Aug 21, 2015 at 04:27:49PM -0400, Paul Gortmaker wrote:
> The Kconfig for this driver is currently:
>
> config MV_XOR
> bool "Marvell XOR engine support"
>
> ...meaning that it currently is not being built as a module by anyone.
> Lets remove the modular code that is essentially
On Fri, Aug 21, 2015 at 02:01:59AM +0300, Laurent Pinchart wrote:
> > > How is 64 bit DMA addressing implemented ? Can you use a 64-bit VDMA on
> > > a 32- bit platform with LPAE ? Can you use a 32-bit VDMA on a 64-bit
> > > platform ? Given that VDMA is an IP core you can instantiate in the
> > >
Oh! Sorry! I made the changes to correct the faults you figured out.
Is it okay now?
Signed-off-by: Aparna Karuthodi
---
drivers/staging/fbtft/fb_pcd8544.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/fbtft/fb_pcd8544.c
Architecture specific code for i386 and x86_64 was unified and merged to
the arch/x86. This patch fix old path of x86 architecture in a comment
from the arch/arm64/include/asm/fixmap.h.
Signed-off-by: Alexander Kuleshov
---
arch/arm64/include/asm/fixmap.h | 2 +-
1 file changed, 1 insertion(+),
Architecture specific code for i386 and x86_64 was unified and merged to
the arch/x86. This patch fix old paths of source code files in comments.
Signed-off-by: Alexander Kuleshov
---
arch/x86/entry/entry_64.S | 4 ++--
arch/x86/ia32/ia32_signal.c| 2 +-
arch/x86/kernel/mcount_64.S
Thanks to Nikolay Borisov who discovered this.
--
Aleksa Sarai (cyphar)
www.cyphar.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read
Export the following functions in order to avoid build errors
when the component PHY_QCOM_UFS is compiled as a module:
ERROR: "ufs_qcom_phy_disable_ref_clk"
[drivers/scsi/ufs/ufs-qcom.ko] undefined!
ERROR: "ufs_qcom_phy_enable_ref_clk"
[drivers/scsi/ufs/ufs-qcom.ko] undefined!
I've discovered a bug in the PIDs cgroup. We aren't properly dealing
with css references (we grab a reference to a css in ->can_attach() and
then drop a reference to a *different* css in ->{cancel_,}attach(). This
is a quick patch I wrote which I believe fixes the problem by getting
This change fixes a compilation warning that happens if SCSI_UFS_QCOM
is compiled as a module.
Also this patch fixes an error happens when insmod the module:
"ufs_qcom: module license 'unspecified' taints kernel."
Signed-off-by: Yaniv Gardi
---
drivers/scsi/ufs/ufs-qcom.c | 7 ++-
1 file
Grab a ref to each source css being migrated from, otherwise it's
possible for the refcount to reach zero between ->can_attach() and
->cancel_attach(). This means that operations on the task's old css
(such as container_of(...)) become unsafe, as we may be operating on a
different css.
In order to simplify the code a set of wrapper functions is created
to test and call each of the variant operations.
Signed-off-by: Yaniv Gardi
---
drivers/scsi/ufs/ufs-qcom.c | 1 -
drivers/scsi/ufs/ufshcd.c | 104 +---
drivers/scsi/ufs/ufshcd.h |
This change is required in order to be able to build the component
as a module.
Signed-off-by: Yaniv Gardi
---
drivers/scsi/ufs/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/scsi/ufs/Kconfig b/drivers/scsi/ufs/Kconfig
index e945383..5f45307 100644
---
Signed-off-by: Yaniv Gardi
---
drivers/scsi/ufs/ufs-qcom.c | 34 +-
drivers/scsi/ufs/ufshcd.h | 21 +
2 files changed, 38 insertions(+), 17 deletions(-)
diff --git a/drivers/scsi/ufs/ufs-qcom.c b/drivers/scsi/ufs/ufs-qcom.c
index
101 - 200 of 522 matches
Mail list logo
