On Wed, May 30, 2018 at 07:46:50AM -0700, Doug Anderson wrote:
> On Wed, May 30, 2018 at 2:37 AM, Mark Brown wrote:
> >> Linux vote for the lowest voltage it's comfortable with. Linux keeps
> >> track of the true voltage that the driver wants and will always change
> >> its vote back to that
On Wed, May 30, 2018 at 4:30 PM, Vivek Goyal wrote:
> On Tue, May 29, 2018 at 04:45:59PM +0200, Miklos Szeredi wrote:
>> From: Vivek Goyal
>>
>> ovl_open() should open file which contains data and not open metacopy
>> inode. With the introduction of metacopy inodes, with current
>>
EMC has a dedicated interrupt that is used to notify about completion of
HW operations. Document the interrupt property.
Signed-off-by: Dmitry Osipenko
---
.../devicetree/bindings/arm/tegra/nvidia,tegra20-emc.txt| 2 ++
1 file changed, 2 insertions(+)
diff --git
The sleeping functions down, down_interruptible, down_killable and
down_timeout can't be called with interrupts disabled, so we don't have to
save and restore interrupt flag.
This patch avoids the costly pushf and popf instructions on the semaphore
path.
Signed-off-by: Mikulas Patocka
---
On 05/30/2018 11:15 AM, Steve Grubb wrote:
On Wednesday, May 30, 2018 9:54:00 AM EDT Stefan Berger wrote:
On 05/29/2018 05:30 PM, Steve Grubb wrote:
Hello,
On Thursday, May 24, 2018 4:11:05 PM EDT Stefan Berger wrote:
The AUDIT_INTEGRITY_RULE is used for auditing IMA policy rules and
the IMA
On 30/05/18 18:28, Tony Lindgren wrote:
* Tero Kristo [180530 15:18]:
For the OCP if part, I think that is still needed until we switch over to
full sysc driver. clkctrl_offs you probably also need because that is used
for mapping the omap_hwmod against a specific clkctrl clock. Those can be
On Wed, May 30, 2018 at 05:12:16PM +0200, Miklos Szeredi wrote:
> >> From: Vivek Goyal
> >>
> >> ovl_open() should open file which contains data and not open metacopy
> >> inode. With the introduction of metacopy inodes, with current
> >> implementaion we will end up opening metacopy inode as
On Wed, May 30, 2018 at 08:34:50AM -0700, Doug Anderson wrote:
> On Wed, May 30, 2018 at 8:02 AM, Mark Brown wrote:
> > What you're describing sounds like what we should be doing normally, if
> > we're not doing that we should probably be fixing the core.
> I'm not convinced that this behavior
On Wed, May 30, 2018 at 09:09:02AM -0700, Doug Anderson wrote:
> On Wed, May 30, 2018 at 9:07 AM, Mark Brown wrote:
> > It needs something to tell it what the new voltage to set is.
> The regulator driver has its own cache of what voltage was most
> recently requested by Linux. It can use
On Wed, May 30, 2018 at 07:04:15PM +0100, Colin King wrote:
> From: Colin Ian King
>
> The addition of the IOCB_CMD_POLL command removed the break
> statement for the IOCM_CMD_FDSYNC. From my understanding, this
> should not have been removed as the fall-through does not seem
> to make sense.
On Wed, May 30, 2018 at 09:59:28AM -0500, Linus Torvalds wrote:
> On Wed, May 30, 2018 at 9:29 AM Alan Stern
> wrote:
>
> > >
> > > Can't we simplify the whole sequence as basically
> > >
> > > A
> > > if (!B)
> > > D
> > >
> > > for that "not B" case, and just think about
* Faiz Abbas [180530 14:12]:
> The dra76x MCAN generic interconnect module has a its own
> format for the bits in the control registers.
...
> --- a/drivers/bus/ti-sysc.c
> +++ b/drivers/bus/ti-sysc.c
> @@ -1262,6 +1262,22 @@ static const struct sysc_capabilities
> sysc_omap4_usb_host_fs = {
>
Synopsys has DWC MSHC controller on HPAS-DX platform connected using PCIe
interface with SD card slot and eMMC device slots. This patch is to
enable SD cards connected on this platform. As Clock generation logic
is implemented using MMCM module of HAPS-DX platform, we have separate
functions to
* Faiz Abbas [180530 14:12]:
> From: Franklin S Cooper Jr
>
> Add support for the MCAN peripheral which supports both classic
> CAN messages along with the new CAN-FD message.
...
> --- a/arch/arm/boot/dts/dra76x.dtsi
> +++ b/arch/arm/boot/dts/dra76x.dtsi
> @@ -27,6 +27,21 @@
>
On Wed, 2018-05-30 at 06:59 +0200, j...@8bytes.org wrote:
> On Tue, May 29, 2018 at 04:10:24PM +, Kani, Toshi wrote:
> > Can you explain why you think allocating a page here is a major problem?
>
> Because a larger allocation is more likely to fail. And if you fail the
> allocation, you also
On Thu, May 10, 2018 at 04:46:15PM -0500, Bjorn Helgaas wrote:
> From: Bjorn Helgaas
>
> 02bfeb484230 ("PCI/portdrv: Simplify PCIe feature permission checking")
> removed the only call of pcie_port_acpi_setup() and removed portdrv_acpi.o
> from the Makefile, but I forgot to remove
On Wed, 2018-05-30 at 18:25 +0200, Charlemagne Lasse wrote:
> Since the commit 9dd0c31c6cc0 ("checkpatch: improve patch
> recognition"), the checkpatch.pl in linux-next is only printing a lot
> of error messages when started (with and without arguments):
https://lkml.org/lkml/2018/5/29/932
Hello Rajendra,
On 05/30/2018 03:14 AM, Rajendra Nayak wrote:
> On 05/30/2018 02:47 PM, Ulf Hansson wrote:
>> On 25 May 2018 at 12:01, Rajendra Nayak wrote:
...
>>> + pm_genpd_init([i]->pd, NULL, true);
>>
>> Question: Is there no hierarchical topology of the PM domains. No
>>
On 05/30/2018 01:02 AM, Michal Hocko wrote:
> On Tue 29-05-18 15:21:14, Mike Kravetz wrote:
>> Just a quick heads up. I noticed a change in libhugetlbfs testing starting
>> with v4.17-rc1.
>>
>> V4.16 libhugetlbfs test results
>> ** TEST SUMMARY
>> * 2M
>>
Hello,
Couple years ago the Tegra20 EMC driver was removed from the kernel
due to incompatible changes in the Tegra's clock driver. This patchset
introduces a modernized EMC driver. Currently the sole purpose of the
driver is to initialize DRAM frequency to maximum rate during of the
kernels
Introduce driver for the External Memory Controller (EMC) found on Tegra20
chips, which controls the external DRAM on the board. The purpose of this
driver is to program memory timings for external memory on the EMC clock
rate change.
Signed-off-by: Dmitry Osipenko
---
On Wed, May 30, 2018 at 02:22:56PM +0200, Hans Westgaard Ry wrote:
> We came up with this code snippet which we think handles both preventing
> immediate re-use and too big/wrapping...
Isn't this basically the same as idr_alloc_cyclic ?
Jason
On 05/29/2018 06:19 PM, Andy Shevchenko wrote:
On Wed, May 30, 2018 at 1:24 AM, Eddie James wrote:
From: "Edward A. James"
Add and initialize I2C adapters for each port on the FSI-attached I2C
master. Ports for each master are defined in the devicetree.
+#include
+static int
Hi Vijay,
On 05/30/2018 10:11 AM, Vijay Viswanath wrote:
> Hi Georgi,
>
> Thanks for testing the patch on 8096 and pointing out this issue.
> The issue is coming because, when card is removed, the HOST_CONTROL2
> register is retaining the 1.8V Signalling enable bit till SDHCI reset
> happens
A missing clock update is causing the below warning:
[ cut here ]
rq->clock_update_flags < RQCF_ACT_SKIP
WARNING: CPU: 10 PID: 0 at kernel/sched/sched.h:963
inactive_task_timer+0x5d6/0x720
Modules linked in: xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 tun
On Wed, May 30, 2018 at 09:06:16AM -0700, Doug Anderson wrote:
> On Wed, May 30, 2018 at 8:48 AM, Mark Brown wrote:
> > Without the core doing something the regulator isn't going to get told
> > that anything updated voltages anyway...
> I was just suggesting that when the core tells the
On Wed, May 30, 2018 at 09:12:25AM -0700, Doug Anderson wrote:
> On Wed, May 30, 2018 at 8:50 AM, Mark Brown wrote:
> > No, I'm saying that I don't know why that property exists at all. This
> > sounds like it's intended to be the amount of current the regulator can
> > deliver in each mode
Hi,
On Wed, May 30, 2018 at 9:13 AM, Mark Brown wrote:
> On Wed, May 30, 2018 at 09:09:02AM -0700, Doug Anderson wrote:
>> On Wed, May 30, 2018 at 9:07 AM, Mark Brown wrote:
>
>> > It needs something to tell it what the new voltage to set is.
>
>> The regulator driver has its own cache of what
On Wed, May 30, 2018 at 11:52:40AM +0100, Ben Hutchings wrote:
> This is the start of the stable review cycle for the 3.2.102 release.
> There are 153 patches in this series, which will be posted as responses
> to this one. If anyone has any issues with these being applied, please
> let me know.
On Tue, May 29, 2018 at 05:17:19PM -0400, Josef Bacik wrote:
> From: Josef Bacik
>
> We need to use blk_rq_stat in the blkcg qos stuff, so export some of
> these helpers so they can be used by other things.
>
> Signed-off-by: Josef Bacik
Acked-by: Tejun Heo
Thanks.
--
tejun
On Thu, May 10, 2018 at 05:09:06PM -0500, Bjorn Helgaas wrote:
> [Sorry for the repost; network hiccup here.]
>
> Trivial reorganization (move quirk infrastructure to the top) and
> whitespace/comment style cleanup for consistency. No functional change
> intended.
>
> ---
>
> Bjorn Helgaas
On Wed, May 30, 2018 at 09:41:55AM -0700, Doug Anderson wrote:
> On Wed, May 30, 2018 at 9:36 AM, Mark Brown wrote:
> > Yeah, and I don't think that's unreasonable for the core to do - just
> > drop the voltage to the constraint minimum after it has turned off the
> > regulator, then recheck and
Ping.
Shenwei
-Original Message-
From: Shenwei Wang
Sent: Thursday, May 24, 2018 1:09 PM
To: thierry.red...@gmail.com
Cc: linux-...@vger.kernel.org; dl-linux-imx ;
linux-kernel@vger.kernel.org; Shenwei Wang
Subject: [PATCH 1/1] pwm: fsl-ftm: Support the new version of FTM block on
Hi Clément,
Correct me if I'm wrong, but I thought the trend is to move to use
earlycon that can be activated from kernel command line for early print
before the serial driver is loaded.
Have you tried earlcon?
Thanks,
Ray
On 5/30/2018 6:19 AM, Clément Péron wrote:
From: Clément Peron
On Wed, 30 May 2018 19:43:09 +0200
Janusz Krzysztofik wrote:
> On Wednesday, May 30, 2018 11:05:00 AM CEST Boris Brezillon wrote:
> > Hi Janusz,
>
> Hi Boris,
>
> > On Sat, 26 May 2018 00:20:45 +0200
> > Janusz Krzysztofik wrote:
> > > ...
> > > Changes since v1:
> > > - fix handling of
On 05/30/2018 11:14 AM, Colin King wrote:
> From: Colin Ian King
>
> The function acpi_table_parse_enties_array can potentially return a
> negative value if parsing fails. Currently the check on the return
> is not checking for errors, so fix this by adding a -ve check too.
>
> Detected by
Hi Steven,
I love your patch! Perhaps something to improve:
[auto build test WARNING on asoc/for-next]
[also build test WARNING on v4.17-rc7 next-20180530]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci
Fixes: 3bed8970d09a ("ASoC: TSCS454: Add Support")
Signed-off-by: kbuild test robot
---
tscs454.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/sound/soc/codecs/tscs454.c b/sound/soc/codecs/tscs454.c
index 8d8cac3..d7e4f7c 100644
--- a/sound/soc/codecs/tscs454.c
+++
On Tue, May 29, 2018 at 10:21:53PM -0500, Linus Torvalds wrote:
> On Tue, May 29, 2018 at 6:38 PM Dmitry Torokhov
> wrote:
>
> > We are switching a bunch of
> > Lenovo devices with Synaptics touchpads from PS/2 emulation over to
> > native RMI/SMbus.
>
> > Given that all commits are marked
Hi Boris,
On 30.05.2018 17:06, Boris Brezillon wrote:
On Wed, 30 May 2018 15:14:33 +0200
Frieder Schrempf wrote:
Move the documentation of the old SPI NOR driver to the place of the new
SPI memory interface based driver and adjust the content to reflect the
new drivers settings.
Maybe it's
On 30/05/18 16:12, Jon Hunter wrote:
> The call to hw_params for a component fails the error code is held by
> the variable '__ret' but the error message displays the value held by
> the variable 'ret'. Fix the return code shown when hw_params fails for
> a component.
Sorry, just resent this as
On 30/05/18 17:50, Tony Lindgren wrote:
* Faiz Abbas [180530 14:12]:
From: Lokesh Vutla
Add MCAN hwmod data and register it for dra762 silicons.
Signed-off-by: Lokesh Vutla
Signed-off-by: Faiz Abbas
---
arch/arm/mach-omap2/omap_hwmod_7xx_data.c | 32 +++
1 file
When the call to hw_params for a component fails, the error code is held
by the variable '__ret' but the error message displays the value held by
the variable 'ret'. Fix the return code shown when hw_params fails for
a component.
Fixes: b8135864d4d3 ("ASoC: snd_soc_component_driver has
On 29/05/18 11:04, Ulf Hansson wrote:
> To support devices being partitioned across multiple PM domains, let's
> begin with extending genpd to cope with these kind of configurations.
>
> Therefore, add a new exported function genpd_dev_pm_attach_by_id(), which
> is similar to the existing
On Tue, May 22, 2018 at 08:11:36AM -0500, Bjorn Helgaas wrote:
> Use dev_printk() to follow style of other arches.
>
> I'll merge via the PCI tree unless there are objections.
>
> ---
>
> Bjorn Helgaas (1):
> MIPS: PCI: Use dev_printk() when possible
>
>
> arch/mips/pci/pci-legacy.c |
Secondary CPUs should have the same information in DeviceTree as booting
CPU from both correctness point of view and for possible hotplug
scenarios.
Suggested-by: Viresh Kumar
Signed-off-by: Krzysztof Kozlowski
---
arch/arm/boot/dts/exynos5420-cpus.dtsi | 6 ++
On Tue, May 22, 2018 at 08:10:07AM -0500, Bjorn Helgaas wrote:
> Remove some dead code, make things static, use dev_printk() to follow style
> of other arches.
>
> I'll merge these via the PCI tree unless there are objections.
>
> ---
>
> Bjorn Helgaas (3):
> xtensa/PCI: Remove dead code
On the new i.MX8x SoC family, the following changes were made on the FTM
block:
1. Need to enable the IPG clock before accessing any FTM registers. Because
the IPG clock is not an option for FTM counter clock source, it can't be
used as the ftm_sys clock.
2. An additional PWM enable bit was
Hi Peter,
maybe you missed this previous my response:
20180518133353.GO30654@e110439-lin
?
Would like to have your tought about the concept of "transient maximum
capacity" I was describing...
On 18-May 14:33, Patrick Bellasi wrote:
> On 18-May 13:29, Peter Zijlstra wrote:
> > On Fri, May 18,
On Wed, May 30, 2018 at 9:29 AM Alan Stern
wrote:
> >
> > Can't we simplify the whole sequence as basically
> >
> > A
> > if (!B)
> > D
> >
> > for that "not B" case, and just think about that. IOW, let's ignore the
> > whole "not executed" code.
> Your listing is slightly
Kernel should never gate the EMC clock as it causes immediate lockup, so
removing clk-gate functionality doesn't affect anything. Turning EMC clk
gate into divider allows to implement glitch-less EMC scaling, avoiding
reparenting to a backup clock.
Signed-off-by: Dmitry Osipenko
---
On Wed, 30 May 2018 15:14:34 +0200
Frieder Schrempf wrote:
> The FSL QSPI driver was moved to the SPI framework and it now
> acts as a SPI controller. Therefore the subnodes need to set
> spi-[rx/tx]-bus-width = <4>, so quad mode is used just as before.
We should try to keep the current
Quoting Lee Jones (2018-05-30 04:16:49)
> On Tue, 29 May 2018, Matti Vaittinen wrote:
>
> > Hello,
> >
> > On Tue, May 29, 2018 at 08:39:58AM +0100, Lee Jones wrote:
> > > On Mon, 28 May 2018, Matti Vaittinen wrote:
> > >
> > > > Patch series adding support for ROHM BD71837 PMIC.
> > > FYI,
On 05/29/2018 06:19 PM, Andy Shevchenko wrote:
On Wed, May 30, 2018 at 1:24 AM, Eddie James wrote:
From: "Edward A. James"
Add and initialize I2C adapters for each port on the FSI-attached I2C
master. Ports for each master are defined in the devicetree.
+#include
+static int
On Wed, May 30, 2018 at 11:39:00PM +0800, Leo Yan wrote:
> Hi Mike,
>
> On Wed, May 30, 2018 at 04:04:34PM +0100, Mike Leach wrote:
>
> [...]
>
> > >>> + /* Generate sample for exception packet */
> > >>> + if (etmq->prev_packet->exc == true)
> > >>> +
On Tue, May 29, 2018 at 05:17:12PM -0400, Josef Bacik wrote:
> From: Josef Bacik
>
> Currently io.low uses a bi_cg_private to stash its private data for the
> blkg, however other blkcg policies may want to use this as well. Since
> we can get the private data out of the blkg, move this to
On Wed, May 30, 2018 at 07:54:47AM -0700, Doug Anderson wrote:
> On Wed, May 30, 2018 at 3:37 AM, Mark Brown wrote:
> > I'm confused as to why we are specifying the maximum current the device
> > can deliver in a given mode in the DT - surely that's a fixed property
> > of the hardware?
> Said
Hi,
On Wed, May 30, 2018 at 8:48 AM, Mark Brown wrote:
> On Wed, May 30, 2018 at 08:34:50AM -0700, Doug Anderson wrote:
>> On Wed, May 30, 2018 at 8:02 AM, Mark Brown wrote:
>
>> > What you're describing sounds like what we should be doing normally, if
>> > we're not doing that we should
On 29/05/18 11:04, Ulf Hansson wrote:
> The power-domain DT property may now contain a list of PM domain
> specifiers, which represents that a device are partitioned across multiple
> PM domains. This leads to a new situation in genpd_dev_pm_attach(), as only
> one PM domain can be attached per
Hi Vincent,
On Friday 25 May 2018 at 15:12:24 (+0200), Vincent Guittot wrote:
> Add both cfs and rt utilization when selecting an OPP for cfs tasks as rt
> can preempt and steal cfs's running time.
>
> Signed-off-by: Vincent Guittot
> ---
> kernel/sched/cpufreq_schedutil.c | 14 +++---
On Wed, 2018-05-30 at 09:51 -0700, Gwendal Grignou wrote:
> Fix syntax error in patch.
https://lkml.org/lkml/2018/5/29/932
On Thu, May 17, 2018 at 10:21:31AM -0700, Ray Jui wrote:
> On certain versions of Broadcom PAXC based root complexes, certain
> regions of the configuration space are corrupted. As a result, it
> prevents the Linux PCIe stack from traversing the linked list of the
> capability registers completely
Hi Andy,
On 5/29/2018 5:59 PM, Andy Shevchenko wrote:
On Wed, May 30, 2018 at 12:58 AM, Ray Jui wrote:
Add PCIe legacy interrupt INTx support to the iProc PCIe driver by
modeling it with its own IRQ domain. All 4 interrupts INTA, INTB, INTC,
INTD share the same interrupt line connected to the
unsubscribe linux-kernel
From: Bjorn Helgaas
Decode the Requester ID from the AER Error Source Register into domain/
bus/device/function format to match other logging. In cases where the ID
matches the device used for pci_err(), drop the extra ID completely so we
don't print it twice.
Signed-off-by: Bjorn Helgaas
---
AER logging printed the plain 16-bit Requester ID straight out of the TLP,
which is hard to interpret, e.g., id=00e4 corresponds to what we normally
see as 00:1c.4 in dmesg or lspci.
Also, there's no need to print the vendor/device ID of the root port
reporting an error; we can easily find that
From: Bjorn Helgaas
The Vendor and Device ID of the root port that raised an AER interrupt is
irrelevant and already available via normal enumeration dmesg logging or
lspci.
Remove the Vendor and Device ID from AER logging.
Signed-off-by: Bjorn Helgaas
---
From: Colin Ian King
The addition of the IOCB_CMD_POLL command removed the break
statement for the IOCM_CMD_FDSYNC. From my understanding, this
should not have been removed as the fall-through does not seem
to make sense. Fix this by adding the break back again.
Detected by CoverityScan,
On Tue, May 29, 2018 at 1:31 AM, Michal Hocko wrote:
> On Mon 28-05-18 10:23:07, Shakeel Butt wrote:
>> On Mon, May 28, 2018 at 2:11 AM, Michal Hocko wrote:
>> Though is there a precedence where the broken feature is not fixed
>> because an alternative is available?
>
> Well, I can see how
On Wed, May 30, 2018 at 10:54 AM Bjorn Helgaas wrote:
> From: Bjorn Helgaas
> The Vendor and Device ID of the root port that raised an AER interrupt is
> irrelevant and already available via normal enumeration dmesg logging or
> lspci.
Er, what is getting printed is not the vendor/device id
On Sun, May 27, 2018 at 01:28:42PM +0200, Eugene Syromiatnikov wrote:
> Recent introduction of netns_dev/netns_ino to bpf_map_info/bpf_prog info
> has broken compat, as offsets of these fields are different in 32-bit
> and 64-bit ABIs. One fix (other than implementing compat support in
> syscall
* Faiz Abbas [180530 14:12]:
> The ti-sysc driver provides support for manipulating the idlemodes
> and interconnect level resets.
...
> --- a/arch/arm/boot/dts/dra76x.dtsi
> +++ b/arch/arm/boot/dts/dra76x.dtsi
> @@ -11,6 +11,25 @@
> / {
> compatible = "ti,dra762", "ti,dra7";
>
> +
* Tero Kristo [180530 15:18]:
> For the OCP if part, I think that is still needed until we switch over to
> full sysc driver. clkctrl_offs you probably also need because that is used
> for mapping the omap_hwmod against a specific clkctrl clock. Those can be
> only removed once we are done with
Since the commit 9dd0c31c6cc0 ("checkpatch: improve patch
recognition"), the checkpatch.pl in linux-next is only printing a lot
of error messages when started (with and without arguments):
Variable "$clean" is not imported at ./scripts/checkpatch.pl line 6496.
Variable "$clean" is not imported at
On Wed, May 30, 2018 at 09:31:55AM -0700, Doug Anderson wrote:
> On Wed, May 30, 2018 at 9:13 AM, Mark Brown wrote:
> > If we're just going to use the most recently set voltage then hopefully
> > the hardware already knew that, and it might not be the lowest available
> > voltage if the last
Hi Gwendal,
2018-05-30 18:04 GMT+02:00 Gwendal Grignou :
> Move to_cros_ec_dev macro to cros_ec.h and use it when the private ec
> object is needed from device object.
>
> Signed-off-by: Gwendal Grignou
> ---
> Change since v1:
>Remove changes in cros_ec_dev.c to avoid inter-dependencies.
>
Hi,
On Wed, May 30, 2018 at 9:36 AM, Mark Brown wrote:
> On Wed, May 30, 2018 at 09:31:55AM -0700, Doug Anderson wrote:
>> On Wed, May 30, 2018 at 9:13 AM, Mark Brown wrote:
>
>> > If we're just going to use the most recently set voltage then hopefully
>> > the hardware already knew that, and
On 27-May 11:50, Rafael J. Wysocki wrote:
> On Thu, May 24, 2018 at 4:10 PM, Patrick Bellasi
> wrote:
> > Since the refactoring introduced by:
> >
> >commit 8f111bc357aa ("cpufreq/schedutil: Rewrite CPUFREQ_RT support")
> >
> > we aggregate FAIR utilization only if this class has runnable
On 30/05/18 18:59, Al Stone wrote:
> On 05/30/2018 11:14 AM, Colin King wrote:
>> From: Colin Ian King
>>
>> The function acpi_table_parse_enties_array can potentially return a
>> negative value if parsing fails. Currently the check on the return
>> is not checking for errors, so fix this by
On Wed, May 30, 2018 at 12:54:15PM -0500, Bjorn Helgaas wrote:
> void aer_print_port_info(struct pci_dev *dev, struct aer_err_info *info)
> {
> - pci_info(dev, "AER: %s%s error received: id=%04x\n",
> + u8 bus = info->id >> 8;
> + u8 devfn = info->id & 0xff;
> +
> + pci_info(dev,
On 05/29/2018 02:17 PM, Josef Bacik wrote:
> From: Josef Bacik
>
> A basic documentation to describe the interface, statistics, and
> behavior of io.latency.
>
> Signed-off-by: Josef Bacik
> ---
> Documentation/blk-iolatency.txt | 80
> +
> 1 file
On Wed, May 30, 2018 at 08:14:09PM +0800, Baolin Wang wrote:
> On 30 May 2018 at 20:01, Matthew Wilcox wrote:
> > On Wed, May 30, 2018 at 07:28:43PM +0800, Baolin Wang wrote:
> >> It will be crash if we pass one NULL name when creating one dma pool,
> >> so we should check the passing name when
Hi Boris,
On 30.05.2018 16:32, Boris Brezillon wrote:
Hi Frieder,
On Wed, 30 May 2018 15:14:30 +0200
Frieder Schrempf wrote:
When porting (Q)SPI controller drivers from the MTD layer to the SPI
layer, the naming scheme for the memory devices changes. To be able
to keep compatibility with
The call to hw_params for a component fails the error code is held by
the variable '__ret' but the error message displays the value held by
the variable 'ret'. Fix the return code shown when hw_params fails for
a component.
Fixes: b8135864d4d3 ("ASoC: snd_soc_component_driver has snd_pcm_ops")
Add interrupt entry into the EMC DT node.
Signed-off-by: Dmitry Osipenko
---
arch/arm/boot/dts/tegra20.dtsi | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/boot/dts/tegra20.dtsi b/arch/arm/boot/dts/tegra20.dtsi
index 983dd5c14794..3cd3cb28cfd9 100644
---
On Tue, May 29, 2018 at 11:41:51AM +0200, Arnd Bergmann wrote:
> Enabling the PCI_MVEBU driver for compile testing caused a build failure
> on ARM randconfig builds:
>
> drivers/pci/host/pci-mvebu.c: In function 'mvebu_pcie_del_windows':
> drivers/pci/host/pci-mvebu.c:341:3: error: implicit
On Wed, May 30, 2018 at 03:56:34PM +0300, Matti Vaittinen wrote:
> On Wed, May 30, 2018 at 12:00:00PM +0100, Mark Brown wrote:
> > The tradeoff with forced PWM mode is that the quality of regulation will
> > be a lot better, especially if the load changes suddenly (as things like
> > CPUs often
On 05/29/2018 06:42 PM, Andy Shevchenko wrote:
On Wed, May 30, 2018 at 1:24 AM, Eddie James wrote:
From: "Edward A. James"
Add register definitions for FSI-attached I2C master and functions to
access those registers over FSI. Add an FSI driver so that our I2C bus
is probed up during an
On Wed, May 30, 2018 at 08:13:27AM -0700, Matthew Wilcox wrote:
> On Wed, May 30, 2018 at 08:14:09PM +0800, Baolin Wang wrote:
> > On 30 May 2018 at 20:01, Matthew Wilcox wrote:
> > > On Wed, May 30, 2018 at 07:28:43PM +0800, Baolin Wang wrote:
> > >> It will be crash if we pass one NULL name
Hi,
On Wed, May 30, 2018 at 9:07 AM, Mark Brown wrote:
> On Wed, May 30, 2018 at 09:06:16AM -0700, Doug Anderson wrote:
>> On Wed, May 30, 2018 at 8:48 AM, Mark Brown wrote:
>
>> > Without the core doing something the regulator isn't going to get told
>> > that anything updated voltages
On 29/05/18 11:04, Ulf Hansson wrote:
> To extend genpd to deal with allowing multiple PM domains per device, some
> of the code in genpd_dev_pm_attach() can be re-used. Let's prepare for this
> by moving some of the code into a sub-function.
>
> Signed-off-by: Ulf Hansson
> ---
>
On Tue, May 22, 2018 at 08:02:17AM -0500, Bjorn Helgaas wrote:
> [+cc sparclinux, sorry I missed this first time around]
>
> On Mon, May 21, 2018 at 07:30:29PM -0500, Bjorn Helgaas wrote:
> > The main thing here is the first patch, a legacy VGA framebuffer fix for
> > issues reported by Meelis.
>
On Fri, May 18, 2018 at 05:31:07PM -0500, Bjorn Helgaas wrote:
> From: Bjorn Helgaas
>
> Host bridge drivers do not use the portdrv interfaces (struct pcie_device,
> struct pcie_port_service_driver, pcie_port_service_register(), etc), and
> they should not select CONFIG_PCIEPORTBUS.
>
> If
Fix syntax error in patch.
Signed-off-by: Gwendal Grignou
---
scripts/checkpatch.pl | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
index f1fecd8aa4d7..03dd7b6b0eab 100755
--- a/scripts/checkpatch.pl
+++ b/scripts/checkpatch.pl
On Wed, May 30, 2018 at 12:31 AM, Greg KH wrote:
> On Tue, May 29, 2018 at 11:52:37PM -0700, John Stultz wrote:
>> On Tue, May 29, 2018 at 10:33 PM, Greg KH wrote:
>> > On Tue, May 29, 2018 at 10:14:35PM -0700, John Stultz wrote:
>> >> On Tue, May 8, 2018 at 7:28 PM, Chanwoo Choi
>> >> wrote:
Hi,
> -Original Message-
> From: Peter Ujfalusi [mailto:peter.ujfal...@ti.com]
> Sent: Tuesday, May 29, 2018 8:35 PM
> To: Radhey Shyam Pandey ; Vinod Koul
>
> Cc: Lars-Peter Clausen ; michal.si...@xilinx.com; linux-
> ker...@vger.kernel.org; dmaeng...@vger.kernel.org;
>
On Wednesday, May 30, 2018 11:05:00 AM CEST Boris Brezillon wrote:
> Hi Janusz,
Hi Boris,
> On Sat, 26 May 2018 00:20:45 +0200
> Janusz Krzysztofik wrote:
> > ...
> > Changes since v1:
> > - fix handling of devm_gpiod_get_optional() return values - thanks to
> > Andy Shevchenko.
>
> Can you
On Wed, 30 May 2018, Linus Torvalds wrote:
> On Wed, May 30, 2018 at 9:29 AM Alan Stern
> wrote:
>
> > >
> > > Can't we simplify the whole sequence as basically
> > >
> > > A
> > > if (!B)
> > > D
> > >
> > > for that "not B" case, and just think about that. IOW, let's ignore
From: Colin Ian King
It may be possible for tsl2772_get_lux to return a zero lux value
and hence a division by zero can occur when lux_val is zero. Check
for this case and return -ERANGE to avoid the division by zero.
Detected by CoverityScan, CID#1469484 ("Division or modulo by zero")
Hi,
On Wed, May 30, 2018 at 3:37 AM, Mark Brown wrote:
> On Tue, May 29, 2018 at 10:23:20PM -0700, Doug Anderson wrote:
>
>> > + qcom,drms-mode-max-microamps = <1 100>;
>
>> Things look pretty good to me now. I'm still hesitant about the whole
>> need to list the
1 - 100 of 1682 matches
Mail list logo
