* Juergen Gross wrote:
> On 11/12/17 11:09, Jan Beulich wrote:
> On 08.12.17 at 16:11, wrote:
> >> Set the boot loader version to 2.14 (0x020e) replacing the wrong 0x0212
> >> which should have been 0x020c.
> >
> > This part of the description has become
* Juergen Gross wrote:
> On 11/12/17 11:09, Jan Beulich wrote:
> On 08.12.17 at 16:11, wrote:
> >> Set the boot loader version to 2.14 (0x020e) replacing the wrong 0x0212
> >> which should have been 0x020c.
> >
> > This part of the description has become partly stale now with the
> > new
On Sun, 2017-12-10 at 12:30 -0800, Linus Torvalds wrote:
> On Sun, Dec 10, 2017 at 10:56 AM, Pavel Machek wrote:
> >
> >
> > Confirmed, revert fixes it. You see how it moves
> > fix_processor_context
> > around #ifdef CONFIG_X86_32 block? And how people forget 32-bit
> > machines
On Sun, 2017-12-10 at 12:30 -0800, Linus Torvalds wrote:
> On Sun, Dec 10, 2017 at 10:56 AM, Pavel Machek wrote:
> >
> >
> > Confirmed, revert fixes it. You see how it moves
> > fix_processor_context
> > around #ifdef CONFIG_X86_32 block? And how people forget 32-bit
> > machines exist? Aha.
>
On 11.12.2017 16:53, Dmitry Osipenko wrote:
> On 11.12.2017 13:13, Thierry Reding wrote:
>> On Mon, Dec 11, 2017 at 02:19:44AM +0300, Dmitry Osipenko wrote:
>>> Add manual HW power management to drivers probe/remove in order to
>>> not fail in a case of runtime power management being disabled in
On Mon, Dec 11, 2017 at 3:46 PM, Pavel Emelyanov wrote:
> On 12/11/2017 10:05 AM, Amir Goldstein wrote:
>> On Mon, Dec 11, 2017 at 8:41 AM, Amir Goldstein wrote:
>>> On Mon, Dec 11, 2017 at 8:04 AM, NeilBrown wrote:
If a filesystem
On 11.12.2017 16:53, Dmitry Osipenko wrote:
> On 11.12.2017 13:13, Thierry Reding wrote:
>> On Mon, Dec 11, 2017 at 02:19:44AM +0300, Dmitry Osipenko wrote:
>>> Add manual HW power management to drivers probe/remove in order to
>>> not fail in a case of runtime power management being disabled in
On Mon, Dec 11, 2017 at 3:46 PM, Pavel Emelyanov wrote:
> On 12/11/2017 10:05 AM, Amir Goldstein wrote:
>> On Mon, Dec 11, 2017 at 8:41 AM, Amir Goldstein wrote:
>>> On Mon, Dec 11, 2017 at 8:04 AM, NeilBrown wrote:
If a filesystem does not set sb->s_export_op, then it
does not
Hi Vincent,
Although I agree that moving the PELT code in a dedicated file is
probably the cleanest way to achieve what you want, I was wondering if
you were able no measure any overhead due to moving the __update_load_avg_*()
functions in a different translation unit ? This is introducing
Hi Vincent,
Although I agree that moving the PELT code in a dedicated file is
probably the cleanest way to achieve what you want, I was wondering if
you were able no measure any overhead due to moving the __update_load_avg_*()
functions in a different translation unit ? This is introducing
Cc: Marek Szyprowski , Bartlomiej Zolnierkiewicz
Hardware operations like reading random numbers and setting a seed need
to be conducted in a single thread. Therefore a mutex is required to
prevent multiple threads (processes) from accessing
Cc: Marek Szyprowski , Bartlomiej Zolnierkiewicz
Hardware operations like reading random numbers and setting a seed need
to be conducted in a single thread. Therefore a mutex is required to
prevent multiple threads (processes) from accessing the hardware at the
same time.
The sequence of
Hello,
This is a series of patches for exynos-rng driver I've decided to
create after adding support for Exynos5250+ chips. They do not
strictly depend on each other, but I think it is better to send them
as a single patch-set.
The driver requires appropriate DT configuration introduced in
Hello,
This is a series of patches for exynos-rng driver I've decided to
create after adding support for Exynos5250+ chips. They do not
strictly depend on each other, but I think it is better to send them
as a single patch-set.
The driver requires appropriate DT configuration introduced in
Cc: Marek Szyprowski , Bartlomiej Zolnierkiewicz
Use memcpy_fromio() instead of custom exynos_rng_copy_random() function
to retrieve generated numbers from the registers of PRNG.
Rearrange the loop around cpu_relax(). In a loop with while()
Cc: Marek Szyprowski , Bartlomiej Zolnierkiewicz
Add support for PRNG in Exynos5250+ SoCs.
Signed-off-by: Łukasz Stelmach
---
.../bindings/crypto/samsung,exynos-rng4.txt| 4 ++-
drivers/crypto/exynos-rng.c
On 2017-12-11 14:45, Rasmus Villemoes wrote:
> On 2017-12-11 11:02, Alexander Stein wrote:
>
>> Oh, and what is the content of register SCFG_SCFGREVCR?
>
> Good point. On my board it's 0x, set even before U-boot starts,
> and lots board support code in U-boot expects this. I can't
Cc: Marek Szyprowski , Bartlomiej Zolnierkiewicz
Use memcpy_fromio() instead of custom exynos_rng_copy_random() function
to retrieve generated numbers from the registers of PRNG.
Rearrange the loop around cpu_relax(). In a loop with while() at the
beginning and the cpu_relax() removed the
Cc: Marek Szyprowski , Bartlomiej Zolnierkiewicz
Add support for PRNG in Exynos5250+ SoCs.
Signed-off-by: Łukasz Stelmach
---
.../bindings/crypto/samsung,exynos-rng4.txt| 4 ++-
drivers/crypto/exynos-rng.c| 32 --
2 files changed, 33
On 2017-12-11 14:45, Rasmus Villemoes wrote:
> On 2017-12-11 11:02, Alexander Stein wrote:
>
>> Oh, and what is the content of register SCFG_SCFGREVCR?
>
> Good point. On my board it's 0x, set even before U-boot starts,
> and lots board support code in U-boot expects this. I can't
Cc: Marek Szyprowski , Bartlomiej Zolnierkiewicz
Reseed PRNG after reading 65 kB of randomness. Although this may reduce
performance, in most cases the loss is not noticeable.
Reseeding of a PRNG does not increase entropy, but it helps
Cc: Marek Szyprowski , Bartlomiej Zolnierkiewicz
Reseed PRNG after reading 65 kB of randomness. Although this may reduce
performance, in most cases the loss is not noticeable.
Reseeding of a PRNG does not increase entropy, but it helps preventing
backtracking the internal state of the device
* Will Deacon wrote:
> On Sat, Dec 02, 2017 at 10:02:08AM +0100, Heiko Carstens wrote:
> > On Tue, Nov 28, 2017 at 06:42:17PM +, Will Deacon wrote:
> > > The following two patches do the following:
> > >
> > > 1. Fix boot breakage reported on s390 caused by
* Will Deacon wrote:
> On Sat, Dec 02, 2017 at 10:02:08AM +0100, Heiko Carstens wrote:
> > On Tue, Nov 28, 2017 at 06:42:17PM +, Will Deacon wrote:
> > > The following two patches do the following:
> > >
> > > 1. Fix boot breakage reported on s390 caused by a8a217c22116
> > > 2. Kill
On 12/11/2017 10:05 AM, Amir Goldstein wrote:
> On Mon, Dec 11, 2017 at 8:41 AM, Amir Goldstein wrote:
>> On Mon, Dec 11, 2017 at 8:04 AM, NeilBrown wrote:
>>> If a filesystem does not set sb->s_export_op, then it
>>> does not support filehandles and
On 12/11/2017 10:05 AM, Amir Goldstein wrote:
> On Mon, Dec 11, 2017 at 8:41 AM, Amir Goldstein wrote:
>> On Mon, Dec 11, 2017 at 8:04 AM, NeilBrown wrote:
>>> If a filesystem does not set sb->s_export_op, then it
>>> does not support filehandles and export_fs_encode_fh()
>>> and
On Sun, 10 Dec 2017, Joe Perches wrote:
> > > Omit an extra message for a memory allocation failure in this function.
> > >
> > > This issue was detected by using the Coccinelle software.
> >
> > And the problem here is?
>
> Markus' terrible commit messages.
>
> Generically, any OOM via a
From: Venkat Prashanth B U
This is the patch to the omap-dma.c file that fixes
the following issues:
1.redefinition of 'omap_dma_filter_fn' in the line 1273
of drivers/dma/omap-dma.c
2.drivers/dma/omap-dma.c:341: ERROR: code indent should
use tabs where possible
On Sun, 10 Dec 2017, Joe Perches wrote:
> > > Omit an extra message for a memory allocation failure in this function.
> > >
> > > This issue was detected by using the Coccinelle software.
> >
> > And the problem here is?
>
> Markus' terrible commit messages.
>
> Generically, any OOM via a
From: Venkat Prashanth B U
This is the patch to the omap-dma.c file that fixes
the following issues:
1.redefinition of 'omap_dma_filter_fn' in the line 1273
of drivers/dma/omap-dma.c
2.drivers/dma/omap-dma.c:341: ERROR: code indent should
use tabs where possible reported by ./checkpatch.pl
Similar to other data types, this helper puts NLA_BITFIELD32 attribute into
a netlink message. It takes separate value and selector arguments, if you
already have struct nla_bitfield32, you can use nla_put().
Signed-off-by: Michal Kubecek
---
include/net/netlink.h | 15
Similar to other data types, this helper puts NLA_BITFIELD32 attribute into
a netlink message. It takes separate value and selector arguments, if you
already have struct nla_bitfield32, you can use nla_put().
Signed-off-by: Michal Kubecek
---
include/net/netlink.h | 15 +++
1 file
Misc helpers used by ethtool netlink code.
Signed-off-by: Michal Kubecek
---
net/core/ethtool_netlink.c | 177 +
1 file changed, 177 insertions(+)
diff --git a/net/core/ethtool_netlink.c b/net/core/ethtool_netlink.c
index
Misc helpers used by ethtool netlink code.
Signed-off-by: Michal Kubecek
---
net/core/ethtool_netlink.c | 177 +
1 file changed, 177 insertions(+)
diff --git a/net/core/ethtool_netlink.c b/net/core/ethtool_netlink.c
index 46a226bb9a2c..22d23d057623
On 11.12.2017 13:13, Thierry Reding wrote:
> On Mon, Dec 11, 2017 at 02:19:44AM +0300, Dmitry Osipenko wrote:
>> Add manual HW power management to drivers probe/remove in order to
>> not fail in a case of runtime power management being disabled in kernel
>> config.
>>
>> Signed-off-by: Dmitry
On 11.12.2017 13:13, Thierry Reding wrote:
> On Mon, Dec 11, 2017 at 02:19:44AM +0300, Dmitry Osipenko wrote:
>> Add manual HW power management to drivers probe/remove in order to
>> not fail in a case of runtime power management being disabled in kernel
>> config.
>>
>> Signed-off-by: Dmitry
2017-12-08 22:25 GMT+01:00 Sven Van Asbroeck :
> Fundamental properties such as capacity and page size differ
> among at24-type chips. But these chips do not have an id register,
> so this can't be discovered at runtime.
>
> Traditionally, at24-type eeprom properties were
The following changes since commit 6363b3f3ac5be096d08c8c504128befa0c033529:
Merge tag 'ipmi-for-4.15' of git://github.com/cminyard/linux-ipmi
(2017-11-15 15:12:28 -0800)
are available in the git repository at:
https://github.com/cminyard/linux-ipmi.git tags/for-linus-4.15-2
for you to
2017-12-08 22:25 GMT+01:00 Sven Van Asbroeck :
> Fundamental properties such as capacity and page size differ
> among at24-type chips. But these chips do not have an id register,
> so this can't be discovered at runtime.
>
> Traditionally, at24-type eeprom properties were determined in two ways:
>
The following changes since commit 6363b3f3ac5be096d08c8c504128befa0c033529:
Merge tag 'ipmi-for-4.15' of git://github.com/cminyard/linux-ipmi
(2017-11-15 15:12:28 -0800)
are available in the git repository at:
https://github.com/cminyard/linux-ipmi.git tags/for-linus-4.15-2
for you to
Hi gengdongjiu,
On 08/12/17 04:43, gengdongjiu wrote:
> by the way, I think also change the info.si_code to "BUS_MCEERR_AR" is
> better, as shown [1].
> BUS_MCEERR_AR can tell user space "Hardware memory error consumed on a
> error; action required".
Today its also used as the last-resort.
Hi gengdongjiu,
On 08/12/17 04:43, gengdongjiu wrote:
> by the way, I think also change the info.si_code to "BUS_MCEERR_AR" is
> better, as shown [1].
> BUS_MCEERR_AR can tell user space "Hardware memory error consumed on a
> error; action required".
Today its also used as the last-resort.
Sets the information provided by ETHTOOL_SCOALESCE, ETHTOOL_SRINGPARAM,
ETHTOOL_SPAUSEPARAM, ETHTOOL_SCHANNELS, ETHTOOL_SEEE and ETHTOOL_SFECPARAM.
Each of these has corresponding nesting attribute containing attributes for
its settings. This way, userspace can request changes equivalent to one or
Sets the information provided by ETHTOOL_SCOALESCE, ETHTOOL_SRINGPARAM,
ETHTOOL_SPAUSEPARAM, ETHTOOL_SCHANNELS, ETHTOOL_SEEE and ETHTOOL_SFECPARAM.
Each of these has corresponding nesting attribute containing attributes for
its settings. This way, userspace can request changes equivalent to one or
Sets the information provided by ETHTOOL_SLINKSETTINGS, ETHTOOL_SWOL and
ETHTOOL_SMSGLVL. Unlike with ioctl(), userspace can send only some
attributes so that we only need to call ethtool_ops callbacks which we
really need (and the "set" callback is only called when we actually changed
some
Sets the information provided by ETHTOOL_SLINKSETTINGS, ETHTOOL_SWOL and
ETHTOOL_SMSGLVL. Unlike with ioctl(), userspace can send only some
attributes so that we only need to call ethtool_ops callbacks which we
really need (and the "set" callback is only called when we actually changed
some
Requests the information provide by ETHTOOL_GCOALESCE, ETHTOOL_GRINGPARAM,
ETHTOOL_GPAUSEPARAM, ETHTOOL_GCHANNELS, ETHTOOL_GEEE and ETHTOOL_GFECPARAM.
Flags in info_mask allow selecting only some (or on) of these categories.
Signed-off-by: Michal Kubecek
---
Requests the information provide by ETHTOOL_GCOALESCE, ETHTOOL_GRINGPARAM,
ETHTOOL_GPAUSEPARAM, ETHTOOL_GCHANNELS, ETHTOOL_GEEE and ETHTOOL_GFECPARAM.
Flags in info_mask allow selecting only some (or on) of these categories.
Signed-off-by: Michal Kubecek
---
Requests the information provided by ETHTOOL_GLINKSETTINGS, ETHTOOL_GWOL
and ETHTOOL_GMSGLVL. The info_mask header field can be used to request only
part of the information. Flag ETH_SETTINGS_RF_COMPACT_BITSETS switches
between flag-by-flag list and compact bitmaps for link modes in the reply.
Requests the information provided by ETHTOOL_GLINKSETTINGS, ETHTOOL_GWOL
and ETHTOOL_GMSGLVL. The info_mask header field can be used to request only
part of the information. Flag ETH_SETTINGS_RF_COMPACT_BITSETS switches
between flag-by-flag list and compact bitmaps for link modes in the reply.
Request the same information as ETHTOOL_GDRVINFO. This is read-only so that
corresponding SET_DRVINFO exists but is only used in kernel replies. Rip
the code to query the driver out of the legacy interface and move it to
a new file ethtool_common.c so that both interfaces can use it.
Request the same information as ETHTOOL_GDRVINFO. This is read-only so that
corresponding SET_DRVINFO exists but is only used in kernel replies. Rip
the code to query the driver out of the legacy interface and move it to
a new file ethtool_common.c so that both interfaces can use it.
Hi Thomas,
Did you get a chance to review the patch series?
Thanks,
Kan
>
> On Fri, 17 Nov 2017, Liang, Kan wrote:
>
> > Hi Thomas,
> >
> > Any comments for this patch series?
>
> it's on my todo list.
Declare attribute type constants and add helper functions to handle
arbitrary length bit sets.
Signed-off-by: Michal Kubecek
---
Documentation/networking/ethtool-netlink.txt | 56 +
include/uapi/linux/ethtool_netlink.h | 31 +++
net/core/ethtool_netlink.c
Hi Thomas,
Did you get a chance to review the patch series?
Thanks,
Kan
>
> On Fri, 17 Nov 2017, Liang, Kan wrote:
>
> > Hi Thomas,
> >
> > Any comments for this patch series?
>
> it's on my todo list.
Declare attribute type constants and add helper functions to handle
arbitrary length bit sets.
Signed-off-by: Michal Kubecek
---
Documentation/networking/ethtool-netlink.txt | 56 +
include/uapi/linux/ethtool_netlink.h | 31 +++
net/core/ethtool_netlink.c | 346
No function implemented yet, only genetlink and module infrastructure.
Register/unregister genetlink family "ethtool" and allow the module to be
autoloaded by genetlink code (if built as a module, distributions would
probably prefer "y").
Signed-off-by: Michal Kubecek
---
No function implemented yet, only genetlink and module infrastructure.
Register/unregister genetlink family "ethtool" and allow the module to be
autoloaded by genetlink code (if built as a module, distributions would
probably prefer "y").
Signed-off-by: Michal Kubecek
---
This is still work in progress and only a very small part of the ioctl
interface is reimplemented but I would like to get some comments before
the patchset becomes too big and changing things becomes too tedious.
The interface used for communication between ethtool and kernel is based on
ioctl()
This is still work in progress and only a very small part of the ioctl
interface is reimplemented but I would like to get some comments before
the patchset becomes too big and changing things becomes too tedious.
The interface used for communication between ethtool and kernel is based on
ioctl()
On Mon, Dec 11 2017 at 6:33am -0500,
Arnd Bergmann wrote:
> The last bugfix apparently introduced another problem, as shown
> by this gcc warning:
>
> drivers/md/dm.c: In function '__send_changing_extent_only':
> drivers/md/dm.c:1365:28: error: 'ti' is used uninitialized in this
On Mon, Dec 11 2017 at 6:33am -0500,
Arnd Bergmann wrote:
> The last bugfix apparently introduced another problem, as shown
> by this gcc warning:
>
> drivers/md/dm.c: In function '__send_changing_extent_only':
> drivers/md/dm.c:1365:28: error: 'ti' is used uninitialized in this function
>
* Randy Dunlap wrote:
> From: Randy Dunlap
>
> Update x86-opcode-map.txt based on the October 2017 Intel SDM publication.
> Correct INVPID to INVVPID.
> Add UD0, UD1, and UD2 instruction opcodes.
>
> Signed-off-by: Randy Dunlap
* Randy Dunlap wrote:
> From: Randy Dunlap
>
> Update x86-opcode-map.txt based on the October 2017 Intel SDM publication.
> Correct INVPID to INVVPID.
> Add UD0, UD1, and UD2 instruction opcodes.
>
> Signed-off-by: Randy Dunlap
> Cc: Masami Hiramatsu
> Cc: Josh Poimboeuf
> Cc: x86
Hi Dhaval,
Thank you for the patch.
On Friday, 8 December 2017 14:35:37 EET Dhaval Shah wrote:
> SPDX-License-Identifier is used for the Xilinx Video IP and
> related drivers.
>
> Signed-off-by: Dhaval Shah
> ---
> drivers/media/platform/xilinx/xilinx-dma.c | 5
Hi Dhaval,
Thank you for the patch.
On Friday, 8 December 2017 14:35:37 EET Dhaval Shah wrote:
> SPDX-License-Identifier is used for the Xilinx Video IP and
> related drivers.
>
> Signed-off-by: Dhaval Shah
> ---
> drivers/media/platform/xilinx/xilinx-dma.c | 5 +
>
On Mon, Dec 11, 2017 at 10:34:17PM +0900, Masami Hiramatsu wrote:
> IMHO, even if we use SPDX license identifier, I recommend to use
> C-style comments as many other files do, since it is C code.
> If SPDX identifier requires C++ style, that is SPDX parser's issue
> and should be fixed to get it
On Mon, Dec 11, 2017 at 10:34:17PM +0900, Masami Hiramatsu wrote:
> IMHO, even if we use SPDX license identifier, I recommend to use
> C-style comments as many other files do, since it is C code.
> If SPDX identifier requires C++ style, that is SPDX parser's issue
> and should be fixed to get it
On Mon 11-12-17 20:59:29, zhong jiang wrote:
> On 2017/12/11 20:03, Michal Hocko wrote:
> > On Fri 01-12-17 18:13:52, zhong jiang wrote:
> >> The acpi table are very much like user input. it is likely to
> >> introduce some unreasonable node in some architecture. but
> >> they do not ingore the
On Mon 11-12-17 20:59:29, zhong jiang wrote:
> On 2017/12/11 20:03, Michal Hocko wrote:
> > On Fri 01-12-17 18:13:52, zhong jiang wrote:
> >> The acpi table are very much like user input. it is likely to
> >> introduce some unreasonable node in some architecture. but
> >> they do not ingore the
On 2017-12-11 11:02, Alexander Stein wrote:
> Oh, and what is the content of register SCFG_SCFGREVCR?
Good point. On my board it's 0x, set even before U-boot starts,
and lots board support code in U-boot expects this. I can't immediately
find examples in the linux source code that
On 2017-12-11 11:02, Alexander Stein wrote:
> Oh, and what is the content of register SCFG_SCFGREVCR?
Good point. On my board it's 0x, set even before U-boot starts,
and lots board support code in U-boot expects this. I can't immediately
find examples in the linux source code that
On 11.12.2017 12:37, Thierry Reding wrote:
> On Mon, Dec 11, 2017 at 02:07:37AM +0300, Dmitry Osipenko wrote:
>> Tegra's PHY driver has a mix of pr_err() and dev_err(), let's switch to
>> dev_err() and use common errors message formatting across the driver for
>> consistency.
>>
>> Signed-off-by:
On 11.12.2017 12:37, Thierry Reding wrote:
> On Mon, Dec 11, 2017 at 02:07:37AM +0300, Dmitry Osipenko wrote:
>> Tegra's PHY driver has a mix of pr_err() and dev_err(), let's switch to
>> dev_err() and use common errors message formatting across the driver for
>> consistency.
>>
>> Signed-off-by:
On Mon, Dec 11, 2017 at 01:16:57PM +0100, Richard Leitner wrote:
> From: Richard Leitner
>
> Some PHYs need a minimum time after the reset gpio was asserted and/or
> deasserted. To ensure we meet these timing requirements add two new
> optional devicetree parameters
On Mon, Dec 11, 2017 at 01:16:57PM +0100, Richard Leitner wrote:
> From: Richard Leitner
>
> Some PHYs need a minimum time after the reset gpio was asserted and/or
> deasserted. To ensure we meet these timing requirements add two new
> optional devicetree parameters for the phy: reset-delay-us
On Mon, Dec 11, 2017 at 11:25 AM, Linus Walleij
wrote:
> On Fri, Dec 8, 2017 at 3:11 PM, Ludovic Barre wrote:
>
>> From: Ludovic Barre
>>
>> This patch prepares the STM32 machine for the integration of Cortex-A
>> based
On Mon, Dec 11, 2017 at 11:25 AM, Linus Walleij
wrote:
> On Fri, Dec 8, 2017 at 3:11 PM, Ludovic Barre wrote:
>
>> From: Ludovic Barre
>>
>> This patch prepares the STM32 machine for the integration of Cortex-A
>> based microprocessor (MPU), on top of the existing Cortex-M
>> microcontroller
* Andy Lutomirski wrote:
> The kernel is very erratic as to which pagetables have _PAGE_USER
> set. The vsyscall page gets lucky: it seems that all of the
> relevant pagetables are among the apparently arbitrary ones that set
> _PAGE_USER. Rather than relying on chance, just
* Andy Lutomirski wrote:
> The kernel is very erratic as to which pagetables have _PAGE_USER
> set. The vsyscall page gets lucky: it seems that all of the
> relevant pagetables are among the apparently arbitrary ones that set
> _PAGE_USER. Rather than relying on chance, just explicitly set
>
> However I would indeed prefer that a commit description is at least
> exhaustive enough for such a dumb reviewer as I am to understand what is
> going on right away.
I can follow your desire in principle.
> So please make it say at least:
>
> "Remove an extraneous message that duplicates
> However I would indeed prefer that a commit description is at least
> exhaustive enough for such a dumb reviewer as I am to understand what is
> going on right away.
I can follow your desire in principle.
> So please make it say at least:
>
> "Remove an extraneous message that duplicates
Hello,
2017-12-11 21:04 GMT+09:00 Kunihiko Hayashi :
> On Mon, 11 Dec 2017 10:19:15 +0100 Phlippe Ombredanne
> wrote:
>
>> Dear Kunihiko-san,
>>
>> On Mon, Dec 11, 2017 at 8:57 AM, Kunihiko Hayashi
>> wrote:
Hello,
2017-12-11 21:04 GMT+09:00 Kunihiko Hayashi :
> On Mon, 11 Dec 2017 10:19:15 +0100 Phlippe Ombredanne
> wrote:
>
>> Dear Kunihiko-san,
>>
>> On Mon, Dec 11, 2017 at 8:57 AM, Kunihiko Hayashi
>> wrote:
>> > The UniPhier platform from Socionext provides the AVE ethernet
>> > controller
On 11.12.2017 13:25, Thierry Reding wrote:
> On Mon, Dec 11, 2017 at 02:07:38AM +0300, Dmitry Osipenko wrote:
>> UTMI pads are shared by USB controllers and reset of UTMI pads is shared
>> with the reset of USB1 controller. Currently reset of UTMI pads is done by
>> the EHCI driver and ChipIdea
On 11.12.2017 13:25, Thierry Reding wrote:
> On Mon, Dec 11, 2017 at 02:07:38AM +0300, Dmitry Osipenko wrote:
>> UTMI pads are shared by USB controllers and reset of UTMI pads is shared
>> with the reset of USB1 controller. Currently reset of UTMI pads is done by
>> the EHCI driver and ChipIdea
On Mon, Dec 11, 2017 at 08:47:00PM +0800, gengdongjiu wrote:
>
> On 2017/12/11 19:59, Dave P Martin wrote:
> > On Sat, Dec 09, 2017 at 03:28:42PM +, Dongjiu Geng wrote:
> >> ARM v8.4 extensions include support for new floating point
> >> multiplication variant instructions to the AArch64 SIMD
On Mon, Dec 11, 2017 at 08:47:00PM +0800, gengdongjiu wrote:
>
> On 2017/12/11 19:59, Dave P Martin wrote:
> > On Sat, Dec 09, 2017 at 03:28:42PM +, Dongjiu Geng wrote:
> >> ARM v8.4 extensions include support for new floating point
> >> multiplication variant instructions to the AArch64 SIMD
In testing, we found that nfsd threads may call set_groups in parallel for
the same entry cached in auth.unix.gid, racing in the call of groups_sort,
corrupting the groups for that entry and leading to permission denials for
the client.
This patch:
- Make groups_sort globally visible.
- Move
In testing, we found that nfsd threads may call set_groups in parallel for
the same entry cached in auth.unix.gid, racing in the call of groups_sort,
corrupting the groups for that entry and leading to permission denials for
the client.
This patch:
- Make groups_sort globally visible.
- Move
On Mon, Dec 11, 2017 at 02:38:45PM +0800, Wei Wang wrote:
> On 12/01/2017 11:49 PM, Michael S. Tsirkin wrote:
> > On Wed, Nov 29, 2017 at 09:55:26PM +0800, Wei Wang wrote:
> > > The guest free pages should not be discarded by the live migration thread
> > > when page poisoning is enabled with
On Mon, Dec 11, 2017 at 02:38:45PM +0800, Wei Wang wrote:
> On 12/01/2017 11:49 PM, Michael S. Tsirkin wrote:
> > On Wed, Nov 29, 2017 at 09:55:26PM +0800, Wei Wang wrote:
> > > The guest free pages should not be discarded by the live migration thread
> > > when page poisoning is enabled with
Hi Viresh,
On 12/11/2017 2:03 PM, Viresh Kumar wrote:
> On 08-12-17, 15:12, Sricharan R wrote:
>> The Platform data was removed earlier by,
>> 'commit eb96924acddc ("cpufreq: dt: Kill platform-data")'
>> since there were no users at that time.
>> Now this is required when the each of the cpu
Hi Viresh,
On 12/11/2017 2:03 PM, Viresh Kumar wrote:
> On 08-12-17, 15:12, Sricharan R wrote:
>> The Platform data was removed earlier by,
>> 'commit eb96924acddc ("cpufreq: dt: Kill platform-data")'
>> since there were no users at that time.
>> Now this is required when the each of the cpu
On Mon, 11 Dec 2017 14:20:23 +0100,
Ville Syrjälä wrote:
>
> On Mon, Dec 11, 2017 at 08:33:33AM +, Anand, Jerome wrote:
> >
> >
> > > -Original Message-
> > > From: Thomas Gleixner [mailto:t...@linutronix.de]
> > > Sent: Saturday, December 9, 2017 4:22 AM
> > > To: Ville Syrjälä
On Mon, 11 Dec 2017 14:20:23 +0100,
Ville Syrjälä wrote:
>
> On Mon, Dec 11, 2017 at 08:33:33AM +, Anand, Jerome wrote:
> >
> >
> > > -Original Message-
> > > From: Thomas Gleixner [mailto:t...@linutronix.de]
> > > Sent: Saturday, December 9, 2017 4:22 AM
> > > To: Ville Syrjälä
>
Hi Viresh,
On 12/11/2017 2:09 PM, Viresh Kumar wrote:
> On 08-12-17, 15:12, Sricharan R wrote:
>> From: Stephen Boyd
>>
>> Register a cpufreq-generic device whenever we detect that a
>> "qcom,krait" compatible CPU is present in DT.
>>
>> Cc:
>>
Hi Viresh,
On 12/11/2017 2:09 PM, Viresh Kumar wrote:
> On 08-12-17, 15:12, Sricharan R wrote:
>> From: Stephen Boyd
>>
>> Register a cpufreq-generic device whenever we detect that a
>> "qcom,krait" compatible CPU is present in DT.
>>
>> Cc:
>> Signed-off-by: Stephen Boyd
>> ---
>>
On Thu, Dec 07, 2017 at 04:40:05PM -0800, Laura Abbott wrote:
> On 12/06/2017 04:35 AM, Will Deacon wrote:
> >Hi everybody,
> >
> >This is version three of the patches formerly known as KAISER (♔).
> >
> > v1:
> > http://lists.infradead.org/pipermail/linux-arm-kernel/2017-November/542751.html
>
On Thu, Dec 07, 2017 at 04:40:05PM -0800, Laura Abbott wrote:
> On 12/06/2017 04:35 AM, Will Deacon wrote:
> >Hi everybody,
> >
> >This is version three of the patches formerly known as KAISER (♔).
> >
> > v1:
> > http://lists.infradead.org/pipermail/linux-arm-kernel/2017-November/542751.html
>
1201 - 1300 of 1744 matches
Mail list logo