From: Colin Ian King
Fix trivial spelling mistake cant't -> can't and add KERN_WARNING to
printk messages. Remove redundant spaces before \n too (thanks to
Joe Perches for spotting those).
Signed-off-by: Colin Ian King
---
drivers/gpu/drm/amd/powerplay/smumgr/fiji_smc.c | 4 ++--
drivers
Kees Cook writes:
> On Mon, Oct 24, 2016 at 1:29 PM, Cyrill Gorcunov wrote:
>> On Mon, Oct 24, 2016 at 02:01:30PM -0500, Eric W. Biederman wrote:
>>> So I am probably going to tweak the !mm case so that instead of failing
>>> we perform the old capable check in that case. That seems the mot
>>>
The following changes since commit 1001354ca34179f3db924eb66672442a173147dc:
Linux 4.9-rc1 (2016-10-15 12:17:50 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git
tags/clk-fixes-for-linus
for you to fetch changes up to 91bbc174d45c347
On Mon, 2016-10-24 at 23:30 +0100, Colin King wrote:
> From: Colin Ian King
>
> Fix trivial spelling mistake cant't -> can't and add KERN_WARNING to
> printk messages.
trivia:
> diff --git a/drivers/gpu/drm/amd/powerplay/smumgr/fiji_smc.c
> b/drivers/gpu/drm/amd/powerplay/smumgr/fiji_smc.c
[]
On 10/24/2016 05:48 PM, David Lechner wrote:
Enable the DA8xx USB PHY driver by default. This driver used by several
davinci family devices.
Signed-off-by: David Lechner
---
arch/arm/configs/davinci_all_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/configs/davinci_all_
[cc list trimmed]
On Sun, Oct 23, 2016 at 05:37:42PM +0530, punnaiah choudary kalluri wrote:
> Hi Boris and Jason,
>
> I am doing rework on these patches to accommodate recent changes with
> respect to ooblayout. Also some of the comments that i have received
> from Boris as part of the arasan
On Mon, Oct 24, 2016 at 10:44:41PM +0200, Richard Weinberger wrote:
> That's a very good idea!
> Do we also have designated git tree for fscrypto?
> As soon UBIFS file encryption is mainline I'll have to monitor changes
> to fscrypto very closely because changes in fscrypto could introduce
> change
We have encountered some RMI4 firmwares where there are blank pages in between
PDT pages which contain functions. Add a device tree property which can be set
to force reading the first N pages.
Signed-off-by: Nick Dyer
---
Documentation/devicetree/bindings/input/rmi4/rmi_i2c.txt | 2 ++
drivers
Hi Bjorn,
On 10/24/2016 3:52 PM, Bjorn Helgaas wrote:
Hi Ray,
On Mon, Oct 24, 2016 at 03:17:00PM -0700, Ray Jui wrote:
This patch series contains various changes and fixes to the iProc PCIe
host driver. It also adds support for the next generation of PAXB and
PAXC based host controllers
This
Hi Ray,
On Mon, Oct 24, 2016 at 03:17:00PM -0700, Ray Jui wrote:
> This patch series contains various changes and fixes to the iProc PCIe
> host driver. It also adds support for the next generation of PAXB and
> PAXC based host controllers
>
> This patch series was developed based on v4.9-rc1 and
On 10/20, Viresh Kumar wrote:
> The OPP structure must not be used out of the rcu protected section.
> Cache the values to be used in separate variables instead.
>
> Signed-off-by: Viresh Kumar
Was this found by visual inspection or through some static
checker? Just curious.
> @@ -633,6 +634,14
On 10/20, Viresh Kumar wrote:
> On certain platforms (like TI), DVFS for a single device (CPU) requires
> configuring multiple power supplies.
>
> The OPP bindings already contains binding and example to explain this
> case, but it isn't sufficient. For example, there is no way for the code
> pars
Enable the DA8xx USB PHY driver by default. This driver used by several
davinci family devices.
Signed-off-by: David Lechner
---
arch/arm/configs/davinci_all_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/configs/davinci_all_defconfig
b/arch/arm/configs/davinci_all_defco
From: Colin Ian King
trivial fix to spelling mistake in dev_err message
Signed-off-by: Colin Ian King
---
drivers/net/ethernet/broadcom/bgmac.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/ethernet/broadcom/bgmac.c
b/drivers/net/ethernet/broadcom/bgmac.c
ind
FWIW, this thread ends up in the spam folder for me also on my private
e-mail account. And it's not the only Broadcom thread. Quite a few
Broadcom e-mails end up there. The thread was sent to me via
infradead.org. My private e-mail is also hosted by Gmail.
I get this:
SPF: PASS with IP 2001:1868:
On Mon, Oct 24, 2016 at 1:46 PM, Linus Torvalds
wrote:
> On Mon, Oct 24, 2016 at 1:06 PM, Andy Lutomirski wrote:
>>>
>>> [69943.450108] Oops: 0003 [#1] PREEMPT SMP DEBUG_PAGEALLOC
>>
>> This is an unhandled kernel page fault. The string "Oops" is so helpful :-/
>
> I think there was a line above
From: Colin Ian King
trivial fix to spelling mistake in printk debug message
Signed-off-by: Colin Ian King
---
arch/ia64/kernel/err_inject.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/ia64/kernel/err_inject.c b/arch/ia64/kernel/err_inject.c
index 5ed0ea9..a18e0b4
Hi Joel,
Ha, finally someone beat me to submitting my driver,
I had an ugly hack to bitbang the SPI since I couldn't figure
out a good way to assert the creset after the CS.
Thanks!
On Mon, Oct 24, 2016 at 04:55:43PM -0500, atull wrote:
> On Mon, 24 Oct 2016, Joel Holdsworth wrote:
>
> > The La
On 10/24/2016 3:30 PM, Scott Branden wrote:
Looks fine other than spelling mistakes in some commit messages.
Acked-by: Scott Branden
Thanks, Scott. I will address those in the next revision of patchset.
But would like to get some comments from Bjorn before sending out the
next patchset.
From: Colin Ian King
Fix trivial spelling mistake cant't -> can't and add KERN_WARNING to
printk messages.
Signed-off-by: Colin Ian King
---
drivers/gpu/drm/amd/powerplay/smumgr/fiji_smc.c | 4 ++--
drivers/gpu/drm/amd/powerplay/smumgr/iceland_smc.c | 4 ++--
drivers/gpu/drm/amd/powerpl
Looks fine other than spelling mistakes in some commit messages.
Acked-by: Scott Branden
On 16-10-24 03:17 PM, Ray Jui wrote:
This patch series contains various changes and fixes to the iProc PCIe
host driver. It also adds support for the next generation of PAXB and
PAXC based host controllers
On Mon, Oct 10, 2016 at 10:13 AM, Hoan Tran wrote:
> SMBus block command uses the first byte of buffer for the data length.
> The dma_buffer should be increased by 1 to avoid the overrun issue.
>
> Reported-by: Phil Endecott
> Signed-off-by: Hoan Tran
> ---
> drivers/i2c/busses/i2c-xgene-slimpr
On Mon, Oct 24, 2016 at 10:59:24PM +0200, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Mon, 24 Oct 2016 22:08:47 +0200
>
> * Multiplications for the size determination of memory allocations
> indicated that array data structures should be processed.
> Thus use the corresponding fun
Thanks! Will address both typos in the next revision. Waiting for
feedback from Bjorn before sending out the next revision.
Ray
On 10/24/2016 3:24 PM, Scott Branden wrote:
2 spelling typos
On 16-10-24 03:17 PM, Ray Jui wrote:
Remove the following outbound related device tree properties:
brcm
Hi all,
In today's device-mapper tree
(git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git#for-next)
I noticed that commit
a6e3a623e7d9 ("dm cache metadata: DM_CACHE_FEATURE_INCOMPAT_SEP_DIRTY_BITS")
has no Signed-off-by tags.
--
Cheers,
Stephen Rothwell
On 24/10/16 23:20, Joe Perches wrote:
> On Mon, 2016-10-24 at 15:13 -0700, Kees Cook wrote:
>> On Mon, Oct 24, 2016 at 3:02 PM, Colin King wrote:
>>> From: Colin Ian King
>>>
>>> trivial fix to spelling mistake in pr_debug message
>>>
>>> Signed-off-by: Colin Ian King
>>> ---
>>> arch/powerpc/p
2 spelling typos
On 16-10-24 03:17 PM, Ray Jui wrote:
Remove the following outbound related device tree properties:
brcm,pcie-ob-window-size
brcm,pcie-ob-oarr-size
The above two prperties are a bit duplicated in functions. In addition,
properties typo
the next generation iProc PCIe controller
On Monday, October 24, 2016 12:30:47 PM CEST Chris Metcalf wrote:
> On 10/21/2016 4:33 PM, Yury Norov wrote:
> > All new 32-bit architectures should have 64-bit off_t type, but existing
> > architectures has 32-bit ones.
> >
> > [...]
> > For syscalls sys_openat() and sys_open_by_handle_at() force_
Hi Maxime,
In today's sunxi tree
(git://git.kernel.org/pub/scm/linux/kernel/git/mripard/linux.git#sunxi/for-next)
I noticed that commit
3861b711f8b5 ("ARM: sun5i: chip: add a node for the w1 gpio controller")
has no Signed-off-by from its committer.
--
Cheers,
Stephen Rothwell
Remove the following outbound related device tree properties:
brcm,pcie-ob-window-size
brcm,pcie-ob-oarr-size
The above two prperties are a bit duplicated in functions. In addition,
the next generation iProc PCIe controller has outbound mapping window that
supports more than just two sizes, which
On 10/24/2016 06:34 PM, Cyrille Pitchen wrote:
> This patch adds support to the SST sst26* QSPI memories.
> It also adds a new SST_BLOCK_PROTECT flag so spi_nor_scan() sends
> a SST Global Block Protection Unlock (98h) command once for all
> otherwise later Sector Erase and Page Program commands wo
On Mon, 2016-10-24 at 15:13 -0700, Kees Cook wrote:
> On Mon, Oct 24, 2016 at 3:02 PM, Colin King wrote:
> > From: Colin Ian King
> >
> > trivial fix to spelling mistake in pr_debug message
> >
> > Signed-off-by: Colin Ian King
> > ---
> > arch/powerpc/platforms/pseries/hotplug-cpu.c | 2 +-
>
This patch adds the support of inbound mapping to the iProc PCIe driver.
The range of the inbound mapping is configured by the optional device
tree property 'dma-ranges'.
While inbound mapping is done automatically in the ASIC on most iProc
based SoCs, newer ASIC (e.g., Stingray) requires inbound
On 10/24/2016 06:34 PM, Cyrille Pitchen wrote:
> This patch adds an entry in the spi_nor_ids[] table to add support
> to the Macronix mx66l1g45g.
>
> Signed-off-by: Cyrille Pitchen
> ---
> drivers/mtd/spi-nor/spi-nor.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/mtd/spi-nor
Improve the iProc PCIe outbound mapping code by making it more generic
and removing redundant device tree properties
'brcm,pcie-ob-window-size' and 'brcm,pcie-ob-oarr-size'. The driver is
still backward compatible to device tree binaries with the two
properties specified
The driver now automatical
Add support for the second generation of the iProc PCIe PAXC host
controller to the iProc PCIe host driver
Signed-off-by: Ray Jui
Reviewed-by: Anup Patel
Reviewed-by: Scott Branden
---
drivers/pci/host/pcie-iproc-platform.c | 3 +
drivers/pci/host/pcie-iproc.c | 176
Add description for optional device tree property 'dma-ranges' for
inbound mapping
Signed-off-by: Oza Oza
Signed-off-by: Ray Jui
Reviewed-by: Scott Branden
---
Documentation/devicetree/bindings/pci/brcm,iproc-pcie.txt | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Documentation/devicet
On 10/24/2016 06:34 PM, Cyrille Pitchen wrote:
> This patch provides an alternative mean to support memory above 16MiB
> (128Mib) by replacing 3byte address op codes by their associated 4byte
> address versions.
>
> Using the dedicated 4byte address op codes doesn't change the internal
> state of
On 10/24/2016 06:34 PM, Cyrille Pitchen wrote:
> Before this patch, m25p80_read() supported few SPI protocols:
> - regular SPI 1-1-1
> - SPI Dual Output 1-1-2
> - SPI Quad Output 1-1-4
> On the other hand, all other m25p80_*() hooks only supported SPI 1-1-1.
>
> This patch adds support to all curr
This patch adds the support for the next generation of the iProc PAXB
host controller, used in Stingray
Signed-off-by: Oza Oza
Signed-off-by: Ray Jui
Reviewed-by: Scott Branden
---
drivers/pci/host/pcie-iproc-platform.c | 3 +
drivers/pci/host/pcie-iproc.c | 128
Add new compatible string "brcm,iproc-pcie-paxc-v2" to the iProc
PCIe device tree binding document. "brcm,iproc-pcie-paxc-v2" is for the
second generation of the Broadcom iProc PCIe PAXC host controller
Also updated the binding document with more detailed description of
each compatible string and
During enumeration with multi-function EP devices, access to the
configuration space of a non-exist function results in an unsupported
request being returned as expected. By default the PAXB based iProc
PCIe controller forwards this as an APB error to the host system and
that causes an exception, w
The iProc PCIe driver is currently using type IPROC_PCIE_PAXB for
the following SoCs: NS, NSP, Cygnus, NS2, and Pegasus. In fact, the BCMA
based NS uses a legacy PAXB controller that is slightly different from
the PAXB controller used in the rest of SoCs, e.g., some registers are
missing and it doe
Add new compatible string 'brcm,iproc-pcie-paxb-v2', for the next
generation of the iProc PAXB PCIe host controller
Signed-off-by: Oza Oza
Signed-off-by: Ray Jui
Reviewed-by: Scott Branden
---
Documentation/devicetree/bindings/pci/brcm,iproc-pcie.txt | 2 ++
1 file changed, 2 insertions(+)
di
This patch series contains various changes and fixes to the iProc PCIe
host driver. It also adds support for the next generation of PAXB and
PAXC based host controllers
This patch series was developed based on v4.9-rc1 and tested on both NS2
SVK and Cygnus wireless audio platform
repo: https://gi
During initialization, the current iProc PCIe host driver resets PAXC
and the downstream internal endpoint device that PAXC connects to. If
the endpoint device is already loaded with firmware and has started
running from the bootloader stage, this downstream reset causes the
endpoint device to stop
As the number of iProc PCIe core registers starts to grow and differ
between different revisions of the iProc PCIe controllers, the
current way of populating each individual unsupported register with
value 'IPROC_PCIE_REG_INVALID' with a table entry has become a bit
messy and is difficult to scale
On Mon, Oct 24, 2016 at 3:02 PM, Colin King wrote:
> From: Colin Ian King
>
> trivial fix to spelling mistake in pr_debug message
>
> Signed-off-by: Colin Ian King
> ---
> arch/powerpc/platforms/pseries/hotplug-cpu.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/
From: Colin Ian King
trivial fix to spelling mistake in ecryptfs_printk message
Signed-off-by: Colin Ian King
---
fs/ecryptfs/keystore.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/ecryptfs/keystore.c b/fs/ecryptfs/keystore.c
index 11d39ab..4bd9099 100644
--- a/fs/ec
On 10/24/2016 06:34 PM, Cyrille Pitchen wrote:
> The patch checks whether the Quad Enable bit is already set in the Status
> Register. If so, the function exits immediately with a successful return
> code. Otherwise, a message is now printed telling we're setting the
> non-volatile bit.
>
> Signed
Hi Masahiro,
On 24.10.2016 10:43, Masahiro Yamada wrote:
> Sylvain Lemieux reports the LPC32xx GPIO driver is broken since
> commit 762c2e46c059 ("gpio: of: remove of_gpiochip_and_xlate() and
> struct gg_data"). Probably, gpio-etraxfs.c and gpio-davinci.c are
> broken as well.
>
> Those drivers
On 10/24/2016 05:50 PM, Linus Torvalds wrote:
On Mon, Oct 24, 2016 at 2:17 PM, Linus Torvalds
wrote:
The vmalloc/vfree code itself is a bit scary. In particular, we have a
rather insane model of TLB flushing. We leave the virtual area on a
lazy purge-list, and we delay flushing the TLB and act
From: Colin Ian King
trivial fix to spelling mistake in pr_debug message
Signed-off-by: Colin Ian King
---
arch/powerpc/platforms/pseries/hotplug-cpu.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/powerpc/platforms/pseries/hotplug-cpu.c
b/arch/powerpc/platforms/pse
On Mon, 24 Oct 2016, Joel Holdsworth wrote:
> The Lattice iCE40 is a family of FPGAs with a minimalistic architecture
> and very regular structure, designed for low-cost, high-volume consumer
> and system applications.
>
> This patch adds support to the FPGA manager for configuring the SRAM of
>
Port firmware update code from Samsung Galaxy S7 driver into
mainline framework.
This patch has been tested on Synaptics S7813.
Signed-off-by: Nick Dyer
---
drivers/input/rmi4/Makefile |2 +-
drivers/input/rmi4/rmi_driver.c | 56 +-
drivers/input/rmi4/rmi_f34.c| 53 +-
drivers/i
Hi-
Please find attached patches to add F34 firmware update to the RMI4
driver.
Changes in v5:
- Improve split between for different versions (req. Bjorn Andersson)
- Address a couple of kbuild test robot issues
- Fix a bug with configuration ID on V7
Changes in v4:
- Add support for v7 bootload
The status is the percentage complete, or once complete, zero for
success or a negative return code.
Signed-off-by: Nick Dyer
---
drivers/input/rmi4/rmi_f34.c | 34 ++
drivers/input/rmi4/rmi_f34.h | 4
drivers/input/rmi4/rmi_f34v7.c | 14 ++
Signed-off-by: Nick Dyer
---
drivers/input/rmi4/rmi_bus.c| 3 +++
drivers/input/rmi4/rmi_driver.c | 1 +
2 files changed, 4 insertions(+)
diff --git a/drivers/input/rmi4/rmi_bus.c b/drivers/input/rmi4/rmi_bus.c
index ef8c747..3c6a1b5 100644
--- a/drivers/input/rmi4/rmi_bus.c
+++ b/drivers/in
Signed-off-by: Nick Dyer
---
drivers/input/rmi4/rmi_driver.h | 1 +
drivers/input/rmi4/rmi_f01.c| 24 +++-
drivers/input/rmi4/rmi_f34.c| 16
3 files changed, 40 insertions(+), 1 deletion(-)
diff --git a/drivers/input/rmi4/rmi_driver.h b/drivers/input
Add support for updating firmware, triggered by a sysfs attribute.
This patch has been tested on Synaptics S7300.
Signed-off-by: Nick Dyer
Tested-by: Chris Healy
---
drivers/input/rmi4/Kconfig | 11 +
drivers/input/rmi4/Makefile | 1 +
drivers/input/rmi4/rmi_bus.c| 3 +
drive
Signed-off-by: Nick Dyer
---
drivers/input/rmi4/rmi_driver.c | 2 +-
drivers/input/rmi4/rmi_driver.h | 5 +-
drivers/input/rmi4/rmi_f01.c| 23 -
drivers/input/rmi4/rmi_f34.c| 110
4 files changed, 137 insertions(+), 3 deletions(-)
dif
On Mon, Oct 24, 2016 at 2:27 PM, Florian Fainelli wrote:
>
> Should we compare the headers added by lists.infradead.org
So for me, it didn't go through infraded.org, but I got it through the
kernel mailing list.
I'll send you the raw email data in private, you can compare it
against your good on
Signed-off-by: Nick Dyer
Signed-off-by: Benjamin Tissoires
---
drivers/input/rmi4/rmi_driver.c | 139 +---
1 file changed, 86 insertions(+), 53 deletions(-)
diff --git a/drivers/input/rmi4/rmi_driver.c b/drivers/input/rmi4/rmi_driver.c
index 4a88312..63c9e22
On Mon, Oct 24, 2016 at 2:17 PM, Linus Torvalds
wrote:
>
> The vmalloc/vfree code itself is a bit scary. In particular, we have a
> rather insane model of TLB flushing. We leave the virtual area on a
> lazy purge-list, and we delay flushing the TLB and actually freeing
> the virtual memory for it
On Mon, Oct 24, 2016 at 02:52:35PM +0100, Sean Young wrote:
> On Fri, Oct 21, 2016 at 10:55:40AM -0500, Nathan Zimmer wrote:
> > It didn't seem to make a difference as far as output.
> > Did I miss a config option? or something else?
> >
> > [0.00] Linux version 3.6.0 (root@r1i2n0) (gcc ve
On Monday 24 October 2016 23:41:52 Pavel Machek wrote:
> On Mon 2016-10-24 14:29:33, Tony Lindgren wrote:
> > Also, the shutdown voltage can depend on external devices
> > connected. It could be for example 3.3V depending on eMMC on some
> > devices while devices with no eMMC could have it at 3.0V.
On Mon, 24 Oct 2016, Linus Torvalds wrote:
> The one I'm *currently* testing seems to work for me, but that's
> because I moved the timer into klogd and that just avoids the issue.
>
> But I'll attach my old patch just for your testing pleasure.
Of course it does not trigger... I probably need to
On Tue, 25 Oct 2016 02:57:58 +0530
Kirti Wankhede wrote:
> On 10/21/2016 12:54 AM, Alex Williamson wrote:
> > On Tue, 18 Oct 2016 02:52:05 +0530
> > Kirti Wankhede wrote:
> >
> >> Vendor driver using mediated device framework should use
> >> vfio_info_add_capability() to add capabilities.
> >
On Mon, Oct 24, 2016 at 2:27 PM, Jarod Wilson wrote:
>
> Yes and no. What are these non-git people doing with the patches? Since
> patch won't apply them, are they just reading them for personal
> enlightenment?
Oh, patch applies them fine.
They might end up not seeing some of the updates to bin
On Mon 2016-10-24 14:29:33, Tony Lindgren wrote:
> * Pavel Machek [161024 14:24]:
> > Hi!
> >
> > What about something like this? N900 will drain the battery down to
> > system crash, which is quite uncool.
>
> Can't we make that generic and configurable for the voltage somehow?
I was afraid so
gcc warns about an uninitialized pointer dereference in the vlan
priority handling:
net/core/flow_dissector.c: In function '__skb_flow_dissect':
net/core/flow_dissector.c:281:61: error: 'vlan' may be used uninitialized in
this function [-Werror=maybe-uninitialized]
As pointed out by Jiri Pirko,
On Tue, 25 Oct 2016 02:52:39 +0530
Kirti Wankhede wrote:
> On 10/21/2016 12:54 AM, Alex Williamson wrote:
> > On Tue, 18 Oct 2016 02:52:06 +0530
> > Kirti Wankhede wrote:
> >
> >> Update msix_sparse_mmap_cap() to use vfio_info_add_capability()
> >> Update region type capability to use vfio_in
On Mon, Oct 24, 2016 at 1:29 PM, Cyrill Gorcunov wrote:
> On Mon, Oct 24, 2016 at 02:01:30PM -0500, Eric W. Biederman wrote:
>> So I am probably going to tweak the !mm case so that instead of failing
>> we perform the old capable check in that case. That seems the mot
>> certain way to avoid regr
On 10/24/2016 02:43 AM, Masahiro Yamada wrote:
Sylvain Lemieux reports the LPC32xx GPIO driver is broken since
commit 762c2e46c059 ("gpio: of: remove of_gpiochip_and_xlate() and
struct gg_data"). Probably, gpio-etraxfs.c and gpio-davinci.c are
broken as well.
Those drivers register multiple gpi
* Pavel Machek [161024 14:24]:
> Hi!
>
> What about something like this? N900 will drain the battery down to
> system crash, which is quite uncool.
Can't we make that generic and configurable for the voltage somehow?
Also, the shutdown voltage can depend on external devices connected.
It could
On 10/21/2016 12:54 AM, Alex Williamson wrote:
> On Tue, 18 Oct 2016 02:52:05 +0530
> Kirti Wankhede wrote:
>
>> Vendor driver using mediated device framework should use
>> vfio_info_add_capability() to add capabilities.
>> Introduced this function to reduce code duplication in vendor drivers.
On Mon, Oct 24, 2016 at 02:10:30PM -0700, Linus Torvalds wrote:
> On Mon, Oct 24, 2016 at 2:02 PM, Josh Boyer wrote:
> >
> > The benefit of tarballs and patches from a distribution standpoint is
> > purely size.
>
> I wonder if you wouldn't be better off just generating your own diffs.
>
> If yo
On 10/24/2016 01:14 PM, Linus Torvalds wrote:
> On Mon, Oct 24, 2016 at 12:54 PM, Florian Fainelli
> wrote:
>>
>> The older setup was using smtphost.broadcom.com which we have now
>> documented as being invalid, here Jonathan used gmail directly (since
>> that's our mail provider now):
>>
>> Rece
Hi Boris,
> On Sun, 23 Oct 2016 23:45:40 +0200
> Lukasz Majewski wrote:
>
> > This patch set brings atomic operation to i.MX's PWMv2 driver.
> >
> > This work has been supported and suggested by Boris Brezillon [1]
> > and Stefan Agner, by showing how simple the transition could be :-).
> >
>
On Sat, Jul 09, 2016 at 11:58:03AM +0200, Pali Rohár wrote:
> On Friday 08 July 2016 23:37:54 Dmitry Torokhov wrote:
> > On Thu, Jul 07, 2016 at 01:41:01PM +0200, Pali Rohár wrote:
> > > On Tuesday 21 June 2016 13:27:30 Pali Rohár wrote:
> > > > On Monday 20 June 2016 17:31:13 Dmitry Torokhov wrote
Hi!
What about something like this? N900 will drain the battery down to
system crash, which is quite uncool.
Pavel
diff --git a/drivers/power/supply/bq27xxx_battery.c
b/drivers/power/supply/bq27xxx_battery.c
index 0fe278b.
On 10/21/2016 12:54 AM, Alex Williamson wrote:
> On Tue, 18 Oct 2016 02:52:06 +0530
> Kirti Wankhede wrote:
>
>> Update msix_sparse_mmap_cap() to use vfio_info_add_capability()
>> Update region type capability to use vfio_info_add_capability()
>> Can't split this commit for MSIx and region_type
Hi Boris,
> On Mon, 24 Oct 2016 17:28:52 +0200
> Boris Brezillon wrote:
>
> > On Sun, 23 Oct 2016 23:45:46 +0200
> > Lukasz Majewski wrote:
> >
> > > The need for set_polarity() function has been removed by
> > > implementing PWM atomic support (apply() callback).
> > >
> > > To indicate that
On 10/24/2016 02:50 PM, David Lechner wrote:
On 10/24/2016 10:50 AM, David Lechner wrote:
On 10/24/2016 06:58 AM, Sekhar Nori wrote:
On Saturday 22 October 2016 12:06 AM, David Lechner wrote:
+&ehrpwm1 {
+status = "disabled";
Hmm, disabled? Can you add this node when you actually use it
On Mon, Oct 24, 2016 at 1:46 PM, Linus Torvalds
wrote:
>
> So this is all some really subtle code, but I'm not seeing that it
> would be wrong.
Ahh... Except maybe..
The vmalloc/vfree code itself is a bit scary. In particular, we have a
rather insane model of TLB flushing. We leave the virtual a
On Mon, Oct 24, 2016 at 2:02 PM, Josh Boyer wrote:
>
> The benefit of tarballs and patches from a distribution standpoint is
> purely size.
I wonder if you wouldn't be better off just generating your own diffs.
If you know the other end uses "git apply", then not only can you use
"--binary", but
On Mon, Oct 24, 2016 at 03:23:06PM -0400, Philippe Proulx wrote:
> This patch removes the need to manually update the static size of
> data.array in struct ctf_writer.
>
> Signed-off-by: Philippe Proulx
Acked-by: Jiri Olsa
thanks,
jirka
> ---
> tools/perf/util/data-convert-bt.c | 65
> +
From: Rafael J. Wysocki
The only times at which intel_pstate checks the policy set for
a given CPU is the initialization of that CPU and updates of its
policy settings from cpufreq when intel_pstate_set_policy() is
invoked.
That is insufficient, however, because intel_pstate uses the same
P-stat
Hi Boris,
> On Sun, 23 Oct 2016 23:45:42 +0200
> Lukasz Majewski wrote:
>
> > The software reset code has been extracted from imx_pwm_config_v2
> > function and moved to new one - imx_pwm_sw_reset().
> >
> > This change reduces the overall size of imx_pwm_config_v2() and
> > prepares it for ato
On Mon, Oct 24, 2016 at 3:24 PM, Linus Torvalds
wrote:
> On Mon, Oct 24, 2016 at 11:25 AM, Jarod Wilson wrote:
>> It's entirely possible that we (Red Hat and the Fedora kernel team) are
>> doing something wrong here, but to the best of our knowledge, it seems
>> that the canonical upstream RC sna
From: Markus Elfring
Date: Mon, 24 Oct 2016 22:44:02 +0200
Move the assignment for the data structure members "isoc_copy"
and "num_bufs" behind the source code for memory allocations
by this function.
Signed-off-by: Markus Elfring
---
drivers/media/usb/au0828/au0828-video.c | 5 ++---
1 file c
Hi Jingoo,
> On Saturday, October 22, 2016, Lukasz Majewski wrote:
> >
> > The commit: a55944ca82d287ca099ca90413af857af9086773 has posed some
> > extra
>
> Please add the subject of the patch, in order to let people know
> which patch you mention exactly. Please loot at other commits that
> fix
From: Markus Elfring
Date: Mon, 24 Oct 2016 22:28:03 +0200
Omit extra messages for a memory allocation failure in this function.
Link:
http://events.linuxfoundation.org/sites/events/files/slides/LCJ16-Refactor_Strings-WSang_0.pdf
Signed-off-by: Markus Elfring
---
drivers/media/usb/au0828/au08
From: Markus Elfring
Date: Mon, 24 Oct 2016 22:08:47 +0200
* Multiplications for the size determination of memory allocations
indicated that array data structures should be processed.
Thus use the corresponding function "kcalloc".
This issue was detected by using the Coccinelle software.
From: Markus Elfring
Date: Mon, 24 Oct 2016 22:52:10 +0200
A few update suggestions were taken into account
from static source code analysis.
Markus Elfring (3):
Use kcalloc()
Delete three error messages for a failed memory allocation
Move two assignments
drivers/media/usb/au0828/au0828-
> On Oct 23, 2016, at 11:02 PM, Mugunthan V N wrote:
>
> Increase ADC reference clock from 3MHz to 24MHz so that the
> sampling rates goes up from 100K samples per second to 800K
> samples per second on AM335x and AM437x SoC.
>
> Also increase opendelay for touchscreen configuration to
> equali
This gets rid of oddities such as:
perf bench futex hash -t -4
perf: calloc: Cannot allocate memory
Runtime (and many more) are equally busted, ie run for bogus amounts
of time. Just use the abs, instead of, for example erroring out.
Signed-off-by: Davidlohr Bueso
---
tools/perf/bench/futex-ha
Hi Arnaldo, here's the requested patch that gets rid of the struct alignment
tackling the main source of cacheline bouncing. In addition a small fix to
bogus inputs.
Thanks!
Davidlohr Bueso (2):
perf/bench-futex: Avoid worker cacheline bouncing
perf/bench-futex: Sanitize numeric parameters
Sebastian noted that overhead for worker thread ops (throughput)
accounting was producing 'perf' to appear in the profiles, consuming
a non-trivial (ie 13%) amount of CPU. This is due to cacheline
bouncing due to the increment of w->ops. We can easily fix this by
just working on a local copy and up
After enabling -Wmaybe-uninitialized warnings, we get a false-postive
warning for shmem:
mm/shmem.c: In function ‘shmem_getpage_gfp’:
include/linux/spinlock.h:332:21: error: ‘info’ may be used uninitialized in
this function [-Werror=maybe-uninitialized]
This can be easily avoided, since the corr
201 - 300 of 1098 matches
Mail list logo
