Em Fri, Jul 21, 2017 at 02:12:08PM +0200, Jiri Olsa escreveu:
> hi,
> sending changes to enable group read of perf counters
> for perf stat command. It allows us to read whole group
> of counters within single read syscall.
>
> Also available in here:
>
Em Fri, Jul 21, 2017 at 02:12:08PM +0200, Jiri Olsa escreveu:
> hi,
> sending changes to enable group read of perf counters
> for perf stat command. It allows us to read whole group
> of counters within single read syscall.
>
> Also available in here:
>
On Wed, Jul 19, 2017 at 05:01:21PM +0100, Mark Rutland wrote:
> This series adds support for the ARMv8.3 pointer authentication extension.
>
> Since RFC [1]:
> * Make the KVM context switch (semi-lazy)
> * Rebase to v4.13-rc1
> * Improve pointer authentication documentation
> * Add hwcap
On Wed, Jul 19, 2017 at 05:01:21PM +0100, Mark Rutland wrote:
> This series adds support for the ARMv8.3 pointer authentication extension.
>
> Since RFC [1]:
> * Make the KVM context switch (semi-lazy)
> * Rebase to v4.13-rc1
> * Improve pointer authentication documentation
> * Add hwcap
On 21/07/17 17:56, Paolo Abeni wrote:
Hi,
On Fri, 2017-07-21 at 17:20 +0200, John Crispin wrote:
In order to make HW flow offloading work in latest MediaTek silicon we need
to propagate part of the RX DMS descriptor to the upper layers populating
the flow offload engines HW tables. This
On 21/07/17 17:56, Paolo Abeni wrote:
Hi,
On Fri, 2017-07-21 at 17:20 +0200, John Crispin wrote:
In order to make HW flow offloading work in latest MediaTek silicon we need
to propagate part of the RX DMS descriptor to the upper layers populating
the flow offload engines HW tables. This
There are a number of file patterns in MAINTAINERS that
don't have an actual matching file in the kernel tree.
Some of those are due to renames, some are typos, some
are added without a matching file being added at the
same time.
There's a pending, might be applied patch to reorder
all the
There are a number of file patterns in MAINTAINERS that
don't have an actual matching file in the kernel tree.
Some of those are due to renames, some are typos, some
are added without a matching file being added at the
same time.
There's a pending, might be applied patch to reorder
all the
Em Fri, 21 Jul 2017 16:40:20 +
"Kani, Toshimitsu" escreveu:
> On Fri, 2017-07-21 at 12:44 -0300, Mauro Carvalho Chehab wrote:
> > Em Fri, 21 Jul 2017 15:34:50 +
> > "Kani, Toshimitsu" escreveu:
> >
> > > On Fri, 2017-07-21 at 17:13 +0200,
Em Fri, 21 Jul 2017 16:40:20 +
"Kani, Toshimitsu" escreveu:
> On Fri, 2017-07-21 at 12:44 -0300, Mauro Carvalho Chehab wrote:
> > Em Fri, 21 Jul 2017 15:34:50 +
> > "Kani, Toshimitsu" escreveu:
> >
> > > On Fri, 2017-07-21 at 17:13 +0200, Borislav Petkov wrote:
> > > > On Fri, Jul
Em Tue, Jul 18, 2017 at 06:18:35PM -0700, David Carrillo-Cisneros escreveu:
> Pickup some small fixes that have been forgotten.
Thanks, applied 2-4, and sent the alternative patch for 1/4 for your
information.
- Arnaldo
Em Tue, Jul 18, 2017 at 06:18:35PM -0700, David Carrillo-Cisneros escreveu:
> Pickup some small fixes that have been forgotten.
Thanks, applied 2-4, and sent the alternative patch for 1/4 for your
information.
- Arnaldo
Hi Quentin,
>>> The Espressif ESP8089 WiFi chips can be often found in cheap tablets.
>>> There is one in A23 Polaroid tablets for example.
>>>
>>> The chip is often embedded as an eMMC SDIO device.
>>>
>>> The code was taken from an out-of-tree repository and has seen a first
>>> pass in the
Hi Quentin,
>>> The Espressif ESP8089 WiFi chips can be often found in cheap tablets.
>>> There is one in A23 Polaroid tablets for example.
>>>
>>> The chip is often embedded as an eMMC SDIO device.
>>>
>>> The code was taken from an out-of-tree repository and has seen a first
>>> pass in the
On Fri, 2017-07-21 at 09:48 -0700, Loc Ho wrote:
> On Fri, Jul 21, 2017 at 9:38 AM, Joe Perches wrote:
> > Section headers should be single line.
> >
> > Fix it.
>
> Can we drop the "Fix it."
I use that frequently.
> > diff --git a/MAINTAINERS b/MAINTAINERS
[]
> > @@
On Fri, 2017-07-21 at 09:48 -0700, Loc Ho wrote:
> On Fri, Jul 21, 2017 at 9:38 AM, Joe Perches wrote:
> > Section headers should be single line.
> >
> > Fix it.
>
> Can we drop the "Fix it."
I use that frequently.
> > diff --git a/MAINTAINERS b/MAINTAINERS
[]
> > @@ -5029,8 +5029,7 @@ L:
On 07/21/2017 04:01 AM, Manu Gautam wrote:
> From: Vivek Gautam
>
> Pipe clock comes out of the phy and is available as long as
> the phy is turned on. Clock controller fails to gate this
> clock after the phy is turned off and generates a warning.
>
> / # [
From: Aleksandar Markovic
Add documentation for DT binding of Goldfish PIC driver. The compatible
string used by OS for binding the driver is "google,goldfish-pic".
Signed-off-by: Miodrag Dinic
Signed-off-by: Goran Ferenc
On 07/21/2017 04:01 AM, Manu Gautam wrote:
> From: Vivek Gautam
>
> Pipe clock comes out of the phy and is available as long as
> the phy is turned on. Clock controller fails to gate this
> clock after the phy is turned off and generates a warning.
>
> / # [ 33.048561] gcc_usb3_phy_pipe_clk
From: Aleksandar Markovic
Add documentation for DT binding of Goldfish PIC driver. The compatible
string used by OS for binding the driver is "google,goldfish-pic".
Signed-off-by: Miodrag Dinic
Signed-off-by: Goran Ferenc
Signed-off-by: Aleksandar Markovic
---
From: Miodrag Dinic
Add device driver for a virtual programmable interrupt controller
The virtual PIC is designed as a device tree-based interrupt controller.
The compatible string used by OS for binding the driver is
"google,goldfish-pic".
Signed-off-by: Miodrag
From: Aleksandar Markovic
v2->v3:
- fixed configuration dependency for VIRTIO_NET and
RTC_DRV_GOLDFISH
- fixed frequency calculation in ranchu_measure_hpt_freq()
- use DT info instead of hard-coding RTC base in
From: Aleksandar Markovic
v2->v3:
- fixed configuration dependency for VIRTIO_NET and
RTC_DRV_GOLDFISH
- fixed frequency calculation in ranchu_measure_hpt_freq()
- use DT info instead of hard-coding RTC base in
ranchu_measure_hpt_freq()
- Goldfish PIC reworked to
From: Miodrag Dinic
Add device driver for a virtual programmable interrupt controller
The virtual PIC is designed as a device tree-based interrupt controller.
The compatible string used by OS for binding the driver is
"google,goldfish-pic".
Signed-off-by: Miodrag Dinic
Signed-off-by: Goran
Em Tue, Jul 18, 2017 at 06:18:36PM -0700, David Carrillo-Cisneros escreveu:
> Atomic reference counters were replaced by refcount_t in
> commit 79c5fe6db8c7 ("perf/core: Fix error handling in perf_event_alloc()")
>
> In util/cgroup.c atomic_inc was replaced by refcount_inc, but the latter
> is
Em Tue, Jul 18, 2017 at 06:18:36PM -0700, David Carrillo-Cisneros escreveu:
> Atomic reference counters were replaced by refcount_t in
> commit 79c5fe6db8c7 ("perf/core: Fix error handling in perf_event_alloc()")
>
> In util/cgroup.c atomic_inc was replaced by refcount_inc, but the latter
> is
From: Aleksandar Markovic
Add documentation for DT binding of Goldfish RTC driver. The compatible
string used by OS for binding the driver is "google,goldfish-rtc".
Signed-off-by: Miodrag Dinic
Signed-off-by: Goran Ferenc
From: Miodrag Dinic
Add device driver for a virtual Goldfish RTC clock.
The driver can be built only if CONFIG_MIPS and CONFIG_GOLDFISH are
set. The compatible string used by OS for binding the driver is
defined as "google,goldfish-rtc".
Signed-off-by: Miodrag Dinic
From: Aleksandar Markovic
Add documentation for DT binding of Goldfish RTC driver. The compatible
string used by OS for binding the driver is "google,goldfish-rtc".
Signed-off-by: Miodrag Dinic
Signed-off-by: Goran Ferenc
Signed-off-by: Aleksandar Markovic
---
From: Miodrag Dinic
Add device driver for a virtual Goldfish RTC clock.
The driver can be built only if CONFIG_MIPS and CONFIG_GOLDFISH are
set. The compatible string used by OS for binding the driver is
defined as "google,goldfish-rtc".
Signed-off-by: Miodrag Dinic
Signed-off-by: Goran
From: Aleksandar Markovic
Add ability to the Goldfish FB driver to be recognized by OS via DT.
Signed-off-by: Miodrag Dinic
Signed-off-by: Goran Ferenc
Signed-off-by: Aleksandar Markovic
From: Aleksandar Markovic
Add ability to the Goldfish FB driver to be recognized by OS via DT.
Signed-off-by: Miodrag Dinic
Signed-off-by: Goran Ferenc
Signed-off-by: Aleksandar Markovic
---
drivers/video/fbdev/goldfishfb.c | 8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff
From: Miodrag Dinic
This effectively disables i8042 driver for MIPS_GENERIC kernel platform.
Currently, only sead-3, boston and ranchu boards are supported by the
MIPS generic kernel and none of them require this driver.
More specifically, kernel would crash if it gets
From: Miodrag Dinic
This effectively disables i8042 driver for MIPS_GENERIC kernel platform.
Currently, only sead-3, boston and ranchu boards are supported by the
MIPS generic kernel and none of them require this driver.
More specifically, kernel would crash if it gets enabled, because
i8042
From: Aleksandar Markovic
Add documentation for DT binding of Goldfish FB driver. The compatible
string used by OS for binding the driver is "google,goldfish-fb".
Signed-off-by: Miodrag Dinic
Signed-off-by: Goran Ferenc
From: Aleksandar Markovic
Add documentation for DT binding of Goldfish FB driver. The compatible
string used by OS for binding the driver is "google,goldfish-fb".
Signed-off-by: Miodrag Dinic
Signed-off-by: Goran Ferenc
Signed-off-by: Aleksandar Markovic
---
From: Miodrag Dinic
Provide amendments to the Mips generic platform framework so that
the new generic-based board Ranchu can be chosen to be built.
Signed-off-by: Miodrag Dinic
Signed-off-by: Goran Ferenc
From: Miodrag Dinic
Provide amendments to the Mips generic platform framework so that
the new generic-based board Ranchu can be chosen to be built.
Signed-off-by: Miodrag Dinic
Signed-off-by: Goran Ferenc
Signed-off-by: Aleksandar Markovic
---
MAINTAINERS |
Hi Greg,
On 21/07/2017 17:01, Greg KH wrote:
> On Fri, Jul 21, 2017 at 04:35:01PM +0200, Quentin Schulz wrote:
>> The Espressif ESP8089 WiFi chips can be often found in cheap tablets.
>> There is one in A23 Polaroid tablets for example.
>>
>> The chip is often embedded as an eMMC SDIO device.
>>
Hi Greg,
On 21/07/2017 17:01, Greg KH wrote:
> On Fri, Jul 21, 2017 at 04:35:01PM +0200, Quentin Schulz wrote:
>> The Espressif ESP8089 WiFi chips can be often found in cheap tablets.
>> There is one in A23 Polaroid tablets for example.
>>
>> The chip is often embedded as an eMMC SDIO device.
>>
My apologies. Yes, I did make a couple of changes to the patch. I was
not sure if I should be sending a v2 since the previous one was a rfc.
Please ignore this patch, I will resend this highlighting the new
changes made.
On Fri, Jul 21, 2017 at 9:28 AM, Arnaldo Carvalho de Melo
My apologies. Yes, I did make a couple of changes to the patch. I was
not sure if I should be sending a v2 since the previous one was a rfc.
Please ignore this patch, I will resend this highlighting the new
changes made.
On Fri, Jul 21, 2017 at 9:28 AM, Arnaldo Carvalho de Melo
wrote:
> Em Fri,
Hi,
On Fri, Jul 21, 2017 at 9:38 AM, Joe Perches wrote:
> Section headers should be single line.
>
> Fix it.
Can we drop the "Fix it."
>
> Signed-off-by: Joe Perches
> ---
> MAINTAINERS | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff
Hi,
On Fri, Jul 21, 2017 at 9:38 AM, Joe Perches wrote:
> Section headers should be single line.
>
> Fix it.
Can we drop the "Fix it."
>
> Signed-off-by: Joe Perches
> ---
> MAINTAINERS | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
>
Now IRQ mappings are always created for all (allowed) GPIOs in gpiochip in
gpiochip_irqchip_add_key() which goes against the idea of SPARSE_IRQ and,
as result, leads to:
- increasing of memory consumption for IRQ descriptors most of which will
never ever be used (espessially on platform with a
On 07/21/2017 12:57 AM, Vinod Koul wrote:
> On Thu, Jul 20, 2017 at 09:56:45AM -0700, Dave Jiang wrote:
>>
>>
>> On 07/20/2017 12:24 AM, walter harms wrote:
>>>
>>>
>>> Am 20.07.2017 00:16, schrieb Christophe JAILLET:
If the 'memcmp' fails, free allocated resources as done in all other
Now IRQ mappings are always created for all (allowed) GPIOs in gpiochip in
gpiochip_irqchip_add_key() which goes against the idea of SPARSE_IRQ and,
as result, leads to:
- increasing of memory consumption for IRQ descriptors most of which will
never ever be used (espessially on platform with a
On 07/21/2017 12:57 AM, Vinod Koul wrote:
> On Thu, Jul 20, 2017 at 09:56:45AM -0700, Dave Jiang wrote:
>>
>>
>> On 07/20/2017 12:24 AM, walter harms wrote:
>>>
>>>
>>> Am 20.07.2017 00:16, schrieb Christophe JAILLET:
If the 'memcmp' fails, free allocated resources as done in all other
Doug,
On Wed, Jul 19, 2017 at 10:36:54AM +0200, Johannes Thumshirn wrote:
> On Wed, Jul 19, 2017 at 03:13:34AM -0500, Jason L Tibbitts III wrote:
> > [ 46.304530] sg_is_valid_dxfer: dxfer_direction: -2, dxfer_len: 0
>
> Ahh now I see the -2 (SG_DXFER_TO_DEV) is the crucial point here. It is 0
Doug,
On Wed, Jul 19, 2017 at 10:36:54AM +0200, Johannes Thumshirn wrote:
> On Wed, Jul 19, 2017 at 03:13:34AM -0500, Jason L Tibbitts III wrote:
> > [ 46.304530] sg_is_valid_dxfer: dxfer_direction: -2, dxfer_len: 0
>
> Ahh now I see the -2 (SG_DXFER_TO_DEV) is the crucial point here. It is 0
On Fri, Jul 21, 2017 at 12:21:50PM +0530, Aneesh Kumar K.V wrote:
> Ram Pai writes:
>
> > On Thu, Jul 20, 2017 at 12:12:47PM +0530, Aneesh Kumar K.V wrote:
> >> Ram Pai writes:
> >>
> >> > helper function that checks if the read/write/execute is
On Fri, Jul 21, 2017 at 12:21:50PM +0530, Aneesh Kumar K.V wrote:
> Ram Pai writes:
>
> > On Thu, Jul 20, 2017 at 12:12:47PM +0530, Aneesh Kumar K.V wrote:
> >> Ram Pai writes:
> >>
> >> > helper function that checks if the read/write/execute is allowed
> >> > on the pte.
> >> >
> >> >
Hi Namhyung,
On Fri, 2017-07-21 at 12:31 +0900, Namhyung Kim wrote:
> On Mon, Jun 26, 2017 at 05:49:20PM -0500, Tom Zanussi wrote:
> > Add the necessary infrastructure to allow the variables defined on one
> > event to be referenced in another. This allows variables set by a
> > previous event
Hi Namhyung,
On Fri, 2017-07-21 at 12:31 +0900, Namhyung Kim wrote:
> On Mon, Jun 26, 2017 at 05:49:20PM -0500, Tom Zanussi wrote:
> > Add the necessary infrastructure to allow the variables defined on one
> > event to be referenced in another. This allows variables set by a
> > previous event
On Fri, 2017-07-21 at 12:44 -0300, Mauro Carvalho Chehab wrote:
> Em Fri, 21 Jul 2017 15:34:50 +
> "Kani, Toshimitsu" escreveu:
>
> > On Fri, 2017-07-21 at 17:13 +0200, Borislav Petkov wrote:
> > > On Fri, Jul 21, 2017 at 03:08:41PM +, Kani, Toshimitsu
> > > wrote:
On Fri, 2017-07-21 at 12:44 -0300, Mauro Carvalho Chehab wrote:
> Em Fri, 21 Jul 2017 15:34:50 +
> "Kani, Toshimitsu" escreveu:
>
> > On Fri, 2017-07-21 at 17:13 +0200, Borislav Petkov wrote:
> > > On Fri, Jul 21, 2017 at 03:08:41PM +, Kani, Toshimitsu
> > > wrote:
> > > > Yes, that is
CLK_SET_RATE_PARENT flag is added to the clocks between the EPLL
and the audio subsystem clock controller so that the EPLL's output
frequency can be set indirectly with clk_set_rate() on a leaf clock.
That should be safe as EPLL is normally only used to generate clock
for the audio subsystem.
With
Section headers should be single line.
Fix it.
Signed-off-by: Joe Perches
---
MAINTAINERS | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 542f7dee98f0..0b59df2498e9 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -5029,8
This allows clk rate propagation up to the clock tree so EPLL
can be reprogrammed indirectly when setting rate of the Audio
Subsystem clocks.
The advantage is that sound machine driver can operate only
on the leaf clocks rather than explicitly re-configuring
the root clock (EPLL).
Signed-off-by:
CLK_SET_RATE_PARENT flag is added to the clocks between the EPLL
and the audio subsystem clock controller so that the EPLL's output
frequency can be set indirectly with clk_set_rate() on a leaf clock.
That should be safe as EPLL is normally only used to generate clock
for the audio subsystem.
With
Section headers should be single line.
Fix it.
Signed-off-by: Joe Perches
---
MAINTAINERS | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 542f7dee98f0..0b59df2498e9 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -5029,8 +5029,7 @@ L:
This allows clk rate propagation up to the clock tree so EPLL
can be reprogrammed indirectly when setting rate of the Audio
Subsystem clocks.
The advantage is that sound machine driver can operate only
on the leaf clocks rather than explicitly re-configuring
the root clock (EPLL).
Signed-off-by:
Parent clock of the MAU_EPLL gate clock on exynos5422 is
"mout_user_mau_epll", not "mout_mau_epll_clk". This change
only affects exynos5422/5800.
Signed-off-by: Sylwester Nawrocki
---
drivers/clk/samsung/clk-exynos5420.c | 12 +---
1 file changed, 9
Parent clock of the MAU_EPLL gate clock on exynos5422 is
"mout_user_mau_epll", not "mout_mau_epll_clk". This change
only affects exynos5422/5800.
Signed-off-by: Sylwester Nawrocki
---
drivers/clk/samsung/clk-exynos5420.c | 12 +---
1 file changed, 9 insertions(+), 3 deletions(-)
diff
On Fri, Jul 21, 2017 at 08:24:40AM +0800, Boqun Feng wrote:
> On Thu, Jul 20, 2017 at 04:07:14PM -0700, Paul E. McKenney wrote:
> [...]
> > >
> > > So if I respin the patch with the extern, would you still feel reluctant?
> >
> > Yes, because I am not seeing how this change helps. What is this
On Fri, Jul 21, 2017 at 08:24:40AM +0800, Boqun Feng wrote:
> On Thu, Jul 20, 2017 at 04:07:14PM -0700, Paul E. McKenney wrote:
> [...]
> > >
> > > So if I respin the patch with the extern, would you still feel reluctant?
> >
> > Yes, because I am not seeing how this change helps. What is this
On Fri, 2017-07-21 at 17:53 +0200, Borislav Petkov wrote:
> On Fri, Jul 21, 2017 at 03:34:50PM +, Kani, Toshimitsu wrote:
> > I suppose it'd depend on vendors, but I do not think users can do
> > it properly unless they have depth knowledge about the hardware.
>
> I'm talking about a menu in
On Fri, 2017-07-21 at 17:53 +0200, Borislav Petkov wrote:
> On Fri, Jul 21, 2017 at 03:34:50PM +, Kani, Toshimitsu wrote:
> > I suppose it'd depend on vendors, but I do not think users can do
> > it properly unless they have depth knowledge about the hardware.
>
> I'm talking about a menu in
Hi Namhyung,
On Fri, 2017-07-21 at 11:02 +0900, Namhyung Kim wrote:
> Hi Tom,
>
> On Mon, Jun 26, 2017 at 05:49:19PM -0500, Tom Zanussi wrote:
> > Add support for simple addition, subtraction, and unary expressions
> > (-(expr) and expr, where expr = b-a, a+b, a+b+c) to hist triggers, in
> >
Hi Namhyung,
On Fri, 2017-07-21 at 11:02 +0900, Namhyung Kim wrote:
> Hi Tom,
>
> On Mon, Jun 26, 2017 at 05:49:19PM -0500, Tom Zanussi wrote:
> > Add support for simple addition, subtraction, and unary expressions
> > (-(expr) and expr, where expr = b-a, a+b, a+b+c) to hist triggers, in
> >
Em Fri, Jul 21, 2017 at 09:46:39AM +0200, Jiri Olsa escreveu:
> On Thu, Jul 20, 2017 at 07:01:13PM -0700, Arun Kalyanasundaram wrote:
> > The process_event python hook receives a dict with most perf_sample
> > entries.
>
> hi,
> was there any change to the rfc post?
I was wondering that, please
Em Fri, Jul 21, 2017 at 09:46:39AM +0200, Jiri Olsa escreveu:
> On Thu, Jul 20, 2017 at 07:01:13PM -0700, Arun Kalyanasundaram wrote:
> > The process_event python hook receives a dict with most perf_sample
> > entries.
>
> hi,
> was there any change to the rfc post?
I was wondering that, please
Without this, I get a build error:
drivers/staging/media/imx/imx-media-vdic.c: In function '__vdic_get_fmt':
drivers/staging/media/imx/imx-media-vdic.c:554:10: error: implicit declaration
of function 'v4l2_subdev_get_try_format'; did you mean
'v4l2_subdev_notify_event'?
Without this, I get a build error:
drivers/staging/media/imx/imx-media-vdic.c: In function '__vdic_get_fmt':
drivers/staging/media/imx/imx-media-vdic.c:554:10: error: implicit declaration
of function 'v4l2_subdev_get_try_format'; did you mean
'v4l2_subdev_notify_event'?
Without this header, we get a build error in some configurations:
drivers/media/platform/omap/omap_vout_vrfb.c: In function
'omap_vout_setup_vrfb_bufs':
drivers/media/platform/omap/omap_vout_vrfb.c:143:26: error: implicit
declaration of function 'kzalloc'; did you mean 'vzalloc'?
Add support for detecting and installing missing packages
on Mageia. I opted to use "urpmi" at the install instructions,
as this is present on Mageia since ever. Yet, if I were using
Mageia 6, I would likely be using "dnf", as it is, IMHO,
easier to use.
Tested with Mageia 6.
Signed-off-by:
Without this header, we get a build error in some configurations:
drivers/media/platform/omap/omap_vout_vrfb.c: In function
'omap_vout_setup_vrfb_bufs':
drivers/media/platform/omap/omap_vout_vrfb.c:143:26: error: implicit
declaration of function 'kzalloc'; did you mean 'vzalloc'?
Add support for detecting and installing missing packages
on Mageia. I opted to use "urpmi" at the install instructions,
as this is present on Mageia since ever. Yet, if I were using
Mageia 6, I would likely be using "dnf", as it is, IMHO,
easier to use.
Tested with Mageia 6.
Signed-off-by:
__WARN() is an internal helper that is only available on
some architectures, but causes a build error e.g. on ARM64
in some configurations:
drivers/xen/pvcalls-back.c: In function 'set_backend_state':
drivers/xen/pvcalls-back.c:1097:5: error: implicit declaration of function
'__WARN'
__WARN() is an internal helper that is only available on
some architectures, but causes a build error e.g. on ARM64
in some configurations:
drivers/xen/pvcalls-back.c: In function 'set_backend_state':
drivers/xen/pvcalls-back.c:1097:5: error: implicit declaration of function
'__WARN'
We get a Kconfig warning when selecting this without also enabling
CONFIG_PCI:
warning: (X86_INTEL_LPSS && INTEL_SOC_DTS_IOSF_CORE && SND_SST_IPC_ACPI &&
MMC_SDHCI_ACPI && PUNIT_ATOM_DEBUG) selects IOSF_MBI which has unmet direct
dependencies (PCI)
This adds a new depedency.
Fixes:
We get a Kconfig warning when selecting this without also enabling
CONFIG_PCI:
warning: (X86_INTEL_LPSS && INTEL_SOC_DTS_IOSF_CORE && SND_SST_IPC_ACPI &&
MMC_SDHCI_ACPI && PUNIT_ATOM_DEBUG) selects IOSF_MBI which has unmet direct
dependencies (PCI)
This adds a new depedency.
Fixes:
On Wed, 12 Jul 2017, Dmitry Torokhov wrote:
> Even though the IO for devices with "always poll" quirk is already running,
> we still need to set HID_OPENED bit in usbhid->iofl so the interrupt
> handler does not ignore the data coming from the device.
>
> Reported-by: Olof Johansson
When CONFIG_OMAP_USB2 is set to 'm' and the charger driver is built-in,
we get this link failure:
drivers/power/supply/cpcap-charger.o: In function `cpcap_charger_probe':
cpcap-charger.c:(.text+0x48c): undefined reference to `omap_usb2_set_comparator'
drivers/power/supply/cpcap-charger.o: In
On Wed, 12 Jul 2017, Dmitry Torokhov wrote:
> Even though the IO for devices with "always poll" quirk is already running,
> we still need to set HID_OPENED bit in usbhid->iofl so the interrupt
> handler does not ignore the data coming from the device.
>
> Reported-by: Olof Johansson
>
When CONFIG_OMAP_USB2 is set to 'm' and the charger driver is built-in,
we get this link failure:
drivers/power/supply/cpcap-charger.o: In function `cpcap_charger_probe':
cpcap-charger.c:(.text+0x48c): undefined reference to `omap_usb2_set_comparator'
drivers/power/supply/cpcap-charger.o: In
Without CONFIG_OF, we can run into a build error:
drivers/gpu/drm/tegra/dpaux.c:378:20: error:
'pinconf_generic_dt_node_to_map_group' undeclared here (not in a function); did
you mean 'pinconf_generic_params'?
.dt_node_to_map = pinconf_generic_dt_node_to_map_group,
Without CONFIG_OF, we can run into a build error:
drivers/gpu/drm/tegra/dpaux.c:378:20: error:
'pinconf_generic_dt_node_to_map_group' undeclared here (not in a function); did
you mean 'pinconf_generic_params'?
.dt_node_to_map = pinconf_generic_dt_node_to_map_group,
Hi Dave,
important fixes for net which had accumulated while I was away. I only
applied the brcmfmac and rtlwifi patches only eight hours ago and I
haven't seen the kbuild report yet so they might have some build
breakage in theory. But the patches are so small so the chances that
they would
Hi Dave,
important fixes for net which had accumulated while I was away. I only
applied the brcmfmac and rtlwifi patches only eight hours ago and I
haven't seen the kbuild report yet so they might have some build
breakage in theory. But the patches are so small so the chances that
they would
From: Colin Ian King
Recently added FE_NONE to the enum fe_status, so update the
documentation accordingly.
Signed-off-by: Colin Ian King
---
Documentation/media/uapi/dvb/fe-read-status.rst | 20 ++--
1 file changed, 14
From: Colin Ian King
Recently added FE_NONE to the enum fe_status, so update the
documentation accordingly.
Signed-off-by: Colin Ian King
---
Documentation/media/uapi/dvb/fe-read-status.rst | 20 ++--
1 file changed, 14 insertions(+), 6 deletions(-)
diff --git
Without the base library support, we get a link failure
drivers/scsi/qedi/qedi_main.o: In function `__qedi_probe.constprop.0':
qedi_main.c:(.text+0x2d8e): undefined reference to `iscsi_boot_create_target'
qedi_main.c:(.text+0x2dee): undefined reference to `iscsi_boot_create_initiator'
Without the base library support, we get a link failure
drivers/scsi/qedi/qedi_main.o: In function `__qedi_probe.constprop.0':
qedi_main.c:(.text+0x2d8e): undefined reference to `iscsi_boot_create_target'
qedi_main.c:(.text+0x2dee): undefined reference to `iscsi_boot_create_initiator'
On 07/20/2017 09:10 PM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20170720:
>
on x86_64:
when CONFIG_BUG is not enabled:
../drivers/media/platform/pxa_camera.c:642:3: error: implicit declaration of
function ‘__WARN’ [-Werror=implicit-function-declaration]
On 07/20/2017 09:10 PM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20170720:
>
on x86_64:
when CONFIG_BUG is not enabled:
../drivers/media/platform/pxa_camera.c:642:3: error: implicit declaration of
function ‘__WARN’ [-Werror=implicit-function-declaration]
On Fri, Jul 21, 2017 at 11:27:09AM -0400, wrote:
> On Thu, Jul 20, 2017 at 04:44:55PM -0700, Benjamin Poirier wrote:
> > Could you please test the following patch and let me know if it:
> > 1) reduces the interrupt rate of the Other msi-x vector
> > 2) avoids the link flaps
> > or
> > 3) logs
On Fri, Jul 21, 2017 at 11:27:09AM -0400, wrote:
> On Thu, Jul 20, 2017 at 04:44:55PM -0700, Benjamin Poirier wrote:
> > Could you please test the following patch and let me know if it:
> > 1) reduces the interrupt rate of the Other msi-x vector
> > 2) avoids the link flaps
> > or
> > 3) logs
On 18/07/17 22:43, Rob Herring wrote:
> Now that we have a custom printf format specifier, convert users of
> full_name to use %pOF instead. This is preparation to remove storing
> of the full path string for each node.
>
> Signed-off-by: Rob Herring
> Cc: Sudeep Holla
On 18/07/17 22:43, Rob Herring wrote:
> Now that we have a custom printf format specifier, convert users of
> full_name to use %pOF instead. This is preparation to remove storing
> of the full path string for each node.
>
> Signed-off-by: Rob Herring
> Cc: Sudeep Holla
> Cc: Mark Rutland
>
501 - 600 of 1478 matches
Mail list logo