Вы сможете характеризоваться четким зрением
http://www.econom-krg.gov.kz/modules/mod_ya/exnrf.htm?mgwkm
NЇВцьrИyњшиbВXЌЖЧЇvи^)оК{.nЧ+ЗЌЕІхz)э
цшw* jgЌБЈ ЖнЂj/ъфzЙор2оЈшк&Ђ)пЁЋaЖкўј ЎGЋщhЎцj:+vЈwшйЅ
On Fri, Oct 11, 2013 at 05:50:33PM -0700, Guenter Roeck wrote:
> On Fri, Oct 11, 2013 at 03:12:41PM -0700, Greg Kroah-Hartman wrote:
> > On Fri, Oct 11, 2013 at 02:56:19PM -0700, Guenter Roeck wrote:
> > > On Fri, Oct 11, 2013 at 12:36:07PM -0700, Greg Kroah-Hartman wrote:
> > > > This is the start
On Fri, Oct 11, 2013 at 05:52:17PM -0700, Guenter Roeck wrote:
> On Fri, Oct 11, 2013 at 03:14:05PM -0700, Greg Kroah-Hartman wrote:
> > On Fri, Oct 11, 2013 at 12:34:44PM -0700, Greg Kroah-Hartman wrote:
> > >
> > > NOTE: This is going to be the next-to-last 3.0.x
On Wed, Oct 9, 2013 at 10:42 AM, Linus Walleij wrote:
> On Mon, Oct 7, 2013 at 7:51 PM, Olof Johansson wrote:
>> On Mon, Oct 07, 2013 at 03:19:53PM +0200, Linus Walleij wrote:
>
>>> This fixes a long-standing Integrator/CP regression from
>>> commit 870e2928cf3368ca9b06bc925d0027b0a56bcd8e
>>> "A
On Sun, Oct 13, 2013 at 2:02 PM, Linus Walleij wrote:
> On Wed, Oct 9, 2013 at 10:42 AM, Linus Walleij
> wrote:
>> On Mon, Oct 7, 2013 at 7:51 PM, Olof Johansson wrote:
>>> On Mon, Oct 07, 2013 at 03:19:53PM +0200, Linus Walleij wrote:
>>
This fixes a long-standing Integrator/CP regression
On Sat, Oct 12, 2013 at 07:36:06AM +0900, Tetsuo Handa wrote:
> Greg Kroah-Hartman wrote:
> > 3.4-stable review patch. If anyone has any objections, please let me know.
>
> 3.4-stable doesn't need this patch because commit 264b83c07a84
> ("usermodehelper: check subprocess_info->path != NULL") alr
--
NOTE! The 3.0.x kernel series will be moving to End-Of-Life soon,
within a week. Please move anything that is relying on this kernel
version to the other longterm kernel releases (3.4.x or 3.10.x) as soon
as possible. If anyone has any questions about this, please
diff --git a/Makefile b/Makefile
index 0d6881a..a6ddb9d 100644
--- a/Makefile
+++ b/Makefile
@@ -1,6 +1,6 @@
VERSION = 3
PATCHLEVEL = 0
-SUBLEVEL = 99
+SUBLEVEL = 100
EXTRAVERSION =
NAME = Sneaky Weasel
diff --git a/arch/powerpc/kernel/iommu.c b/arch/powerpc/kernel/iommu.c
index 961bb03..795
I'm announcing the release of the 3.4.66 kernel.
All users of the 3.4 kernel series must upgrade.
The updated 3.4.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-3.4.y
and can be browsed at the normal kernel.org git web browser:
diff --git a/Makefile b/Makefile
index 3a8897f..e9587ab 100644
--- a/Makefile
+++ b/Makefile
@@ -1,6 +1,6 @@
VERSION = 3
PATCHLEVEL = 4
-SUBLEVEL = 65
+SUBLEVEL = 66
EXTRAVERSION =
NAME = Saber-toothed Squirrel
diff --git a/arch/arm/mm/init.c b/arch/arm/mm/init.c
index 8f5813b..056cfbe 10064
Hello,
On Sat, Oct 12, 2013 at 05:37:55PM +0800, Weijie Yang wrote:
> Hi, all
>
> I thought out a new way to resolve this problem: use CAS instead of refcount.
>
> It not only resolve this problem, but also fix another issue,
> can be expanded to support frontswap get_and_free mode easily.
> And
I'm announcing the release of the 3.10.16 kernel.
All users of the 3.10 kernel series must upgrade.
The updated 3.10.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-3.10.y
and can be browsed at the normal kernel.org git web browser:
I'm announcing the release of the 3.11.5 kernel.
All users of the 3.11 kernel series must upgrade.
The updated 3.11.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-3.11.y
and can be browsed at the normal kernel.org git web browser:
This patch looks like it should be in the 3.11-stable tree, should we apply
it?
--
From: "Jan Kara "
commit 9c12a831d73dd938a22418d70b39aed4feb4bdf2 upstream
The Linux Kernel Performance project guys have reported that commit
4e7ea81db5 introduces a performance regression for th
This patch looks like it should be in the 3.11-stable tree, should we apply
it?
--
From: "Dan Carpenter "
commit 8612ed0d97abcf1c016d34755b7cf2060de71963 upstream
Calling the WDIOC_GETSTATUS & WDIOC_GETBOOTSTATUS and twice will cause a
interruptible deadlock.
Signed-off-by: Dan
This patch looks like it should be in the 3.11-stable tree, should we apply
it?
--
From: "Jingoo Han "
commit 4c4e45669de475573b15d968a6dca8d00124c9ad upstream
STAGE_CFG bits are defined as [5:4] bits. However, '(((x) & 0x30) << 4)'
handles [9:8] bits. Thus, it should be fixed i
This patch looks like it should be in the 3.11-stable tree, should we apply
it?
--
From: "Yuvaraj Kumar C D "
commit 4d594dd3028ba8cdfcbd854bde3811a1ee4e36d7 upstream
Without the "clock-frequency" property in arch timer node, could able
to see the below crash dump.
[] (unwind_b
Hi Jonghwan,
> This patch looks like it should be in the 3.11-stable tree, should we apply
> it?
>
> --
>
> From: "Dan Carpenter "
>
> commit 8612ed0d97abcf1c016d34755b7cf2060de71963 upstream
>
> Calling the WDIOC_GETSTATUS & WDIOC_GETBOOTSTATUS and twice will cause a
> interru
Hi Jonghwan,
> This patch looks like it should be in the 3.11-stable tree, should we apply
> it?
>
> --
>
> From: "Jingoo Han "
>
> commit 4c4e45669de475573b15d968a6dca8d00124c9ad upstream
>
> STAGE_CFG bits are defined as [5:4] bits. However, '(((x) & 0x30) << 4)'
> handles [9
19 matches
Mail list logo
