On 28-04-17, 10:44, Sudeep Holla wrote:
> Just thinking out loud, I can see platforms with have OPPs can move to
> this binding in future eliminating the need to specify the clock and
> regulators explicitly. So, I am not saying I against this idea, but I
> see it might complicate the above case
On 28-04-17, 10:44, Sudeep Holla wrote:
> Just thinking out loud, I can see platforms with have OPPs can move to
> this binding in future eliminating the need to specify the clock and
> regulators explicitly. So, I am not saying I against this idea, but I
> see it might complicate the above case
From: Sebastian Andrzej Siewior
Provide static_key_[enable|slow_inc]_cpuslocked() variant that
don't take cpu_hotplug_lock().
Signed-off-by: Sebastian Andrzej Siewior
Signed-off-by: Mark Rutland
Cc: Peter Zijlstra
From: Sebastian Andrzej Siewior
Provide static_key_[enable|slow_inc]_cpuslocked() variant that
don't take cpu_hotplug_lock().
Signed-off-by: Sebastian Andrzej Siewior
Signed-off-by: Mark Rutland
Cc: Peter Zijlstra
Cc: Sebastian Siewior
Cc: Steven Rostedt
Cc: jba...@akamai.com
---
Recently, the hotplug locking was conveted to use a percpu rwsem. Unlike
the existing {get,put}_online_cpus() logic, this can't nest.
Unfortunately, in arm64's secondary boot path we can end up nesting via
static_branch_enable() in cpus_set_cap() when we detect an erratum.
This leads to a stream
Recently, the hotplug locking was conveted to use a percpu rwsem. Unlike
the existing {get,put}_online_cpus() logic, this can't nest.
Unfortunately, in arm64's secondary boot path we can end up nesting via
static_branch_enable() in cpus_set_cap() when we detect an erratum.
This leads to a stream
Hi,
These patches fix a boot issue seen on some arm64 platforms as a result of the
hotplug rwsem rework.
Thomas, would you be able to take these into the tip smp/hotplug branch?
Will has acked the arm64 part, and is happy for this to go via tip [1].
I've tested this atop of the tip smp/hotplug
Hi,
These patches fix a boot issue seen on some arm64 platforms as a result of the
hotplug rwsem rework.
Thomas, would you be able to take these into the tip smp/hotplug branch?
Will has acked the arm64 part, and is happy for this to go via tip [1].
I've tested this atop of the tip smp/hotplug
On Fri, Apr 28, 2017 at 12:29:55PM +0200, Greg Kroah-Hartman wrote:
> On Sun, Apr 23, 2017 at 05:51:17PM -0300, Marcos Paulo de Souza wrote:
> > Fix the following sparse warning:
> > rtl8192u/ieee80211/ieee80211_rx.c:1489:45: warning: incorrect type in
> > assignment (different base types)
> >
On Thu, Apr 27, 2017 at 11:10:55AM -0700, Guenter Roeck wrote:
> On Thu, Apr 27, 2017 at 11:50:12AM +0530, Rajaram R wrote:
> > On Tue, Apr 25, 2017 at 7:40 PM, Guenter Roeck wrote:
> > > On 04/25/2017 01:26 AM, Rajaram R wrote:
> > >>
> > >> On Mon, Apr 24, 2017 at 11:20 PM,
On Fri, Apr 28, 2017 at 12:29:55PM +0200, Greg Kroah-Hartman wrote:
> On Sun, Apr 23, 2017 at 05:51:17PM -0300, Marcos Paulo de Souza wrote:
> > Fix the following sparse warning:
> > rtl8192u/ieee80211/ieee80211_rx.c:1489:45: warning: incorrect type in
> > assignment (different base types)
> >
On Thu, Apr 27, 2017 at 11:10:55AM -0700, Guenter Roeck wrote:
> On Thu, Apr 27, 2017 at 11:50:12AM +0530, Rajaram R wrote:
> > On Tue, Apr 25, 2017 at 7:40 PM, Guenter Roeck wrote:
> > > On 04/25/2017 01:26 AM, Rajaram R wrote:
> > >>
> > >> On Mon, Apr 24, 2017 at 11:20 PM, Badhri Jagan
>> @@ -334,8 +334,8 @@ static int asoc_simple_card_parse_aux_devs(struct
>> device_node *node,
>> if (n <= 0)
>> return -EINVAL;
>>
>> -card->aux_dev = devm_kzalloc(dev,
>> -n * sizeof(*card->aux_dev), GFP_KERNEL);
>> +card->aux_dev =
>> @@ -334,8 +334,8 @@ static int asoc_simple_card_parse_aux_devs(struct
>> device_node *node,
>> if (n <= 0)
>> return -EINVAL;
>>
>> -card->aux_dev = devm_kzalloc(dev,
>> -n * sizeof(*card->aux_dev), GFP_KERNEL);
>> +card->aux_dev =
On 4/28/2017 1:32 PM, Greg KH wrote:
> On Sat, Apr 22, 2017 at 09:44:49AM +0300, Horia Geantă wrote:
>> When checking the response verb, the valid bit should be masked out,
>> since its value flips depending on what Response Register
>> (RR0 /RR1) it's been read from.
>>
>> Fixes: 321eecb06bfb
On 4/28/2017 1:32 PM, Greg KH wrote:
> On Sat, Apr 22, 2017 at 09:44:49AM +0300, Horia Geantă wrote:
>> When checking the response verb, the valid bit should be masked out,
>> since its value flips depending on what Response Register
>> (RR0 /RR1) it's been read from.
>>
>> Fixes: 321eecb06bfb
On Wed, Apr 26, 2017 at 11:13:44AM -0700, Ricardo Neri wrote:
> Masami Hiramatsu had originally requested to add the two functions. I
> suppose the unneeded functions could be added if/when needed.
Yap, exactly.
--
Regards/Gruss,
Boris.
SUSE Linux GmbH, GF: Felix Imendörffer, Jane
On Wed, Apr 26, 2017 at 11:13:44AM -0700, Ricardo Neri wrote:
> Masami Hiramatsu had originally requested to add the two functions. I
> suppose the unneeded functions could be added if/when needed.
Yap, exactly.
--
Regards/Gruss,
Boris.
SUSE Linux GmbH, GF: Felix Imendörffer, Jane
On Wed, 12 Apr 2017, Lee Jones wrote:
> Currently users have to use all sorts of ugly #ifery within
> their drivers in order to avoid linking issues at build time.
> This patch allows users to safely call these functions when
> !CONFIG_RC_CORE and make decisions based on the return value
>
On Wed, 12 Apr 2017, Lee Jones wrote:
> Currently users have to use all sorts of ugly #ifery within
> their drivers in order to avoid linking issues at build time.
> This patch allows users to safely call these functions when
> !CONFIG_RC_CORE and make decisions based on the return value
>
Checkpatch was showing:
WARNING: Block comments use a trailing */ on a separate line.
Move trailing */ to a separate line.
Signed-off-by: Ilia Sergachev
---
Changes for v4:
- remove one trailing whitespace in the last hunk,
which was corrupting the patch
Checkpatch was showing:
WARNING: Block comments use a trailing */ on a separate line.
Move trailing */ to a separate line.
Signed-off-by: Ilia Sergachev
---
Changes for v4:
- remove one trailing whitespace in the last hunk,
which was corrupting the patch
Changes for v3:
- improve the
When using 'ls -l' to display a large directory, if noac option is used,
in function nfs_getattr() nfs_need_revalidate_inode() will always be true
for NFSv3 and the nfs_entry cache of the directory will be flushed. The
flush will lead to a fully reread of the directory entries from server.
To
When using 'ls -l' to display a large directory, if noac option is used,
in function nfs_getattr() nfs_need_revalidate_inode() will always be true
for NFSv3 and the nfs_entry cache of the directory will be flushed. The
flush will lead to a fully reread of the directory entries from server.
To
On Wed, Apr 26, 2017 at 02:59:09PM -0300, Lauro Venancio wrote:
> Maybe, to make the debug messages clear, you could print "balance_cpu:
> %d" instead of "capacity(%d): " and assert (sgc id == balance cpu). You
> would need to restart the sgc id count on every topology level.
Right, that's a
On Wed, Apr 26, 2017 at 02:59:09PM -0300, Lauro Venancio wrote:
> Maybe, to make the debug messages clear, you could print "balance_cpu:
> %d" instead of "capacity(%d): " and assert (sgc id == balance cpu). You
> would need to restart the sgc id count on every topology level.
Right, that's a
On Fri, Apr 28, 2017 at 11:20:21AM +0100, Ard Biesheuvel wrote:
> On 28 April 2017 at 10:53, Mark Rutland wrote:
> > On Fri, Apr 28, 2017 at 08:18:52AM +0100, Ard Biesheuvel wrote:
> >> On 27 April 2017 at 23:52, Matthias Kaehlcke wrote:
> >> > El Thu,
On Fri, Apr 28, 2017 at 11:20:21AM +0100, Ard Biesheuvel wrote:
> On 28 April 2017 at 10:53, Mark Rutland wrote:
> > On Fri, Apr 28, 2017 at 08:18:52AM +0100, Ard Biesheuvel wrote:
> >> On 27 April 2017 at 23:52, Matthias Kaehlcke wrote:
> >> > El Thu, Apr 27, 2017 at 12:02:56PM +0100 Mark
On Sat, Apr 22, 2017 at 09:44:49AM +0300, Horia Geantă wrote:
> When checking the response verb, the valid bit should be masked out,
> since its value flips depending on what Response Register
> (RR0 /RR1) it's been read from.
>
> Fixes: 321eecb06bfb ("bus: fsl-mc: dpio: add QBMan portal APIs for
On Sat, Apr 22, 2017 at 09:44:49AM +0300, Horia Geantă wrote:
> When checking the response verb, the valid bit should be masked out,
> since its value flips depending on what Response Register
> (RR0 /RR1) it's been read from.
>
> Fixes: 321eecb06bfb ("bus: fsl-mc: dpio: add QBMan portal APIs for
On Sun, Apr 23, 2017 at 05:51:17PM -0300, Marcos Paulo de Souza wrote:
> Fix the following sparse warning:
> rtl8192u/ieee80211/ieee80211_rx.c:1489:45: warning: incorrect type in
> assignment (different base types)
> rtl8192u/ieee80211/ieee80211_rx.c:1489:45:expected restricted __le16
>
>
On Sun, Apr 23, 2017 at 05:51:17PM -0300, Marcos Paulo de Souza wrote:
> Fix the following sparse warning:
> rtl8192u/ieee80211/ieee80211_rx.c:1489:45: warning: incorrect type in
> assignment (different base types)
> rtl8192u/ieee80211/ieee80211_rx.c:1489:45:expected restricted __le16
>
>
On Sat, Apr 22, 2017 at 11:55:23PM +0100, Tuomo Rinne wrote:
> This patch fixes following sparse warnings:
>
> drivers/staging/rtl8192u//r8192U_dm.c:2307:49: warning: cast from restricted
> __le16
> drivers/staging/rtl8192u//r8192U_dm.c:2308:44: warning: cast from restricted
> __le16
>
On Sat, Apr 22, 2017 at 11:55:23PM +0100, Tuomo Rinne wrote:
> This patch fixes following sparse warnings:
>
> drivers/staging/rtl8192u//r8192U_dm.c:2307:49: warning: cast from restricted
> __le16
> drivers/staging/rtl8192u//r8192U_dm.c:2308:44: warning: cast from restricted
> __le16
>
On Fri, Apr 21, 2017 at 09:24:57AM +0530, surenderpolsani wrote:
> kernel coding style doesn't allow the return statement
> in void function.
>
> Signed-off-by: Surenderp
Your "From" line does not match this line.
And I need a "full" name here.
thanks,
greg k-h
On Fri, Apr 21, 2017 at 09:24:57AM +0530, surenderpolsani wrote:
> kernel coding style doesn't allow the return statement
> in void function.
>
> Signed-off-by: Surenderp
Your "From" line does not match this line.
And I need a "full" name here.
thanks,
greg k-h
Ignore linux kernel's console= option at uml's console
option handler. Since uml's con= option is only for
setting up new console, and Linux kernel's console=
option specify to which console kernel output its
message, we can use both option for different purpose.
Signed-off-by: Masami Hiramatsu
Ignore linux kernel's console= option at uml's console
option handler. Since uml's con= option is only for
setting up new console, and Linux kernel's console=
option specify to which console kernel output its
message, we can use both option for different purpose.
Signed-off-by: Masami Hiramatsu
These configs are required for booting kernel in QCOM IPQ4019 boards.
Signed-off-by: Abhishek Sahu
---
arch/arm/configs/qcom_defconfig | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/configs/qcom_defconfig b/arch/arm/configs/qcom_defconfig
index
These configs are required for booting kernel in QCOM IPQ4019 boards.
Signed-off-by: Abhishek Sahu
---
arch/arm/configs/qcom_defconfig | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/configs/qcom_defconfig b/arch/arm/configs/qcom_defconfig
index 4ffdd60..28c98c6 100644
---
Suppress non-fatal boot messages when "quiet" kernel
parameter is given.
Signed-off-by: Masami Hiramatsu
---
arch/um/os-Linux/util.c | 16
1 file changed, 16 insertions(+)
diff --git a/arch/um/os-Linux/util.c b/arch/um/os-Linux/util.c
index
Suppress non-fatal boot messages when "quiet" kernel
parameter is given.
Signed-off-by: Masami Hiramatsu
---
arch/um/os-Linux/util.c | 16
1 file changed, 16 insertions(+)
diff --git a/arch/um/os-Linux/util.c b/arch/um/os-Linux/util.c
index 8745f23..7afcb41 100644
---
Print out fatal error in stderr as same as fatal() does.
Signed-off-by: Masami Hiramatsu
---
arch/um/kernel/physmem.c |8
arch/um/kernel/um_arch.c |2 +-
arch/um/os-Linux/main.c |4 ++--
3 files changed, 7 insertions(+), 7 deletions(-)
diff --git
Print out fatal error in stderr as same as fatal() does.
Signed-off-by: Masami Hiramatsu
---
arch/um/kernel/physmem.c |8
arch/um/kernel/um_arch.c |2 +-
arch/um/os-Linux/main.c |4 ++--
3 files changed, 7 insertions(+), 7 deletions(-)
diff --git
Use non_fatal() for non-fatal information or warning
messages instead of printf(). This also changes these
messages output to stderr.
Signed-off-by: Masami Hiramatsu
---
arch/um/kernel/um_arch.c | 14 --
arch/um/kernel/umid.c|4 ++--
Use non_fatal() for non-fatal information or warning
messages instead of printf(). This also changes these
messages output to stderr.
Signed-off-by: Masami Hiramatsu
---
arch/um/kernel/um_arch.c | 14 --
arch/um/kernel/umid.c|4 ++--
arch/um/os-Linux/main.c |6 +++---
Move non_fatal() to util.c and make it global so that
it can be used from other files.
Signed-off-by: Masami Hiramatsu
---
arch/um/include/shared/os.h |1 +
arch/um/os-Linux/start_up.c |9 -
arch/um/os-Linux/util.c |9 +
3 files changed, 10
Move non_fatal() to util.c and make it global so that
it can be used from other files.
Signed-off-by: Masami Hiramatsu
---
arch/um/include/shared/os.h |1 +
arch/um/os-Linux/start_up.c |9 -
arch/um/os-Linux/util.c |9 +
3 files changed, 10 insertions(+), 9
On 04/28/2017 12:21 AM, Florian Fainelli wrote:
> On 04/27/2017 02:16 PM, Florian Fainelli wrote:
>> Hi Herbert,
>>
>> On 04/26/2017 10:44 PM, Herbert Xu wrote:
>>> On Tue, Apr 25, 2017 at 10:48:22AM -0400, David Miller wrote:
From: Florian Westphal
Date: Tue, 25 Apr
On 04/28/2017 12:21 AM, Florian Fainelli wrote:
> On 04/27/2017 02:16 PM, Florian Fainelli wrote:
>> Hi Herbert,
>>
>> On 04/26/2017 10:44 PM, Herbert Xu wrote:
>>> On Tue, Apr 25, 2017 at 10:48:22AM -0400, David Miller wrote:
From: Florian Westphal
Date: Tue, 25 Apr 2017 16:17:49 +0200
Use non_fatal() instead of printf in check_coredump_limit().
Signed-off-by: Masami Hiramatsu
---
arch/um/os-Linux/start_up.c | 14 --
1 file changed, 8 insertions(+), 6 deletions(-)
diff --git a/arch/um/os-Linux/start_up.c b/arch/um/os-Linux/start_up.c
index
Use non_fatal() instead of printf in check_coredump_limit().
Signed-off-by: Masami Hiramatsu
---
arch/um/os-Linux/start_up.c | 14 --
1 file changed, 8 insertions(+), 6 deletions(-)
diff --git a/arch/um/os-Linux/start_up.c b/arch/um/os-Linux/start_up.c
index 22a358e..5052817
Since this function will be called after printk buffer
initialized, use printk as other functions do.
Signed-off-by: Masami Hiramatsu
---
arch/um/os-Linux/umid.c |6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/arch/um/os-Linux/umid.c
Since this function will be called after printk buffer
initialized, use printk as other functions do.
Signed-off-by: Masami Hiramatsu
---
arch/um/os-Linux/umid.c |6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/arch/um/os-Linux/umid.c b/arch/um/os-Linux/umid.c
index
Hello,
This series fixes some boot time printf output to stderr
by default, and support "quiet" option to suppress non-
fatal error (or warning) messages in user-mode-linux.
Also the last one allows user to pass "console=" option
to kernel.
Thank you,
---
Masami Hiramatsu (7):
um: Use
Hello,
This series fixes some boot time printf output to stderr
by default, and support "quiet" option to suppress non-
fatal error (or warning) messages in user-mode-linux.
Also the last one allows user to pass "console=" option
to kernel.
Thank you,
---
Masami Hiramatsu (7):
um: Use
On 28 April 2017 at 10:53, Mark Rutland wrote:
> On Fri, Apr 28, 2017 at 08:18:52AM +0100, Ard Biesheuvel wrote:
>> On 27 April 2017 at 23:52, Matthias Kaehlcke wrote:
>> > El Thu, Apr 27, 2017 at 12:02:56PM +0100 Mark Rutland ha dit:
>> >> On Wed, Apr
On 28 April 2017 at 10:53, Mark Rutland wrote:
> On Fri, Apr 28, 2017 at 08:18:52AM +0100, Ard Biesheuvel wrote:
>> On 27 April 2017 at 23:52, Matthias Kaehlcke wrote:
>> > El Thu, Apr 27, 2017 at 12:02:56PM +0100 Mark Rutland ha dit:
>> >> On Wed, Apr 26, 2017 at 02:46:16PM -0700, Matthias
The ceph_inode_xattr needs to be released when removing an xattr. Easily
reproducible running the 'generic/020' test from xfstests or simply by
doing:
attr -s attr0 -V 0 /mnt/test && attr -r attr0 /mnt/test
While there, also fix the error path.
Here's the kmemleak splat:
unreferenced object
The ceph_inode_xattr needs to be released when removing an xattr. Easily
reproducible running the 'generic/020' test from xfstests or simply by
doing:
attr -s attr0 -V 0 /mnt/test && attr -r attr0 /mnt/test
While there, also fix the error path.
Here's the kmemleak splat:
unreferenced object
Fixed the following sparse warning:
CHECK drivers/staging/lustre/lustre/llite//file.c
drivers/staging/lustre/lustre/llite//file.c:441:24: warning: incorrect
type in assignment (different base types)
drivers/staging/lustre/lustre/llite//file.c:441:24:expected
restricted fmode_t
Fixed the following sparse warning:
CHECK drivers/staging/lustre/lustre/llite//file.c
drivers/staging/lustre/lustre/llite//file.c:441:24: warning: incorrect
type in assignment (different base types)
drivers/staging/lustre/lustre/llite//file.c:441:24:expected
restricted fmode_t
> Il giorno 28 apr 2017, alle ore 12:10, Ulf Hansson
> ha scritto:
>
> Seems like this was forgotten in the bfq-series from Paolo. Let's do it now
> so people don't miss out involving Paolo for any future changes or when
> reporting bugs.
>
> Signed-off-by: Ulf Hansson
> Il giorno 28 apr 2017, alle ore 12:10, Ulf Hansson
> ha scritto:
>
> Seems like this was forgotten in the bfq-series from Paolo. Let's do it now
> so people don't miss out involving Paolo for any future changes or when
> reporting bugs.
>
> Signed-off-by: Ulf Hansson
Acked-by: Paolo
Seems like this was forgotten in the bfq-series from Paolo. Let's do it now
so people don't miss out involving Paolo for any future changes or when
reporting bugs.
Signed-off-by: Ulf Hansson
---
MAINTAINERS | 8
1 file changed, 8 insertions(+)
diff --git
Seems like this was forgotten in the bfq-series from Paolo. Let's do it now
so people don't miss out involving Paolo for any future changes or when
reporting bugs.
Signed-off-by: Ulf Hansson
---
MAINTAINERS | 8
1 file changed, 8 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
Hi Linus,
On Fri, Apr 28, 2017 at 10:32 AM, Linus Walleij
wrote:
> On Thu, Apr 27, 2017 at 4:56 PM, Andy Shevchenko
> wrote:
>> On Thu, Apr 27, 2017 at 11:19 AM, Jacopo Mondi
>> wrote:
>>> Add bi-directional and
Hi Linus,
On Fri, Apr 28, 2017 at 10:32 AM, Linus Walleij
wrote:
> On Thu, Apr 27, 2017 at 4:56 PM, Andy Shevchenko
> wrote:
>> On Thu, Apr 27, 2017 at 11:19 AM, Jacopo Mondi
>> wrote:
>>> Add bi-directional and output-enable pin configuration properties.
>>>
>>> bi-directional allows to
Hello,
thanks for report. I'm heading out now but I'll have a look next week. From
a quick look it seems like some problem with uniqueness of bdi names as
generated by NFS bdi.
Honza
On Fri 28-04-17 11:56:24, Corentin Labbe wrote:
Hello,
thanks for report. I'm heading out now but I'll have a look next week. From
a quick look it seems like some problem with uniqueness of bdi names as
generated by NFS bdi.
Honza
On Fri 28-04-17 11:56:24, Corentin Labbe wrote:
On Fri, Apr 28, 2017 at 05:35:29PM +0800, Xiaoguang Chen wrote:
> dmabuf for GVT-g can be exported to users who can use the dmabuf to show
> the desktop of vm which use intel vgpu.
>
> Currently we provide query and create new dmabuf operations.
>
> Users of dmabuf can cache some created dmabufs
On Fri, Apr 28, 2017 at 05:35:29PM +0800, Xiaoguang Chen wrote:
> dmabuf for GVT-g can be exported to users who can use the dmabuf to show
> the desktop of vm which use intel vgpu.
>
> Currently we provide query and create new dmabuf operations.
>
> Users of dmabuf can cache some created dmabufs
On Sun, Apr 23, 2017 at 03:21:31PM +0100, Eric Curtin wrote:
> checkpatch spits out a warning about the 80 character line limit. Split
> the parameters of these functions onto different lines. Put the ; with
> the macro caller instead. Lined up parameters as there was another
> CHECK warning about
On Fri, Apr 28, 2017 at 11:02:30AM +0100, Mark Rutland wrote:
> On Thu, Apr 27, 2017 at 07:01:04PM +0100, Will Deacon wrote:
> > On Thu, Apr 27, 2017 at 06:44:37PM +0100, Mark Rutland wrote:
> > > diff --git a/arch/arm64/kernel/cpu_errata.c
> > > b/arch/arm64/kernel/cpu_errata.c
> > > index
On Sun, Apr 23, 2017 at 03:21:31PM +0100, Eric Curtin wrote:
> checkpatch spits out a warning about the 80 character line limit. Split
> the parameters of these functions onto different lines. Put the ; with
> the macro caller instead. Lined up parameters as there was another
> CHECK warning about
On Fri, Apr 28, 2017 at 11:02:30AM +0100, Mark Rutland wrote:
> On Thu, Apr 27, 2017 at 07:01:04PM +0100, Will Deacon wrote:
> > On Thu, Apr 27, 2017 at 06:44:37PM +0100, Mark Rutland wrote:
> > > diff --git a/arch/arm64/kernel/cpu_errata.c
> > > b/arch/arm64/kernel/cpu_errata.c
> > > index
On Fri, Apr 21, 2017 at 05:54:47PM +0200, Cezary Gapinski wrote:
> Sparse reports the following in fb_watterott.c:
>
> warning: incorrect type in assignment (different base types)
> expected unsigned short [unsigned] [short] [usertype]
> got restricted __be16 [usertype]
>
> Use __be16 types
On Fri, Apr 28, 2017 at 10:16 AM, Linus Walleij
wrote:
> On Thu, Apr 27, 2017 at 10:19 AM, Jacopo Mondi
>> +#define PIN_CONF_UNPACK_PARAM(c) ((c) & 0xffUL)
>> +#define PIN_CONF_UNPACK_ARGS(c) ((c) >> 8)
>
> But why.
>
> I have these two static inlines just below your new
On Fri, Apr 21, 2017 at 05:54:47PM +0200, Cezary Gapinski wrote:
> Sparse reports the following in fb_watterott.c:
>
> warning: incorrect type in assignment (different base types)
> expected unsigned short [unsigned] [short] [usertype]
> got restricted __be16 [usertype]
>
> Use __be16 types
On Fri, Apr 28, 2017 at 10:16 AM, Linus Walleij
wrote:
> On Thu, Apr 27, 2017 at 10:19 AM, Jacopo Mondi
>> +#define PIN_CONF_UNPACK_PARAM(c) ((c) & 0xffUL)
>> +#define PIN_CONF_UNPACK_ARGS(c) ((c) >> 8)
>
> But why.
>
> I have these two static inlines just below your new macros:
>
> static inline
On 28/04/17 11:04, Geert Uytterhoeven wrote:
> On Fri, Apr 28, 2017 at 10:52 AM, Sergei Shtylyov
> wrote:
>> On 4/27/2017 9:26 PM, Kieran Bingham wrote:
>>> --- a/arch/arm64/boot/dts/renesas/r8a7795-salvator-x.dts
>>> +++
On 28/04/17 11:04, Geert Uytterhoeven wrote:
> On Fri, Apr 28, 2017 at 10:52 AM, Sergei Shtylyov
> wrote:
>> On 4/27/2017 9:26 PM, Kieran Bingham wrote:
>>> --- a/arch/arm64/boot/dts/renesas/r8a7795-salvator-x.dts
>>> +++ b/arch/arm64/boot/dts/renesas/r8a7795-salvator-x.dts
>>
>> [...]
>>>
>>> @@
On Fri, Apr 28, 2017 at 10:52 AM, Sergei Shtylyov
wrote:
> On 4/27/2017 9:26 PM, Kieran Bingham wrote:
>> --- a/arch/arm64/boot/dts/renesas/r8a7795-salvator-x.dts
>> +++ b/arch/arm64/boot/dts/renesas/r8a7795-salvator-x.dts
>
> [...]
>>
>> @@ -387,6 +403,50 @@
On Fri, Apr 28, 2017 at 10:52 AM, Sergei Shtylyov
wrote:
> On 4/27/2017 9:26 PM, Kieran Bingham wrote:
>> --- a/arch/arm64/boot/dts/renesas/r8a7795-salvator-x.dts
>> +++ b/arch/arm64/boot/dts/renesas/r8a7795-salvator-x.dts
>
> [...]
>>
>> @@ -387,6 +403,50 @@
>> };
>> };
>>
>> + {
>> +
On Wed, Apr 26, 2017 at 06:15:40PM +0200, Karim Eshapa wrote:
> Fixing sparse warnings incorrect type assignment.
>
> Signed-off-by: Karim Eshapa
> ---
> drivers/staging/wlan-ng/hfa384x_usb.c | 24 ++--
> 1 file changed, 14 insertions(+), 10
On Wed, Apr 26, 2017 at 06:15:40PM +0200, Karim Eshapa wrote:
> Fixing sparse warnings incorrect type assignment.
>
> Signed-off-by: Karim Eshapa
> ---
> drivers/staging/wlan-ng/hfa384x_usb.c | 24 ++--
> 1 file changed, 14 insertions(+), 10 deletions(-)
>
> diff --git
Hi,
> > So just not using the swapping indeed looks like the only sensible
> > option. Which in turn implies there is no BGRA support for dumb
> > bos. Hmm, I can see the problem. Userspace expectation appears to be
> > that ADDFB configures a native endian framebuffer, which the driver
Hi,
> > So just not using the swapping indeed looks like the only sensible
> > option. Which in turn implies there is no BGRA support for dumb
> > bos. Hmm, I can see the problem. Userspace expectation appears to be
> > that ADDFB configures a native endian framebuffer, which the driver
On Thu, Apr 27, 2017 at 07:01:04PM +0100, Will Deacon wrote:
> On Thu, Apr 27, 2017 at 06:44:37PM +0100, Mark Rutland wrote:
> > diff --git a/arch/arm64/kernel/cpu_errata.c b/arch/arm64/kernel/cpu_errata.c
> > index f6cc67e..379ad8d 100644
> > --- a/arch/arm64/kernel/cpu_errata.c
> > +++
On Thu, Apr 27, 2017 at 07:01:04PM +0100, Will Deacon wrote:
> On Thu, Apr 27, 2017 at 06:44:37PM +0100, Mark Rutland wrote:
> > diff --git a/arch/arm64/kernel/cpu_errata.c b/arch/arm64/kernel/cpu_errata.c
> > index f6cc67e..379ad8d 100644
> > --- a/arch/arm64/kernel/cpu_errata.c
> > +++
From: Abhishek Sahu
These configs are required for booting kernel in QCOM
IPQ8074 boards.
Signed-off-by: Abhishek Sahu
Signed-off-by: Varadarajan Narayanan
---
arch/arm64/configs/defconfig | 2 ++
1 file changed, 2
From: Abhishek Sahu
These configs are required for booting kernel in QCOM
IPQ8074 boards.
Signed-off-by: Abhishek Sahu
Signed-off-by: Varadarajan Narayanan
---
arch/arm64/configs/defconfig | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm64/configs/defconfig
From: Abhishek Sahu
This patch adds support for the global clock controller found on
the IPQ8074 based devices. This includes UART, I2C, SPI etc.
Signed-off-by: Abhishek Sahu
Signed-off-by: Varadarajan Narayanan
---
From: Abhishek Sahu
This patch adds support for the global clock controller found on
the IPQ8074 based devices. This includes UART, I2C, SPI etc.
Signed-off-by: Abhishek Sahu
Signed-off-by: Varadarajan Narayanan
---
.../devicetree/bindings/clock/qcom,gcc.txt |1 +
Add initial pinctrl driver to support pin configuration with
pinctrl framework for ipq8074.
Signed-off-by: Manoharan Vijaya Raghavan
Signed-off-by: Varadarajan Narayanan
---
.../bindings/pinctrl/qcom,ipq8074-pinctrl.txt | 202
Signed-off-by: Varadarajan Narayanan
---
Documentation/devicetree/bindings/arm/qcom.txt | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/devicetree/bindings/arm/qcom.txt
b/Documentation/devicetree/bindings/arm/qcom.txt
index 028d16e..0ed4d39 100644
---
Add initial pinctrl driver to support pin configuration with
pinctrl framework for ipq8074.
Signed-off-by: Manoharan Vijaya Raghavan
Signed-off-by: Varadarajan Narayanan
---
.../bindings/pinctrl/qcom,ipq8074-pinctrl.txt | 202
drivers/pinctrl/qcom/Kconfig |
Signed-off-by: Varadarajan Narayanan
---
Documentation/devicetree/bindings/arm/qcom.txt | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/devicetree/bindings/arm/qcom.txt
b/Documentation/devicetree/bindings/arm/qcom.txt
index 028d16e..0ed4d39 100644
---
Add initial device tree support for the Qualcomm IPQ8074 SoC and
HK01 evaluation board.
Signed-off-by: Manoharan Vijaya Raghavan
Signed-off-by: Abhishek Sahu
Signed-off-by: Varadarajan Narayanan
---
Add initial device tree support for the Qualcomm IPQ8074 SoC and
HK01 evaluation board.
Signed-off-by: Manoharan Vijaya Raghavan
Signed-off-by: Abhishek Sahu
Signed-off-by: Varadarajan Narayanan
---
arch/arm64/boot/dts/qcom/Makefile | 1 +
arch/arm64/boot/dts/qcom/ipq8074-hk01.dts |
901 - 1000 of 1460 matches
Mail list logo