On Sun, 13 Sep 2015, Shraddha Barke wrote:
>
>
> On Sat, Sep 12, 2015 at 11:07 PM, Julia Lawall
> wrote:
>
>
> On Sat, 12 Sep 2015, Shraddha Barke wrote:
>
> > This patch removes comparisons to true/false values on bool
> variables.
> >
> > Changes in v3-
>
On Sat, Sep 12, 2015 at 11:52 PM, Dmitry Torokhov
wrote:
> On Sat, Sep 12, 2015 at 08:26:18PM +0530, Vaishali Thakkar wrote:
>> Use managed resource functions devm_request_threaded_irq,
>> devm_inpute_allocate_device and devm_kzalloc to simplify
>> error handling. Also, remove use of
This patch removes the commented printk inside else block as
it is not needed.
Signed-off-by: Shraddha Barke
---
drivers/staging/rtl8192u/ieee80211/ieee80211_softmac.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/staging/rtl8192u/ieee80211/ieee80211_softmac.c
During testing of these patches
[PATCH] mmc: pxamci: fix card detect threaded interrupt
[PATCH 1/3] dmaengine: virt-dma: don't always free descriptor upon
completion
I have found unrelated error.
How to reproduce:
1) Remove any SD card
2) No CPLD initial power for card (in
Subject: [PATCH 2/2] UV: NMI: simple dump failover if kdump fails
The ability to trigger a kdump using the system NMI command
was added by
commit 12ba6c990fab ("x86/UV: Add kdump to UV NMI handler")
Author: Mike Travis
Date: Mon Sep 23 16:25:03 2013 -0500
This is useful because
On Wed, Sep 09, 2015 at 01:24:08PM +0100, Matt Fleming wrote:
> On Thu, 27 Aug, at 06:21:44PM, joeyli wrote:
> > On Fri, Aug 21, 2015 at 02:27:53PM +0100, Matt Fleming wrote:
> > > On Tue, 11 Aug, at 02:16:29PM, Lee, Chun-Yi wrote:
> > > > +static int __init init_hibernation_keys(void)
> > > > +{
UV: NMI: insert this_cpu_read accessor function on uv_hub_nmi.
On SGI UV systems a 'power nmi' command from the CMC causes
all processors to drop into uv_handle_nmi(). With the 4.0
kernel this results in
BUG: unable to handle kernel paging request
The bug is caused by the current code
Dne 12.9.2015 v 13:03 Robert Jarzmik napsal(a):
> Petr Cvek writes:
>
> And it is true I have not tested the rootfs special case, where drivers
> are not
> yet initialized (and more specifically gpio and interrupt chip). Your
> backtrace
> should tell me if you fall into
On Wed, Sep 09, 2015 at 01:15:45PM +0100, Matt Fleming wrote:
> On Thu, 27 Aug, at 05:04:52PM, joeyli wrote:
> >
> > The purpose of checking attribute of hibernation key variable is
> > in case someone created a key variable on runtime environment _before_
> > this kernel create boot service
Hi Lee,
You acked this patch. However finally it did not go through other tree
so maybe you could pick it up for 4.4?
If you want I could reabse and resend it.
Best regards,
Krzysztof
2015-08-11 19:09 GMT+09:00 Krzysztof Kozlowski :
>
> On Odroid XU3 board (with S2MPS11 PMIC) the PWRHOLD bit
Hi all,
I'm having some problems trying to work out how to get mdadm to restart
a RAID array after a disk failure. It is refusing to close the array
saying it's in use, and it's refusing to let me start the array again
saying the devices are already part of another array:
$ mdadm --manage
Dne 12.9.2015 v 13:36 Robert Jarzmik napsal(a):
> Add io memory and dma requestor lines to the irda pxa device. This is
> part of the conversion of pxaficp_ir to dmaengine, and to shrink its
> adherence to 'mach' includes.
>
> Signed-off-by: Robert Jarzmik
> Cc: Petr Cvek
> ---
>
Dne 12.9.2015 v 13:45 Robert Jarzmik napsal(a):
> Convert the pxa IRDA driver to readl and writel primitives, and remove
> another set of direct registers access. This leaves only the DMA
> registers access, which will be dealt with dmaengine conversion.
>
> Signed-off-by: Robert Jarzmik
> ---
>
Hi!
I would like you to come and see my latest photos on MyDailyFlog.
Check out:
http://www.mydailyflog.com/go/invite_register/saiprathap/22143969=89
Thanks!
sai sadasivam
~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~
To unsubscribe of this type of email from MyDailyFlog in the future,
On Sat, Sep 12, 2015 at 10:25 AM, Jonathan Corbet wrote:
> On Sat, 12 Sep 2015 01:59:34 -0300
> Diego Viola wrote:
>
>> I really wish the commit message instead said:
>>
>> "GTK+ is an initialism"
>>
>> Can't I change the commit message any longer?
>
> No, you need to consider it set in stone at
So it's been fairly quiet today (which is normal: there tends to be a
small rush of stuff on the last Friday of the merge window is closing,
but weekends tend to calm down), and I decided that I'm not interested
in catering to anything that comes in tomorrow, and I might as well
just close the
On Sat, Sep 12, 2015 at 04:29:06PM -0700, Linus Torvalds wrote:
> On Sat, Sep 12, 2015 at 4:00 PM, Chris Mason wrote:
> >
> > I did the plain revert as well, just to have a baseline.
>
> Ahh, I ended up not expecting you to get this done until after rc1 was
> out, so I in the meantime just
On Sat, Sep 12, 2015 at 4:00 PM, Chris Mason wrote:
>
> I did the plain revert as well, just to have a baseline.
Ahh, I ended up not expecting you to get this done until after rc1 was
out, so I in the meantime just merged my fix instead rather than leave
the expected scheduling-while-atomic
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
From: "Dr. David Alan Gilbert"
Hi,
On the latest tree my compiler has started giving the warning:
drivers/dma/dmatest.c:575:28: warning: the omitted middle operand in ?: will
always be
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
From: Jiri Kosina
commit 4ab25786c87eb20857bbb715c3ae34ec8fd6a214 upstream.
There are a few very theoretical off-by-one bugs in report descriptor size
checking when performing a pre-parsing
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
From: Ben Hutchings
pipe_iov_copy_{from,to}_user() may be tried twice with the same iovec,
the first time atomically and the second time not. The second attempt
needs to continue from the iovec
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
From: "Kirill A. Shutemov"
commit 6b7339f4c31ad69c8e9c0b2859276e22cf72176d upstream.
Reading page fault handler code I've noticed that under right
circumstances kernel would map anonymous pages
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
From: Lior Amsalem
commit 9136291f1dbc1d4d1cacd2840fb35f4f3ce16c46 upstream.
This patch fixes a bug in the XOR driver where the cleanup function can be
called and free descriptors that never
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
From: Pablo Neira Ayuso
commit 20e1db19db5d6b9e4e83021595eab0dc8f107bef upstream.
Non-root user-space processes can send Netlink messages to other
processes that are well-known for being
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
From: Heiko Carstens
commit e47994dd44bcb4a77b4152bd0eada585934703c0 upstream.
The sfpc inline assembly within execve_tail() may incorrectly set bits
28-31 of the sfpc instruction to a value
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
From: NeilBrown
commit 6e9eac2dcee5e19f125967dd2be3e36558c42fff upstream.
If any memory allocation in resize_stripes fails we will return
-ENOMEM, but in some cases we update conf->pool_size
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
From: Sasha Levin
commit dcbff39da3d815f08750552fdd04f96b51751129 upstream.
match_token() expects a NULL terminator at the end of the token list so
that it would know where to stop. Not having
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
From: Michael Halcrow
commit 942080643bce061c3dd9d5718d3b745dcb39a8bc upstream.
Dmitry Chernenkov used KASAN to discover that eCryptfs writes past the
end of the allocated buffer during
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
From: Olga Kornievskaia
commit e8d975e73e5fa05f983fbf2723120edcf68e0b38 upstream.
Problem: When an operation like WRITE receives a BAD_STATEID, even though
recovery code clears the
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
From: "Markus F.X.J. Oberhumer"
Update the LZO compression test vectors according to the latest compressor
version.
Signed-off-by: Markus F.X.J. Oberhumer
(cherry picked from commit
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
From: Trond Myklebust
commit 88de6af24f2b48b06c514d3c3d0a8f22fafe30bd upstream.
req->rq_private_buf isn't initialised when xprt_setup_backchannel calls
xprt_free_allocation.
Fixes:
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
From: Jan Kara
commit 79144954278d4bb5989f8b903adcac7a20ff2a5a upstream.
Store blocksize in a local variable in udf_fill_inode() since it is used
a lot of times.
Signed-off-by: Jan Kara
[bwh:
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
From: Sabrina Dubroca
commit 08e8331654d1d7b2c58045e549005bc356aa7810 upstream.
There is a race condition between e1000_change_mtu's cleanups and
netpoll, when we change the MTU across jumbo
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
From: Dave Olson
commit f7e9e358362557c3aa2c1ec47490f29fe880a09e upstream.
This problem appears to have been introduced in 2.6.29 by commit
93197a36a9c1 "Rewrite sysfs processor cache info
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
From: Mauro Carvalho Chehab
commit 12f4543f5d6811f864e6c4952eb27253c7466c02 upstream.
The maximum size for a DiSEqC command is 6, according to the
userspace API. However, the code allows to
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
From: Ryan Underwood
commit 2fb22a8042fe96b4220843f79241c116d90922c4 upstream.
Disable write buffering on the Toshiba ToPIC95 if it is enabled by
somebody (it is not supposed to be a power-on
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
From: Jan Kara
commit e237ec37ec154564f8690c5bd1795339955eeef9 upstream.
Check that length specified in a component of a symlink fits in the
input buffer we are reading. Also properly ignore
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
From: Heiko Carstens
commit d74419495633493c9cd3f2bbeb7f3529d0edded6 upstream.
Sebastian reported a crash caused by a jump label mismatch after resume.
This happens because we do not save the
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
From: Mauro Carvalho Chehab
commit 1fa2337a315a2448c5434f41e00d56b01a22283c upstream.
The maximum size for a DiSEqC command is 6, according to the
userspace API. However, the code allows to
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
From: "Darrick J. Wong"
commit e531d0bceb402e643a4499de40dd3fa39d8d2e43 upstream.
The journal revoke block recovery code does not check r_count for
sanity, which means that an evil value of
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
From: Mark Hounschell
commit 74856fbf441929918c49ff262ace9835048e4e6a upstream.
256 bytes per sector support has been broken since 2.6.X,
and no-one stepped up to fix this.
So disable support
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
From: Theodore Ts'o
commit 89d96a6f8e6491f24fc8f99fd6ae66820e85c6c1 upstream.
Normally all of the buffers will have been forced out to disk before
we call invalidate_bdev(), but there will be
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
From: Mikulas Patocka
commit d531be2ca2f27cca5f041b6a140504999144a617 upstream.
I have a ST4000DM000 disk. If Linux is booted while the disk is spun down,
the command that sets transfer mode
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
From: Anton Blanchard
commit 5e95235ccd5442d4a4fe11ec4eb99ba1b7959368 upstream.
Recent toolchains force the TOC to be 256 byte aligned. We need
to enforce this alignment in our linker script,
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
From: Wang Weidong
Check the return value of request_module during dccp_probe initialisation,
bail out if that call fails.
Signed-off-by: Gerrit Renker
Signed-off-by: Wang Weidong
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
From: Dan Carpenter
commit 13f6b191aaa11c7fd718d35a0c565f3c16bc1d99 upstream.
Using the indenting we can see the curly braces were obviously intended.
This is a static checker fix, but my guess
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
commit beb39db59d14990e401e235faf66a6b9b31240b0 upstream.
We have two problems in UDP stack related to bogus checksums :
1) We return -EAGAIN to application even if receive
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
From: Andy Lutomirski
commit aa1acff356bbedfd03b544051f5b371746735d89 upstream.
The update_va_mapping hypercall can fail if the VA isn't present
in the guest's page tables. Under certain
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
From: Alexander Sverdlin
[ Upstream commit 29c4afc4e98f4dc0ea9df22c631841f9c220b944 ]
There is NULL pointer dereference possible during statistics update if the route
used for OOTB responce is
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
From: Lars Persson
commit 4d46a67a3eb827ccf1125959936fd51ba318dabc upstream.
The lazy cache flushing implemented in the MIPS kernel suffers from a
race condition that is exposed by do_set_pte()
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
From: Ralf Baechle
commit 9cdf30bd3bac697fc533988f44a117434a858f69 upstream.
Returns a non-zero value if the current processor implementation requires
an IHB instruction to deal with an
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
From: Rusty Russell
commit 83a35114d0e4583e6b0ca39502e68b6a92e2910c upstream.
This bug has been there since day 1; addresses in the top guest physical
page weren't considered valid. You could
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
From: Al Viro
commit 451a2886b6bf90e2fb378f7c46c655450fb96e81 upstream.
unfortunately, allowing an arbitrary 16bit value means a possibility of
overflow in the calculation of total number of
On Sun, Sep 13, 2015 at 12:56:06AM +0200, Willy Tarreau wrote:
> Responses should be made by Sat Sep 19 00:56:05 CEST 2015.
I really meant Fri Sep 18 09:00:00 CEST 2015, sorry the unedited message
went out.
Also, special thanks go to Ben Hutchings who provided me with a clean
series of fixes
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
From: Jan Kara
commit 0e5cc9a40ada6046e6bc3bdfcd0c0d7e4b706b14 upstream.
Symlink reading code does not check whether the resulting path fits into
the page provided by the generic code. This
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
From: Ralf Baechle
commit f05ff43355e6997c18f82ddcee370a6e5f8643ce upstream.
This is no longer needed with the fixed, new and improved definition
of cpu_has_mips_r2_exec_hazard in .
For a
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
From: Oleg Nesterov
commit b72c186999e689cb0b055ab1c7b3cd8fffbeb5ed upstream.
ptrace_resume() is called when the tracee is still __TASK_TRACED. We set
tracee->exit_code and then
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
From: Jan Kara
commit e159332b9af4b04d882dbcfe1bb0117f0a6d4b58 upstream.
Verify that inode size is sane when loading inode with data stored in
ICB. Otherwise we may get confused later when
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
From: "Steven Rostedt (Red Hat)"
commit 6b88f44e161b9ee2a803e5b2b1fbcf4e20e8b980 upstream.
While debugging a WARN_ON() for filtering, I found that it is possible
for the filter string to be
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
From: Theodore Ts'o
commit bdf96838aea6a265f2ae6cbcfb12a778c84a0b8e upstream.
The commit cf108bca465d: "ext4: Invert the locking order of page_lock
and transaction start" caused
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
From: Jiri Slaby
commit c290f8358acaeffd8e0c551ddcc24d1206143376 upstream.
When tty_driver_lookup_tty fails in tty_open, we forget to drop a
reference to the tty driver. This was added by
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
From: "David S. Miller"
Like ipv4, just return xfrm6_rcv_spi()'s return value directly.
Signed-off-by: David S. Miller
(cherry picked from commit 6ac3f6649223d916bbdf1e823926f8f3b34b5d99)
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
From: Gerrit Renker
This fixes commit (38ff3e6bb987ec583268da8eb22628293095d43b) ("dccp_probe:
Fix module load dependencies between dccp and dccp_probe", from 15 Jan).
It fixes the construction
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
From: Malcolm Priestley
commit b5eeed8cb6097c8ea660b6598d36fdbb94065a22 upstream.
There is a small chance that pRD->pRDInfo->skb could go NULL
while the interrupt is processing.
Put NULL check
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
From: Oleg Nesterov
commit e1403b8edf669ff49bbdf602cc97fefa2760cb15 upstream.
task_struct->pid/tgid should go away.
1. Change same_thread_group() to use task->signal for comparison.
2. Change
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
From: Jan Kara
commit a1d47b262952a45aae62bd49cfaf33dd76c11a2c upstream.
UDF specification allows arbitrarily large symlinks. However we support
only symlinks at most one block large. Check the
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
From: Alexander Sverdlin
commit 73bf3c2a500b2db8ac966469591196bf55afb409 upstream.
udelay() in PCI/PCIe read/write callbacks cause 30ms IRQ latency on Octeon
platforms because these operations
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
From: Jesper Dangaard Brouer
commit d079abd181950a44cdf31daafd1662388a6c4d2e upstream.
Too many spaces were introduced in commit 63adc6fb8ac0 ("pktgen: cleanup
checkpatch warnings"), thus
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
From: Feng Tang
commit 55c844a4dd16a4d1fdc0cf2a283ec631a02ec448 upstream.
When rebooting our 24 CPU Westmere servers with 3.4-rc6, we
always see this warning msg:
Restarting system.
machine
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
From: Peter Zijlstra
commit 5de2755c8c8b3a6b8414870e2c284914a2b42e4d upstream.
Because we drop cpu_base->lock around calling hrtimer::function, it is
possible for hrtimer_start() to come in
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
From: Jeff Layton
commit 764ad8ba8cd4c6f836fca9378f8c5121aece0842 upstream.
The current buffer is much too small if you have a relatively long
hostname. Bring it up to the size of the one that
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
From: Steven Rostedt
commit 2cf30dc180cea808077f003c5116388183e54f9e upstream.
When the following filter is used it causes a warning to trigger:
# cd /sys/kernel/debug/tracing
# echo
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
From: "Steven Rostedt (Red Hat)"
commit b4875bbe7e68f139bd3383828ae8e994a0df6d28 upstream.
When testing the fix for the trace filter, I could not come up with
a scenario where the operand count
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
From: Miklos Szeredi
commit 0ad0b3255a08020eaf50e34ef0d6df5bdf5e09ed upstream.
fc->release is called from fuse_conn_put() which was used in the error
cleanup before fc->release was initialized.
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
From: Catalin Marinas
commit c5f3b1a51a591c18c8b33983908e7fdda6ae417e upstream.
The kmemleak scanning thread can run for minutes. Callbacks like
kmemleak_free() are allowed during this time,
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
From: Ralf Baechle
commit d496f7842aada20c61e6044b3395383fa972872c upstream.
A ROSE socket doesn't necessarily always have a neighbour pointer so check
if the neighbour pointer is valid before
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
From: Mark Grondona
commit 73af963f9f3036dffed55c3a2898598186db1045 upstream.
__ptrace_may_access() checks get_dumpable/ptrace_has_cap/etc if task !=
current, this can can lead to surprising
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
From: Jan Kara
commit 23b133bdc452aa441fcb9b82cbf6dd05cfd342d0 upstream.
Check length of extended attributes and allocation descriptors when
loading inodes from disk. Otherwise corrupted
2.6.32-longterm review patch. If anyone has any objections, please let me know.
--
From: Ben Hutchings
Inspired by commit f18c34e483ff ("lib: Fix strnlen_user() to not touch
memory after specified maximum") upstream. This version of
strnlen_user(), no longer present upstream,
This is the start of the longterm review cycle for the 2.6.32.68 release.
All patches will be posted as a response to this one. If anyone has any
issue with these being applied, please let me know. If anyone is a
maintainer of the proper subsystem, and wants to add a Signed-off-by: line
to the
On Fri, Sep 11, 2015 at 5:08 PM, Lee Jones wrote:
> + res = platform_get_resource(pdev, IORESOURCE_MEM, 0);
> + base = devm_ioremap_resource(>dev, res);
> + if (IS_ERR(base))
> + return PTR_ERR(base);
> +
> + clk = devm_clk_get(>dev, NULL);
> + if
On Fri, Sep 11, 2015 at 04:36:39PM -0700, Linus Torvalds wrote:
> On Fri, Sep 11, 2015 at 4:16 PM, Chris Mason wrote:
> >
> > For 4.3 timeframes, what runs do you want to see numbers for:
> >
> > 1) revert
> > 2) my hack
> > 3) plug over multiple sbs (on different devices)
> > 4) ?
>
> Just 2 or
Hi Lee,
On 11 September 2015 at 21:08, Lee Jones wrote:
> Signed-off-by: Pankaj Dev
> Signed-off-by: Lee Jones
> ---
> drivers/char/hw_random/Kconfig | 10 +++
> drivers/char/hw_random/Makefile | 1 +
> drivers/char/hw_random/st-rng.c | 142
>
> 3
On Fri, Sep 11, 2015 at 4:22 PM, Davidlohr Bueso wrote:
> On Fri, 11 Sep 2015, Vinson Lee wrote:
>
>> Hi.
>>
>> With the latest Linux 4.3-rc1, I am hitting this build error on CentOS
>> 5.11.
>>
>> HOSTCC scripts/sign-file
>> scripts/sign-file.c:23:25: fatal error: openssl/cms.h: No such file
On Mon, 7 Sep 2015 17:01:58 -0300
Danilo Cesar Lemes de Paula wrote:
> The following series contains:
> * kernel-doc: markdown support and improvements.
OK, I've spent a while looking this stuff over. I like the general idea,
but I do have a couple of concerns.
1 Installing pandoc on a
On Wed, Sep 9, 2015 at 2:54 PM, Peter Zijlstra wrote:
> On Wed, Sep 09, 2015 at 12:05:50PM +0200, Sedat Dilek wrote:
>> I can boot into a CLANG v3.7 compiled Linux-kernel when lib/bitmap is
>> compiled with GCC (here: v4.9).
>>
>> CONFIG_OPTIMIZE_INLINING has no effect on this.
>>
>> Attached are
Hi linux
http://projectlifestories.org/mixture.php?beyond=m10x2wpkaxc1vps5
james.leitch
--
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 http://vger.kernel.org/majordomo-info.html
Please
Le 06/18/15 17:11, Brian Norris a écrit :
> Support S2, S3, and S5 through /sys/power/state ("standby" and "mem")
> and the poweroff code paths. See comments in pm.c for a few more details
> about these system suspend modes.
>
> Signed-off-by: Brian Norris
Applied to soc/next with an
On Mon, 7 Sep 2015 19:06:14 +0200
ulfalizer.l...@gmail.com wrote:
> Without knowing this, the use of sysfs_streq() becomes puzzling.
>
> The termination happens in kernfs_fop_write().
Applied to the docs tree. I moved it up a paragraph, though, since it
better fits the flow of the document
Le 06/18/15 17:11, Brian Norris a écrit :
> Used on BCM7xxx Set-Top Box chips (e.g., BCM7445).
>
> Signed-off-by: Brian Norris
Applied to soc/next, thanks!
--
Florian
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On Wed, 2 Sep 2015 14:34:51 +0200
ulfalizer.l...@gmail.com wrote:
> sysfs-tagging.txt contains more outdated references (e.g., to various
> kobj_ns_*() functions that no longer exist), but hopefully it should be in
> a better shape than before. I'm new to sysfs internals in general.
>
> The
On Sat, Sep 12, 2015 at 01:37:02PM -0400, Alan Stern wrote:
> On Fri, 11 Sep 2015, Greg Kroah-Hartman wrote:
>
> > 4.1-stable review patch. If anyone has any objections, please let me know.
>
> It turns out that this patch causes problems with the sr driver. A
> reversion and alternate
Le 06/18/15 17:11, Brian Norris a écrit :
> Useful for waking the system from suspend after a specified period of
> time.
>
> This IP could potentially be supported as an RTC driver (for use with
> the 'rtcwake' utility), but it is not battery backed, so that's not a
> great fit. Implement a
Le 06/18/15 17:11, Brian Norris a écrit :
> Signed-off-by: Brian Norris
Although the binding looks good to me, I am not applying this one just
yet since we would want to merge the wake-timer driver and its binding
at the same time, thanks!
> ---
>
Le 06/18/15 17:11, Brian Norris a écrit :
> Need the aon_pm_l2_intc, aon-ctrl, waketimer, boot SRAM, and
> memory_controller descriptions.
>
> Signed-off-by: Brian Norris
Applied to devicetree/next sans the wake-timer node and the now
duplicate aon_pm_l2_intc entry, thanks!
--
Florian
--
To
Le 06/18/15 17:11, Brian Norris a écrit :
> Signed-off-by: Brian Norris
Applied to devicetree/next, thanks!
--
Florian
--
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
Le 06/18/15 17:11, Brian Norris a écrit :
> Lazily-masked IRQs can cause system suspend problems (e.g., spurious
> wakeups from WFI), so we need to be sure non-wakeup GIC interrupts get
> masked, not just disabled, during system suspend.
>
> Signed-off-by: Brian Norris
Dropped this patch, no
Add charge control limit to the power supply subsystem of the Compal
platform driver.
This apparently was present in the original driver by Cezary Jackiewicz
at http://eko.one.pl/index.php?page=compal-laptop but it seems to have been
overlooked.
The Kconfig description is updated to reflect this
Hi Linus!
Please pull the below tree for CRIS changes for 4.3.
Mostly removal of old cruft of which we can use a generic version,
or fixes for code not commonly run in the cris port,
but also additions to enable som good debug.
Thanks!
The following changes since commit
On Wed, Aug 26, 2015 at 12:48 PM, Jagan Teki wrote:
> The clear flag status register operation is required by Micron
> SPI-NOR chips, which support FSR. And if error bits of FSR
> have been set like protection, voltage, erase, and program,
> it must be cleared by executing clear FSR operation.
>
1 - 100 of 466 matches
Mail list logo
