Commit 0a1eb2d474ed ("fs/proc: Stop reporting eip and esp in
/proc/PID/stat") stopped reporting eip/esp because it is
racey and dangerous for executing tasks. The comment adds:
As far as I know, there are no use programs that make any
material use of these fields, so just get rid of them.
Commit 0a1eb2d474ed ("fs/proc: Stop reporting eip and esp in
/proc/PID/stat") stopped reporting eip/esp because it is
racey and dangerous for executing tasks. The comment adds:
As far as I know, there are no use programs that make any
material use of these fields, so just get rid of them.
On 2017/9/14 17:19, Wanpeng Li wrote:
2017-09-14 16:36 GMT+08:00 Quan Xu :
on 2017/9/13 19:56, Yang Zhang wrote:
On 2017/8/29 22:56, Michael S. Tsirkin wrote:
On Tue, Aug 29, 2017 at 11:46:34AM +, Yang Zhang wrote:
Some latency-intensive workload will see obviously
On 2017/9/14 17:19, Wanpeng Li wrote:
2017-09-14 16:36 GMT+08:00 Quan Xu :
on 2017/9/13 19:56, Yang Zhang wrote:
On 2017/8/29 22:56, Michael S. Tsirkin wrote:
On Tue, Aug 29, 2017 at 11:46:34AM +, Yang Zhang wrote:
Some latency-intensive workload will see obviously performance
drop
On (09/14/17 11:15), Laurent Dufour wrote:
> On 14/09/2017 11:11, Sergey Senozhatsky wrote:
> > On (09/14/17 10:58), Laurent Dufour wrote:
> > [..]
> >> That's right, but here this is the sequence counter mm->mm_seq, not the
> >> vm_seq one.
> >
> > d'oh... you are right.
>
> So I'm doubting
On (09/14/17 11:15), Laurent Dufour wrote:
> On 14/09/2017 11:11, Sergey Senozhatsky wrote:
> > On (09/14/17 10:58), Laurent Dufour wrote:
> > [..]
> >> That's right, but here this is the sequence counter mm->mm_seq, not the
> >> vm_seq one.
> >
> > d'oh... you are right.
>
> So I'm doubting
On 14/09/2017 at 09:41, romain izard wrote:
> 2017-09-13 19:03 GMT+02:00 Alexandre Belloni
> :
>> On 13/09/2017 at 14:29:35 +0200, Nicolas Ferre wrote:
>>> On 08/09/2017 at 17:35, Romain Izard wrote:
From: Romain Izard
On 14/09/2017 at 09:41, romain izard wrote:
> 2017-09-13 19:03 GMT+02:00 Alexandre Belloni
> :
>> On 13/09/2017 at 14:29:35 +0200, Nicolas Ferre wrote:
>>> On 08/09/2017 at 17:35, Romain Izard wrote:
From: Romain Izard
Save and restore the System Clock and Programmable Clock
* Ingo Molnar wrote:
> 1)
>
> Note how R12 is used immediately, right in the next instruction:
>
> vpaddq (TBL), Y_0, XFER
>
> I.e. the RBP fixes lengthen the program order data dependencies - that's a
> new
> constraint and a few extra cycles per loop iteration
* Ingo Molnar wrote:
> 1)
>
> Note how R12 is used immediately, right in the next instruction:
>
> vpaddq (TBL), Y_0, XFER
>
> I.e. the RBP fixes lengthen the program order data dependencies - that's a
> new
> constraint and a few extra cycles per loop iteration if the workload is
On Wed, 13 Sep 2017, Keerthy wrote:
> When the initial support was added for this PMIC was added
> only regulator support was present. Now we have GPIO and Powerbutton
> support as well. Hence correct the description of MFD_TPS65218 config
> option.
>
> Signed-off-by: Keerthy
On Wed, 13 Sep 2017, Keerthy wrote:
> When the initial support was added for this PMIC was added
> only regulator support was present. Now we have GPIO and Powerbutton
> support as well. Hence correct the description of MFD_TPS65218 config
> option.
>
> Signed-off-by: Keerthy
> ---
>
On Wed, 13 Sep 2017, Keerthy wrote:
> Currently the driver boots only via device tree hence add a
> dependency on CONFIG_OF. This leaves with a bunch of unused code
> so clean that up.
>
> Signed-off-by: Keerthy
> ---
> drivers/mfd/Kconfig| 2 +-
> drivers/mfd/tps65218.c
On Wed, 13 Sep 2017, Keerthy wrote:
> Currently the driver boots only via device tree hence add a
> dependency on CONFIG_OF. This leaves with a bunch of unused code
> so clean that up.
>
> Signed-off-by: Keerthy
> ---
> drivers/mfd/Kconfig| 2 +-
> drivers/mfd/tps65218.c | 8
> 2
On (09/14/17 10:39), Helge Deller wrote:
[..]
> The basic concept of your proposal may work, and since it will avoid such
> coding issues in the future I think it's probably the best solution.
>
> Will you come up with a patch ? (I won't have time the next few days).
> If yes,I'd be happy to test
On (09/14/17 10:39), Helge Deller wrote:
[..]
> The basic concept of your proposal may work, and since it will avoid such
> coding issues in the future I think it's probably the best solution.
>
> Will you come up with a patch ? (I won't have time the next few days).
> If yes,I'd be happy to test
On Tue, 12 Sep 2017, Steve Twiss wrote:
> From: Steve Twiss
>
> Commit 340267640d769d3b3af9 ("MAINTAINERS: da9062/61 updates to the Dialog
> Semiconductor search terms") contained a typo for the watchdog binding:
> da92??-wdt.txt should have read da90??-wdt.txt.
On Tue, 12 Sep 2017, Steve Twiss wrote:
> From: Steve Twiss
>
> Commit 340267640d769d3b3af9 ("MAINTAINERS: da9062/61 updates to the Dialog
> Semiconductor search terms") contained a typo for the watchdog binding:
> da92??-wdt.txt should have read da90??-wdt.txt. This new commit will fix
> the
On Tue, 12 Sep 2017, Martin Kaiser wrote:
> When fsl-imx25-tsadc is compiled as a module, unloading and reloading
> the module will lead to a crash.
>
> Add a removal function which clears the irq handler and removes the irq
> domain. With this cleanup in place, it's possible to unload and
On 09/13/2017 06:17 AM, Jarkko Sakkinen wrote:
On Wed, Sep 06, 2017 at 08:56:39AM -0400, Nayna Jain wrote:
Currently, tpm_msleep() uses delay_msec as the minimum value in
usleep_range. However, that is the maximum time we want to wait.
The function is modified to use the delay_msec as the
On Tue, 12 Sep 2017, Martin Kaiser wrote:
> When fsl-imx25-tsadc is compiled as a module, unloading and reloading
> the module will lead to a crash.
>
> Add a removal function which clears the irq handler and removes the irq
> domain. With this cleanup in place, it's possible to unload and
On 09/13/2017 06:17 AM, Jarkko Sakkinen wrote:
On Wed, Sep 06, 2017 at 08:56:39AM -0400, Nayna Jain wrote:
Currently, tpm_msleep() uses delay_msec as the minimum value in
usleep_range. However, that is the maximum time we want to wait.
The function is modified to use the delay_msec as the
On Tue, 12 Sep 2017, Martin Kaiser wrote:
> Replace the two separate calls for setting the irq handler and data with
> a single irq_set_chained_handler_and_data() call.
>
> Signed-off-by: Martin Kaiser
> ---
> drivers/mfd/fsl-imx25-tsadc.c | 3 +--
> 1 file changed, 1
On Tue, 12 Sep 2017, Martin Kaiser wrote:
> Replace the two separate calls for setting the irq handler and data with
> a single irq_set_chained_handler_and_data() call.
>
> Signed-off-by: Martin Kaiser
> ---
> drivers/mfd/fsl-imx25-tsadc.c | 3 +--
> 1 file changed, 1 insertion(+), 2
14.09.2017 02:38, Ian Kent пишет:
> On 01/09/17 19:21, Stanislav Kinsburskiy wrote:
>> Signed-off-by: Stanislav Kinsburskiy
>> ---
>> fs/autofs4/autofs_i.h |3 +++
>> fs/autofs4/dev-ioctl.c |3 +++
>> fs/autofs4/inode.c |4 +++-
>> 3 files changed, 9
14.09.2017 02:38, Ian Kent пишет:
> On 01/09/17 19:21, Stanislav Kinsburskiy wrote:
>> Signed-off-by: Stanislav Kinsburskiy
>> ---
>> fs/autofs4/autofs_i.h |3 +++
>> fs/autofs4/dev-ioctl.c |3 +++
>> fs/autofs4/inode.c |4 +++-
>> 3 files changed, 9 insertions(+), 1
On Thu, Sep 14, 2017 at 06:42:03AM +, mario.limoncie...@dell.com wrote:
> > On Fri, Sep 08, 2017 at 10:23:11AM -0500, Mario Limonciello wrote:
> > > +static const struct wmi_device_id intel_wmi_thunderbolt_id_table[] = {
> > > + { .guid_string = INTEL_WMI_THUNDERBOLT_GUID },
> > > + { },
> > >
On Thu, Sep 14, 2017 at 06:42:03AM +, mario.limoncie...@dell.com wrote:
> > On Fri, Sep 08, 2017 at 10:23:11AM -0500, Mario Limonciello wrote:
> > > +static const struct wmi_device_id intel_wmi_thunderbolt_id_table[] = {
> > > + { .guid_string = INTEL_WMI_THUNDERBOLT_GUID },
> > > + { },
> > >
2017-09-14 16:36 GMT+08:00 Quan Xu :
>
>
> on 2017/9/13 19:56, Yang Zhang wrote:
>>
>> On 2017/8/29 22:56, Michael S. Tsirkin wrote:
>>>
>>> On Tue, Aug 29, 2017 at 11:46:34AM +, Yang Zhang wrote:
Some latency-intensive workload will see obviously performance
2017-09-14 16:36 GMT+08:00 Quan Xu :
>
>
> on 2017/9/13 19:56, Yang Zhang wrote:
>>
>> On 2017/8/29 22:56, Michael S. Tsirkin wrote:
>>>
>>> On Tue, Aug 29, 2017 at 11:46:34AM +, Yang Zhang wrote:
Some latency-intensive workload will see obviously performance
drop when running
On Thu, Sep 14, 2017 at 04:41:39PM +0800, Quan Xu wrote:
> > > On Tue, Aug 29, 2017 at 11:46:37AM +, Yang Zhang wrote:
> > > > Add poll in do_idle. For UP VM, if there are running task, it will not
> > > > goes into idle path, so we only enable poll in SMP VM.
> > > >
> > > > Signed-off-by:
Hi Michal,
On Thu, Sep 14, 2017 at 11:07 AM, Michal Hocko wrote:
> I've started seeing the following compilation failures with microblaze
> with the current linux-next (next-20170913). I have no idea when this
> has been introduced but microblaze clearly doesn't have arch
On Thu, Sep 14, 2017 at 04:41:39PM +0800, Quan Xu wrote:
> > > On Tue, Aug 29, 2017 at 11:46:37AM +, Yang Zhang wrote:
> > > > Add poll in do_idle. For UP VM, if there are running task, it will not
> > > > goes into idle path, so we only enable poll in SMP VM.
> > > >
> > > > Signed-off-by:
Hi Michal,
On Thu, Sep 14, 2017 at 11:07 AM, Michal Hocko wrote:
> I've started seeing the following compilation failures with microblaze
> with the current linux-next (next-20170913). I have no idea when this
> has been introduced but microblaze clearly doesn't have arch specific
> kvm_para.h.
Le 14/09/2017 à 01:51, Rob Landley a écrit :
From: Rob Landley
Make initramfs honor CONFIG_DEVTMPFS_MOUNT, and move
/dev/console open after devtmpfs mount.
Add workaround for Debian bug that was copied by Ubuntu.
Is that a bug only for Debian ? Why ?
Why should a Debian
Le 14/09/2017 à 01:51, Rob Landley a écrit :
From: Rob Landley
Make initramfs honor CONFIG_DEVTMPFS_MOUNT, and move
/dev/console open after devtmpfs mount.
Add workaround for Debian bug that was copied by Ubuntu.
Is that a bug only for Debian ? Why ?
Why should a Debian bug be fixed by a
On Wed, Sep 13, 2017 at 10:50 AM, Geert Uytterhoeven
wrote:
> On Thu, Jul 20, 2017 at 12:54 PM, Mauro Carvalho Chehab
> wrote:
>> This is an automatic generated email to let you know that the following
>> patch were queued:
>>
>> Subject: media:
On Wed, Sep 13, 2017 at 10:50 AM, Geert Uytterhoeven
wrote:
> On Thu, Jul 20, 2017 at 12:54 PM, Mauro Carvalho Chehab
> wrote:
>> This is an automatic generated email to let you know that the following
>> patch were queued:
>>
>> Subject: media: adv7180: add missing adv7180cp, adv7180st i2c
On 14/09/2017 11:11, Sergey Senozhatsky wrote:
> On (09/14/17 10:58), Laurent Dufour wrote:
> [..]
>> That's right, but here this is the sequence counter mm->mm_seq, not the
>> vm_seq one.
>
> d'oh... you are right.
So I'm doubting about the probability of a deadlock here, but I don't like
to
* Josh Poimboeuf wrote:
> I'm still looking at the other one (sha512-avx2), but so far I haven't
> found a way to speed it back up.
Here's a couple of very quick observations with possible optimizations:
AFAICS the main effect of the RBP fixes is the introduction of a
On Wed, Sep 13, 2017 at 12:14 AM, Jamie Iles wrote:
> On Tue, Sep 12, 2017 at 11:47:52AM +0200, Linus Walleij wrote:
>> Jamie, do you consider yourself maintainer? If not
>> would someone else using this driver please step up?
>
> I don't think I'm best suited to the job - I
On 14/09/2017 11:11, Sergey Senozhatsky wrote:
> On (09/14/17 10:58), Laurent Dufour wrote:
> [..]
>> That's right, but here this is the sequence counter mm->mm_seq, not the
>> vm_seq one.
>
> d'oh... you are right.
So I'm doubting about the probability of a deadlock here, but I don't like
to
* Josh Poimboeuf wrote:
> I'm still looking at the other one (sha512-avx2), but so far I haven't
> found a way to speed it back up.
Here's a couple of very quick observations with possible optimizations:
AFAICS the main effect of the RBP fixes is the introduction of a memory load
into
the
On Wed, Sep 13, 2017 at 12:14 AM, Jamie Iles wrote:
> On Tue, Sep 12, 2017 at 11:47:52AM +0200, Linus Walleij wrote:
>> Jamie, do you consider yourself maintainer? If not
>> would someone else using this driver please step up?
>
> I don't think I'm best suited to the job - I don't actually have
On (09/14/17 10:58), Laurent Dufour wrote:
[..]
> That's right, but here this is the sequence counter mm->mm_seq, not the
> vm_seq one.
d'oh... you are right.
-ss
On (09/14/17 10:58), Laurent Dufour wrote:
[..]
> That's right, but here this is the sequence counter mm->mm_seq, not the
> vm_seq one.
d'oh... you are right.
-ss
Hi Florian,
On Thu, Sep 14, 2017 at 1:28 AM, Florian Fainelli wrote:
> On 09/13/2017 10:42 AM, Geert Uytterhoeven wrote:
>> If the network interface is kept running during suspend, the net core
>> may call net_device_ops.ndo_start_xmit() while the Ethernet device is
>>
Hi Florian,
On Thu, Sep 14, 2017 at 1:28 AM, Florian Fainelli wrote:
> On 09/13/2017 10:42 AM, Geert Uytterhoeven wrote:
>> If the network interface is kept running during suspend, the net core
>> may call net_device_ops.ndo_start_xmit() while the Ethernet device is
>> still suspended, which may
Hi,
I've started seeing the following compilation failures with microblaze
with the current linux-next (next-20170913). I have no idea when this
has been introduced but microblaze clearly doesn't have arch specific
kvm_para.h.
In file included from ./include/linux/kvm_para.h:4:0,
Hi,
I've started seeing the following compilation failures with microblaze
with the current linux-next (next-20170913). I have no idea when this
has been introduced but microblaze clearly doesn't have arch specific
kvm_para.h.
In file included from ./include/linux/kvm_para.h:4:0,
On 14.09.2017 10:16, Masahiro Yamada wrote:
Hi.
2017-09-14 17:04 GMT+09:00 Oleksij Rempel :
Hi,
i assume arch/arm/boot/dts/socfpga.dtsi should be update as well. Right?
I think so.
(also arch/arm/boot/dts/socfpga_arria10.dtsi in the same way)
Hm.. according to
On 14.09.2017 10:16, Masahiro Yamada wrote:
Hi.
2017-09-14 17:04 GMT+09:00 Oleksij Rempel :
Hi,
i assume arch/arm/boot/dts/socfpga.dtsi should be update as well. Right?
I think so.
(also arch/arm/boot/dts/socfpga_arria10.dtsi in the same way)
Hm.. according to
On Wed 13-09-17 18:58:13, Jorgen S. Hansen wrote:
[...]
> The patch series look good to me.
Thanks for double checking. Ben, could you merge this to 3.16 stable
branch, please?
--
Michal Hocko
SUSE Labs
* Thomas Gleixner :
> The broken lockup_detector_suspend/resume() interface is going away. Use
> the new lockup_detector_soft_poweroff() interface to stop the watchdog from
> the busy looping power off routine.
>
> Signed-off-by: Thomas Gleixner
> Cc: Don
On Wed 13-09-17 18:58:13, Jorgen S. Hansen wrote:
[...]
> The patch series look good to me.
Thanks for double checking. Ben, could you merge this to 3.16 stable
branch, please?
--
Michal Hocko
SUSE Labs
* Thomas Gleixner :
> The broken lockup_detector_suspend/resume() interface is going away. Use
> the new lockup_detector_soft_poweroff() interface to stop the watchdog from
> the busy looping power off routine.
>
> Signed-off-by: Thomas Gleixner
> Cc: Don Zickus
> Cc: Chris Metcalf
> Cc:
On 14/09/2017 10:13, Sergey Senozhatsky wrote:
> Hi,
>
> On (09/14/17 09:55), Laurent Dufour wrote:
> [..]
>>> so if there are two CPUs, one doing write_seqcount() and the other one
>>> doing read_seqcount() then what can happen is something like this
>>>
>>> CPU0
On 14/09/2017 10:13, Sergey Senozhatsky wrote:
> Hi,
>
> On (09/14/17 09:55), Laurent Dufour wrote:
> [..]
>>> so if there are two CPUs, one doing write_seqcount() and the other one
>>> doing read_seqcount() then what can happen is something like this
>>>
>>> CPU0
At the moment, the in-kernel emulated ITS is not properly reset.
On guest restart/reset some registers keep their old values and
internal structures like device, ITE, collection lists are not emptied.
This may lead to various bugs. Among them, we can have incorrect state
backup or failure when
At the moment, the in-kernel emulated ITS is not properly reset.
On guest restart/reset some registers keep their old values and
internal structures like device, ITE, collection lists are not emptied.
This may lead to various bugs. Among them, we can have incorrect state
backup or failure when
Philipp,
On 9/14/17 00:37, Philipp Guendisch wrote:
> This patch adds a software based secure erase option to improve data
> confidentiality. The CONFIG_BLK_DEV_SECURE_ERASE option enables a mount
> flag called 'sw_secure_erase'. When you mount a volume with this flag,
> every discard call is
Philipp,
On 9/14/17 00:37, Philipp Guendisch wrote:
> This patch adds a software based secure erase option to improve data
> confidentiality. The CONFIG_BLK_DEV_SECURE_ERASE option enables a mount
> flag called 'sw_secure_erase'. When you mount a volume with this flag,
> every discard call is
on 2017/9/1 13:57, Quan Xu wrote:
on 2017/8/29 20:45, Peter Zijlstra wrote:
On Tue, Aug 29, 2017 at 11:46:37AM +, Yang Zhang wrote:
Add poll in do_idle. For UP VM, if there are running task, it will not
goes into idle path, so we only enable poll in SMP VM.
Signed-off-by: Yang Zhang
on 2017/9/1 13:57, Quan Xu wrote:
on 2017/8/29 20:45, Peter Zijlstra wrote:
On Tue, Aug 29, 2017 at 11:46:37AM +, Yang Zhang wrote:
Add poll in do_idle. For UP VM, if there are running task, it will not
goes into idle path, so we only enable poll in SMP VM.
Signed-off-by: Yang Zhang
On 14.09.2017 10:03, Sergey Senozhatsky wrote:
On (09/14/17 16:40), Sergey Senozhatsky wrote:
[..]
powerpc and parisc handle kernel .opd section as well:
arch/powerpc/kernel/vmlinux.lds.S: .opd
arch/parisc/kernel/vmlinux.lds.S: .opd
for modules, arch-s define mod_arch_specific
On 14.09.2017 10:03, Sergey Senozhatsky wrote:
On (09/14/17 16:40), Sergey Senozhatsky wrote:
[..]
powerpc and parisc handle kernel .opd section as well:
arch/powerpc/kernel/vmlinux.lds.S: .opd
arch/parisc/kernel/vmlinux.lds.S: .opd
for modules, arch-s define mod_arch_specific
on 2017/9/13 19:56, Yang Zhang wrote:
On 2017/8/29 22:56, Michael S. Tsirkin wrote:
On Tue, Aug 29, 2017 at 11:46:34AM +, Yang Zhang wrote:
Some latency-intensive workload will see obviously performance
drop when running inside VM.
But are we trading a lot of CPU for a bit of lower
on 2017/9/13 19:56, Yang Zhang wrote:
On 2017/8/29 22:56, Michael S. Tsirkin wrote:
On Tue, Aug 29, 2017 at 11:46:34AM +, Yang Zhang wrote:
Some latency-intensive workload will see obviously performance
drop when running inside VM.
But are we trading a lot of CPU for a bit of lower
On Wed 13-09-17 17:59:27, Sherry Yang wrote:
> Restore asynchronous mmput, allowing mmput_async to be called
> from an atomic context in Android binder shrinker callback.
>
> mmput_async was initially introduced in ec8d7c14e
> ("mm, oom_reaper: do not mmput synchronously from the
> oom reaper
On Wed 13-09-17 17:59:27, Sherry Yang wrote:
> Restore asynchronous mmput, allowing mmput_async to be called
> from an atomic context in Android binder shrinker callback.
>
> mmput_async was initially introduced in ec8d7c14e
> ("mm, oom_reaper: do not mmput synchronously from the
> oom reaper
On Wed, Sep 13, 2017 at 05:37:53PM +0200, Philipp Guendisch wrote:
> This patch adds a software based secure erase option to improve data
> confidentiality. The CONFIG_BLK_DEV_SECURE_ERASE option enables a mount
> flag called 'sw_secure_erase'. When you mount a volume with this flag,
> every
On Wed, Sep 13, 2017 at 05:37:53PM +0200, Philipp Guendisch wrote:
> This patch adds a software based secure erase option to improve data
> confidentiality. The CONFIG_BLK_DEV_SECURE_ERASE option enables a mount
> flag called 'sw_secure_erase'. When you mount a volume with this flag,
> every
Hi.
2017-09-14 17:04 GMT+09:00 Oleksij Rempel :
> Hi,
>
> i assume arch/arm/boot/dts/socfpga.dtsi should be update as well. Right?
I think so.
(also arch/arm/boot/dts/socfpga_arria10.dtsi in the same way)
The wrong property "dma-mask" was removed by
commit
Hi.
2017-09-14 17:04 GMT+09:00 Oleksij Rempel :
> Hi,
>
> i assume arch/arm/boot/dts/socfpga.dtsi should be update as well. Right?
I think so.
(also arch/arm/boot/dts/socfpga_arria10.dtsi in the same way)
The wrong property "dma-mask" was removed by
commit
On Thu, Sep 14, 2017 at 08:53:04AM +0800, Huang, Ying wrote:
> Hi, Andrew,
>
> Andrew Morton writes:
>
> > On Wed, 13 Sep 2017 10:40:19 +0900 Minchan Kim wrote:
> >
> >> Every zram users like low-end android device has used 0 page-cluster
> >> to
On Thu, Sep 14, 2017 at 08:53:04AM +0800, Huang, Ying wrote:
> Hi, Andrew,
>
> Andrew Morton writes:
>
> > On Wed, 13 Sep 2017 10:40:19 +0900 Minchan Kim wrote:
> >
> >> Every zram users like low-end android device has used 0 page-cluster
> >> to disable swap readahead because it has no seek
From: Steffen Trumtrar
The only way of stopping the watchdog is by resetting it.
Add the watchdog op for stopping the device and reset if
a reset line is provided.
Signed-off-by: Steffen Trumtrar
Signed-off-by: Oleksij Rempel
From: Steffen Trumtrar
The only way of stopping the watchdog is by resetting it.
Add the watchdog op for stopping the device and reset if
a reset line is provided.
Signed-off-by: Steffen Trumtrar
Signed-off-by: Oleksij Rempel
Cc: Wim Van Sebroeck
Cc: Guenter Roeck
Cc:
From: Steffen Trumtrar
Signed-off-by: Steffen Trumtrar
Signed-off-by: Oleksij Rempel
Cc: Dinh Nguyen
Cc: linux-arm-ker...@lists.infradead.org
---
arch/arm/boot/dts/socfpga.dtsi | 2
From: Steffen Trumtrar
Signed-off-by: Steffen Trumtrar
Signed-off-by: Oleksij Rempel
Cc: Dinh Nguyen
Cc: linux-arm-ker...@lists.infradead.org
---
arch/arm/boot/dts/socfpga.dtsi | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/boot/dts/socfpga.dtsi
Hi,
On (09/14/17 09:55), Laurent Dufour wrote:
[..]
> > so if there are two CPUs, one doing write_seqcount() and the other one
> > doing read_seqcount() then what can happen is something like this
> >
> > CPU0CPU1
> >
> >
Hi,
On (09/14/17 09:55), Laurent Dufour wrote:
[..]
> > so if there are two CPUs, one doing write_seqcount() and the other one
> > doing read_seqcount() then what can happen is something like this
> >
> > CPU0CPU1
> >
> >
On 13/09/17 18:20, Boris Ostrovsky wrote:
> On 09/13/2017 10:45 AM, Juergen Gross wrote:
>> On 13/09/17 15:50, Boris Ostrovsky wrote:
>>> On 09/13/2017 09:38 AM, Juergen Gross wrote:
On 13/09/17 15:22, Boris Ostrovsky wrote:
> On 09/12/2017 02:18 PM, Juergen Gross wrote:
>> On
On 13/09/17 18:20, Boris Ostrovsky wrote:
> On 09/13/2017 10:45 AM, Juergen Gross wrote:
>> On 13/09/17 15:50, Boris Ostrovsky wrote:
>>> On 09/13/2017 09:38 AM, Juergen Gross wrote:
On 13/09/17 15:22, Boris Ostrovsky wrote:
> On 09/12/2017 02:18 PM, Juergen Gross wrote:
>> On
On 09/13/2017 11:26 PM, Wolfram Sang wrote:
> Hi,
>
> thanks for this driver!
>
>> +/**
>> + * struct stm32f7_i2c_spec - private i2c specification timing
>> + * @rate: I2C bus speed (Hz)
>> + * @rate_min: 80% of I2C bus speed (Hz)
>> + * @rate_max: 120% of I2C bus speed (Hz)
>
> You would
On 09/13/2017 11:26 PM, Wolfram Sang wrote:
> Hi,
>
> thanks for this driver!
>
>> +/**
>> + * struct stm32f7_i2c_spec - private i2c specification timing
>> + * @rate: I2C bus speed (Hz)
>> + * @rate_min: 80% of I2C bus speed (Hz)
>> + * @rate_max: 120% of I2C bus speed (Hz)
>
> You would
On Wed, 13 Sep 2017, Don Zickus wrote:
>
> Aside from the simple compile issue in patch 25. I have no issues with this
> patchset. Thanks Thomas!
>
> Reviewed-by: Don Zickus
Thanks for your time and feedback!
tglx
On Wed, 13 Sep 2017, Don Zickus wrote:
>
> Aside from the simple compile issue in patch 25. I have no issues with this
> patchset. Thanks Thomas!
>
> Reviewed-by: Don Zickus
Thanks for your time and feedback!
tglx
New price, New products, New certificate, solar water heater 2017
It is our pleasure to work with you to make the business better.
We will try our best to support you on the new price,new products, new
certificate,
1. Temperature limitation heat pipe which stop working at 80 degree C,
New price, New products, New certificate, solar water heater 2017
It is our pleasure to work with you to make the business better.
We will try our best to support you on the new price,new products, new
certificate,
1. Temperature limitation heat pipe which stop working at 80 degree C,
On 09/14/17 at 03:49pm, Dave Young wrote:
> > > diff --git a/arch/x86/include/asm/uv/uv.h b/arch/x86/include/asm/uv/uv.h
> > > index b5a32231abd8..93d7ad8763ba 100644
> > > --- a/arch/x86/include/asm/uv/uv.h
> > > +++ b/arch/x86/include/asm/uv/uv.h
> > > @@ -18,6 +18,11 @@ extern void
On 09/14/17 at 03:49pm, Dave Young wrote:
> > > diff --git a/arch/x86/include/asm/uv/uv.h b/arch/x86/include/asm/uv/uv.h
> > > index b5a32231abd8..93d7ad8763ba 100644
> > > --- a/arch/x86/include/asm/uv/uv.h
> > > +++ b/arch/x86/include/asm/uv/uv.h
> > > @@ -18,6 +18,11 @@ extern void
On Monday 11 September 2017 23:25:27 Gabriel M. Elder wrote:
> Hi all,Hans de Goede, one of
> the upower maintainers, suggested I alert you all to this
> bug: href="https://bugs.freedesktop.org/show_bug.cgi?id=100041;
> mce_href="https://bugs.freedesktop.org/show_bug.cgi?id=100041;
>
On Monday 11 September 2017 23:25:27 Gabriel M. Elder wrote:
> Hi all,Hans de Goede, one of
> the upower maintainers, suggested I alert you all to this
> bug: href="https://bugs.freedesktop.org/show_bug.cgi?id=100041;
> mce_href="https://bugs.freedesktop.org/show_bug.cgi?id=100041;
>
On Mon, Jul 10, 2017 at 04:59:48PM +0200, Christian König wrote:
> Hi everyone,
>
> This is the eighth incarnation of this set of patches. It enables device
> drivers to resize and most likely also relocate the PCI BAR of devices
> they manage to allow the CPU to access all of the device local
On Mon, Jul 10, 2017 at 04:59:48PM +0200, Christian König wrote:
> Hi everyone,
>
> This is the eighth incarnation of this set of patches. It enables device
> drivers to resize and most likely also relocate the PCI BAR of devices
> they manage to allow the CPU to access all of the device local
Hi,
i assume arch/arm/boot/dts/socfpga.dtsi should be update as well. Right?
On 14.09.2017 09:17, Masahiro Yamada wrote:
This example allocates too much for register regions. Especially,
there are only two registers in the "nand_data" interface of this
hardware (ADDR: 0x00, DATA: 0x10).
Hi,
i assume arch/arm/boot/dts/socfpga.dtsi should be update as well. Right?
On 14.09.2017 09:17, Masahiro Yamada wrote:
This example allocates too much for register regions. Especially,
there are only two registers in the "nand_data" interface of this
hardware (ADDR: 0x00, DATA: 0x10).
On Wed, Sep 13, 2017 at 12:38:56PM +0200, Adam Borowski wrote:
> On Wed, Sep 13, 2017 at 04:12:46PM +0900, Minchan Kim wrote:
> > On Tue, Sep 12, 2017 at 02:00:05PM +0900, Sergey Senozhatsky wrote:
> > > ZSTD tends to outperform deflate/inflate, thus we remove
> > > zlib from the list of
On Wed, Sep 13, 2017 at 12:38:56PM +0200, Adam Borowski wrote:
> On Wed, Sep 13, 2017 at 04:12:46PM +0900, Minchan Kim wrote:
> > On Tue, Sep 12, 2017 at 02:00:05PM +0900, Sergey Senozhatsky wrote:
> > > ZSTD tends to outperform deflate/inflate, thus we remove
> > > zlib from the list of
1201 - 1300 of 1388 matches
Mail list logo