Hi Mark,
(BTW, your mailer is creating some pretty long, unwrapped lines. I've
rewrapped them when quoting below.)
On Fri, Aug 15, 2014 at 08:36:07PM -0700, Mark D Rustad wrote:
> On Aug 15, 2014, at 12:33 PM, Brian Norris
> wrote:
> > On Fri, Aug 15, 2014 at 02:30:49AM -0700, Jeff Kirsher
On Fri, Aug 15, 2014 at 11:38:33AM -0500, Rob Herring wrote:
> Adding Greg...
>
> On Tue, Aug 12, 2014 at 9:30 PM, Stepan Moskovchenko
> wrote:
> > When we parse the device tree and allocate platform
> > devices, the 'name' of the newly-created platform_device
> > is set to point to the 'name'
Brian,
On Aug 15, 2014, at 12:33 PM, Brian Norris wrote:
> Hi,
>
> On Fri, Aug 15, 2014 at 02:30:49AM -0700, Jeff Kirsher wrote:
>> Funny that you bring this up because I have ~60 patches in my queue to
>> resolve several thousand of these warnings. Half of the patches
>> actually resolve
On Fri, Aug 15, 2014 at 04:39:02PM +0200, Oleg Nesterov wrote:
> On 08/15, Luis R. Rodriguez wrote:
> >
> > On Wed, Aug 13, 2014 at 07:51:01PM +0200, Oleg Nesterov wrote:
> > > On 08/12, Luis R. Rodriguez wrote:
> > > >
> > > > +/* To be used by modules which can take over 30 seconds at probe */
>
(2014/08/16 10:38), Wang Nan wrote:
> On 2014/8/15 23:23, Masami Hiramatsu wrote:
>> (2014/08/12 13:56), Wang Nan wrote:
>>> +/* Caller must ensure addr & 3 == 0 */
>>> +static int can_optimize(unsigned long paddr)
>>> +{
>>> + return 1;
>>> +}
>>
>> As we have talked on another thread, we'd
The following changes since commit 263782c1c95bbddbb022dc092fd89a36bb8d5577:
aio: protect reqs_available updates from changes in interrupt handlers
(2014-07-14 13:05:26 -0400)
are available in the git repository at:
git://git.kvack.org/~bcrl/aio-next.git master
for you to fetch changes up
2014-08-15 (금), 21:51 +0200, Jiri Olsa:
> On Fri, Aug 15, 2014 at 10:57:14AM +0900, Namhyung Kim wrote:
> > Hi Jiri,
> >
> > 2014-08-14 (목), 16:10 +0200, Jiri Olsa:
> > > On Thu, Aug 14, 2014 at 03:01:40PM +0900, Namhyung Kim wrote:
> > >
> > > SNIP
> > >
> > > > However, with --children
On 08/15/2014 05:45 PM, Xuetao Guan wrote:
- Guenter Roeck 写道：
On 08/10/2014 08:29 AM, Guenter Roeck wrote:
unicore32 builds fail with
arch/unicore32/kernel/signal.c: In function ‘setup_frame’:
arch/unicore32/kernel/signal.c:257: error:
‘usig’ undeclared (first
On Fri, Aug 15, 2014 at 06:35:25PM -0600, Linus Torvalds wrote:
> Ben,
>
> *please* stop doing this kind of crap.
>
> You're creating fake emails with invalid senders. That's simply not
> acceptable.
...
I'll admit this was my mistake and I should have caught it while reviewing
the emails.
On 2014/8/15 23:23, Masami Hiramatsu wrote:
> (2014/08/12 13:56), Wang Nan wrote:
>> +/* Caller must ensure addr & 3 == 0 */
>> +static int can_optimize(unsigned long paddr)
>> +{
>> +return 1;
>> +}
>
> As we have talked on another thread, we'd better filter-out all stack-pushing
>
On Wed, 13 Aug 2014, Andrew Morton wrote:
> On Tue, 12 Aug 2014 16:46:48 -0700 Davidlohr Bueso wrote:
> > On Wed, 2014-08-13 at 00:52 +0300, Kirill A. Shutemov wrote:
> > > On Tue, Aug 12, 2014 at 10:45:23AM -0700, Davidlohr Bueso wrote:
> > > > The most common way of iterating through the list
This is a cleanup. In function parse_crashkernel_suffix, the
parameter crash_base is not used. So here remove it.
Signed-off-by: Baoquan He
---
kernel/kexec.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/kernel/kexec.c b/kernel/kexec.c
index 0b49a0a..7c3e72a 100644
---
--
POZOR!
=
Vážený užívateľ,
Toto je váš správca webmail. Prosím, byť informovaný, že e-mailový
server bol práve aktualizovaný a váš e-mail musí byť okamžite obnoviť.
Tento proces je udržiavať aktualizované a chránené ako vždy webmail
server.
Kliknite nižšie Ak
- Guenter Roeck 写道：
> On 08/10/2014 08:29 AM, Guenter Roeck wrote:
> > unicore32 builds fail with
> >
> > arch/unicore32/kernel/signal.c: In function ‘setup_frame’:
> > arch/unicore32/kernel/signal.c:257: error:
> > ‘usig’ undeclared (first use in this function)
> >
Ben,
*please* stop doing this kind of crap.
You're creating fake emails with invalid senders. That's simply not acceptable.
The way to specify the author of a commit is *not* to fake the email
sender information, it's to have
From: Real A U Thor
at the top of the message body. NOT by
On Friday, August 15, 2014 10:17:42 AM Markus Gutschke wrote:
> Just wondering if any of you had any other ideas of what I could try
> to help debug this problem?
My theory is that there is a device in your system that we don't have a driver
for, but it had been enumerated as a PNP device before
I have a Business proposal worth $47.1M USD for you.Get back to me for full
details via my private email:xjhushun...@admin.in.th
--
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 at
I have a Business proposal worth $47.1M USD for you.Get back to me for full
details via my private email:xjhushun...@admin.in.th
--
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 at
Hi Everyone,
I'll be traveling through Aug. 24 with limited access to e-mail, so there's
a little chance that I'll be able to process any patches sent to me during
that time.
Kind regards,
Rafael
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message
I have a Business proposal worth $47.1M USD for you.Get back to me for full
details via my private email:xjhushun...@admin.in.th
--
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 at
I have a Business proposal worth $47.1M USD for you.Get back to me for full
details via my private email:xjhushun...@admin.in.th
--
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 at
I have a Business proposal worth $47.1M USD for you.Get back to me for full
details via my private email:xjhushun...@admin.in.th
--
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 at
I have a Business proposal worth $47.1M USD for you.Get back to me for full
details via my private email:xjhushun...@admin.in.th
--
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 at
it/commit/?h=extcon-test=5e519b04db6c5b42f8d8ee246c16903c130b5fd5
>
linux-next of 20140815 still has this build error.
Please get this patch into linux-next.
Thanks.
>
> Best Regards,
> Chanwoo Choi
>
> On 08/13/2014 04:22 PM, Randy Dunlap wrote:
>> From: Randy Dunlap
>>
>> Fix bu
On Fri, Aug 15, 2014 at 11:48:05PM +0530, Hema Prathaban wrote:
> This patch fixes the following warning using checkpatch.pl
> WARNING: Prefer [subsystem eg: netdev]_warn([subsystem]dev, ... then
> dev_warn(dev, ... then pr_warn(... to printk(KERN_WARNING ...
>
> Signed-off-by: Hema Prathaban
>
On 8/15/2014 3:43 AM, Will Deacon wrote:
On Wed, Aug 13, 2014 at 02:11:09AM +0100, Rohit Vaswani wrote:
Currently, the CPU_STARTING notifiers would observe an incorrect sibling
mask since the notifier chain is called before the topology masks are updated
for the new cpu.
Update the topology
Good day Friend,
I am Cedric Lizin,Managing Director of Barclays Bank in United Arab
Emirates .I write you this proposal in good faith hoping that I will
rely on you in a business transaction that require absolute
confidentiality and of great interest and benefit to our both
families.
In
The latest feature release Git v2.1.0 is now available at the
usual places.
The tarballs are found at:
https://www.kernel.org/pub/software/scm/git/
The following public repositories all have a copy of the 'v2.1.0'
tag and the 'master' branch that the tag points at:
url =
On Tue, Jul 22, 2014 at 07:16:15PM +0200, Stephen Warren wrote:
> On 07/15/2014 09:24 AM, Peter De Schrijver wrote:
> > Just continue initializing clocks if there's an error on one of them. This
> > is useful if there's a mistake in the inittable, because the system could
> > hang if
* Tony Lindgren [140815 14:10]:
> * Sebastian Andrzej Siewior [140815 10:46]:
> > This patch provides a 8250-core based UART driver for the internal OMAP
> > UART. The long term goal is to provide the same functionality as the
> > current OMAP uart driver and DMA support.
> > I tried to merge
> Additional driver specific
> +data should be passed in the appropriate _DSM (ACPI Section 9.14.1) method or
> +_DSD (ACPI Section 6.2.5).
Re: _DSD
Yes.
Re: _DSM
No, not if it can be handled by _DSD.
cheers,
Len Brown, Intel Open Source Technology Center
--
To unsubscribe from this list:
On Fri, Aug 15, 2014 at 04:26:01PM +0200, Oleg Nesterov wrote:
> On 08/15, Frederic Weisbecker wrote:
> >
> > 2014-08-14 16:39 GMT+02:00 Oleg Nesterov :
> > > On 08/14, Frederic Weisbecker wrote:
> > >>
> > >> I mean the read side doesn't use a lock with seqlocks. It's only made
> > >> of barriers
On Fri, Aug 15, 2014 at 07:19:41AM -0700, Tim Kryger wrote:
> That is a little different from my suggestion where the constraints
> check is skipped when the regulator output is fixed. It effectively
> does this now when the regulator itself provides the fixed voltage.
> However, the checks
From: "J. German Rivera"
Signed-off-by: J. German Rivera
---
MAINTAINERS |8
1 file changed, 8 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 7e2eb4c..eb8597d 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -3841,6 +3841,14 @@ S: Maintained
F:
> I verified that CPU freq requests were taken by reading out the PERF_STATUS
> register.
Don't use the x86 PERF_STATUS register -- it will not tell you what
you want to know.
If you want to see the actual frequency, you need to watch how many
cycles elapse per a known time interval,
which is
On Fri, Aug 15, 2014 at 11:46:49PM +0200, Stephen Warren wrote:
> On 08/15/2014 03:34 PM, Peter De Schrijver wrote:
> > On Fri, Aug 15, 2014 at 09:45:46PM +0200, Peter De Schrijver wrote:
> >> On Fri, Aug 15, 2014 at 08:07:01PM +0200, Stephen Warren wrote:
> > However, the new code sets the
From: "J. German Rivera"
Platform device driver that sets up the basic bus infrastructure
for the fsl-mc bus type, including support for adding/removing
fsl-mc devices, register/unregister of fsl-mc drivers, and bus
match support to bind devices to drivers.
Signed-off-by: J. German Rivera
---
From: "J. German Rivera"
A DPRC (Data Path Resource Container) is an isolation device
that contains a set of DPAA networking devices to be
assigned to an isolation domain (e.g., a virtual machine).
Signed-off-by: J. German Rivera
---
drivers/bus/fsl-mc/Makefile |3 +-
This patch series introduces Linux support for the Freescale
Management Complex (fsl-mc) hardware.
The fsl-mc is a hardware resource manager that manages specialized
hardware objects used in network-oriented packet processing
applications. After the fsl-mc block is enabled, pools of hardware
From: "J. German Rivera"
APIs to access the Management Complex (MC) hardware
module of Freescale LS2 SoCs. This patch includes
APIs to check the MC firmware version and to manipulate
DPRC objects in the MC.
Signed-off-by: J. German Rivera
---
drivers/bus/fsl-mc/dpmng.c | 93 +
From: "J. German Rivera"
Signed-off-by: J. German Rivera
---
MAINTAINERS |8
1 file changed, 8 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 7e2eb4c..eb8597d 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -3841,6 +3841,14 @@ S: Maintained
F:
The Linux team at Intel did not implement ACPI CPPC support
because we see no benefit to it over the native hardware interface on x86.
cheers,
Len Brown
Intel Open Source Technology Center
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
From: "J. German Rivera"
APIs to access the Management Complex (MC) hardware
module of Freescale LS2 SoCs. This patch includes
APIs to check the MC firmware version and to manipulate
DPRC objects in the MC.
Signed-off-by: J. German Rivera
---
drivers/bus/fsl-mc/dpmng.c | 93 +
From: "J. German Rivera"
A DPRC (Data Path Resource Container) is an isolation device
that contains a set of DPAA networking devices to be
assigned to an isolation domain (e.g., a virtual machine).
Signed-off-by: J. German Rivera
---
drivers/bus/fsl-mc/Makefile |3 +-
This patch series introduces Linux support for the Freescale
Management Complex (fsl-mc) hardware.
The fsl-mc is a hardware resource manager that manages specialized
hardware objects used in network-oriented packet processing
applications. After the fsl-mc block is enabled, pools of hardware
From: "J. German Rivera"
Platform device driver that sets up the basic bus infrastructure
for the fsl-mc bus type, including support for adding/removing
fsl-mc devices, register/unregister of fsl-mc drivers, and bus
match support to bind devices to drivers.
Signed-off-by: J. German Rivera
---
I think we need to let the dirty node pages remain in the page cache instead
of rewriting them in their places.
So, after done with successful recovery, write_checkpoint will flush all of them
through the normal write path.
Through this, we can avoid potential error cases in terms of block
The init_inode_metadata calls truncate_blocks when error is occurred.
The callers holds f2fs_lock_op, so we should not call it again in
truncate_blocks.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/data.c | 2 +-
fs/f2fs/dir.c| 2 +-
fs/f2fs/f2fs.h | 2 +-
fs/f2fs/file.c | 13
Any checkpoint should not be done during the core roll-forward procedure.
Especially, it includes error cases too.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/recovery.c | 8
1 file changed, 8 insertions(+)
diff --git a/fs/f2fs/recovery.c b/fs/f2fs/recovery.c
index 7ca7aad..d36ef35 100644
This patch adds WARN_ON when f2fs_bug_on is disable to see kernel messages.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/f2fs.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/f2fs/f2fs.h b/fs/f2fs/f2fs.h
index 2d009ae..2723b2d 100644
--- a/fs/f2fs/f2fs.h
+++ b/fs/f2fs/f2fs.h
On 08/15/2014 02:34 PM, atull wrote:
Hello,
I am interested in adding functionality to be able to gate power supplies
going through a ltc2978. I see that there is a hwmon driver already
existing (hwmon/pmbus/ltc2978.c). I see some of the other hwmon drivers
have MFD's. It looks like this ltc
Change log from v1:
o relocate F2FS_SET_SB_DIRT to avoid unnecessary checkpoints
The generic_shutdown_super calls sync_filesystem, evict_inode, and then
f2fs_put_super. In f2fs_evict_inode, we remain some dirty inode information
so we should release them at f2fs_put_super.
But normally, it's
Hi Linus,
Please pull these idle power patches.
two Intel-platform-specific updates to intel_idle,
and a cosmetic tweak to the turbostat utility.
thanks!
Len Brown, Intel Open Source Technology Center
The following changes since commit 19583ca584d6f574384e17fe7613dfaeadcdc4a6:
Linux 3.16
Hello,
I am interested in adding functionality to be able to gate power supplies
going through a ltc2978. I see that there is a hwmon driver already
existing (hwmon/pmbus/ltc2978.c). I see some of the other hwmon drivers
have MFD's. It looks like this ltc driver would need a MFD and a
Hi Chao,
On Thu, Aug 14, 2014 at 10:57:10AM +0800, Chao Yu wrote:
> Hi Jaegeuk,
>
> > -Original Message-
> > From: Jaegeuk Kim [mailto:jaeg...@kernel.org]
> > Sent: Wednesday, August 13, 2014 3:49 AM
> > To: linux-kernel@vger.kernel.org; linux-fsde...@vger.kernel.org;
> >
Here's a variant using the even-odd speedup:
(Feel free to add my S-o-b if you use it.)
/*
* This implements Brent & Kung's "even-odd" variant of the binary GCD
* algorithm. (Often attributed to Stein, but as Knith has noted, appears
* a first-century Chinese math text.)
*
* First, find
On Wed, 2014-08-13 at 12:10 +0800, Zhang Zhen wrote:
> Currently memory-hotplug has two limits:
> 1. If the memory block is in ZONE_NORMAL, you can change it to
> ZONE_MOVABLE, but this memory block must be adjacent to ZONE_MOVABLE.
> 2. If the memory block is in ZONE_MOVABLE, you can change it to
On 08/15/2014 03:34 PM, Peter De Schrijver wrote:
On Fri, Aug 15, 2014 at 09:45:46PM +0200, Peter De Schrijver wrote:
On Fri, Aug 15, 2014 at 08:07:01PM +0200, Stephen Warren wrote:
However, the new code sets the clock rate after the clock is prepared. I
think the rate should be set first,
On Fri, Aug 15, 2014 at 09:45:46PM +0200, Peter De Schrijver wrote:
> On Fri, Aug 15, 2014 at 08:07:01PM +0200, Stephen Warren wrote:
> > >> However, the new code sets the clock rate after the clock is prepared. I
> > >> think the rate should be set first, then the clock prepared. While this
> >
On Fri, Aug 15, 2014 at 04:16:01PM -0400, George Spelvin wrote:
> What I'd like is a better way to automatically configure "divide is
> slow" from an architecture.
So the usual thing and have arch/*/Kconfig select the fancy one if it
doesn't have a hardware divide instruction.
For instance:
Commit-ID: fb21b84e7f809ef04b1e5aed5d463cf0d4866638
Gitweb: http://git.kernel.org/tip/fb21b84e7f809ef04b1e5aed5d463cf0d4866638
Author: Stefan Bader
AuthorDate: Fri, 15 Aug 2014 10:57:46 +0200
Committer: H. Peter Anvin
CommitDate: Fri, 15 Aug 2014 13:45:32 -0700
x86_32, entry: Clean up
(apparently I hit "reply" instead of "reply all" sometime back, sorry
for that. Readding ccs)
On Fri, Aug 15, 2014 at 7:35 PM, Steven Noonan wrote:
> On Fri, Aug 15, 2014 at 04:03:08PM +0200, Andreas Noever wrote:
>> On Fri, Aug 15, 2014 at 2:48 PM, Steven Noonan wrote:
>> > On Fri, Aug 15,
* Sebastian Andrzej Siewior [140815 10:46]:
> This patch provides a 8250-core based UART driver for the internal OMAP
> UART. The long term goal is to provide the same functionality as the
> current OMAP uart driver and DMA support.
> I tried to merge omap-serial code together with the 8250-core
* Sebastian Andrzej Siewior [140815 11:13]:
> +#ifdef CONFIG_SERIAL_8250_DMA
> + if (pdev->dev.of_node) {
> + /*
> + * Oh DMA support. If there are no DMA properties in the DT then
> + * we will fall back to a generic DMA channel which does not
> +
* Sebastian Andrzej Siewior [140815 12:16]:
> On 08/15/2014 08:17 PM, Lennart Sorensen wrote:
>
> > Are you saying that with the new driver you have to respond to the RX
> > irq faster than before to avoid overflows? It is not quite clear.
>
> Yes. The irq fires 46 bytes giving you 16 bytes
On 08/15/2014 09:33 PM, Lennart Sorensen wrote:
>> On the other hand if you use DMA then it can handle transfers > 64bytes
>> in one go and you can start transfers while the FIFO is not completely
>> empty.
>
> You can dma more than the fifo size?
Yes. The UART asserts the DMA line as long as
Quoting Andy Lutomirski (l...@amacapital.net):
> On Fri, Aug 15, 2014 at 12:37 PM, Serge Hallyn
> wrote:
> > Quoting Andy Lutomirski (l...@amacapital.net):
> >> On Fri, Aug 15, 2014 at 12:05 PM, Serge Hallyn
> >> wrote:
> >> > Quoting Andy Lutomirski (l...@amacapital.net):
> >> >> Currently,
Quoting Andy Lutomirski (l...@amacapital.net):
> Currently, creating a new mount (as opposed to bindmount) in a
> non-root userns will implicitly set nodev unless the fs is devpts.
> Something like this will be necessary for file systems that allow
> the mounter to create device nodes without
This one is most likely harmless but best to be safe. Applied to
percpu/for-3.17-fixes.
Thanks.
-- 8< --
>From 849f5169097e1ba35b90ac9df76b5bb6f9c0aabd Mon Sep 17 00:00:00 2001
From: Tejun Heo
Date: Fri, 15 Aug 2014 16:06:10 -0400
If pcpu_map_pages() fails midway, it unmaps the already
> So I looked at wikipedia (I wasn't aware of this algorithm, clever
> though), and am still somewhat puzzled by your 'r'.
>
> What's 'wrong' with their iterative version, or what's better about your
> 'r' stuff?
I need to look more carefully, but it looks nifty.
Basically, it's avoiding the
Fix for a sneaky bug which has been there for many years. Applied to
percpu/for-3.17-fixes.
Thanks.
-- 8< --
>From f0d279654dea22b7a6ad34b9334aee80cda62cde Mon Sep 17 00:00:00 2001
From: Tejun Heo
Date: Fri, 15 Aug 2014 16:06:06 -0400
When pcpu_alloc_pages() fails midway,
From: Rik van Riel
Oleg pointed out that wait_task_zombie adds a task's usage statistics
to the parent's signal struct, but the task's own signal struct should
also propagate the statistics at exit time.
This allows thread_group_cputime(reaped_zombie) to get the statistics
after
From: Rik van Riel
The functions task_cputime_adjusted and thread_group_cputime_adjusted
can be called locklessly, as well as concurrently on many different CPUs.
This can occasionally lead to the utime and stime reported by times(), and
other syscalls like it, going backward. The cause for
From: Rik van Riel
Both times() and clock_gettime(CLOCK_PROCESS_CPUTIME_ID) have scalability
issues on large systems, due to both functions being serialized with a
lock.
The lock protects against reporting a wrong value, due to a thread in the
task group exiting, its statistics reporting up to
Thanks to the feedback from Oleg, Peter, Mike, and Frederic,
I seem to have a patch series that manages to do times()
locklessly, and apparently correctly.
Oleg points out that the monotonicity alone is not enough of a
guarantee, but that should probably be attacked separately, since
that issue
On Monday 11 August 2014, gre...@linuxfoundation.org wrote:
> On Mon, Aug 11, 2014 at 04:25:49PM +, Stuart Yoder wrote:
> > Greg,
> >
> > We (Freescale) have a patch series nearly ready to send out
> > for a new bus driver. It's for a block we call the Freescale
> > 'Management Complex'
On Fri, Aug 15, 2014 at 12:37 PM, Serge Hallyn wrote:
> Quoting Andy Lutomirski (l...@amacapital.net):
>> On Fri, Aug 15, 2014 at 12:05 PM, Serge Hallyn
>> wrote:
>> > Quoting Andy Lutomirski (l...@amacapital.net):
>> >> Currently, creating a new mount (as opposed to bindmount) in a
>> >>
On Fri, Aug 15, 2014 at 10:57:14AM +0900, Namhyung Kim wrote:
> Hi Jiri,
>
> 2014-08-14 (목), 16:10 +0200, Jiri Olsa:
> > On Thu, Aug 14, 2014 at 03:01:40PM +0900, Namhyung Kim wrote:
> >
> > SNIP
> >
> > > However, with --children feature added, it now can show all callees of
> > > the entry.
On Fri, Aug 15, 2014 at 08:07:01PM +0200, Stephen Warren wrote:
> >> However, the new code sets the clock rate after the clock is prepared. I
> >> think the rate should be set first, then the clock prepared. While this
> >> likely doesn't apply to the Tegra clock controller, prepare() is allowed
>
Just a note, we do have a couple of bug fixes coming under separate
cover, but they don't have to be part of the merge window
This is a small set of updates which missed the first pull. It's more
msix updates, some iscsi and qla4xxx fixes, we also have some string
null termination fixes a return
Quoting Andy Lutomirski (l...@amacapital.net):
> On Fri, Aug 15, 2014 at 12:05 PM, Serge Hallyn
> wrote:
> > Quoting Andy Lutomirski (l...@amacapital.net):
> >> Currently, creating a new mount (as opposed to bindmount) in a
> >> non-root userns will implicitly set nodev unless the fs is devpts.
On 08/10/2014 08:29 AM, Guenter Roeck wrote:
unicore32 builds fail with
arch/unicore32/kernel/signal.c: In function ‘setup_frame’:
arch/unicore32/kernel/signal.c:257: error:
‘usig’ undeclared (first use in this function)
arch/unicore32/kernel/signal.c:279: error:
On Fri, Aug 15, 2014 at 12:18 PM, Andy Lutomirski wrote:
>>
>> clang/llvm has no problem with u64 :)
>> This bpf_context struct for tracing is trying to answer the question:
>> 'what's the most convenient way to access tracepoint arguments
>> from a script'.
>> When kernel code has something
On Thu, Aug 07, 2014 at 06:18:34PM -0700, Davidlohr Bueso wrote:
> On Tue, 2014-08-05 at 10:42 -0700, Davidlohr Bueso wrote:
> > On Tue, 2014-08-05 at 15:04 +0200, Geert Uytterhoeven wrote:
> > > It looks like you forgot to update frv? It's been failing on -next since
> > > a
> > > few days:
>
On Fri, Aug 15, 2014 at 09:27:59PM +0200, Sebastian Andrzej Siewior wrote:
> If you want to change this to reduce the gap, then you have first
> change 8250 core code. Currently it waits until the shift register is
> empty.
Oh the 8250 normally works this way? I didn't know that.
> On the other
Hi,
On Fri, Aug 15, 2014 at 02:30:49AM -0700, Jeff Kirsher wrote:
> Funny that you bring this up because I have ~60 patches in my queue to
> resolve several thousand of these warnings. Half of the patches
> actually resolve warnings that can be resolved and the other half
> implement compiler
On Fri, Aug 15, 2014 at 12:29 PM, Alexei Starovoitov wrote:
> On Fri, Aug 15, 2014 at 12:20 PM, Andy Lutomirski wrote:
I don't think that fixing this should be a prerequisite for merging,
since the risk is so small. Nonetheless, it would be nice. (This
family of attacks has
On Fri, 2014-08-15 at 12:25 -0700, Christoph Hellwig wrote:
> On Thu, Aug 14, 2014 at 10:47:08AM -0700, James Bottomley wrote:
> > So this is a bit late to get through linux-next and into a pull request.
> > I was planning on sending the final pull tomorrow (in case Linus planned
> > a surprise
On Fri, Aug 15, 2014 at 03:23:01PM -0400, Paul Gortmaker wrote:
> --- /dev/null
> +++ b/include/linux/compiler-gcc5.h
> @@ -0,0 +1,52 @@
> +#ifndef __LINUX_COMPILER_H
> +#error "Please don't include directly, include
> instead."
> +#endif
> +
> +#define __used
On Fri, Aug 15, 2014 at 12:20 PM, Andy Lutomirski wrote:
>>>
>>> I don't think that fixing this should be a prerequisite for merging,
>>> since the risk is so small. Nonetheless, it would be nice. (This
>>> family of attacks has lead to several root vulnerabilities in the
>>> past.)
>>
>> Ok. I
On 08/15/2014 08:37 PM, Lennart Sorensen wrote:
> On Fri, Aug 15, 2014 at 07:42:33PM +0200, Sebastian Andrzej Siewior wrote:
>> This patch provides a 8250-core based UART driver for the internal OMAP
>> UART. The long term goal is to provide the same functionality as the
>> current OMAP uart
On Fri, Aug 15, 2014 at 11:49 AM, Rusty Russell wrote:
> Andy Lutomirski writes:
>> The commit
>>
>> 4982223e51e8 module: set nx before marking module MODULE_STATE_COMING.
>>
>> introduced a regression: if a module fails to parse its arguments or
>> if mod_sysfs_setup fails, then the
On 08/15/2014 12:22 PM, Christoph Hellwig wrote:
On Fri, Aug 15, 2014 at 12:34:22PM -0600, Jens Axboe wrote:
On 2014-08-15 12:22, Guenter Roeck wrote:
ping ... the problem fixed by this patch still affects the upstream kernel
(v3.16-11383-gc9d2642) as well as -next (20140815).
James, could
in place, what essentially amounts to what will be v3.17-rc1
(in a couple days) builds and boots defconfig on an older Dell dual
core box without any oops or WARN or similar:
$ cat /proc/version
Linux version 3.16.0-11383-gc9d26423e56c (paul@yow-pgortmak-d2) (gcc version
5.0.0 20140815 (experiment
On Thu, Aug 14, 2014 at 10:47:08AM -0700, James Bottomley wrote:
> So this is a bit late to get through linux-next and into a pull request.
> I was planning on sending the final pull tomorrow (in case Linus planned
> a surprise early release). Can we redo some of these as bug fixes and
> send
The following changes since commit c9d26423e56ce1ab4d786f92aebecf859d419293:
Merge tag 'pm+acpi-3.17-rc1-2' of
git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm (2014-08-14
18:13:46 -0600)
are available in the git repository at:
Andy Lutomirski writes:
> The commit
>
> 4982223e51e8 module: set nx before marking module MODULE_STATE_COMING.
>
> introduced a regression: if a module fails to parse its arguments or
> if mod_sysfs_setup fails, then the module's memory will be freed
> while still read-only. Anything that
kpark3...@gmail.com writes:
> From: Sahara
>
> Although there are many obs_kernel_param and its names are
> earlyprintk and also EARLY_PRINTK is also enabled, we could not
> see the early_printk output properly until now. This patch
> considers earlycon as well as earlyprintk.
Hmm, the initial
On Fri, Aug 15, 2014 at 12:34:22PM -0600, Jens Axboe wrote:
> On 2014-08-15 12:22, Guenter Roeck wrote:
>> ping ... the problem fixed by this patch still affects the upstream kernel
>> (v3.16-11383-gc9d2642) as well as -next (20140815).
>
> James, could you upstream this
On Fri, Aug 15, 2014 at 12:16 PM, Alexei Starovoitov wrote:
> On Fri, Aug 15, 2014 at 12:02 PM, Andy Lutomirski wrote:
>>>
>>> correct. eBPF program would be using 8-byte read on 64-bit kernel
>>> and 4-byte read on 32-bit kernel. Same with access to ptrace fields
>>> and pretty much all other
1 - 100 of 1024 matches
Mail list logo
