On Fri, 2014-05-30 at 14:35 +0200, Rafael J. Wysocki wrote:
> From: Zhang Rui
>
> Because of the growing demand for enumerating ACPI devices to
> platform bus, change the code to enumerate ACPI device objects to
> platform bus by default. Namely, create platform devices for the
> ACPI device
[ Please don't top post. ]
On Fri, May 30, 2014 at 06:22:55PM -0700, H. Peter Anvin wrote:
> On May 30, 2014 6:14:50 PM PDT, Dave Chinner wrote:
> >On Fri, May 30, 2014 at 05:41:14PM -0700, H. Peter Anvin wrote:
> >> On 05/30/2014 05:37 PM, Dave Chinner wrote:
> >> >
> >> > IOWs, the
On Fri, 30 May 2014 22:31:20 -0600 Daniel Dressler
wrote:
> From: danieru
>
> Following Greg Kroah-Hartman's newbie guide to hacking
> the linux kernel this patch addresses only coding style
> issues.
>
> Binder still has many too-long lines but I'm worried
> doing too much work in a single
Hi Alexander,
> The reasoning to do this is the following:
>
> - If a timeout occurs, the HCI-communication is broken afterwards and the
> dongle isn't usable anymore.
> - If it works after e.g. waiting 4s everyone is still happy but if it
> just breaks after only waiting 2s nothing is gained.
Hi Alexander,
> I assume the timeout for processing HCI commands was originally intended to
> detect hung bluetooth devices and should not include the time needed locally
> to handle the response to an HCI command. That is important because the time
> needed locally (by the kernel or even
On 05/29/2014 08:46 PM, Manfred Spraul wrote:
> Hi all,
>
> a) If we increase SHMMAX/SHMALL, then it makes sense to
>increase MSGMNI, too.
>And: This allows to remove the automatic scaling (~300 lines)
>
> b) We can also increase SEMMSL, SEMMNI and SEMOPM
>
> c) I think it would make
Hi Heinrich,
On 05/27/2014 09:32 PM, Heinrich Schuchardt wrote:
> On 27.05.2014 19:25, Jeff Smith wrote:
>> inotify's behavior concerning events from removed watches (they do
>> happen) and watch descriptor reuse (beyond my knowledge) is currently
>> undocumented.
>>
>> Although it mimics a
Hello, Jens.
On Fri, May 30, 2014 at 06:48:54PM -0600, Jens Axboe wrote:
> What I really like about the implementation is, as Tejun highlights, that
> the algorithm is detailed and characterized. Nobody ever wrote any detailed
> documentation on CFQ - I think the closest is a talk I gave at LCA
On Mon, 26 May 2014, David Herrmann wrote:
>
> (CC migrate.c committers)
>
> On Tue, May 20, 2014 at 12:11 AM, Hugh Dickins wrote:
> > On Mon, 19 May 2014, Jan Kara wrote:
> >> On Mon 19-05-14 13:44:25, David Herrmann wrote:
> >> > On Thu, May 15, 2014 at 12:35 AM, Hugh Dickins wrote:
> >> > >
From: danieru
Following Greg Kroah-Hartman's newbie guide to hacking
the linux kernel this patch addresses only coding style
issues.
Binder still has many too-long lines but I'm worried
doing too much work in a single patch is unfair to the
reviewers. So this patch address 20% of the file's
On Fri, May 30, 2014 at 03:56:44PM +1000, Scott Weir wrote:
> On Wed, May 28, 2014 at 02:30:27PM -0700, Greg KH wrote:
> > On Wed, May 28, 2014 at 06:52:51PM +1000, Scott Weir wrote:
> > > This patch corrects coding style issue:
> > > WARNING: Missing a black line after declarations
> > >
> > >
On Fri, May 30, 2014 at 11:41:01AM -0500, Kumar Gala wrote:
> The following changes since commit 5d144e36b7c51612922fa05d37ff3a869261cc82:
>
> soc: qcom: Add GSBI driver (2014-05-23 11:38:04 -0500)
>
> are available in the git repository at:
>
>
On Fri, May 30, 2014 at 08:08:42PM -0700, Olof Johansson wrote:
> On Fri, May 30, 2014 at 4:57 PM, Greg KH wrote:
> > On Fri, May 30, 2014 at 11:41:01AM -0500, Kumar Gala wrote:
> >> The following changes since commit
> >> 5d144e36b7c51612922fa05d37ff3a869261cc82:
> >>
> >> soc: qcom: Add GSBI
On 05/30/2014 06:28 PM, Mike Turquette wrote:
> Quoting Alex Elder (2014-05-30 13:53:02)
>> Use a counter rather than a Boolean to track whether write access to
>> a CCU has been enabled or not. This will allow more than one of
>> these requests to be nested.
>>
>> Note that __ccu_write_enable()
On 05/30/2014 06:37 PM, Mike Turquette wrote:
> Quoting Alex Elder (2014-05-30 13:53:04)
>> +static int kona_clk_prepare(struct clk_hw *hw)
>> {
>> + struct kona_clk *bcm_clk = to_kona_clk(hw);
>> + struct ccu_data *ccu = bcm_clk->ccu;
>> + unsigned long flags;
>> + int
On Sat, May 31, 2014 at 04:56:34AM +0200, Sune Mølgaard wrote:
> Hi Greg, and thank you for correcting me!
>
> Greg KH wrote:
> [snip]
> > Not true at all.
>
> I trust you to know enough to be correct, but as we speak, I have at
> least 3 pieces of hardware, whose (out-of-tree) drivers regularly
Commit-ID: 8ff925e10f2c72680918b95173ef4f8bb982d59e
Gitweb: http://git.kernel.org/tip/8ff925e10f2c72680918b95173ef4f8bb982d59e
Author: Fenghua Yu
AuthorDate: Fri, 30 May 2014 14:59:24 -0700
Committer: H. Peter Anvin
CommitDate: Fri, 30 May 2014 17:12:41 -0700
x86/xsaves: Clean up code
Commit-ID: c9e5a5a7034146493386d985ff432aed8059929a
Gitweb: http://git.kernel.org/tip/c9e5a5a7034146493386d985ff432aed8059929a
Author: H. Peter Anvin
AuthorDate: Fri, 30 May 2014 08:19:21 -0700
Committer: H. Peter Anvin
CommitDate: Fri, 30 May 2014 08:19:21 -0700
x86/xsave: Make it
On Fri, May 30, 2014 at 11:43:13AM -0500, Kumar Gala wrote:
> The following changes since commit 87cfb00d666cca3abf36f755279cde1b27b9c377:
>
> ARM: qcom: Select PINCTRL by default for ARCH_QCOM (2014-05-22 11:50:42
> -0500)
>
> are available in the git repository at:
>
>
On Fri, May 30, 2014 at 11:42:25AM -0500, Kumar Gala wrote:
> The following changes since commit f604759ec025e21d0c29a6d0addd53bbc60eb12e:
>
> ARM: config: Update msm_defconfig (2014-05-22 11:18:56 -0500)
>
> are available in the git repository at:
>
>
On Fri, May 30, 2014 at 11:38:13AM -0500, Kumar Gala wrote:
> The following changes since commit 08f9234ad6b0b8bc51046346eabf5b92e631e62a:
>
> soc: qcom: Add device tree binding for GSBI (2014-05-23 11:38:53 -0500)
>
> are available in the git repository at:
>
>
Commit-ID: add4eed0a2abea3951206f504330ee5daf8c178a
Gitweb: http://git.kernel.org/tip/add4eed0a2abea3951206f504330ee5daf8c178a
Author: Andy Lutomirski
AuthorDate: Fri, 30 May 2014 08:48:49 -0700
Committer: H. Peter Anvin
CommitDate: Fri, 30 May 2014 16:58:43 -0700
x86/vdso, build: Fix
Commit-ID: e002e99ea4b07c8446d8e1ca892c60f44630643e
Gitweb: http://git.kernel.org/tip/e002e99ea4b07c8446d8e1ca892c60f44630643e
Author: H. Peter Anvin
AuthorDate: Fri, 30 May 2014 17:03:22 -0700
Committer: H. Peter Anvin
CommitDate: Fri, 30 May 2014 17:03:22 -0700
x86/vdso, build: Make
Commit-ID: 011561837dad082a92c0537db2d134e66419c6ad
Gitweb: http://git.kernel.org/tip/011561837dad082a92c0537db2d134e66419c6ad
Author: Andy Lutomirski
AuthorDate: Fri, 30 May 2014 08:48:48 -0700
Committer: H. Peter Anvin
CommitDate: Fri, 30 May 2014 16:58:39 -0700
x86/vdso, build:
On Fri, May 30, 2014 at 4:57 PM, Greg KH wrote:
> On Fri, May 30, 2014 at 11:41:01AM -0500, Kumar Gala wrote:
>> The following changes since commit 5d144e36b7c51612922fa05d37ff3a869261cc82:
>>
>> soc: qcom: Add GSBI driver (2014-05-23 11:38:04 -0500)
>>
>> are available in the git repository
>From 357d4ba36284eee4c2a99085450a9039735767c6 Mon Sep 17 00:00:00 2001
From: Tetsuo Handa
Date: Sat, 31 May 2014 10:22:17 +0900
Subject: [PATCH 5/5] gpu/drm/ttm: Pass GFP flags in order to avoid deadlock.
Commit 7dc19d5a "drivers: convert shrinkers to new count/scan API" added
deadlock warnings
>From d960cdf1e1c91172b86ab9517e576e5fb7e71785 Mon Sep 17 00:00:00 2001
From: Tetsuo Handa
Date: Sat, 31 May 2014 10:05:02 +0900
Subject: [PATCH 4/5] gpu/drm/ttm: Fix possible stack overflow by recursive
shrinker calls.
While ttm_dma_pool_shrink_scan() tries to take mutex before doing
On Sat, May 31, 2014 at 04:04:05AM +0200, Sune Mølgaard wrote:
>
> As a user first, and only secondly a developer, I'd like my HW to work,
> and finding fully supported gear can still be hard if not impossible,
> but I imagine that if we had a central place to list deprecations (and,
> possibly,
>From 4e8d1a83629c5966bfd401c5f2187355624194f2 Mon Sep 17 00:00:00 2001
From: Tetsuo Handa
Date: Sat, 31 May 2014 09:59:44 +0900
Subject: [PATCH 3/5] gpu/drm/ttm: Use mutex_trylock() to avoid deadlock inside
shrinker functions.
I can observe that RHEL7 environment stalls with 100% CPU usage
>From 19927a63c5d2dcda467373c31d810be42e40e190 Mon Sep 17 00:00:00 2001
From: Tetsuo Handa
Date: Sat, 31 May 2014 09:47:02 +0900
Subject: [PATCH 2/5] gpu/drm/ttm: Choose a pool to shrink correctly in
ttm_dma_pool_shrink_scan().
We can use "unsigned int" instead of "atomic_t" by updating
>From c1af6a76f8566d049d3cf24635a43b4a83a6 Mon Sep 17 00:00:00 2001
From: Tetsuo Handa
Date: Sat, 31 May 2014 09:39:22 +0900
Subject: [PATCH 1/5] gpu/drm/ttm: Fix possible division by 0 in
ttm_dma_pool_shrink_scan().
list_empty(&_manager->pools) being false before taking _manager->lock
does
Hi Greg, and thank you for correcting me!
Greg KH wrote:
[snip]
> Not true at all.
I trust you to know enough to be correct, but as we speak, I have at
least 3 pieces of hardware, whose (out-of-tree) drivers regularly fail
to compile come a new rc1. I usually manage to find or create a patch,
On 2014/5/30 17:28, Lee Jones wrote:
>> +static const struct i2c_device_id intel_soc_pmic_i2c_id[] = {
>> +{"INT33FD:00", (kernel_ulong_t)_soc_pmic_config_crc},
>> +{ }
>> +};
>> +MODULE_DEVICE_TABLE(i2c, intel_soc_pmic_i2c_id);
>> +
>> +static struct
On Wed, 28 May 2014 11:43:16 +0200 (CEST)
Thomas Gleixner wrote:
[snip]
> >
> > In the above case, could we go 1 step further and avoid taking the pi
> > lock as well?
[snip]
>
> Indeed.
>
>
Are you going to repost this patch? I'd like to review that one instead
of this one if you're
On Sat, May 31, 2014 at 04:04:05AM +0200, Sune Mølgaard wrote:
> Dear list,
>
> In order to keep this non-code RFC brief, allow me to list a few
> observations and then a proposal, that I shall be happy to engage in,
> but for which I'd like a bit of guidance:
>
> 1) System calls get superseded
On Thu, 22 May 2014 03:25:54 -
Thomas Gleixner wrote:
> Add a separate local variable for the boost/deboost logic to make the
> code more readable. Add comments where appropriate.
>
> Signed-off-by: Thomas Gleixner
> ---
> kernel/locking/rtmutex.c | 50
>
Dear list,
In order to keep this non-code RFC brief, allow me to list a few
observations and then a proposal, that I shall be happy to engage in,
but for which I'd like a bit of guidance:
1) System calls get superseded and deprecated on a regular basis
2) Keeping track of deprecations can be
On Thu, 22 May 2014 03:25:50 -
Thomas Gleixner wrote:
> Index: tip/kernel/locking/rtmutex.c
> ===
> --- tip.orig/kernel/locking/rtmutex.c
> +++ tip/kernel/locking/rtmutex.c
> @@ -957,47 +957,53 @@
On 2014-05-28 20:42, Linus Torvalds wrote:
Regardless of whether it is swap or something external queues the
bio on the plug, perhaps we should look at why it's done inline
rather than by kblockd, where it was moved because it was blowing
the stack from schedule():
So it sounds like we need to
On 05/30/2014 08:33 AM, Frederic Weisbecker wrote:
diff --git a/arch/x86/include/asm/debugreg.h b/arch/x86/include/asm/debugreg.h
>index 4b528a9..145b009 100644
>--- a/arch/x86/include/asm/debugreg.h
>+++ b/arch/x86/include/asm/debugreg.h
>@@ -114,5 +114,10 @@ static inline void
On Thu, May 29, 2014 at 9:37 PM, Linus Torvalds
wrote:
>
> It really might be very good to create a "struct alloc_info" that
> contains those shared arguments, and just pass a (const) pointer to
> that around. [ .. ]
>
> Ugh. I think I'll try looking at that tomorrow.
I did look at it, but the
From: Robert Elliott
Eliminate duplicate TRACE_GRAPH_PRINT_xx defines
in trace_functions_graph.c that are already in
trace.h.
Add TRACE_GRAPH_PRINT_IRQS to trace.h, which is
the only one that is missing.
Link:
http://lkml.kernel.org/p/20140520221031.8359.24733.st...@beardog.cce.hp.com
From: Yoshihiro YUNOMAE
Current tracing_saved_cmdlines_read() implementation is naive; It allocates
a large buffer, constructs output data to that buffer for each read
operation, and then copies a portion of the buffer to the user space
buffer. This has several issues such as slow memory
From: Steven Rostedt
trace_printk() is used to debug fast paths within the kernel. Places
that gets called in any context (interrupt or NMI) or thousands of
times a second. Something you do not want to do with a printk().
In order to make it completely lockless as it needs a temporary buffer
to
From: "Steven Rostedt (Red Hat)"
In order to prevent the saved cmdline cache from being filled when
tracing is not active, the comms are only recorded after a trace event
is recorded.
The problem is, a comm can fail to be recorded if the trace_cmdline_lock
is held. That lock is taken via a
From: Robert Elliott
In the function-graph tracer, add a funcgraph_tail option
to print the function name on all } lines, not just
functions whose first line is no longer in the trace
buffer.
If a function calls other traced functions, its total
time appears on its } line. This change allows
From: "Steven Rostedt (Red Hat)"
In order to help benchmark the time tracepoints take, a new config
option is added called CONFIG_TRACEPOINT_BENCHMARK. When this option
is set a tracepoint is created called "benchmark:benchmark_event".
When the tracepoint is enabled, it kicks off a kernel thread
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
for-next
Head SHA1: 676412a37f248205ecadfaddb50e150a44ef2b0c
Robert Elliott (2)
tracing: Eliminate duplicate TRACE_GRAPH_PRINT_xx defines
tracing: Add funcgraph_tail option to print function name after closing
From: "Steven Rostedt (Red Hat)"
With the conversion of the saved_cmdlines output to use seq_read, there
is now a race between accessing the values of the saved_cmdlines and
the writing to them. The trace_cmdline_lock needs to be taken at
the start and stop of the seq calls.
A new
No, not a strawman. Replace with Jan 26, 2038 and you have the same situation.
On May 30, 2014 6:14:50 PM PDT, Dave Chinner wrote:
>On Fri, May 30, 2014 at 05:41:14PM -0700, H. Peter Anvin wrote:
>> On 05/30/2014 05:37 PM, Dave Chinner wrote:
>> >
>> > IOWs, the filesystem has to be able to
On Fri, May 30, 2014 at 05:41:14PM -0700, H. Peter Anvin wrote:
> On 05/30/2014 05:37 PM, Dave Chinner wrote:
> >
> > IOWs, the filesystem has to be able to reject any attempt to set a
> > timestamp that is can't represent on disk otherwise Bad Stuff will
> > happen,
>
> Actually it is
On Fri, May 30, 2014 at 10:01:46PM +0200, Arnd Bergmann wrote:
> tty, usbgadgetfs, configfs and cramfs do not store inode timestamps
> permanently, but they use code that interacts with the VFS inode
> times. In order to change over VFS to a struct inode_time, we
> have to make trivial changes to
On Thu, May 29, 2014 at 07:32:29AM -0700, Guenter Roeck wrote:
> On 05/28/2014 09:36 PM, Greg Kroah-Hartman wrote:
> >This is the start of the stable review cycle for the 3.10.41 release.
> >There are 86 patches in this series, all will be posted as a response
> >to this one. If anyone has any
On Fri, May 30, 2014 at 01:43:08PM -0600, Shuah Khan wrote:
> On 05/29/2014 08:18 AM, Greg Kroah-Hartman wrote:
> >On Thu, May 29, 2014 at 03:59:23PM +1000, NeilBrown wrote:
> >>On Wed, 28 May 2014 21:32:19 -0700 Greg Kroah-Hartman
> >> wrote:
> >>
> >>>This is the start of the stable review cycle
On Fri, May 30, 2014 at 11:41:01AM -0500, Kumar Gala wrote:
> The following changes since commit 5d144e36b7c51612922fa05d37ff3a869261cc82:
>
> soc: qcom: Add GSBI driver (2014-05-23 11:38:04 -0500)
>
> are available in the git repository at:
>
>
On Fri, May 30, 2014 at 01:44:02PM -0600, Shuah Khan wrote:
> On 05/29/2014 08:32 AM, Guenter Roeck wrote:
> >On 05/28/2014 09:36 PM, Greg Kroah-Hartman wrote:
> >>This is the start of the stable review cycle for the 3.10.41 release.
> >>There are 86 patches in this series, all will be posted as a
On Fri, 30 May 2014 23:03:27 +
"Luck, Tony" wrote:
> All of this stuff only applies to server systems - so quibbling over
> a handful of *bytes* in an error record on a system that has tens,
> hundreds or even thousands of *gigabytes* of memory seems
> a bit pointless.
But there's still
From: Himangi Saraogi
Date: Fri, 30 May 2014 21:17:13 +0530
> This patch replaces a comma between expression statements by a semicolon.
>
> A simplified version of the semantic patch that performs this
> transformation is as follows:
...
> Signed-off-by: Himangi Saraogi
> Acked-by: Julia
From: Himangi Saraogi
Date: Fri, 30 May 2014 21:18:12 +0530
> This patch replaces a comma between expression statements by a semicolon.
>
> A simplified version of the semantic patch that performs this
> transformation is as follows:
...
> Signed-off-by: Himangi Saraogi
> Acked-by: Julia
From: Himangi Saraogi
Date: Fri, 30 May 2014 21:16:05 +0530
> This patch replaces a comma between expression statements by a semicolon.
>
> A simplified version of the semantic patch that performs this
> transformation is as follows:
...
> Signed-off-by: Himangi Saraogi
> Acked-by: Julia
On 2014-05-30 10:07, Tejun Heo wrote:
We do have multiple ioscheds but sans for anticipatory which pretty
much has been superceded by cfq, they serve different purposes and I'd
really hate the idea of carrying two mostly similar ioscheds in tree.
AS was removed, and exactly for that reason. So
From: Himangi Saraogi
Date: Fri, 30 May 2014 21:10:48 +0530
> This patch replaces a comma between expression statements by a semicolon.
>
> A simplified version of the semantic patch that performs this
> transformation is as follows:
...
> Signed-off-by: Himangi Saraogi
Applied.
--
To
On 05/30/2014 05:37 PM, Dave Chinner wrote:
>
> IOWs, the filesystem has to be able to reject any attempt to set a
> timestamp that is can't represent on disk otherwise Bad Stuff will
> happen,
Actually it is questionable if it is worse to reject a timestamp or just
let it wrap. Rejecting a
On Sat, May 31, 2014 at 12:30:34AM +0100, Liviu Dudau wrote:
> On Fri, May 30, 2014 at 05:16:52PM -0600, Bjorn Helgaas wrote:
> > On Fri, May 30, 2014 at 5:11 PM, Liviu Dudau wrote:
> > > On Fri, May 30, 2014 at 03:45:05PM -0500, Kumar Gala wrote:
> > >>
> > >> On May 29, 2014, at 8:41 PM, Liviu
We would like to be able to describe PCIe ECAM resources as
IORESOURCE_MEM blocks while distinguish them from standard
memory resources. Add an IORESOURCE_BIT entry for this case.
Signed-off-by: Liviu Dudau
---
include/linux/ioport.h | 1 +
1 file changed, 1 insertion(+)
diff --git
If we have a PCI config space specified in something like a ranges
property we should treat it as memory type resource. Use the
IORESOURCE_ECFG bit to distinguish the config space from standard
IORESOURCE_MEM resources.
Signed-off-by: Kumar Gama
[Updated commit log and added IORESOURCE_ECFG bit]
On Fri, May 30, 2014 at 10:01:35PM +0200, Arnd Bergmann wrote:
> xfs uses unsigned 32-bit seconds for inode timestamps, which will work
> for the next 92 years, but the VFS uses struct timespec for timestamps,
> which is only good until 2038 on 32-bit CPUs.
>
> This gets us one small step closer
From: David Miller
Date: Fri, 30 May 2014 17:21:09 -0700 (PDT)
> From: Paul Bolle
> Date: Tue, 27 May 2014 21:53:44 +0200
>
>> A check for CONFIG_SA1100_CT6001 was added in v2.6.11. But the related
>> Kconfig symbol was never added to the tree. Remove this check and do
>> some related cleaning
Removing the risk of using a non-allocated file resource
Signed-off-by: Rickard Strandqvist
---
tools/power/cpupower/bench/parse.c |7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/tools/power/cpupower/bench/parse.c
b/tools/power/cpupower/bench/parse.c
index
From: Paul Bolle
Date: Tue, 27 May 2014 21:53:44 +0200
> A check for CONFIG_SA1100_CT6001 was added in v2.6.11. But the related
> Kconfig symbol was never added to the tree. Remove this check and do
> some related cleaning up.
>
> Signed-off-by: Paul Bolle
Applied to net-next, thanks.
--
To
From: "John W. Linville"
Date: Tue, 27 May 2014 14:12:01 -0400
> Please pull this batch of updates intended for 3.16...
Pulled, thanks a lot John.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info
From: Paul Bolle
Date: Tue, 27 May 2014 17:07:12 +0200
> This preprocessor check is commented out ever since this file was added
> during the v2.3 development cycle. It is unclear what it purpose might
> have been. Whatever it was, it can safely be removed now.
>
> Signed-off-by: Paul Bolle
>
On 05/30/2014 01:34 PM, Andy Lutomirski wrote:
>>
>> GET_LE() then?
>
> Sounds good.
>
> Are you planning on writing the patch?
>
> I think my v2 is good -- the only diff I could find in my image.c
> files and Stephen's was in the alt_xyz output, and I think I fixed
> that in v2.
>
Build
On 05/30/2014 01:24 PM, Jan Kara wrote:
> Now with the attachment... :)
Jan, I suspect that the issue Jet has reported is different from mine.
Your patch (or even removing all of print_PIC() didn't solve the issue
I've reported.
Thanks,
Sasha
--
To unsubscribe from this list: send the line
On Wed, May 28 2014, Joonsoo Kim wrote:
> @@ -1143,10 +1223,15 @@ __rmqueue_fallback(struct zone *zone, int order, int
> start_migratetype)
> static struct page *__rmqueue(struct zone *zone, unsigned int order,
> int migratetype)
> {
> - struct
Instead of ballooning up and down dom0 memory this remaps the existing mfns
that were replaced by the identity map. The reason for this is that the
existing implementation ballooned memory up and and down which caused dom0
to have discontiguous pages. In some cases this resulted in the use of
Quoting Colin King (2014-04-12 10:59:14)
> From: Colin Ian King
>
> commit a183da63 introduced a new error return path that does
> not kfree icst if the kmemdup of desc->params fails.
>
> Signed-off-by: Colin Ian King
Applied to clk-next.
Thanks,
Mike
> ---
>
> On Thu, May 29, 2014 at 05:09:34PM +0900, Gioh Kim wrote:
>> Is IS_ENABLED(CONFIG_CMA) necessary?
>> What about if (migratetype == MIGRATE_MOVABLE && zone->managed_cma_pages) ?
On Fri, May 30 2014, Joonsoo Kim wrote:
> Yes, field, managed_cma_pages exists only if CONFIG_CMA is enabled, so
>
Il giorno 31/mag/2014, alle ore 01:28, Tejun Heo ha scritto:
> Hello,
>
> On Sat, May 31, 2014 at 12:23:01AM +0200, Paolo Valente wrote:
>> I do agree that bfq has essentially the same purpose as cfq. I am
>> not sure that it is what you are proposing, but, in my opinion,
>> since both the
Cleaning up a file resource leak
Signed-off-by: Rickard Strandqvist
---
Documentation/connector/ucon.c |2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/connector/ucon.c b/Documentation/connector/ucon.c
index 8a4da64..f09c6de 100644
--- a/Documentation/connector/ucon.c
+++
Quoting Alex Elder (2014-05-30 13:53:04)
> +static int kona_clk_prepare(struct clk_hw *hw)
> {
> + struct kona_clk *bcm_clk = to_kona_clk(hw);
> + struct ccu_data *ccu = bcm_clk->ccu;
> + unsigned long flags;
> + int ret = 0;
> +
> + flags = ccu_lock(ccu);
> +
Il giorno 30/mag/2014, alle ore 19:09, Vivek Goyal ha
scritto:
> […]
> Instead of just looking at numbers, I am keen on knowing what's the
> fundamental design change which allows this. What is CFQ doing wrong
> which BFQ gets right.
>
I think that Tejun has already highlighted the key
From: Ivan Mikhaylov
Date: Mon, 26 May 2014 22:34:39 +0400
> Aggreagation of version 1-2 because of version 1 can hit
> PLB errors too. If it's not set so we missing events for PLB bits
> and driver can't process those interrupts.
>
> Signed-off-by: Ivan Mikhaylov
Applied.
--
To unsubscribe
From: Ivan Mikhaylov
Date: Mon, 26 May 2014 22:24:17 +0400
> In chips of emac/rgmii b'000' for 0/1 channel isn't suitable which
> resulted in non working network interface in this mode.
>
> Signed-off-by: Ivan Mikhaylov
Applied.
--
To unsubscribe from this list: send the line "unsubscribe
On Fri, May 30, 2014 at 05:16:52PM -0600, Bjorn Helgaas wrote:
> On Fri, May 30, 2014 at 5:11 PM, Liviu Dudau wrote:
> > On Fri, May 30, 2014 at 03:45:05PM -0500, Kumar Gala wrote:
> >>
> >> On May 29, 2014, at 8:41 PM, Liviu Dudau wrote:
> >>
> >> > On Thu, May 29, 2014 at 07:29:31PM -0600,
Hi Linus,
Mostly quiet now,
i915: fixing userspace visiblie issues, all stable marked
radeon: one more pll fix, two crashers, one suspend/resume regression.
Dave.
The following changes since commit c7208164e66f63e3ec1759b98087849286410741:
Linux 3.15-rc7 (2014-05-25 16:06:00 -0700)
are
Hello,
On Sat, May 31, 2014 at 12:23:01AM +0200, Paolo Valente wrote:
> I do agree that bfq has essentially the same purpose as cfq. I am
> not sure that it is what you are proposing, but, in my opinion,
> since both the engine and all the new heuristics of bfq differ from
> those of cfq, a
Quoting Alex Elder (2014-05-30 13:53:02)
> Use a counter rather than a Boolean to track whether write access to
> a CCU has been enabled or not. This will allow more than one of
> these requests to be nested.
>
> Note that __ccu_write_enable() and __ccu_write_disable() calls all
> come in pairs,
From: Benoit Taine
Date: Mon, 26 May 2014 17:21:23 +0200
> This issue was reported by coccicheck using the semantic patch
> at scripts/coccinelle/api/memdup.cocci
>
> Signed-off-by: Benoit Taine
> ---
> Tested by compilation without errors.
Applied to net-next, thank you.
--
To unsubscribe
From: Andrea Adami
This family of chips was long ago supported by the pre-cfi driver.
CFI code tested on several Zaurus SL-5500 (Collie) 2x16 on 32 bit bus.
Function is_LH28F640BF() mimics is_m29ew() from cmdset_0002.c
Buffer write fixes as seen in 2007 patch c/o
Anti Sullin artecdesign.ee>
From: Andrea Adami
This family of chips was long ago supported by the pre-cfi driver.
CFI code tested on several Zaurus SL-5500 (Collie) 2x16 on 32 bit bus.
Function is_LH28F640BF() mimics is_m29ew() from cmdset_0002.c
Buffer write fixes as seen in 2007 patch c/o
Anti Sullin artecdesign.ee>
On Fri, May 30, 2014 at 5:11 PM, Liviu Dudau wrote:
> On Fri, May 30, 2014 at 03:45:05PM -0500, Kumar Gala wrote:
>>
>> On May 29, 2014, at 8:41 PM, Liviu Dudau wrote:
>>
>> > On Thu, May 29, 2014 at 07:29:31PM -0600, Bjorn Helgaas wrote:
>> >> On Thu, May 29, 2014 at 6:56 PM, Liviu Dudau
Replace spaces at beginning of the string with tabs, and replace foo * bar with
foo *bar in a pointer declaration.
Signed-off-by: Thomas Wood
---
This time using linux-next!
drivers/w1/w1_int.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/drivers/w1/w1_int.c
On Fri, May 30, 2014 at 03:45:05PM -0500, Kumar Gala wrote:
>
> On May 29, 2014, at 8:41 PM, Liviu Dudau wrote:
>
> > On Thu, May 29, 2014 at 07:29:31PM -0600, Bjorn Helgaas wrote:
> >> On Thu, May 29, 2014 at 6:56 PM, Liviu Dudau wrote:
> >>> On Thu, May 29, 2014 at 03:51:28PM -0500, Kumar
Hi,
On Sat, 31 May 2014 01:12:08 +0900 jaeg...@kernel.org wrote:
>
> From: Jaegeuk Kim
>
> This patch changes the valid email address to maintain the f2fs file system.
Have you remembered to notify the linux-next maintainer? :-)
> F2FS FILE SYSTEM
> -M: Jaegeuk Kim
> +M: Jaegeuk Kim
pretty much any smartcommands...I was running something that got all
of the smart stats 1x per hour per disk...and this made it crash about
1x per week, if you were pushing the disks hard it appear to make it
even more likely to crash under the smart cmds, removing the commands
took things up to
>> For memory error location, I will utilize type offset to save one
>> more byte, furthermore, I want to drop requestor_id, responder_id
>> and target_id. 1) They are very rare (I've never seen them by now)
>
> My concern is, are we sure we're never going to need them at all? Tony,
> what's your
* Manuel Schölling , 2014-05-30, 15:27:
Add a scrollback buffers for each VGA console. The benefit is that the
scrollback history is not flushed when switching between consoles but
is persistent.
Some people rely on this scrollback flushing as a security feature. Is
there even another way to
Hi Dave,
You'll get piles of those, and you get to rewrite the (x86) dma
implementation to fix them.
There's two parts of the problem:
- We hang onto dma mappings forever, and we don't enforce any
ownership. Actually we can't since our userspace _wants_ to access
some memory ranges while the gpu
From: Himangi Saraogi
Date: Wed, 28 May 2014 19:53:09 +0530
> This patch moves data allocated using kzalloc to managed data allocated
> using devm_kzalloc and cleans now unnecessary kfrees in probe and remove
> functions. Also, linux/device.h is added to make sure the devm_*()
> routine
1 - 100 of 1446 matches
Mail list logo
