On Fri, Jan 27, 2017 at 5:34 PM, Boris Brezillon
wrote:
> devm_get_gpiod_from_child() currently allows GPIO users to request a GPIO
> that is defined in a child fwnode instead of directly in the device
> fwnode. Extend this API by adding the devm_get_index_gpiod_from_child()
> helpers which does
Below is the list of build error/warning regressions/improvements in
v4.10-rc6[1] compared to v4.9[2].
Summarized:
- build errors: +1/-8
- build warnings: +1197/-649
JFYI, when comparing v4.10-rc6[1] to v4.10-rc5[3], the summaries are:
- build errors: +1/-1
- build warnings: +504/-368
Ha
On Mon, Jan 30, 2017 at 09:46:32AM +0100, Ingo Molnar wrote:
> Ok, I have applied this to tip:x86/urgent.
>
> Note that there are new conflicts with your pending work in
> tip:x86/microcode, and
> I fixed them up in:
>
> 7c5b4112040e Merge branch 'x86/urgent' into x86/microcode, to resolve
>
On Sun, Jan 29, 2017 at 10:33:27AM +0800, Icenowy Zheng wrote:
> As we have already changed the DTSI file, the trnasitional dt-bindings
> header sun8i-h3-ccu.h will not be needed any more.
>
> Remove them.
>
> Signed-off-by: Icenowy Zheng
Your prefix is wrong, this is not part of the clk framew
On 30/01/17 11:10, Ulf Hansson wrote:
> On 28 January 2017 at 09:16, Adrian Hunter wrote:
>> On 27/01/2017 5:12 p.m., Ulf Hansson wrote:
>>>
>>> On 26 January 2017 at 13:39, Adrian Hunter
>>> wrote:
On 26/01/17 12:50, Ulf Hansson wrote:
>
> On 11 January 2017 at 18:19, Gregory C
On 01/27/2017 07:06 PM, Bhumika Goyal wrote:
> Declare i2c_algorithm structures as const as they are only stored in the
> algo field of an i2c_adapter structure. This field is of type const, so
> i2c_algorithm structures having this property can be made const too.
> Done using Coccinelle:
>
> @r
Hi all,
Ok if we merge the entire series through drm-intel (likely for 4.12, 4.11
is getting a bit late)? We'd like to use this there, and Mauro already
reviewed the v4l side ...
Thanks, Daniel
On Mon, Jan 16, 2017 at 02:12:07PM +, Tvrtko Ursulin wrote:
> From: Tvrtko Ursulin
>
> Scatterli
On 24/01/17 10:50, Ritesh Harjani wrote:
> platform_execute_tuning should not really exist as it does not
> do anything useful.
>
> So remove this ops and directly plug sdhci_msm_execute_tuning
> with mmc_host_ops.
>
> Also in case of HS400 tuning clear SDHCI_HS400_TUNING flag once
> HS400 relate
; Suggested-by: Michael Ellerman
> Signed-off-by: Andrew Donnellan
> ---
>
> On top of linux-next 20170130
Probably best done on top of powerpc-next and I can cope with the
conflicts one more time.
> diff --git a/arch/powerpc/Kconfig b/arch/powerpc/Kconfig
> index 689cf9218b21.
On Mon, Jan 23, 2017 at 5:08 PM, Dan O'Donovan wrote:
> From: Crestez Dan Leonard
>
> When using devicetree spi_device.modalias is set to the compatible
> string with the vendor prefix removed. For SPI devices described via
> ACPI the spi_device.modalias string is initialized by acpi_device_hid.
From: "Ken Goldman" mailto:kg...@linux.vnet.ibm.com>>
Date: 26-Jan-2017 2:53 AM
Subject: Re: [tpmdd-devel] [PATCH v9 2/2] tpm: add securityfs
support,for TPM 2.0 firmware event log
To: mailto:linux-kernel@vger.kernel.org>>,
mailto:linux-security-mod...@vger.kernel.org>>,
mailto:tpmdd-de...@lists
Mark the corresponding VMA with VM_CDM flag if the allocated page happens
to be from a CDM node. This can be expensive from performance stand point.
There are multiple checks to avoid an expensive page_to_nid lookup but it
can be optimized further.
Signed-off-by: Anshuman Khandual
---
mm/mempoli
On Mon, Jan 30, 2017 at 01:42:40AM +, André Przywara wrote:
> > +&ccu {
> > + compatible = "allwinner,sun8i-h3-ccu";
> > +};
>
> I believe this kind of sharing nodes is a bit frowned upon in connection
> with sharing .dtsi's. If the compatible name differs, I think it
> deserves to be a sepa
KY Srinivasan writes:
>> -Original Message-
>> From: Vitaly Kuznetsov [mailto:vkuzn...@redhat.com]
>> Sent: Thursday, January 19, 2017 6:17 AM
>> To: de...@linuxdriverproject.org
>> Cc: Thomas Gleixner ; linux-kernel@vger.kernel.org;
>> Haiyang Zhang ; KY Srinivasan
>> ; John Stultz ; Ale
VMA containing CDM memory should be excluded from KSM merging. This change
makes madvise(MADV_MERGEABLE) request on target VMA to be ignored.
Signed-off-by: Anshuman Khandual
---
mm/ksm.c | 4
1 file changed, 4 insertions(+)
diff --git a/mm/ksm.c b/mm/ksm.c
index 9ae6011..2fb8939 100644
--
Hi,
On Sun, Jan 29, 2017 at 10:33:24AM +0800, Icenowy Zheng wrote:
> As the CCU in the Allwinner H5 SoC is very similar to the one in H3,
> rename the H3 driver to sunxi-h3-h5 so that it can be extended with H5
> support.
>
> Signed-off-by: Icenowy Zheng
> ---
> The original PATCH v2 3/9 is spli
On Mon, Jan 30, 2017 at 02:23:38PM +0900, Taeung Song wrote:
> Currently there are several parts not checking NULL
> after allocating with zalloc() or asigning NULL value
> to a pointer variable after doing free().
>
> So I fill in code checking NULL and
> use zfree() instead of free().
can't see
On Sun, Jan 29, 2017 at 04:50:03PM -0600, Trevor Cordes wrote:
> On 2017-01-25 Michal Hocko wrote:
> > On Wed 25-01-17 04:02:46, Trevor Cordes wrote:
> > > OK, I patched & compiled mhocko's git tree from the other day
> > > 4.9.0+. (To confirm, weird, but mhocko's git tree I'm using from a
> > > co
On 24/01/17 10:50, Ritesh Harjani wrote:
> This removes CDC init sequence comments which are
> not useful anyway.
>
> Signed-off-by: Ritesh Harjani
Acked-by: Adrian Hunter
> ---
> drivers/mmc/host/sdhci-msm.c | 14 +-
> 1 file changed, 1 insertion(+), 13 deletions(-)
>
> diff --g
On Mon, Jan 30, 2017 at 08:25:25AM +, Ajay Kaher wrote:
>
First off, you are sending html email, which the mailing list keeps
rejecting, why are you ignoring that?
>
> There is race condition when two USB class drivers try to call
>
> init_usb_class at the same time and leads to crash.
On Mon, Jan 30, 2017 at 05:35:28PM +0900, Taeung Song wrote:
SNIP
> +#define for_each_event_system(dir, dent, tps)\
> + while ((dent = readdir(dir))) \
> + if (dent->d_type == DT_DIR && \
> + (strc
On Mon, Jan 30, 2017 at 09:55:04AM +0100, Lukasz Majewski wrote:
> Hi Thierry,
>
> > On Mon, Jan 30, 2017 at 09:36:49AM +0100, Lukasz Majewski wrote:
> > > Hi Thierry,
> > >
> > > > On Mon, Jan 30, 2017 at 08:23:12AM +0100, Thierry Reding wrote:
> > > > > On Sun, Jan 29, 2017 at 10:54:07PM +0100,
On 01/26/2017 01:09 PM, Michal Hocko wrote:
On Thu 12-01-17 16:37:12, Michal Hocko wrote:
[...]
+void *kvmalloc_node(size_t size, gfp_t flags, int node)
+{
+ gfp_t kmalloc_flags = flags;
+ void *ret;
+
+ /*
+* vmalloc uses GFP_KERNEL for some internal allocations (e.g p
>-Original Message-
>From: Arseny Solokha [mailto:asolo...@kb.kras.ru]
>Sent: Sunday, January 29, 2017 2:52 PM
>To: Claudiu Manoil
>Cc: net...@vger.kernel.org; linux-kernel@vger.kernel.org; Arseny Solokha
>
>Subject: [PATCH] gianfar: synchronize DMA API usage by free_skb_rx_queue w/
>gfar_
On 01/28/2017 07:41 PM, Jonathan Cameron wrote:
On 26/01/17 14:28, Fabrice Gasnier wrote:
Add DMA optional support to STM32 ADC, as there is a limited number DMA
channels (request lines) that can be assigned to ADC. This way, driver
may fall back using interrupts when all DMA channels are in use
On Mon, Jan 30, 2017 at 02:23:39PM +0900, Taeung Song wrote:
> If 'evsel' is NULL, in perf_evsel__is_bpf_output()
> NULL pointer error can happen so check it.
>
> Cc: Jiri Olsa
> Cc: Namhyung Kim
> Signed-off-by: Taeung Song
> ---
> tools/perf/util/evsel.c | 6 --
> 1 file changed, 4 inser
* Borislav Petkov wrote:
> On Fri, Jan 27, 2017 at 11:14:06AM +0300, Andrey Ryabinin wrote:
> > Works for me as well.
> > Tested-by: Andrey Ryabinin
>
> Thanks!
Ok, I have applied this to tip:x86/urgent.
Note that there are new conflicts with your pending work in tip:x86/microcode,
and
I f
On Sun 29-01-17 00:27:27, Tetsuo Handa wrote:
> Michal Hocko wrote:
> > Tetsuo,
> > before we settle on the proper fix for this issue, could you give the
> > patch a try and try to reproduce the too_many_isolated() issue or
> > just see whether patch [1] has any negative effect on your oom stress
>
Hi Thierry,
> On Mon, Jan 30, 2017 at 09:36:49AM +0100, Lukasz Majewski wrote:
> > Hi Thierry,
> >
> > > On Mon, Jan 30, 2017 at 08:23:12AM +0100, Thierry Reding wrote:
> > > > On Sun, Jan 29, 2017 at 10:54:07PM +0100, Lukasz Majewski wrote:
> > > > > From: Lukasz Majewski
> > > > >
> > > > > T
On Mon, Jan 30, 2017 at 09:07:15AM +0100, Uwe Kleine-König wrote:
> Hello,
>
> On Mon, Jan 30, 2017 at 08:12:17AM +0100, Thierry Reding wrote:
> > On Mon, Jan 30, 2017 at 10:33:07AM +0530, Shailendra Verma wrote:
> > > of_device_get_match_data could return NULL, and so can cause
> > > a NULL point
ARM-soc folks,
Please find below the pull request for a DT fix affecting a large
number of 32bit platforms, which has been acked by a number of
platform maintainers.
* From v1: Dropped the controvertial cortex-a15-gic->arm,gic-400
change in the example, at Rob's request.
The following changes
On Mon, Jan 30, 2017 at 09:36:49AM +0100, Lukasz Majewski wrote:
> Hi Thierry,
>
> > On Mon, Jan 30, 2017 at 08:23:12AM +0100, Thierry Reding wrote:
> > > On Sun, Jan 29, 2017 at 10:54:07PM +0100, Lukasz Majewski wrote:
> > > > From: Lukasz Majewski
> > > >
> > > > This patch provides separate s
On 29/01/17 22:51, Olof Johansson wrote:
> On Fri, Jan 27, 2017 at 02:30:01PM -0600, Rob Herring wrote:
>> On Mon, Jan 23, 2017 at 03:56:13PM +, Marc Zyngier wrote:
>>> The joys of copy/paste: the example of a virtualization capable GIC
>>> in the DT binding was wrong, and propagated to dozens
Hi Noralf,
On Fri, Jan 27, 2017 at 08:56:29PM +0100, Noralf Trønnes wrote:
> This is an attempt at providing a DRM version of drivers/staging/fbtft.
>
> The tinydrm library provides a very simplified view of DRM in particular
> for tiny displays that has onboard video memory and is connected thro
Commit-ID: 24c2503255d35c269b67162c397a1a1c1e02f6ce
Gitweb: http://git.kernel.org/tip/24c2503255d35c269b67162c397a1a1c1e02f6ce
Author: Borislav Petkov
AuthorDate: Wed, 25 Jan 2017 21:00:48 +0100
Committer: Ingo Molnar
CommitDate: Mon, 30 Jan 2017 09:32:42 +0100
x86/microcode: Do not ac
[...]
>>> + */
>>> +static int xenon_child_node_of_parse(struct platform_device *pdev)
>>> +{
>>> + struct device_node *np = pdev->dev.of_node;
>>> + struct sdhci_host *host = platform_get_drvdata(pdev);
>>> + struct mmc_host *mmc = host->mmc;
>>> + struct sdhci_pltfm_host
Hi Thierry,
> On Mon, Jan 30, 2017 at 08:23:12AM +0100, Thierry Reding wrote:
> > On Sun, Jan 29, 2017 at 10:54:07PM +0100, Lukasz Majewski wrote:
> > > From: Lukasz Majewski
> > >
> > > This patch provides separate set of pwm ops utilized by
> > > i.MX's PWMv1 and PWMv2.
> > >
> > > Signed-off
On Fri, Jan 27, 2017 at 05:23:24PM +, Brian Starkey wrote:
> Hi,
>
> We're looking to enable the per-plane color management hardware in
> Mali-DP with atomic properties, which has sparked some conversation
> around how to handle YCbCr formats.
>
> As it stands today, it's assumed that a drive
Such as for_each_subsystem and for_each_event in util/parse-events.c,
add new macros 'for_each_event_system' and 'for_each_event_file'
for easy iteration over the tracepoints
in order to be more compact and readable.
Cc: Steven Rostedt
Cc: Frederic Weisbecker
Cc: Jiri Olsa
Cc: Namhyung Kim
Sig
Hello,
On Mon, 30 Jan 2017 10:21:43 +0530, Shailendra Verma wrote:
> of_match_device could return NULL, and so can cause a NULL
> pointer dereference later.
>
> Signed-off-by: Shailendra Verma
In practice, I don't see how of_match_device() can return NULL here.
Indeed, those drivers only suppor
Hello,
On Mon, Jan 30, 2017 at 08:12:17AM +0100, Thierry Reding wrote:
> On Mon, Jan 30, 2017 at 10:33:07AM +0530, Shailendra Verma wrote:
> > of_device_get_match_data could return NULL, and so can cause
> > a NULL pointer dereference later.
> >
> > Signed-off-by: Shailendra Verma
> > ---
> > d
On Fri 27-01-17 11:40:42, Theodore Ts'o wrote:
> On Fri, Jan 27, 2017 at 10:37:35AM +0100, Michal Hocko wrote:
> > If this ever turn out to be a problem and with the vmapped stacks we
> > have good chances to get a proper stack traces on a potential overflow
> > we can add the scope API around the
On 27 January 2017 at 17:04, Stefan Wahren wrote:
> Am 27.01.2017 um 16:27 schrieb Ulf Hansson:
>> On 27 January 2017 at 12:36, Gerd Hoffmann wrote:
>>> From: Eric Anholt
>>>
>>> The 2835 has two SD controllers: The Arasan SDHCI controller (supported
>>> by the iproc driver) and a custom SD con
The following upstream headers were updated:
- The x86 cpufeatures.h file picked up a couple of new feature entries
- The PowerPC and ARM KVM headers picked up new features
None of which requires changes to perf tooling, so refresh the tooling copy.
Solves these build time warnings:
Warning
On Fri 27-01-17 21:12:26, Daniel Borkmann wrote:
> On 01/27/2017 11:05 AM, Michal Hocko wrote:
> > On Thu 26-01-17 21:34:04, Daniel Borkmann wrote:
[...]
> > > So to answer your second email with the bpf and netfilter hunks, why
> > > not replacing them with kvmalloc() and __GFP_NORETRY flag and ad
Hi Shailendra,
Marek and I already reviewed this patch, and you're resending it
without any of the comments addressed. Is this a mistake?
On Mon, 30 Jan 2017 10:29:17 +0530
Shailendra Verma wrote:
> of_match_device could return NULL, and so can cause a NULL
> pointer dereference later.
>
> Sig
This patch adds a struct device member to UDC data structure and
makes changes to the arguments of dev_err and dev_dbg calls so that
the debug prints work for both pci and platform devices.
Signed-off-by: Raviteja Garimella
---
drivers/usb/gadget/udc/amd5536udc.h | 4 +++-
drivers/usb/gadge
Change the argument from NULL to a struct device for the
dma_pool_create call during dma init.
Signed-off-by: Raviteja Garimella
---
drivers/usb/gadget/udc/snps_udc_core.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/usb/gadget/udc/snps_udc_core.c
b/drivers/us
This patch splits the amd5536udc driver into two -- one that does
pci device registration and the other file that does the rest of
the driver tasks like the gadget/ep ops etc for Synopsys UDC.
This way of splitting helps in exporting core driver symbols which
can be used by any other platform/pci
The changes are being submitted as PATCH this time. Below are the
details of main changes with respect to previous RFC versions.
Changes from RFC v2:
===
Patch 1/6 now splits the driver into amd5536udc_pci_.c (which
contains only the PCI device registration part), and amd5536udc.c
On 2017-01-27 16:52, Rob Herring wrote:
> On Mon, Jan 23, 2017 at 11:24:18AM +0100, Peter Rosin wrote:
>> On 2017-01-22 14:30, Jonathan Cameron wrote:
>>> On 18/01/17 15:57, Peter Rosin wrote:
Allow bindings for a GPIO controlled mux to be specified in the
mux consumer node.
Sig
On Mon, Jan 30, 2017 at 08:49:14AM +0100, Boris Brezillon wrote:
> On Sun, 29 Jan 2017 22:54:11 +0100
> Lukasz Majewski wrote:
>
> > This commit provides apply() callback implementation for i.MX's PWMv2.
> >
> > Suggested-by: Stefan Agner
> > Suggested-by: Boris Brezillon
> > Signed-off-by: Lu
On 30/01/2017 at 10:30:05 +0530, Shailendra Verma wrote:
> of_device_get_match_data could return NULL, and so can cause
> a NULL pointer dereference later.
>
No, it will never return NULL because it will always match.
At some point, I would really like people to stop blindly sending
patches gene
1001 - 1053 of 1053 matches
Mail list logo
