For the vmwgfx part:
Acked-by: Thomas Hellstrom
On 11/05/2016 08:33 AM, Eric Engestrom wrote:
> Fixes: 90844f00049e9f42573fd31d7c32e8fd31d3fd07
>
> drm: make drm_get_format_name thread-safe
>
> Signed-off-by: Eric Engestrom
> [danvet: Clarify that the returned pointer must be freed
On Sat, Nov 05, 2016 at 11:12:00AM +0800, Chao Yu wrote:
> On 2016/11/5 6:53, Jaegeuk Kim wrote:
> > On Fri, Nov 04, 2016 at 04:30:09PM +0800, Chao Yu wrote:
> >> On 2016/11/4 2:02, Jaegeuk Kim wrote:
> >>> On Fri, Nov 04, 2016 at 12:26:56AM +0800, Chao Yu wrote:
> From: Chao Yu
>
>
On Sat, Nov 05, 2016 at 10:44:07AM +0800, Chao Yu wrote:
> On 2016/10/20 10:26, Jaegeuk Kim wrote:
> > Change log from v1:
> > o avoid performance regression
> >
> >>From b34a3d3c4c3fa2d6e000acc99bc5216a247bd6cb Mon Sep 17 00:00:00 2001
> > From: Jaegeuk Kim
> > Date: Fri, 14 Oct 2016 11:51:23 -
On Wed, Nov 02, 2016 at 01:00:03PM -0500, Frank Li wrote:
> i.MX6QP added new reigster bit PROFILE_SEL in MADPCR0.
s/reigster/register
> need set it at perf start.
>
> Signed-off-by: Frank Li
We probably need a 'for' in patch subject after 'support'?
> ---
> V1 to V2: remove fsl_mmdc_devtype
On 11/02/2016 06:13 PM, Masahiro Yamada wrote:
> The probe function calls pci_request_regions(), but I do not see
> corresponding pci_release_regions() calls.
>
> While we are here, rename the jump labels to follow the guideline
> "Choose label names which say what the goto does" suggested by
> Do
On 11/03/2016 12:39 PM, Sandeep Jain wrote:
> Dear Maintainers,
> Requesting for your attention for patch review/merge.
>
> Thanks & Regards,
> Sandeep Jain
>
> On Thu, Aug 04, 2016 at 07:46:33PM +0530, Sandeep Jain wrote:
>> From: Vladimir Zapolskiy
>>
>> The change controls module users
On 11/03/2016 12:34 PM, Sandeep Jain wrote:
> Dear Maintainers,
> This patch is reviewed by Richard.
> Requesting for Maintainer's attention for patch merge.
>
> Thanks & Regards,
> Sandeep Jain
>
> On Sat, Sep 17, 2016 at 04:41:47PM +0200, Richard Weinberger wrote:
>> On Thu, Aug 4, 2016 at 4:
On 11/02/2016 06:21 PM, Masahiro Yamada wrote:
> The denali_dt_probe() calls clk_disable_unprepare() in the bailout
> path, whereas denali_dt_remove calls clk_disable(), inconsistently.
> Replace the latter with clk_disable_unprepare() to make sure to
> unprepare the clock.
>
> Signed-off-by: Masa
On 11/04/2016 11:42 AM, Masahiro Yamada wrote:
>
> nand_scan(), nand_scan_ident(), nand_scan_tail() return
> an appropriate negative value on error.
>
> Most of drivers return the value from them on error,
> but some of them return the fixed error code -ENXIO
> (and a few return -ENODEV).
>
> Th
On Wed, Nov 02, 2016 at 01:00:04PM -0500, Frank Li wrote:
> mmdc of i.MX6QP are little difference with i.MX6Q.
> added new compatible stream fsl,imx6qp-mmdc
s/stream/string
>
> Signed-off-by: Frank Li
> ---
> No change for this patch.
> suspend resume code need fsl,imx6q-mmdc
You should probab
Usually the memory of android phones is very small, so after a long
running, the fragment is very large. Kernel stack which called by
alloc_thread_stack_node() usually alloc 16K memory, and it failed
frequently.
However we have CONFIG_VMAP_STACK now, but it do not support arm64,
and maybe it has s
Add soc a64 dma support.
Signed-off-by: Hao Zhang
---
drivers/dma/sun6i-dma.c | 19 +++
1 file changed, 19 insertions(+)
diff --git a/drivers/dma/sun6i-dma.c b/drivers/dma/sun6i-dma.c
index 8346199..00fcfc7 100644
--- a/drivers/dma/sun6i-dma.c
+++ b/drivers/dma/sun6i-dma.c
@@ -1
Hi,
This patch add the allwinner soc a64 dma support on already done driver
sun6i-dma.
A64 is a 64bit SOC, it has 8 channel DMA which flexible
data width of 8/16/32/64-bit. Detailed info about it is on
Allwinner_A64_User_Manual_V1.0 page 196 and A64_Datasheet_V1.1 page 8.
Due to the patch of c
Hi Laurent,
Thanks for your prompt reply. I will fix them in patch v4.
On Sat, 2016-11-05 at 01:32 +0200, Laurent Pinchart wrote:
> Hi Rick,
>
> Thank you for the patch.
>
> On Friday 04 Nov 2016 13:51:18 Rick Chang wrote:
> > Add a DT binding documentation for Mediatek JPEG Decoder of
> > MT27
On Wed, Nov 2, 2016 at 9:37 AM, Richard Vidal-Dorsch
wrote:
> Signed-off-by: Richard Vidal-Dorsch
> +#include
> +#include
#include
should be enough.
> +#include
> +#include
> +#include
> +#include
> +#include
> +
> +#define EC_GPIOF_DIR_OUT BIT(6)
> +#define EC_GPIOF_DIR_IN
Hi!
> > 4.9-rc2 has bios_limit:
> >
> > pavel@duo:~$ cat /sys/devices/system/cpu/cpu0/cpufreq/bios_limit
> > 1833000
> >
> > and it has thermal zones:
> >
> > /sys/devices/virtual/thermal/thermal_zone0/trip_point_0_temp 127000
> > /sys/devices/virtual/thermal/thermal_zone0/trip_point_0_type cri
Both the field and the value are in registers, so they are not clear from
existing tracepoints.
Cc: Ladi Prosek
Signed-off-by: Paolo Bonzini
---
arch/x86/kvm/trace.h | 23 +++
arch/x86/kvm/vmx.c | 2 ++
arch/x86/kvm/x86.c | 1 +
3 files changed, 26 insertions(+)
diff
On 11/4/2016 7:30 PM, Jon Mason wrote:
Add support for the AMAC ethernet to the Broadcom Northstar2 SoC device
tree
Signed-off-by: Jon Mason
---
arch/arm64/boot/dts/broadcom/ns2-svk.dts | 5 +
arch/arm64/boot/dts/broadcom/ns2.dtsi| 12
2 files changed, 17 insertions(+)
dif
On Fri, Nov 04, 2016 at 04:51:23PM +0100, Neil Armstrong wrote:
> Add driver for the Internal RMII PHY found in the Amlogic Meson GXL SoCs.
>
> This PHY seems to only implement some standard registers and need some
> workarounds to provide autoneg values from vendor registers.
>
> Some magic valu
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media
tags/media/v4.9-3
For a series of fixup patches meant to fix the usage of DMA on stack,
plus one warning fixup.
---
PS.: I tried to send it earlier, but I was unable to send this patch series
from
return_io() resolves request_queue even if trace point isn't active:
static inline struct request_queue *bdev_get_queue(struct block_device *bdev)
{
return bdev->bd_disk->queue; /* this is never NULL */
}
static void return_io(struct bio_list *return_bi)
{
struct bio *bi;
On Fri, 2016-11-04 at 23:16 +0100, Pavel Machek wrote:
> Hi!
>
> >
> > I'd prefer mails over bugzilla for now...
> >
> > 4.9-rc2 has bios_limit:
> >
> > pavel@duo:~$ cat /sys/devices/system/cpu/cpu0/cpufreq/bios_limit
> > 1833000
> >
> > and it has thermal zones:
> >
> > /sys/devices/virtual/
On Tue, Nov 01, 2016 at 04:51:45PM -0700, Joshua Clayton wrote:
> imx-weim should always set address-cells to 2,
> and size_cells to 1.
> On imx6, fsl,weim-cs-gpr will always be &gpr
>
> Set these common parameters in the dtsi file,
> rather than in a downstream dts.
>
> Signed-off-by: Joshua Cla
On 03/11/2016 17:21, Dmitry Torokhov wrote:
On Tue, Nov 01, 2016 at 11:25:03AM +0100, Paul Cercueil wrote:
Right now, the gpio-keys driver is mostly used with EV_KEY event types.
However, this driver (and its devicetree bindings) support specifying
a different input type, like EV_ABS, even thoug
On Friday, 4 November 2016 14:22:17 GMT Hans de Goede wrote:
> Hi,
>
> On 04-11-16 13:30, Paul Burton wrote:
> > Hi Hans,
> >
> > On Friday, 4 November 2016 13:11:34 GMT Hans de Goede wrote:
> >> Hi All,
> >>
> >> While booting 4.9-rc# for the first time on an Allwinner A33 tablet,
> >> I notice
On Wed, Nov 02, 2016 at 08:58:38AM +0100, Marek Szyprowski wrote:
> Hi Greg,
>
>
> On 2016-10-31 18:47, Greg Kroah-Hartman wrote:
> > On Sun, Oct 30, 2016 at 05:22:13PM +0100, Rafael J. Wysocki wrote:
> > > Let me quote from the previous intro messages for this series first:
> > >
> > > > > Time
On Friday, 4 November 2016 14:22:17 GMT Hans de Goede wrote:
> Hi,
>
> On 04-11-16 13:30, Paul Burton wrote:
> > Hi Hans,
> >
> > On Friday, 4 November 2016 13:11:34 GMT Hans de Goede wrote:
> >> Hi All,
> >>
> >> While booting 4.9-rc# for the first time on an Allwinner A33 tablet,
> >> I notice
Hi!
> Under v4.8-rc, behaviour is different: bios_limit goes to 1GHz there
> when temperature is around 84C at the thermal zone. That keeps
> ibm/thermal temperatures under 90C, and no "thermal emergency"
> messages in syslog.
Argh. So v4.9 thermal management does not work.
v4.8 passive thermal
On 11/05/2016 01:27 PM, Xishi Qiu wrote:
> Usually the memory of android phones is very small, so after a long
> running, the fragment is very large. Kernel stack which called by
> alloc_thread_stack_node() usually alloc 16K memory, and it failed
> frequently.
>
> However we have CONFIG_VMAP_STACK
Implement mandatory export_operations, so it is possible to export befs via
nfs.
Signed-off-by: Luis de Bethencourt
---
Hi,
NFS exporting is a very useful feature. I implement here fh_to_dentry because
it is the mandatory member of struct export_operations, and fh_to_parent since
it is easy onc
On 05/11/16 12:42, Luis de Bethencourt wrote:
> Implement mandatory export_operations, so it is possible to export befs via
> nfs.
>
> Signed-off-by: Luis de Bethencourt
> ---
Forgot to add Richard.
Sorry Richard,
Luis
On 01/11/16 19:58, Lars-Peter Clausen wrote:
> On 11/01/2016 05:03 AM, Matt Ranostay wrote:
>> On Mon, Oct 31, 2016 at 10:04 AM, Eva Rachel Retuya
>> wrote:
>>> The name passed to devm_regulator_get() should match the name of the
>>> supply as specified in the device datasheet. This makes it clea
Sebastian Frias writes:
> Commit a999589ccaae ("phylib: add RGMII-ID interface mode definition")
> and commit 7d400a4c5897 ("phylib: add PHY interface modes for internal
> delay for tx and rx only") added several RGMII definitions:
> PHY_INTERFACE_MODE_RGMII_ID, PHY_INTERFACE_MODE_RGMII_RXID and
The ethtool api {get|set}_settings is deprecated.
We move this driver to new api {get|set}_link_ksettings.
Signed-off-by: Philippe Reynes
---
drivers/net/ethernet/adaptec/starfire.c | 14 --
1 files changed, 8 insertions(+), 6 deletions(-)
diff --git a/drivers/net/ethernet/adaptec
On 03/11/16 13:35, Srinivas Pandruvada wrote:
> On Thu, 2016-11-03 at 18:43 +0800, Ooi, Joyce wrote:
>> Sensitivity Percent Relative is added for ambient light sensor as it
>> is
>> used based on HID Sensor Usages specifications.
> The same patch is submitted by Song Hongyan
> . We may need new II
Hi!
> > So we seem to have thermal or ACPI regression in v4.9-rc3.
> >
> To me, there are two problems,
> the first one is a 4.9-rc regression that BIOS limit stops working,
> results in overheating because of high cpu frequency. I agree with
> Srinivas to check acpi_cpufreq driver code for this
Whoops,
one more:
---
From: Borislav Petkov
Date: Sat, 5 Nov 2016 12:47:03 +0100
Subject: [PATCH] x86/MCE: Remove MCP_TIMESTAMP
MCP_TIMESTAMP controls whether current TSC value should be added to
the MCE record. Most of machine_check_poll() callers supply it, except
__mcheck_cpu_init_generic()
On Fri 2016-11-04 23:20:53, Pandruvada, Srinivas wrote:
> On Fri, 2016-11-04 at 23:16 +0100, Pavel Machek wrote:
> > Hi!
> >
>
> [...]
>
> > So we seem to have thermal or ACPI regression in v4.9-rc3.
> >
> It is possible. Can you add either add printk
> in acpi_processor_ppc_has_changed() or us
Two more important data integrity fixes related to RAID device drivers
which wrongly throw away the SYNCHRONIZE CACHE command in the non-RAID
path and a memory leak fix in the scsi_debug driver.
The patch is available here:
git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi.git scsi-fixes
T
On Sat, 2016-11-05 at 14:20 +0100, Pavel Machek wrote:
> On Fri 2016-11-04 23:20:53, Pandruvada, Srinivas wrote:
> >
> > On Fri, 2016-11-04 at 23:16 +0100, Pavel Machek wrote:
> > >
> > > Hi!
> > >
> >
> > [...]
> >
> > >
> > > So we seem to have thermal or ACPI regression in v4.9-rc3.
> > >
On Tue, Oct 18, 2016 at 02:18:43PM +0200, Oliver Neukum wrote:
> On Mon, 2016-10-17 at 17:20 +0200, Wim Osterholt wrote:
> > On Mon, Oct 17, 2016 at 04:10:45PM +0200, Oliver Neukum wrote:
> > > Hi,
> > >
> > > I got one of those devices. However, I don't get a crash.
> > > Could you please give
From: Randy Li
Add a dummy function for phy_reset in case the CONFIG_GENERIC_PHY
is disabled.
Signed-off-by: Randy Li
Signed-off-by: Kishon Vijay Abraham I
---
include/linux/phy/phy.h |7 +++
1 file changed, 7 insertions(+)
diff --git a/include/linux/phy/phy.h b/include/linux/phy/phy
Hi Greg,
Please find the pull request for the phy fixes below. It includes a fix
in phy core to add a static inline function when CONFIG_GENERIC_PHY
is not selected and 3 fixes in different phy drivers. The phy device name
in the phy lookup table used for non-dt boot is fixed for da8xx-usb phy,
NU
From: Axel Haslam
The ohci device name has changed in the board configuraion files,
hence, change the phy lookup table to match the new name.
Signed-off-by: Axel Haslam
Signed-off-by: Kishon Vijay Abraham I
---
drivers/phy/phy-da8xx-usb.c |5 +++--
1 file changed, 3 insertions(+), 2 delet
From: Shawn Lin
The deassert of phy_rst from exit callback is incorrect as when
doing phy_exit, we expect the phy_rst is on asserted state which was
done by power_off callback, but not deasserted state. Meanwhile when
disabling clk_pciephy_ref, the assert/deassert signal can't actually
take effec
From: Icenowy Zheng
Allwinner SoC's PHY 0, when used as OTG controller, have no pmu part.
The code that poke some unknown bit of PMU for H3/A64 didn't check
the PHY, and will cause kernel oops when PHY 0 is used.
This patch will check whether the pmu is not NULL before poking.
Fixes: b3e0d141ca
Am 05.11.2016 um 02:33 schrieb Eric Engestrom:
+typedef char drm_format_name_buf[32];
Please don't use a typedef for this, just define the maximum size of
characters the function might write somewhere.
See the kernel coding style as well:
In general, a pointer, or a struct that has elements
Most of z3fold operations are in-page, such as modifying z3fold
page header or moving z3fold objects within a page. Taking
per-pool spinlock to protect per-page objects is therefore
suboptimal, and the idea of having a per-page spinlock (or rwlock)
has been around for some time. However, adding on
Hi!
> > Ok, can do, let me recompile and reboot.
> >
> > >
> > > When temperature limit is reached acpi_processor_ppc_notifier()
> > > should
> > > be called.
> >
> > No, that's not correct for ACPI passive trip points, is it? If I
> > recall correctly, those should be monitored even when tempe
On Sat, 2016-11-05 at 14:37 +0100, Pavel Machek wrote:
> Hi!
>
> >
> > [...]
> >
> > >
> > > So we seem to have thermal or ACPI regression in v4.9-rc3.
> > >
> > It is possible. Can you add either add printk
> > in acpi_processor_ppc_has_changed() or use ftrace and see do you
> > get to
> > th
On Sat 2016-11-05 14:53:13, Pavel Machek wrote:
> Hi!
>
> > > Ok, can do, let me recompile and reboot.
> > >
> > > >
> > > > When temperature limit is reached acpi_processor_ppc_notifier()
> > > > should
> > > > be called.
> > >
> > > No, that's not correct for ACPI passive trip points, is it?
On Sat, 2016-11-05 at 15:04 +0100, Pavel Machek wrote:
> On Sat 2016-11-05 14:53:13, Pavel Machek wrote:
> >
> > Hi!
> >
> > >
> > > >
> > > > Ok, can do, let me recompile and reboot.
> > > >
> > > > >
> > > > >
> > > > > When temperature limit is
> > > > > reached acpi_processor_ppc_notifie
Hi!
> > > > So we seem to have thermal or ACPI regression in v4.9-rc3.
> > > >
> > > It is possible. Can you add either add printk
> > > in acpi_processor_ppc_has_changed() or use ftrace and see do you
> > > get to
> > > these functions
> > >
> > > acpi_processor_ppc_init()
> > > acpi_processor_
function is defined as unsigned int.
So we need %u to print it.
Signed-off-by: Heinrich Schuchardt
---
drivers/pinctrl/pinctrl-st.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/pinctrl/pinctrl-st.c b/drivers/pinctrl/pinctrl-st.c
index b7bb371..8308f15 100644
--- a/
for_each_property_of_node(pins, pp) checks that pp is not NULL.
So there is no need to check it inside the loop.
Signed-off-by: Heinrich Schuchardt
---
drivers/pinctrl/pinctrl-st.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/pinctrl/pinctrl-st.c b/drivers/pinctrl/
fw_rev_major and fw_rev_minor are defined as int.
Use %d to print them.
Signed-off-by: Heinrich Schuchardt
---
drivers/watchdog/pcwd_pci.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/watchdog/pcwd_pci.c b/drivers/watchdog/pcwd_pci.c
index c0d07ee..e1fbbf6 100644
-
When moving from typhoon_get_settings to typhoon_getlink_ksettings
in the commit commit f7a5537cd2a5 ("net: 3com: typhoon: use new api
ethtool_{get|set}_link_ksettings"), we use a local variable supported
but we forgot to update the struct ethtool_link_ksettings with
this value.
We also initialize
From: Jiri Kosina
ts_format.reserved is not used anywhere yet, but the compiler generates a
warning when the struct's (uninitialized) field is being copied around
drivers/hid/intel-ish-hid/ipc/ipc.c: In function ‘write_ipc_from_queue’:
drivers/hid/intel-ish-hid/ipc/ipc.c:316: warning: ‘ts_forma
The ethtool api {get|set}_settings is deprecated.
We move this driver to new api {get|set}_link_ksettings.
Signed-off-by: Philippe Reynes
---
drivers/net/ethernet/alteon/acenic.c | 65 ++---
1 files changed, 35 insertions(+), 30 deletions(-)
diff --git a/drivers/ne
On 11/05/2016 07:50 AM, Heinrich Schuchardt wrote:
fw_rev_major and fw_rev_minor are defined as int.
Use %d to print them.
Signed-off-by: Heinrich Schuchardt
---
drivers/watchdog/pcwd_pci.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/watchdog/pcwd_pci.c b/driver
Hi!
> > > Yes, this seems to work. scaling_max goes to 1.5, then 1.1. Also
> > > under
> > > load, scaling_max_freq changes. But at that point, we are already
> > > around 98C... and bios_limit stays the same all the time in v4.9.
> >
> > ...while in v4.8-rc1, bios limit goes to 1.0 GHz at 90C, a
Hi Eric Miao, Haojian Zhuang,
Could you pick up this patch, please?
2016-09-19 2:58 GMT+09:00 Masahiro Yamada :
> In many of clk_disable() implementations, it is a no-op for a NULL
> pointer input, but this is one of the exceptions.
>
> Making it treewide consistent will allow clock consumers to
On 03/11/16 08:20, Fabrice Gasnier wrote:
> On 10/30/2016 04:27 PM, Jonathan Cameron wrote:
>> On 25/10/16 17:25, Fabrice Gasnier wrote:
>>> This patch adds support for STMicroelectronics STM32 MCU's analog to
>>> digital converter.
>>>
>>> Signed-off-by: Fabrice Gasnier
>> Hi Fabrice,
>>
>> Somet
Hi Wan,
This patch was acked by you long before,
but it has not been pulled-in yet for some reasons.
Now the patch was split per platform.
So, could you apply this patch to your tree, please?
2016-09-19 2:59 GMT+09:00 Masahiro Yamada :
> In many of clk_disable() implementations, it is a no-op
Hi Steven,
Could you take a look at this patch, please?
2016-09-19 3:03 GMT+09:00 Masahiro Yamada :
> In many of clk_disable() implementations, it is a no-op for a NULL
> pointer input, but this is one of the exceptions.
>
> Making it treewide consistent will allow clock consumers to call
> clk_
Hi,
On Tue, Sep 6, 2016 at 10:46 PM, Maxime Ripard
wrote:
> The A33 has a significantly different pipeline, with components that differ
> too.
>
> Make sure we had compatible for them.
>
> Signed-off-by: Maxime Ripard
> ---
> Documentation/devicetree/bindings/display/sunxi/sun4i-drm.txt | 7 +++
On Thu, 3 Nov 2016, Ooi, Joyce wrote:
> User is unable to access to input-X-yyy and feature-X-yyy where
> X is a hex value and more than 9 (e.g. input-a-yyy, feature-b-yyy) in HID
> sensor custom sysfs interface.
> This is because when creating the attribute, the attribute index is
> written to us
On Sat, 5 Nov 2016, Chris Metcalf wrote:
> Here are the notes I took; I welcome any corrections and follow-up.
Thank you for writing this up. I hope we can now move forward further on
these issues.
> == Remote statistics ==
>
> We discussed the possibility of remote statistics gathering, i.e. lo
On 05/11/16 12:58, Jonathan Cameron wrote:
> On 01/11/16 19:58, Lars-Peter Clausen wrote:
>> On 11/01/2016 05:03 AM, Matt Ranostay wrote:
>>> On Mon, Oct 31, 2016 at 10:04 AM, Eva Rachel Retuya
>>> wrote:
The name passed to devm_regulator_get() should match the name of the
supply as spe
On 31/10/16 17:04, Eva Rachel Retuya wrote:
> The name passed to devm_regulator_get() should match the name of the
> supply as specified in the device datasheet. This makes it clear what
> power supply is being referred to in case of presence of other
> regulators.
>
> Currently, the supply name s
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
Two small patches related to sched_show_task():
- Make sure to hold a reference on the task stack while accessing it
- Remove the thread_sa
Linus,
please pull from the tag "firewire-fixes" at
git://git.kernel.org/pub/scm/linux/kernel/git/ieee1394/linux1394.git
firewire-fixes
to receive the following FireWire (IEEE 1394) subsystem fixes:
- Add missing input validation to the firewire-net driver.
Invalid IP-over-1394 encap
Linus,
please pull the latest core-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
core-urgent-for-linus
Add a sanity check into release_task_stack() to catch problems with task
stack references.
Thanks,
tglx
-->
Andy Luto
On 31/10/16 17:04, Eva Rachel Retuya wrote:
> Currently, the affected drivers ignore all errors from regulator_get().
> The way it is now, it also breaks probe deferral (EPROBE_DEFER). The
> correct behavior is to propagate the error to the upper layers so they
> can handle it accordingly.
>
> Rew
On 31/10/16 17:04, Eva Rachel Retuya wrote:
> The AD7190/AD7192/AD7193/AD7195 is supplied with two power sources:
> AVdd as analog supply voltage and DVdd as digital supply voltage.
>
> Attempt to fetch and enable the regulator 'dvdd'. Bail out if any error
> occurs.
>
> Suggested-by: Lars-Peter
Extend the driver to support Ricoh RC5T619.
Support the additional regulators and slightly different voltage ranges.
Signed-off-by: Pierre-Hugues Husson
---
drivers/regulator/Kconfig | 4 ++--
drivers/regulator/rn5t618-regulator.c | 35 +++
include/li
The Ricoh RN5T567 is from the same family as the Ricoh RN5T618 is,
the differences are:
+ DCDC4/DCDC5
+ LDO7-10
+ Slightly different output voltage/currents
+ 32kHz Output
+ RTC
+ USB Charger detection
Signed-off-by: Pierre-Hugues Husson
---
Documentation/devicetree/bindings/mfd/rn5t618.txt | 1
This patchset adds RC5T619 support. This PMIC is used on many
rockchip-based devices, for instance the GPD XD, or the Archos 101 Oxygen
---
Documentation/devicetree/bindings/mfd/rn5t618.txt | 16 +++--
drivers/mfd/Kconfig |3 -
drivers/mfd/rn5t618.c
On 31/10/16 17:04, Eva Rachel Retuya wrote:
> Rename regulator 'reg' to 'avdd' so as to be clear what regulator it
> stands for specifically. Also, update the goto label accordingly.
>
> Signed-off-by: Eva Rachel Retuya
Applied.
Thanks,
Jonathan
> ---
> drivers/staging/iio/adc/ad7192.c | 22 ++
On 31/10/16 17:04, Eva Rachel Retuya wrote:
> The AD9832/AD9835 is supplied with two power sources: AVDD as analog
> supply voltage and DVDD as digital supply voltage.
>
> Attempt to fetch and enable the regulator 'dvdd'. Bail out if any error
> occurs.
>
> Suggested-by: Lars-Peter Clausen
> Sig
On 31/10/16 17:04, Eva Rachel Retuya wrote:
> Rename regulator 'reg' to 'avdd' so as to be clear what regulator it
> stands for specifically. Additionally, get rid of local variable 'reg'
> and use direct assignment instead. Update also the goto label pertaining
> to the avdd regulator during disab
I do wonder about this new dmesg entry at a ThinkdPad T440s since 4.6.5:
amd_nb: Cannot enumerate AMD northbridges
--
Toralf
PGP: C4EACDDE 0076E94E
On 03/11/16 14:16, Ludovic Desroches wrote:
> On Wed, Nov 02, 2016 at 05:21:48PM +0800, Wenyou Yang wrote:
>> Add suspend/resume callback, support the pinctrl sleep state when
>> the system suspend as well.
>>
>> Signed-off-by: Wenyou Yang
> Acked-by: Ludovic Desroches
Applied to the togreg branc
On Sat, Nov 05, 2016 at 05:26:22PM +0100, Toralf Förster wrote:
> I do wonder about this new dmesg entry at a ThinkdPad T440s since 4.6.5:
>
> amd_nb: Cannot enumerate AMD northbridges
Those are gone:
09c6c30e72ce ("x86/amd_nb: Clean up init path")
but you can disregard them - the
On Saturday, 2016-11-05 13:11:36 +0100, Christian König wrote:
> Am 05.11.2016 um 02:33 schrieb Eric Engestrom:
> > +typedef char drm_format_name_buf[32];
>
> Please don't use a typedef for this, just define the maximum size of
> characters the function might write somewhere.
>
> See the kernel c
On Sat, Nov 5, 2016 at 12:38 PM, Eric Engestrom wrote:
> On Saturday, 2016-11-05 13:11:36 +0100, Christian König wrote:
>> Am 05.11.2016 um 02:33 schrieb Eric Engestrom:
>> > +typedef char drm_format_name_buf[32];
>>
>> Please don't use a typedef for this, just define the maximum size of
>> charac
On Sat, 2016-11-05 at 16:15 +0100, Jiri Kosina wrote:
> From: Jiri Kosina
>
> ts_format.reserved is not used anywhere yet, but the compiler
> generates a
> warning when the struct's (uninitialized) field is being copied
> around
>
> drivers/hid/intel-ish-hid/ipc/ipc.c: In function
> ‘write_ipc_
On 05/10/16 10:26, Peter Ujfalusi wrote:
> On 10/05/16 12:04, Mugunthan V N wrote:
>> This patch adds the required pieces to ti_am335x_adc driver for
>> DMA support
>>
>> Signed-off-by: Mugunthan V N
Applied to a special branch in iio.git that I'll pull into togreg and then
push out as testing in
On 05/10/16 10:04, Mugunthan V N wrote:
> Add DMA properties for tscadc
>
> Signed-off-by: Mugunthan V N
The support in the driver is now working it's way through iio.git towards
linux-next. I'm guessing this and the next patch will ultimately go through
arm-soc.
Shout if you'd rather I took the
On Friday 04 November 2016 19:33:13 Andrew F. Davis wrote:
> The BQ27510 and BQ27520 use a slightly different register map than
> the BQ27500, add a new type enum and add these gauges to it.
>
> Fixes: d74534c27775 ("power: bq27xxx_battery: Add support for
> additional bq27xxx family devices") Bas
On Fri, Nov 4, 2016 at 11:44 PM, Amir Goldstein wrote:
>
> Can you please clarify your objection?
There are several:
- timing. No way in hell will I take a new feature like this during an rc
- lack of explanation. Why is this bad feature needed in the first
place? Why would overlayfs versioni
On 31/10/16 08:16, Lee Jones wrote:
> On Sun, 30 Oct 2016, Jonathan Cameron wrote:
>
>> On 26/10/16 13:17, Lee Jones wrote:
>>> On Fri, 30 Sep 2016, Mugunthan V N wrote:
>>>
On Wednesday 28 September 2016 01:10 AM, Lee Jones wrote:
> On Wed, 21 Sep 2016, Mugunthan V N wrote:
>
>>
On Sat, 05 Nov 2016, Pavel Machek wrote:
> Hmm, thanks for the pointer. But it seems like I'll have to build my
> own, as /proc/acpi/ibm does not follow the usual infrastructure...
/proc/acpi/ibm has been deprecated for years. 99% of the functionality
is available through more modern, standard in
On Sat, Nov 05, 2016 at 10:51:21AM +0530, Anshuman Khandual wrote:
> On 10/25/2016 09:56 AM, Aneesh Kumar K.V wrote:
> > I looked at the hmm-v13 w.r.t migration and I guess some form of device
> > callback/acceleration during migration is something we should definitely
> > have. I still haven't fig
On Sat, 05 Nov 2016, Pavel Machek wrote:
> [ 825.759661] thinkpad_acpi: THERMAL EMERGENCY: a sensor reports something
> is extremely hot!
> [ 825.761935] thinkpad_acpi: temperatures (Celsius): 101 49 N/A 78 33 N/A 33
> N/A 47 50 N/A N/A N/A N/A N/A N/A
Oh boy, that must be the second time in a
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git for-linus
to receive updates for the input subsystem.
Changelog:
-
Dmitry Tunin (1):
Input: psmouse - cleanup Focaltech code
Patrick Scheuring (1):
Input: i8042 - add XMG C504
On 11/05/2016 04:29 PM, Guenter Roeck wrote:
> On 11/05/2016 07:50 AM, Heinrich Schuchardt wrote:
>> fw_rev_major and fw_rev_minor are defined as int.
>> Use %d to print them.
>>
>> Signed-off-by: Heinrich Schuchardt
>> ---
>> drivers/watchdog/pcwd_pci.c | 2 +-
>> 1 file changed, 1 insertion(+),
On Fri, 04 Nov 2016, Viresh Kumar wrote:
> On 04-11-16, 10:26, Pavel Machek wrote:
> > How would I know if it is thermal capping? There's nothing in dmesg.
>
> I am not sure what code is responsible for doing that in case of x86, maybe
> Rafael and Rui can explain it that better.
>
> But surely i
On Mon, Oct 31, 2016 at 11:56:10PM -0200, Marcos Paulo de Souza wrote:
> Without this patch, the Asus X45U wireless card can't be turned
> on (hard-blocked), but after a suspend/resume it just starts working.
>
> Following this bug report[1], there are other cases like this one, but
> this Asus is
On Thu, Nov 03, 2016 at 11:40:15AM +0800, Anthony Wong wrote:
> On 1 November 2016 at 12:30, Lee, Chun-Yi wrote:
> >
> > The AMW0_GUID1 wmi is not only found on Acer family but also other
> > machines like Lenovo, Fujitsu and Medion. In the past days, acer-wmi
> > driver handled those non-Acer mac
1 - 100 of 168 matches
Mail list logo
