Signed-off-by: Grzegorz Jaszczyk
---
arch/arm/configs/mvebu_v7_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/configs/mvebu_v7_defconfig
b/arch/arm/configs/mvebu_v7_defconfig
index f1a0e25..000a866 100644
--- a/arch/arm/configs/mvebu_v7_defconfig
+++ b/arch/arm/configs/mv
This commit enables:
- CA9's Performance Monitor Unit
- CA9 MPcore SoC Controller
- Coherency fabric
on Armada 39x, basing on the Armada 38x (which has the same CA9 CPU).
Signed-off-by: Grzegorz Jaszczyk
Reviewed-by: Lior Amsalem
---
arch/arm/boot/dts/armada-39x.dtsi | 15 +++
1 fil
On Thu, Jul 21, 2016 at 02:43:59PM +0200, Grzegorz Jaszczyk wrote:
> Signed-off-by: Grzegorz Jaszczyk
Why? It's not like this is an on-soc device, but most likely a PCIe card.
Should we build-in all PCIe drivers?
I think it makes more sense to have this as a module rather than built-in.
--
RM
This commit enables:
- CA9's Performance Monitor Unit
- CA9 MPcore SoC Controller
- Coherency fabric
on Armada 39x, basing on the Armada 38x (which has the same CA9 CPU).
Signed-off-by: Grzegorz Jaszczyk
Reviewed-by: Lior Amsalem
---
arch/arm/boot/dts/armada-39x.dtsi | 15 +++
1 fil
The armada-390.dtsi was broken since the first patch which adds Device Tree
files for Armada 39x SoC was introduced.
Signed-off-by: Grzegorz Jaszczyk
Cc: # 4.0+
Fixes 538da83 ("ARM: mvebu: add Device Tree files for Armada 39x SoC and board")
---
arch/arm/boot/dts/armada-390.dtsi | 3 +++
1 file
Hi Dave + list,
I've started doing some trinity fuzzing and I'm seeing quite a few hung
tasks ("blocked for more than 120 seconds").
It started with unshare()/net_mutex which I found a few others running
into as well:
http://www.spinics.net/lists/trinity/msg00724.html
http://www.spinics.net/lis
UBIFS is commonly used on Marvell EBU v7 platforms to store the root
file-system, so it makes sense to have those options enabled by default
in mvebu_v7_defconfig.
Signed-off-by: Grzegorz Jaszczyk
---
arch/arm/configs/mvebu_v7_defconfig | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/
Signed-off-by: Grzegorz Jaszczyk
---
arch/arm/configs/mvebu_v7_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/configs/mvebu_v7_defconfig
b/arch/arm/configs/mvebu_v7_defconfig
index 486a4ca..f43a7aa 100644
--- a/arch/arm/configs/mvebu_v7_defconfig
+++ b/arch/arm/configs/mv
Hello,
On Thu, 21 Jul 2016 13:44:09 +0100, Russell King - ARM Linux wrote:
> On Thu, Jul 21, 2016 at 02:43:59PM +0200, Grzegorz Jaszczyk wrote:
> > Signed-off-by: Grzegorz Jaszczyk
>
> Why? It's not like this is an on-soc device, but most likely a PCIe card.
> Should we build-in all PCIe driv
I see that linux-4.1.y is still at 5880876e9469 which has the serious
bug introduced by the backport c5ad33184354 "mm/swap.c: flush lru
pvecs on compound page arrival".
The analogous problem is also still affecting at least linux-3.18.y.
Is there some problem with reverting this patch in the stab
> I think the original code was fine.
I suggest to reconsider involved implementation details once more.
> x = blah(); if (x) ... is a perfectly familiar kernel coding pattern.
I can agree to such a general information.
> There is no benefit in terms of performance
It might be possible that
On Thursday, July 21, 2016 2:52:24 PM CEST Daniel Lezcano wrote:
> On Tue, Jul 12, 2016 at 10:28:35AM +0200, Arnd Bergmann wrote:
>
> [ ... ]
>
> > > > Also the init function has changed its return type in linux-next:
> > > >
> > > >> +static void __init nuc970_timer_of_init(struct device_node *n
pmbus/dps400: disable PMBus status check through platform data structure to
provide support for PSU DPS-460, DPS-800 from Delta Electronics, INC and for
SGD009 from Acbel Polytech, INC.
These devices do not support the STATUS_CML register, and reports communication
error in response to this command
On Tue, Jul 12, 2016 at 10:28:35AM +0200, Arnd Bergmann wrote:
[ ... ]
> > > Also the init function has changed its return type in linux-next:
> > >
> > >> +static void __init nuc970_timer_of_init(struct device_node *node)
> > >
> > > This now needs to return an error code or we get:
> > >
> > >
On Thu, 21 Jul 2016, SF Markus Elfring wrote:
> > I think the original code was fine.
>
> I suggest to reconsider involved implementation details once more.
>
>
> > x = blah(); if (x) ... is a perfectly familiar kernel coding pattern.
>
> I can agree to such a general information.
>
>
> > There
On 04/15/2011, 10:08 AM, Petr Písař wrote:
> Traditional \E[2J sequence erases console display but scroll-back
> buffer and underlying device (frame) buffer keep data that can be
> accessed by scrolling console back.
>
> This patch introduce new \E[J parameter 3 that allows to scramble
> scroll-ba
On Thu, 2016-07-21 at 11:40 +0100, Mark Brown wrote:
> On Thu, Jul 21, 2016 at 02:27:02PM +0800, Andy Green wrote:
> >
> > On July 21, 2016 1:22:02 PM GMT+08:00, John Stultz > aro.org> wrote:
> > >
> > > On Wed, Jul 20, 2016 at 9:26 PM, zhangfei > > g>
>
> Please fix your mail client to word w
Em Thu, Jul 21, 2016 at 09:29:50AM +1000, Stephen Rothwell escreveu:
> Hi Arnaldo,
>
> On Tue, 19 Jul 2016 23:52:02 -0300 Arnaldo Carvalho de Melo
> wrote:
> >
> > Humm, it seems that the compiler used is not the cross one, but the
> > native, check if, say, __powerpc__ is defined.
>
> Yes, __p
On Fri, 15 Jul, at 10:41:31AM, Christ, Austin wrote:
> According to UEFI 2.6 section 7.5.3, the capsule should be in contiguous
> virtual memory and firmware may consume the capsule immediately. To
> correctly implement this functionality, the kernel driver needs to vmap
> the entire capsule at the
On Tuesday, July 19, 2016 01:49:57 PM Paolo Bonzini wrote:
> People complain about the driver saying there's no valid RAPL domains
> in a VM, and doing so at KERN_ERR severity. Downgrade this to KERN_INFO
> if running on a hypervisor, since it is basically stating the obvious.
>
> Suggested-by: P
According to page 16 of Sharp LQ123P1JX31 datasheet, we need to add the
missing delay timing. Panel prepare time should be t1 (0.5ms~10ms) plus
t3 (0ms~100ms), and panel enable time should equal to t7 (0ms~50ms), and
panel unprepare time should be t11 (1ms~50ms) plus t12 (500ms~).
Signed-off-by: Y
Hi all,
On Sat, Aug 08, 2015 at 09:41:51PM +0200, Olliver Schinagl wrote:
> Alexandru sent this patch over a year and a half ago, and I believe several
> tree's have been carrying it since. We've been using this patch on an
> Olimex OLinuxIno Lime1 and Lime2 using the mmc-spi driver to access SD
Add support for cdn DP controller which is embedded in the rk3399
SoCs. The DP is compliant with DisplayPort Specification,
Version 1.3, This IP is compatible with the rockchip type-c PHY IP.
There is a uCPU in DP controller, it need a firmware to work,
please put the firmware file to /lib/firmware
Some panels (like Sharp LQ123P1JX31) need to be turn off when eDP
controller stop to send valid video signal, otherwhise panel would
go burn in, and keep flicker and flicker.
So it's better to turn off the panel when eDP need to disable, and
we need to turn on the panel in connector->detect() call
Add EXTCON_DISP_DP for the Display external connector. For Type-C
connector the DisplayPort can work as an Alternate Mode(VESA DisplayPort
Alt Mode on USB Type-C Standard). The Type-C support both normal and
flipped orientation, so add a property to extcon.
Signe-off-by: Chris Zhong
Signed-off-b
There are 2 Type-C phy on RK3399, they are almost same, except the
address of register. They support USB3.0 Type-C and DisplayPort1.3
Alt Mode on USB Type-C. Register a phy, supply it to USB3 controller
and DP controller.
Signed-off-by: Chris Zhong
---
Changes in v6: None
Changes in v5: None
Cha
This patch adds a binding that describes the cdn DP controller for
rk3399.
Signed-off-by: Chris Zhong
Acked-by: Rob Herring
---
Changes in v6:
- add assigned-clocks and assigned-clock-rates
- add power-domains
Changes in v5: None
Changes in v4:
- add a reset node
- support 2 phys
Changes in
This patch adds a binding that describes the Rockchip USB Type-C PHY
for rk3399
Signed-off-by: Chris Zhong
Reviewed-by: Tomasz Figa
Reviewed-by: Kever Yang
Acked-by: Rob Herring
---
Changes in v6:
- add assigned-clocks and assigned-clock-rates
Changes in v5: None
Changes in v4:
- add a #phy
Hi all
This series patch is for rockchip Type-C phy and DisplayPort controller
driver.
The USB Type-C PHY is designed to support the USB3 and DP applications.
The PHY basically has two main components: USB3 and DisplyPort. USB3
operates in SuperSpeed mode and the DP can operate at RBR, HBR and H
On Thu, Jul 21, 2016 at 02:43:34PM +0200, Vegard Nossum wrote:
> The rules for net_mutex are very simple, it's used in very few places so
> I don't see how the locking could get messed up there. I'll buy your
> theory that the lock is held for a long time if there are a lot of
> namespaces to
Add a PHY provider driver for the rk3399 SoC Type-c PHY. The USB
Type-C PHY is designed to support the USB3 and DP applications. The
PHY basically has two main components: USB3 and DisplyPort. USB3
operates in SuperSpeed mode and the DP can operate at RBR, HBR and
HBR2 data rates.
Signed-off-by: C
On Tuesday, July 19, 2016 08:36:44 AM Chen Yu wrote:
> test_resume mode is to verify if the snapshot data
> written to swap device can be successfully restored
> to memory. It is useful to ease the debugging process
> on hibernation, since this mode can not only bypass
> the BIOSes/bootloader, but
GPIO control register is divided into IOPINS1 and IOPINS2.
And low 4-bit of register is controls output.
So, this patch fixes wrong mask of GPIO output.
Signed-off-by: Jaewon Kim
---
drivers/usb/host/max3421-hcd.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/usb/h
On Wednesday, July 20, 2016 02:18:00 AM fu@linaro.org wrote:
> From: Fu Wei
>
> This patch adds support for parsing arch timer in GTDT,
> provides some kernel APIs to parse all the PPIs and
> always-on info in GTDT and export them.
>
> By this driver, we can simplify arm_arch_timer drivers,
Hi,
On Tuesday 10 May 2016 05:09 AM, David Lechner wrote:
> We will be using a generic syscon device for the TI DA8XX SoC CFGCHIPx
> retisters. This will be used by a number of planned drivers including a
> new USB PHY driver and common clock framework drivers.
>
> The same defines are removed fr
On 07/21/2016 01:59 AM, Enric Balletbo Serra wrote:
[ ... ]
+static ssize_t ziirave_wdt_sysfs_store_firm(struct device *dev,
+ struct device_attribute *attr,
+ const char *buf, size_t count)
+{
+ struct i
On Tuesday, July 19, 2016 06:52:54 PM Sudeep Holla wrote:
> ACPI 6.0 introduced an optional object _LPI that provides an alternate
> method to describe Low Power Idle states. It defines the local power
> states for each node in a hierarchical processor topology. The OSPM can
> use _LPI object to se
On Tuesday, July 19, 2016 04:11:02 PM Lv Zheng wrote:
> There are many AML tables reporting wrong initial lid state, and some of
> them never report lid open state. As a proxy layer acting between, ACPI
> button driver is not able to handle all such cases, but need to re-define
> the usage model of
> if (atomic_read(&priv->sleepstatus.status) == 0) {
> rw_data = GCR_B_DOZE;
> - retval =
> - ks7010_sdio_write(priv, GCR_B, &rw_data, sizeof(rw_data));
> - if (retval) {
> + if (ks7010_sdio_write(priv,
> +
On Tuesday, July 19, 2016 06:00:39 PM Lv Zheng wrote:
> This patch adds debugger log flushing support in kernel via .ioctl()
> callback. The in-kernel flushing is more efficient, because it reduces
> useless log IOs by bypassing log user_read/kern_write during the flush
> period.
>
> Signed-off-by
Hi Thomas,
On 19/07/2016 16:38, Thomas Gleixner wrote:
> On Tue, 19 Jul 2016, Eric Auger wrote:
>> msi_doorbell_pages sum up the number of iommu pages of a given order
>
> adding () to the function name would make it immediately clear that
> msi_doorbell_pages is a function.
>
>> +/**
>> + * msi
Hi,
On 20/07/2016 10:12, Thomas Gleixner wrote:
> On Tue, 19 Jul 2016, Eric Auger wrote:
>> +bool msi_doorbell_safe(void)
>> +{
>> +struct irqchip_doorbell *db;
>> +bool irq_remapping = true;
>> +
>> +mutex_lock(&irqchip_doorbell_mutex);
>> +list_for_each_entry(db, &irqchip_doorbel
On Wednesday, July 20, 2016 04:12:08 PM Lv Zheng wrote:
> This patch adds multi-commands support for the batch mode. The same mode
> can be seen in acpiexec.
>
> However people may think this is not useful for an in-kernel debugger,
> because the in-kernel debugger is always running, never exits.
2016-07-21 15:24 GMT+02:00 Guenter Roeck :
> On 07/21/2016 01:59 AM, Enric Balletbo Serra wrote:
>
> [ ... ]
>
+static ssize_t ziirave_wdt_sysfs_store_firm(struct device *dev,
+ struct device_attribute
*attr,
+
Hi Vadim,
On 07/21/2016 07:55 AM, Vadim Pasternak wrote:
pmbus/dps400: disable PMBus status check through platform data structure to
provide support for PSU DPS-460, DPS-800 from Delta Electronics, INC and for
SGD009 from Acbel Polytech, INC.
These devices do not support the STATUS_CML register,
On Wed, Jul 20, 2016 at 11:59:44PM +0300, Pantelis Antoniou wrote:
> Hi David,
>
> Spent some time looking at this, and it looks like it’s going to the right
> direction.
>
> Comments inline.
>
> > On Jul 18, 2016, at 17:20 , David Gibson
> > wrote:
> >
> > Hi,
> >
> > Here's some of my tho
On Thu, Jul 21, 2016 at 02:43:56PM +0200, Grzegorz Jaszczyk wrote:
Hi Grzegorz
Some of these patches are missing a commit log entry. Please add at
least one line.
Andrew
>> @@ -323,14 +323,14 @@ static void tx_device_task(void *dev)
>> {
>> struct ks_wlan_private *priv = (struct ks_wlan_private *)dev;
>> struct tx_device_buffer *sp;
>> -int rc = 0;
>>
>> DPRINTK(4, "\n");
>> if (cnt_txqbody(priv) > 0
>> && atomic_read(&priv->psstat
On Thu, 21 Jul 2016, SF Markus Elfring wrote:
> >> @@ -323,14 +323,14 @@ static void tx_device_task(void *dev)
> >> {
> >>struct ks_wlan_private *priv = (struct ks_wlan_private *)dev;
> >>struct tx_device_buffer *sp;
> >> - int rc = 0;
> >>
> >>DPRINTK(4, "\n");
> >>if (cnt_txq
This patch allows flock, posix locks, ofd locks and leases to work
correctly on overlayfs.
Instead of using the underlying inode for storing lock context use the
overlay inode. This allows locks to be persistent across copy-up.
This is done by introducing locks_inode() helper and using it instea
I've split out the writecount handling and changed it around so that
underlying layers are consistent and yet leases work correctly on
overlayfs.
Also pushed to the tip of
git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/vfs.git overlayfs-next
Thanks,
Miklos
---
Miklos Szeredi (3):
lo
The problem with writecount is: we want consistent handling of it for
underlying filesystems as well as overlayfs. Making sure i_writecount is
correct on all layers is difficult. Instead this patch makes sure that
when write access is acquired, it's always done on the underlying writable
layer (c
d_op->d_real() leaves the dentry alone except if the third argument is
non-zero. Unfortunately very difficult to explain to the compiler without
a cast.
Signed-off-by: Miklos Szeredi
---
include/linux/dcache.h | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/include/linu
With the reintroduction of per-zone LRU stats, highmem_file_pages is
redundant so remove it.
Signed-off-by: Mel Gorman
---
include/linux/mm_inline.h | 17 -
mm/page-writeback.c | 12
2 files changed, 4 insertions(+), 25 deletions(-)
diff --git a/include/linux/
Both Joonsoo Kim and Minchan Kim have reported premature OOM kills.
The common element is a zone-constrained allocation failings. Two factors
appear to be at fault -- pgdat being considered unreclaimable prematurely
and insufficient rotation of the active list.
The series is in three basic parts;
Page reclaim determines whether a pgdat is unreclaimable by examining how
many pages have been scanned since a page was freed and comparing that to
the LRU sizes. Skipped pages are not reclaim candidates but contribute to
scanned. This can prematurely mark a pgdat as unreclaimable and trigger
an OO
On Wed, Jul 20, 2016 at 05:48:37PM -0600, Jens Axboe wrote:
> On 07/15/2016 10:19 AM, Konrad Rzeszutek Wilk wrote:
> >Hey Jens,
> >
> >I have some patches for Xen block driver that are based on Linus's tree
> >which has:
> >7b427a5 xen-blkfront: save uncompleted reqs in blkfront_resume()
> >
>
If per-zone LRU accounting is available then there is no point
approximating whether reclaim and compaction should retry based on pgdat
statistics. This is effectively a revert of "mm, vmstat: remove zone and
node double accounting by approximating retries" with the difference that
inactive/active
From: Minchan Kim
While I did stress test with hackbench, I got OOM message frequently which
didn't ever happen in zone-lru.
gfp_mask=0x26004c0(GFP_KERNEL|__GFP_REPEAT|__GFP_NOTRACK), order=0
..
..
[] __alloc_pages_nodemask+0xe52/0xe60
[] ? new_slab+0x39c/0x3b0
[] new_slab+0x39c/0x3b0
[] ___
On Thu, Jul 21, 2016 at 10:10:57AM +0900, SeongJae Park wrote:
> An example result for data dependent write has a typo. This commit
> fixes the wrong typo.
>
> Signed-off-by: SeongJae Park
Good catch! Queued, thank you!
Thanx, Paul
> --
From: Minchan Kim
Minchan Kim reported that with per-zone lru state it was possible to
identify that a normal zone with 8^M anonymous pages could trigger
OOM with non-atomic order-0 allocations as all pages in the zone
were in the active list.
gfp_mask=0x26004c0(GFP_KERNEL|__GFP_REPEAT|__GFP_
On 7/20/2016 10:04 PM, Christoph Lameter wrote:
We are trying to test the patchset on x86 and are getting strange
backtraces and aborts. It seems that the cpu before the cpu we are running
on creates an irq_work event that causes a latency event on the next cpu.
This is weird. Is there a new rou
>> * Do you occasionally care for a refactoring like "Reduce scope of variable"?
>>
>> http://refactoring.com/catalog/reduceScopeOfVariable.html
>
> Probably not. Certainly not in this case.
In which use cases would the suggested change pattern be more interesting
for you?
Regards,
Markus
Hi,
On 18/07/16 21:37, Xunlei Pang wrote:
> On 2016/07/18 at 21:04, Juri Lelli wrote:
> > On 15/07/16 18:39, Xunlei Pang wrote:
> >> On 2016/07/13 at 18:58, Juri Lelli wrote:
> > [...]
> >
> >> Since this is only called for queued cases now, there is no need to
> >> check boosted stuff here. As en
Hi Russel, Thmoas
2016-07-21 14:46 GMT+02:00 Thomas Petazzoni
:
> Hello,
>
> On Thu, 21 Jul 2016 13:44:09 +0100, Russell King - ARM Linux wrote:
>> On Thu, Jul 21, 2016 at 02:43:59PM +0200, Grzegorz Jaszczyk wrote:
>> > Signed-off-by: Grzegorz Jaszczyk
>>
>> Why? It's not like this is an on-soc
Hi David,
> On Jul 21, 2016, at 16:42 , David Gibson wrote:
>
> On Wed, Jul 20, 2016 at 11:59:44PM +0300, Pantelis Antoniou wrote:
>> Hi David,
>>
>> Spent some time looking at this, and it looks like it’s going to the right
>> direction.
>>
>> Comments inline.
>>
>>> On Jul 18, 2016, at 17:
On Fri, Jul 10, 2015 at 02:57:51PM -0400, Konrad Rzeszutek Wilk wrote:
> On Fri, Jul 10, 2015 at 02:37:46PM -0400, Konrad Rzeszutek Wilk wrote:
> > When Xen migrates an HVM guest, by default its shared_info can
> > only hold up to 32 CPUs. As such the hypercall
> > VCPUOP_register_vcpu_info was int
Some panels (like Sharp LQ123P1JX31) need to be turn off when eDP
controller stop to send valid video signal, otherwhise panel would
go burn in, and keep flicker and flicker.
So it's better to turn off the panel when eDP need to disable, and
we need to turn on the panel in connector->detect() call
On Thu 21-07-16 13:45:40, Ian Jackson wrote:
> I see that linux-4.1.y is still at 5880876e9469 which has the serious
> bug introduced by the backport c5ad33184354 "mm/swap.c: flush lru
> pvecs on compound page arrival".
>
> The analogous problem is also still affecting at least linux-3.18.y.
>
>
On Thu, Jul 21, 2016 at 9:14 AM, Yakir Yang wrote:
> Some panels (like Sharp LQ123P1JX31) need to be turn off when eDP
> controller stop to send valid video signal, otherwhise panel would
> go burn in, and keep flicker and flicker.
>
> So it's better to turn off the panel when eDP need to disable,
Allow drivers to pass in the affinity mask from the generic interrupt
layer, and spread queues based on that. If the driver doesn't pass in
a mask we will create it using the genirq helper. As this helper was
modelled after the blk-mq algorithm there should be no change in
behavior.
Signed-off-b
On Thu, Jul 21, 2016 at 9:14 AM, Yakir Yang wrote:
> According to page 16 of Sharp LQ123P1JX31 datasheet, we need to add the
> missing delay timing. Panel prepare time should be t1 (0.5ms~10ms) plus
> t3 (0ms~100ms), and panel enable time should equal to t7 (0ms~50ms), and
> panel unprepare time s
This series adds a new set of functions that transparently use the right
type of interrupt (MSI-X, MSI, legacy interrupt line) for a PCI device,
and if multiple vectors are supported automatically spreads the irq
routing to different CPUs. This will allow the block layer (and hopefully
other consu
On 07/21/2016 07:08 AM, Vadim Pasternak wrote:
[ ... ]
};
diff --git a/drivers/hwmon/pmbus/pmbus_core.c
b/drivers/hwmon/pmbus/pmbus_core.c
index ba59eae..3d98070 100644
--- a/drivers/hwmon/pmbus/pmbus_core.c
+++ b/drivers/hwmon/pmbus/pmbus_core.c
@@ -1931,8 +1931,11 @@ EXPORT_SYMBOL_GPL(pmb
Currently blk-mq will totally remap hardware context when a CPU hotplug
even happened, which causes major havoc for drivers, as they are never
told about this remapping. E.g. any carefully sorted out CPU affinity
will just be completely messed up.
The rebuild also doesn't really help for the comm
Quoting Aleksa Sarai (asa...@suse.de):
> >>I feel like the permission model makes sense in certain cases (the common
> >>ancestor restriction, as well as the ability for a parent to apply limits to
> >>children by setting its own limits). Neither of those are violated (if you
> >>read the commit th
The mapping is identical for all queues in a tag_set, so stop wasting
memory for building multiple. Note that for now I've kept the mq_map
pointer in the request_queue, but we'll need to investigate if we can
remove it without suffering from the additional indirection. The same
would apply to the
On 21/07/16 15:21, Juri Lelli wrote:
> Hi,
>
> On 18/07/16 21:37, Xunlei Pang wrote:
> > On 2016/07/18 at 21:04, Juri Lelli wrote:
> > > On 15/07/16 18:39, Xunlei Pang wrote:
> > >> On 2016/07/13 at 18:58, Juri Lelli wrote:
> > > [...]
> > >
> > >> Since this is only called for queued cases now, t
I feel like the permission model makes sense in certain cases (the common
ancestor restriction, as well as the ability for a parent to apply limits to
children by setting its own limits). Neither of those are violated (if you
read the commit that introduced the common ancestor restriction).
Maybe
On 07/20/2016 06:55 PM, zhouchengming wrote:
> Thanks for your reply. I don't know the compiler will optimize the loop.
> But when I see the assembly code of __section_nr, it seems to still have
> the loop in it.
Oh, well. I guess it got broken in the last decade or so. Your patch
looks good to
Hi Andrey,
On 07/14/2016 08:20 PM, Andrey Vagin wrote:
Each namespace has an owning user namespace and now there is not way
to discover these relationships.
Pid and user namepaces are hierarchical. There is no way to discover
parent-child relationships too.
Why we may want to know relationship
Signed-off-by: Pratik Prajapati
---
drivers/iio/light/vcnl4000.c | 78
1 file changed, 72 insertions(+), 6 deletions(-)
diff --git a/drivers/iio/light/vcnl4000.c b/drivers/iio/light/vcnl4000.c
index 360b6e9..1378175 100644
--- a/drivers/iio/light/vcnl
Signed-off-by: Pratik Prajapati
---
drivers/iio/light/vcnl4000.c | 91 +---
1 file changed, 78 insertions(+), 13 deletions(-)
diff --git a/drivers/iio/light/vcnl4000.c b/drivers/iio/light/vcnl4000.c
index 1378175..61e48f8 100644
--- a/drivers/iio/light/vcn
Hi Andi,
On Thu, Jul 21, 2016 at 09:48:12AM +0900, Andi Shyti wrote:
> > > Raw transmitters receive the data which need to be sent to
> > > receivers from userspace as stream of bits, they don't require
> > > any handling from the lirc framework.
> >
> > No drivers of type RC_DRIVER_IR_RAW_TX sho
Hi Andrew,
Andrew Lunn writes:
>> net/dsa/dsa.c| 985
>> net/dsa/legacy.c | 1013
>> ++
>
> I'm surprised git did not notice this is a rename.
I used -M though, even -C doesn't change
Hello, Stephen.
On Thu, Jul 21, 2016 at 03:26:03PM +1000, Stephen Rothwell wrote:
> Hi Tejun,
>
> After merging the libata tree, today's linux-next build (arm
> multi_v7_defconfig) produced these warning:
>
> drivers/ata/libata-scsi.c: In function 'ata_mselect_caching':
> drivers/ata/libata-scsi
On 21/07/16 15:36, Juri Lelli wrote:
> On 21/07/16 15:21, Juri Lelli wrote:
> > Hi,
> >
> > On 18/07/16 21:37, Xunlei Pang wrote:
> > > On 2016/07/18 at 21:04, Juri Lelli wrote:
> > > > On 15/07/16 18:39, Xunlei Pang wrote:
> > > >> On 2016/07/13 at 18:58, Juri Lelli wrote:
> > > > [...]
> > > >
>
On 21 July 2016 at 01:47, Jiri Olsa wrote:
> On Wed, Jul 20, 2016 at 02:38:17PM -0600, Mathieu Poirier wrote:
>
> SNIP
>
>> diff --git a/tools/perf/util/parse-events.h b/tools/perf/util/parse-events.h
>> index d1edbf8cc66a..8d09a976fca8 100644
>> --- a/tools/perf/util/parse-events.h
>> +++ b/tools
On Tue, Jul 19, 2016 at 11:51 AM, Peter Meerwald-Stadler
wrote:
>
>
> > > comments below; nice addition
> > >
> > > it seems this patch clashes with the recent changes to this driver in
> > > iio-testing; can you rebase on top please?
> >
> > Where is iio-testing? I couldn't found it in linux.
>
>
Florian Fainelli writes:
> Le 20/07/2016 à 17:35, Andrew Lunn a écrit :
>> On Wed, Jul 20, 2016 at 06:26:41PM -0400, Vivien Didelot wrote:
>>> This patch simply moves the legacy DSA code from dsa.c to legacy.c,
>>> except the few shared symbols which remain in dsa.c.
>>
>> I think it is a bit ea
On Thu, 21 Jul 2016, Greg Ungerer wrote:
> Hi Nicolas,
>
> On 21/07/16 05:22, Nicolas Pitre wrote:
> > This series provides the necessary changes to allow "flat" executable
> > binaries meant for no-MMU systems to actually run on systems with a MMU.
> > Also thrown in are various cleanups to binf
On 07/20/2016 11:49 AM, Catalin Marinas wrote:
On Fri, Jul 08, 2016 at 12:35:48PM -0400, David Long wrote:
+#define MIN_STACK_SIZE(addr) (on_irq_stack(addr, raw_smp_processor_id()) ? \
+ min((unsigned long)IRQ_STACK_SIZE, \
+ IRQ_STACK_PTR(raw_smp_processor_id()) - (addr)) : \
On Thu, Jul 21, 2016 at 08:44:53AM -0600, Mathieu Poirier wrote:
SNIP
> >> diff --git a/tools/perf/util/parse-events.l
> >> b/tools/perf/util/parse-events.l
> >> index 7a2519435da0..1f7e11a6c5b3 100644
> >> --- a/tools/perf/util/parse-events.l
> >> +++ b/tools/perf/util/parse-events.l
> >> @@ -5
Hi Sean,
> > > > + ret = regulator_enable(idata->regulator);
> > > > + if (ret)
> > > > + return ret;
> > > > +
> > > > + mutex_lock(&idata->mutex);
> > > > + idata->xfer.len = n;
> > > > + idata->xfer.tx_buf = buffer;
> > > > + mutex_unlock(&idata
Enable the kernel to detect "hung tasks",
which are bugs that cause the task to be stuck in
uninterruptible "D" state indefinitiley.
Note we're setting HUNG_TASK_TIMEOUT to 10 seconds instead of
default 120 to shorten time required for detection of hung task,
as it set in axs101, axs103 and axs103_
On Thu, 2016-07-21 at 09:33 -0500, Serge E. Hallyn wrote:
> Quoting Aleksa Sarai (asa...@suse.de):
> > > > The reason I'm doing this is so that we might be able to
> > > > _practically_ use cgroups as an unprivileged user (something
> > > > that will almost certainly be useful to not just the cont
Hello, Aleksa.
On Thu, Jul 21, 2016 at 05:49:36PM +1000, Aleksa Sarai wrote:
> > > The reason I'm doing this is so that we might be able to _practically_ use
> > > cgroups as an unprivileged user (something that will almost certainly be
> > > useful to not just the container crowd, but people also
On Jul 21, 2016 1:14 AM, "Ingo Molnar" wrote:
>
>
> * Andy Lutomirski wrote:
>
> > Under some conditions, my Dell XPS 13 9350 puts the EBDA at 0x2c000
> > but reports the lowmem cutoff as 0. The old code reserves
> > everything above 0x2c000 and I can't boot [1].
>
> > [1] This only breaks boot
Hello, James.
On Thu, Jul 21, 2016 at 07:51:49AM -0700, James Bottomley wrote:
> What I haven't really heard yet in the debate is the policy reason why
> an unprivileged user shouldn't set up their own cgroups as children of
> the current ones (inheriting the constraints).
It's not even about pol
- Original Message -
> From: "Rafael J. Wysocki"
> To: "Paolo Bonzini"
> Cc: linux-kernel@vger.kernel.org, "Thomas Renninger" , "Peter
> Zijlstra" ,
> linux...@vger.kernel.org, "Jacob Pan" , "Andy
> Lutomirski"
> Sent: Thursday, July 21, 2016 3:19:28 PM
> Subject: Re: [PATCH resend]
201 - 300 of 792 matches
Mail list logo
