Bjorn Andersson writes:
> On Wed 16 Nov 10:49 PST 2016, Kalle Valo wrote:
>
>> Bjorn Andersson wrote:
>> > The correct include file for getting errno constants and ERR_PTR() is
>> > linux/err.h, rather than linux/errno.h, so fix the include.
>> >
>> > Fixes: e8b123e60084 ("soc: qcom: smem_state
On Tuesday, November 22, 2016 3:47:09 PM CET Hannes Reinecke wrote:
> index 05f7782..ee6f852 100644
> --- a/drivers/scsi/hpsa.c
> +++ b/drivers/scsi/hpsa.c
> @@ -2031,7 +2031,7 @@ static struct hpsa_scsi_dev_t
> *lookup_hpsa_scsi_dev(struct ctlr_info *h,
>
> static int hpsa_slave_alloc(struct scs
-replace-kzalloc-with-kmem_cache/20161122-213614
coccinelle warnings: (new ones prefixed by >>)
>> drivers/android/binder.c:3705:2-20: WARNING: NULL check before freeing
>> functions like kfree, debugfs_remove, debugfs_remove_recursive or
>> usb_free_urb is not needed. May
David Howells wrote:
> That makes it less clear. I think something like this makes it much more
> obvious:
>
> static efi_status_t get_efi_var(const efi_char16_t *name,
> const efi_guid_t *vendor,
> u32 *attr,
>
On Tue, 2016-11-22 at 14:17 +, David Howells wrote:
> Lukas Wunner wrote:
>
> > Small nit, checkpatch usually complains that this should be written as
> > 12-character SHA-1 followed by the commit subject, i.e.
> >
> > 0a637ee61247 ("x86/efi: Allow invocation of arbitrary boot services")
>
Lukas Wunner wrote:
> You dropped the efi_system_table_t *sys_table_arg argument but this
> isn't defined anywhere as a static global.
It seems to me that passing this value in on x86 is probably a bad idea as
it's not mixed-mode safe. Should I just pass NULL there in that case?
David
Dear one.
This is to officially inform you about your $8.7m with the United
Nations Assisted Program and for your information you will receive
your fund through (ATM CARD, CASHIER CHECK OR wire transfer) please
choose payment method. Therefore you are advised to contact US with
your personal in
Am Dienstag, 22. November 2016, 10:44:22 schrieb Daniel Lezcano:
> From: Brian Norris
>
> The "arm,no-tick-in-suspend" property was introduced to note
> implementations where the system counter does not quite follow the ARM
> specification that it "must be implemented in an always-on power
> doma
A bugfix has left the 'sd' variable uninitialized:
drivers/scsi/hpsa.c: In function 'hpsa_slave_alloc':
drivers/scsi/hpsa.c:2033:5: error: 'sd' may be used uninitialized in this
function [-Werror=maybe-uninitialized]
This reverts back to calling lookup_hpsa_scsi_dev() for the
HPSA_PHYSICAL_DEVIC
We get a harmless false-positive warning with the newly added nps
clocksource driver:
drivers/clocksource/timer-nps.c: In function 'nps_setup_clocksource':
drivers/clocksource/timer-nps.c:102:6: error: 'nps_timer1_freq' may be used
uninitialized in this function [-Werror=maybe-uninitialized]
Gcc
On Tue, 22 Nov 2016 15:52:45 +0900
Namhyung Kim wrote:
> Hi Steve,
>
> On Fri, Nov 18, 2016 at 05:54:00PM -0500, Steven Rostedt wrote:
> > From: "Steven Rostedt (Red Hat)"
> >
> > Add a way to retrieve the preempt count as well as the latency flags from a
> > pevent_record.
> >
> > int peven
On Tue, Nov 22, 2016 at 01:51:50PM +0800, Gonglei wrote:
> # make C=2 CF="-D__CHECK_ENDIAN__" ./drivers/virtio/
>
> drivers/virtio/virtio_ring.c:423:19: warning: incorrect type in assignment
> (different base types)
> drivers/virtio/virtio_ring.c:423:19:expected unsigned int [unsigned]
> [a
Hi Tomasz
> -Original Message-
> From: Tomasz Nowicki [mailto:t...@semihalf.com]
> Sent: 22 November 2016 13:58
> To: liudongdong (C); helg...@kernel.org; a...@arndb.de;
> raf...@kernel.org; lorenzo.pieral...@arm.com; Wangzhou (B);
> pratyush.an...@gmail.com
> Cc: linux-...@vger.kernel.org
From: Hannes Frederic Sowa
Date: Tue, 22 Nov 2016 13:26:45 +0100
> On 22.11.2016 07:27, Manjeet Pawar wrote:
>> From: Rohit Thapliyal
>>
>> np checked for NULL and then dereferenced. It should be modified
>> for NULL case.
>>
>> Signed-off-by: Rohit Thapliyal
>> Signed-off-by: Manjeet Pawar
Hi Sudeep,
On Tuesday 22 November 2016 04:23 PM, Sudeep Holla wrote:
>
>
> On 22/11/16 10:41, Bartosz Golaszewski wrote:
>> Add a function allowing to retrieve the compatible string of the root
>> node of the device tree.
>>
>
> Rob has queued [1] and it's in -next today. You can reuse that if
Hi Arnd,
On mar., nov. 22 2016, Arnd Bergmann wrote:
> Both of these drivers won't work on 64-bit architectures unless they
> are redesigned, since they store a virtual address pointer in a 32-bit
> field of the descriptors:
>
> drivers/net/ethernet/marvell/mvneta_bm.c: In function 'mvneta_bm_
- Original Message -
> From: "Tom Lendacky"
> To: "Paolo Bonzini" , "Brijesh Singh"
> , k...@vger.kernel.org
> Cc: rkrc...@redhat.com, j...@8bytes.org, x...@kernel.org,
> linux-kernel@vger.kernel.org, mi...@redhat.com,
> h...@zytor.com, t...@linutronix.de, b...@suse.de
> Sent: Tuesday,
Em Tue, 22 Nov 2016 15:49:47 +0200
Jani Nikula escreveu:
> On Mon, 21 Nov 2016, Mauro Carvalho Chehab wrote:
> > Em Mon, 21 Nov 2016 10:44:44 -0700
> > Jonathan Corbet escreveu:
> >
> >> On Sun, 20 Nov 2016 14:08:31 -0200
> >> Mauro Carvalho Chehab wrote:
> >> > NOTE: some images use more
On Tue, Nov 22, 2016 at 12:38:59PM +0100, Borislav Petkov wrote:
> On Tue, Nov 15, 2016 at 12:29:35PM -0600, Tom Lendacky wrote:
> > > Makes sense, but I think at least a dmesg warning here
> > > might be a good idea.
> >
> > Good idea. Should it be a warning when it is first being set up or
> >
On 21 November 2016 at 16:51, Pali Rohár wrote:
> On Friday 11 November 2016 18:20:50 Pali Rohár wrote:
>> Hi! I will open discussion about mac address and calibration data for
>> wl1251 wireless chip again...
>>
>> Problem: Mac address & calibration data for wl1251 chip on Nokia N900
>> are store
Hi,
On Mon, Nov 21, 2016 at 07:04:50PM +0100, Nicola Saenz Julienne wrote:
> The current device name for sbs-battery is derived from it's i2c address.
> This is not acceptable if we want to be able to trigger the
> "external_power_changed()" routine from a charger driver.
>
> Signed-off-by: Nicol
From: Arnd Bergmann
Date: Tue, 22 Nov 2016 15:21:22 +0100
> Both of these drivers won't work on 64-bit architectures unless they
> are redesigned, since they store a virtual address pointer in a 32-bit
> field of the descriptors:
>
> drivers/net/ethernet/marvell/mvneta_bm.c: In function 'mvneta_
On 22.11.2016 16:04, Michael S. Tsirkin wrote:
> On Tue, Nov 22, 2016 at 01:51:50PM +0800, Gonglei wrote:
>> # make C=2 CF="-D__CHECK_ENDIAN__" ./drivers/virtio/
>>
>> drivers/virtio/virtio_ring.c:423:19: warning: incorrect type in assignment
>> (different base types)
>> drivers/virtio/virtio_rin
Currently we leak a lot of things when tearing down the IRQs this patch
fixes this cleaning up both the IRQ mappings and the IRQ domain itself.
Signed-off-by: Charles Keepax
---
Changes since v2:
- Updated to use the defines added in the previous patch
Thanks,
Charles
drivers/mfd/arizona-irq
Hi Eric,
On Tue, Nov 22, 2016 at 06:29:33AM -0800, Eric Dumazet wrote:
On Tue, Nov 22, 2016 at 2:33 AM, Brian Starkey wrote:
Hi,
On Fri, Nov 18, 2016 at 01:40:43AM +0100, Thomas Gleixner wrote:
Brian,
On Thu, 17 Nov 2016, Brian Starkey wrote:
No joy with this patch :-(
I had to add an
Signed-off-by: Charles Keepax
---
drivers/mfd/arizona-irq.c | 21 +++--
1 file changed, 15 insertions(+), 6 deletions(-)
diff --git a/drivers/mfd/arizona-irq.c b/drivers/mfd/arizona-irq.c
index 724fa54..88729cf 100644
--- a/drivers/mfd/arizona-irq.c
+++ b/drivers/mfd/arizona-irq.
On Monday 21 November 2016 10:31 PM, Axel Haslam wrote:
> Enable the davinci ohci driver as a module for usb
> tested with the omap138-lcdk hawk board.
>
> Signed-off-by: Axel Haslam
Applied to v4.10/defconfg after dropping "hawk" from commit description.
Thanks,
Sekhar
On 11/05/2016 06:44 PM, Maciej W. Rozycki wrote:
On Fri, 4 Nov 2016, Peter Hurley wrote:
These bios screens do not have any mention of PNP settings.
I am getting output over the console (via ipmi) until the boot hangs.
Yeah, probably the device actually decodes io address access anyway,
but
Hi Sebastian,
sorry I wasn't aware of that feature, I'll have a look at the whole
thing and rework the patch.
Regards,
Nicolas
On 22/11/16 16:23, Sebastian Reichel wrote:
> Hi,
>
> On Mon, Nov 21, 2016 at 07:04:50PM +0100, Nicola Saenz Julienne wrote:
>> The current device name for sbs-battery i
On Tuesday 22 November 2016 16:22:57 Michal Kazior wrote:
> On 21 November 2016 at 16:51, Pali Rohár wrote:
> > On Friday 11 November 2016 18:20:50 Pali Rohár wrote:
> >> Hi! I will open discussion about mac address and calibration data for
> >> wl1251 wireless chip again...
> >>
> >> Problem: Mac
Hi,
On Fri, Nov 18, 2016 at 10:22:40AM +0800, Chen-Yu Tsai wrote:
> On Fri, Nov 18, 2016 at 3:02 AM, Maxime Ripard
> wrote:
> > On Wed, Nov 16, 2016 at 05:37:31PM +0800, Chen-Yu Tsai wrote:
> >> The sun4i DRM driver counts the number of endpoints it found and
> >> registers the whole DRM pipeline
On Mon, Nov 21, 2016 at 02:19:32PM +0100, Oliver Neukum wrote:
> I don't understand it, bit please test the attached patch
> with dynamic debugging for cdc-acm and the kernel log level
> at maximum.
> diff --git a/drivers/usb/class/cdc-acm.c b/drivers/usb/class/cdc-acm.c
> index 6895f9e..f03b5db
Linus,
Please pull the latest sched-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
sched-urgent-for-linus
# HEAD: 8e5bfa8c1f8471aa4a2d30be631ef2b50e10abaf sched/autogroup: Do not use
autogroup->tg in zombie threads
Two fixes for autogroup sched
Hi Allan,
On 18/11/16 15:09, Jon Hunter wrote:
> Hi Allan,
>
> On 14/11/16 09:45, ASIX_Allan [Office] wrote:
>> Hi Jon,
>>
>> Please help to double check if the USB host controller of your Terga
>> platform had been powered OFF while running the ax88772_suspend() routine or
>> not?
>
> Sorry fo
Actually only the mvneta_bm support is not 64-bits compatible.
The mvneta code itself can run on 64-bits architecture.
Signed-off-by: Gregory CLEMENT
---
drivers/net/ethernet/marvell/Kconfig | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/net/ethernet/marvell/Kconfi
On Tue, 22 Nov 2016, Mauro Carvalho Chehab wrote:
> I tried both, none broke the long lines on
> Documentation/media/uapi/v4l/fieldseq_tb.svg.
How about:
'tidy -xml -i Documentation/media/uapi/v4l/fieldseq_tb.svg | fmt -sw 80'
Both pretty indents and folds. I think it should Just Work(tm).
B
On Tue, Nov 22, 2016 at 03:34:19PM +0100, Arnd Bergmann wrote:
> We now pass the device to the debug messages, but on non-x86,
> this is an invalid pointer in vga_arb_device_init:
>
> drivers/gpu/vga/vgaarb.c: In function 'vga_arb_device_init':
> drivers/gpu/vga/vgaarb.c:1467:4: error: 'dev' may b
On Tue, 15 Nov 2016, Milo Kim wrote:
> TPS65217 IRQ domain should be removed and initialised as NULL when the
> module is unloaded for the next use. When tps65217.ko is loaded again,
> it causes the page fault. This patch fixes the error below.
>
> root@arm:~# lsmod | grep "tps"
> tps65217_charge
On Tue, Nov 22, 2016 at 05:22:38PM +0200, Michael S. Tsirkin wrote:
> The issue is it's a (potential) security hole, not a slowdown.
How? Because the bounce buffers will be unencrypted and someone might
intercept them?
> To disable unsecure things. If someone enables SEV one might have an
> expec
On Tue, 15 Nov 2016, Milo Kim wrote:
> TPS65217 MFD is an interrupt controller and MFD slave devices like
> tps65217-charger and tps65217-pwrbutton request an interrupt to handle
> each HW event.
>
> Currently, TPS65217 IRQ name is not defined, so the result is as below.
>
> root@arm:~# cat /pro
On Tue, 15 Nov 2016, Milo Kim wrote:
> TPS65217 interrupt register includes read/writeable mask bits with
> read-only status bits. (bit 4, 5, 6 are R/W, bit 0, 1, 2 are RO)
> And reserved bit is not required.
>
> Register update operation is preferred for disabling all interrupts during
> the dev
[linux-next: manual merge of the char-misc tree with the lightnvm tree] On
22/11/2016 (Tue 18:29) Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the char-misc tree got a conflict in:
>
> drivers/lightnvm/core.c
>
> between commit:
>
> 7b0d392f6957 ("lightnvm: remove sys
On Tue, 15 Nov 2016, Milo Kim wrote:
> Rework the IRQ handler by using HW IRQ number and status bit.
>
> Each HW IRQ number is matched with TPS65217 register layout[*].
> (USB IRQ number is 0, AC is 1, Push button is 2)
>
> When an interrupt is enabled, mask bit should be cleared (unmasked).
> I
On Tue, 15 Nov 2016, Milo Kim wrote:
> TPS65217 INT pin is used for the system wakeup from suspend mode.
> This patch enables push button or charger input event as a wakeup source.
>
> Signed-off-by: Milo Kim
> ---
> drivers/mfd/tps65217.c | 2 ++
> 1 file changed, 2 insertions(+)
Applied, tha
Hi Sekhar,
On 22/11/16 15:06, Sekhar Nori wrote:
Hi Sudeep,
On Tuesday 22 November 2016 04:23 PM, Sudeep Holla wrote:
On 22/11/16 10:41, Bartosz Golaszewski wrote:
Add a function allowing to retrieve the compatible string of the root
node of the device tree.
Rob has queued [1] and it's i
Hi Sekhar
On Tue, Nov 22, 2016 at 11:37 AM, Sekhar Nori wrote:
> On Monday 21 November 2016 10:23 PM, Axel Haslam wrote:
>> The hawk board VBUS is fixed to a 5v source, and the over
>> current pin is actually not connected to the SoC.
>>
>> Do not reseve these gpios for OHCI as they are not relat
On 11/22/2016 12:03 AM, Tejun Heo wrote:
> blkcg allocates some per-cgroup data structures with GFP_NOWAIT and
> when that fails falls back to operations which aren't specific to the
> cgroup. Occassional failures are expected under pressure and falling
> back to non-cgroup operation is the right
On Fri, Nov 18, 2016 at 07:18:47PM +0100, Christophe JAILLET wrote:
> If 'sun4i_backend_drm_format_to_layer()' does not return 0, then 'val' is
> left unmodified.
> As it is not initialized either, the return value can be anything.
>
> It is likely that returning the error code was expected here.
Hi Kieran,
Thank you for the patch.
On Thursday 09 Jun 2016 18:57:02 Kieran Bingham wrote:
> Minor tweaks to document the swap register and make the documentation
> match the struct ordering
>
> Signed-off-by: Kieran Bingham
Reviewed-by: Laurent Pinchart
and applied to my tree.
> ---
> dri
On Mon, 21 Nov 2016, Christophe JAILLET wrote:
> The "perf_counter_reset" case has already been handled above.
> Moreover "ORANGEFS_PARAM_REQUEST_OP_READAHEAD_COUNT_SIZE" is not a really
> consistent.
> It is likely that this (dead) code is a cut and paste left over.
That's exactly what this is.
On apq8016, apq8084 and apq8074 platforms, when we want to do a
software reset, we need to poke some additional vendor specific
registers. If we don't do so, the following error message appears:
mmc0: Reset 0x1 never completed.
sdhci: === REGISTER DUMP (mmc0)===
sdhci: Sys addr: 0x
Joe Perches wrote:
> > > Small nit, checkpatch usually complains that this should be written as
> > > 12-character SHA-1 followed by the commit subject, i.e.
> > >
> > > 0a637ee61247 ("x86/efi: Allow invocation of arbitrary boot services")
> >
> > In this case, checkpatch is wrong.
>
> Why do y
On Tue, 22 Nov 2016, Lee Jones wrote:
> On Mon, 14 Nov 2016, Charles Keepax wrote:
>
> > We have arizona_map_irq we might as well use it rather than hard coding
> > it in several places.
> >
> > Signed-off-by: Charles Keepax
> > ---
> > drivers/mfd/arizona-irq.c | 21 +
> >
On 19.11.2016 18:40, Quentin Lambert wrote:
> Most error branches following the call to kzalloc contain
> a call to kfree. This patch add these calls where they are
> missing.
>
> This issue was found with Hector.
Hi Quentin,
most error branches also do set the freed pointer to NULL,
please do the
On 11/22/2016 01:13 AM, Stephen Boyd wrote:
On 11/21, Georgi Djakov wrote:
The clk_hw_onecell_data struct is missing references to the
actual clocks. Fix this.
Reported-by: Michael Scott
Signed-off-by: Georgi Djakov
---
drivers/clk/qcom/clk-smd-rpm.c | 20 +---
1 file changed
On Mon, 21 Nov 2016, Milo Kim wrote:
> AC and USB interrupts are related with external power input.
> PB interrupt means push button pressed or released event.
> Use better human readable definitions.
>
> Signed-off-by: Milo Kim
> ---
> arch/arm/boot/dts/am335x-bone-common.dtsi | 4 ++--
> incl
On 11/11/2016 05:05 AM, Ming Lei wrote:
Hi,
This patchset cleans up direct access to bvec table.
The 1st patch passes bvec table to bio_init(), so that
direct access to bvec table in bio initialization is avoided.
For other patches, most of them uses bio_add_page()
to replace hardcode style of
Linus,
Please pull the latest x86-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
x86-urgent-for-linus
# HEAD: e5dce2868818ca8706924f7bdc7939d481eefab0 x86/platform/intel-mid:
Rename platform_wdt to platform_mrfld_wdt
Misc fixes:
- two fixes t
Hello, Ingo,
This series contains the following changes:
1. Documentation updates, yet again just simple changes.
http://lkml.kernel.org/r/20161114164649.ga15...@linux.vnet.ibm.com
2. Miscellaneous fixes, including a change to call_rcu()'s
rcu_head alignment check.
Hi,
On Sun, Nov 20, 2016 at 06:45:40PM +0800, Hao Zhang wrote:
> Changes the limited buswith to 8 bytes,and add
> the test in sun6i_dma_config function
>
> Accroding to sun6i dma driver, i think ,if the client
> doesn't configure the address width with dmaengine_slave_config
> function, it would
On 11/21/2016 04:03 PM, Tejun Heo wrote:
blkcg allocates some per-cgroup data structures with GFP_NOWAIT and
when that fails falls back to operations which aren't specific to the
cgroup. Occassional failures are expected under pressure and falling
back to non-cgroup operation is the right thing
On Mon, Nov 21, 2016 at 9:53 AM, Bjorn Helgaas wrote:
> On Wed, Nov 16, 2016 at 12:11:58PM -0600, Bjorn Helgaas wrote:
>> Hi Johannes,
>>
>> On Wed, Nov 02, 2016 at 04:35:52PM -0600, Johannes Thumshirn wrote:
>> > The Read Completion Boundary (RCB) bit must only be set on a device or
>> > endpoint
On Tue, 22 Nov 2016, Lee Jones wrote:
> On Mon, 21 Nov 2016, Milo Kim wrote:
>
> > AC and USB interrupts are related with external power input.
> > PB interrupt means push button pressed or released event.
> > Use better human readable definitions.
> >
> > Signed-off-by: Milo Kim
> > ---
> > a
On Tue, Nov 22, 2016 at 08:08:48PM +0800, Dongdong Liu wrote:
> The acpi_get_rc_resources() is used to get the RC register address that can
> not be described in MCFG. It takes the _HID&segment to look for and returns
> the RC address resource. Use PNP0C02 devices to describe such RC address
> reso
Actually only the mvneta_bm support is not 64-bits compatible.
The mvneta code itself can run on 64-bits architecture.
Signed-off-by: Gregory CLEMENT
---
drivers/net/ethernet/marvell/Kconfig | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/net/ethernet/marvell/Kconfi
Hi,
On mar., nov. 22 2016, Gregory CLEMENT
wrote:
> Actually only the mvneta_bm support is not 64-bits compatible.
> The mvneta code itself can run on 64-bits architecture.
I have just realized that my topic prefix was wrong (net-next was
missing), I am send a new email with the correct pref
On Mon, Nov 21, 2016 at 01:56:39PM -0800, Marc MERLIN wrote:
> On Mon, Nov 21, 2016 at 10:50:20PM +0100, Vlastimil Babka wrote:
> > > 4.9rc5 however seems to be doing better, and is still running after 18
> > > hours. However, I got a few page allocation failures as per below, but the
> > > system
On Tue, Nov 22, 2016 at 03:54:36PM +, Lee Jones wrote:
> On Tue, 22 Nov 2016, Lee Jones wrote:
>
> > On Mon, 14 Nov 2016, Charles Keepax wrote:
> >
> > > We have arizona_map_irq we might as well use it rather than hard coding
> > > it in several places.
> > >
> > > Signed-off-by: Charles Kee
Signed-off-by: Charles Keepax
---
drivers/mfd/arizona-irq.c | 21 +++--
1 file changed, 15 insertions(+), 6 deletions(-)
diff --git a/drivers/mfd/arizona-irq.c b/drivers/mfd/arizona-irq.c
index 724fa54..88729cf 100644
--- a/drivers/mfd/arizona-irq.c
+++ b/drivers/mfd/arizona-irq.
We have arizona_map_irq we might as well use it rather than hard coding
it in several places.
Signed-off-by: Charles Keepax
---
Changes since v1:
- Just a rebase
Thanks,
Charles
drivers/mfd/arizona-irq.c | 22 ++
1 file changed, 10 insertions(+), 12 deletions(-)
diff --g
As DCVDD will often be supplied by a child node of the MFD, we
can't call mfd_remove_devices as the first step in arizona_dev_exit
as might be expected (tidy up the children before we tidy up the
MFD). We need to disable and put the DCVDD regulator before we call
mfd_remove_devices, to prevent PM r
>
> Looks like there's a few similarly named devices and drivers. Mine is
> an SMSC LAN91C111 using the smc91x driver in
> drivers/net/ethernet/smsc/smc91x.c, rather than smc911x.c. So the
> interrupt handler is smc_interrupt()
>
> CONFIG_ARCH_PXA is not set, nor is SMC_USE_PXA_DMA or SMC_USE_DMA.
Hi Lorenzo
Thanks for reviewing
> -Original Message-
> From: Lorenzo Pieralisi [mailto:lorenzo.pieral...@arm.com]
> Sent: 22 November 2016 15:57
> To: liudongdong (C)
> Cc: helg...@kernel.org; a...@arndb.de; raf...@kernel.org;
> t...@semihalf.com; Wangzhou (B); pratyush.an...@gmail.com; l
Currently we leak a lot of things when tearing down the IRQs this patch
fixes this cleaning up both the IRQ mappings and the IRQ domain itself.
Signed-off-by: Charles Keepax
---
Changes since v3:
- Just included the other patches in the chain.
Thanks
Charles
drivers/mfd/arizona-irq.c | 59 ++
Timers IPs can be used to generate triggers for other IPs like
DAC, ADC or other timers.
Each trigger may result of timer internals signals like counter enable,
reset or edge, this configuration could be done through "master_mode"
device attribute.
A timer device could be triggered by other timers
Add bindings information for stm32 timer MFD
Signed-off-by: Benjamin Gaignard
---
.../devicetree/bindings/mfd/stm32-timer.txt| 53 ++
1 file changed, 53 insertions(+)
create mode 100644 Documentation/devicetree/bindings/mfd/stm32-timer.txt
diff --git a/Documentation
On 11/22/2016 05:06 PM, Marc MERLIN wrote:
> On Mon, Nov 21, 2016 at 01:56:39PM -0800, Marc MERLIN wrote:
>> On Mon, Nov 21, 2016 at 10:50:20PM +0100, Vlastimil Babka wrote:
4.9rc5 however seems to be doing better, and is still running after 18
hours. However, I got a few page allocation
On 19.11.2016 18:43, Quentin Lambert wrote:
> Most error branches following the call to pmcraid_get_free_cmd contain
> a call to pmcraid_return_cmd. This patch add these calls where they are
> missing.
>
> Moreover, most error branches following the call to class_create contain
> a call to class_de
Define bindings for stm32 IIO timer
Signed-off-by: Benjamin Gaignard
---
.../bindings/iio/timer/stm32-iio-timer.txt | 33 ++
1 file changed, 33 insertions(+)
create mode 100644
Documentation/devicetree/bindings/iio/timer/stm32-iio-timer.txt
diff --git a/Documentati
This driver add support for pwm driver on stm32 platform.
The SoC have multiple instances of the hardware IP and each
of them could have small differences: number of channels,
complementary output, counter register size...
To handle those variations each block have its own compatible
linked to inte
Hello Mike and others,
The autogroup feature that you added in 2.6.38 remains poorly
documented, so I took a stab at adding some text to the sched(7)
manual page. There are still a few pieces to be fixed, and you
may also see some other pieces that should be added. Could I
ask you to take a lo
Hi,
On Tue, Nov 22, 2016 at 04:31:51PM +0100, Nicolas Saenz Julienne wrote:
> > NAK. This is not ok for systems using multiple sbs-batteries.
> > Also please read:
>
> sorry I wasn't aware of that feature, I'll have a look at the
> whole thing and rework the patch.
no problem. I also reviewed the
From: Gregory CLEMENT
Date: Tue, 22 Nov 2016 17:00:37 +0100
> Actually only the mvneta_bm support is not 64-bits compatible.
> The mvneta code itself can run on 64-bits architecture.
>
> Signed-off-by: Gregory CLEMENT
No it cannot, it emits warnings because it casts pointers to and
from 32-bit
The following patches enable pwm and IIO Timer features for stm32 platforms.
Those two features are mixed into the registers of the same hardware block
(named timer) which lead to introduce a multifunctions driver on the top to
be able to share the registers.
In stm32 14 instances of timer hardwa
Hi Nicola,
I have a couple of comments.
On Mon, Nov 21, 2016 at 07:04:51PM +0100, Nicola Saenz Julienne wrote:
> This adds support for sbs-charger compilant chips as defined here:
> http://sbs-forum.org/specs/sbc110.pdf
Please add that link in the header of the driver.
>
> This was tested on a
On 11/22/2016 2:58 AM, Stephen Rothwell wrote:
> Hi James,
>
> I noticed that there are some commits in the security tree that have no
> Signed-off-by from the committer (Casey Schaufler).
>
My understanding is that patches I don't write should
be Acked, not Signed-off when I commit them. If this i
Define binding for pwm-stm32
Signed-off-by: Benjamin Gaignard
---
.../devicetree/bindings/pwm/pwm-stm32.txt | 43 ++
1 file changed, 43 insertions(+)
create mode 100644 Documentation/devicetree/bindings/pwm/pwm-stm32.txt
diff --git a/Documentation/devicetree/bindin
This hardware block could at used at same time for PWM generation
and IIO timer for other IPs like DAC, ADC or other timers.
PWM and IIO timer configuration are mixed in the same registers
so we need a MFD to be able to share those registers.
Signed-off-by: Benjamin Gaignard
---
drivers/mfd/Kcon
Hi!
I have only tested this on an 8-bit sx1502, so I'm uncertain if
the there needs to be locking for this to work as intended for
the bigger chips with an oscio pin? Probably.
So, I didn't add (or rather, removed) these lines at the end of
sx150x_gpio_set_multiple() and made the op optional inst
On Tue, Nov 22, 2016 at 12:48:50AM +0530, maitysancha...@gmail.com wrote:
> On 16-11-22 00:44:30, maitysancha...@gmail.com wrote:
> > This is not a resend of an applied patch. The whole series applies on
> > top of your topic/fsl-dspi branch and has fixes for the SPI DMA as
> > incremental changes
On 22 November 2016 at 16:31, Pali Rohár wrote:
> On Tuesday 22 November 2016 16:22:57 Michal Kazior wrote:
>> On 21 November 2016 at 16:51, Pali Rohár wrote:
>> > On Friday 11 November 2016 18:20:50 Pali Rohár wrote:
>> >> Hi! I will open discussion about mac address and calibration data for
>>
Add timers MFD and childs into DT for stm32f4.
Define and enable pwm1 and pwm3 for stm32f469 discovery board
Signed-off-by: Benjamin Gaignard
---
arch/arm/boot/dts/stm32f429.dtsi | 246 ++
arch/arm/boot/dts/stm32f469-disco.dts | 29
2 files changed, 275
Neil Armstrong writes:
> The Nexbox A95X exists with a Meson GXBB (S905) Soc or a Meson GXL SoC
> (S905X).
> Add the S905X variant which uses the internal PHY instead of an external PHY.
Missing SoB?
Kevin
On Tue 22-11-16 17:14:02, Vlastimil Babka wrote:
> On 11/22/2016 05:06 PM, Marc MERLIN wrote:
> > On Mon, Nov 21, 2016 at 01:56:39PM -0800, Marc MERLIN wrote:
> >> On Mon, Nov 21, 2016 at 10:50:20PM +0100, Vlastimil Babka wrote:
> 4.9rc5 however seems to be doing better, and is still running a
On Tue, 2016-11-22 at 15:52 +, David Howells wrote:
> Joe Perches wrote:
>
> > > > Small nit, checkpatch usually complains that this should be written as
> > > > 12-character SHA-1 followed by the commit subject, i.e.
> > > >
> > > > 0a637ee61247 ("x86/efi: Allow invocation of arbitrary boot
From: Zi Yan
From: Zi Yan
Since base page migration did not gain any speedup from
multi-threaded methods, we only accelerate the huge page case.
Signed-off-by: Zi Yan
Signed-off-by: Zi Yan
---
kernel/sysctl.c | 11 +++
mm/migrate.c| 6 ++
2 files changed, 17 insertions(+)
From: Zi Yan
From: Zi Yan
migrate_page_copy() and copy_huge_page() are affected.
Signed-off-by: Zi Yan
Signed-off-by: Zi Yan
---
fs/aio.c| 2 +-
fs/hugetlbfs/inode.c| 2 +-
fs/ubifs/file.c | 2 +-
include/linux/migrate.h | 6 --
mm/migrate.c|
From: Zi Yan
Hi all,
This patchset boosts the hugepage migration throughput and helps THP migration
which is added by Naoya's patches: https://lwn.net/Articles/705879/.
Motivation
===
In x86, 4KB page migrations are underutilizing the memory bandwidth compared
to 2M
From: Zi Yan
From: Zi Yan
No functionality is changed.
Signed-off-by: Zi Yan
Signed-off-by: Zi Yan
---
include/linux/migrate_mode.h | 6 +++---
mm/compaction.c | 20 ++--
mm/migrate.c | 14 +++---
3 files changed, 20 insertions(+), 20 de
Neil Armstrong writes:
> Following the Amlogic Linux kernel, it seem the only differences
> between the GXL and GXM SoCs are the CPU Clusters.
>
> This commit renames the gxl-s905d-p23x DTSI in a common file for
> S905D p23x and S912 q20x boards.
>
> Then adds a meson-gxm dtsi and reproduce the P
301 - 400 of 916 matches
Mail list logo