On (07/03/13 11:37), Jerome Marchand wrote:
Subject: Re: [PATCH staging-next] zram: protect zram_reset_device() call
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130110
Thunderbird/17.0.2
On 06/26/2013 02:28 PM, Sergey Senozhatsky wrote:
Commit
This patch removes DMAC platform data on r8a7740 and switches to using
device ID data.
Signed-off-by: Guennadi Liakhovetski g.liakhovetski+rene...@gmail.com
---
Simon: this patch should only be applied after DMA driver changes,
otherwise DMA on r8a7740 will be broken. We can delay this patch
This patch adds Device Tree support for the three generic DMA controller
instances on r8a7740 in a DMA multiplexer node.
Signed-off-by: Guennadi Liakhovetski g.liakhovetski+rene...@gmail.com
---
arch/arm/boot/dts/r8a7740.dtsi | 61
On Thu, Jul 11, 2013 at 12:34:49PM +0100, Preeti U Murthy wrote:
Hi Morten,
I have a few quick comments.
On 07/09/2013 10:28 PM, Arjan van de Ven wrote:
On 7/9/2013 8:55 AM, Morten Rasmussen wrote:
Hi,
This patch set is an initial prototype aiming at the overall power-aware
On Fri, 12 Jul 2013, Peter Ujfalusi wrote:
TWL6040 is used only with OMAP4/5 SoCs and they can only boot in in DT mode.
The support for pdata/legacy boot can be removed.
Add TODO comment to the header file that all pdata struct can be removed in
the next merge window (after the sub driver
On Fri, Jul 12, 2013 at 03:26:15PM +0200, Jean Delvare wrote:
Hi Wei, Guenter,
Guenter, thanks for reviewing the previous version of this patch.
Wei, thanks for incorporating review feedback and posting updated
patches so quickly, this is very appreciated, even though I'm too busy
these
On Fri, 12 Jul 2013, Peter Ujfalusi wrote:
To comply with coding style.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
drivers/mfd/twl6040.c | 21 ++---
1 file changed, 10 insertions(+), 11 deletions(-)
It's fine indent using tabs as well as squaring up to
On Fri, 12 Jul 2013, Peter Ujfalusi wrote:
The err: label is not needed we can just return instead of the jump there.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
drivers/mfd/twl6040.c | 14 +-
1 file changed, 5 insertions(+), 9 deletions(-)
Nice little clean-up.
Hi Kevin,
Could you please take a look to the following patch series.
It consists of two patches, which are needed for proper
SmartReflex Interrupt handling.
Based on Linux v3.10. Verified on OMAP4430.
Thank you in advance.
Regards,
Andrii
Nishanth Menon (2):
PM / AVS: SmartReflex: fix
From: Nishanth Menon n...@ti.com
With the current interrupt disable sequence, we disable IRQENABLE
followed by clearing of IRQSTATUS. With this sequence, we see, at
times CORE domain does not hit OFF mode during cold boot because
SR modules(Core/IVA/MPU domains) are stuck 'in transition'. This
is
On Thu, Jul 11, 2013 at 03:20:29PM -0700, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.0.86 release.
There are 8 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.
Em 12-07-2013 10:41, Borislav Petkov escreveu:
On Fri, Jul 12, 2013 at 10:04:28AM +0200, Markus Trippelsdorf wrote:
Mauro said he will fix this in the coming weeks:
http://article.gmane.org/gmane.linux.kernel/1522719
Here's a possible fix which works fine here. Markus, if you could verify
From: Nishanth Menon n...@ti.com
At times with bad SR configurations, especially during silicon bring-ups,
we could get continuous spurious interrupts which end up hanging the
platform in the form of an ISR call for status bits that are
automatically enabled by the hardware without any software
Signed-off-by: Alexandru Juncu al...@rosedu.org
---
drivers/video/matrox/matroxfb_base.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/video/matrox/matroxfb_base.c
b/drivers/video/matrox/matroxfb_base.c
index 401a56e..2456529 100644
---
On 07/08/2013 06:26 PM, Mark Brown wrote:
On Mon, Jul 08, 2013 at 05:48:14PM +0200, Michal Simek wrote:
On 07/08/2013 04:49 PM, Mark Brown wrote:
Is it definitely safe to leave the IRQ hanging around after the master
has been freed - there's no possibility of a late error interrupt or
On 07/12/2013 06:30 AM, Gustavo Padovan wrote:
Hi Gianluca,
* Gianluca Anzolin gianl...@sottospazio.it [2013-07-09 10:35:35 +0200]:
Hello,
In linux 3.10 in the file drivers/tty/tty_port.c the function
tty_port_tty_hangup may leak a tty reference:
struct tty_struct *tty =
On Thu, Jul 11, 2013 at 03:44:55PM -0700, Greg Kroah-Hartman wrote:
On Thu, Jul 11, 2013 at 06:29:35PM -0400, Dave Jones wrote:
On Thu, Jul 11, 2013 at 03:01:17PM -0700, Greg Kroah-Hartman wrote:
rant
I'm sitting on top of over 170 more patches that have been marked for
the
On Fri, Jul 12, 2013 at 10:57:41AM -0300, Mauro Carvalho Chehab wrote:
This will be overriding the content of the static var mc_bus every for
every new memory controller. Are you sure that bus.name is only used
on register, or if its contents is stored somewhere?
bus_register does
On 2013.07.12 at 15:41 +0200, Borislav Petkov wrote:
On Fri, Jul 12, 2013 at 10:04:28AM +0200, Markus Trippelsdorf wrote:
Mauro said he will fix this in the coming weeks:
http://article.gmane.org/gmane.linux.kernel/1522719
Here's a possible fix which works fine here. Markus, if you
The prev_state is defined as long which is 4 bytes long
on 32-bit x86. Changing the check against sizeof(long).
Signed-off-by: Jiri Olsa jo...@redhat.com
Cc: Corey Ashford cjash...@linux.vnet.ibm.com
Cc: Frederic Weisbecker fweis...@gmail.com
Cc: Namhyung Kim namhy...@kernel.org
Cc: Paul
Hi Guenter,
On Fri, 12 Jul 2013 06:50:00 -0700, Guenter Roeck wrote:
On Fri, Jul 12, 2013 at 03:26:15PM +0200, Jean Delvare wrote:
One thing I am a little worried about (but maybe I'm wrong) is that I
seem to understand you want to register every LM90-like chip as both a
hwmon device and
Thanks for the heads-up, Ingo.
On Fri, Jul 12, 2013 at 02:14:20PM +0200, Ingo Molnar wrote:
Jul 10 12:20:19 turing-police kernel: [0.021583] DMAR:[fault reason 06]
PTE Read access is not set
Now I have 3 extra messages talking about handling a fault status. lspci
says 00:1f.2
On Fri, Jul 12, 2013 at 04:28:44PM +0200, Markus Trippelsdorf wrote:
Yes, it's working fine here, too. Thanks Boris.
Thanks Markus!
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
--
To unsubscribe from this list: send the line unsubscribe linux-kernel
On Fri, 12 Jul 2013, Yanmin Zhang wrote:
On Thu, 2013-07-11 at 16:03 +0800, shuox@intel.com wrote:
From: Liu ShuoX shuox@intel.com
In shutdown progress, system is possible to do power transition
(such as suspend-to-ram) in parallel. It is unreasonable. So,
fixes it by adding a
On Fri, Jul 12, 2013 at 04:30:34PM +0200, Jean Delvare wrote:
Hi Guenter,
On Fri, 12 Jul 2013 06:50:00 -0700, Guenter Roeck wrote:
On Fri, Jul 12, 2013 at 03:26:15PM +0200, Jean Delvare wrote:
One thing I am a little worried about (but maybe I'm wrong) is that I
seem to understand you
On Fri, Jul 12, 2013 at 12:54:15PM +0800, Robin Gong wrote:
Add pfuze100 regulator driver.
This looks mostly good. A few small issues below but nothing major.
+enum pfuze_id {
+ PFUZE_ID_PFUZE100,
+ PFUZE_ID_INVALID,
+};
+struct pfuze_chip {
Missing blank line here - there are a
On Fri, Jul 12, 2013 at 04:46:29PM +0300, Sergey Senozhatsky wrote:
On (07/03/13 11:37), Jerome Marchand wrote:
Subject: Re: [PATCH staging-next] zram: protect zram_reset_device() call
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130110
Thunderbird/17.0.2
On 06/26/2013
On Fri, 2013-07-12 at 09:24 +0900, Yasuaki Ishimatsu wrote:
(2013/07/11 1:47), Toshi Kani wrote:
device-driver_data needs to be cleared when releasing its data,
mem_device, in an error path of acpi_memory_device_add().
Signed-off-by: Toshi Kani toshi.k...@hp.com
---
Reviewed-by:
On Fri, Jul 12, 2013 at 03:56:01PM +0300, Adrian Hunter wrote:
There's events where this isn't a possible location; take PERF_RECORD_MMAP
for
instance; the tail is the complete filename.
PERF_RECORD_MMAP falls in the category I have called non-sample events.
Those events are appended
Hello.
On 07/12/2013 05:43 PM, Guennadi Liakhovetski wrote:
This patch adds Device Tree support for the three generic DMA controller
instances on r8a7740 in a DMA multiplexer node.
Signed-off-by: Guennadi Liakhovetski g.liakhovetski+rene...@gmail.com
---
arch/arm/boot/dts/r8a7740.dtsi
On Thu, Jul 11, 2013 at 03:11:00PM -0700, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.4.53 release.
There are 11 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.
Fixes for 4 cifs bugs, including a reconnect problem, a problem
parsing responses to SMB2 open request, and setting nlink incorrectly
to some servers which don't report it properly on the wire. Also
improves data integrity on reconnect with series from Pavel which adds
durable handle support for
When CONFIG_HAS_DMA isn't enabled, the UDC core gets build errors:
drivers/built-in.o: In function `dma_set_coherent_mask':
include/linux/dma-mapping.h:93: undefined reference to `dma_supported'
include/linux/dma-mapping.h:93: undefined reference to `dma_supported'
drivers/built-in.o: In function
On Fri, Jul 12, 2013 at 10:58:46AM -0400, Benjamin LaHaise wrote:
On Thu, Jul 11, 2013 at 03:11:00PM -0700, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.4.53 release.
There are 11 patches in this series, all will be posted as a response
to this one. If
Webmail actualización
20GB 23GB
Su buzón ha superado el límite de almacenamiento lo establecido por el
administrador y usted no será capaz de recibir nuevos correos hasta
que vuelva a validar. Para revalidar:
On Thu, Jul 11, 2013 at 5:54 PM, Haojian Zhuang
haojian.zhu...@gmail.com wrote:
Well, Daniel Drake spoke up for OLPC. Does that count?
We don't know they used DT on Marvell MMP2/MMP3. So they don't have DTS file
in kernel, we could use both old name new name in driver.
You are listed as one
On Fri, Jul 12, 2013 at 11:47:33AM +0200, Gianluca Anzolin wrote:
Hello,
I'm sorry to bother you again, I'm just pinging to see if you received the
patch or if it got lost in the noise. It fixes a regression introduced in git
commit aa27a094e2c2e
I have another patch for rfcomm tty
Found using coccinelle.
Signed-off-by: Alexandru Juncu al...@rosedu.org
---
drivers/block/nvme-scsi.c | 24
1 file changed, 8 insertions(+), 16 deletions(-)
diff --git a/drivers/block/nvme-scsi.c b/drivers/block/nvme-scsi.c
index 102de2f..4a4ff4e 100644
---
On Fri, Jul 12, 2013 at 7:15 AM, Guenter Roeck li...@roeck-us.net wrote:
I get the impression as soon as we hit -rc1, some maintainers immediately
go into OH SHIT, I CAN'T SEND PATCHES OR LINUS WILL SHOUT AT ME mode.
I agree. But it seems that I need to now start shouting at them :(
Hello Jeff
Thank you for your comments. Please see inline.
On 7/11/2013 9:41 PM, Jeff Moyer wrote:
Tanya Brokhman tlin...@codeaurora.org writes:
When the scheduler reports to the block layer that there is an urgent
request pending, the device driver may decide to stop the transmission
of the
Hi,
On Friday, July 05, 2013 09:29:26 PM Cho KyongHo wrote:
Since acquiring read_lock is not more frequent than write_lock, it is
not beneficial to use rwlock, this commit changes rwlock to spinlock.
This change is not of a fix type and is not required to make the driver
work so it would
Apply for loan at 3% interest rate. Contact us with your requirement via Email;
tenger.gr...@mail.com, for more information. Try us and be convinced
--
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
On Fri, Jul 12, 2013 at 14:14 +0200, Gerhard Sittig wrote:
We shall combine the parts which currently are floating around.
So that others aren't supposed to pick up pieces but instead can
use a series and get something consistent.
Here are the parts that I'm aware of:
- Anatolij's work
On 7/12/2013 5:46 AM, Morten Rasmussen wrote:
I have had a quick look at intel_pstate.c and to me it seems that it can
be turned into a power driver that uses the proposed interface with a
few modifications. intel_pstate.c already has max and min P-state as
well as a current P-state calculated
On 07/11, David Rientjes wrote:
On Wed, 10 Jul 2013, Oleg Nesterov wrote:
+int vma_dup_policy(struct vm_area_struct *src, struct vm_area_struct *dst)
+{
+ struct mempolicy *pol = mpol_dup(vma_policy(src));
+
+ if (IS_ERR(pol))
+ return PTR_ERR(pol);
PTR_ERR() returns
Hi Linus,
On 07/10/2013 11:36 PM, Linus Walleij wrote:
On Thu, Jun 27, 2013 at 4:01 PM, Grygorii Strashko
grygorii.stras...@ti.com wrote:
I think, In the future the OMAP pinctrl configurations would be manged in
more flexible way then now (thanks to pinctrl PM helpers and you;))
- Idle state
On 7/12/2013 5:51 AM, Morten Rasmussen wrote:
On Wed, Jul 10, 2013 at 02:10:59PM +0100, Arjan van de Ven wrote:
On 7/9/2013 8:55 AM, Morten Rasmussen wrote:
Extends the power scheduler capacity management algorithm to handle
frequency scaling and provide basic frequency/P-state selection hints
On 07/12/2013 03:31 AM, Ingo Molnar wrote:
* Dave Jones da...@redhat.com wrote:
On Wed, Jul 10, 2013 at 05:20:15PM +0200, Markus Trippelsdorf wrote:
On 2013.07.10 at 11:13 -0400, Dave Jones wrote:
I get this right after booting..
[ 114.516619] perf samples too long (4262 2500),
On Thu 11-07-13 13:58:32, Jan Kara wrote:
On Thu 11-07-13 12:53:46, Jan Kara wrote:
On Wed 10-07-13 16:12:36, Paul Taysom wrote:
The following commit introduced a 10x regression for
syncing inodes in ext4 with relatime enabled where just
the atime had been modified.
commit
But on x86 you still have a P-state hint for the CPU and the scheduler
could at least hope for more CPU performance. We can make the power
scheduler ask the power driver for an increase or decrease of
performance (as Preeti suggested) and give it the current load as
argument rather than a
On Fri, Jul 12, 2013 at 08:38:52AM -0700, Dave Hansen wrote:
The warning comes from calling perf_sample_event_took(), which is only
called from one place: perf_event_nmi_handler().
So we can be pretty sure that the perf NMI is firing, or at least that
this handler code is running.
On Fri, 2013-07-12 at 08:22 -0700, Linus Torvalds wrote:
Listen to yourself. In fact, there is a damn good solution: don't
mark crap for stable, and don't send crap to me after -rc4.
I tend to hold things off after -rc4 because you scare me more than Greg
does ;-)
Actually, as I consider
Hello kernel experts,
I was wondering if someone has any ideas on this Oops. My analysis must
be incorrect. From what I can tell, this shouldn't have caused a bad
page fault, but it did :).
Here is what I see in the crash dump:
dmesg log shows this:
[ 1053.156266] BUG: unable to handle
On Fri, Jul 12, 2013 at 12:02:45PM +, Rasmus Villemoes wrote:
But isn't the problem the case where dirname does not exist? I.e., the
application has to make sure that /some/where exists and is a directory
before open(/some/where, O_CREAT | O_TMPFILE | O_RDWR, 0666) can be
relied upon to
On Fri, Jul 12, 2013 at 6:48 AM, Eric Van Hensbergen eri...@gmail.com wrote:
It's likely my fault.
This is not a fault.
Duplicate commits happen. It's fine. It's normal, and even expected.
In fact, it's very much something that sometimes happen for *good*
reasons.
Sometimes it's just because
From: Jan Vesely jves...@redhat.com
Export the function so it can be used to predict segment counts
without calling the recalc function. This will be used in the next
patch.
Signed-off-by: Jan Vesely jves...@redhat.com
CC: Alexander Viro v...@zeniv.linux.org.uk
CC: James Bottomley
From: Jan Vesely jves...@redhat.com
The original behavior was to refuse all pages after the maximum number of
segments has been reached. However, some drivers (like st) craft their buffers
to potentially require exactly max segments and multiple pages in the last
segment. This patch modifies the
Hi
These patches modify __bio_add_page to accept pages that extent the last bio
segment. some drivers craft their buffers and rely on this behavior (see
message in patch 2 for details)
jan
v4: whitespace fixes to make checkpatch happy
v3: Use code from __blk_recalc_rq_segments to decide
On 07/12/2013 08:45 AM, Dave Jones wrote:
On Fri, Jul 12, 2013 at 08:38:52AM -0700, Dave Hansen wrote:
Dave, for your case, my suspicion would be that it got turned on
inadvertently, or that we somehow have a bug which bumped up
perf_event.c's 'active_events' and we're running some perf
On Fri, Jul 12, 2013 at 09:10:49AM -0600, Daniel Drake wrote:
On Thu, Jul 11, 2013 at 5:54 PM, Haojian Zhuang
haojian.zhu...@gmail.com wrote:
Well, Daniel Drake spoke up for OLPC. Does that count?
We don't know they used DT on Marvell MMP2/MMP3. So they don't have DTS file
in kernel, we
On Fri, Jul 12, 2013 at 8:47 AM, Steven Rostedt rost...@goodmis.org wrote:
I tend to hold things off after -rc4 because you scare me more than Greg
does ;-)
Have you guys *seen* Greg? The guy is a freakish giant. He *should*
scare you. He might squish you without ever even noticing.
(2013/07/10 20:00), Michael Holzheu wrote:
On Wed, 10 Jul 2013 18:50:18 +0900
HATAYAMA Daisuke d.hatay...@jp.fujitsu.com wrote:
[snip]
(2013/07/10 17:42), Michael Holzheu wrote:
My suggestion is to add the WARN_ONCE() for #ifndef CONFIG_S390. This has the
same
effect as your suggestion for
On Fri, Jul 12, 2013 at 9:57 AM, Jason Cooper ja...@lakedaemon.net wrote:
This also means we should do a patch for stable v3.5+ appending the
mrvl,... string to the drivers that had it removed improperly, as
Daniel discovered. Daniel, since you are probably most familiar (and
most able to
Mark,
Thanks for your kindly review, please see below comments.
On Fri, Jul 12, 2013 at 03:40:37PM +0100, Mark Brown wrote:
On Fri, Jul 12, 2013 at 12:54:15PM +0800, Robin Gong wrote:
Add pfuze100 regulator driver.
This looks mostly good. A few small issues below but nothing
Em Fri, 12 Jul 2013 16:21:06 +0200
Borislav Petkov b...@alien8.de escreveu:
On Fri, Jul 12, 2013 at 10:57:41AM -0300, Mauro Carvalho Chehab wrote:
This will be overriding the content of the static var mc_bus every for
every new memory controller. Are you sure that bus.name is only used
on
On Fri, Jul 12, 2013 at 10:05:45AM -0600, Daniel Drake wrote:
On Fri, Jul 12, 2013 at 9:57 AM, Jason Cooper ja...@lakedaemon.net wrote:
This also means we should do a patch for stable v3.5+ appending the
mrvl,... string to the drivers that had it removed improperly, as
Daniel discovered.
* Linus Torvalds torva...@linux-foundation.org wrote:
On Fri, Jul 12, 2013 at 8:47 AM, Steven Rostedt rost...@goodmis.org wrote:
I tend to hold things off after -rc4 because you scare me more than Greg
does ;-)
Have you guys *seen* Greg? The guy is a freakish giant. He *should*
scare
What would be a reasonable maximum limit for the number of memory
controllers, on a -EX machine?
Westmere-EX has one memory controller per socket ... and there are glueless
systems up to 8 sockets. So 8 there. Not sure if any OEM is building larger
machines with a node controller (SGI? Not
On 07/12/2013 05:08 AM, Ingo Molnar wrote:
Note, there was a second fix posted by Stephane Eranian for
a separate patch which I also botched:
http://lkml.kernel.org/r/20130704223010.GA30625@quad
Both of these fixes need to get pulled in to Linus's tree and
the 3.10 stable tree.
Al Viro v...@zeniv.linux.org.uk writes:
On Fri, Jul 12, 2013 at 12:02:45PM +, Rasmus Villemoes wrote:
But isn't the problem the case where dirname does not exist? I.e., the
application has to make sure that /some/where exists and is a directory
before open(/some/where, O_CREAT |
On 07/10/2013 11:12 PM, Joonsoo Kim wrote:
On Wed, Jul 10, 2013 at 10:38:20PM -0700, Dave Hansen wrote:
You're probably right for small numbers of pages. But, if we're talking
about things that are more than, say, 100 pages (isn't the pcp batch
size clamped to 128 4k pages?) you surely don't
On Fri, Jul 12, 2013 at 12:17 PM, Ingo Molnar mi...@kernel.org wrote:
* Linus Torvalds torva...@linux-foundation.org wrote:
On Fri, Jul 12, 2013 at 8:47 AM, Steven Rostedt rost...@goodmis.org wrote:
I tend to hold things off after -rc4 because you scare me more than Greg
does ;-)
Have
On Fri, Jul 12, 2013 at 12:35 PM, Josh Boyer jwbo...@gmail.com wrote:
On Fri, Jul 12, 2013 at 12:17 PM, Ingo Molnar mi...@kernel.org wrote:
* Linus Torvalds torva...@linux-foundation.org wrote:
On Fri, Jul 12, 2013 at 8:47 AM, Steven Rostedt rost...@goodmis.org wrote:
I tend to hold
On 07/12/2013 11:25 AM, Alexandre Belloni wrote:
Hi,
On 01/07/2013 19:16, Alexandre Belloni wrote:
The mxs LRADC is able to read an internal die temperature sensor. The
temperature has to be calculated from the value read on channel 8 and
channel 9.
To be able to expose the result to
On Fri, 2013-07-12 at 08:55 -0700, Linus Torvalds wrote:
On Fri, Jul 12, 2013 at 8:47 AM, Steven Rostedt rost...@goodmis.org wrote:
I tend to hold things off after -rc4 because you scare me more than Greg
does ;-)
Have you guys *seen* Greg? The guy is a freakish giant. He *should*
scare
On Fri, Jul 12, 2013 at 10:48:21AM -0500, Steve Wise wrote:
So 'movb $0x0,0xe(%rax,%rdx,1)' should be storing 0 into the byte
location:
%rax + 0xe + (%rdx * 1) ==
0x40fc+ 0xe + 0x8808b550 ==
0x8808b5540fce.
That address is readable in the crash dump:
crash
On 7/12/2013 11:48 AM, Dave Jones wrote:
On Fri, Jul 12, 2013 at 10:48:21AM -0500, Steve Wise wrote:
So 'movb $0x0,0xe(%rax,%rdx,1)' should be storing 0 into the byte
location:
%rax + 0xe + (%rdx * 1) ==
0x40fc+ 0xe + 0x8808b550 ==
0x8808b5540fce.
That
`On Fri, Jul 12, 2013 at 8:43 AM, Jan Kara j...@suse.cz wrote:
On Thu 11-07-13 13:58:32, Jan Kara wrote:
On Thu 11-07-13 12:53:46, Jan Kara wrote:
On Wed 10-07-13 16:12:36, Paul Taysom wrote:
The following commit introduced a 10x regression for
syncing inodes in ext4 with relatime
On Fri, Jul 12, 2013 at 11:53:30AM -0500, Steve Wise wrote:
On 7/12/2013 11:48 AM, Dave Jones wrote:
On Fri, Jul 12, 2013 at 10:48:21AM -0500, Steve Wise wrote:
So 'movb $0x0,0xe(%rax,%rdx,1)' should be storing 0 into the byte
location:
%rax + 0xe + (%rdx * 1)
On 07/10/2013 03:08 PM, Oleksandr Kravchenko wrote:
From: Oleksandr Kravchenko o.v.kravche...@globallogic.com
This patch adds IIO driver for APDS9300 ambilent light sensor (ALS).
s/ambilent/ambient/
http://www.avagotech.com/docs/AV02-1077EN
The driver allows to read raw data from ADC
On Fri, Jul 12, 2013 at 08:55:31AM -0700, Dave Hansen wrote:
I mean that somebody turned 'active_events' on without actually wanting
perf to be on. I'd be curious how it got set to something nonzero.
Could you stick a WARN_ONCE() or printk_ratelimit() on the three sites
that modify it?
On Fri, Jul 12, 2013 at 12:35:26PM -0400, Josh Boyer wrote:
On Fri, Jul 12, 2013 at 12:17 PM, Ingo Molnar mi...@kernel.org wrote:
* Linus Torvalds torva...@linux-foundation.org wrote:
On Fri, Jul 12, 2013 at 8:47 AM, Steven Rostedt rost...@goodmis.org
wrote:
I tend to hold things
From: Jens Axboe ax...@kernel.dk
We have officially run out of flags in a 32-bit space. Extend it
to 64-bit even on 32-bit archs.
Signed-off-by: Jens Axboe ax...@kernel.dk
diff --git a/block/blk-core.c b/block/blk-core.c
index 93a18d1..cfa4dd3 100644
--- a/block/blk-core.c
+++
Add support for reinserting a dispatched request back to the
scheduler's internal data structures.
This capability is used by the device driver when it chooses to
interrupt the current request transmission and execute another (more
urgent) pending request. For example: interrupting long write in
When the scheduler reports to the block layer that there is an urgent
request pending, the device driver may decide to stop the transmission
of the current request in order to handle the urgent one. This is done
in order to reduce the latency of an urgent request. For example:
long WRITE may be
This patch add support in block elevator layers for handling
urgent requests. The decision if a request is urgent or not is taken
by the scheduler. Request is marked as urgent in cmd_flags (by the
scheduler) with a new flag - REQ_URGENT.
Urgent request notification is passed to the underlying
On 7/12/2013 12:00 PM, Dave Jones wrote:
On Fri, Jul 12, 2013 at 11:53:30AM -0500, Steve Wise wrote:
On 7/12/2013 11:48 AM, Dave Jones wrote:
On Fri, Jul 12, 2013 at 10:48:21AM -0500, Steve Wise wrote:
So 'movb $0x0,0xe(%rax,%rdx,1)' should be storing 0 into the byte
On 07/11/2013 05:50 PM, Theodore Ts'o wrote:
At least at one point in the past...
And at at least one *other* point in the past, Linus stated that
holding back anything with a Cc: stable waiting for the merge window is
wrong. This would imply that the post-rc5-or-so policy and the stable
On 7/12/13 9:45 AM, Dave Jones wrote:
Here's a fun trick:
trinity -c perf_event_open -C4 -q -l off
Within about a minute, that brings any of my boxes to its knees.
The softlockup detector starts going nuts, and then the box wedges solid.
I tried that in a VM running latest Linus tree. I see
On Fri, Jul 12, 2013 at 12:08:25PM -0500, Steve Wise wrote:
There is no 'Code:' line in the log. I thought about that that too, but
I don't see it dumping the code. The kernel is a SLES11sp1 kernel,
1.6.32.54-0.3-default.
Ask suse is probably your best bet in that case.
[
On Fri, Jul 12, 2013 at 08:28:05AM +0900, Jingoo Han wrote:
On Friday, July 12, 2013 12:41 AM, Thierry Reding wrote:
On Thu, Jul 11, 2013 at 02:49:43PM +0900, Jingoo Han wrote:
[...]
diff --git a/drivers/pci/host/Makefile b/drivers/pci/host/Makefile
[...]
obj-$(CONFIG_PCI_MVEBU) +=
On Fri, Jul 12, 2013 at 11:12:13AM -0600, David Ahern wrote:
On 7/12/13 9:45 AM, Dave Jones wrote:
Here's a fun trick:
trinity -c perf_event_open -C4 -q -l off
Within about a minute, that brings any of my boxes to its knees.
The softlockup detector starts going nuts, and then
On 07/11/2013 04:24 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.10.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
On 07/11/2013 05:19 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.4.53 release.
There are 11 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
On the subject of the stable tree: could we get a standard format for
requesting post-inclusion elevation of patches to stable status? It
isn't all that unusual that the need for -stable is highlighted after a
patch has been included in a maintainer's tree, and rebasing to add
stable metadata
On 07/11/2013 05:44 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.0.86 release.
There are 8 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
On 07/11/2013 07:24 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.9.10 release.
There are 15 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
On Fri, Jul 12, 2013 at 10:20:46AM -0700, H. Peter Anvin wrote:
On the subject of the stable tree: could we get a standard format for
requesting post-inclusion elevation of patches to stable status? It
isn't all that unusual that the need for -stable is highlighted after a
patch has been
On Fri, Jul 12, 2013 at 05:20:29PM +, Shuah Khan wrote:
On 07/11/2013 04:24 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.10.1 release.
There are 19 patches in this series, all will be posted as a response
to this one. If anyone has any issues
On Fri, Jul 12, 2013 at 06:54:43AM -0700, Guenter Roeck wrote:
On Thu, Jul 11, 2013 at 03:20:29PM -0700, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.0.86 release.
There are 8 patches in this series, all will be posted as a response
to this one. If
201 - 300 of 938 matches
Mail list logo
