Looks good to me.
Reviewed-by: Ashley Lai
Thanks,
--Ashley
On Thu, 12 Feb 2015, honclo wrote:
The tpm_ibmvtpm module is affected by an unaligned access problem.
ibmvtpm_crq_get_version failed with rc=-4 during boot when vTPM is
enabled in Power partition, which supports both little endian an
The patch titled
Subject: mm: hwpoison: drop lru_add_drain_all() in __soft_offline_page()
has been removed from the -mm tree. Its filename was
mm-hwpoison-drop-lru_add_drain_all-in-__soft_offline_page.patch
This patch was dropped because it was merged into mainline or a subsystem tree
The patch titled
Subject: mm: fix negative nr_isolated counts
has been removed from the -mm tree. Its filename was
mm-fix-negative-nr_isolated-counts.patch
This patch was dropped because it was merged into mainline or a subsystem tree
--
The patch titled
Subject: mm/memory.c: actually remap enough memory
has been removed from the -mm tree. Its filename was
mm-actually-remap-enough-memory.patch
This patch was dropped because it was merged into mainline or a subsystem tree
---
The patch titled
Subject: mm/compaction: fix wrong order check in compact_finished()
has been removed from the -mm tree. Its filename was
mm-compaction-fix-wrong-order-check-in-compact_finished.patch
This patch was dropped because it was merged into mainline or a subsystem tree
--
On Fri, Feb 13, 2015 at 09:37:31PM +0200, Alexander Ploumistos wrote:
> On Fri, Feb 13, 2015 at 9:21 PM, Josh Boyer wrote:
> >
> > On Fri, Feb 13, 2015 at 10:20:51PM +0300, Dmitry Tunin wrote:
> > >
> > > I think it makes sense to add
> > >
> > > Cc: stable@vger.kernel.org
> > >
> > > If you do, i
On Fri, Feb 13, 2015 at 9:21 PM, Josh Boyer wrote:
>
> On Fri, Feb 13, 2015 at 10:20:51PM +0300, Dmitry Tunin wrote:
> >
> > I think it makes sense to add
> >
> > Cc: stable@vger.kernel.org
> >
> > If you do, it will be merged into stable kernel versions.
>
> I agree, but this is something the ups
On Fri, Feb 13, 2015 at 10:20:51PM +0300, Dmitry Tunin wrote:
>
> > From: alxpl
> >
> > Add 04f2:aff1 to ath3k.c supported devices list and btusb.c blacklist, so
> > that the device can load the ath3k firmware and re-enumerate itself as an
> > AR3011 device.
> >
> >
> > T: Bus=05 Lev=01 Prn
> From: alxpl
>
> Add 04f2:aff1 to ath3k.c supported devices list and btusb.c blacklist, so
> that the device can load the ath3k firmware and re-enumerate itself as an
> AR3011 device.
>
>
> T: Bus=05 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12 MxCh= 0
> D: Ver= 1.10 Cls=e0(wlcon) Sub=
From: alxpl
Add 04f2:aff1 to ath3k.c supported devices list and btusb.c blacklist, so that
the device can load the ath3k firmware and re-enumerate itself as an AR3011
device.
T: Bus=05 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64
> From: alxpl
>
>
> With a lot of help and pointers from Dmitry Tunin, I managed to put the patch
> together in the "appropriate" fashion, against bluetooth-next. He also
> suggested that I include the relevant information from my
> /sys/kernel/debug/usb/devices. If it is still sub-par, pleas
From: alxpl
With a lot of help and pointers from Dmitry Tunin, I managed to put the patch
together in the "appropriate" fashion, against bluetooth-next. He also
suggested that I include the relevant information from my
/sys/kernel/debug/usb/devices. If it is still sub-par, please let me know
On Tue, 2015-02-10 at 12:49 -0800, a...@linux-foundation.org wrote:
> From: Chen Jie
> Subject: jffs2: fix handling of corrupted summary length
>
> sm->offset maybe wrong but magic maybe right, the offset do not have
> CRC.
Applied; thanks.
--
David WoodhouseOpen So
We have a scenario where after the fsync log replay we can lose file data
that had been previously fsync'ed if we added an hard link for our inode
and after that we sync'ed the fsync log (for example by fsync'ing some
other file or directory).
This is because when adding an hard link we updated th
On 02/12/2015, 05:13 AM, Austin Lund wrote:
> Is the following commit appropriate for inclusion into stable branches
> (particularly for 3.14 from my own personal perspective):
>
> a8f29e89f2b54fbf2c52be341f149bc195b63a8b
>
> It fixes the synchronization with the lirc daemon when there is long
>
From: Alex Elder
This patch has been added to the 3.12 stable tree. If you have any
objections, please let us know.
===
commit 638c323c4d1f8eaf25224946e21ce8818f1bcee1 upstream.
Olivier Bonvalet reported having repeated crashes due to a failed
assertion he was hitting in rbd_img_ob
At Fri, 13 Feb 2015 11:14:41 +0800,
Hui Wang wrote:
>
> Otherwise, the mute led can't work at all.
>
> Tested-by: Taihsiang Ho
> Cc:
> BugLink: https://bugs.launchpad.net/bugs/1410704
> Signed-off-by: Hui Wang
Thanks, applied.
Takashi
> ---
> sound/pci/hda/patch_realtek.c | 1 +
> 1 file
From: Austin Lund
This patch has been added to the 3.12 stable tree. If you have any
objections, please let us know.
===
commit a8f29e89f2b54fbf2c52be341f149bc195b63a8b upstream.
Userspace expects to see a long space before the first pulse is sent on
the lirc device. Currently, if
This is an automatic generated email to let you know that the following patch
were queued at the
http://git.linuxtv.org/cgit.cgi/media_tree.git tree:
Subject: [media] gpsca: remove the risk of a division by zero
Author: Luis de Bethencourt
Date:Mon Feb 9 07:16:25 2015 -0300
As reported by
This is an automatic generated email to let you know that the following patch
were queued at the
http://git.linuxtv.org/cgit.cgi/media_tree.git tree:
Subject: [media] vb2: Fix dma_dir setting for dma-contig mem type
Author: Sakari Ailus
Date:Fri Feb 13 04:42:37 2015 -0300
The last argumen
On 02/11/2015, 02:34 PM, Ilya Dryomov wrote:
> Hello,
>
> Any kernel that has 0f2d5be792b0 ("rbd: use reference counts for image
> requests", went into 3.16) backported should also have 638c323c4d1f
> ("rbd: drop an unsafe assertion", went into 3.14).
>
> Please add 638c323c4d1f to 3.10, 3.12, Ub
21 matches
Mail list logo
