On Sun, Dec 14, 2014 at 12:58:31PM +0100, Heinz Diehl wrote:
> Hi,
>
> since kernel 3.18 I'm no longer able to run X on my machine. While
> 3.17.6 is fine, 3.18 leaves me with a black screen when starting
> X. Booting into runlevel 1/3 is fine.
>
> I did a "git bisect", and the offending commit i
On Fri, Dec 12, 2014 at 4:16 PM, Griffis, Brad wrote:
> How are you configuring ti,charge-delay in your dts? I've seen this behavior
> on some custom boards where we were using a smaller charge delay (0x400) to
> begin with, and by upping it to 0xb000 we resolved the issue. These patches
> h
On Wed, Dec 10, 2014 at 10:30:17AM -0600, Christoph Lameter wrote:
> We had to insert a preempt enable/disable in the fastpath a while ago. This
> was mainly due to a lot of state that is kept to be allocating from the per
> cpu freelist. In particular the page field is not covered by
> this_cpu_cm
Acked-by: David Mosberger
On Mon, Dec 15, 2014 at 8:22 AM, Asaf Vertz wrote:
> To be future-proof and for better readability the time comparisons are
> modified to use time_after() instead of plain, error-prone math.
>
> Signed-off-by: Asaf Vertz
> ---
> drivers/usb/host/max3421-hcd.c |3 +
On Fri, Dec 12, 2014 at 05:01:24PM +0100, Vlastimil Babka wrote:
> When allocation falls back to another migratetype, it will steal a page with
> highest available order, and (depending on this order and desired
> migratetype),
> it might also steal the rest of free pages from the same pageblock.
On Fri, Dec 12, 2014 at 05:01:22PM +0100, Vlastimil Babka wrote:
> Changes since v1:
> o Reorder patch 2 and 3, Cc stable for patch 1
> o Fix tracepoint in patch 1 (Joonsoo Kim)
> o Cleanup in patch 2 (suggested by Minchan Kim)
> o Improved comments and changelogs per Minchan and Mel.
> o Considere
On Sun, Dec 14, 2014 at 02:07:19AM +0100, Emmanuel Benisty wrote:
> Hi Daniel,
>
> > On Mon, Nov 10, 2014 at 10:19 PM, Daniel Vetter
> > wrote:
> >> Adding relevant mailing lists.
> >>
> >>
> >> On Sat, Nov 8, 2014 at 7:34 PM, Emmanuel Benisty
> >> wrote:
> >>> Hi,
> >>>
> >>> The following co
On Mon, 2014-12-15 at 11:12 +0800, Charles Chiou wrote:
>
> On 12/10/2014 05:02 PM, Oliver Neukum wrote:
> > On Wed, 2014-12-10 at 09:38 +0800, Charles Chiou wrote:
> >> From 91868d4afe10533b8a4496075109e411100217bb Mon Sep 17 00:00:00 2001
> >> From: Charles Chiou
> >> Date: Fri, 7 Nov 2014 10
On Mon, 2014-12-15 at 16:28 +0900, Joonsoo Kim wrote:
> On Thu, Dec 11, 2014 at 04:00:30PM +0800, Huang Ying wrote:
> > FYI, we noticed the below changes on
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git master
> > commit 6a7d22008b2294f1dacbc77632a26f2142f2d4b0 ("mm: Fix boot c
We don't need to force to write dirty_exceeded for f2fs_balance_fs_bg.
This flag was only meaningful to write bypassing conditions.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/node.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/fs/f2fs/node.c b/fs/f2fs/node.c
index f83326c..d6f073e 100644
---
This patch adds two new ioctls to release inmemory pages grabbed by atomic
writes.
o f2fs_ioc_abort_volatile_write
- If transaction was failed, all the grabbed pages and data should be written.
o f2fs_ioc_release_volatile_write
- This is to enhance the performance of PERSIST mode in sqlite.
We don't need to call lock_op and lock_page at the aborting path.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/segment.c | 35 ---
1 file changed, 20 insertions(+), 15 deletions(-)
diff --git a/fs/f2fs/segment.c b/fs/f2fs/segment.c
index 11e4b5c..3ce86c5 100644
--- a/f
Now we use inmemory pages for atomic write only and provide abort procedure,
we don't need to truncate them explicitly.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/data.c| 3 ---
fs/f2fs/f2fs.h| 1 -
fs/f2fs/segment.c | 17 -
3 files changed, 21 deletions(-)
diff --git a/fs
This patch calls f2fs_kunmap_page which I missed before.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/dir.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/fs/f2fs/dir.c b/fs/f2fs/dir.c
index b1a7d57..b74097a 100644
--- a/fs/f2fs/dir.c
+++ b/fs/f2fs/dir.c
@@ -286,8 +286,7 @@ void
The ckpt_valid_map and cur_valid_map are synced by seg_info_to_raw_sit.
In the case of small discards, the candidates are selected before sync,
while fitrim selects candidates after sync.
So, for small discards, we need to add candidates only just being obsoleted.
Signed-off-by: Jaegeuk Kim
---
If there is not enough available memory, we need to trigger f2fs_sync_fs.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/segment.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/f2fs/segment.c b/fs/f2fs/segment.c
index 42607a6..11e4b5c 100644
--- a/fs/f2fs/segment.c
+++ b/fs/f2fs
Hi Viresh,
Let me explain why I think this is happening.
1. tick_nohz_irq_enter/exit() both get called *only if the cpu is idle*
and receives an interrupt.
2. Commit 2a16fc93d2c9568e1, cancels programming of tick_sched timer
in its handler, assuming that tick_nohz_irq_exit() will take care of
pr
On Thu, Dec 11, 2014 at 04:00:30PM +0800, Huang Ying wrote:
> FYI, we noticed the below changes on
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git master
> commit 6a7d22008b2294f1dacbc77632a26f2142f2d4b0 ("mm: Fix boot crash with
> f7426b983a6a ("mm: cma: adjust address limit to avo
On Tuesday 16 September 2014 08:46 PM, Alexey Brodkin wrote:
> In case of compilation with "-Wextra" following breakage happens:
> --->---
> fs.c: In function ‘fs__valid_mount’:
> fs.c:76:24: error: comparison between signed and unsigned integer expressions
> [-Werror=sign-compare]
> else if (st
To be future-proof and for better readability the time comparisons are
modified to use time_after() instead of plain, error-prone math.
Signed-off-by: Asaf Vertz
---
drivers/usb/host/max3421-hcd.c |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/drivers/usb/host/max3421
Hi,
Am 14.12.2014 um 20:19 schrieb Marek Vasut:
> On Sunday, December 14, 2014 at 06:16:17 PM, Stefan Wahren wrote:
>>> [...]
>>>
>>> Also, it might be a good idea to zap the 0x3f mask and use HEX and DEC
>>> numbers consistently, but this is an idea for another patch.
>> Yes.
>>
>> Btw i hope thi
On Wed, Dec 10, 2014 at 5:07 PM, Jonathan Richardson
wrote:
> If config is called when the pwm is disabled and there is nothing to do,
> the while loop to calculate duty cycle and period doesn't need to be
> done. The function now just returns if the pwm state is disabled.
It doesn't
Hi all,
Please do not add any code destined for v3.20 to your linux-next included
trees/branches until after v3.19-rc1 is released.
Changes since 20141212:
The tip tree gained a conflict against the pm tree.
The rcu tree lost its build failure.
The driver-core tree gained conflicts against Lin
Hi Linus,
This is the main drm pull, as explained this was queued behind arm soc and
iommu, the diffstat seems confused which worries me always, but I've git pull'ed
this tree into yours and gotten a minor conflict in mm/hugetlb.c, which is
easily solved. The -mm changes from the AMD HSA driver
4/cyclic_netperf-performance-300s-200%-SCTP_STREAM-x86_64-rhel-HEAD-057b16997d77a23a4dd2b8e8a9bd56656afac86d-0.yaml"
dequeue_time: 2014-12-14 08:50:11.387688351 +08:00
job_state: finished
loadavg: 0.16 0.22 0.14 2/526 13068
start_time: '1418518283'
end_time: '1418518586'
vers
On Monday 15 December 2014 05:31 AM, Michael Ellerman wrote:
> On Sun, 2014-12-14 at 17:22 +0530, Shreyas B Prabhu wrote:
>> On Sunday 14 December 2014 03:35 PM, Michael Ellerman wrote:
diff --git a/arch/powerpc/platforms/powernv/subcore.h
b/arch/powerpc/platforms/powernv/subcore.h
>>>
On Mon, 15 Dec 2014 00:12:18 +0100, Robert Jarzmik wrote:
> As the interrupt handling was transferred to the cottula driver, make
> the switch in lubbock platform code.
As the pxa25x itself is named Cotulla, the 'cottula' doesn't look like
a good name for FPGA irq driver.
>
> Signed-off-by: Rob
> -Original Message-
> From: Jeremiah Mahler [mailto:jmmah...@gmail.com]
> Sent: Wednesday, December 10, 2014 6:10 PM
> To: KY Srinivasan
> Cc: gre...@linuxfoundation.org; linux-kernel@vger.kernel.org;
> de...@linuxdriverproject.org; o...@aepfle.de; a...@canonical.com;
> jasow...@redhat.c
FYI, we noticed the below changes on
commit 05bfb65f52cbdabe26ebb629959416a6cffb034d ("sched: Remove a wake_affine()
condition")
testbox/testcase/testparams: ivb42/thrulay/performance-300s
afdeee0510db918b 05bfb65f52cbdabe26ebb62995
--
%s
On Mon, Dec 15, 2014 at 09:29:55AM +1100, Stephen Rothwell wrote:
> Hi Michael,
>
> Just wondering if all those commits added to the vhost
> (git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git#linux-next)
> tree today are really destined for v3.19.
Most of them fix static analysis warnin
On 12/13/2014 11:51 PM, Manfred Spraul wrote:
> Hi,
>
> On 12/04/2014 12:25 AM, Andrew Morton wrote:
>> On Wed, 03 Dec 2014 15:41:21 +0300 Andrey Ryabinin
>> wrote:
>>
>>> Use the 'unsigned long' type for 'zero' variable to fix this.
>>> Changing type to 'unsigned long' shouldn't affect any othe
On Fri, Dec 12, 2014 at 09:41:11PM +0200, Laurent Pinchart wrote:
> (Resend, as the message doesn't seem to have made it to the mailing lists)
>
> On Thursday 11 December 2014 01:16:31 Kuninori Morimoto wrote:
> > > > On Mon, Dec 08, 2014 at 11:20:44PM +0530, Vinod Koul wrote:
> > > > > On Mon, De
On Sun, Dec 14, 2014 at 08:20:13PM -0500, Sasha Levin wrote:
> On 12/14/2014 07:11 PM, Paul E. McKenney wrote:
> >> Does it depend on anything not currently in -next? My build fails with
> >> >
> >> > kernel/rcu/tree.c: In function ‘rcu_report_qs_rdp’:
> >> > kernel/rcu/tree.c:2099:6: error: ‘stru
Jeremiah,
Thanks for your review and comments.
I have updated v15 based on your comments and suggestions.
Could you help review again please.
Thank you very much,
Dudley
> -Original Message-
> From: linux-input-ow...@vger.kernel.org
> [mailto:linux-input-ow...@vger.kernel.org] On Behalf
Hi Andrew,
After merging the akpm-current tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
mm/oom_kill.c:257:20: error: redefinition of 'task_will_free_mem'
static inline bool task_will_free_mem(struct task_struct *task)
^
In file included from /scra
On 12/12/14 18:10, Steve Capper wrote:
On 12 December 2014 at 22:42, David Long wrote:
On 12/10/14 11:38, Steve Capper wrote:
On Tue, Dec 09, 2014 at 09:27:18AM -0500, David Long wrote:
On 12/09/14 08:33, Steve Capper wrote:
On Thu, Dec 04, 2014 at 08:53:03PM +0900, Masami Hiramatsu wrote
Add acpi device tree supported.
acpi device id "CYAP" is for old gen3 trackpad devices.
acpi device id "CYAP0001" is for new gen5 trackpad devices.
TEST=test on Chromebooks.
Signed-off-by: Dudley Du
---
drivers/input/mouse/cyapa.c | 13 +
1 file changed, 13 insertions(+)
diff --
Add read baseline function supported for gen3 trackpad device,
it can be used through sysfs baseline interface.
TEST=test on Chromebooks.
Signed-off-by: Dudley Du
---
drivers/input/mouse/cyapa_gen3.c | 71
1 file changed, 71 insertions(+)
diff --git a/dr
Add read baseline function supported for gen5 trackpad device,
it can be used through sysfs baseline interface.
TEST=test on Chromebooks.
Signed-off-by: Dudley Du
---
drivers/input/mouse/cyapa.h | 2 +
drivers/input/mouse/cyapa_gen5.c | 621 +++
2 files
Add force re-calibrate function supported for gen5 trackpad device,
it can be used through sysfs calibrate interface.
TEST=test on Chromebooks.
Signed-off-by: Dudley Du
---
drivers/input/mouse/cyapa_gen5.c | 65
1 file changed, 65 insertions(+)
diff --gi
Add force re-calibrate function supported for gen3 trackpad device,
it can be used through sysfs calibrate interface.
TEST=test on Chromebooks.
Signed-off-by: Dudley Du
---
drivers/input/mouse/cyapa_gen3.c | 58
1 file changed, 58 insertions(+)
diff --gi
Add firmware image update function supported for gen5 trackpad device,
it can be used through sysfs update_fw interface.
TEST=test on Chromebooks.
Signed-off-by: Dudley Du
---
drivers/input/mouse/Kconfig | 1 +
drivers/input/mouse/cyapa_gen5.c | 292 ++-
Add runtime_suspend_scanrate_ms power management interfaces in device's
power group, so users or applications can control the runtime power
management strategy of trackpad device as their requirements.
TEST=test on Chromebooks.
Signed-off-by: Dudley Du
---
drivers/input/mouse/cyapa.c | 171 +
Add firmware image update function supported for gen3 trackpad device,
it can be used through sysfs update_fw interface.
TEST=test on Chromebooks.
Signed-off-by: Dudley Du
---
drivers/input/mouse/cyapa_gen3.c | 284 +++
1 file changed, 284 insertions(+)
diff
Add device's basic control and features supported in cyapa driver through
sysfs file system interfaces. These interfaces are commonly used in
pre- and after production, for trackpad device state checking, managing
and firmware image updating.
These interfaces including mode, firmware_version and pr
Add suspend_scanrate_ms power management interfaces in device's
power group, so users or applications can control the power management
strategy of trackpad device as their requirements.
TEST=test on Chromebooks.
Signed-off-by: Dudley Du
---
drivers/input/mouse/cyapa.c | 111 +
Based on the cyapa core, add the gen5 trackpad device's basic functions
supported, so gen5 trackpad device can work with kernel input system.
And also based on the state parse interface, the cyapa driver can
automatically determine the attached is gen3 or gen5 protocol trackpad
device, then set the
In order to support multiple different chipsets and communication protocols
trackpad devices in one cyapa driver, the new cyapa driver is re-designed
with one cyapa driver core and multiple device specific functions component.
The cyapa driver core is contained in this patch, it supplies basic func
Replace calls for smp_processor_id() to get_cpu() to get the CPU ID of
the current CPU. In these instances, there is no correctness issue with
regards to preemption, we just need the current CPU ID.
Signed-off-by: K. Y. Srinivasan
---
drivers/hv/channel_mgmt.c |4 +++-
drivers/hv/connection.
V15 patches have below updates, details of other updates see history list:
1) Fix all warning errors of sparse tool when running with "make C=1".
2) Change variable name "unique_str" to "product_id" for clearer meanings.
This patch series is aimed to re-design the cyapa driver to support
old gen3
On Fri, Dec 12, 2014 at 10:38 PM, Dinh Nguyen wrote:
>> +
>> +#include
>> +#include
>> +#include
>> +#include
>> +#include
>> +#include
>> +#include
>> +#include
>
> Alphabetize the headers.
Okay.
>> +static int altera_mbox_startup_sender(struct mbox_chan *chan)
>> +{
>> + int ret;
On Fri, Dec 12, 2014 at 02:17:28PM +0100, Robert Baldyga wrote:
> As usb function drivers assumes that all usb request will be completed
> before function unbind call, we should supply such behavior. In some
> cases ep_disable() won't kill all request effectively, because some
> IN requests can be
On Sun, Dec 14, 2014 at 09:27:00PM -0800, Omar Sandoval wrote:
> As with the generic blockdev code, kernel pages shouldn't be dirtied by
> the direct I/O path.
This really asks for an inlined helper (iter_is_bvec(iter) or something like
that)
--
To unsubscribe from this list: send the line "unsubs
On Sun, Dec 14, 2014 at 09:26:57PM -0800, Omar Sandoval wrote:
> The rw argument to direct_IO has some ill-defined semantics. Some
> filesystems (e.g., ext4, FAT) decide whether they're doing a write with
> rw == WRITE, but others (e.g., XFS) check rw & WRITE. Let's set a good
> example in the swap
Ask patch submitters to avoid sending non-critical patches when the
merge window is open. This basically extends the net-next policy in
netdev-FAQ.txt to the entire kernel.
Suggested-by: Thomas Gleixner
Signed-off-by: Kevin Cernekee
---
Documentation/development-process/5.Posting | 9 +
Give submitters a rough idea of how long to wait before reposting, to
help avoid situations where a series is reposted before the original
submission is fully reviewed.
Suggested-by: Thomas Gleixner
Signed-off-by: Kevin Cernekee
---
Documentation/development-process/6.Followthrough | 5 -
1
Currently the checklist does not provide an indication of appropriate
times to send patches; add a brief note on the topic.
Signed-off-by: Kevin Cernekee
---
Documentation/SubmitChecklist | 5 +
1 file changed, 5 insertions(+)
diff --git a/Documentation/SubmitChecklist b/Documentation/Submi
This has been a recurring source of confusion for the new submitters who
I've helped; let's see if adding a small illustration improves the
situation.
Signed-off-by: Kevin Cernekee
---
Documentation/development-process/5.Posting | 16
1 file changed, 16 insertions(+)
diff --git
This patch series amends the kernel development process to reduce the
load on key maintainers during peak periods, by discouraging the submission
of non-urgent patches while the merge window is open.
Original discussion here:
https://lkml.org/lkml/2014/12/12/772
(As a non-subsystem-maintainer I
--
Attention User;
Your email Quota is almost exceeded. Starting from December 15th, we are
migrating to new email interface. So we are currently doing a
maintenance on our server. Please, click the link below to Enter and
update your account and avoid losing your inbox.
http://www.jakkies.c
(2014/12/13 8:10), Steve Capper wrote:
> On 12 December 2014 at 22:42, David Long wrote:
>> On 12/10/14 11:38, Steve Capper wrote:
>>>
>>> On Tue, Dec 09, 2014 at 09:27:18AM -0500, David Long wrote:
On 12/09/14 08:33, Steve Capper wrote:
>
> On Thu, Dec 04, 2014 at 08:53:03PM +09
On Sun, Dec 14, 2014 at 09:47:26PM -0800, Linus Torvalds wrote:
> so it's always in __do_page_fault, but at sometimes it has gotten into
> handle_mm_fault too. So it really really looks like it is taking an
> endless stream of page faults on that "xsaveq" instruction. Presumably
> the page fau
On Sun, 14 Dec 2014 17:39:36 -0500 Benjamin LaHaise wrote:
> How about the documentation/comment updates below?
lgtm.
> ...
>
> +/* aio_ring_remap()
> + * Called when th aio event ring is being relocated within the process'
"the"
> + * address space. The primary purpose is to update the
On Sun, Dec 14, 2014 at 4:38 PM, Linus Torvalds
wrote:
>
> Can anybody make sense of that backtrace, keeping in mind that we're
> looking for some kind of endless loop where we don't make progress?
So looking at all the backtraces, which is kind of messy because
there's some missing data (presuma
(2014/12/15 14:19), Lai Jiangshan wrote:
On 12/15/2014 12:04 PM, Kamezawa Hiroyuki wrote:
(2014/12/15 12:34), Lai Jiangshan wrote:
On 12/15/2014 10:55 AM, Kamezawa Hiroyuki wrote:
(2014/12/15 11:48), Lai Jiangshan wrote:
On 12/15/2014 10:20 AM, Kamezawa Hiroyuki wrote:
(2014/12/15 11:12), La
On Mon, Nov 17, 2014 at 07:48:17AM -0800, Christoph Hellwig wrote:
> With the new iov_iter infrastructure that supprots direct I/O to kernel
> pages please get rid of the ->readpage hack first. I'm still utterly
> disapoined that this crap ever got merged.
Signed-off-by: Omar Sandoval
---
mm/pa
When updating PT_NOTE header size (ie. p_memsz), an overflow issue
happens with the following bogus note entry:
n_namesz = 0x
n_descsz = 0x0
n_type = 0x0
This kind of note entry should be dropped during updating p_memsz. But
because n_namesz is 32bit, after (n_namesz + 3) & (~3), it's o
The generic write code locks i_mutex for a direct_IO. Swap-over-NFS
doesn't grab the mutex because nfs_direct_IO doesn't expect i_mutex to
be held, but most direct_IO implementations do.
Signed-off-by: Omar Sandoval
---
mm/page_io.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/mm/page_
As with the generic blockdev code, kernel pages shouldn't be dirtied by
the direct I/O path.
Signed-off-by: Omar Sandoval
---
fs/nfs/direct.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/fs/nfs/direct.c b/fs/nfs/direct.c
index 9402b96..a502b3f 100644
--- a/fs/nfs/direc
Parameters were added to swap_activate in the same patch series that
introduced it without updating the documentation. Additionally, the
documentation claims that non-existent address space operations
swap_{in,out} are used for swap I/O, but it's (now) direct_IO.
Signed-off-by: Omar Sandoval
---
Signed-off-by: Omar Sandoval
---
fs/splice.c | 7 ++-
include/linux/uio.h | 2 ++
mm/iov_iter.c | 12
mm/page_io.c| 14 +-
4 files changed, 21 insertions(+), 14 deletions(-)
diff --git a/fs/splice.c b/fs/splice.c
index 75c6058..7c7176f 100644
The rw argument to direct_IO has some ill-defined semantics. Some
filesystems (e.g., ext4, FAT) decide whether they're doing a write with
rw == WRITE, but others (e.g., XFS) check rw & WRITE. Let's set a good
example in the swap file code and say ITER_BVEC belongs in
iov_iter->flags but not in rw.
Hi, everyone,
This patch series contains all of the non-BTRFS changes that I've made
as a part of implementing swap file support on BTRFS. The BTRFS parts of
that series (https://lkml.org/lkml/2014/12/9/718) are still undergoing
development, and the non-BTRFS changes now outnumber those within BTR
Reads through the iov_iter infrastructure for kernel pages shouldn't be
dirtied by the direct I/O code.
This is based on Dave Kleikamp's and Ming Lei's previously posted
patches.
Cc: Ming Lei
Acked-by: Dave Kleikamp
Signed-off-by: Omar Sandoval
---
fs/direct-io.c | 8 +---
1 file changed,
The generic callers of direct_IO lock i_mutex before doing a write. NFS
doesn't use the generic write code, so it doesn't follow this
convention. This is now a problem because the interface introduced for
swap-over-NFS calls direct_IO for a write without holding i_mutex, but
other implementations o
On 12/13/2014 01:12 AM, Tejun Heo wrote:
> On Fri, Dec 12, 2014 at 06:19:51PM +0800, Lai Jiangshan wrote:
>> wq_numa_init() will quit directly on some bonkers cases without freeing the
>> memory. Add the missing cleanup code.
>>
>> Cc: Tejun Heo
>> Cc: Yasuaki Ishimatsu
>> Cc: "Gu, Zheng"
>> Cc
On 12/12/2014 11:48 PM, Boris Ostrovsky wrote:
On 12/11/2014 01:04 PM, Juergen Gross wrote:
diff --git a/scripts/xen-hypercalls.sh b/scripts/xen-hypercalls.sh
new file mode 100644
index 000..e6447b7
--- /dev/null
+++ b/scripts/xen-hypercalls.sh
@@ -0,0 +1,11 @@
+#!/bin/sh
+out="$1"
+shift
+i
On 12/14/2014 06:07 AM, 허종만 wrote:
>
> Hi,
>
> My Linux virtual machine on (Windows) VMWare workstation 10 can't boot with
> following commit.
>
> commit bd809af16e3ab1f8d55b3e2928c47c67e2a865d2
> Author: Juergen Gross
> Date: Mon Nov 3 14:02:03 2014 +0100
>
> x86: Enable PAT to use ca
On 12/15/2014 12:04 PM, Kamezawa Hiroyuki wrote:
> (2014/12/15 12:34), Lai Jiangshan wrote:
>> On 12/15/2014 10:55 AM, Kamezawa Hiroyuki wrote:
>>> (2014/12/15 11:48), Lai Jiangshan wrote:
On 12/15/2014 10:20 AM, Kamezawa Hiroyuki wrote:
> (2014/12/15 11:12), Lai Jiangshan wrote:
>> On
Hi Greg,
On Sun, 14 Dec 2014 20:35:06 -0800 Greg KH wrote:
>
> How is this happening, nothing has changed in my trees, did something
> new get added to the watchdog tree?
Yep.
It would have been much easier on me (and maybe Linus) if those "drop
owner assignment from platform_drivers" patches h
From: Magnus Damm
Add r8a7779 specific support for IRLM bit configuration
in the INTC-IRQPIN driver. Without this code we need
special workaround code in arch/arm/mach-shmobile.
The IRLM bit for the INTC hardware exists on various
older SH-based SoCs and is used to select between two
modes for t
On Sat, Dec 13, 2014 at 11:22 PM, Bjorn Andersson wrote:
> On Tue, Nov 4, 2014 at 7:31 AM, Tim Kryger wrote:
>> On Tue, Nov 4, 2014 at 1:00 AM, Alexandre Courbot
>> wrote:
>>> Hi Tim, thanks for your reply!
>>>
>>> On 11/04/2014 02:28 PM, Tim Kryger wrote:
On Mon, Nov 3, 2014 at 7:05
On Mon, Dec 15, 2014 at 02:11:14PM +1100, Stephen Rothwell wrote:
> Hi Greg,
>
> Today's linux-next merge of the driver-core tree got a conflict in
> drivers/watchdog/imx2_wdt.c between commit 6dc21678dbd9 ("watchdog:
> imx2_wdt: Add power management support") from the watchdog tree and
> commit f
On Sun, Dec 14, 2014 at 07:33:12PM -0800, Guenter Roeck wrote:
> On 12/14/2014 12:21 PM, Greg Kroah-Hartman wrote:
> >This is the start of the stable review cycle for the 3.18.1 release.
> >There are 19 patches in this series, all will be posted as a response
> >to this one. If anyone has any issu
On Fri, Dec 12, 2014 at 10:48 PM, Nishanth Menon wrote:
> CONFIG_GENERIC_CPUFREQ_CPU0 disappeared with commit bbcf071969b20f
> ("cpufreq: cpu0: rename driver and internals to 'cpufreq_dt'")
>
> Use the renamed CONFIG_CPUFREQ_DT generic driver. It looks like with
> v3.18-rc1, commit bbcf071969b20f
(2014/12/15 12:34), Lai Jiangshan wrote:
On 12/15/2014 10:55 AM, Kamezawa Hiroyuki wrote:
(2014/12/15 11:48), Lai Jiangshan wrote:
On 12/15/2014 10:20 AM, Kamezawa Hiroyuki wrote:
(2014/12/15 11:12), Lai Jiangshan wrote:
On 12/14/2014 12:38 AM, Kamezawa Hiroyuki wrote:
Although workqueue det
As i know, SECURITY PROTOCOL IN/OUT are support RPMB access for UFS.
On 12/14/14, Tomas Winkler wrote:
> Hi, sorry fore a newbie question.
> What is the current interface for accessing rpmb LUN in a UFS devices.
> For emmc one need to issue a raw mmc ioctl command MMC_IOC_CMD.
>
> Thanks
> Tomas
On Sat, Dec 13, 2014 at 7:16 AM, Silvio Fricke wrote:
> Signed-off-by: Silvio Fricke
> CC: Thomas Gleixner
> CC: Jason Cooper
> CC: Marc Zyngier
> ---
> arch/arm/boot/dts/spear1310-evb.dts | 1 -
> arch/arm/boot/dts/spear1340-evb.dts | 2 --
> arch/arm/boot/dts/spear320-hmi.dts | 3 ---
> 3
Hi Greg,
Today's linux-next merge of the staging tree got a conflict in
drivers/staging/lustre/lustre/llite/llite_lib.c between commit
6a661bd6ffba ("lustre: get rid of playing with ->fs") from the vfs tree
and commit 9c234f6cb4c4 ("drivers: staging: lustre: Fix "'foo* bar'
should be 'foo *bar'" e
Thanks for your remove and comments.
Dudley
> -Original Message-
> From: linux-input-ow...@vger.kernel.org
> [mailto:linux-input-ow...@vger.kernel.org] On Behalf Of Jeremiah Mahler
> Sent: 2014?12?13? 19:16
> To: Dudley Du
> Cc: dmitry.torok...@gmail.com; rydb...@euromail.se; ble...@googl
From: Kuninori Morimoto
Current vendor-prefixes.txt already has "ak" prefix for Asahi Kasei Corp
by ae8c4209af2c(of: Add vendor prefix for Asahi Kasei Corp.)
It went through the appropriate review process. But, almost all
Asahi Kasei chip drivers are using "asahi-kasei" prefix today.
(arch/arm/b
Jeremiah,
Thanks for your information.
I will fix the space check warnning.
Are there any other driver check tools that need to be run?
Thanks.
Dudley
> -Original Message-
> From: linux-input-ow...@vger.kernel.org
> [mailto:linux-input-ow...@vger.kernel.org] On Behalf Of Jeremiah Mahler
This function looks up a PM domain form the provider. This will be
useful to add parent/child domain relationship from the SoC specific
code. The caller of the function must make sure that PM domain provider
is already registered.
Cc: Rafael J. Wysocki
Reviewed-by: Ulf Hansson
Signed-off-by: Ami
Hi,
On Fri, 2014-12-12 at 15:50 +0100, Matthias Brugger wrote:
> This patch adds a driver for the Mediatek SoC integrated
> watchdog. This driver supports watchdog and software reset
> for mt65xx and mt81xx SoCs.
>
> Signed-off-by: Matthias Brugger
> +static int mtk_reset_handler(struct notifie
On 12/14/2014 12:21 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.18.1 release.
There are 19 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be ma
Using the device tree ids for wm8904 codec.
Signed-off-by: Bo Shen
---
Changes in v2: None
arch/arm/boot/dts/at91sam9n12ek.dts | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/at91sam9n12ek.dts
b/arch/arm/boot/dts/at91sam9n12ek.dts
index 13bb24e..9575c0d 1
Excerpts from Ian Munsie's message of 2014-12-08 19:18:01 +1100:
> From: Ian Munsie
>
> If we need to force detach a context (e.g. due to EEH or simply force
> unbinding the driver) we should prevent the userspace contexts from
> being able to access the Problem State Area MMIO region further, wh
On 12/14/2014 12:20 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.17.7 release.
There are 47 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be ma
On 12/15/2014 10:55 AM, Kamezawa Hiroyuki wrote:
> (2014/12/15 11:48), Lai Jiangshan wrote:
>> On 12/15/2014 10:20 AM, Kamezawa Hiroyuki wrote:
>>> (2014/12/15 11:12), Lai Jiangshan wrote:
On 12/14/2014 12:38 AM, Kamezawa Hiroyuki wrote:
> Although workqueue detects relationship between cp
From: Alexander Morozov
Using the wm8904 device tree compatible string.
Signed-off-by: Alexander Morozov
Signed-off-by: Bo Shen
---
Changes in v2: None
arch/arm/boot/dts/sama5d3xmb.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/sama5d3xmb.dtsi
b/
1 - 100 of 454 matches
Mail list logo
