3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Takashi Iwai
commit b5a663aa426f4884c71cd8580adae73f33570f0d upstream.
A slave timer instance might be still accessible
APB0 is bearly mentioned in H3 User Manual and it is only setup in the
Allwinners kernel dump for CIR. I have verified experimentally that the
gate for R_PIO exists and works, though. There are probably other gates
there but I don't know their order right now and I don't have access to
their
On Tue, 2 Feb 2016, Dmitry Vyukov wrote:
> If the following program run in a parallel loop, eventually it leaves
> hanged uninterruptable tasks on mmap_sem.
I am now able to reproduce the issue and will be looking into it.
[ .. snip .. ]
> // autogenerated by syzkaller
This patch series is extension of my original single patch with the same
subject. It adds support for R_PIO so that GPIO port L can be used in H3
based devices. It was tested on OrangePi PC where PL is connected amount
others to an onboard led, a switch, an IR receiver and some VCC
controllers.
On 2016-02-03 06:04, Thierry Reding wrote:
> On Wed, Jan 27, 2016 at 06:46:50PM -0800, Stefan Agner wrote:
> [...]
>> On 2015-11-18 18:42, Stefan Agner wrote:
> [...]
>> > diff --git a/drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_crtc.c
> [...]
>> > @@ -89,6 +91,15 @@ static void
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Vegard Nossum
commit 9f2dfda2f2f1c6181c3732c16b85c59ab2d195e0 upstream.
An inverted return value check in
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Uri Mashiach
commit e47301b06d5a65678690f04c2248fd181db1e59a upstream.
Fix the below Oops when trying to
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Kent Overstreet
commit 627ccd20b4ad3ba836472468208e2ac4dfadbf03 upstream.
Previously, it would only scan
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Larry Finger
commit d4d60b4caaa5926e1b243070770968f05656107a upstream.
Two of the module parameters are
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: =?UTF-8?q?Aur=C3=A9lien=20Francillon?=
commit dd0d0d4de582a6a61c032332c91f4f4cb2bab569 upstream.
Without
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Zheng Liu
commit 2ef9ccbfcb90cf84bdba320a571b18b05c41101b upstream.
Subject : [PATCH v2] bcache: fix a
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Andrew Elble
commit 361cad3c89070aeb37560860ea8bfc092d545adc upstream.
We've seen this in a packet capture - I've
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Zheng Liu
commit fecaee6f20ee122ad75402c53d8278f9bb142ddc upstream.
This bug can be reproduced by the following
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Trond Myklebust
commit ade14a7df796d4e86bd9d181193c883a57b13db0 upstream.
If a NFSv4 client uses the
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Al Viro
commit 4d4d8573a8451acc9f01cbea24b7e55f04a252fe upstream.
Signed-off-by: Al Viro
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Kent Overstreet
commit c5f1e5adf956e3ba82d204c7c141a75da9fa449a upstream.
Signed-off-by: Takashi Iwai
bugzilla-dae...@bugzilla.kernel.org writes:
> https://bugzilla.kernel.org/show_bug.cgi?id=111541
>
> --- Comment #8 from Weilong Chen ---
> (In reply to Rusty Russell from comment #7)
>> Rusty Russell writes:
>> > And there are other places with the
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Antonio Ospite
commit dcc7fdbec53a960588f2c40232db2c6466c09917 upstream.
v4l2-compliance sends a zeroed struct
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Anna Schumaker
commit 343ae531f12b046ddfe54b0aa91b11b257f0c55f upstream.
inode is unused when
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Marcelo Ricardo Leitner
commit 38ee8fb67c3457f36f5137073c4b8ac2436d2393 upstream.
They don't need to be any
Hi Linus,
This is an optional pull request, Alex was waiting for some alsa
bits and some amdgpu bits to land to enable audio support on some
AMD APUs. The number of chips using this is quite low, and it's
just enabling the audio block for those GPUs.
I'm happy enough it shouldn't cause any
On Tue, 26 Jan 2016, Vlastimil Babka wrote:
> With the new printk format strings for flags, we can get rid of dump_flags()
> in mm/debug.c.
>
> This also fixes dump_vma() which used dump_flags() for printing vma flags.
> However dump_flags() did a page-flags specific filtering of bits higher
On Tue, 26 Jan 2016, Vlastimil Babka wrote:
> It would be useful to translate gfp_flags into string representation when
> printing in case of an allocation failure, especially as the flags have been
> undergoing some changes recently and the script ./scripts/gfp-translate needs
> a matching
The regmap_irq_get_virq() can return 0 or -EINVAL in error conditions
but driver checked only for value of 0.
This could lead to a cast of -EINVAL to an unsigned int used as a
interrupt number for devm_request_threaded_irq(). Although this is not
yet fatal (devm_request_threaded_irq() will just
On 02/03/2016 03:02 PM, Christoph Lameter wrote:
The fast path uses the per cpu caches. No locks are taken and there
is no IRQ disabling. For concurrency protection this comment
explains it best:
/*
* The cmpxchg will only match if there was no additional
* operation and if we are on the
FYI, we noticed the below changes on
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
commit 63c6a211b0eb5b1c86ffdd9d89639fb7f1b70fca ("mm: workingset: per-cgroup
cache thrash detection")
[8.134495] No soundcards found.
[8.137598] debug: unmapping init [mem
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Guenter Roeck
commit c86576ea114a9a881cf7328dc7181052070ca311 upstream.
mn10300 builds fail with
fs/stat.c: In
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Jamie Bainbridge
commit ec7147a99e33a9e4abad6fc6e1b40d15df045d53 upstream.
Under some conditions, CIFS can
On Wed, 3 Feb 2016 18:14:16 +0300 "Kirill A. Shutemov"
wrote:
> rmap_walk_locked() is the same as rmap_walk(), but caller takes care
> about relevant rmap lock. It only supports anonymous pages for now.
>
> It's preparation to switch THP splitting from custom
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Andrew Morton
commit 04ea1e91f85615318ea91ce8ab50cb6a01ee4005 upstream.
openrisc-allnoconfig:
On Tue, Jan 05, 2016 at 02:35:17PM -0500, James Simmons wrote:
> From: Parinay Kondekar
>
> With struct libcfs_device_userstate gone we can move
> the remaining code of libcfs_psdev_ops.p_[open|close]
> into the libcfs_psdev_[open|release] functions directly.
>
>
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Sven Eckelmann
commit 2baa753c276f27f8e844637561ad597867aa6fb6 upstream.
It is not allowed to free the memory of
clear_pages() is never used expect by clear_page, and PPC32 is the
only architecture (still) having this function. Neither PPC64 nor
any other architecture has it.
This patch removes clear_pages() and moves clear_page() function
inline (same as PPC64) as it only is a few isns
Signed-off-by:
This simplification helps the compiler. We now have only one test
instead of two, so it reduces the number of branches.
Signed-off-by: Christophe Leroy
---
v2: new
v3: no change
v4: no change
v5: no change
arch/powerpc/mm/dma-noncoherent.c | 2 +-
1 file changed, 1
On Thu, 4 Feb 2016 01:45:07 +0300 "Kirill A. Shutemov"
wrote:
> On Wed, Feb 03, 2016 at 02:40:19PM -0800, Andrew Morton wrote:
> > On Wed, 3 Feb 2016 18:14:16 +0300 "Kirill A. Shutemov"
> > wrote:
> >
> > > rmap_walk_locked()
Now the noltlbs kernel parameter is also applicable to PPC8xx
Signed-off-by: Christophe Leroy
---
v2: no change
v3: no change
v4: no change
v5: no change
Documentation/kernel-parameters.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
From: Jiri Olsa
We broke interval data displays with commit:
3f416f22d1e2 ("perf stat: Do not clean event's private stats")
This commit removed stats cleaning, which is important for '-r' option
to carry counters data over the whole run. But it's necessary to clean
it for
We are spending between 40 and 160 cycles with a mean of 65 cycles in
the DTLB handling routine (measured with mftbl) so make it more
simple althought it adds one instruction.
With this modification, we get three registers available at all time,
which will help with following patch.
The INIT IPI event handler special cases the boot-strap processor
(BSP) handling, avoiding the same mp state handling which is done for
the other (AP) processors. Debugging a linux guest usage scenario of
avoiding a reboot through the bios for a crash on any processor via eg:
kexec -p
On 01/31/2016 07:47 PM, Dave Chinner wrote:
On Fri, Jan 29, 2016 at 02:30:44PM -0500, Waiman Long wrote:
Linked list insertion or deletion under lock is a very common activity
in the Linux kernel. If this is the only activity under lock, the
locking overhead can be pretty large compared with
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Herbert Xu
commit 6a935170a980024dd29199e9dbb5c4da4767a1b9 upstream.
This patch allows
Commit d28bc9dd25ce reversed the order of two lines which initialize cr0,
allowing the current (old) cr0 value to mess up vcpu initialization.
This was observed in the checks for cr0 X86_CR0_WP bit in the context of
kvm_mmu_reset_context(). Besides, setting vcpu->arch.cr0 after vmx_set_cr0()
is
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Nicolas Boichat
commit 9586495dc3011a80602329094e746dbce16cb1f1 upstream.
This reverts one hunk of
commit
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Nicolas Boichat
commit 43c54b8c7cfe22f868a751ba8a59abf1724160b1 upstream.
This reverts one hunk of
commit
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Tejun Heo
commit 8d91f8b15361dfb438ab6eb3b319e2ded43458ff upstream.
@console_may_schedule tracks whether console_sem
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Naoya Horiguchi
commit d96b339f453997f2f08c52da3f41423be48c978f upstream.
I saw the following BUG_ON
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Takashi Iwai
commit db8948e653e12b218058bb6696f4a33fa7845f64 upstream.
ASUS N550JX (PCI SSID 1043:13df) requires the
On Wed, 2016-02-03 at 23:55 +0100, Marcel Ziswiler wrote:
> On Mon, 2016-02-01 at 21:29 +0800, Shawn Guo wrote:
>
> [snip]
>
> > + /* STMPE811 touch screen controller */
> > > + stmpe811@41 {
> > > + compatible = "st,stmpe811";
> >
> > The compatible seems to be used by kernel without
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Herbert Xu
commit 37766586c965d63758ad542325a96d5384f4a8c9 upstream.
This patch adds a compatibility path
Oops.
Anyhow, I see my patch has done a similar change in init_vmcb() , so you may
want to revert it as well.
Nadav
Bruce Rogers wrote:
> Commit d28bc9dd25ce reversed the order of two lines which initialize cr0,
> allowing the current (old) cr0 value to mess up vcpu
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Roman Volkov
commit f9eccf24615672896dc13251410c3f2f33a14f95 upstream.
The vt8500 clocksource driver declares
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Jeff Layton
commit 7f3697e24dc3820b10f445a4a7d914fc356012d1 upstream.
Dmitry reported that he was able to
On Mon, 2016-02-01 at 21:29 +0800, Shawn Guo wrote:
[snip]
> > + stmpe_touchscreen {
>
> Shouldn't the node name be generic as just touchscreen? Or at least,
> hyphen instead of underscore should be used in node name.
This one is actually as per binding document example:
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Vegard Nossum
commit 0754fb298f2f2719f0393491d010d46cfb25d043 upstream.
I was seeing some really weird
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Mikulas Patocka
commit 385277bfb57faac44e92497104ba542cdd82d5fe upstream.
When there is an error copying a chunk
Sorry for spamming. The correct fix appears to reload the DRs (set
KVM_DEBUGREG_RELOAD) in kvm_arch_vcpu_load .
(for me it works)
Regards,
Nadav
Nadav Amit wrote:
> I think the problem lies here:
>
>/*
> * If the guest has used debug registers, at
From: Rafael J. Wysocki
The preprocessor magic used for setting the default cpufreq governor
(and for using the performance governor as a fallback one for that
matter) is really nasty, so replace it with __weak functions and
overrides.
Signed-off-by: Rafael J.
Hi,
A few days ago I looked at the common code used by the ondemand and conservative
governors because of the deadlock issue that Viresh has addressed recently
(http://marc.info/?l=linux-pm=145450832814058=4) and it occurred to me
that the whole thing was really too tangled and might be made
On Thu, Feb 04, 2016 at 12:15:50AM +0200, Felipe Balbi wrote:
>> Since I've now been bitten by this several times: Is there any sort of best
>> practice for integrating git with MUAs? What I'm doing right now is
>> cut-and-paste from mutt to get the to/cc/in-reply-to headers right, and
>> that's
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Larry Finger
commit b24f19f16b9e43f54218c07609b783ea8625406a upstream.
The module parameter for software
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Lorenzo Pieralisi
commit 60792ad349f3c6dc5735aafefe5dc9121c79e320 upstream.
The pmuserenr_el0 register
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Trond Myklebust
commit 762674f86d0328d5dc923c966e209e1ee59663f2 upstream.
Donald Buczek reports that
On 02/04/2016 05:43 AM, Greg Kroah-Hartman wrote:
> On Tue, Feb 02, 2016 at 10:34:34PM +0800, Lu Baolu wrote:
>>
>> On 01/26/2016 08:58 PM, Lu Baolu wrote:
>>> Hi,
>>>
>>> This patch series adds support for early printk through USB3 debug port.
>>> USB3 debug port is described in xHCI
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Dmitry Tunin
commit 1623d0bf847d3b38d8cf24367b3689ba0e3fe2aa upstream.
BugLink:
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: John Blackwood
commit 5db4fd8c52810bd9740c1240ebf89223b171aa70 upstream.
Make sure to clear out any ptrace
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Ido Schimmel
commit 60a6531bfe4981ccd65f66a350cc5693fcde upstream.
We can't be within an RCU read-side
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Joe Jin
commit ca88ea1247dfee094e2467a3578eaec9bdf0833a upstream.
Sometimes xennet_create_queues() may failed to
On Tue, 26 Jan 2016, Vlastimil Babka wrote:
> When updating tracing's show_gfp_flags() I have noticed that perf's
> gfp_compact_table is also outdated. Fill in the missing flags and place a
> note in gfp.h to increase chance that future updates are synced. Convert the
> __GFP_X flags from "GFP_X"
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Wei Liu
commit 32a844056fd43dda647e1c3c6b9983bdfa04d17d upstream.
Originally that parameter was always reset to
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: lucien
commit 8a0d19c5ed417c78d03f4e0fa7215e58c40896d8 upstream.
when A sends a data to B, then A close() and
On Wed, Feb 03, 2016 at 08:52:50PM +, Andrew Cooper wrote:
> On 03/02/16 18:55, Luis R. Rodriguez wrote:
> > We add new hypervisor type to close the semantic gap for hypervisor types,
> > and
> > much like subarch enable also a subarch_data to let you pass and use your
> > hvmlite_start_info.
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Takashi Iwai
commit 3567eb6af614dac436c4b16a8d426f9faed639b3 upstream.
ALSA sequencer code has an open race between the
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Sergey Senozhatsky
commit 3d5fe03a3ea013060ebba2a811aeb0f23f56aefa upstream.
We can end up allocating a
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Takashi Iwai
commit ee8413b01045c74340aa13ad5bdf905de32be736 upstream.
ALSA timer instance object has a couple of
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Rabin Vincent
commit 820962dc700598ffe8cd21b967e30e7520c34748 upstream.
cifs_call_async() queues the MID to
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Ben Skeggs
commit 0a882cadbc63fd2da3994af7115b4ada2fcbd638 upstream.
fdo#93634
Signed-off-by: Ben Skeggs
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: "Ouyang Zhaowei (Charles)"
commit 6a1f513776b78c994045287073e55bae44ed9f8c upstream.
On a cancelled suspend
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Ulrich Weigand
commit 2e50c4bef77511b42cc226865d6bc568fa7f8769 upstream.
If a text section starts out with
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Herbert Xu
commit c840ac6af3f8713a71b4d2363419145760bd6044 upstream.
Each af_alg parent socket obtained
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Russell King
commit d9812780a020bcec44565b5950b2a8b31afb5545 upstream.
The SD card specification allows
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Stephane Eranian
commit 61b87cae6361ea6af161c1ffa549898892707b19 upstream.
This patch fixes a bug in the
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Dan Carpenter
commit 0dc924c5f2a3c4d999e12feaccee5f970cea1315 upstream.
If we return 1 here, then the caller
On Thu, 28 Jan, at 09:23:10AM, Gabriel L. Somlo wrote:
> From: "Gabriel Somlo"
>
> Allow access to QEMU firmware blobs, passed into the guest VM via
> the fw_cfg device, through SysFS entries. Blob meta-data (e.g. name,
> size, and fw_cfg key), as well as the raw binary blob data
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Brian Norris
commit 715780ae4bb76d6fd2f20eb78e2a9ba9769a6cdc upstream.
The kerneldoc for
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Bart Van Assche
commit f0a8afecb29ad0005e7e946228a0ef5422058b85 upstream.
strsep() modifies its first
There is no real need to have set_context() in assembly.
Now that we have mtspr() handling CPU6 ERRATA directly, we
can rewrite set_context() in C language for easier maintenance.
Signed-off-by: Christophe Leroy
---
v2: no change
v3: no change
v4: no change
v5: no change
This patch adds inline functions to use dcbz, dcbi, dcbf, dcbst
from C functions
Signed-off-by: Christophe Leroy
---
v2: new
v3: no change
v4: no change
v5: no change
arch/powerpc/include/asm/cache.h | 19 +++
1 file changed, 19 insertions(+)
diff
On PPC8xx, flushing instruction cache is performed by writing
in register SPRN_IC_CST. This registers suffers CPU6 ERRATA.
The patch rewrites the fonction in C so that CPU6 ERRATA will
be handled transparently
Signed-off-by: Christophe Leroy
---
v2: no change
v3: no
Commit 771168494719 ("[POWERPC] Remove unused machine call outs")
removed the call to setup_io_mappings(), so remove the associated
progress line message
Signed-off-by: Christophe Leroy
---
v2: no change
v3: no change
v4: no change
v5: no change
flush/clean/invalidate _dcache_range() functions are all very
similar and are quite short. They are mainly used in __dma_sync()
perf_event locate them in the top 3 consumming functions during
heavy ethernet activity
They are good candidate for inlining, as __dma_sync() does
almost nothing but
On Wed, 3 Feb 2016, Michal Hocko wrote:
> Hi,
> this thread went mostly quite. Are all the main concerns clarified?
> Are there any new concerns? Are there any objections to targeting
> this for the next merge window?
Did we ever figure out what was causing the oom killer to be called much
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Rich Felker
commit 114bf37e04d839b555b3dc460b5e6ce156f49cf0 upstream.
Add Yoshinori Sato and Rich Felker as
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Oliver Freyermuth
commit f7d7f59ab124748156ea551edf789994f05da342 upstream.
Add the USB device ID for ELV
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Vinit Agnihotri
commit fbbeb8632bf0b46ab44cfcedc4654cd7831b7161 upstream.
The current code is
On Sun, Dec 27, 2015 at 11:59:57PM +0700, Ivan Safonov wrote:
> 1) Return value of this function does not used;
> 2) wilc_parse_network_info has no reasons to return an error;
> 3) kfree does not free memory if argument is NULL.
>
> Signed-off-by: Ivan Safonov
> ---
>
On Wed, 3 Feb 2016, Michal Hocko wrote:
> diff --git a/mm/oom_kill.c b/mm/oom_kill.c
> index 8e345126d73e..b87acdca2a41 100644
> --- a/mm/oom_kill.c
> +++ b/mm/oom_kill.c
> @@ -420,6 +420,7 @@ static struct task_struct *oom_reaper_th;
> static struct task_struct *task_to_reap;
> static
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Jean Delvare
commit fd7f6727102a1ccf6b4c1dfcc631f9b546526b26 upstream.
I don't think it makes sense for a module to
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Mario Kleiner
commit 2f0c0b2d96b1205efb14347009748d786c2d9ba5 upstream.
Without the reboot=pci method, the
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Mike Marciniszyn
commit 09dc9cd6528f5b52bcbd3292a6312e762c85260f upstream.
The code produces the following
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Vitaly Kuznetsov
commit 7625b3a0007decf2b135cb47ca67abc78a7b1bc1 upstream.
Commit 08d78658f393 ("panic: release
701 - 800 of 2948 matches
Mail list logo