Works exactly as __get_free_pages except it also tries to charge newly
allocated pages to kmemcg. It will be used by the next patch.
Signed-off-by: Vladimir Davydov
---
include/linux/gfp.h | 1 +
mm/page_alloc.c | 12
2 files changed, 13 insertions(+)
* Matt Fleming wrote:
> From: Ard Biesheuvel
>
> The new Properties Table feature introduced in UEFIv2.5 may split
> memory regions that cover PE/COFF memory images into separate code
> and data regions. Since these regions only differ in
On Sat, Sep 26, 2015 at 3:15 AM, Sudip Mukherjee
wrote:
> BTW, I had a doubt about drm drivers. Is there any library or test suite
> to test the driver? I am almost halfway in making a KMS driver for SM712
> but still don't know how to test it properly. I was thinkig
If dma_pool_alloc() fails we are jumping to fail and releasing all the
bd_tables which have been added to the chain but we missed freeing this
bd_table which was just allocated and still not added to the chain of
bd_table.
Signed-off-by: Sudip Mukherjee
---
Hi, Christoph, tj,
On 09/11/2015 08:14 AM, Christoph Lameter wrote:
On Thu, 10 Sep 2015, Tejun Heo wrote:
Why not just update node_data[]->node_zonelist in the first place?
Also, what's the synchronization rule here? How are allocators
synchronized against node hot [un]plugs?
Also,
On Thu, Sep 24, 2015 at 11:38:58PM +0800, Yingjoe Chen wrote:
> +struct mtk_smp_boot_info {
> + unsigned long smp_base;
...
> +static const struct mtk_smp_boot_info mtk_mt8135_tz_boot = {
> + 0x80002000, 0x3fc,
...
> +static const struct mtk_smp_boot_info mtk_mt6589_boot = {
> +
Hi tj,
On 09/11/2015 03:55 AM, Tejun Heo wrote:
Hello,
So, overall, I think this is the right way to go although I have no
idea whether the acpi part is okay.
Thank you very much for reviewing. :)
+/*
+ * Current allocated max logical CPU ID plus 1.
+ * All allocated CPU ID should be in
> Your approach finds a function definition.
Yes. - I assumed that it might also be relevant.
> My approach works on the call directly, using whatever type information is
> available.
The connection between the SmPL specification "f(...)@e" and the desired return
type
was not obvious for me
Hi,
while still playing with llvmlinux patches against Linux v4.3-rc2+ I
wondered about the diverse usage of memcpy() in several string*.[c,h]
files below x86 arch.
Just FYI: I am here on Ubuntu/precise AMD64.
The background is my build breaks again due to commit (see [1])...
"x86, efi,
Straigntforward conversion from
int has_N44_O17_errata[NR_CPUS]
to
DECLARE_BITMAP(has_N44_O17_errata, NR_CPUS)
Saves about 2 kbytes in bss for NR_CPUS=512.
Signed-off-by: Denys Vlasenko
CC: Viresh Kumar
CC: Rafael J. Wysocki
Straigntforward conversion from
int was_in_debug_nmi[NR_CPUS]
to
DECLARE_BITMAP(was_in_debug_nmi, NR_CPUS)
Saves about 2 kbytes in bss for NR_CPUS=512.
Signed-off-by: Denys Vlasenko
CC: Jason Wessel
CC: Ingo Molnar
CC:
On Thursday, September 24, 2015 at 10:50:07 AM UTC+8, Myron Stowe wrote:
> I've encountered numerous bugzilla reports related to platform BIOS' not
> programming valid values into a PCI device's Type 0 Configuration space
> "Expansion ROM Base Address" field (a.k.a. Expansion ROM BAR). The main
>
Add compaction callbacks for zpool compaction API extension.
Signed-off-by: Vitaly Wool
---
mm/zsmalloc.c | 15 +++
1 file changed, 15 insertions(+)
diff --git a/mm/zsmalloc.c b/mm/zsmalloc.c
index f135b1b..8f2ddd1 100644
--- a/mm/zsmalloc.c
+++
Hi Daniel,
On Thu, Sep 24, 2015 at 5:23 PM, Daniel Vetter wrote:
> On Thu, Sep 24, 2015 at 02:46:21PM +0200, Thomas Petazzoni wrote:
>> Or are there some plans to make the writing of DRM drivers for very
>> simple/trivial devices a bit simpler?
>
> Since years I'm trying to sell
We have requested the firmware and it was loaded but we missed releasing
it both on success and error.
Signed-off-by: Sudip Mukherjee
---
v1: relased the firmware only on the error path.
drivers/video/fbdev/broadsheetfb.c | 8 +---
1 file changed, 5 insertions(+), 3
Acked-by: Dimitri Sivanich
On Mon, Sep 21, 2015 at 03:48:19PM +0530, Sudip Mukherjee wrote:
> If kzalloc() fails then gms is NULL and we are returning NULL, but the
> functions which called this function gru_register_mmu_notifier() are not
> expecting NULL as the return. They
On Fri, Sep 25, 2015 at 05:52:37PM +0900, byungchul.p...@lge.com wrote:
> From: Byungchul Park
>
> hello,
>
> i have already sent this patch about 1 month ago.
> (see https://lkml.org/lkml/2015/8/13/160)
>
> now, i am resending the same patch with adding some additional
Hi, Rafael,
> -Original Message-
> From: linux-pm-ow...@vger.kernel.org [mailto:linux-pm-
> ow...@vger.kernel.org] On Behalf Of Rafael J. Wysocki
> Sent: Friday, September 25, 2015 9:57 PM
> To: Chen, Yu C
> Cc: Wysocki, Rafael J; jiang@linux.intel.com; Zhang, Rui; Brown, Len;
>
commit aa2110cb1a7510f9b834adfb39b05d4843a35d35
("ACPI: add boot option acpi=copy_dsdt to fix corrupt DSDT") added
copy_dsdt as an ACPI boot option, but did not add it to ACPI format options in
Documentation/kernel-parameters.txt. This patch fixes it.
Signed-off-by: Rami Rosen
The following changes since commit 1f93e4a96c9109378204c147b3eec0d0e8100fde:
Linux 4.3-rc2 (2015-09-20 14:32:34 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git/
tags/char-misc-4.3-rc3
for you to fetch changes up to
This patch is to the rtl871x_ioctl_linux.c that fixes up following
warning reported by checkpatch.pl :
- Comparisons should place the constant on the right side of the test
Signed-off-by: Punit Vara
---
drivers/staging/rtl8712/rtl871x_ioctl_linux.c | 16
1
On Fri, Sep 25, 2015 at 12:22 AM, Ingo Molnar wrote:
>
> * Kees Cook wrote:
>
>> On Thu, Sep 24, 2015 at 1:26 PM, Stephen Smalley wrote:
>> > Hi,
>> >
>> > With the attached config and 4.3-rc2 on x86_64, I see the following in
>> >
The following changes since commit 6ff33f3902c3b1c5d0db6b1e2c70b6d76fba357f:
Linux 4.3-rc1 (2015-09-12 16:35:56 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git/
tags/driver-core-4.3-rc3
for you to fetch changes up to
I think it "works" because the affected BIOSes don't put spaces between the
chunks. I have discussed this with Matt.
On September 26, 2015 10:01:14 AM PDT, Andy Lutomirski
wrote:
>On Fri, Sep 25, 2015 at 10:56 PM, Ingo Molnar wrote:
>>
>> So this commit
Hello,
On Sun, Sep 27, 2015 at 02:09:24AM +0900, Akinobu Mita wrote:
> @@ -420,7 +420,9 @@ static void blk_mq_sysfs_init(struct request_queue *q)
> /* see blk_register_queue() */
> void blk_mq_finish_init(struct request_queue *q)
> {
> + mutex_lock(>mq_freeze_lock);
>
On 09/26/2015 11:49 AM, Punit Vara wrote:
This patch is to the rtl871x_ioctl_linux.c that fixes up following
warning reported by checkpatch.pl :
- Comparisons should place the constant on the right side of the test
Signed-off-by: Punit Vara
This warning is crap. WTF
On 09/24/2015 02:11 AM, Lars Svensson wrote:
Fixing Sparse warnings in rtw_security.c. When checking crc, both
actual and expected value was converted to cpu endianness before
comparing, causing sparse warnings as below. Since the values are
read from the buffer in correct byte order the extra
Hi Valentin,
On Tue, Sep 22, 2015 at 07:28:23PM +0200, Valentin Rothberg wrote:
> From bceb7cace76aba9212db56be939bfecaacb75bc2 Mon Sep 17 00:00:00 2001
> From: Valentin Rothberg
> Date: Tue, 22 Sep 2015 19:00:40 +0200
> Subject: [PATCH] wm831x_power: Use IRQF_ONESHOT
Hi Marek,
On Fri, Sep 25, 2015 at 10:20:45PM +0200, Marek Belisko wrote:
> If either twl4030_charger or twl4030_madc is configured as MODULE,
> we get build (link) errors.
>
> To solve, the direct call of twl4030_get_madc_conversion() is replaced
> by a call to iio_read_channel_processed().
>
>
On Sat, Sep 26, 2015 at 11:15 PM, Larry Finger
wrote:
> On 09/26/2015 11:49 AM, Punit Vara wrote:
>>
>> This patch is to the rtl871x_ioctl_linux.c that fixes up following
>> warning reported by checkpatch.pl :
>>
>> - Comparisons should place the constant on the right
Hello, Tang.
On Sat, Sep 26, 2015 at 05:31:07PM +0800, Tang Chen wrote:
> >>@@ -307,13 +307,19 @@ static inline struct page *alloc_pages_node(int nid,
> >>gfp_t gfp_mask,
> >>if (nid < 0)
> >>nid = numa_node_id();
> >>+ if (!node_online(nid))
> >>+ nid =
Looks good. I actually just came up with exactly the same fix after
Keith told me to test hotplug for my nvme changes.
Reviewed-by: Christoph Hellwig
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
Hi
On Sat, Sep 26, 2015 at 8:01 PM, Geert Uytterhoeven
wrote:
> Hi Alex,
>
> On Sat, Sep 26, 2015 at 7:07 PM, Alex Deucher wrote:
>> On Sat, Sep 26, 2015 at 4:28 AM, Geert Uytterhoeven
>> wrote:
>>> On Thu, Sep 24, 2015 at 5:23
Hi Dimitry,
> Is it Debian-derivative by any chance? Their capslock setup is wonky
> because CapsLock key does no actually set up as a CapsLock but another
> modifier. Also is it in X or is it on text console? Because X handles
> led state on its own...
I'm on Fedora 22. Yeah, you're correct X
This driver supports the following functions:
- reading and settings time
- alarms when connected to an IRQ
- reading and clearing the voltage low flags
- nvram
Signed-off-by: Alexandre Belloni
---
drivers/rtc/Kconfig | 9 +
drivers/rtc/Makefile
On Sat, 26 Sep 2015, SF Markus Elfring wrote:
> >> The connection between the SmPL specification "f(...)@e" and the desired
> >> return type
> >> was not obvious for me so far.
> >
> > The nearest enclosing expression of the ) is the whole function call itself.
>
> Thanks for your explanation.
>
On Sat, 26 Sep 2015, Rafael J. Wysocki wrote:
> > > So something like:
> > >
> > > echo on >/sys/.../power/control (in case the device was
> > > already in runtime suspend with wakeups enabled)
> > > echo off >/sys/.../power/wakeup
> > > echo auto >/sys/.../power/control
On Sat, 26 Sep 2015, SF Markus Elfring wrote:
> >> * Will a command-line parameter like "--include-headers-for-types"
> >> be needed here?
> >
> > This argument is never needed. It is only an optimization. It means that
> > he header files are only considered when collecting type information,
Notifier callbacks for CPU_ONLINE action can be run on the other CPU
than the CPU which was just onlined. So it is possible for the
process running on the just onlined CPU to insert request and run
hw queue before establishing new mapping which is done by
blk_mq_queue_reinit_notify().
This can
CPU hotplug handling for blk-mq (blk_mq_queue_reinit) acquires
all_q_mutex in blk_mq_queue_reinit_notify() and then removes sysfs
entries by blk_mq_sysfs_unregister(). Removing sysfs entry needs to
be blocked until the active reference of the kernfs_node to be zero.
On the other hand, reading
There are several race conditions while freezing queue.
When unfreezing queue, there is a small window between decrementing
q->mq_freeze_depth to zero and percpu_ref_reinit() call with
q->mq_usage_counter. If the other calls blk_mq_freeze_queue_start()
in the window, q->mq_freeze_depth is
This patchset addresses several race conditions on cpu hotplug handling
for blk-mq. All problems can be reproducible by the following script.
while true; do
echo 0 > /sys/devices/system/cpu/cpu1/online
echo 1 > /sys/devices/system/cpu/cpu1/online
done &
while true; do
Hi Marek,
On Fri, Sep 25, 2015 at 10:20:47PM +0200, Marek Belisko wrote:
> Added new iio properties which are required for twl4030-charger driver and
> allow to use twl4030-madc indirectly.
>
> Signed-off-by: Marek Belisko
> ---
> arch/arm/boot/dts/twl4030.dtsi | 2 ++
> 1
On 09/26/2015 02:14 AM, Dmitry Torokhov wrote:
When configuring input device via input_configured callback we may
encounter errors (for example input_mt_init_slots() may fail). Instead
of continuing with half-initialized input device let's allow driver
indicate failures.
diff --git
If parkbd_allocate_serio() fails to allocate memory we are releasing the
parport but we missed unregistering the device. As a result this device
with exclusive access to that parport remains registered. And no other
device will be able to use that parport even though this driver has
failed to
The enable bit indexes for DCDC4 and DCDC5 regulators are off by 1.
We haven't run into any problems with this since either the regulators
aren't defined in the DT and aren't used, or all the DCDC regulators
have the "always-on" property set, as they are almost always used
for system critical
> It doesn't matter, as long as the type is available.
I suggest to make the circumstances better known when this will be the case.
>> How do you think about reuse another data type enumeration there?
>
> No idea what you mean by this.
A SmPL variable can also be connected with a data type
2015-09-22 14:27 GMT+09:00 Masahiro Yamada :
> Hi Russell,
>
>
> 2015-09-22 4:38 GMT+09:00 Russell King - ARM Linux :
>> On Fri, Sep 18, 2015 at 01:37:32PM +0900, Masahiro Yamada wrote:
>>> +/**
>>> + * __uniphier_cache_maint_common - run a
Hi,
On Tue, Sep 22, 2015 at 10:01:33PM +0200, Valentin Rothberg wrote:
> I CCed Anton, who signed with Mark the responsible commit.
mh Mark is now working for Linaro, so he probably didn't see this
thread and Anton no longer maintains the power-supply subsystem.
Maybe you could add support for
The following changes since commit 1f93e4a96c9109378204c147b3eec0d0e8100fde:
Linux 4.3-rc2 (2015-09-20 14:32:34 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git/ tags/tty-4.3-rc3
for you to fetch changes up to
The following changes since commit 6ff33f3902c3b1c5d0db6b1e2c70b6d76fba357f:
Linux 4.3-rc1 (2015-09-12 16:35:56 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git/
tags/staging-4.3-rc3
for you to fetch changes up to
The following changes since commit 6ff33f3902c3b1c5d0db6b1e2c70b6d76fba357f:
Linux 4.3-rc1 (2015-09-12 16:35:56 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git/ tags/usb-4.3-rc3
for you to fetch changes up to
On Fri, Sep 25, 2015 at 10:56 PM, Ingo Molnar wrote:
>
> So this commit worries me.
>
> This bug is a good find, and the fix is obviously needed and urgent, but I'm
> not
> sure about the implementation at all. (I've Cc:-ed a few more x86 low level
> gents.)
>
> * Matt Fleming
On Sat, Sep 26, 2015 at 05:52:09PM +0800, Tang Chen wrote:
> >>+static int allocate_logical_cpuid(int apicid)
> >>+{
> >>+ int i;
> >>+
> >>+ /*
> >>+* cpuid <-> apicid mapping is persistent, so when a cpu is up,
> >>+* check if the kernel has allocated a cpuid for it.
> >>+*/
>
On Saturday, September 26, 2015 11:24:06 PM punit vara wrote:
> On Sat, Sep 26, 2015 at 11:15 PM, Larry Finger
> wrote:
> > On 09/26/2015 11:49 AM, Punit Vara wrote:
> >>
> >> This patch is to the rtl871x_ioctl_linux.c that fixes up following
> >> warning reported by
* Denys Vlasenko wrote:
> For 64-bit kernels, MAX_LOCAL_APIC is 32k:
>
> #ifdef CONFIG_X86_32
> ...
> #else
> # define MAX_IO_APICS 128
> # define MAX_LOCAL_APIC 32768
> #endif
>
> (It seems to be a bit of a misnomer, it's not a maximum
> number of APICs we support, it's
Commit-ID: 597ee40722bf05195f91a41e88e15b79bdab152c
Gitweb: http://git.kernel.org/tip/597ee40722bf05195f91a41e88e15b79bdab152c
Author: Adrian Hunter
AuthorDate: Thu, 24 Sep 2015 13:05:21 +0300
Committer: Arnaldo Carvalho de Melo
CommitDate:
Commit-ID: b5cabbcbd157a4bf5a92dfc85134999a3b55342d
Gitweb: http://git.kernel.org/tip/b5cabbcbd157a4bf5a92dfc85134999a3b55342d
Author: Adrian Hunter
AuthorDate: Thu, 24 Sep 2015 13:05:22 +0300
Committer: Arnaldo Carvalho de Melo
CommitDate:
Commit-ID: 266fa2b22294909ddf6e7d2f8acfe07adf9fd978
Gitweb: http://git.kernel.org/tip/266fa2b22294909ddf6e7d2f8acfe07adf9fd978
Author: Arnaldo Carvalho de Melo
AuthorDate: Thu, 24 Sep 2015 11:24:18 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate:
On Thu, Sep 24, 2015 at 03:27:01PM +0300, Tomi Valkeinen wrote:
> Hi all,
>
> fbdev is (more or less) maintained, but it's a deprecated framework. All
> new Linux display drivers should be done on DRM.
>
> SM750 hardware seems to support multiple outputs, hardware overlays, 2D
> accelerator...
To collect function calls that have a return value of a given type t, it
should be sufficient to do the following:
@@
t e;
identifier f;
@@
f(...)@e
The @e notation reaches upwards to match the innermost enclosing term of
the right kind (here expression).
t can of course be arbitrarily
On Sat, 26 Sep 2015, SF Markus Elfring wrote:
> > Your approach finds a function definition.
>
> Yes. - I assumed that it might also be relevant.
>
>
>
> > My approach works on the call directly, using whatever type information is
> > available.
>
> The connection between the SmPL
braces {} are not necessary for single statement blocks
Signed-off-by: Alexandre Belloni
---
drivers/rtc/rtc-rx8025.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/rtc/rtc-rx8025.c b/drivers/rtc/rtc-rx8025.c
index
Toshiba laptops that feature WMI events for hotkeys were left unsupported
by the toshiba_acpi driver, however, commit a88bc06e5aec ("toshiba_acpi:
Avoid registering input device on WMI event laptops") added hardware
support for such laptops, but the hotkeys are not handled there.
This driver adds
On Sat, 26 Sep 2015, SF Markus Elfring wrote:
> > It doesn't matter, as long as the type is available.
>
> I suggest to make the circumstances better known when this will be the case.
It is like for the type of anything. If the declaration of the thing is
available with the type information, eg
CPU hotplug handling for blk-mq (blk_mq_queue_reinit) updates
q->mq_map by blk_mq_update_queue_map() for all request queues in
all_q_list. On the other hand, q->mq_map is released before deleting
the queue from all_q_list.
So if CPU hotplug event occurs in the window, invalid memory access
can
When unmapped hw queue is remapped after CPU topology is changed,
hctx->tags->cpumask has to be set after hctx->tags is setup in
blk_mq_map_swqueue(), otherwise it causes null pointer dereference.
Fixes: f26cdc8536 ("blk-mq: Shared tag enhancements")
Signed-off-by: Akinobu Mita
There is a race between cpu hotplug handling and adding/deleting
gendisk for blk-mq, where both are trying to register and unregister
the same sysfs entries.
null_add_dev
--> blk_mq_init_queue
--> blk_mq_init_allocated_queue
--> add to 'all_q_list' (*)
--> add_disk
CPU hotplug handling for blk-mq (blk_mq_queue_reinit) accesses
q->mq_usage_counter while freezing all request queues in all_q_list.
On the other hand, q->mq_usage_counter is deinitialized in
blk_mq_free_queue() before deleting the queue from all_q_list.
So if CPU hotplug event occurs in the
On 26 September 2015 at 10:20, H. Peter Anvin wrote:
> I think it "works" because the affected BIOSes don't put spaces between the
> chunks. I have discussed this with Matt.
>
Forgive the ASCII art but perhaps an illustration might help:
before the 2.5 feature, PE/COFF runtime
Hi David,
On Sat, Sep 26, 2015 at 8:13 PM, David Herrmann wrote:
> On Sat, Sep 26, 2015 at 8:01 PM, Geert Uytterhoeven
> wrote:
>> On Sat, Sep 26, 2015 at 7:07 PM, Alex Deucher wrote:
>>> On Sat, Sep 26, 2015 at 4:28 AM, Geert
4.2-stable review patch. If anyone has any objections, please let me know.
--
From: Sagi Grimberg
commit 8d5944d80359e645feb2ebd069a6f4caf7825e40 upstream.
If iser_initialize_task_headers() routine failed before
dma mapping, we should not attempt to unmap
4.2-stable review patch. If anyone has any objections, please let me know.
--
From: Sagi Grimberg
commit d16739055bd1f562ae4d83e69f7f7f1cefcfbe16 upstream.
Since commit "IB/iser: Fix race between iser connection teardown..."
iser_initialize_task_headers()
4.2-stable review patch. If anyone has any objections, please let me know.
--
From: Jaewon Kim
commit c54839a722a02818677bcabe57e957f0ce4f841d upstream.
reclaim_clean_pages_from_list() assumes that shrink_page_list() returns
number of pages removed
4.2-stable review patch. If anyone has any objections, please let me know.
--
From: Jack Morgenstein
commit 90c1d8b6350cca9d8a234f03c77a317a7613bcee upstream.
send_mad_to_wire takes the same spinlock that is taken in
the interrupt context.
4.2-stable review patch. If anyone has any objections, please let me know.
--
From: Tim Gardner
commit 1dadafa86a779884f14a6e7a3ddde1a57b0a0a65 upstream.
Commit 37b1ef31a568fc02e53587620226e5f3c66454c8 ("workqueue: move
flush_scheduled_work() to
4.2-stable review patch. If anyone has any objections, please let me know.
--
From: Haggai Eran
commit 11d748045c6dadb279d1acdb6d2ea8f3f2ede85b upstream.
The mlx5_ib_reg_user_mr() function will attempt to call clean_mr() in
its error flow even though
Its a bit odd that debugfs_create_bool() takes 'u32 *' as an argument,
when all it needs is a boolean pointer.
It would be better to update this API to make it accept 'bool *'
instead, as that will make it more consistent and often more convenient.
Over that bool takes just a byte.
That required
global_lock is defined as an unsigned long and accessing only its lower
32 bits from sysfs is incorrect, as we need to consider other 32 bits
for big endian 64-bit systems. There are no such platforms yet, but the
code needs to be robust for such a case.
Fix that by changing type of 'global_lock'
4.2-stable review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
commit eb38f3a4f6e86f8bb10a3217ebd85ecc5d763aae upstream.
We've got bug reports showing the old systemd-logind (at least
system-210) aborting unexpectedly, and this
4.2-stable review patch. If anyone has any objections, please let me know.
--
From: Dmitry Torokhov
commit e51e38494a8ecc18650efb0c840600637891de2c upstream.
Bit 2 of the mode byte has dual meaning: it can disable reporting of
gestures when touchpad
4.2-stable review patch. If anyone has any objections, please let me know.
--
From: Christophe Ricard
commit 8b706884eac958ec16518315053f77e052627084 upstream.
PCB_SYNC different than PCB_TYPE_SUPERVISOR or PCB_TYPE_DATAFRAME
should be discarded.
This is the start of the stable review cycle for the 4.2.2 release.
There are 134 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 made by Mon Sep 28 20:51:27 UTC 2015.
Anything
4.2-stable review patch. If anyone has any objections, please let me know.
--
From: Christophe Ricard
commit adca3c38d807b341a965d0aba8721d0784d8471b upstream.
When NFC_ATTR_VENDOR_DATA is not set, data_len is 0 and data is NULL.
Fixes the
4.2-stable review patch. If anyone has any objections, please let me know.
--
From: Pavel Fedin
commit c2f58514cfb374d5368c9da945f1765cd48eb0da upstream.
Until b26e5fdac43c ("arm/arm64: KVM: introduce per-VM ops"),
kvm_vgic_map_resources() used to include
4.2-stable review patch. If anyone has any objections, please let me know.
--
From: Paul Burton
commit 90996511187d6282db6d02d3f97006b4dbb5c457 upstream.
Commit b677bc03d757 ("MIPS: cps-vec: Use macros for various arithmetics
and memory operations")
4.2-stable review patch. If anyone has any objections, please let me know.
--
From: Shota Suzuki
commit 72ddef0506da852dc82f078f37ced8ef4d74a2bf upstream.
When initializing igb driver (e.g. 82576, I350), IGB_FLAG_QUEUE_PAIRS is
set if
4.2-stable review patch. If anyone has any objections, please let me know.
--
From: Christophe Ricard
commit fe202fe95564023223ce1910c9e352f391abb1d5 upstream.
NFC_ATTR_VENDOR_DATA is an optional vendor_cmd argument.
The current code was
Hi Linus,
Here are the outstanding target-pending fixes for v4.3-rc3 code.
Please go ahead and pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/nab/target-pending.git master
This includes a iser-target series from Jenny + Sagi @ Mellanox that
addresses the few remaining active I/O
4.2-stable review patch. If anyone has any objections, please let me know.
--
From: Christophe Ricard
commit e7723b33077b04648213f043bc22654c54e375e4 upstream.
Due to a copy and paste error st_nci_i2c_read still contains
st21nfca header comment.
4.2-stable review patch. If anyone has any objections, please let me know.
--
From: Will Deacon
commit 412fcb6cebd758d080cacd5a41a0cbc656ea5fce upstream.
We have a micro-optimisation on the fast syscall return path where we
take care to keep x0 live with
4.2-stable review patch. If anyone has any objections, please let me know.
--
From: Ard Biesheuvel
commit 674c242c9323d3c293fc4f9a3a3a619fe3063290 upstream.
When a task calls execve(), its FP/SIMD state is flushed so that
none of the original
On 09/26/2015 01:54 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.1.9 release.
There are 159 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
Currently, BG2Q shares a compatible with BG2. This is incorrect, since
BG2 and BG2Q use different USB PLL dividers. In reality, BG2Q shares a
divider with BG2CD. Change BG2Q's USB PHY compatible string to reflect
that.
Signed-off-by: Thomas Hebb
Cc: sta...@vger.kernel.org
The previous register layout was incorrect, many of the fields having
fewer bits than were needed to represent all their modes. The new layout
is taken from the bootloader source of a BG2CD device.
Signed-off-by: Thomas Hebb
---
drivers/pinctrl/berlin/berlin-bg2cd.c | 62
4.2-stable review patch. If anyone has any objections, please let me know.
--
From: Trond Myklebust
commit 7c2dad99d60c86ec686b3bfdcb787c450a7ea89f upstream.
Chuck reports seeing cases where a GETATTR that happens to race
with an asynchronous
4.2-stable review patch. If anyone has any objections, please let me know.
--
From: Trond Myklebust
commit 6f536936b79bd4b5cea8fb0e5b8b0bce8cd1ea4a upstream.
- Switch back to using list_for_each_entry(). Fixes an incorrect test
for list NULL
4.2-stable review patch. If anyone has any objections, please let me know.
--
From: Kinglong Mee
commit 18e3b739fdc826481c6a1335ce0c5b19b3d415da upstream.
---Steps to Reproduce--
# cat /etc/exports
/nfs/referal
4.2-stable review patch. If anyone has any objections, please let me know.
--
From: Trond Myklebust
commit 86d80f973434de24d8a807a92cd59d5ced7bd519 upstream.
pnfs_layout_mark_request_commit() needs to ensure that it adds the
request to the
4.2-stable review patch. If anyone has any objections, please let me know.
--
From: Trond Myklebust
commit e9ae58aeee8842a50f7e199d602a5ccb2e41a95f upstream.
We should ensure that we always set the pgio_header's error field
if a READ or WRITE
501 - 600 of 946 matches
Mail list logo