On Thu, Jul 04, 2019 at 04:34:58PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> After merging the usb tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
>
> arm-linux-gnueabi-ld: drivers/usb/dwc3/trace.o: in function
> `trace_raw_output_dwc3_log_ctrl':
> trace.c:(.text+0
On Thu, Jul 04, 2019 at 12:13:40PM +0530, Sai Prakash Ranjan wrote:
> On 7/4/2019 1:32 AM, Mathieu Poirier wrote:
> > Hi Greg,
> >
> > On Thu, 27 Jun 2019 at 12:15, Sai Prakash Ranjan
> > wrote:
> > >
> > > Do not assume the affinity to CPU0 if cpu phandle is omitted.
> > > Update the DT binding
On Thu, Jul 04, 2019 at 02:35:20PM +0800, Jason Wang wrote:
> On 2019/7/4 下午2:21, Tiwei Bie wrote:
> > On Thu, Jul 04, 2019 at 12:31:48PM +0800, Jason Wang wrote:
> > > On 2019/7/3 下午9:08, Tiwei Bie wrote:
> > > > On Wed, Jul 03, 2019 at 08:16:23PM +0800, Jason Wang wrote:
> > > > > On 2019/7/3 下午7
On Wed, Jul 3, 2019 at 7:21 PM Pawel Dembicki wrote:
> This commit introduce how to use vsc73xx platform driver.
>
> Signed-off-by: Pawel Dembicki
Nice!
> +If Platform driver is used, the device tree node is an platform device so it
> +must reside inside a platform bus device tree node.
I wou
On 2019/7/4 12:20, Dennis Zhou wrote:
> On Wed, Jul 03, 2019 at 04:25:52PM +0800, Kefeng Wang wrote:
>> pcpu_setup_first_chunk() will panic or BUG_ON if the are some
>> error and doesn't return any error, hence it can be defined to
>> return void.
>>
>> Signed-off-by: Kefeng Wang
>> ---
...
>>
On Wed, Jul 3, 2019 at 7:21 PM Pawel Dembicki wrote:
> This driver (currently) only takes control of the switch chip over
> SPI and configures it to route packages around when connected to a
> CPU port. But Vitesse chip support also parallel interface.
>
> This patch split driver into two parts:
On 03/07/2019 18:00, Dmitry Osipenko wrote:
> 03.07.2019 19:37, Jon Hunter пишет:
>>
>> On 03/07/2019 02:28, Dmitry Osipenko wrote:
>>> Tegra's APB DMA engine updates words counter after each transferred burst
>>> of data, hence it can report transfer's residual with more fidelity which
>>> may b
On Wed, 3 Jul 2019 at 23:33, Saravana Kannan wrote:
>
> On Tue, Jul 2, 2019 at 11:45 PM Vincent Guittot
> wrote:
> >
> > On Wed, 3 Jul 2019 at 03:10, Saravana Kannan wrote:
> > >
> > > Interconnect paths can have different performance points. Now that OPP
> > > framework supports bandwidth OPP t
Hi Shijith,
On 04/07/2019 05:22, Shijith Thotton wrote:
> The NMI handlers handle_percpu_devid_fasteoi_nmi() and
> handle_fasteoi_nmi() added by commit 2dcf1fbcad35 ("genirq: Provide NMI
> handlers") do not update the interrupt counts. Due to that the NMI
> interrupt count does not show up correct
Hi Andy,
On Wed, Jul 3, 2019 at 4:37 PM Andy Shevchenko
wrote:
> On Wed, Jun 26, 2019 at 01:00:45PM +0200, Geert Uytterhoeven wrote:
> > On Wed, Jun 26, 2019 at 11:39 AM Andy Shevchenko
> > wrote:
> > > --- a/include/linux/kernel.h
> > > +++ b/include/linux/kernel.h
> >
> > > @@ -437,7 +435,15 @
Hi Pawel,
this looks overall good and the following is just
documentation nit-pick so feel free to add my
Reviewed-by: Linus Walleij
On Wed, Jul 3, 2019 at 7:21 PM Pawel Dembicki wrote:
> This patch add platform part of vsc73xx driver.
> It allows to use chip connected by parallel interface.
>
+Kees for the safe-array-iteratio question.
On Wed, 03 Jul 2019 16:26:46 +0200
Philipp Zabel wrote:
> Hi Ezequiel
>
> On Tue, 2019-07-02 at 14:00 -0300, Ezequiel Garcia wrote:
> > From: ZhiChao Yu
> >
> > Introduce VP8 decoding support in RK3288.
> >
> > Signed-off-by: ZhiChao Yu
> > Signed
On Jul 03 2019, Alistair Francis wrote:
> On Wed, Jul 3, 2019 at 12:08 AM Andreas Schwab wrote:
>>
>> On Jul 02 2019, Alistair Francis wrote:
>>
>> > In the RISC-V 32-bit glibc port [1] the siginfo_t struct in the kernel
>> > doesn't line up with the struct in glibc. In glibc world the _sifield
On Wed, Jul 3, 2019 at 7:21 PM Pawel Dembicki wrote:
> Driver allow to use devices with disabled iCPU only.
>
> Some devices have pre-initialised iCPU by bootloader.
> That state make switch unmanaged. This patch force reset
> if device is in unmanaged state. In the result chip lost
> internal fi
On Tue, Jun 25, 2019 at 11:04 PM 'Nick Desaulniers' via Clang Built
Linux wrote:
>
> Clang produces references to __aeabi_uidivmod and __aeabi_idivmod for
> arm-linux-gnueabi and arm-linux-gnueabihf targets incorrectly when AEABI
> is not selected (such as when OABI_COMPAT is selected).
>
> While
If clk_enable is not defined and chip initialization
is canceled code hits null dereference.
Easily reproducible with vTPM init fail:
swtpm chardev --tpmstate dir=nonexistent_dir --tpm2 --vtpm-proxy
BUG: kernel NULL pointer dereference, address:
...
Call Trace:
tpm_chip_start+0x9d/0xa
On Fri, Jun 28, 2019 at 4:13 AM Sowjanya Komatineni
wrote:
> This patch adds support for Tegra pinctrl driver suspend and resume.
>
> During suspend, context of all pinctrl registers are stored and
> on resume they are all restored to have all the pinmux and pad
> configuration for normal operati
Hi,
On Thu, Jul 4, 2019 at 9:59 AM Greg KH wrote:
>
> On Thu, Jul 04, 2019 at 04:34:58PM +1000, Stephen Rothwell wrote:
> > Hi all,
> >
> > After merging the usb tree, today's linux-next build (arm
> > multi_v7_defconfig) failed like this:
> >
> > arm-linux-gnueabi-ld: drivers/usb/dwc3/trace.o: i
Hi Arnaldo,
On Wed, Jul 03, 2019 at 03:18:15PM -0300, Arnaldo Carvalho de Melo wrote:
> Em Wed, Jul 03, 2019 at 09:48:08AM +0800, Leo Yan escreveu:
> > On Tue, Jul 02, 2019 at 01:07:43PM +0200, Jiri Olsa wrote:
> > > On Tue, Jul 02, 2019 at 06:34:09PM +0800, Leo Yan wrote:
> > > > When I used stat
Hi all,
After merging the slave-dma tree, today's linux-next build (x86_64
allmodconfig) failed like this:
ERROR: "of_irq_count" [drivers/dma/fsl-edma.ko] undefined!
Caused by commit
7144afd025b2 ("dmaengine: fsl-edma: add i.mx7ulp edma2 version support")
I have reverted that commit for toda
On Sat, Jun 29, 2019 at 5:58 PM Dmitry Osipenko wrote:
> Oh, also what about GPIO-pinctrl suspend resume ordering .. is it okay that
> pinctrl
> will be resumed after GPIO? Shouldn't a proper pin-muxing be selected at
> first?
Thierry sent some initial patches about this I think. We need to us
On Mon, Jul 01, 2019 at 11:06:34AM +, Hallsmark, Per wrote:
> +struct proc_dir_entry *proc_net_mkdir(struct net *net, const char *name,
> + struct proc_dir_entry *parent)
> +{
> + struct proc_dir_entry *pde;
> +
> + pde = proc_mkdir_data(name, 0, paren
On Mon, Jul 1, 2019 at 4:26 PM Geert Uytterhoeven
wrote:
> A new field init_valid_mask was added to struct gpio_chip, but it was
> not documented.
>
> Fixes: f8ec92a9f63b3b11 ("gpiolib: Add init_valid_mask exported function")
> Signed-off-by: Geert Uytterhoeven
Patch applied.
Yours,
Linus Wall
On Mon, Jul 1, 2019 at 4:27 PM Geert Uytterhoeven
wrote:
> Commit 372e722ea4dd4ca1 ("gpiolib: use descriptors internally") renamed
> the functions to use a "gpiod" prefix, and commit 79a9becda8940deb
> ("gpiolib: export descriptor-based GPIO interface") introduced the "raw"
> variants, but both c
Hello,
Sorry about another version after another round of embarrassment over
compilation issues. The same patches have gone through pm/linux-next and
linux-next/master earlier, not sure why the current issues never came up
before. Anyway, they were stupid coding mistakes :(
I have pushed these pa
dev_pm_qos_read_value() will soon need to support more constraint types
(min/max frequency) and will have another argument to it, i.e. type of
the constraint. While that is fine for the existing users of
dev_pm_qos_read_value(), but not that optimal for the callers of
__dev_pm_qos_read_value() and
This patch introduces the min-frequency and max-frequency device
constraints, which will be used by the cpufreq core to begin with.
Reviewed-by: Matthias Kaehlcke
Reviewed-by: Ulf Hansson
Signed-off-by: Viresh Kumar
Signed-off-by: Rafael J. Wysocki
---
drivers/base/power/qos.c | 111 +
This registers the notifiers for min/max frequency constraints with the
PM QoS framework. The constraints are also taken into consideration in
cpufreq_set_policy().
This also relocates cpufreq_policy_put_kobj() as it is required to be
called from cpufreq_policy_alloc() now.
refresh_frequency_limi
In order to allow dev_pm_qos_read_value() to read values for different
QoS requests, pass request type as a parameter to these routines.
For now, it only supports resume-latency request type but will be
extended to frequency limit (min/max) constraints later on.
Reviewed-by: Matthias Kaehlcke
Re
In order to use the same set of routines to register notifiers for
different request types, update the existing
dev_pm_qos_{add|remove}_notifier() routines with an additional
parameter: request-type.
For now, it only supports resume-latency request type but will be
extended to frequency limit (min
The implementation of intel_pstate_update_max_freq() is quite similar to
refresh_frequency_limits(), lets reuse it.
Finding minimum of policy->user_policy.max and policy->cpuinfo.max_freq
in intel_pstate_update_max_freq() is redundant as cpufreq_set_policy()
will call the ->verify() callback of in
This implements QoS requests to manage userspace configuration of min
and max frequency.
Reviewed-by: Matthias Kaehlcke
Reviewed-by: Ulf Hansson
Signed-off-by: Viresh Kumar
Signed-off-by: Rafael J. Wysocki
---
drivers/cpufreq/cpufreq.c | 87 ---
include/lin
On Mon, Jul 1, 2019 at 4:28 PM Geert Uytterhoeven
wrote:
> Obviously functions that are safe to be called from atomic contexts, can
> be called from non-atomic contexts, too.
>
> Signed-off-by: Geert Uytterhoeven
Patch applied.
Yours,
Linus Walleij
On Wed, Jul 3, 2019 at 12:33 AM Martin Blumenstingl
wrote:
> Return early if devm_gpiochip_add_data() returns an error instead of
> having two consecutive "if (!ret) ..." statements.
>
> Also make xway_stp_hw_init() return void because it unconditionally
> returns 0. While here also update the ke
On Wed, Jul 3, 2019 at 12:33 AM Martin Blumenstingl
wrote:
> Three module clock error handling improvements:
> - use devm_clk_get() so the clock instance can be freed if
> devm_gpiochip_add_data() fails later on
> - switch to clk_prepare_enable() so the driver is ready whenever the
> lantiq t
On Wed, Jul 3, 2019 at 12:33 AM Martin Blumenstingl
wrote:
> Use the xway_stp_{r,w}32 helpers in xway_stp_w32_mask instead of relying
> on ltq_{r,w}32 from the architecture specific .
> This will allow the driver to be compile-tested on all architectures
> that support MMIO.
>
> Signed-off-by: Ma
On Wed, Jul 3, 2019 at 12:33 AM Martin Blumenstingl
wrote:
> Enable compile-testing of the stp-xway GPIO driver now that it does not
> depend on any architecture specific includes anymore.
>
> Signed-off-by: Martin Blumenstingl
Patch applied.
Yours,
Linus Walleij
On Tue, Jul 2, 2019 at 12:54 PM Vinod Koul wrote:
> The bindings for msm8998-pinctrl was missing gpio-ranges and
> gpio-reserved-ranges, so document them as well
>
> Signed-off-by: Vinod Koul
Patch applied with Bjorn's ACK.
Yours,
Linus Walleij
On Tue, Jul 2, 2019 at 12:54 PM Vinod Koul wrote:
> From: Prasad Sodagudi
>
> Add the binding for the TLMM pinctrl block found in the SM8150 platform.
>
> Signed-off-by: Prasad Sodagudi
> Signed-off-by: Isaac J. Manjarres
> [vkoul: add missing nodes of gpio range and reserved
> rewrote
On 14.06.2019 17:36, YueHaibing wrote:
> Fix sparse warning:
>
> drivers/gpu/drm/bridge/sii902x.c:665:5: warning:
> symbol 'sii902x_audio_digital_mute' was not declared. Should it be static?
>
> Reported-by: Hulk Robot
> Signed-off-by: YueHaibing
> ---
> drivers/gpu/drm/bridge/sii902x.c | 3 ++-
Martin - a kind reminder.
Thanks,
Avri
> Subject: RE: [PATCH] scsi: uapi: ufs: Fix SPDX license identifier
>
> From: Avri Altman
> Date: Wed, Jun 12, 2019 at 14:34:37
>
> > added 'WITH Linux-syscall-note' exception, which is the officially
> > assigned exception identifier for the kernel sysca
On Thu, Jul 04, 2019 at 01:02:49AM +0200, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> Using acpi_device_get_power() outside of ACPI device initialization
> and ACPI sysfs is problematic due to the way in which power resources
> are handled by it, so unexport it and add a paragraph expl
Hi Greg,
On Thu, 4 Jul 2019 08:59:49 +0200 Greg KH wrote:
>
> Odd, I thought I pulled the usb-gadget tree into mine.
You did. So after it failed in your tree and I used yesterday's
version of your tree, the build then failed after I merged the
usb-gadget tree (which I do after merging your tree
On 7/4/2019 9:23 AM, anson.hu...@nxp.com wrote:
> From: Anson Huang
>
> Assign highest OPP as suspend OPP to reduce suspend/resume
> latency on i.MX8MM.
>
> Signed-off-by: Anson Huang
> ---
> arch/arm64/boot/dts/freescale/imx8mm.dtsi | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/
On Wed, Jul 3, 2019 at 3:50 PM Marc Zyngier wrote:
> On 03/07/2019 13:26, Linus Walleij wrote:
> > On Wed, Jul 3, 2019 at 11:24 AM tip-bot for Ard Biesheuvel
> > wrote:
> >
> >> Committer: Marc Zyngier
> >> CommitDate: Wed, 29 May 2019 10:42:19 +0100
> >>
> >> gpio: mb86s7x: Enable ACPI support
> On Wed, Jul 03, 2019 at 12:25:16AM -0700, jeyentam wrote:
> > Add NI PXIe-RS232, PXI-RS485 and PXIe-RS485 device IDs.
> >
> > Signed-off-by: jeyentam
> > ---
> > include/linux/pci_ids.h | 12
> > 1 file changed, 12 insertions(+)
>
> You have read the comment at the top of this fil
When I use the following command to power on a slot which has been
powered off already.
echo 1 > /sys/bus/pci/slots/22/power
It prints the following error:
-bash: echo: write error: No such device
But the slot is actually powered on and the devices is probed.
In function 'pciehp_sysfs_enable_slot(
On 2019-07-02 17:40, Colin King wrote:
From: Colin Ian King
There are several occasions where a negative cid value is passed
into wil_cid_valid and this is converted into a u8 causing the
range check of cid >= 0 to always succeed. Fix this by making
the cid argument an int to handle any -ve er
Hi, Leonard
> On 7/4/2019 9:23 AM, anson.hu...@nxp.com wrote:
> > From: Anson Huang
> >
> > Assign highest OPP as suspend OPP to reduce suspend/resume latency on
> > i.MX8MM.
> >
> > Signed-off-by: Anson Huang
> > ---
> > arch/arm64/boot/dts/freescale/imx8mm.dtsi | 1 +
> > 1 file changed, 1
On Thu, Jul 04, 2019 at 01:05:38AM +0200, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> After recent hibernation-related changes, there are no more callers
> of dev_pm_skip_next_resume_phases() except for the PM core itself
> in which it is more straightforward to run the statements from
Wed, Jul 03, 2019 at 08:18:51PM CEST, mkube...@suse.cz wrote:
>On Wed, Jul 03, 2019 at 01:49:33PM +0200, Jiri Pirko wrote:
>> Tue, Jul 02, 2019 at 01:50:09PM CEST, mkube...@suse.cz wrote:
>> >diff --git a/Documentation/networking/ethtool-netlink.txt
>> >b/Documentation/networking/ethtool-netlink.t
Fix Kconfig warning for PCMCIA_FDOMAIN symbol:
WARNING: unmet direct dependencies detected for SCSI_FDOMAIN
Depends on [n]: SCSI_LOWLEVEL [=n] && SCSI [=y]
Selected by [m]:
- PCMCIA_FDOMAIN [=m] && SCSI_LOWLEVEL_PCMCIA [=y] && SCSI [=y] && PCMCIA
[=m] && m && MODULES [=y]
Add SCSI_FDOMAIN
Wed, Jul 03, 2019 at 04:16:14PM CEST, mkube...@suse.cz wrote:
>On Wed, Jul 03, 2019 at 03:33:52PM +0200, Jiri Pirko wrote:
>> >+/* notifications */
>> >+
>> >+typedef void (*ethnl_notify_handler_t)(struct net_device *dev,
>> >+ struct netlink_ext_ack *extack,
>> >+
> Subject: [EXTERNAL] [priv] Re: [PATCH 1/2] serial/8250: Add support for
> NI-Serial
> PXI/PXIe+485 devices.
>
> On 02.07.19 05:23, jeyentam wrote:
>
> Hi,
>
> better writing to you personally, off-list.
>
> > Add support for NI-Serial PXIe-RS232, PXI-RS485 and PXIe-RS485 devices.
> >
> > Sig
>
>Hi,
>
>On Thu, Jul 4, 2019 at 9:59 AM Greg KH wrote:
>>
>> On Thu, Jul 04, 2019 at 04:34:58PM +1000, Stephen Rothwell wrote:
>> > Hi all,
>> >
>> > After merging the usb tree, today's linux-next build (arm
>> > multi_v7_defconfig) failed like this:
>> >
>> > arm-linux-gnueabi-ld: drivers/usb/dw
> On Wed, Jul 03, 2019 at 12:24:35AM -0700, jeyentam wrote:
> > Add support for NI-Serial PXIe-RS232, PXI-RS485 and PXIe-RS485 devices.
> >
> > Signed-off-by: jeyentam
>
> I need a "full" name here please.
Ok, will do so.
>
> Also, this patch breaks the build, which is not allowed, and makes m
Wed, Jul 03, 2019 at 04:37:22PM CEST, mkube...@suse.cz wrote:
>On Wed, Jul 03, 2019 at 03:44:52PM +0200, Jiri Pirko wrote:
>> Tue, Jul 02, 2019 at 01:50:19PM CEST, mkube...@suse.cz wrote:
>> >Introduce file net/ethtool/common.c for code shared by ioctl and netlink
>> >ethtool interface. Move name t
> On Mon, Jul 01, 2019 at 08:23:23PM -0700, jeyentam wrote:
> > Add support for NI-Serial PXIe-RS232, PXI-RS485 and PXIe-RS485 devices.
> >
> > Signed-off-by: jeyentam
> > ---
> > drivers/tty/serial/8250/8250_pci.c | 879 +++--
> > 1 file changed, 582 insertions(+), 297 de
On Tue, Jun 25, 2019 at 11:04 PM Nick Desaulniers
wrote:
> Clang produces references to __aeabi_uidivmod and __aeabi_idivmod for
> arm-linux-gnueabi and arm-linux-gnueabihf targets incorrectly when AEABI
> is not selected (such as when OABI_COMPAT is selected).
>
> While this means that OABI user
On Thu, Jul 04, 2019 at 07:55:33AM +, Je Yen Tam wrote:
> > On Wed, Jul 03, 2019 at 12:24:35AM -0700, jeyentam wrote:
> > > Add support for NI-Serial PXIe-RS232, PXI-RS485 and PXIe-RS485 devices.
> > >
> > > Signed-off-by: jeyentam
> >
> > I need a "full" name here please.
>
> Ok, will do so
On Thu, Jul 04, 2019 at 06:58:39AM +, Je Yen Tam wrote:
> > On Wed, Jul 03, 2019 at 12:25:16AM -0700, jeyentam wrote:
> > > Add NI PXIe-RS232, PXI-RS485 and PXIe-RS485 device IDs.
> > >
> > > Signed-off-by: jeyentam
> > > ---
> > > include/linux/pci_ids.h | 12
> > > 1 file chang
Tue, Jul 02, 2019 at 01:50:29PM CEST, mkube...@suse.cz wrote:
[...]
>@@ -87,6 +89,64 @@ enum {
> ETHTOOL_A_BITSET_MAX = (__ETHTOOL_A_BITSET_CNT - 1)
You don't need "()". Same for the others below.
> };
>
>+/* string sets */
>+
>+enum {
>+ ETHTOOL_A_STRING_UNSPEC,
>+ ETHTOOL_A
> -Original Message-
> From: Greg KH
> Sent: Thursday, July 4, 2019 4:16 PM
> To: Je Yen Tam
> Cc: linux-ser...@vger.kernel.org; linux-kernel@vger.kernel.org
> Subject: [EXTERNAL] Re: Re: [PATCH V2 2/2] PCI: Add NI-Serial PXI/PXIe+485
> device
> IDs
>
> On Thu, Jul 04, 2019 at 06:58:39A
On 2019/7/4 14:46, Jia He wrote:
>
> On 2019/6/29 10:42, Xiongfeng Wang wrote:
>> We set 'cpu_possible_mask' based on the enabled GICC node in MADT. If
>> the GICC node is disabled, we will skip initializing the kernel data
>> structure for that CPU.
>>
>> To support CPU hotplug, we need to ini
> -Original Message-
> From: Greg KH
> Sent: Thursday, July 4, 2019 4:15 PM
> To: Je Yen Tam
> Cc: linux-ser...@vger.kernel.org; linux-kernel@vger.kernel.org
> Subject: [EXTERNAL] Re: Re: [PATCH V2 1/2] serial/8250: Add support for
> NI-Serial
> PXI/PXIe+485 devices
>
> On Thu, Jul 0
On Thu, Jul 04, 2019 at 04:24:35PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> After merging the driver-core tree, today's linux-next build (x86_64
> allmodconfig) produced this warning:
>
> fs/orangefs/orangefs-debugfs.c: In function 'orangefs_debugfs_init':
> fs/orangefs/orangefs-debugfs.c:193
On Thu, Jul 04, 2019 at 09:58:43AM +0300, Oded Gabbay wrote:
> Hello Greg,
>
> This is v2 of the pull request for habanalabs driver for kernel 5.3.
>
> v2 contains the missing sign-off-by tags for the relevant commits.
>
> The commits mostly contains improvements to the existing code base.
> Not
Hi,
Pawel Laszczak writes:
>>
>>Hi,
>>
>>On Thu, Jul 4, 2019 at 9:59 AM Greg KH wrote:
>>>
>>> On Thu, Jul 04, 2019 at 04:34:58PM +1000, Stephen Rothwell wrote:
>>> > Hi all,
>>> >
>>> > After merging the usb tree, today's linux-next build (arm
>>> > multi_v7_defconfig) failed like this:
>>>
Hello!
On 03.07.2019 10:15, Mason Yang wrote:
Document the bindings used by the Macronix raw NAND controller.
Signed-off-by: Mason Yang
---
Documentation/devicetree/bindings/mtd/mxic-nand.txt | 20
1 file changed, 20 insertions(+)
create mode 100644 Documentation/dev
On Thu, Jul 4, 2019 at 10:13 AM Linus Walleij wrote:
> On Tue, Jun 25, 2019 at 11:04 PM Nick Desaulniers
> wrote:
>
> > Clang produces references to __aeabi_uidivmod and __aeabi_idivmod for
> > arm-linux-gnueabi and arm-linux-gnueabihf targets incorrectly when AEABI
> > is not selected (such as
On Thu, Jul 04, 2019 at 11:25:16AM +0300, Felipe Balbi wrote:
>
> Hi,
>
> Pawel Laszczak writes:
>
> >>
> >>Hi,
> >>
> >>On Thu, Jul 4, 2019 at 9:59 AM Greg KH wrote:
> >>>
> >>> On Thu, Jul 04, 2019 at 04:34:58PM +1000, Stephen Rothwell wrote:
> >>> > Hi all,
> >>> >
> >>> > After merging the
On Thu, Jul 4, 2019 at 12:18 AM Alistair Francis wrote:
> On Wed, Jul 3, 2019 at 12:47 PM Arnd Bergmann wrote:
> > On Wed, Jul 3, 2019 at 8:45 PM Alistair Francis
> > wrote:
> > > What I don't understand though is how that impacted this struct, it
> > > doesn't use clock_t at all, everything in
After calling of_node_put() on the codec_ep and codec_port variables,
they are still being used, which may result in use-after-free.
We fix this issue by calling of_node_put() after the last usage.
Fixes: fce9b90c1ab7 ("ASoC: audio-graph-card: cleanup DAI link loop method -
step2")
Signed-off-by:
Hi all,
Today's linux-next merge of the pidfd tree got a conflict in:
kernel/fork.c
between commits:
6fd2fe494b17 ("copy_process(): don't use ksys_close() on cleanups")
28dd29c06d0d ("fork: return proper negative error code")
from Linus' tree and commit:
7f192e3cd316 ("fork: add clone
On Fri, 2019-06-28 at 18:13 +0300, Oshri Alkoby wrote:
The long descriptions are still missing. Please take the time and write
a proper commit messages that clearly tell what the patch does.
Check out tpm_tis_core.c and tpm_tis_spi.c. TPM TIS driver implements
that spec so you should only impleme
Hi,
Greg KH writes:
> On Thu, Jul 04, 2019 at 11:25:16AM +0300, Felipe Balbi wrote:
>>
>> Hi,
>>
>> Pawel Laszczak writes:
>>
>> >>
>> >>Hi,
>> >>
>> >>On Thu, Jul 4, 2019 at 9:59 AM Greg KH wrote:
>> >>>
>> >>> On Thu, Jul 04, 2019 at 04:34:58PM +1000, Stephen Rothwell wrote:
>> >>> > Hi
Wed, Jul 03, 2019 at 07:53:39PM CEST, mkube...@suse.cz wrote:
>On Wed, Jul 03, 2019 at 04:25:10PM +0200, Jiri Pirko wrote:
>> Tue, Jul 02, 2019 at 01:50:24PM CEST, mkube...@suse.cz wrote:
>>
>> [...]
>>
>> >+/* generic ->doit() handler for GET type requests */
>> >+static int ethnl_g
Platform drivers now have the option to have the platform core create
and remove any needed sysfs attribute files. So take advantage of that
and do not register "by hand" a sysfs group of attributes.
Signed-off-by: Greg Kroah-Hartman
---
drivers/uio/uio_fsl_elbc_gpcm.c | 23
If a platform driver wants to add a sysfs group, it has to do so in a
racy way, adding it after the driver is bound. To resolve this issue,
have the platform driver core do this for the driver, making the
individual drivers logic smaller and simpler, and solving the race at
the same time.
All of
Platform drivers now have the option to have the platform core create
and remove any needed sysfs attribute files. So take advantage of that
and do not register "by hand" a bunch of sysfs files.
Cc: Bartlomiej Zolnierkiewicz
Cc: dri-de...@lists.freedesktop.org
Cc: linux-fb...@vger.kernel.org
Sig
Platform drivers now have the option to have the platform core create
and remove any needed sysfs attribute files. So take advantage of that
and do not register "by hand" a lid sysfs file.
Cc: Darren Hart
Cc: Andy Shevchenko
Cc: Thomas Gleixner
Cc: Ingo Molnar
Cc: Borislav Petkov
Cc: "H. Pet
Platform drivers now have the option to have the platform core create
and remove any needed sysfs attribute files. So take advantage of that
and do not register "by hand" a sysfs group of attributes.
Cc: Sudeep Holla
Cc: linux-arm-ker...@lists.infradead.org
Signed-off-by: Greg Kroah-Hartman
---
Platform drivers now have the option to have the platform core create
and remove any needed sysfs attribute files. So take advantage of that
and do not register "by hand" a bunch of sysfs files.
Cc: Darren Hart
Cc: Andy Shevchenko
Cc: Thomas Gleixner
Cc: Ingo Molnar
Cc: Borislav Petkov
Cc: "
Platform drivers now have the option to have the platform core create
and remove any needed sysfs attribute files. So take advantage of that
and do not register "by hand" a sysfs file.
Cc: Darren Hart
Cc: Andy Shevchenko
Cc: platform-driver-...@vger.kernel.org
Signed-off-by: Greg Kroah-Hartman
Platform drivers like to add sysfs groups to their device, but right now
they have to do it "by hand". The driver core should handle this for
them, but there is no way to get to the bus-default attribute groups as
all platform devices are "special and unique" one-off drivers/devices.
To combat th
Platform drivers now have the option to have the platform core create
and remove any needed sysfs attribute files. So take advantage of that
and do not register "by hand" a bunch of sysfs files.
Cc: Tony Prisk
Cc: Bartlomiej Zolnierkiewicz
Cc: linux-arm-ker...@lists.infradead.org
Cc: dri-de...@
Platform drivers now have the option to have the platform core create
and remove any needed sysfs attribute files. So take advantage of that
and do not register "by hand" a sysfs group of attributes.
Cc: Dmitry Torokhov
Cc: Andy Shevchenko
Cc: Florian Fainelli
Cc: linux-in...@vger.kernel.org
S
This is a driver, do not call "raw" sysfs functions, instead call driver
core ones. Specifically convert the use of sysfs_create_file() and
sysfs_remove_file() to use device_create_file() and device_remove_file()
Cc: Greg Kroah-Hartman
Cc: Jiri Slaby
Cc: linux-ser...@vger.kernel.org
Signed-off-
Tue, Jul 02, 2019 at 01:50:24PM CEST, mkube...@suse.cz wrote:
[...]
>+/* The structure holding data for unified processing GET requests consists of
>+ * two parts: request info and reply data. Request info is related to client
>+ * request and for dump request it stays constant through all proce
Hi,
On 01/07/19 07:51, Tejun Heo wrote:
> Hello,
>
> On Mon, Jul 01, 2019 at 10:27:31AM +0200, Peter Zijlstra wrote:
> > IIRC TJ figured it wasn't strictly required to fix the lock invertion at
> > that time and they sorted it differently. If I (re)read the thread
> > correctly the other day, he
Hi Anson,
On Mon, 2019-07-01 at 17:39 +0800, anson.hu...@nxp.com wrote:
> From: Anson Huang
>
> i.MX8MM SoC has a subset of i.MX8MQ IP block variant, it can reuse
> the i.MX8MQ reset controller driver and just skip those non-existing
> IP blocks, add support for i.MX8MM SoC reset control.
>
> S
On Thu, Jul 04, 2019 at 10:29:35AM +0200, Arnd Bergmann wrote:
> On Thu, Jul 4, 2019 at 10:13 AM Linus Walleij
> wrote:
> > On Tue, Jun 25, 2019 at 11:04 PM Nick Desaulniers
> > wrote:
> >
> > > Clang produces references to __aeabi_uidivmod and __aeabi_idivmod for
> > > arm-linux-gnueabi and ar
If REGMAP_SPI is m and RTC_DRV_PCF2123 is y,
drivers/rtc/rtc-pcf2123.o: In function `pcf2123_probe':
rtc-pcf2123.c:(.text+0xb2b): undefined reference to `__devm_regmap_init_spi'
Select REGMAP_SPI as RTC_DRV_DS1347 driver does.
Reported-by: Hulk Robot
Fixes: 790d033933b8 ("rtc: pcf2123: port to
Hi all,
Today's linux-next merge of the hmm tree got a conflict in:
include/linux/ioport.h
between commit:
ae9e13d621d6 ("x86/e820, ioport: Add a new I/O resource descriptor
IORES_DESC_RESERVED")
5da04cc86d12 ("x86/mm: Rework ioremap resource mapping determination")
from the tip tree an
On Wed, Jul 03, 2019 at 05:30:53PM +, Tyler Baicar OS wrote:
> Hello Andrew,
>
> Thank you for the feedback!
>
> On Wed, Jul 3, 2019 at 5:26 AM Andrew Murray wrote:
> >
> > On Tue, Jul 02, 2019 at 04:51:38PM +, Tyler Baicar OS wrote:
> > > Add support for parsing the ARM Error Source Tab
>
>
>Hi,
>
>Pawel Laszczak writes:
>
>>>
>>>Hi,
>>>
>>>On Thu, Jul 4, 2019 at 9:59 AM Greg KH wrote:
On Thu, Jul 04, 2019 at 04:34:58PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> After merging the usb tree, today's linux-next build (arm
> multi_v7_defconfig) failed
Hi CK-Hu,
On 01/07/2019 05:55, CK Hu wrote:
> Hi, Matthias:
>
> On Fri, 2018-11-30 at 16:59 +0800, Matthias Brugger wrote:
>>
>> On 30/11/2018 07:43, Stephen Boyd wrote:
>>> Quoting Matthias Brugger (2018-11-21 09:09:52)
On 21/11/2018 17:46, Stephen Boyd wrote:
> Quoting Rob He
Hi, Philipp
> On Mon, 2019-07-01 at 17:39 +0800, anson.hu...@nxp.com wrote:
> > From: Anson Huang
> >
> > i.MX8MM SoC has a subset of i.MX8MQ IP block variant, it can reuse the
> > i.MX8MQ reset controller driver and just skip those non-existing IP
> > blocks, add support for i.MX8MM SoC reset co
* Add the gpio number, so the button subsystem can find the right gpio.
* Change also the keycode from KEY_SETUP to KEY_RESTART, because it
seems more expressive to me and in the Alix-Board, which is the
predecessor, there isthis keycode defined too. I think this is also
intended by Pcengines
On APUx we have also mpcie2/mpcie3 reset pins. To make it possible to reset
the ports from the userspace, add the definition to this platform
device. The gpio can then be exported by the legancy gpio subsystem to
toggle the mpcie reset pin.
Signed-off-by: Florian Eckert
---
drivers/platform/x86/
1 - 100 of 652 matches
Mail list logo
