Hi Paul,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 0c2b6dc4fd4fa13796b319aae969a009f03222c6
commit: cf2a5e0bb4c66e8c43caf9f1be93a1bd7fd07b17 MIPS: Support generating
Flattened Image Trees (.itb)
date: 2
Hi Paul,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 0c2b6dc4fd4fa13796b319aae969a009f03222c6
commit: cf2a5e0bb4c66e8c43caf9f1be93a1bd7fd07b17 MIPS: Support generating
Flattened Image Trees (.itb)
date: 2
On Sat, 22 Oct 2016, SF Markus Elfring wrote:
> >> @@ -494,12 +494,11 @@ static int sn2_ptc_seq_show(struct seq_file *file,
> >> void *data)
> >>int cpu;
> >>
> >>cpu = *(loff_t *) data;
> >> -
> >> - if (!cpu) {
> >> + if (!cpu)
> >>seq_printf(file,
> >> -
On Sat, 22 Oct 2016, SF Markus Elfring wrote:
> >> @@ -494,12 +494,11 @@ static int sn2_ptc_seq_show(struct seq_file *file,
> >> void *data)
> >>int cpu;
> >>
> >>cpu = *(loff_t *) data;
> >> -
> >> - if (!cpu) {
> >> + if (!cpu)
> >>seq_printf(file,
> >> -
Hi James,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 0c2b6dc4fd4fa13796b319aae969a009f03222c6
commit: 034827c727f7f3946a18355b63995b402c226c82 MIPS: Fix -mabi=64 build of
vdso.lds
date: 12 days ago
config:
Hi James,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 0c2b6dc4fd4fa13796b319aae969a009f03222c6
commit: 034827c727f7f3946a18355b63995b402c226c82 MIPS: Fix -mabi=64 build of
vdso.lds
date: 12 days ago
config:
Hi Paul,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 0c2b6dc4fd4fa13796b319aae969a009f03222c6
commit: eed0eabd12ef061821cbfa20d903476e07645320 MIPS: generic: Introduce
generic DT-based board support
date: 2
Hi Paul,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 0c2b6dc4fd4fa13796b319aae969a009f03222c6
commit: eed0eabd12ef061821cbfa20d903476e07645320 MIPS: generic: Introduce
generic DT-based board support
date: 2
On 20 October 2016 at 09:21, Sinan Kaya wrote:
> The SCI penalize function was removed in two steps (first refactor
> and then remove) and these changes are reverted here in one go.
>
> The commit 103544d86976 ("ACPI,PCI,IRQ: reduce resource requirements")
> refactored the
On 20 October 2016 at 09:21, Sinan Kaya wrote:
> This reverts commit f7eca374f000 ("ACPI,PCI,IRQ: separate ISA penalty
> calculation") and commit 487cf917ed0d ("revert "ACPI, PCI, IRQ: remove
> redundant code in acpi_irq_penalty_init()"").
>
> Now that we understand the real
On 20 October 2016 at 09:21, Sinan Kaya wrote:
> The SCI penalize function was removed in two steps (first refactor
> and then remove) and these changes are reverted here in one go.
>
> The commit 103544d86976 ("ACPI,PCI,IRQ: reduce resource requirements")
> refactored the original code so that
On 20 October 2016 at 09:21, Sinan Kaya wrote:
> This reverts commit f7eca374f000 ("ACPI,PCI,IRQ: separate ISA penalty
> calculation") and commit 487cf917ed0d ("revert "ACPI, PCI, IRQ: remove
> redundant code in acpi_irq_penalty_init()"").
>
> Now that we understand the real issue (SCI and ISA
On 20 October 2016 at 09:21, Sinan Kaya wrote:
> The penalty determination of ISA IRQ goes through 4 paths.
> 1. assign PCI_USING during power up via acpi_irq_penalty_init.
> 2. update the penalty with acpi_penalize_isa_irq function based on the
> active parameter.
> 3.
On 20 October 2016 at 09:21, Sinan Kaya wrote:
> The penalty determination of ISA IRQ goes through 4 paths.
> 1. assign PCI_USING during power up via acpi_irq_penalty_init.
> 2. update the penalty with acpi_penalize_isa_irq function based on the
> active parameter.
> 3. kernel command line
Signed-off-by: Peter Rosin
---
drivers/iio/potentiometer/mcp4531.c | 104 +---
1 file changed, 62 insertions(+), 42 deletions(-)
diff --git a/drivers/iio/potentiometer/mcp4531.c
b/drivers/iio/potentiometer/mcp4531.c
index
Signed-off-by: Peter Rosin
---
drivers/iio/potentiometer/mcp4531.c | 104 +---
1 file changed, 62 insertions(+), 42 deletions(-)
diff --git a/drivers/iio/potentiometer/mcp4531.c
b/drivers/iio/potentiometer/mcp4531.c
index 13b6ae2fcf7b..0d1bcf89ae17 100644
---
The DAC is used to find the peak level of an alternating voltage input
signal by a binary search using the output of a comparator wired to
an interrupt pin. Like so:
_
| \
input +-->---|+ \
| \
The DAC is used to find the peak level of an alternating voltage input
signal by a binary search using the output of a comparator wired to
an interrupt pin. Like so:
_
| \
input +-->---|+ \
| \
Hi Rich,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 0c2b6dc4fd4fa13796b319aae969a009f03222c6
commit: b4214e41b7152b1964a3421a40251d202ae2d2c0 sh: add SMP support for J2
date: 3 months ago
config:
Hi Rich,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 0c2b6dc4fd4fa13796b319aae969a009f03222c6
commit: b4214e41b7152b1964a3421a40251d202ae2d2c0 sh: add SMP support for J2
date: 3 months ago
config:
On Fri, Oct 21, 2016 at 2:09 AM, Neil Armstrong wrote:
> Since the I2C sx150x GPIO expander driver uses platform_data to manage
> the pins configurations, rewrite the driver as a pinctrl driver using
> pinconf to get/set pin configurations from DT or debugfs.
>
> The
On Fri, Oct 21, 2016 at 2:09 AM, Neil Armstrong wrote:
> Since the I2C sx150x GPIO expander driver uses platform_data to manage
> the pins configurations, rewrite the driver as a pinctrl driver using
> pinconf to get/set pin configurations from DT or debugfs.
>
> The pinctrl driver is
Hi Will,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 0c2b6dc4fd4fa13796b319aae969a009f03222c6
commit: da48d094ce5d7c7dcdad9011648a81c42fd1c2ef Kconfig: remove
HAVE_LATENCYTOP_SUPPORT
date: 9 months ago
Hi Will,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 0c2b6dc4fd4fa13796b319aae969a009f03222c6
commit: da48d094ce5d7c7dcdad9011648a81c42fd1c2ef Kconfig: remove
HAVE_LATENCYTOP_SUPPORT
date: 9 months ago
Hello Linus,
Here are the outstanding target-pending fixes for v4.9-rc2. Please go
ahead and pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/nab/target-pending.git master
This includes:
- Fix v4.1.y+ reference leak regression with concurrent TMR ABORT_TASK +
session shutdown.
Hello Linus,
Here are the outstanding target-pending fixes for v4.9-rc2. Please go
ahead and pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/nab/target-pending.git master
This includes:
- Fix v4.1.y+ reference leak regression with concurrent TMR ABORT_TASK +
session shutdown.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 0c2b6dc4fd4fa13796b319aae969a009f03222c6
commit: 034827c727f7f3946a18355b63995b402c226c82 MIPS: Fix -mabi=64 build of
vdso.lds
date: 12 days ago
config: mips-decstation_defconfig (attached as .config)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 0c2b6dc4fd4fa13796b319aae969a009f03222c6
commit: 034827c727f7f3946a18355b63995b402c226c82 MIPS: Fix -mabi=64 build of
vdso.lds
date: 12 days ago
config: mips-decstation_defconfig (attached as .config)
Hi Alistair,
On Fri, Oct 21, 2016 at 05:22:54PM +1100, Alistair Popple wrote:
From what I can tell it seems that kernels without this patch will try
and use this memory even if it is marked in the device-tree as
status="disabled" which could lead to problems for older kernels when
we start
Hi Alistair,
On Fri, Oct 21, 2016 at 05:22:54PM +1100, Alistair Popple wrote:
From what I can tell it seems that kernels without this patch will try
and use this memory even if it is marked in the device-tree as
status="disabled" which could lead to problems for older kernels when
we start
Your e-mail has been blocked due to detection of unsafe file attachment.
--- Additional Information ---:
Subject:
Sender: linux-kernel@vger.kernel.org
Time received: 10/22/2016 11:14:24 PM
Message
ID:<147717805956.1197.11354522112670710...@173-13-69-253-newengland.hfc.comcastbusiness.net>
Your e-mail has been blocked due to detection of unsafe file attachment.
--- Additional Information ---:
Subject:
Sender: linux-kernel@vger.kernel.org
Time received: 10/22/2016 11:14:24 PM
Message
ID:<147717805956.1197.11354522112670710...@173-13-69-253-newengland.hfc.comcastbusiness.net>
On Sat, Oct 22, 2016 at 09:27:59PM +0200, Stefan Richter wrote:
> Adding Cc: linux1394-devel, dropping several Ccs, no additional comment.
>
> On Oct 22 Stefan Richter wrote:
> > On Oct 20 Jarod Wilson wrote:
> > > firewire-net:
> > > - set min/max_mtu
> > > - remove fwnet_change_mtu
> > [...]
On Sat, Oct 22, 2016 at 09:27:59PM +0200, Stefan Richter wrote:
> Adding Cc: linux1394-devel, dropping several Ccs, no additional comment.
>
> On Oct 22 Stefan Richter wrote:
> > On Oct 20 Jarod Wilson wrote:
> > > firewire-net:
> > > - set min/max_mtu
> > > - remove fwnet_change_mtu
> > [...]
Hi!
These two drivers share the fact that they wrap another iio channel,
and I use the first in combination with the second, which is why I'm
submitting them as a pair.
The first driver is a simple wrapper converting an iio dpot into an
iio dac. It only changes the unit and scale. It also does
Signed-off-by: Peter Rosin
---
.../devicetree/bindings/iio/dac/dpot-dac.txt | 41 ++
MAINTAINERS| 6
2 files changed, 47 insertions(+)
create mode 100644
Signed-off-by: Peter Rosin
---
.../bindings/iio/adc/envelope-detector.txt | 55 ++
MAINTAINERS| 6 +++
2 files changed, 61 insertions(+)
create mode 100644
Signed-off-by: Peter Rosin
---
.../devicetree/bindings/iio/dac/dpot-dac.txt | 41 ++
MAINTAINERS| 6
2 files changed, 47 insertions(+)
create mode 100644 Documentation/devicetree/bindings/iio/dac/dpot-dac.txt
diff --git
Signed-off-by: Peter Rosin
---
.../bindings/iio/adc/envelope-detector.txt | 55 ++
MAINTAINERS| 6 +++
2 files changed, 61 insertions(+)
create mode 100644
Documentation/devicetree/bindings/iio/adc/envelope-detector.txt
diff
Hi!
These two drivers share the fact that they wrap another iio channel,
and I use the first in combination with the second, which is why I'm
submitting them as a pair.
The first driver is a simple wrapper converting an iio dpot into an
iio dac. It only changes the unit and scale. It also does
It is assumed the that the dpot is used as a voltage divider between the
current dpot wiper setting and the maximum resistance of the dpot. The
divided voltage is provided by a vref regulator.
.--.
.---. | |
| vref |--'.---.
| regulator |--.
Signed-off-by: Peter Rosin
---
Documentation/devicetree/bindings/vendor-prefixes.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/vendor-prefixes.txt
b/Documentation/devicetree/bindings/vendor-prefixes.txt
index
It is assumed the that the dpot is used as a voltage divider between the
current dpot wiper setting and the maximum resistance of the dpot. The
divided voltage is provided by a vref regulator.
.--.
.---. | |
| vref |--'.---.
| regulator |--.
Signed-off-by: Peter Rosin
---
Documentation/devicetree/bindings/vendor-prefixes.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/vendor-prefixes.txt
b/Documentation/devicetree/bindings/vendor-prefixes.txt
index f0a48ea78659..a437120a7eee 100644
---
On Sat, Oct 22, 2016 at 09:46:24AM +0200, Sven Eckelmann wrote:
> The maximum MTU is defined via the slave devices of an batman-adv
> interface. Thus it is not possible to calculate the max_mtu during the
> creation of the batman-adv device when no slave devices are attached. Doing
> so would for
On Sat, Oct 22, 2016 at 09:46:24AM +0200, Sven Eckelmann wrote:
> The maximum MTU is defined via the slave devices of an batman-adv
> interface. Thus it is not possible to calculate the max_mtu during the
> creation of the batman-adv device when no slave devices are attached. Doing
> so would for
Hi Guenter,
First bad commit (maybe != root cause):
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 0c2b6dc4fd4fa13796b319aae969a009f03222c6
commit: 398c7500a1f5f74e207bd2edca1b1721b3cc1f1e MIPS: VDSO: Fix build error
with binutils 2.24 and earlier
Hi Guenter,
First bad commit (maybe != root cause):
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 0c2b6dc4fd4fa13796b319aae969a009f03222c6
commit: 398c7500a1f5f74e207bd2edca1b1721b3cc1f1e MIPS: VDSO: Fix build error
with binutils 2.24 and earlier
Hi Vincent,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 0c2b6dc4fd4fa13796b319aae969a009f03222c6
commit: 3194c6870158e305dac2af52f83681e9cb67280f NFC: nfcmrvl: add firmware
download support
date: 12 months
Hi Vincent,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 0c2b6dc4fd4fa13796b319aae969a009f03222c6
commit: 3194c6870158e305dac2af52f83681e9cb67280f NFC: nfcmrvl: add firmware
download support
date: 12 months
Hi Alex,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 0c2b6dc4fd4fa13796b319aae969a009f03222c6
commit: ebb5e78cc63417a35254a791de66e1cc84f963cc MIPS: Initial implementation
of a VDSO
date: 12 months ago
Hi Alex,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 0c2b6dc4fd4fa13796b319aae969a009f03222c6
commit: ebb5e78cc63417a35254a791de66e1cc84f963cc MIPS: Initial implementation
of a VDSO
date: 12 months ago
From: Rafael J. Wysocki
There may be reasons to use generic cpufreq governors (eg. schedutil)
on Intel platforms instead of the intel_pstate driver's internal
governor. However, that currently can only be done by disabling
intel_pstate altogether and using the
From: Rafael J. Wysocki
There may be reasons to use generic cpufreq governors (eg. schedutil)
on Intel platforms instead of the intel_pstate driver's internal
governor. However, that currently can only be done by disabling
intel_pstate altogether and using the acpi-cpufreq driver instead
of it,
On Saturday, October 22, 2016 06:37:35 PM Borislav Petkov wrote:
> On Fri, Oct 21, 2016 at 11:28:29PM +0200, Rafael J. Wysocki wrote:
> > Boris, all fine here?
>
> Short answer: Yeah, looks ok to me.
>
> Longer answer: I mean, this way ghes_proc() *actually* propagates the
> return value of
On Saturday, October 22, 2016 06:37:35 PM Borislav Petkov wrote:
> On Fri, Oct 21, 2016 at 11:28:29PM +0200, Rafael J. Wysocki wrote:
> > Boris, all fine here?
>
> Short answer: Yeah, looks ok to me.
>
> Longer answer: I mean, this way ghes_proc() *actually* propagates the
> return value of
On Thu, Oct 20, 2016 at 07:58:57PM -0700, Sinan Kaya wrote:
> On 10/20/2016 7:31 PM, Bjorn Helgaas wrote:
> ...
> > And I don't think it fixes a user-visible problem, so it doesn't need
> > to be applied immediately. I'm not sure this is worth doing by
> > itself; maybe it should wait until we
On Thu, Oct 20, 2016 at 07:58:57PM -0700, Sinan Kaya wrote:
> On 10/20/2016 7:31 PM, Bjorn Helgaas wrote:
> ...
> > And I don't think it fixes a user-visible problem, so it doesn't need
> > to be applied immediately. I'm not sure this is worth doing by
> > itself; maybe it should wait until we
On Sat, Oct 15, 2016 at 12:31:05AM -0400, Sinan Kaya wrote:
> The change introduced in commit 103544d86976 ("ACPI,PCI,IRQ: reduce
> resource requirements") removed PCI_USING penalty from
> acpi_pci_link_allocate function as there is no longer a fixed size penalty
> array for both PCI interrupts
On Sat, Oct 15, 2016 at 12:31:05AM -0400, Sinan Kaya wrote:
> The change introduced in commit 103544d86976 ("ACPI,PCI,IRQ: reduce
> resource requirements") removed PCI_USING penalty from
> acpi_pci_link_allocate function as there is no longer a fixed size penalty
> array for both PCI interrupts
On Saturday, October 22, 2016 11:58:51 AM Greg Kroah-Hartman wrote:
> On Fri, Oct 21, 2016 at 11:02:13PM +0200, Rafael J. Wysocki wrote:
> > On Friday, October 21, 2016 11:17:23 AM Greg Kroah-Hartman wrote:
> > > This is the start of the stable review cycle for the 4.8.4 release.
> > > There are
On Saturday, October 22, 2016 11:58:51 AM Greg Kroah-Hartman wrote:
> On Fri, Oct 21, 2016 at 11:02:13PM +0200, Rafael J. Wysocki wrote:
> > On Friday, October 21, 2016 11:17:23 AM Greg Kroah-Hartman wrote:
> > > This is the start of the stable review cycle for the 4.8.4 release.
> > > There are
Hi,
The patch set that can be downloaded at [1] provides a different approach to /
dev/random which I call Linux Random Number Generator (LRNG) to collect
entropy within the Linux kernel. The main improvements compared to the legacy
/dev/random is to provide sufficient entropy during boot time
Hi,
The patch set that can be downloaded at [1] provides a different approach to /
dev/random which I call Linux Random Number Generator (LRNG) to collect
entropy within the Linux kernel. The main improvements compared to the legacy
/dev/random is to provide sufficient entropy during boot time
On Thu, Oct 20, 2016 at 08:58:14PM -0500, Bjorn Helgaas wrote:
> On Wed, Oct 19, 2016 at 06:21:03PM -0400, Sinan Kaya wrote:
> > The SCI penalize function was removed in two steps (first refactor
> > and then remove) and these changes are reverted here in one go.
> >
> > The commit 103544d86976
On Thu, Oct 20, 2016 at 08:58:14PM -0500, Bjorn Helgaas wrote:
> On Wed, Oct 19, 2016 at 06:21:03PM -0400, Sinan Kaya wrote:
> > The SCI penalize function was removed in two steps (first refactor
> > and then remove) and these changes are reverted here in one go.
> >
> > The commit 103544d86976
The commit: a55944ca82d287ca099ca90413af857af9086773 has posed some extra
restrictions on blanking and unblanking frame buffer device.
Unfortunately, pwm_bl driver's probe did not initialize members of
struct backlight_device necessary for further blank/unblank operation.
This code in case of
The commit: a55944ca82d287ca099ca90413af857af9086773 has posed some extra
restrictions on blanking and unblanking frame buffer device.
Unfortunately, pwm_bl driver's probe did not initialize members of
struct backlight_device necessary for further blank/unblank operation.
This code in case of
On 22/10/2016 13:37, Marc Zyngier wrote:
> Mason wrote:
>
>> In my mental picture of interrupts (which is obviously so
>> incomplete as to be wrong) interrupts are a way for hardware
>> to tell the CPU that they urgently need the CPU's attention.
>
> That's how the CPU interprets it, but this
On 22/10/2016 13:37, Marc Zyngier wrote:
> Mason wrote:
>
>> In my mental picture of interrupts (which is obviously so
>> incomplete as to be wrong) interrupts are a way for hardware
>> to tell the CPU that they urgently need the CPU's attention.
>
> That's how the CPU interprets it, but this
From: Jonathan Cameron
A large number of attributes can only take a limited range of values.
Currently in IIO this is handled by directly registering additional
*_available attributes thus providing this information to userspace.
It is desirable to provide this information via
From: Jonathan Cameron
A large number of attributes can only take a limited range of values.
Currently in IIO this is handled by directly registering additional
*_available attributes thus providing this information to userspace.
It is desirable to provide this information via the core for much
From: Cyrill Gorcunov
Date: Fri, 21 Oct 2016 13:03:44 +0300
> In criu we are actively using diag interface to collect sockets
> present in the system when dumping applications. And while for
> unix, tcp, udp[lite], packet, netlink it works as expected,
> the raw sockets do
From: Cyrill Gorcunov
Date: Fri, 21 Oct 2016 13:03:44 +0300
> In criu we are actively using diag interface to collect sockets
> present in the system when dumping applications. And while for
> unix, tcp, udp[lite], packet, netlink it works as expected,
> the raw sockets do not have. Thus add it.
On 10/22/2016 01:00 PM, Jagan Teki wrote:
> On Wed, Oct 5, 2016 at 5:30 PM, Cyrille Pitchen
> wrote:
>> Hi all,
>>
>> This series extends support of SPI protocols to new protocols such as
>> SPI x-2-2 and SPI x-4-4. Also spi_nor_scan() tries now to select the right
>>
On 10/22/2016 01:00 PM, Jagan Teki wrote:
> On Wed, Oct 5, 2016 at 5:30 PM, Cyrille Pitchen
> wrote:
>> Hi all,
>>
>> This series extends support of SPI protocols to new protocols such as
>> SPI x-2-2 and SPI x-4-4. Also spi_nor_scan() tries now to select the right
>> op codes, timing parameters
This is basically the same as module_misc_device but without the
presence of an exit/remove function. Similar in nature to the
commit f309d4443130bf814e991f836e919dca22df37ae ("platform_device:
better support builtin boilerplate avoidance").
Cc: Arnd Bergmann
Cc: Greg
This is basically the same as module_misc_device but without the
presence of an exit/remove function. Similar in nature to the
commit f309d4443130bf814e991f836e919dca22df37ae ("platform_device:
better support builtin boilerplate avoidance").
Cc: Arnd Bergmann
Cc: Greg Kroah-Hartman
This driver currently uses modular infrastructure but is controlled
by a bool Kconfig.
There is a general consensus from the DMA reviewers and maintainers
that "if it can be modular, it should be modular" in order to keep
the bzImage size under control for multi platform kernels.
Build tested
This driver currently uses modular infrastructure but is controlled
by a bool Kconfig.
There is a general consensus from the DMA reviewers and maintainers
that "if it can be modular, it should be modular" in order to keep
the bzImage size under control for multi platform kernels.
Build tested
[[PATCH 0/5] reset: make non-modular drivers really non modular] On 13/06/2016
(Mon 14:03) Paul Gortmaker wrote:
> For anyone new to the underlying goal of this cleanup, we are trying to
> not use module support for code that can never be built as a module since:
Hi Philipp,
I sent this
[[PATCH 0/5] reset: make non-modular drivers really non modular] On 13/06/2016
(Mon 14:03) Paul Gortmaker wrote:
> For anyone new to the underlying goal of this cleanup, we are trying to
> not use module support for code that can never be built as a module since:
Hi Philipp,
I sent this
Viresh Kumar writes:
> On 15-10-16, 21:57, Robert Jarzmik wrote:
>> As the clock settings have been introduced into the clock pxa drivers,
>> which are now available to change the CPU clock by themselves, remove
>> the clock handling from this driver, and rely on pxa
Viresh Kumar writes:
> On 15-10-16, 21:57, Robert Jarzmik wrote:
>> As the clock settings have been introduced into the clock pxa drivers,
>> which are now available to change the CPU clock by themselves, remove
>> the clock handling from this driver, and rely on pxa clock drivers.
>>
>>
From: Andrei Vagin
Date: Thu, 20 Oct 2016 19:46:26 -0700
> @@ -1525,6 +1530,9 @@ void netdev_unregister_kobject(struct net_device *ndev)
> {
> struct device *dev = &(ndev->dev);
>
> + if (!list_empty(_net(ndev)->exit_list))
> +
From: Andrei Vagin
Date: Thu, 20 Oct 2016 19:46:26 -0700
> @@ -1525,6 +1530,9 @@ void netdev_unregister_kobject(struct net_device *ndev)
> {
> struct device *dev = &(ndev->dev);
>
> + if (!list_empty(_net(ndev)->exit_list))
> + dev->kobj.uevent_suppress = 1;
> +
Please
>> @@ -494,12 +494,11 @@ static int sn2_ptc_seq_show(struct seq_file *file,
>> void *data)
>> int cpu;
>>
>> cpu = *(loff_t *) data;
>> -
>> -if (!cpu) {
>> +if (!cpu)
>> seq_printf(file,
>> - "# cpu ptc_l newrid ptc_flushes nodes_flushed
>>
>> @@ -494,12 +494,11 @@ static int sn2_ptc_seq_show(struct seq_file *file,
>> void *data)
>> int cpu;
>>
>> cpu = *(loff_t *) data;
>> -
>> -if (!cpu) {
>> +if (!cpu)
>> seq_printf(file,
>> - "# cpu ptc_l newrid ptc_flushes nodes_flushed
>>
Hi Jonathan,
> Am 22.10.2016 um 20:33 schrieb Jonathan Cameron :
>
> On 17/10/16 14:57, H. Nikolaus Schaller wrote:
>> The tsc2007 chip not only has a resistive touch screen controller but
>> also an external AUX adc imput which can be used for an ambient
>> light sensor,
Hi Jonathan,
> Am 22.10.2016 um 20:33 schrieb Jonathan Cameron :
>
> On 17/10/16 14:57, H. Nikolaus Schaller wrote:
>> The tsc2007 chip not only has a resistive touch screen controller but
>> also an external AUX adc imput which can be used for an ambient
>> light sensor, battery voltage
PTR_ERR should access the value just tested by IS_ERR
Generated by: scripts/coccinelle/tests/odd_ptr_err.cocci
CC: Tomas Novotny
Signed-off-by: Julia Lawall
Signed-off-by: Fengguang Wu
---
Please take the patch only if it's a
PTR_ERR should access the value just tested by IS_ERR
Generated by: scripts/coccinelle/tests/odd_ptr_err.cocci
CC: Tomas Novotny
Signed-off-by: Julia Lawall
Signed-off-by: Fengguang Wu
---
Please take the patch only if it's a positive warning. Thanks!
Not checked at all. This is being
From: Florian Fainelli
Date: Fri, 21 Oct 2016 14:21:54 -0700
> These are the two patches following the discussing we had on
> kexec_in_progress.
>
> Feel free to apply or discard them, thanks!
Applied, thanks.
From: Florian Fainelli
Date: Fri, 21 Oct 2016 14:21:54 -0700
> These are the two patches following the discussing we had on
> kexec_in_progress.
>
> Feel free to apply or discard them, thanks!
Applied, thanks.
On Sat, 2016-10-22 at 21:58 +0200, SF Markus Elfring wrote:
> Some data were printed into a sequence by two separate function calls.
> Print the same data by a single function call instead.
[]
> diff --git a/arch/ia64/sn/kernel/sn2/sn2_smp.c
> b/arch/ia64/sn/kernel/sn2/sn2_smp.c
[]
> @@ -494,12
On Sat, 2016-10-22 at 21:58 +0200, SF Markus Elfring wrote:
> Some data were printed into a sequence by two separate function calls.
> Print the same data by a single function call instead.
[]
> diff --git a/arch/ia64/sn/kernel/sn2/sn2_smp.c
> b/arch/ia64/sn/kernel/sn2/sn2_smp.c
[]
> @@ -494,12
From: Markus Elfring
Date: Sat, 22 Oct 2016 21:19:03 +0200
Some data were printed into a sequence by two separate function calls.
Print the same data by a single function call instead.
This issue was detected by using the Coccinelle software.
Signed-off-by:
From: Markus Elfring
Date: Sat, 22 Oct 2016 21:19:03 +0200
Some data were printed into a sequence by two separate function calls.
Print the same data by a single function call instead.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
From: Markus Elfring
Date: Sat, 22 Oct 2016 20:53:38 +0200
A string which did not contain a data format specification should be put
into a sequence. Thus use the corresponding function "seq_puts".
This issue was detected by using the Coccinelle software.
From: Markus Elfring
Date: Sat, 22 Oct 2016 20:53:38 +0200
A string which did not contain a data format specification should be put
into a sequence. Thus use the corresponding function "seq_puts".
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
1 - 100 of 532 matches
Mail list logo