On Wed, Mar 25, 2015 at 12:23:19PM +0530, rtat...@codeaurora.org wrote:
> From: Rupesh Tatiya
>
> USB 2.01+ full-speed devices can have extended descriptor as well
> and can support LPM.
>
> Change-Id: Ic055d51c02651810d3eb7141bab20a090fe8453b
We can't take patches with this in it, as it makes
Greg Kroah-Hartman writes:
> 3.19-stable review patch. If anyone has any objections, please let me know.
>
> --
>
> From: RafaÅ MiÅecki
>
> commit 0ff66cffde47de51c155ebdd2356403276c04cc4 upstream.
>
> It was incorrectly detected as 2 GHz device.
>
> Signed-off-by: RafaÅ MiÅ
On Fri, 20 Mar 2015 08:32:12 -0500
, Rob Herring
wrote:
> On Fri, Mar 20, 2015 at 7:25 AM, Grant Likely wrote:
> > On Fri, 23 Jan 2015 17:10:04 +0100
> > , Geert Uytterhoeven
> > wrote:
> >> Currently OF_DYNAMIC and OF_OVERLAY are not visible to the user, and are
> >> selected automatically on
On Thu, 19 Mar 2015 19:39:27 +
, Will Deacon
wrote:
> On Thu, Mar 19, 2015 at 10:17:27AM +, Lorenzo Pieralisi wrote:
> > On Thu, Mar 19, 2015 at 04:09:33AM +, Hanjun Guo wrote:
> > > On 2015/3/19 3:05, Will Deacon wrote:
> > > > On Wed, Mar 11, 2015 at 12:39:26PM +, Hanjun Guo wro
From: Rupesh Tatiya
USB 2.01+ full-speed devices can have extended descriptor as well
and can support LPM.
Change-Id: Ic055d51c02651810d3eb7141bab20a090fe8453b
Signed-off-by: Rupesh Tatiya
---
drivers/usb/core/hub.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/us
Hi Sergey,
On Wed, 25 Mar 2015 14:42:30 +0900 Sergey Senozhatsky
wrote:
>
> On (03/24/15 14:03), a...@linux-foundation.org wrote:
> > The patch titled
> > Subject: zsmalloc: do not remap dst page while prepare next src page
> > has been added to the -mm tree. Its filename is
> > zsmal
I apologize for bringing this to the list, but after several hours of
google, testing, and so forth I'm coming up blank. I've been unable
to reproduce this state in targeted tests, however the application
itself does it on a semi-regular basis.
I currently have an application with the following s
Hi Rob,
On 15-03-22 06:20 PM, Rob Herring wrote:
On 03/20/2015 08:06 PM, Scott Branden wrote:
This patchset attempts to standardize the naming of dt-bindings
documents based on the Broadcom vendor prefix of brcm.
Although there are no guidelines currently present for how to name
the dt-binding
Make PCIE_IPROC depending on both OF and ARM and default to be disabled,
so it cannot be accidentally enabled by other platforms
PCIE_IPROC is meant to be enabled by a front-end bus driver. Curenntly
it's enabled by PCIE_IPROC_PLTFM driver
Signed-off-by: Ray Jui
---
drivers/pci/host/Kconfig |
This patch series contains two patches to address iProc PCIe Kconfig related
issues. The first patch adds more protection to PCIE_IPROC so it cannot be
accidentally enabled for non-ARM based platforms. The second patch changes the
config name of the iProc PCIe platform driver from PCIE_IPROC_PLTFM
Change the config name of the iProc PCIe platform bus driver from
PCIE_IPROC_PLTFM to PCIE_IPROC_PLATFORM
Signed-off-by: Ray Jui
---
drivers/pci/host/Kconfig |2 +-
drivers/pci/host/Makefile |2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/pci/host/Kconfig b
On Wed, Mar 25, 2015 at 07:23:52AM +0100, Julia Lawall wrote:
> Please take a look.
>
It is strange why I did not receive it.
The patch is ok.
Signed-off-by: Peter Chen
> thanks,
> julia
>
> On Wed, 25 Mar 2015, kbuild test robot wrote:
>
> > TO: Peter Chen
> > CC: "Greg Kroah-Hartman"
> >
Around Tue 24 Mar 2015 18:31:22 +0300 or thereabout, Andrey Ryabinin wrote:
> Almost all arches define ELF_ET_DYN_BASE as 2/3 of TASK_SIZE.
> Though it seems that some architectures do this in a wrong way.
> The problem is that 2*TASK_SIZE may overflow 32-bits so
> the real ELF_ET_DYN_BASE becomes
Hi Bjorn,
On 3/24/2015 5:28 PM, Bjorn Helgaas wrote:
> On Tue, Mar 24, 2015 at 12:33 AM, Ray Jui wrote:
>> Make PCIE_IPROC depending on both OF and ARM and default to be disabled,
>> so it cannot be accidentally enabled by other platforms
>>
>> PCIE_IPROC is meant to be enabled by a front-end bus
Please take a look.
thanks,
julia
On Wed, 25 Mar 2015, kbuild test robot wrote:
> TO: Peter Chen
> CC: "Greg Kroah-Hartman"
> CC: linux-...@vger.kernel.org
> CC: linux-kernel@vger.kernel.org
>
> drivers/usb/chipidea/usbmisc_imx.c:277:5-8: Unneeded variable: "ret". Return
> "0" on line 297
>
Setting oom_killer_disabled to false is atomic, there is no need for
further synchronization with ongoing allocations trying to OOM-kill.
Signed-off-by: Johannes Weiner
---
mm/oom_kill.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/mm/oom_kill.c b/mm/oom_kill.c
index 2b665da1b3c9..73763e
Hi Thierry,
After merging the drm-panel tree, today's linux-next build (powerpc
ppc64_defconfig) produced this warning:
drivers/video/fbdev/Kconfig:5:error: recursive dependency detected!
drivers/video/fbdev/Kconfig:5: symbol FB is selected by DRM_KMS_FB_HELPER
drivers/gpu/drm/Kconfig:34: sy
On 24 March 2015 at 18:58, Lorenzo Pieralisi wrote:
> If acpi=force is passed on the command line, it forces ACPI to be
> the only available boot method, hence it must be left enabled even
> if the initialization and sanity checks on ACPI tables fails.
>
> This patch refactors ACPI initialization
Disabling the OOM killer needs to exclude allocators from entering,
not existing victims from exiting.
Right now the only waiter is suspend code, which achieves quiescence
by disabling the OOM killer. But later on we want to add waits that
hold the lock instead to stop new victims from showing up
It turns out that the mechanism to wait for exiting OOM victims is
less generic than it looks: it won't issue wakeups unless the OOM
killer is disabled.
The reason this check was added was the thought that, since only the
OOM disabling code would wait on this queue, wakeup operations could
be save
The should_alloc_retry() function was meant to encapsulate retry
conditions of the allocator slowpath, but there are still checks
remaining in the main function, and much of how the retrying is
performed also depends on the OOM killer progress. The physical
separation of those conditions make the
The OOM killer connects random tasks in the system with unknown
dependencies between them, and the OOM victim might well get blocked
behind the task that is trying to allocate. That means that while
allocations can issue OOM kills to improve the low memory situation,
which generally frees more tha
__GFP_NOFAIL allocations can deadlock the OOM killer when they're
holding locks that the OOM victim might need to exit. When that
happens the allocation may never complete, which has disastrous
effects on things like in-flight filesystem transactions.
When the system is OOM, allow __GFP_NOFAIL al
There is not much point in rushing back to the freelists and burning
CPU cycles in direct reclaim when somebody else is in the process of
OOM killing, or right after issuing a kill ourselves, because it could
take some time for the OOM victim to release memory.
This is a very cold error path, so t
GFP_NOFS allocations are not allowed to invoke the OOM killer since
their reclaim abilities are severely diminished. However, without the
OOM killer available there is no hope of progress once the reclaimable
pages have been exhausted.
Don't risk hanging these allocations. Leave it to the alloca
When both page reclaim and the OOM killer fail to free memory, there
are no more options for the allocator to make progress on its own.
Don't risk hanging these allocations. Leave it to the allocation site
to implement the fallback policy for failing allocations.
Signed-off-by: Johannes Weiner
The zonelist locking and the oom_sem are two overlapping locks that
are used to serialize global OOM killing against different things.
The historical zonelist locking serializes OOM kills from allocations
with overlapping zonelists against each other to prevent killing more
tasks than necessary in
Hi everybody,
in the recent past we've had several reports and discussions on how to
deal with allocations hanging in the allocator upon OOM.
The idea of this series is mainly to make the mechanism of detecting
OOM situations reliable enough that we can be confident about failing
allocations, and
exit_oom_victim() already knows that TIF_MEMDIE is set, and nobody
else can clear it concurrently. Use clear_thread_flag() directly.
Signed-off-by: Johannes Weiner
---
mm/oom_kill.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/mm/oom_kill.c b/mm/oom_kill.c
index b2f081f
Rename unmark_oom_victim() to exit_oom_victim(). Marking and
unmarking are related in functionality, but the interface is not
symmetrical at all: one is an internal OOM killer function used during
the killing, the other is for an OOM victim to signal its own death on
exit later on. This has locki
On Tue, Mar 24, 2015 at 7:22 AM, James Hogan wrote:
> Hi Andrew,
>
> On 04/03/15 23:59, Andrew Bresticker wrote:
>> If a machine-specific hook is not implemented for restart, poweroff,
>> or halt, fall back to halting secondary CPUs, disabling interrupts,
>> and spinning. In the case of restart,
On 03/24/2015 11:24 PM, Nicholas Krause wrote:
Fixes memory leaks in the function,sa11xx_drv_pcmcia_probe for
when either clk_get returns a error value or when we cannot allocate
memory with the pointer sinfo to memory required for this function
to continue and return successfully. Further more
On Wed, Mar 25, 2015 at 7:00 AM, Andrew Morton
wrote:
> On Thu, 19 Mar 2015 23:04:39 +0900 Roman Pen wrote:
>
>> If suitable block can't be found, new block is allocated and put into a head
>> of a free list, so on next iteration this new block will be found first.
>>
>> ...
>>
>> Cc: sta...@vger
In the squashfs_symlink_readpage(), the return value should be -EIO
instead of 0 when the code fails in obtaining the information about
the symlink metadata.
Signed-off-by: Sanidhya Kashyap
---
fs/squashfs/symlink.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/squashfs/
On Sun, Feb 22, 2015 at 12:45:43AM +0900, Namjae Jeon wrote:
> From: Namjae Jeon
>
> FALLOC_FL_INSERT_RANGE command is the opposite command of
> FALLOC_FL_COLLAPSE_RANGE that is needed for advertisers or someone who want to
> add some data in the middle of file. FALLOC_FL_INSERT_RANGE will create
On (03/24/15 14:03), a...@linux-foundation.org wrote:
> The patch titled
> Subject: zsmalloc: do not remap dst page while prepare next src page
> has been added to the -mm tree. Its filename is
> zsmalloc-do-not-remap-dst-page-while-prepare-next-src-page.patch
>
> This patch should soon
On Tue, Mar 24, 2015 at 06:33:57PM -0500, Bjorn Helgaas wrote:
> On Tue, Mar 24, 2015 at 04:42:35PM +0100, Michael S. Tsirkin wrote:
> > pci_msi_init_pci_dev and pci_msi_off share a lot of code.
> > This used to be justified since pci_msi_init_pci_dev
> > wasn't compiled in when CONFIG_PCI_MSI is o
This patch fixes race condition between dvb_dmxdev_buffer_read and
dvb_demux_io_ioctl.
There are race conditions executing DMX_ADD_PID or DMX_REMOVE_PID in the
dvb_demux_ioctl when dvb_demux_read is waiting for the data by
wait_event_interruptible. So, this fixes to sleep with acquired mutex
and s
On Tue, Mar 24, 2015 at 10:28:05AM -0700, Dmitry Torokhov wrote:
> > > > > + err = input_register_device(vi->idev);
> > > > > + if (err)
> > > > > + goto err_input_register;
> > > > > +
> > > > > + return 0;
> > > > > +
> > > > > +err_input_register:
> > > >
> > > > > +
On Wed, Mar 25, 2015 at 01:51:43PM +1030, Rusty Russell wrote:
> Gerd Hoffmann writes:
> > virtio-input is basically evdev-events-over-virtio, so this driver isn't
> > much more than reading configuration from config space and forwarding
> > incoming events to the linux input layer.
> >
> > Signe
Ping.
On 03/16/2015 10:22 AM, Preeti U Murthy wrote:
> Hi Peter, Ingo, Thomas,
>
> Can you please take a look at the conversation on this thread ?
> This fix is urgent.
>
> Regards
> Preeti U Murthy
>
> On 03/02/2015 08:26 PM, Peter Zijlstra wrote:
>> On Fri, Feb 27, 2015 at 02:19:05PM +0530, P
On Tue, Mar 17, 2015 at 3:30 PM, Pantelis Antoniou
wrote:
> Add me as the device tree overlays maintainer.
>
> Signed-off-by: Pantelis Antoniou
Applied. Thanks.
Rob
> ---
> MAINTAINERS | 9 +
> 1 file changed, 9 insertions(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 0e1abe8.
On (03/25/15 14:05), Heesub Shin wrote:
> No, it's not unnecessary. We should do kunmap_atomic() in the reverse
> order of kmap_atomic(), so unfortunately it's inevitable to
> kunmap_atomic() both on d_addr and s_addr.
>
Andrew, can you please drop this patch?
> >
> > Signed-off-by: Sergey Sen
On Tue, Mar 17, 2015 at 3:30 PM, Pantelis Antoniou
wrote:
> Implement a throw once master enable switch to protect against any
> further overlay applications if the administrator desires so.
sysfs documentation?
> Signed-off-by: Pantelis Antoniou
> ---
> drivers/of/overlay.c | 66
> ++
On Tue, 2015-24-03 at 12:33:22 UTC, Jan Stancek wrote:
> One path in power_pmu_event_init() calls get_cpu_var(), but is
> missing matching call to put_cpu_var(), which causes preemption
> imbalance and crash in user-space:
>
> Page fault in user mode with in_atomic() = 1 mm = c01fefa5a280
>
2015-03-25 12:09 GMT+08:00 :
> From: Fu Wei
>
> This is a Chinese translated version of
> Documentation/arm64/legacy_instructions.txt
>
> It is based on the modifications of
> Documentation/arm64/legacy_instructions.txt in submission:
> "587064b6", "bd35a4ad", "2d888f48", "c852f320".
>
> Signed
This is the driver for the AXI Central Direct Memory Access (AXI
CDMA) core, which is a soft Xilinx IP core that provides high-bandwidth
Direct Memory Access (DMA) between a memory-mapped source address and a
memory-mapped destination address.
This module works on Zynq (ARM Based SoC) and Microbla
On Wed, Mar 25, 2015 at 12:25:59AM +0100, Willy Tarreau wrote:
> On Tue, Mar 24, 2015 at 02:56:33PM +0530, Sudip Mukherjee wrote:
> > with reference to the previous patch of the series, fixed the
> > lcd type in module parameters.
>
> Sudip, it's better to avoid fragmenting patches like you did, b
Hello,
On 03/25/2015 12:24 AM, Sergey Senozhatsky wrote:
> object may belong to different pages. zs_object_copy() handles
> this case and maps a new source page (get_next_page() and
> kmap_atomic()) when object crosses boundaries of the current
> source page. But it also performs unnecessary kunma
On Tue, Mar 17, 2015 at 3:30 PM, Pantelis Antoniou
wrote:
> During the course of the overlay selftests some of them remain
> applied. While this does not pose a real problem, make sure you track
> them and destroy them at the end of the test.
This is going to need to be rebased on my tree as ther
On Tue, Mar 24, 2015 at 06:56:05PM -0700, Bjorn Andersson wrote:
> Instead of resolving regulator supplies during registration move this to
> the time of a consumer retrieving a handle. The benefit is that it's
> possible for one driver to register regulators with internal
> dependencies out of ord
On Fri, Mar 13, 2015 at 2:21 PM, Frank Rowand wrote:
> From: Frank Rowand
>
> If CONFIG_OF_UNITTEST=y then a kernel image make will always cause .version to
> be incremented, even if there are not source changes. This is caused by
> a lack of dependency tracking and checking for
> drivers/of/uni
On Wed, Mar 11, 2015 at 3:36 AM, Wang Long wrote:
> This series patches do some small fixes in drivers/of/unittest.c,
> and update the Documenttion.
>
> At last, replace selftest with unittest in the c, dtsi
> and binding files.
>
> * v2 <- v1:
> - According to Gaurav's advice. make the re
This fixes the following sparse warnings:
make C=1 CF=-D__CHECK_ENDIAN__ net/tipc/name_table.o
net/tipc/name_table.c:977:17: error: incompatible types in comparison
expression (different address spaces)
net/tipc/name_table.c:977:17: error: incompatible types in comparison
expression (different a
On Tue, Mar 24, 2015 at 4:15 AM, Russell King - ARM Linux
wrote:
> On Mon, Mar 23, 2015 at 05:29:02PM +0100, Heiko Stuebner wrote:
>> Hi Rob, Philipp,
>>
>> Am Mittwoch, 11. März 2015, 09:51:21 schrieb Philipp Zabel:
>> > Am Dienstag, den 10.03.2015, 14:05 -0500 schrieb Rob Herring:
>> > > I've on
It was introduced in commit f2ca09f381a59
(ARM: 8311/1: Don't use is_module_addr in setting page attributes)
We have no need to check start twice, but see if end is also in range.
Signed-off-by: Hillf Danton
---
--- a/arch/arm/mm/pageattr.cWed Mar 25 11:55:13 2015
+++ b/arch/arm/mm/pageattr
On 03/23/2015 02:32 PM, Prarit Bhargava wrote:
> This patch splits rtc.txt into two separate files, one for the
> documentation itself, and the other for the rtctest.c file. The rtctest
> file is moved into the kernel tools/testing/selftests/timers directory.
> This will make automated testing eas
Hi Lee,
On Mon, Mar 9, 2015 at 10:28 AM, Lee Jones wrote:
> On Fri, 06 Mar 2015, Mike Turquette wrote:
>> Quoting Lee Jones (2015-03-04 04:00:03)
>> > Mike,
>> >
>> > Do you want me to resend this set with Robert's Reviewed-by applied,
>> > or are you happy to apply it yourself?
>>
>> No need for
Denys Vlasenko writes:
> On 03/23/2015 04:30 AM, Rusty Russell wrote:
>> + * They may be about to iret, where they asked us never to
>> + * deliver interrupts. In this case, we can emulate that iret
>> + * then immediately deliver the interrupt. This is bascia
Gerd Hoffmann writes:
> virtio-input is basically evdev-events-over-virtio, so this driver isn't
> much more than reading configuration from config space and forwarding
> incoming events to the linux input layer.
>
> Signed-off-by: Gerd Hoffmann
Is the input layer sane? I've never dealt with it
From: Fu Wei
This is a Chinese translated version of
Documentation/arm64/legacy_instructions.txt
It is based on the modifications of Documentation/arm64/legacy_instructions.txt
in submission:
"587064b6", "bd35a4ad", "2d888f48", "c852f320".
Signed-off-by: Fu Wei
---
Documentation/zh_CN/arm64
On Thu, 19 Mar 2015, Naoya Horiguchi wrote:
> This cleanup patch moves all strings passed to action_result() into a single
> array action_page_type so that a reader can easily find which kind of action
> results are possible. And this patch also fixes the odd lines to be printed
> out, like "unkno
On 03/20/2015 08:06 PM, Scott Branden wrote:
> This patchset attempts to standardize the naming of dt-bindings
> documents based on the Broadcom vendor prefix of brcm.
>
> Although there are no guidelines currently present for how to name
> the dt-bindings document the "vendor,binding.txt" style i
On Tue, Mar 24, 2015 at 10:02 PM, Hanjun Guo wrote:
> Some fixes since last version:
>
> - Add a patch 19/23 for disabling ACPI for Xen on ARM64 for now to fix
>compile errors on XEN ACPI, Stefano and Julien are ok with this
>temporary solution.
> - Add patch "ARM64 / ACPI: Don't unflatt
On 03/25/2015 at 12:54 AM, Josh Boyer wrote:
On Tue, Mar 24, 2015 at 12:49 PM, Daniel Vetter wrote:
On Tue, Mar 24, 2015 at 05:48:31PM +0100, Daniel Vetter wrote:
On Tue, Mar 24, 2015 at 12:10:28PM -0400, Josh Boyer wrote:
On Tue, Mar 24, 2015 at 10:46 AM, Josh Boyer wrote:
On Tue, Mar 24
On 03/25/2015 07:00 AM, Ingi Kim wrote:
This patch adds the device tree bindings for ktd2692 flash LEDs.
Add optional properties 'flash-timeout-us' to control flash timeout
and 'vin-supply' for flash-led regulator
Signed-off-by: Ingi Kim
---
.../devicetree/bindings/leds/leds-ktd2692.txt
On 03/25/2015 07:00 AM, Ingi Kim wrote:
This patch adds a driver to support the ktd2692 flash LEDs.
ktd2692 can control flash current by ExpressWire interface.
Signed-off-by: Ingi Kim
---
drivers/leds/Kconfig| 9 +
drivers/leds/Makefile | 1 +
drivers/leds/leds-ktd2692.c
On Tue, Mar 24, 2015 at 11:50:47AM -0700, Matt Mullins wrote:
> On Thu, Sep 25, 2014 at 04:33:38PM -0400, Matthew Wilcox wrote:
> > --- a/drivers/block/brd.c
> > +++ b/drivers/block/brd.c
> > @@ -97,13 +97,13 @@ static struct page *brd_insert_page(struct brd_device
> > *brd, sector_t sector)
> >
On Tue, Mar 24, 2015 at 05:20:13PM -0400, Len Brown wrote:
>
>
> On Thu, Nov 13, 2014 at 6:19 PM, Andi Kleen wrote:
> > From: Andi Kleen
> >
> > Add support for reading PCU power metrics on Sandy Bridge / Ivy Bridge EP
> > and Haswell Server in turbostat. This is done using the perf ABI,
> > us
On Wed, 18 Mar 2015 13:03:19 +0800 Yuanahn Liu
wrote:
> Hi,
>
> FYI, we noticed performance changes on `fsmark.files_per_sec' by
> d4b4c2cdffab86f5c7594c44635286a6d277d5c6:
>
> > commit d4b4c2cdffab86f5c7594c44635286a6d277d5c6
> > Author: s...@kernel.org
> > AuthorDate: Mon De
On Wed, 18 Mar 2015 13:00:30 +0800 Yuanahn Liu
wrote:
> Hi,
>
> FYI, we noticed performance changes on `fsmark.files_per_sec' by
> 4400755e356f9a2b0b7ceaa02f57b1c7546c3765:
>
> > commit 4400755e356f9a2b0b7ceaa02f57b1c7546c3765
> > Author: NeilBrown
> > AuthorDate: Thu Feb 26 1
On 03/24/2015 08:45 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.14.37 release.
There are 79 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 m
On Tue, Mar 24, 2015 at 09:27:00AM -0600, Jens Axboe wrote:
> Get the streamid from the file, if any, and set it on the bio.
>
> Signed-off-by: Jens Axboe
> ---
> fs/direct-io.c | 4
> 1 file changed, 4 insertions(+)
>
> diff --git a/fs/direct-io.c b/fs/direct-io.c
> index e181b6b2e297..5d
FYI, we noticed the below changes on
git://flatbed.openfabrics.org/~amirv/linux.git for-upstream
commit ccd57b1bd32460d27bbb9c599e795628a3c66983 ("rhashtable: Add immediate
rehash during insertion")
+-+++
|
On Tue, Mar 24, 2015 at 09:27:03AM -0600, Jens Axboe wrote:
> Signed-off-by: Jens Axboe
> ---
> fs/xfs/xfs_aops.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/fs/xfs/xfs_aops.c b/fs/xfs/xfs_aops.c
> index 3a9b7a1b8704..2b00a57732e3 100644
> --- a/fs/xfs/xfs_aops.c
> +++ b/fs/xfs/xfs_
On Tue, Mar 24, 2015 at 09:27:01AM -0600, Jens Axboe wrote:
> Add a streamid field to the writeback_control structure, and use
> it for the various parts of buffered writeback.
>
> Signed-off-by: Jens Axboe
> ---
> fs/buffer.c | 4 ++--
> fs/fs-writeback.c | 1 +
> fs/mpage
My driver allocates more than 40MB pages via alloc_page() at a time and
maps them at virtual address. Totally it uses 300~400MB pages.
If I run a heavy load test for a few days in 1GB memory system, I cannot
allocate even order=3 pages
because-of the external fragmentation.
I thought I needed a
On Tue, 2015-03-24 at 19:15 +0100, Sebastian Andrzej Siewior wrote:
> * Mike Galbraith | 2015-03-21 19:02:23 [+0100]:
>
> >> Steve, I'm still working on the fix we discussed using dummy irq_task.
> >> I should be able to submit some time next week, if still interested.
> >>
> >> Either that, or I
On 03/24/2015 08:45 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.19.3 release.
There are 123 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 m
On 03/24/2015 08:42 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.10.73 release.
There are 55 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 m
On Tue, 2015-03-24 at 19:10 +0100, Sebastian Andrzej Siewior wrote:
> * Steven Rostedt | 2015-03-19 12:26:11 [-0400]:
>
> >On Thu, 19 Mar 2015 09:17:09 +0100
> >Mike Galbraith wrote:
> >
> >
> >> (aw crap, let's go shopping)... so why is the one in timer.c ok?
> >
> >It's not. Sebastian, you said
On Tue, Mar 24, 2015 at 09:26:58AM -0600, Jens Axboe wrote:
> The top bits of bio->bi_flags are reserved for keeping the
> allocation pool, set aside the next four bits for carrying
> a stream ID. That leaves us with support for 15 streams,
> 0 is reserved as a "stream not set" value.
>
> Add help
On Tue, Mar 24, 2015 at 7:18 PM, Chengyu Song wrote:
> posix_lock_file_wait may fail under certain circumstances, and its result is
> usually checked/returned. But given the complexity of cifs, I'm not sure if
> the result is intentially left unchecked and always expected to succeed.
>
> Signed-of
Hello,
On 2015년 03월 25일 03:32, Rob Clark wrote:
> On Mon, Mar 16, 2015 at 4:05 AM, Daniel Vetter wrote:
>> On Fri, Mar 13, 2015 at 03:12:10PM -0400, Stephane Viau wrote:
>>> From: Beeresh Gopal
>>>
>>> Using fb modifier flag, support NV12MT format in MDP4.
>>>
>>> v2:
>>> - rework the modifier's
Hi all,
Today's linux-next merge of the net-next tree got conflicts in
net/ipv4/tcp_ipv4.c and net/ipv6/tcp_ipv6.c between commit d0c294c53a77
("tcp: prevent fetching dst twice in early demux code") from the tree
and commit f7e4eb03f9d9 ("inet: ip early demux should avoid request
sockets") from t
On Tue, 2015-02-03 at 12:39 +0100, Christophe Leroy wrote:
> csum_tcpudp_magic() is only a few instructions, and does not modifies any
> other
> register than the returned result. So it is not worth having it as a separate
> function and suffer function branching and saving of volatile registers.
On 03/24/2015 05:22 PM, David Rientjes wrote:
mempool_alloc() does not support __GFP_ZERO since elements may come from
memory that has already been released by mempool_free().
Remove __GFP_ZERO from mempool_alloc() in drbd_req_new() and properly
initialize it to 0.
This (and the other drbd pat
On 03/24/2015 05:21 PM, David Rientjes wrote:
blk_init_rl() allocates a mempool using mempool_create_node() with node
local memory. This only allocates the mempool and element list locally
to the requeue queue node.
What we really want to do is allocate the request itself local to the
queue. T
On Fri, 2015-27-02 at 22:22:54 UTC, Yannick Guerrini wrote:
> Change 'Kenrel' to 'Kernel'
>
> Signed-off-by: Yannick Guerrini
> ---
> arch/powerpc/include/asm/smu.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
If you're going to send spelling fix patches, please at least fix all the
From: Carlos Roberto Silveira Junior
---
kernel/sched/fair.c | 9 -
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
index 7ce18f3..834aa55 100644
--- a/kernel/sched/fair.c
+++ b/kernel/sched/fair.c
@@ -296,13 +296,12 @@ static inlin
On Tue, Mar 24, 2015 at 11:43:41AM +0100, Thierry Reding wrote:
> On Wed, Mar 18, 2015 at 02:38:18AM +0100, Linus Walleij wrote:
> > On Wed, Mar 11, 2015 at 12:05 PM, Thierry Reding
> > wrote:
> > > On Fri, Jan 16, 2015 at 09:06:14AM +0800, kbuild test robot wrote:
> > >> drivers/pwm/pwm-stmpe.c:9
Instead of resolving regulator supplies during registration move this to
the time of a consumer retrieving a handle. The benefit is that it's
possible for one driver to register regulators with internal
dependencies out of order.
Signed-off-by: Bjorn Andersson
---
drivers/regulator/core.c
>From 6cb5fffc41911a29212be52d4ce7e481f5077ccf Mon Sep 17 00:00:00 2001
From: "Tom(JeHyeon) Yeon"
Date: Thu, 19 Mar 2015 17:10:45 +0900
Subject: [PATCH] PM / Hiberante : optimize swsusp_free()
Our team developed the snapshot booting.
Fisrt of all, make a snapshot image, compress it and finally sa
Hi,
On Tue, Mar 24, 2015 at 06:58:15PM +0100, Dr. H. Nikolaus Schaller wrote:
> So you propose that the parent->child relationship is “control”? I.e. some
> channel which allows to address some bus client (through ) and
> control that devices.
>
> Makes sense. This is how i2c and spi clients are
On 03/24/2015 04:07 PM, Ming Lin-SSI wrote:
-Original Message-
From: Jens Axboe [mailto:ax...@kernel.dk]
Sent: Tuesday, March 24, 2015 10:27 AM
To: Matias Bjørling; Jens Axboe; linux-kernel@vger.kernel.org; linux-
fsde...@vger.kernel.org
Cc: Ming Lin-SSI
Subject: Re: [PATCH 1/6] block: ad
Signed-off-by: Bjorn Andersson
---
drivers/mmc/host/mmci.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/drivers/mmc/host/mmci.c b/drivers/mmc/host/mmci.c
index 7fe1619..fb26674 100644
--- a/drivers/mmc/host/mmci.c
+++ b/drivers/mmc/host/mmci.c
@@ -1613,7 +1613,10 @@ sta
On Tue, 2015-03-24 at 21:49 +0200, Alex Dowad wrote:
> On 20/03/15 01:54, Michael Ellerman wrote:
> > On Thu, 2015-03-19 at 09:22 +0200, Alex Dowad wrote:
> >> On 19/03/15 08:45, Michael Ellerman wrote:
> >>> On Fri, 2015-13-03 at 18:14:46 UTC, Alex Dowad wrote:
> The 'arg' argument to copy_th
block_truncate_page may fail under certain circumstances, so its result
should be checked.
Signed-off-by: Chengyu Song
---
fs/ufs/truncate.c | 7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/fs/ufs/truncate.c b/fs/ufs/truncate.c
index f04f89f..8b41f07 100644
--- a/fs/ufs/
This patch adds vendor prefix for Kinetic technologies
Signed-off-by: Ingi Kim
Acked-by: Rob Herring
---
Documentation/devicetree/bindings/vendor-prefixes.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/vendor-prefixes.txt
b/Documentation/devicetree/bi
This patch adds the device tree bindings for ktd2692 flash LEDs.
Add optional properties 'flash-timeout-us' to control flash timeout
and 'vin-supply' for flash-led regulator
Signed-off-by: Ingi Kim
---
.../devicetree/bindings/leds/leds-ktd2692.txt | 33 ++
1 file changed
1 - 100 of 1219 matches
Mail list logo
