On Mon 13-06-16 22:44:10, Topi Miettinen wrote:
> Present maximum used memory in cgroup memory.current_max.
It would be really much more preferable to present the usecase in the
patch description. It is true that this information is presented in the
v1 API but the current policy is to export new k
On Mon, Jun 13, 2016 at 02:23:16PM +0100, Srinivas Kandagatla wrote:
> This patch adds module licence to lpass-cpu driver, without this
> patch lpass-cpu module would taint with below error, while insmod/modprobe.
>
> snd_soc_lpass_cpu: module license 'unspecified' taints kernel.
> Disabling lock
Hi Zhang
> > > > struct thermal_zone_device *thermal_zone_device_register()
> > > > {
> > > > ...
> > > > if (!tz->tzp || !tz->tzp->no_hwmon) {
> > > > result = thermal_add_hwmon_sysfs(tz);
> > > > ...
> > > > }
> > > > ...
> > >
On Sat 11-06-16 22:15:59, Ebru Akagunduz wrote:
> This patch takes back allocstall comparing when deciding
> whether swapin worthwhile because it does not work,
> if vmevent disabled.
>
> Related commit:
> http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=2548306628308aa6a
On Tue, Jun 7, 2016 at 8:55 AM, Tan Jui Nee wrote:
> This is to cater the need for non-ACPI system whereby
> a platform device has to be created in order to bind
> with the Apollo Lake Pinctrl GPIO platform driver.
>
> Signed-off-by: Tan Jui Nee
You forgot to put me on the To: line for the patc
> > Next time, when/if you send patch series, send patches in one thread, i.e.
> > patches should be replies to the cover letter.
> > Your patches are not linked together, which makes them harder to track.
Thanks for the tip; but doesn't this conflict with the advice in
https://www.kernel.org/doc/
On Sat 11-06-16 22:16:00, Ebru Akagunduz wrote:
> Currently, khugepaged collapses pages saying only
> a referenced page enough to create a THP.
>
> This patch changes the design from optimistic to conservative.
> It gives a default threshold which is half of HPAGE_PMD_NR
> for referenced pages, al
-product/20160614-142621
base: https://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi.git for-next
config: x86_64-allmodconfig (attached as .config)
compiler: gcc-6 (Debian 6.1.1-1) 6.1.1 20160430
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
Note: it
Hi,
[auto build test WARNING on scsi/for-next]
[also build test WARNING on v4.7-rc3 next-20160614]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Charles-Chiou/scsi-stex-c-Support-Pegasus-3
On Mon, Jun 13, 2016 at 5:02 PM, Dan Williams wrote:
> On Mon, Jun 13, 2016 at 4:59 PM, Kani, Toshimitsu wrote:
>> On Mon, 2016-06-13 at 16:18 -0700, Dan Williams wrote:
>>> Thanks Toshi!
>>>
>>> On Mon, Jun 13, 2016 at 3:21 PM, Toshi Kani wrote:
>>> >
>>> > This patch-set adds DAX support to de
Hi Joonsoo,
On Tue, Jun 14, 2016 at 8:24 AM, Joonsoo Kim wrote:
> On Mon, Jun 13, 2016 at 09:43:13PM +0200, Geert Uytterhoeven wrote:
>> On Tue, Apr 12, 2016 at 6:51 AM, wrote:
>> > From: Joonsoo Kim
>> > To check whther free objects exist or not precisely, we need to grab a
>> > lock. But, a
* Matt Fleming wrote:
> On Sun, 12 Jun, at 02:37:26PM, Lukas Wunner wrote:
> >
> > Resetting the card solves the problem at the root and fixes both,
> > the spurious interrupts and the memory corruption.
>
> It also avoids the need to figure out exactly which Boot Services
> regions may have
On 06/01/2016 10:34 AM, Daniel Lezcano wrote:
The macro OF_DECLARE_1 expect a void (*func)(struct device_node *) while the
OF_DECLARE_2 expect a int (*func)(struct device_node *, struct device_node *).
The second one allows to pass an init function returning a value, which make
possible to call
Hi Stephan,
On 14 June 2016 at 07:12, Stephan Mueller wrote:
> Am Dienstag, 14. Juni 2016, 00:16:11 schrieb Andrew Zaborowski:
>> On 8 June 2016 at 21:14, Mat Martineau
>>
>> wrote:
>> > On Wed, 8 Jun 2016, Stephan Mueller wrote:
>> >> What is your concern?
>> >
>> > Userspace must allocate larg
* WANG Chao wrote:
> unlikely() was dropped in commit ce03e41 ("sched/core: Drop unlikely
> behind BUG_ON()"), but commit 29d6455 ("sched: panic on corrupted stack
> end") dropped BUG_ON() and called panic directly.
>
> Now we should bring unlikely() back for branch prediction.
>
> Signed-off-
Hi Matthias,
On Wed, 2016-06-08 at 17:35 +0200, Matthias Brugger wrote:
>
> On 08/06/16 14:25, Horng-Shyang Liao wrote:
> > Hi Matthias,
> >
> > On Wed, 2016-06-08 at 12:45 +0200, Matthias Brugger wrote:
> >>
> >> On 08/06/16 07:40, Horng-Shyang Liao wrote:
> >>> Hi Matthias,
> >>>
> >>> On Tue,
* Ivaylo Dimitrov [160613 12:01]:
> Hi,
>
> On 13.06.2016 10:10, Tony Lindgren wrote:
> > * Ivaylo Dimitrov [160610 14:23]:
> > >
> > > On 10.06.2016 13:22, Tony Lindgren wrote:
> > > >
> > > > OK. And I just applied the related dts changes. Please repost the driver
> > > > changes and DT bind
Dear Kernel developers,
we detected a missing dependency inside the Kconfig model, which allows to
configure Memstick support for power management (MEMSTICK_UNSAFE_RESUME) even
if Power Management (PM) was disabled. We suggest to add a "depends on"
constraint to the Kconfig model for semantical
dmam_declare_coherent_memory doesn't take into account the return
value of dma_declare_coherent_memory, which leads to incorrect resource
handling
Signed-off-by: Vyacheslav V. Yurkov
---
drivers/base/dma-mapping.c | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/drivers
SUSE's regression testing noticed that...
0905f04eb21f sched/fair: Fix new task's load avg removed from source CPU in
wake_up_new_task()
...introduced a hackbench regression, and indeed it does. I think this
regression has more to do with randomness than anything else, but in
general...
While
On (06/13/16 15:49), Ganesh Mahendran wrote:
[..]
> > some parts (of the info above) are already available: zram maps to
> > pool name, which maps to a sysfs file name, that can contain the rest.
> > I'm just trying to understand what kind of optimizations we are talking
> > about here and how woul
Hi Jitao,
On Thu, Jun 2, 2016 at 5:57 PM, Jitao Shi wrote:
>
> This patch adds drm_bridge driver for parade DSI to eDP bridge chip.
>
> Signed-off-by: Jitao Shi
> Reviewed-by: Daniel Kurtz
> ---
> Changes since v15:
> - Drop drm_connector_(un)register calls from parade ps8640.
>The main DR
On Tue, Jun 14, 2016 at 09:31:23AM +0200, Geert Uytterhoeven wrote:
> Hi Joonsoo,
>
> On Tue, Jun 14, 2016 at 8:24 AM, Joonsoo Kim wrote:
> > On Mon, Jun 13, 2016 at 09:43:13PM +0200, Geert Uytterhoeven wrote:
> >> On Tue, Apr 12, 2016 at 6:51 AM, wrote:
> >> > From: Joonsoo Kim
> >> > To chec
Signed-off-by: Richard Weinberger
---
drivers/mtd/ubi/fastmap.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/mtd/ubi/fastmap.c b/drivers/mtd/ubi/fastmap.c
index 990898b..ab337e6 100644
--- a/drivers/mtd/ubi/fastmap.c
+++ b/drivers/mtd/ubi/fastmap.c
@@ -578,7 +578,7
This makes the logic more easy to follow.
Signed-off-by: Richard Weinberger
---
drivers/mtd/ubi/attach.c | 24 ++--
drivers/mtd/ubi/ubi.h| 15 +++
2 files changed, 33 insertions(+), 6 deletions(-)
diff --git a/drivers/mtd/ubi/attach.c b/drivers/mtd/ubi/attach
+Alan. (Sorry Alan, I forgot to add copy you in this series).
Hi,
On 14/06/16 05:17, Peter Chen wrote:
> On Fri, Jun 10, 2016 at 04:07:09PM +0300, Roger Quadros wrote:
>> Hi,
>>
>> This series centralizes OTG/Dual-role functionality in the kernel.
>> As of now I've got Dual-role functionality wor
...don't waste memory by allocating one sizeof(int) per
PEB.
Signed-off-by: Richard Weinberger
---
drivers/mtd/ubi/fastmap.c | 20 +++-
1 file changed, 11 insertions(+), 9 deletions(-)
diff --git a/drivers/mtd/ubi/fastmap.c b/drivers/mtd/ubi/fastmap.c
index b66cb3e..48eb55f 1006
This helps to detect cases where an user copies an UBI image to
another target with different bad blocks.
Signed-off-by: Richard Weinberger
---
drivers/mtd/ubi/fastmap.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/drivers/mtd/ubi/fastmap.c b/drivers/mtd/ubi/fastmap.c
index 12bdb09
Signed-off-by: Richard Weinberger
---
drivers/mtd/ubi/attach.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/mtd/ubi/attach.c b/drivers/mtd/ubi/attach.c
index c1aaf03..cc04ca8 100644
--- a/drivers/mtd/ubi/attach.c
+++ b/drivers/mtd/ubi/attach.c
@@ -1326,7 +1326,7 @@
Introduce a new list to the UBI attach information
object to be able to deal better with old and corrupted
Fastmap eraseblocks.
Also move more Fastmap specific code into fastmap.c.
Signed-off-by: Richard Weinberger
---
drivers/mtd/ubi/attach.c | 99 +-
Since PEB erasure is asynchornous it can happen that there is
more than one Fastmap on the MTD. This is fine because the attach logic
will pick the Fastmap data structure with the highest sequence number.
On a not so well configured MTD stack spurious ECC errors are common.
Causes can be different
Hi Jon,
On Fri, Jun 10, 2016 at 10:41 PM, Dave Airlie wrote:
> On 11 June 2016 at 04:17, Daniel Vetter wrote:
>> On Thu, Jun 9, 2016 at 9:55 PM, Jonathan Corbet wrote:
>>> On Sat, 4 Jun 2016 14:37:01 +0300
>>> Jani Nikula wrote:
>>>
When this lands in docs-next and we can backmerge to dr
Nice cleanup!
I think I see a buglet in your level-5 cascading.
Suppose a timer is requested far in the future for a time
that is an exact multiple of 32768 jiffies.
collect_expired_timers() scans level 5 after all the previous ones,
and will cascade it to level 0, in a level-0 bucket which has
+Alan,
On 10/06/16 16:07, Roger Quadros wrote:
> When using the OTG/DRD library we can call hcd_add/remove
> consecutively without calling usb_put_hcd/usb_create_hcd in between
> so hcd->flags can be stale.
>
> If the HC dies due to whatever reason then without this
> patch we get the below error
On Tue, Jun 14, 2016 at 02:43:06PM +0800, WANG Chao wrote:
> unlikely() was dropped in commit ce03e41 ("sched/core: Drop unlikely
> behind BUG_ON()"), but commit 29d6455 ("sched: panic on corrupted stack
> end") dropped BUG_ON() and called panic directly.
Please use git config core.abbrev=12 and t
+Alan
On 10/06/16 16:07, Roger Quadros wrote:
> The OTG core will use struct otg_hcd_ops to interface
> with the HCD (Host Controller Driver).
>
> The main purpose of this interface is to avoid directly
> calling HCD APIs from the OTG core as they
> wouldn't be defined in the built-in symbol tabl
+Alan
On 10/06/16 16:07, Roger Quadros wrote:
> Introduce usb_otg_add/remove_hcd() for use by host
> controllers that are part of OTG/dual-role port.
>
> Non device tree platforms can use the otg_dev argument
> to specify the OTG controller device. If otg_dev is NULL
> then the device tree node's
Hi Vinod,
Thanks for the review...
>
> On Wed, Jun 08, 2016 at 07:40:52AM +, Appana Durga Kedareswara Rao
> wrote:
> > > > +static void zynqmp_dma_desc_config_eod(struct zynqmp_dma_chan
> > > > +*chan, void *desc)
> > >
> > > eod? 80 line?
>
> What's eod?
End of descriptor...
>
>
On Thu, Jun 09, 2016 at 10:11:51PM +0200, Wolfram Sang wrote:
> On Wed, Jun 08, 2016 at 08:51:18AM +0200, Jan Glauber wrote:
> > The controller specification states that when receiving STAT_RXADDR_NAK
> > the START should be sent again. Retry several times before finally
> > failing with -ENXIO.
>
Mathias,
On 10/06/16 16:07, Roger Quadros wrote:
> Host controllers that are part of an OTG/dual-role instance
> need to somehow pass the OTG controller device information
> to the HCD core.
>
> We use platform data to pass the OTG controller device.
>
> Signed-off-by: Roger Quadros
> Reviewed-
unlikely() was dropped in commit ce03e4137bb2 ("sched/core: Drop
unlikely behind BUG_ON()"), but commit 29d6455178a0 ("sched: panic on
corrupted stack end") dropped BUG_ON() and called panic directly.
Now we should bring unlikely() back for branch prediction. While we're
at it, it's better and cle
On 2016/6/13 21:32, Andrew Lunn wrote:
> On Mon, Jun 13, 2016 at 02:07:54PM +0800, Dongpo Li wrote:
>> This patch adds a separate driver for the MDIO interface of the
>> Hisilicon Fast Ethernet MAC.
>>
>> Reviewed-by: Jiancheng Xue
>> Signed-off-by: Dongpo Li
>> ---
>> .../bindings/net/hisilic
On Mon, Jun 13, 2016 at 11:11:05PM -0700, Linus Torvalds wrote:
> On Mon, Jun 13, 2016 at 5:52 AM, Kirill A. Shutemov
> wrote:
> > On Sat, Jun 11, 2016 at 06:02:57PM -0700, Linus Torvalds wrote:
> >>
> >> I've timed it at over a thousand cycles on at least some CPU's, but
> >> that's still peanuts
On Fri, Jun 10, 2016 at 04:32:26PM -0500, Christoph Lameter wrote:
> One reason for SLUBs creation was the 2 second scans in SLAB which causes
> significant disruption of latency sensitive tasksk.
That's not good, indeed.
>
> You can simply implement a reaper in userspace by running
>
> slabin
Move dma channel allocations to pcmops open and close functions. Reason
to do this is that, lpass_platform_pcm_free() accesses snd_soc_pcm_runtime
via substream->private data, However By this time runtimes are already
freed as part of soc_cleanup_card_resources() sequence.
This patch moves the cha
This patch adds module licence to lpass-cpu driver, without this
patch lpass-cpu module would taint with below error:
snd_soc_lpass_cpu: module license 'unspecified' taints kernel.
Disabling lock debugging due to kernel taint
snd_soc_lpass_cpu: Unknown symbol regmap_write (err 0)
snd_soc_lpass_cpu
From: Charles
Pegasus series is a RAID support product by using Thunderbolt technology.
The newest product, Pegasus 3 is support Thunderbolt 3 technology with another
chip.
1.Change driver version.
2.Add Pegasus 3 VID, DID and define it's device address.
3.Pegasus 3 use msi interrupt, so ste
From: Charles
1.Add reboot notifier and register it in stex_probe for all supported device.
2.For all supported device in restart flow, we get a callback from notifier and
set S6flag for stex_shutdown & stex_hba_stop to send restart command to FW.
Signed-off-by: Charles
Signed-off-by: Paul
-
On Mon, Jun 13, 2016 at 08:56:44AM -0700, John Fastabend wrote:
> On 16-06-13 04:47 AM, Richard Cochran wrote:
> > [...]
> > Here is what is missing to support audio TSN:
> >
> > * User Space
> >
> > 1. A proper userland stack for AVDECC, MAAP, FQTSS, and so on. The
> >OpenAVB project does n
On 13 June 2016 20:33, Frank Rowand wrote:
> > DT node names are case insensitive. The of.h header does provide a helper
> > macro
> > which is equivalent to this, but that macro is part of the '#ifdef
> > CONFIG_OF'
> > block. If I were to use it then it would cause non-DT builds to fail. I
>
Faultaround changes cause regression in unixbench, let's revert them.
Kirill A. Shutemov (2):
Revert "mm: make faultaround produce old ptes"
Revert "mm: disable fault around on emulated access bit architecture"
include/linux/mm.h | 2 +-
mm/filemap.c | 2 +-
mm/memory.c| 31 +
Replace the in order struct initialisation style with explicit field
style.
The Coccinelle semantic patch used to make this change is as follows:
@decl@
identifier i1,fld;
type T;
field list[n] fs;
@@
struct i1 {
fs
T fld;
...};
@@
identifier decl.i1,i2,decl.fld;
expression e;
position bad.p
This reverts commit d0834a6c2c5b0c76cfb806bd7dba6556d8b4edbb.
After revert of 5c0a85fad949 ("mm: make faultaround produce old ptes")
faultaround doesn't have dependencies on hardware accessed bit, so let's
revert this one too.
Signed-off-by: Kirill A. Shutemov
---
mm/memory.c | 8
1 fi
This reverts commit 5c0a85fad949212b3e059692deecdeed74ae7ec7.
The commit causes ~6% regression in unixbench.
Let's revert it for now and consider other solution for reclaim problem
later.
Signed-off-by: Kirill A. Shutemov
Reported-by: "Huang, Ying"
---
include/linux/mm.h | 2 +-
mm/filemap.c
Hi,
On Mon, May 30, 2016 at 09:02:54PM +0200, Marc Haber wrote:
> on my Bananapis, in kernel 4.6 USB does not work. Kernel configuration
> is USB-wise identical to 4.5 (grepped for differences in (hci|usb)),
> and in 4.6 there is not even /dev/bus/usb.
This turned out to be a configuration issue.
On Wed, Jun 8, 2016 at 6:13 AM, Hans Verkuil wrote:
>
>
> On 06/07/2016 11:22 PM, Mauro Carvalho Chehab wrote:
>>
>> Em Mon, 30 May 2016 20:29:14 +0800
>> Tiffany Lin escreveu:
>>
>>> ==
>>> Introduction
>>> ==
>>>
>>> The purpose of this series is to add the driver for
On 06/14/2016 06:51 AM, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the kvms390 tree got a conflict in:
>
> arch/s390/hypfs/hypfs_diag.c
>
> between commit:
>
> 6c22c9863760 ("s390: avoid extable collisions")
>
> from the s390 tree and commit:
>
> e65f30e0cb29 ("s3
From: Chuanxiao Dong
When the enhanced area feature was not enabled, the related sysfs will
have -EINVAL(-22) value, so change the sysfs output format to display
the correct value.
Signed-off-by: Chuanxiao Dong
---
drivers/mmc/core/mmc.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletion
On some platforms, root port doesn't support MSI/MSI-X/INTx in RC mode.
When chip support the aer interrupt with none MSI/MSI-X/INTx mode,
maybe there is interrupt line for aer pme etc. Search the interrupt
number in the fdt file. Then fixup the dev->irq with it.
Signed-off-by: Po Liu
---
changes
NXP some platforms aer interrupt was not MSI/MSI-X/INTx
but using interrupt line independently. This patch add a "aer"
interrupt-names for aer interrupt.
Signed-off-by: Po Liu
---
changes for v3:
- None;
.../devicetree/bindings/pci/layerscape-pci.txt | 4 ++--
arch/arm/boot/dts
On Tue, 14 Jun 2016, George Spelvin wrote:
> I think I see a buglet in your level-5 cascading.
>
> Suppose a timer is requested far in the future for a time
> that is an exact multiple of 32768 jiffies.
>
> collect_expired_timers() scans level 5 after all the previous ones,
> and will cascade it
Hi,
On Thursday 02 June 2016 13:24:57 Pranay Kr. Srivastava wrote:
> spinlocked ranges should be small and not contain calls into huge
> subfunctions. Fix my mistake and just get the pointer to the socket
> instead of doing everything with spinlock held.
>
> Reported-by: Mikulas Patocka
> Signed
* WANG Chao wrote:
> unlikely() was dropped in commit ce03e4137bb2 ("sched/core: Drop
> unlikely behind BUG_ON()"), but commit 29d6455178a0 ("sched: panic on
> corrupted stack end") dropped BUG_ON() and called panic directly.
>
> Now we should bring unlikely() back for branch prediction. While
On Tue, Jun 14, 2016 at 11:11:36AM +0800, Wei Chen wrote:
> On 13 June 2016 at 20:45, Will Deacon wrote:
> > On Mon, Jun 13, 2016 at 05:20:17PM +0800, Wei Chen wrote:
> >> The PCIe ACS capability will affect the layout of iommu groups.
> >> Generally speaking, if the path from root port to the PCI
On Mon, Jun 13, 2016 at 10:00:45AM -0700, Doug Anderson wrote:
> Yakir,
>
> On Sat, Jun 11, 2016 at 7:56 PM, Yakir Yang wrote:
> > The Samsung LSN122DL01-C01 is an 12.2" 2560x1600 (WQXGA) TFT-LCD panel
> > connected using eDP interfaces.
> >
> > Signed-off-by: Yakir Yang
> > ---
> > Changes in v
On Wed, Jun 08, 2016 at 11:58:11AM +0300, Kirill A. Shutemov wrote:
> On Wed, Jun 08, 2016 at 04:41:37PM +0800, Huang, Ying wrote:
> > "Huang, Ying" writes:
> >
> > > "Kirill A. Shutemov" writes:
> > >
> > >> On Mon, Jun 06, 2016 at 10:27:24AM +0800, kernel test robot wrote:
> > >>>
> > >>> FYI
On 14/06/16 06:53, Ravishankar Karkala Mallikarjunayya wrote:
This Replace all occurences of (1<
---
Changes V1 -> V2:
- BIT macros added(suggested by Ian Abbott)
-i.e.DMM32AT_AI_CFG_SCINT(x), DMM32AT_CTRL_PAGE(x)
---
drivers/staging/comedi/drivers/dmm32at.c | 98 +++
On Thursday 02 June 2016 13:25:00 Pranay Kr. Srivastava wrote:
> When a timeout occurs or a recv fails, then
> instead of abruplty killing nbd block device
> wait for it's users to finish.
>
> This is more required when filesystem(s) like
> ext2 or ext3 don't expect their buffer heads to
> disappe
Updated struct alarm and struct alarm_timer descriptions.
Signed-off-by: Pratyush Patel
---
include/linux/alarmtimer.h | 6 +++---
kernel/time/alarmtimer.c | 1 -
2 files changed, 3 insertions(+), 4 deletions(-)
diff --git a/include/linux/alarmtimer.h b/include/linux/alarmtimer.h
index 52f3b7
On Mon, Jun 13, 2016 at 10:51 PM, Dongdong Liu wrote:
> Hi Duc
>
> 在 2016/6/14 4:57, Duc Dang 写道:
>>
>> On Mon, Jun 13, 2016 at 8:47 AM, Christopher Covington
>> wrote:
>>>
>>> Hi Dongdong,
>>>
>>> On 06/13/2016 09:02 AM, Dongdong Liu wrote:
diff --git a/drivers/acpi/pci_mcfg.c b/driver
Hi Arnd,
Sorry for late response. Please see comments inline.
On 02.06.2016 17:19, Arnd Bergmann wrote:
On Thursday, June 2, 2016 3:35:34 PM CEST Tomasz Nowicki wrote:
On 02.06.2016 14:32, Arnd Bergmann wrote:
On Thursday, June 2, 2016 2:07:43 PM CEST Tomasz Nowicki wrote:
On 02.06.2016 13:4
Boris Brezillon wrote:
> On 12 Jun 2016 16:24:53 George Spelvin wrote:
>> Boris Brezillon wrote:
>> My problem is that I don't really understand MLC programming.
> I came to the same conclusion: we really have these 2 cases in the
> wild, which makes it even more complicated to define a standard
>
Hi,
[auto build test ERROR on tip/sched/core]
[also build test ERROR on v4.7-rc3 next-20160614]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/WANG-Chao/sched-unlikely-corrupted-stack-end
Hi,
I've got only nitpicks for the changelog. Otherwise the patch looks good
to me (and yes, without it bw inheritance would be a problem).
On 07/06/16 21:56, Peter Zijlstra wrote:
> From: Xunlei Pang
>
> We should deboost before waking the high-prio task, such that
> we don't run two tasks wit
On 2016年06月14日 12:00, Huang, Tao wrote:
Hi Daniel:
On 2016年06月13日 21:06, Daniel Lezcano wrote:
On Tue, Jun 07, 2016 at 12:54:29PM +0800, Caesar Wang wrote:
This series patches had been tested on rockchip inside kernel.
In order to support the rk3399 SoC timer and turn off interrupts and IPIs t
The continuous PWM voltage regulator is caching the voltage value in
the ->volt_uV field. While most of the time this value should reflect the
real voltage, sometime it can be sightly different if the PWM device
rounded the set_duty_cycle request.
Moreover, this value is not valid until someone has
On Mon, Jun 13, 2016 at 03:41:54PM -0600, Al Stone wrote:
> This is a resend only: Ping? Last ping was 26 May; there has been zero
> response since then. Already have one ACK from Lorenzo; another from an
> arm64 maintainer would be really helpful.
I thought there were outstanding comments on v4
Document the pwm-dutycycle-unit and pwm-dutycycle-range properties.
Signed-off-by: Boris Brezillon
Acked-by: Brian Norris
---
.../devicetree/bindings/regulator/pwm-regulator.txt | 19 +++
1 file changed, 19 insertions(+)
diff --git a/Documentation/devicetree/bindings/regulato
The continuous mode allows one to declare a PWM regulator without having
to declare the voltage <-> dutycycle association table. It works fine as
long as your voltage(dutycycle) function is linear, but also has the
following constraints:
- dutycycle for min_uV = 0%
- dutycycle for max_uV = 100%
-
On Mon, Jun 13, 2016 at 10:44 PM, Topi Miettinen wrote:
> Present current cputimer status in /proc/self/limits.
> --- a/fs/proc/base.c
> +++ b/fs/proc/base.c
> @@ -650,8 +650,30 @@ static int proc_pid_limits(struct seq_file *m, struct
> pid_namespace *ns,
> + switch (i) {
> +
Implement ->get_state() to provide support for initial state retrieval.
Signed-off-by: Boris Brezillon
---
drivers/pwm/pwm-sti.c | 38 ++
1 file changed, 38 insertions(+)
diff --git a/drivers/pwm/pwm-sti.c b/drivers/pwm/pwm-sti.c
index 92abbd5..6300d3e 100644
The ->state field is currently initialized to 0, thus referencing the
voltage selector at index 0, which might not reflect the current
voltage value.
If possible, retrieve the current voltage selector from the PWM state,
else return -EINVAL.
Signed-off-by: Boris Brezillon
Tested-by: Brian Norris
Use the atomic API wherever appropriate and get rid of pwm_apply_args()
call (the reference period and polarity are now explicitly set when
calling pwm_apply_state()).
We also make use of the pwm_set_relative_duty_cycle() helper to ease
relative to absolute duty_cycle conversion.
Note that change
The current logic will disable the PWM clk even if a PWM was left
enabled by the bootloader (because it's controlling a critical device
like a regulator for example).
Keep the PWM clk enabled if at least one PWM is enabled to avoid any
glitches.
Signed-off-by: Boris Brezillon
---
drivers/pwm/pwm
The PWM attached to a PWM regulator device might have been previously
configured by the bootloader.
Make sure the bootloader and linux config are in sync, and adjust the PWM
config if that's not the case.
Signed-off-by: Boris Brezillon
Acked-by: Mark Brown
Acked-by: Brian Norris
Tested-by: Bria
The current logic will disable the PWM clk even if the PWM was left
enabled by the bootloader (because it's controlling a critical device
like a regulator for example).
Keep the PWM clk enabled if the PWM is enabled to avoid any glitches.
Signed-off-by: Boris Brezillon
Reviewed-by: Brian Norris
The pwm_init_state() helper prepares a new state object containing the
current PWM state except for the polarity and period fields which are
set to the reference values (those in pwm_args).
This is particularly useful for PWM users who want to apply a new
duty-cycle expressed relatively to the refe
Implement the ->apply() function to add support for atomic update.
Signed-off-by: Boris Brezillon
Tested-by: Heiko Stuebner
Reviewed-by: Brian Norris
Tested-by: Brian Norris
---
drivers/pwm/pwm-rockchip.c | 84 --
1 file changed, 43 insertions(+), 4
Hello,
This patch series series aims at adding two important features to the
pwm-regulator driver.
The first one is the support for 'smooth handover' between the
bootloader and the kernel. This is mainly solving problems we have when
the PWM is controlling a critical regulator (like the one power
Implement the ->get_state() function to expose initial state.
Signed-off-by: Boris Brezillon
Reviewed-by: Brian Norris
Tested-by: Brian Norris
Tested-by: Heiko Stuebner
---
drivers/pwm/pwm-rockchip.c | 67 ++
1 file changed, 67 insertions(+)
diff -
The PWM framework expects PWM users to configure the duty cycle in
nanoseconds, but most users just want to express this duty cycle
relatively to the period value (i.e. duty_cycle = 33% of the period).
Add the pwm_{get,set}_relative_duty_cycle() helpers to ease this kind
of conversion.
Signed-off-
The current implementation always round down the duty and period
values, while it would be better to round them to the closest integer.
These changes are needed in preparation of atomic update support to
prevent a period/duty cycle drift when executing several time the
'pwm_get_state() / modify /
From: z00281421
more mapcount page as kpage could reduce total replacement
times than fewer mapcount one when ksmd scan and replace
among forked pages later.
Signed-off-by: z00281421
---
mm/ksm.c | 15 +++
1 file changed, 15 insertions(+)
diff --git a/mm/ksm.c b/mm/ksm.c
index
On Tue, Jun 14, 2016 at 10:13:31AM +0100, Will Deacon wrote:
> On Mon, Jun 13, 2016 at 03:41:54PM -0600, Al Stone wrote:
> > This is a resend only: Ping? Last ping was 26 May; there has been zero
> > response since then. Already have one ACK from Lorenzo; another from an
> > arm64 maintainer woul
On Mon, Jun 13, 2016 at 09:32:10PM +0200, Richard Cochran wrote:
> On Mon, Jun 13, 2016 at 03:00:59PM +0200, Henrik Austad wrote:
> > On Mon, Jun 13, 2016 at 01:47:13PM +0200, Richard Cochran wrote:
> > > Which driver is that?
> >
> > drivers/net/ethernet/renesas/
>
> That driver is merely a PTP
On Mon, Jun 13, 2016 at 01:01:35PM -0700, Duc Dang wrote:
> On Mon, Jun 13, 2016 at 3:40 AM, Lorenzo Pieralisi
> wrote:
> >
> > On Fri, Jun 10, 2016 at 06:36:12PM -0500, Bjorn Helgaas wrote:
> > > On Fri, Jun 10, 2016 at 09:55:17PM +0200, Tomasz Nowicki wrote:
> > > > To enable PCI legacy IRQs on
Hi Markus,
On Tue, Jun 14, 2016 at 2:29 PM, Markus Pargmann wrote:
>
> On Thursday 02 June 2016 13:25:00 Pranay Kr. Srivastava wrote:
> > When a timeout occurs or a recv fails, then
> > instead of abruplty killing nbd block device
> > wait for it's users to finish.
> >
> > This is more required w
On 14 Jun 2016 05:07:26 -0400
"George Spelvin" wrote:
> Boris Brezillon wrote:
> > On 12 Jun 2016 16:24:53 George Spelvin wrote:
> >> Boris Brezillon wrote:
> >> My problem is that I don't really understand MLC programming.
>
> > I came to the same conclusion: we really have these 2 cases in
On Mon, Jan 25, 2016 at 10:57:48PM +0530, Amitoj Kaur Chawla wrote:
> for_each_child_of_node performs an of_node_get on each iteration, so
> to break out of the loop an of_node_put is required.
>
> Found using Coccinelle. The semantic patch used for this is as follows:
>
> //
> @@
> expression e
On Fri, Oct 09, 2015 at 07:47:40PM +0200, Julia Lawall wrote:
> for_each_child_of_node performs an of_node_put on each iteration, so
> putting an of_node_put before a continue results in a double put.
>
> The semantic match that finds this problem is as follows
> (http://coccinelle.lip6.fr):
>
>
1 - 100 of 1085 matches
Mail list logo
