On 15-05-15, 00:03, Rafael J. Wysocki wrote:
> > + * SCPI CPUFreq Interface driver
>
> It would be good to expand the TLA here IMO.
>
> The rest I'm leaving to Viresh. :-)
The rest looks fine :)
Acked-by: Viresh Kumar
--
viresh
--
To unsubscribe from this list: send the line "unsubscribe
Hi Linus,
radeon, one oops fix, one bug fix, one pci id addition patch
i915, one suspend/resume regression fix.
all seems quiet enough.
Dave.
The following changes since commit 030bbdbf4c833bc69f502eae58498bc5572db736:
Linux 4.1-rc3 (2015-05-10 15:12:29 -0700)
are available in the git
On 5/14/15 8:54 PM, Wangnan (F) wrote:
Hi Alexei Starovoitov and other,
I triggered a kernel panic when developing my 'perf bpf' facility. The
call stack is listed at the bottom of
this mail.
I attached two bpf programs on 'kmem_cache_free%return' and
'__alloc_pages_nodemask'. The programs is
On Thu, May 14, 2015 at 05:52:38PM -0700, Guenter Roeck wrote:
> On 05/14/2015 07:09 AM, Andreas Werner wrote:
> >On Thu, May 14, 2015 at 06:30:05AM -0700, Guenter Roeck wrote:
> >>On 05/14/2015 04:56 AM, Andreas Werner wrote:
> >>>Hi,
> >>>in the next few weeks I need to write a driver for a
Hi Paul,
Today's linux-next merge of the rcu tree got a conflict in
net/netfilter/core.c between commit f7191483461c ("netfilter: add hook
list to nf_hook_state") from the net-next tree and commit e4dcfe3a648b
("netfilter: Fix list_entry_rcu usage") from the rcu tree.
I fixed it up (I used the
On Wed, May 13, 2015 at 05:00:26AM -0700, Srinivas Kandagatla wrote:
> This patch tries to make the lpass driver more generic by moving the
> ipq806x specific bits out of the cpu and platform driver, also allows the
> SOC specific drivers to add the correct register offsets.
>
> This patch also
On Wed, May 13, 2015 at 05:03:14AM -0700, Srinivas Kandagatla wrote:
> This patch adds apq8016 machine driver support. This patch was tested on
> two apq8016-sbc and msm8916-mtp board for both hdmi and analog audio
> features.
> diff --git a/sound/soc/qcom/Kconfig b/sound/soc/qcom/Kconfig
> index
On Wed, May 13, 2015 at 05:00:52AM -0700, Srinivas Kandagatla wrote:
> This patch adds support to allow bitclk and osrclk per i2s dai port.
> on APQ8016 there are 4 i2s ports each one has its own bit clks.
>
> Without this patch its not possible to support multiple i2s ports in the
> lpass
On Wed, May 13, 2015 at 05:03:06AM -0700, Srinivas Kandagatla wrote:
> This patch adds apq8016 lpass driver support. APQ8016 has 4 MI2S which
> can be routed to one internal codec and 2 external codec interfaces.
>
> Primary, Secondary, Quaternary I2S can do Rx(playback) and Tertiary and
>
On Thu, May 14, 2015 at 05:39:46PM -0400, David Miller wrote:
> From: kbuild test robot
> Date: Fri, 15 May 2015 03:02:35 +0800
>
> >
> > Signed-off-by: Fengguang Wu
> > ---
> > be_main.c |2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git
On Fri, 2015-05-15 at 12:31PM +0900, Masahiro Yamada wrote:
> This function is only referenced in this file.
>
> Signed-off-by: Masahiro Yamada
Reviewed-by: Sören Brinkmann
Sören
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On 05/15/2015 05:09 AM, Viresh Kumar wrote:
On 15 May 2015 at 01:45, Rafael J. Wysocki wrote:
You need ACKs from Viresh for those two, then. He's officially responsible
for ARM cpufreq drivers.
I thought an Ack for 14th is enough :)
For: 12/13/14.
Acked-by: Viresh Kumar
Thanks! :)
It
On Fri, May 15, 2015 at 8:59 AM, Rafael J. Wysocki wrote:
> On Fri, May 15, 2015 at 2:40 AM, Ming Lei wrote:
>> On Fri, May 15, 2015 at 8:34 AM, Rafael J. Wysocki
>> wrote:
>>> On Friday, May 15, 2015 09:54:26 AM Dave Chinner wrote:
ng back On Thu, May 14, 2015 at 09:22:51AM +1000,
On Mon, May 11, 2015 at 07:08:09PM +0100, Al Viro wrote:
> @@ -499,7 +499,7 @@ struct nameidata {
> struct path root;
> struct inode*inode; /* path.dentry.d_inode */
> unsigned intflags;
> - unsignedseq, m_seq;
> + unsignedseq, m_seq, root_seq;
On Tue, May 12, 2015 at 05:10:01AM +0100, Al Viro wrote:
> +static int unlazy_link(struct nameidata *nd, struct path *link, unsigned seq)
> +{
> + if (unlikely(!legitimize_path(nd, link, seq))) {
> + drop_links(nd);
> + rcu_read_unlock();
> + nd->flags &=
>
> kmemleak_disable() may be called in an atomic context, so calling
> kthread_stop() here is not safe. We have a scan_should_stop() function
> which checks for the kmemleak_enabled variable but it doesn't seem to be
> enough.
>
> Basically the object_list has some vmalloc'ed objects. Scanning
> -Original Message-
> From: Linux-nvdimm [mailto:linux-nvdimm-boun...@lists.01.org] On Behalf
> Of Dan Williams
> Sent: Thursday, May 14, 2015 7:42 PM
> To: Kani, Toshimitsu
> Cc: Neil Brown; Greg KH; linux-kernel@vger.kernel.org; linux-
> nvd...@lists.01.org
> Subject: Re: [Linux-nvdimm]
The arch independent uart8250 early console driver has good
support for memory mapped and io port based 8250 uarts. Since
pci is arch independent so it's natural to extend uart8250 to
support mem, io and pci. Hence pci uart early console in
arch/x86/kernel_printk.c by the following commit:
'commit
On some Intel Atom SoCs, the legacy IO port UART(0x3F8) is not available.
Instead, a 8250 compatible PCI uart can be used as early console.
This patch adds pci support to the 8250 early console driver uart8250.
For example, to enable pci uart(00:21.3) as early console on these
platforms, append
In powerpc, when a thread running in the guest context needs to exit to
the hypervisor to serve interrupts like the external interrupt, or the
hcall interrupt, etc, all the threads running in that specific vcore
inside the guest exit. These events can be classified as gang exits
which mean that
In powerpc, if a thread running inside a guest needs to exit to the
host to serve interrupts like the external interrupt, or the hcall
interrupts, etc., all the threads running in that specific vcore
inside the guest exit to the host. These events are called as ganged
exits.
Because of the ganged
Whenever an interrupt is received for opal the linux kernel gets a
bitfield indicating certain events that have occurred and need handling
by the various device drivers. Currently this is handled using a
notifier interface where we call every device driver that has
registered to receive opal
Convert the opal hvc driver to use the new irqchip to register for
opal events. As older firmware versions may not have device tree
bindings for the interrupt parent we just use a hardcoded hwirq based
on the event number.
Signed-off-by: Alistair Popple
---
drivers/tty/hvc/hvc_opal.c | 33
The eeh code currently uses the old notifier method to get eeh events
from OPAL. It also contains some logic to filter opal events which has
been moved into the virtual irqchip. This patch converts the eeh code
to the new event interface which simplifies event handling.
Signed-off-by: Alistair
Convert the opal ipmi driver to use the new irq interface for events.
Signed-off-by: Alistair Popple
Acked-by: Corey Minyard
Cc: Corey Minyard
Cc: openipmi-develo...@lists.sourceforge.net
---
drivers/char/ipmi/ipmi_powernv.c | 39 ++-
1 file changed, 22
This patch converts the elog code to use the opal irq domain instead
of notifier events.
Signed-off-by: Alistair Popple
---
arch/powerpc/platforms/powernv/opal-elog.c | 32 +++---
1 file changed, 16 insertions(+), 16 deletions(-)
diff --git
All users of the old opal events notifier have been converted over to
the irq domain so remove the event notifier functions.
Signed-off-by: Alistair Popple
---
arch/powerpc/platforms/powernv/opal-irqchip.c | 16 ++---
arch/powerpc/platforms/powernv/opal.c | 84
This patch converts the opal message event to use the new opal irq
domain.
Signed-off-by: Alistair Popple
---
arch/powerpc/platforms/powernv/opal.c | 29 +++--
1 file changed, 15 insertions(+), 14 deletions(-)
diff --git a/arch/powerpc/platforms/powernv/opal.c
Convert the opal dump driver to the new opal irq domain.
Signed-off-by: Alistair Popple
---
arch/powerpc/platforms/powernv/opal-dump.c | 56 +-
1 file changed, 17 insertions(+), 39 deletions(-)
diff --git a/arch/powerpc/platforms/powernv/opal-dump.c
Most of the OPAL subsystems are always compiled in for PowerNV and
many of them need to be initialised before or after other OPAL
subsystems. Rather than trying to control this ordering through
machine initcalls it is clearer and easier to control initialisation
order with explicit calls in
Whenever an interrupt is received for opal the linux kernel gets a
bitfield indicating certain events that have occurred and need handling
by the various device drivers. Currently this is handled using a
notifier interface where we call every device driver that has
registered to receive opal
Hi Alexei Starovoitov and other,
I triggered a kernel panic when developing my 'perf bpf' facility. The
call stack is listed at the bottom of
this mail.
I attached two bpf programs on 'kmem_cache_free%return' and
'__alloc_pages_nodemask'. The programs is very simple.
The panic is raised
This refactors the fw_event code to use the new refcount.
Signed-off-by: Calvin Owens
---
drivers/scsi/mpt2sas/mpt2sas_scsih.c | 20 +---
1 file changed, 13 insertions(+), 7 deletions(-)
diff --git a/drivers/scsi/mpt2sas/mpt2sas_scsih.c
b/drivers/scsi/mpt2sas/mpt2sas_scsih.c
Since the fw_event deletes itself from the list, cleanup_queue() can
walk onto garbage pointers or walk off into freed memory.
This refactors the code in _scsih_fw_event_cleanup_queue() to not
iterate over the fw_event_list without a lock.
Signed-off-by: Calvin Owens
---
We cannot iterate over the list without holding a lock for the entire
duration, or we risk corrupting random memory if items are added or
deleted as we iterate.
This refactors code such that it always holds the lock when iterating
on or accessing the sas_device_list.
Signed-off-by: Calvin Owens
These objects can be referenced concurrently throughout the driver, we
need a way to make sure threads can't delete them out from under each
other.
Signed-off-by: Calvin Owens
---
drivers/scsi/mpt2sas/mpt2sas_base.h | 16
1 file changed, 16 insertions(+)
diff --git
Hello all,
This patchset attempts to address problems we've been having with
panics due to memory corruption from the mpt2sas driver.
I will provide a similar set of fixes for mpt3sas, since we see
similar issues there as well. "Porting" this to mpt3sas will be
trivial since the part of the
The fw_event_work struct is concurrently referenced at shutdown, so
add a refcount to protect it.
Signed-off-by: Calvin Owens
---
drivers/scsi/mpt2sas/mpt2sas_scsih.c | 28
1 file changed, 28 insertions(+)
diff --git a/drivers/scsi/mpt2sas/mpt2sas_scsih.c
This patch refactors the code in the driver to use the new reference
count on the sas_device struct.
Signed-off-by: Calvin Owens
---
drivers/scsi/mpt2sas/mpt2sas_base.h | 4 +-
drivers/scsi/mpt2sas/mpt2sas_scsih.c | 329 ---
This function is only referenced in this file.
Signed-off-by: Masahiro Yamada
---
drivers/pinctrl/pinctrl-zynq.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/pinctrl/pinctrl-zynq.c b/drivers/pinctrl/pinctrl-zynq.c
index 22280bd..3d5453a 100644
---
When encryption feature is enable, if we rmmod f2fs module,
we will encounter a stack backtrace reported in syslog:
"BUG: Bad page state in process rmmod pfn:aaf8a
page:f0f4f148 count:0 mapcount:129 mapping:ee2f4104 index:0x80
flags:
On 05/14/2015 08:06 PM, Daniel Phillips wrote:
> Hi Rik,
>
> Added Mel, Andrea and Peterz to CC as interested parties. There are
> probably others, please just jump in.
>
> On 05/14/2015 05:59 AM, Rik van Riel wrote:
>> On 05/14/2015 04:26 AM, Daniel Phillips wrote:
>>> Hi Rik,
>>>
>>> Our
Hello,
I am Liliane Bettencourt,confirm that you got this email as soon as you read
it, you can read about me on:http://en.wikipedia.org/wiki/Liliane_Bettencourt
I write to you because I intend to give to you a portion of my Net-worth which
I have been banking. I want to cede it out as gift
god dag
Dette er Santander Consumer Finance tilbyr vi sikret og usikret personlige lån
som hjelper i forretnings dine investeringer og hjem behov og budsjett med en
lav rente på 3% og konsentrasjoner på opp til 5000 i både dollar / euro og
10,000.000.00 dollar / euro. Kontakt oss ved å fylle
It is possible for fbq_classify_rq to indicate that a CPU has tasks that
should be moved to another NUMA node, but for migrate_improves_locality
and migrate_degrades_locality to not identify those tasks.
This patch always gives preference to preferred node evaluations, and
only checks the number
On Thu, 14 May 2015 22:52:50 -0400
Steven Rostedt wrote:
> TRACE_SYSTEM_STRING is used internally to the TRACE_EVENT system. It
> should not be defined by tracepoint files. I'm not even sure who
> started that (I hope it wasn't me!)
According to git history, that define first showed up in
TRACE_SYSTEM_STRING is used internally to the TRACE_EVENT system. It
should not be defined by tracepoint files. I'm not even sure who
started that (I hope it wasn't me!)
Reported-by: kbuild test robot
Signed-off-by: Steven Rostedt http://vger.kernel.org/majordomo-info.html
Please read the FAQ at
On Thu, May 14, 2015 at 07:18:16PM -0700, Linus Torvalds wrote:
> The only difference - EVER - would be if you pass in the ICASE flag.
> Nothing I suggested would change semantics without it (the _hash_
> changes, but that doesn't change semantics, it's a purely internal
> random number).
>
>
From: Simon Xiao
Date: Thu, 14 May 2015 01:00:25 -0700
> Current code does not lock anything when calculating the TX and RX stats.
> As a result, the RX and TX data reported by ifconfig are not accuracy in a
> system with high network throughput and multiple CPUs (in my test,
> RX/TX = 83%
I am not replying for concept here, as sched maintainers are in a
better position for that, but a nit below..
On 14-05-15, 17:12, Ruchi Kandoi wrote:
> Adds the sysfs file for userspace to initialize the active current
> values for all the cores at each of the frequencies.
>
> The format for
Hi Ishimatsu,
On 05/15/2015 12:44 AM, Yasuaki Ishimatsu wrote:
> Hi Gu,
>
> Before 8 months, I posted the following patch to relate
> cpuid to apicid.
>
> https://lkml.org/lkml/2014/9/3/1120
>
> Could you try this patch?
Thanks for your reminder.
It seems similar to the
On Thu, May 14, 2015 at 06:01:01PM +0100, Julien Grall wrote:
> The PV network protocol is using 4KB page granularity. The goal of this
> patch is to allow a Linux using 64KB page granularity working as a
> network backend on a non-modified Xen.
>
> It's only necessary to adapt the ring size and
On 15/05/14, Paul Moore wrote:
> On Thursday, May 14, 2015 10:57:14 AM Steve Grubb wrote:
> > On Tuesday, May 12, 2015 03:57:59 PM Richard Guy Briggs wrote:
> > > On 15/05/05, Steve Grubb wrote:
> > > > I think there needs to be some more discussion around this. It seems
> > > > like this is not
From: Bjorn Helgaas
Date: Thu, 14 May 2015 18:17:08 -0500
> With a cross-compiler based on gcc-4.9, I see warnings like the following:
>
> drivers/net/ethernet/mellanox/mlx4/resource_tracker.c: In function
> 'mlx4_SW2HW_CQ_wrapper':
>
This allows detecting improper format string at build time, like:
fs/coredump.c:225:5: warning: format '%ld' expects argument of type
'long int', but argument 3 has type 'int' [-Wformat=]
err = cn_printf(cn, "%ld", cprm->siginfo->si_signo);
^
As si_signo is always an int, the
When adding __printf attribute to cn_printf, gcc reports some issues:
fs/coredump.c:213:5: warning: format '%d' expects argument of type
'int', but argument 3 has type 'kuid_t' [-Wformat=]
err = cn_printf(cn, "%d", cred->uid);
^
fs/coredump.c:217:5: warning: format '%d'
Hello,
On Thu, May 14, 2015 at 12:22:30PM +, Wang Nan wrote:
> Original vmlinux_path__exit() doesn't revert vmlinux_path__nr_entries
> to its original state. After the while loop vmlinux_path__nr_entries
> becomes -1 instead of 0. This makes a problem that, if runs twice,
> during the second
On 15/05/14, Eric W. Biederman wrote:
> Paul Moore writes:
> > As Eric, and others, have stated, the container concept is a userspace
> > idea,
> > not a kernel idea; the kernel only knows, and cares about, namespaces.
> > This
> > is unlikely to change.
> >
> > However, as Steve points out,
From: Minfei Huang
The previous patches can be applied, once the corresponding module is
loaded. In general, the patch will do relocation (if necessary) and
obtain/verify function address before we start to enable patch.
There are three different situations in which the coming module notifier
On Thu, May 14, 2015 at 6:26 PM, Al Viro wrote:
>
> Hold on. Should
> stat("blah", ) => ENOENT, OK, let's create it
> mkdir("blah", 0)=> EEXIST, bugger, looks like a race
> stat("blah", ) => ENOENT, Whiskey, Tango, Foxtrot
> be possible?
No. What I
Hi Arnaldo,
On Thu, May 14, 2015 at 10:18:27AM -0300, Arnaldo Carvalho de Melo wrote:
> Em Thu, May 14, 2015 at 05:23:30PM +0900, Namhyung Kim escreveu:
> > On Mon, May 11, 2015 at 11:06:26AM -0300, Arnaldo Carvalho de Melo wrote:
> > > Em Mon, May 11, 2015 at 02:09:39PM +0900, Namhyung Kim
On 05/14/2015 09:43 AM, S Twiss wrote:
From: S Twiss
Add watchdog driver support for DA9062
Signed-off-by: Steve Twiss
---
Changes in V2:
- Removed informational dev_info() 'installed watchdog' message
- Copyright headers GPL v2 (and later) match correct 'GPL' in MODULE_LICENSE
-
Hi Michael,
On 05/13/2015 08:57 AM, Stephen Boyd wrote:
> On 05/12, Michael Turquette wrote:
>> Quoting Joonyoung Shim (2015-04-07 00:46:46)
>>> The round_rate callback function will returns alway same parent clk rate
>>> of divider with CLK_DIVIDER_READ_ONLY flag. If be used
>>>
On 15/05/14, Oren Laadan wrote:
> On Thu, May 14, 2015 at 8:48 PM, Richard Guy Briggs wrote:
>
> >
> > > > > Recording each instance of a name space is giving me something that I
> > > > > cannot use to do queries required by the security target. Given these
> > > > > events, how do I locate a
On 15 May 2015 at 01:45, Rafael J. Wysocki wrote:
> You need ACKs from Viresh for those two, then. He's officially responsible
> for ARM cpufreq drivers.
I thought an Ack for 14th is enough :)
For: 12/13/14.
Acked-by: Viresh Kumar
--
To unsubscribe from this list: send the line "unsubscribe
On 15/05/14, Eric W. Biederman wrote:
> Steve Grubb writes:
> > On Tuesday, May 12, 2015 03:57:59 PM Richard Guy Briggs wrote:
> >> On 15/05/05, Steve Grubb wrote:
> >> > I think there needs to be some more discussion around this. It seems like
> >> > this is not exactly recording things that are
Hi Stephen,
On 05/13/2015 08:59 AM, Stephen Boyd wrote:
> On 04/07, Joonyoung Shim wrote:
>> Even if use CLK_DIVIDER_READ_ONLY flag, divider setting can be changed
>> by set_rate callback. Don't change divider setting from set_rate
>> callback of divider with CLK_DIVIDER_READ_ONLY flag.
>>
>>
On 05/14/2015 09:39 PM, Nicholas Krause wrote:
On May 14, 2015 9:22:22 PM EDT, Jens Axboe wrote:
On 05/14/2015 07:57 PM, Nicholas Krause wrote:
This adds the proper required error checking to the function,
disk_add_events for when there are no disk events by returning
the error code,
On 05/14/15 at 05:05pm, Miroslav Benes wrote:
>
> Hi,
>
> I have few nitpicks...
>
> The subject is slightly misleading. We still apply the patch (or the patch
> is already applied to be precise). Only the coming module is not patched
> and won't be patched. So I propose something like
>
>
Paul Moore writes:
> As Eric, and others, have stated, the container concept is a userspace idea,
> not a kernel idea; the kernel only knows, and cares about, namespaces. This
> is unlikely to change.
>
> However, as Steve points out, there is precedence for the kernel to record
> userspace
SEGBITS default is 40 bits or less, depending from CPU type.
This patch introduces 48bits of application virtual address (SEGBITS) support.
It is defined only for 16K and 64K pages and is optional (configurable).
Penalty - a small number of additional pages for generic (small) applications.
But
On Wed, 2015-05-13 at 18:11 +0200, Torsten Duwe wrote:
> In order to avoid an endless recursion, functions that may get
> called from the data access handler must not call into tracing
> functions, which may cause data access faults ;-)
>
> Advancing from my previous approach that lavishly
Hello Stephen,
On 2015/5/15 8:27, Stephen Boyd wrote:
On 05/05, Bintian Wang wrote:
This patch adds documentation for the devicetree bindings used by the
DT files of Hisilicon hi6220 SoC mobile platform.
Signed-off-by: Bintian Wang
Acked-by: Stephen Boyd
Thanks for your ACK!
Bintian
On 05/14/15 at 09:30am, Josh Poimboeuf wrote:
> On Thu, May 14, 2015 at 09:51:07AM +0800, Minfei Huang wrote:
> > @@ -891,22 +891,24 @@ static void klp_module_notify_coming(struct klp_patch
> > *patch,
> > int ret;
> >
> > ret = klp_init_object_loaded(patch, obj);
> > - if (ret)
> > -
On Thu, May 14, 2015 at 05:25:39PM -0700, Linus Torvalds wrote:
> We can easily make things per-operation, by adding another flag. We
> already have per-operation flags like LOOKUP_FOLLOW, which decides if
> we follow the last symlink or not. We could add a LOOKUP_ICASE, which
> decides whether
Added support to calculate lux value from visible
and IR spectrum adc count values. Also added IIO_LIGHT
channel to enable user read the lux value directly
from device using illuminance input ABI.
Signed-off-by: Kuppuswamy Sathyanarayanan
---
drivers/iio/light/ltr501.c | 57
SEGBITS default is 40 bits or less, depending from CPU type.
This patch introduces 48bits of application virtual address (SEGBITS) support.
It is defined only for 16K and 64K pages and is optional (configurable).
Penalty - a small number of additional pages for generic (small) applications.
But
On 05/14/2015 07:57 PM, Nicholas Krause wrote:
This adds the proper required error checking to the function,
disk_add_events for when there are no disk events by returning
the error code, -EBUSY. Further this also adds error checking
for when our call to the function, sysfs_create_files by
On 04/27, Chanwoo Choi wrote:
> This patch shows the correct information for debugging when fail to set clock
> rate because original error message shows the error value instead of current
> clock rate.
>
> Cc: Mike Turquette
> Cc: Stephen Boyd
> Cc: Sylwester Nawrocki
> Signed-off-by: Chanwoo
On 04/07, Antoine Tenart wrote:
> The Berlin clock documentation was part of the Marvell Berlin SoC
> documentation because the Berlin clock configuration was inside the
> chip controller. With the recent rework of the chip and system
> controller handling (now all sub-devices of the soc and
On 04/07, Antoine Tenart wrote:
> The Berlin clock driver was sharing a DT node with the pin controller
> and the reset driver. All these devices are now sub-nodes of the chip
> controller. This patch rework the Berlin clock driver to allow moving
> the Berlin clock DT bindings into their own
On Thu, May 14, 2015 at 6:33 PM, Omar Sandoval wrote:
>
>
> Yup, Chris says he has a proper fix but it hasn't hit the list yet.
>
>
> Actually, ext4 convert is broken anyways (with irrelevant output
> elided):
I'm curious how this bug ended up in mainline. Isn't there an XFS test
for both
n the Exynos DRM options were enabled.
I saw your response in email 0/9 but let us stick to one thread.
So these are my only concerns - instability in the past.
>> http://storage.kernelci.org/next/next-20150514/arm-exynos_defconfig/lab-khilman/boot-exynos5250-arndale.html
>> [1.6
On Fri, May 8, 2015 at 5:24 PM, Peter Zijlstra wrote:
> On Thu, May 07, 2015 at 03:15:43PM +0100, Robert Bragg wrote:
>
>> I've changed the uapi for configuring the i915_oa specific attributes
>> when calling perf_event_open(2) whereby instead of cramming lots of
>> bitfields into the
On Fri, 15 May 2015 09:54:26 +1000 Dave Chinner wrote:
> ng back On Thu, May 14, 2015 at 09:22:51AM +1000, NeilBrown wrote:
> > On Mon, 11 May 2015 11:44:28 +1000 Dave Chinner wrote:
> >
> > > On Fri, May 08, 2015 at 03:08:43AM -0400, Len Brown wrote:
> > > > From: Len Brown
> > > >
> > > >
On Fri, May 15, 2015 at 2:40 AM, Ming Lei wrote:
> On Fri, May 15, 2015 at 8:34 AM, Rafael J. Wysocki wrote:
>> On Friday, May 15, 2015 09:54:26 AM Dave Chinner wrote:
>>> ng back On Thu, May 14, 2015 at 09:22:51AM +1000, NeilBrown wrote:
>>> > On Mon, 11 May 2015 11:44:28 +1000 Dave Chinner
t. Exception is Arndale 5250:
Yes, like I said in the other thread, the fact that Exynos DRM is
working fine now on most boards is mostly because the bugs were
exposed when the Exynos DRM options were enabled.
> http://storage.kernelci.org/next/next-20150514/arm-exynos_defconfig/lab-khilman
Hi,
On Wed, Apr 22, 2015 at 04:04:10PM -0700, Arun Ramamurthy wrote:
> Most of the phy providers use "select" to enable GENERIC_PHY. Since select
> is only recommended when the config is not visible, GENERIC_PHY is changed
> an invisible option. To maintain consistency, all phy providers are
On 05/14/2015 03:41 AM, Josh Triplett wrote:
>
> I have a patch series that does exactly that, compiling out the syscalls
> as well as the underlying architecture-specific infrastructure. (Saves
> quite a bit of space, too.)
>
> It still needs some more detailed x86 architecture review. Peter,
On 05/14/2015 07:09 AM, Andreas Werner wrote:
On Thu, May 14, 2015 at 06:30:05AM -0700, Guenter Roeck wrote:
On 05/14/2015 04:56 AM, Andreas Werner wrote:
Hi,
in the next few weeks I need to write a driver for a window wachtdog
implemented in a CPLD. I have some questions about the design
of
On 15/05/14, Steve Grubb wrote:
> On Tuesday, May 12, 2015 03:57:59 PM Richard Guy Briggs wrote:
> > On 15/05/05, Steve Grubb wrote:
> > > I think there needs to be some more discussion around this. It seems like
> > > this is not exactly recording things that are useful for audit.
> >
> > It
On Tue, May 12, 2015 at 9:33 AM, Toshi Kani wrote:
> On Tue, 2015-04-28 at 14:25 -0400, Dan Williams wrote:
>> Block devices from an nd bus, in addition to accepting "struct bio"
>> based requests, also have the capability to perform byte-aligned
>> accesses. By default only the bio/block
On Fri, May 15, 2015 at 8:34 AM, Rafael J. Wysocki wrote:
> On Friday, May 15, 2015 09:54:26 AM Dave Chinner wrote:
>> ng back On Thu, May 14, 2015 at 09:22:51AM +1000, NeilBrown wrote:
>> > On Mon, 11 May 2015 11:44:28 +1000 Dave Chinner
>> > wrote:
>> >
>> > > On Fri, May 08, 2015 at
Having this Kconfig sourced outside the clk menu means the option
is under the "Device Drivers" menu instead of the "Common Clock
Framework" menu. Move it so that the bcm clock config options are
in the right place.
Cc: Alex Elder
Signed-off-by: Stephen Boyd
---
drivers/clk/Kconfig | 2 +-
1
DMI displays.
Enabling the display would be nice but for some quite long time we had
issues with DRM on Exynos. exynos_defconfig has it enabled and most of
boards boot fine with it. Exception is Arndale 5250:
http://storage.kernelci.org/next/next-20150514/arm-exynos_defconfig/lab-khilman/boot-exynos5250-
Hello Krzysztof,
On Fri, May 15, 2015 at 2:18 AM, Krzysztof Kozlowski
wrote:
> 2015-05-15 0:40 GMT+09:00 Javier Martinez Canillas
> :
>> Hello arm-soc maintainers,
>>
>> This series is an attempt to reduce the delta between exynos_defconfig
>> and multi_v7_defconfig. Primarily to enable the
On Fri, May 15, 2015 at 12:15:06AM +, Duncan wrote:
> Josh Boyer posted on Thu, 14 May 2015 08:43:25 -0400 as excerpted:
>
> > Hi Omar and Chris,
> >
> > We have a bug reported [1] against 4.0 saying that btrfs balance is
> > broken. The reporter found a revert patch that Omar sent [2] to
On 05/05, Bintian Wang wrote:
> This patch adds documentation for the devicetree bindings used by the
> DT files of Hisilicon hi6220 SoC mobile platform.
>
> Signed-off-by: Bintian Wang
Acked-by: Stephen Boyd
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux
On Thu, May 14, 2015 at 06:00:48PM +0100, Julien Grall wrote:
> The variables old_req_cons and ring_slots_used are assigned but never
> used since commit 1650d5455bd2dc6b5ee134bd6fc1a3236c266b5b "xen-netback:
> always fully coalesce guest Rx packets".
>
> Signed-off-by: Julien Grall
> Cc: Ian
On Thu, May 14, 2015 at 4:36 PM, Al Viro wrote:
> On Thu, May 14, 2015 at 04:24:13PM -0700, Linus Torvalds wrote:
>
>> So ASCII-only case-insensitivity is sufficient for you guys?
>>
>> Doing case-insensitive lookups at a vfs layer level wouldn't be
>> impossible (add some new lookup flag, so it
1 - 100 of 1832 matches
Mail list logo
