From: Al Viro
Only two of dev_ioctl() callers may pass SIOCGIFCONF to it.
Separating that codepath from the rest of dev_ioctl() allows both
to simplify dev_ioctl() itself (all other cases work with struct ifreq *)
*and* seriously simplify the compat side of that beast:
From: Al Viro
Signed-off-by: Al Viro
---
include/net/wext.h | 4 ++--
net/core/dev_ioctl.c | 18 --
net/socket.c | 2 +-
net/wireless/wext-core.c | 13 +
4 files changed, 12 insertions(+), 25
From: Al Viro
Only two of dev_ioctl() callers may pass SIOCGIFCONF to it.
Separating that codepath from the rest of dev_ioctl() allows both
to simplify dev_ioctl() itself (all other cases work with struct ifreq *)
*and* seriously simplify the compat side of that beast: all it takes
is passing to
From: Al Viro
Signed-off-by: Al Viro
---
include/net/wext.h | 4 ++--
net/core/dev_ioctl.c | 18 --
net/socket.c | 2 +-
net/wireless/wext-core.c | 13 +
4 files changed, 12 insertions(+), 25 deletions(-)
diff --git a/include/net/wext.h
From: Al Viro
no users since 2014
Signed-off-by: Al Viro
---
include/linux/net.h | 1 -
net/socket.c| 13 -
2 files changed, 14 deletions(-)
diff --git a/include/linux/net.h b/include/linux/net.h
index
From: Al Viro
it's been equivalent to sock_do_ioctl() since 2009...
Signed-off-by: Al Viro
---
net/socket.c | 38 --
1 file changed, 38 deletions(-)
diff --git a/net/socket.c b/net/socket.c
index
From: Al Viro
Signed-off-by: Al Viro
---
include/net/route.h | 2 +-
net/ipv4/af_inet.c | 7 ++-
net/ipv4/fib_frontend.c | 8 ++--
net/ipv4/ipconfig.c | 13 +
4 files changed, 10 insertions(+), 20
From: Al Viro
no users since 2014
Signed-off-by: Al Viro
---
include/linux/net.h | 1 -
net/socket.c| 13 -
2 files changed, 14 deletions(-)
diff --git a/include/linux/net.h b/include/linux/net.h
index caeb159abda5..68acc54976bf 100644
--- a/include/linux/net.h
+++
From: Al Viro
it's been equivalent to sock_do_ioctl() since 2009...
Signed-off-by: Al Viro
---
net/socket.c | 38 --
1 file changed, 38 deletions(-)
diff --git a/net/socket.c b/net/socket.c
index 112216c537e7..f280258bd6a4 100644
--- a/net/socket.c
+++
From: Al Viro
Signed-off-by: Al Viro
---
include/net/route.h | 2 +-
net/ipv4/af_inet.c | 7 ++-
net/ipv4/fib_frontend.c | 8 ++--
net/ipv4/ipconfig.c | 13 +
4 files changed, 10 insertions(+), 20 deletions(-)
diff --git a/include/net/route.h
On Thursday, January 18, 2018 12:26:37 PM CET Mika Westerberg wrote:
> On Thu, Jan 18, 2018 at 12:20:32PM +0200, Mika Westerberg wrote:
> > On Wed, Jan 17, 2018 at 12:53:41PM +0100, Takashi Iwai wrote:
> > > Unfortunately we couldn't get approval yet, since it's a prototype
> > > machine.
> >
> >
On Thursday, January 18, 2018 12:26:37 PM CET Mika Westerberg wrote:
> On Thu, Jan 18, 2018 at 12:20:32PM +0200, Mika Westerberg wrote:
> > On Wed, Jan 17, 2018 at 12:53:41PM +0100, Takashi Iwai wrote:
> > > Unfortunately we couldn't get approval yet, since it's a prototype
> > > machine.
> >
> >
On Thu, Jan 18, 2018 at 11:09:31AM -0800, Guenter Roeck wrote:
> Hi folks,
>
> On Thu, Jan 11, 2018 at 09:46:24PM +, Woodhouse, David wrote:
> > Getting objtool to understand retpolines is going to be a bit of a
> > challenge. For now, take advantage of the fact that retpolines are
> >
On Thu, Jan 18, 2018 at 11:09:31AM -0800, Guenter Roeck wrote:
> Hi folks,
>
> On Thu, Jan 11, 2018 at 09:46:24PM +, Woodhouse, David wrote:
> > Getting objtool to understand retpolines is going to be a bit of a
> > challenge. For now, take advantage of the fact that retpolines are
> >
Fixes the following sparse warning:
mm/memcontrol.c:1097:14: warning:
symbol 'memcg1_stats' was not declared. Should it be static?
Signed-off-by: Christopher Díaz Riveros
---
mm/memcontrol.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Fixes the following sparse warning:
mm/memcontrol.c:1097:14: warning:
symbol 'memcg1_stats' was not declared. Should it be static?
Signed-off-by: Christopher Díaz Riveros
---
mm/memcontrol.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/mm/memcontrol.c b/mm/memcontrol.c
On Thu, Jan 18, 2018 at 04:43:02AM +, Al Viro wrote:
> We could turn ->msg_control/->msg_controllen into another
> iov_iter, but seeing that we never do scatter-gather for those
> IMO that would be a massive overkill. A flag controlling whether
> ->msg_control is kernel or userland
On Thu, Jan 18, 2018 at 04:43:02AM +, Al Viro wrote:
> We could turn ->msg_control/->msg_controllen into another
> iov_iter, but seeing that we never do scatter-gather for those
> IMO that would be a massive overkill. A flag controlling whether
> ->msg_control is kernel or userland
Hi!
Ubifs seems to have atime support these days:
sb->s_flags |= SB_ACTIVE;
#ifndef CONFIG_UBIFS_ATIME_SUPPORT
sb->s_flags |= SB_NOATIME;
#else
ubifs_msg(c, "full atime support is enabled.");
#endif
Which can be configured at compile-time, but no option to disable
Hi!
Ubifs seems to have atime support these days:
sb->s_flags |= SB_ACTIVE;
#ifndef CONFIG_UBIFS_ATIME_SUPPORT
sb->s_flags |= SB_NOATIME;
#else
ubifs_msg(c, "full atime support is enabled.");
#endif
Which can be configured at compile-time, but no option to disable
On Thursday, January 18, 2018 7:34:04 AM CET Viresh Kumar wrote:
> On 22-12-17, 12:56, Viresh Kumar wrote:
> > Hi,
> >
> > Now that the DT bindings [1] are already Reviewed/Acked by respective
> > maintainers, here is the code to start using them.
> >
> > The first two patches provide helpers in
On Thursday, January 18, 2018 7:34:04 AM CET Viresh Kumar wrote:
> On 22-12-17, 12:56, Viresh Kumar wrote:
> > Hi,
> >
> > Now that the DT bindings [1] are already Reviewed/Acked by respective
> > maintainers, here is the code to start using them.
> >
> > The first two patches provide helpers in
Hi Jacob,
I've got minor comments after working with this patch, sorry for the
multiple replies
On 17/11/17 18:55, Jacob Pan wrote:
[...]
> diff --git a/drivers/iommu/iommu.c b/drivers/iommu/iommu.c
> index 829e9e9..97b7990 100644
> --- a/drivers/iommu/iommu.c
> +++ b/drivers/iommu/iommu.c
> @@
Hi Jacob,
I've got minor comments after working with this patch, sorry for the
multiple replies
On 17/11/17 18:55, Jacob Pan wrote:
[...]
> diff --git a/drivers/iommu/iommu.c b/drivers/iommu/iommu.c
> index 829e9e9..97b7990 100644
> --- a/drivers/iommu/iommu.c
> +++ b/drivers/iommu/iommu.c
> @@
On Thu, 2018-01-18 at 10:08 -0500, Christopher Díaz Riveros wrote:
> Fixes the following sparse warning:
>
> mm/memcontrol.c:1097:14: warning:
> symbol 'memcg1_stats' was not declared. Should it be static?
>
> Signed-off-by: Christopher Díaz Riveros
> ---
>
On Thu, 2018-01-18 at 10:08 -0500, Christopher Díaz Riveros wrote:
> Fixes the following sparse warning:
>
> mm/memcontrol.c:1097:14: warning:
> symbol 'memcg1_stats' was not declared. Should it be static?
>
> Signed-off-by: Christopher Díaz Riveros
> ---
> mm/memcontrol.c | 2 +-
> 1 file
On Wed, Jan 17, 2018 at 10:45:19AM +, Colin King wrote:
> From: Colin Ian King
>
> The variable pwr_cmd is being assigned to cyapa->suspend_power_mode
> twice, once during the declaration and once after taking an
> interruptible mutex lock. Remove the redundant
On Wed, Jan 17, 2018 at 10:45:19AM +, Colin King wrote:
> From: Colin Ian King
>
> The variable pwr_cmd is being assigned to cyapa->suspend_power_mode
> twice, once during the declaration and once after taking an
> interruptible mutex lock. Remove the redundant first assignment
> since the
On Thu, Jan 18, 2018 at 07:58:11PM +0100, Corentin Labbe wrote:
> Since AVR32 arch is gone, at32psif driver is useless.
> This patch remove it.
>
> Signed-off-by: Corentin Labbe
Applied, thank you.
What about:
config TOUCHSCREEN_WM97XX_ATMEL
tristate "WM97xx
On Thu, Jan 18, 2018 at 07:58:11PM +0100, Corentin Labbe wrote:
> Since AVR32 arch is gone, at32psif driver is useless.
> This patch remove it.
>
> Signed-off-by: Corentin Labbe
Applied, thank you.
What about:
config TOUCHSCREEN_WM97XX_ATMEL
tristate "WM97xx Atmel accelerated touch"
Hi Vineet,
On Thu, 2018-01-18 at 10:54 -0800, Vineet Gupta wrote:
> On 01/18/2018 05:48 AM, Alexey Brodkin wrote:
> > HS48 core starts with dual-issue enabled but in some cases like
> > debugging as well as benchmarking it might be useful to disable
> > dual-issue for a particular run.
> >
> >
Hi Vineet,
On Thu, 2018-01-18 at 10:54 -0800, Vineet Gupta wrote:
> On 01/18/2018 05:48 AM, Alexey Brodkin wrote:
> > HS48 core starts with dual-issue enabled but in some cases like
> > debugging as well as benchmarking it might be useful to disable
> > dual-issue for a particular run.
> >
> >
On Thu, Jan 18, 2018 at 10:30:18PM +0900, Tetsuo Handa wrote:
> On 2018/01/18 1:44, Michael S. Tsirkin wrote:
> >> +static void add_one_sg(struct virtqueue *vq, unsigned long pfn, uint32_t
> >> len)
> >> +{
> >> + struct scatterlist sg;
> >> + unsigned int unused;
> >> + int err;
> >> +
> >> +
On Thu, Jan 18, 2018 at 10:30:18PM +0900, Tetsuo Handa wrote:
> On 2018/01/18 1:44, Michael S. Tsirkin wrote:
> >> +static void add_one_sg(struct virtqueue *vq, unsigned long pfn, uint32_t
> >> len)
> >> +{
> >> + struct scatterlist sg;
> >> + unsigned int unused;
> >> + int err;
> >> +
> >> +
Hi folks,
On Thu, Jan 11, 2018 at 09:46:24PM +, Woodhouse, David wrote:
> Getting objtool to understand retpolines is going to be a bit of a
> challenge. For now, take advantage of the fact that retpolines are
> patched in with alternatives. Just read the original (sane)
> non-alternative
Hi folks,
On Thu, Jan 11, 2018 at 09:46:24PM +, Woodhouse, David wrote:
> Getting objtool to understand retpolines is going to be a bit of a
> challenge. For now, take advantage of the fact that retpolines are
> patched in with alternatives. Just read the original (sane)
> non-alternative
On Thu, Jan 18, 2018 at 12:24:31PM -0600, Josh Poimboeuf wrote:
> On Thu, Jan 18, 2018 at 06:12:36PM +0100, Paolo Bonzini wrote:
> > On 18/01/2018 18:08, Dave Hansen wrote:
> > > On 01/18/2018 08:37 AM, Josh Poimboeuf wrote:
> > >>>
> > >>> --- a/Documentation/admin-guide/kernel-parameters.txt
> >
On Thu, Jan 18, 2018 at 12:24:31PM -0600, Josh Poimboeuf wrote:
> On Thu, Jan 18, 2018 at 06:12:36PM +0100, Paolo Bonzini wrote:
> > On 18/01/2018 18:08, Dave Hansen wrote:
> > > On 01/18/2018 08:37 AM, Josh Poimboeuf wrote:
> > >>>
> > >>> --- a/Documentation/admin-guide/kernel-parameters.txt
> >
Since AVR32 arch is gone, at32psif driver is useless.
This patch remove it.
Signed-off-by: Corentin Labbe
---
drivers/input/serio/Kconfig| 10 --
drivers/input/serio/Makefile | 1 -
drivers/input/serio/at32psif.c | 357
Since AVR32 arch is gone, at32psif driver is useless.
This patch remove it.
Signed-off-by: Corentin Labbe
---
drivers/input/serio/Kconfig| 10 --
drivers/input/serio/Makefile | 1 -
drivers/input/serio/at32psif.c | 357 -
3 files changed, 368
On 01/18/2018 06:10 AM, Sekhar Nori wrote:
On Monday 08 January 2018 07:47 AM, David Lechner wrote:
This adds a new binding for TI DA8XX USB PHY clocks. These clocks are part
of a syscon register called CFGCHIP3.
CFGCHIP2
Signed-off-by: David Lechner
+Examples:
+
On 01/18/2018 06:10 AM, Sekhar Nori wrote:
On Monday 08 January 2018 07:47 AM, David Lechner wrote:
This adds a new binding for TI DA8XX USB PHY clocks. These clocks are part
of a syscon register called CFGCHIP3.
CFGCHIP2
Signed-off-by: David Lechner
+Examples:
+
+ cfgchip:
On Thu, 18 Jan 2018 10:02:17 -0800
Andi Kleen wrote:
> Dave Young writes:
> > printk("%sHardware name: %s\n",
> >log_lvl, dump_stack_arch_desc_str);
> > + if (kexec_crash_loaded())
> > + printk("%skdump kernel
On Thu, 18 Jan 2018 10:02:17 -0800
Andi Kleen wrote:
> Dave Young writes:
> > printk("%sHardware name: %s\n",
> >log_lvl, dump_stack_arch_desc_str);
> > + if (kexec_crash_loaded())
> > + printk("%skdump kernel loaded\n", log_lvl);
>
> Oops/warnings
On 01/18/2018 05:48 AM, Alexey Brodkin wrote:
HS48 core starts with dual-issue enabled but in some cases like
debugging as well as benchmarking it might be useful to disable
dual-issue for a particular run.
Note:
1. To disable dual-issue user has to change a value of a global variable
On 01/18/2018 05:48 AM, Alexey Brodkin wrote:
HS48 core starts with dual-issue enabled but in some cases like
debugging as well as benchmarking it might be useful to disable
dual-issue for a particular run.
Note:
1. To disable dual-issue user has to change a value of a global variable
On Thu, Jan 18, 2018 at 10:25:21AM -0800, Randy Dunlap wrote:
> On 01/17/2018 01:53 PM, Dmitry Torokhov wrote:
> > On Wed, Jan 17, 2018 at 10:30:10PM +0100, Marcus Folkesson wrote:
> >> A driver should not enable an entire subsystem.
> >
> > I disagree. As you go through menuconfig and you
On Thu, Jan 18, 2018 at 10:25:21AM -0800, Randy Dunlap wrote:
> On 01/17/2018 01:53 PM, Dmitry Torokhov wrote:
> > On Wed, Jan 17, 2018 at 10:30:10PM +0100, Marcus Folkesson wrote:
> >> A driver should not enable an entire subsystem.
> >
> > I disagree. As you go through menuconfig and you
On Thu, Jan 18, 2018 at 12:55:47PM -0500, Colin Walters wrote:
>
> FWIW:
> https://git.gnome.org/browse/glib/commit/?id=3904c8761a60dbadbdfaf98fe23ff19cbdcc4a9a
>
> Since that a lot of userspace (including NetworkManager) uses eventfd. I
> haven't
> tried this patchset myself but I'd look at
On Thu, Jan 18, 2018 at 12:55:47PM -0500, Colin Walters wrote:
>
> FWIW:
> https://git.gnome.org/browse/glib/commit/?id=3904c8761a60dbadbdfaf98fe23ff19cbdcc4a9a
>
> Since that a lot of userspace (including NetworkManager) uses eventfd. I
> haven't
> tried this patchset myself but I'd look at
On Thu, Jan 18, 2018 at 02:03:07PM +0100, David Woodhouse wrote:
> On Thu, 2018-01-18 at 05:01 -0800, Andi Kleen wrote:
> > >
> > > Side effect: [1/3] will move __x86_indirect_thunk_* functions
> > > in kernel text area. Of course those functions were in the
> > > .text area, but placed in right
On 01/18/2018 07:05 AM, Sekhar Nori wrote:
On Monday 08 January 2018 07:47 AM, David Lechner wrote:
+static int da8xx_usb1_phy_clk_set_parent(struct clk_hw *hw, u8 index)
+{
+ struct da8xx_usb1_phy_clk *clk = to_da8xx_usb1_phy_clk(hw);
+ unsigned int mask, val;
+
+ /* Set the
On Thu, Jan 18, 2018 at 02:03:07PM +0100, David Woodhouse wrote:
> On Thu, 2018-01-18 at 05:01 -0800, Andi Kleen wrote:
> > >
> > > Side effect: [1/3] will move __x86_indirect_thunk_* functions
> > > in kernel text area. Of course those functions were in the
> > > .text area, but placed in right
On 01/18/2018 07:05 AM, Sekhar Nori wrote:
On Monday 08 January 2018 07:47 AM, David Lechner wrote:
+static int da8xx_usb1_phy_clk_set_parent(struct clk_hw *hw, u8 index)
+{
+ struct da8xx_usb1_phy_clk *clk = to_da8xx_usb1_phy_clk(hw);
+ unsigned int mask, val;
+
+ /* Set the
On 01/18/2018 05:48 AM, Alexey Brodkin wrote:
Signed-off-by: Alexey Brodkin
---
arch/arc/Kconfig | 5 +
arch/arc/include/asm/processor.h | 11 +++
arch/arc/lib/memcpy-archs.S | 16
arch/arc/lib/memset-archs.S |
On 01/18/2018 05:48 AM, Alexey Brodkin wrote:
Signed-off-by: Alexey Brodkin
---
arch/arc/Kconfig | 5 +
arch/arc/include/asm/processor.h | 11 +++
arch/arc/lib/memcpy-archs.S | 16
arch/arc/lib/memset-archs.S | 6 ++
4 files
On Thu, 2018-01-18 at 13:30 -0500, Mike Snitzer wrote:
> 1%!? Where are you getting that number? Ming has detailed more
> significant performance gains than 1%.. and not just on lpfc (though you
> keep seizing on lpfc because of the low queue_depth of 3).
That's what I derived from the numbers
Read-only pll don't need param table to recalculate the rate. Providing
them with a param table is just a waste of memory.
Remove the useless tables from sys_pll on gxbb and axg.
Signed-off-by: Jerome Brunet
---
drivers/clk/meson/axg.c | 94
On Thu, 2018-01-18 at 13:30 -0500, Mike Snitzer wrote:
> 1%!? Where are you getting that number? Ming has detailed more
> significant performance gains than 1%.. and not just on lpfc (though you
> keep seizing on lpfc because of the low queue_depth of 3).
That's what I derived from the numbers
Read-only pll don't need param table to recalculate the rate. Providing
them with a param table is just a waste of memory.
Remove the useless tables from sys_pll on gxbb and axg.
Signed-off-by: Jerome Brunet
---
drivers/clk/meson/axg.c | 94
The pll driver perform the rate calculation in Mhz, which adds an
unnecessary rounding down to the Mhz of the rate. Use 64bits long
integer to perform this calculation safely on meson8b and perform the
calculation in Hz instead
Fixes: 7a29a869434e ("clk: meson: Add support for Meson clock
The pll driver perform the rate calculation in Mhz, which adds an
unnecessary rounding down to the Mhz of the rate. Use 64bits long
integer to perform this calculation safely on meson8b and perform the
calculation in Hz instead
Fixes: 7a29a869434e ("clk: meson: Add support for Meson clock
This changeset is collection of fixes and clean-up around the pll clock
provider. This has been triggered by the discussion around the ethernet
clock on the axg [0].
On the axg the rate reported by the fixed_pll was off by 8Mhz,
which led the internal mux of the ethernet driver to pick an mpll2
This changeset is collection of fixes and clean-up around the pll clock
provider. This has been triggered by the discussion around the ethernet
clock on the axg [0].
On the axg the rate reported by the fixed_pll was off by 8Mhz,
which led the internal mux of the ethernet driver to pick an mpll2
Use the fractional part width in the calculation instead of 12, which
happens to e the witdh right now. This is safer in case the field width
ever change in the future
Signed-off-by: Jerome Brunet
---
drivers/clk/meson/clk-pll.c | 2 +-
1 file changed, 1 insertion(+), 1
Make sure the rate param table is available before using it.
Some read-only pll don't provide it, which is ok because the
table is not used by read-only clock. R/W clock are supposed
to provide it, but it does not hurt check it.
Signed-off-by: Jerome Brunet
---
Use the fractional part width in the calculation instead of 12, which
happens to e the witdh right now. This is safer in case the field width
ever change in the future
Signed-off-by: Jerome Brunet
---
drivers/clk/meson/clk-pll.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Make sure the rate param table is available before using it.
Some read-only pll don't provide it, which is ok because the
table is not used by read-only clock. R/W clock are supposed
to provide it, but it does not hurt check it.
Signed-off-by: Jerome Brunet
---
drivers/clk/meson/clk-pll.c | 10
On Thu, Jan 18, 2018 at 12:35:23PM -0600, Josh Poimboeuf wrote:
> Maybe I missed the memo, why do we need both X86_FEATURE_IBPB and
> X86_FEATURE_AMD_IBPB?
So AMD_IBPB is a different CPUID bit in a different CPUID function
and on Intel, IBPB is set only when X86_FEATURE_SPEC_CTRL - see
The rate of the parent should not be multiplied by 2 when there is a
fractional part to the pll. This is making the rate calculation of
gxl_hdmi_pll wrong (and others as well). This multiplication is specific
to the hdmi_pll of gxbb and is most likely due to a multiplier sitting
in front of this
On Thu, Jan 18, 2018 at 12:35:23PM -0600, Josh Poimboeuf wrote:
> Maybe I missed the memo, why do we need both X86_FEATURE_IBPB and
> X86_FEATURE_AMD_IBPB?
So AMD_IBPB is a different CPUID bit in a different CPUID function
and on Intel, IBPB is set only when X86_FEATURE_SPEC_CTRL - see
The rate of the parent should not be multiplied by 2 when there is a
fractional part to the pll. This is making the rate calculation of
gxl_hdmi_pll wrong (and others as well). This multiplication is specific
to the hdmi_pll of gxbb and is most likely due to a multiplier sitting
in front of this
The fixed_pll of gxbb and gxl also has a fractional parameter. This has
not been a problem so far because fractional part is actually set to 0
on these platforms, so the rate remains correct when it is ignored.
Still, it is better represent the pll the way it is, so add the frac
parameter now
The fixed_pll of gxbb and gxl also has a fractional parameter. This has
not been a problem so far because fractional part is actually set to 0
on these platforms, so the rate remains correct when it is ignored.
Still, it is better represent the pll the way it is, so add the frac
parameter now
The hdmi pll used in the gxl family is actually different from the gxbb.
The register layout is completely different, which explain why the hdmi
pll rate has always been rubbish on the gxl.
Adding the correct register field is the first part of the fix to get a
correct rate out the hdmi pll
The hdmi pll used in the gxl family is actually different from the gxbb.
The register layout is completely different, which explain why the hdmi
pll rate has always been rubbish on the gxl.
Adding the correct register field is the first part of the fix to get a
correct rate out the hdmi pll
Some meson plls, such as the hdmi pll, are using a 3rd od parameter,
which is yet another "power of 2" post divider. Add it to fix the
calculation of the hdmi_pll rate
Fixes: 738f66d3211d ("clk: gxbb: add AmLogic GXBB clk controller driver")
Signed-off-by: Jerome Brunet
---
Some meson plls, such as the hdmi pll, are using a 3rd od parameter,
which is yet another "power of 2" post divider. Add it to fix the
calculation of the hdmi_pll rate
Fixes: 738f66d3211d ("clk: gxbb: add AmLogic GXBB clk controller driver")
Signed-off-by: Jerome Brunet
---
The fixed_pll also has a fractional part. On axg s400 board, without
this parameter, the calculated rate is off by ~8Mhz (0,4%). The fixed_pll
being the root of peripheral clock tree, this error is propagated to the
rest of the clocks
Adding the definition of the parameter fixes the problem
The fixed_pll also has a fractional part. On axg s400 board, without
this parameter, the calculated rate is off by ~8Mhz (0,4%). The fixed_pll
being the root of peripheral clock tree, this error is propagated to the
rest of the clocks
Adding the definition of the parameter fixes the problem
On 01/18/2018 09:14 AM, Sekhar Nori wrote:
On Monday 08 January 2018 07:47 AM, David Lechner wrote:
+int __init da8xx_register_usb20_phy_clk(bool use_usb_refclkin)
+{
+ struct regmap *cfgchip;
+ struct clk *usb0_psc_clk, *clk;
+ struct clk_hw *parent;
+
+ cfgchip =
On 01/18/2018 09:14 AM, Sekhar Nori wrote:
On Monday 08 January 2018 07:47 AM, David Lechner wrote:
+int __init da8xx_register_usb20_phy_clk(bool use_usb_refclkin)
+{
+ struct regmap *cfgchip;
+ struct clk *usb0_psc_clk, *clk;
+ struct clk_hw *parent;
+
+ cfgchip =
This fall-through comment is both misspelled and unneeded (it appears
between case statements, not between operations before a case statement).
Signed-off-by: Kees Cook
---
arch/x86/kernel/cpu/bugs.c | 1 -
1 file changed, 1 deletion(-)
diff --git
This fall-through comment is both misspelled and unneeded (it appears
between case statements, not between operations before a case statement).
Signed-off-by: Kees Cook
---
arch/x86/kernel/cpu/bugs.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/x86/kernel/cpu/bugs.c
On 01/18/2018 09:27 AM, Sekhar Nori wrote:
On Monday 08 January 2018 07:55 AM, David Lechner wrote:
This removes all of the clock init code from da8xx-dt.c. This includes
all of the OF_DEV_AUXDATA that was just used for looking up clocks.
Note: You need to have clocks defined in your device
From: Tvrtko Ursulin
For situations where sysadmins might want to allow different level of
of access control for different PMUs, we start creating per-PMU
perf_event_paranoid controls in sysfs.
These work in equivalent fashion as the existing perf_event_paranoid
On 01/18/2018 09:27 AM, Sekhar Nori wrote:
On Monday 08 January 2018 07:55 AM, David Lechner wrote:
This removes all of the clock init code from da8xx-dt.c. This includes
all of the OF_DEV_AUXDATA that was just used for looking up clocks.
Note: You need to have clocks defined in your device
From: Tvrtko Ursulin
For situations where sysadmins might want to allow different level of
of access control for different PMUs, we start creating per-PMU
perf_event_paranoid controls in sysfs.
These work in equivalent fashion as the existing perf_event_paranoid
sysctl, which now becomes the
On Tue, Jan 16, 2018 at 05:34:07PM +0800, Tianyu Lan wrote:
> kvm_valid_sregs() should use X86_CR0_PG and X86_CR4_PAE to check bit
> status rather than X86_CR0_PG_BIT and X86_CR4_PAE_BIT. This patch is
> to fix it.
>
> Fixes: f29810335965a(KVM/x86: Check input paging mode when cs.l is set)
>
On Tue, Jan 16, 2018 at 05:34:07PM +0800, Tianyu Lan wrote:
> kvm_valid_sregs() should use X86_CR0_PG and X86_CR4_PAE to check bit
> status rather than X86_CR0_PG_BIT and X86_CR4_PAE_BIT. This patch is
> to fix it.
>
> Fixes: f29810335965a(KVM/x86: Check input paging mode when cs.l is set)
>
Crypto framework requires export/import in async hash. If driver do not
implement them, wrapper functions in framework will be used, and it will
cause error during ahash alg registration (unless one disables crypto
internal tests). To make change in framework and expose this requirement,
I will
Crypto framework requires export/import in async hash. If driver do not
implement them, wrapper functions in framework will be used, and it will
cause error during ahash alg registration (unless one disables crypto
internal tests). To make change in framework and expose this requirement,
I will
Crypto framework requires export/import in async hash. If driver do not
implement them, wrapper functions in framework will be used, and it will
cause error during ahash alg registration (unless one disables crypto
internal tests). To make change in framework and expose this requirement,
I will
Crypto framework requires export/import in async hash. If driver do not
implement them, wrapper functions in framework will be used, and it will
cause error during ahash alg registration (unless one disables crypto
internal tests). To make change in framework and expose this requirement,
I will
On Thu, Jan 18, 2018 at 05:39:02PM +0100, Arnd Bergmann wrote:
[...]
> > However, since pci_irqd_intx_xlate is only defined inside
> > CONFIG_PCI, even 489f8fe6aa71 will not help.
> >
> > Not completely sure about this, but perhaps a better fix is:
> >
> > +++ b/include/linux/pci.h
> > @@
On Thu, Jan 18, 2018 at 05:39:02PM +0100, Arnd Bergmann wrote:
[...]
> > However, since pci_irqd_intx_xlate is only defined inside
> > CONFIG_PCI, even 489f8fe6aa71 will not help.
> >
> > Not completely sure about this, but perhaps a better fix is:
> >
> > +++ b/include/linux/pci.h
> > @@
Export and import are mandatory in async hash. As drivers were
rewritten, drop empty wrappers and correct init of ahash transformation.
Signed-off-by: Kamil Konieczny
---
crypto/ahash.c | 18 ++
1 file changed, 2 insertions(+), 16 deletions(-)
Export and import are mandatory in async hash. As drivers were
rewritten, drop empty wrappers and correct init of ahash transformation.
Signed-off-by: Kamil Konieczny
---
crypto/ahash.c | 18 ++
1 file changed, 2 insertions(+), 16 deletions(-)
diff --git a/crypto/ahash.c
On Thu, Jan 18, 2018 at 07:31:16PM +0100, Borislav Petkov wrote:
> On Thu, Jan 18, 2018 at 02:48:29PM +0100, Peter Zijlstra wrote:
> > From: Thomas Gleixner
>
> <--- Add commit message here.
>
> > Signed-off-by: Thomas Gleixner
> > Signed-off-by: Peter
On Thu, Jan 18, 2018 at 07:31:16PM +0100, Borislav Petkov wrote:
> On Thu, Jan 18, 2018 at 02:48:29PM +0100, Peter Zijlstra wrote:
> > From: Thomas Gleixner
>
> <--- Add commit message here.
>
> > Signed-off-by: Thomas Gleixner
> > Signed-off-by: Peter Zijlstra (Intel)
> > ---
> >
701 - 800 of 1962 matches
Mail list logo