Add missing arch code - arch_trace_is_compat_syscall and
arch_syscall_addr
Signed-off-by: Marcin Nowakowski
Cc: Steven Rostedt
Cc: Ingo Molnar
Cc: Martin Schwidefsky
Cc: Heiko Carstens
The patch
ASoC: Intel: haswell depends on sst-firmware
has been applied to the asoc tree at
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to
Tejun Heo writes:
> Hello, Michael.
>
> On Mon, Oct 10, 2016 at 09:22:55PM +1100, Michael Ellerman wrote:
>> This patch seems to be causing one of my Power8 boxes not to boot.
>>
>> Specifically commit 3347fa092821 ("workqueue: make workqueue available
>> early during boot") in
Commit c6017e793b93 ("virtio: console: add locks around buffer removal
in port unplug path") added locking around the freeing of buffers in the
vq. However, when free_buf() is called with can_sleep = true and rproc
is enabled, it calls dma_free_coherent() directly, requiring interrupts
to be
The Xen docs specify several flags which a guest can set to advertise
which values of the xenstore control/shutdown key it will recognize.
This patch adds code to write all the relevant feature-flag keys.
Based-on-patch-by: Paul Durrant
Signed-off-by: Juergen Gross
Display name of feature instead of just the number
during recording data.
Before:
failed to write feature 13
Now:
failed to write feature HEADER_CPU_TOPOLOGY
Link: http://lkml.kernel.org/n/tip-k9d9trozi5kkx737cy8n5...@git.kernel.org
Signed-off-by: Jiri Olsa
---
Sukadev reported segfault on releasing perf env's numa data.
It's due to nr_numa_nodes being set no matter if the numa
data gets parsed properly. The perf_env__exit crash the on
releasing non existed data.
Setting nr_numa_nodes only when data are parsed out properly.
Reported-by: Sukadev
Add a possibility to disable source line column with
new --no-source option. It source line data could take
lot of time to retrieve, so it could be a performance
burden for big data.
Link: http://lkml.kernel.org/n/tip-8p6s2727fq8nbsm3it5gi...@git.kernel.org
Signed-off-by: Jiri Olsa
On Mon, Oct 10, 2016 at 8:05 PM, CAI Qian wrote:
> It usually report failures when enabled KASAN (inline) and
> CONFIG_KPROBES_SANITY_TEST on today's
> mainline HEAD. Occasionally, kernel panic with trace at the bottom.
Hi CAI,
This is a KASAN false positive. 0xf1-0xf4
hi,
sending few perf.data header fixes and adding
two new c2c report options.
Also available in:
git://git.kernel.org/pub/scm/linux/kernel/git/jolsa/perf.git
perf/fixes
thanks,
jirka
---
Jiri Olsa (6):
perf report: Move captured info to generic header info
perf header: Display
Dne 11.10.2016 v 15:10 Michal Marek napsal(a):
> Dne 30.9.2016 v 01:26 Stephen Rothwell napsal(a):
>> Hi all,
>>
>> On Tue, 20 Sep 2016 10:55:32 +0800 kernel test robot
>> wrote:
>>>
>>> FYI, we noticed the following commit:
>>>
>>>
On Sat, 08 Oct 2016, Vadim Lobanov wrote:
> I'm seeing a repeatable crash on my HP EliteBook 840 G2/2216 when
> booting it while in a docking station connected to two external
> DisplayPort monitors, undocking, and then either logging out or
> shutting down -- regardless
On Sun, Oct 09, 2016 at 09:23:58PM +0200, Thomas Gleixner wrote:
> On Sun, 9 Oct 2016, Rich Felker wrote:
> > On Sun, Oct 09, 2016 at 01:03:10PM +0200, Thomas Gleixner wrote:
> > My preference would just be to keep the branch, but with your improved
> > version that doesn't need a function call:
>
On 10/11/2016 11:19 AM, Dave Jones wrote:
On Tue, Oct 11, 2016 at 04:11:39PM +0100, Al Viro wrote:
> On Tue, Oct 11, 2016 at 10:45:08AM -0400, Dave Jones wrote:
> > This is from Linus' current tree, with Al's iovec fixups on top.
>
> Those iovec fixups are in the current tree...
ah yeah,
On Tue, Oct 11, 2016 at 03:53:57PM +0100, Brian Starkey wrote:
> Hi,
>
> This RFC series introduces a new connector type:
> DRM_MODE_CONNECTOR_WRITEBACK
> It is a follow-on from a previous discussion: [1]
>
> Writeback connectors are used to expose the memory writeback engines
> found in some
On Tue, Oct 11, 2016 at 05:04:34PM +0200, Heinz Mauelshagen wrote:
>
> Andy,
>
> good catch.
>
> We should rather check for V190 support only in case any
> compat feature flags are actually set.
>
> {
> + if (le32_to_cpu(sb->compat_features) &&
> +
On 10/10/2016 12:41 PM, Kyle Roeschley wrote:
Because the SMSC PHY completes auto-negotiation before the driver is
ready to handle interrupts, the PHY state machine never realizes that we
have a link. Clear the ANENABLE bit on initialization, which lets
genphy_config_aneg do its thing when that
Some clocks still use an explicit list of arguments, which make it a bit
more tedious to add new parameters.
Convert those over to a structure pointer argument to add as many
arguments as possible without having to many noise in our patches, or a
very long list of arguments.
Signed-off-by:
On Tue, Oct 11 2016 at 10:28am -0400,
Andy Whitcroft wrote:
> In commit ecbfb9f118bce4 ("dm raid: add raid level takeover support") a new
> compatible feature flag was added. Validation for these compat_features
> was added but this only passes for new raid mappings with
Dear Concern,
I am Talent Scout For BLUE SKY FILM STUDIO, Present Blue sky Studio a
Film Corporation Located in the United State, is Soliciting for the
Right to use Your Photo/Face and Personality as One of the Semi -Major
Role/ Character in our Upcoming ANIMATED Stereoscope 3D Movie-The Story
of
Mali-DP has a memory writeback engine which can be used to write the
composition result to a memory buffer.
Expose this functionality as a DRM writeback connector on supported
hardware.
Signed-off-by: Brian Starkey
---
drivers/gpu/drm/arm/Makefile |1 +
So that userspace can determine what pixel formats are supported for a
writeback connector's framebuffer, add a pixel format list to writeback
connectors. This is in the form of an immutable blob containing an array
of formats, and an immutable uint holding the array size.
Signed-off-by: Brian
From: Liviu Dudau
Mali-DP display processors are able to write the composition result to a
memory buffer via the SE.
Add entry points in the HAL for enabling/disabling this feature, and
implement support for it on DP650 and DP550. DP500 acts differently and
so is omitted
Implement the CRTC/Plane disable functionality of drm_framebuffer_remove
using the atomic API, and use it if possible.
For atomic drivers, this removes the possibility of several commits when
a framebuffer is in use by more than one CRTC/plane.
Additionally, this will provide a suitable place to
Expose the framebuffer for writeback connectors to userspace by
attaching the fb_id property to them.
Signed-off-by: Brian Starkey
---
drivers/gpu/drm/drm_atomic.c|9 +
drivers/gpu/drm/drm_connector.c |4
2 files changed, 13 insertions(+)
diff
Add a framebuffer to the connector state, for use as the output target
by writeback connectors.
If a framebuffer is in use by a writeback connector when userspace
removes it, it is handled by removing the framebuffer from the connector.
Signed-off-by: Brian Starkey
---
Add a layer bit for the SE memory-write, and add it to the pixel format
matrix for DP550/DP650.
Signed-off-by: Brian Starkey
---
drivers/gpu/drm/arm/malidp_hw.c | 28 ++--
drivers/gpu/drm/arm/malidp_hw.h |1 +
2 files changed, 15
Writeback connectors represent writeback engines which can write the
CRTC output to a memory framebuffer.
Add a writeback connector type, hidden from userspace behind a client
cap. They are hidden from non-aware clients so that they do not attempt
to use writeback connectors to provide visual
We're going to use the same format list for output formats, so rename
everything related to input formats to avoid confusion.
Signed-off-by: Brian Starkey
Reviewed-by: Liviu Dudau
---
drivers/gpu/drm/arm/malidp_hw.c | 24
2016-10-11 20:17+0800, Wanpeng Li:
> From: Wanpeng Li
>
> Most windows guests still utilize APIC Timer periodic/oneshot mode
> instead of tsc-deadline mode, and the APIC Timer periodic/oneshot
> mode are still emulated by high overhead hrtimer on host. This patch
>
On Mon, Oct 10, 2016 at 4:48 PM, Kees Cook wrote:
> On Fri, Oct 7, 2016 at 10:28 PM, Joel Fernandes wrote:
>> In preparation of not locking at all for certain buffers depending on if
>> there's contention, make locking optional depending if caller
Hi,
This patch set reworks the Allwinner pinctrl driver to support the generic
pin configuration and multiplexing bindings.
In the process, we also covered some lasting issues that were found: we
were ignoring the case where no pull-up was set, and while our binding was
saying that the
In order to support more easily the generic pinctrl properties, rework the
pinctrl maps configuration and split it into several sub-functions.
One of the side-effects from that rework is that we only parse the pin
configuration once, since it's going to be common to every pin, instead of
having
Since we have some bindings header for our hardcoded flags, let's use them
when we can.
Acked-by: Chen-Yu Tsai
Signed-off-by: Maxime Ripard
---
drivers/pinctrl/sunxi/pinctrl-sunxi.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
Now that we can handle the generic pinctrl bindings, convert our DT to it.
Signed-off-by: Maxime Ripard
---
arch/arm/boot/dts/ntc-gr8-evb.dts| 16 +-
arch/arm/boot/dts/ntc-gr8.dtsi | 76 +--
Our bindings are mostly irrelevant now that we have generic pinctrl
bindings that cover exactly the same uses cases.
Add support for the new ones, and obviously keep our old binding support in
order to keep the ABI stable.
Acked-by: Chen-Yu Tsai
Signed-off-by: Maxime Ripard
On Oct 10 2016 or thereabouts, Dmitry Torokhov wrote:
> Hi Benjamin,
>
> On Mon, Oct 10, 2016 at 9:42 AM, Benjamin Tissoires
> wrote:
> > The Thinkpad series 13 uses Host Notify to report the interrupt.
> > Add elan_smb_alert() to handle those interrupts and
The patch adds watchdog support for Loongson1B/1C board.
Signed-off-by: Yang Ling
---
V1.1:
Add watchdog support for Loongson1B.
---
arch/mips/configs/loongson1c_defconfig | 4
arch/mips/include/asm/mach-loongson32/platform.h | 1 +
Hi all,
please ignore this patch since it includes a build error
i resend the fixed patch in v2 version
i am sorry for my incaution
On 2016/10/11 21:03, zijun_hu wrote:
> From: zijun_hu
>
> as shown by pcpu_build_alloc_info(), the number of units within a percpu
> group is
Modify the current clocks we have to be able to specify the minimum for
each clocks we support, just like we support the max.
Signed-off-by: Maxime Ripard
---
drivers/clk/sunxi-ng/ccu_mult.c | 7 ++-
drivers/clk/sunxi-ng/ccu_nk.c | 12
In commit ecbfb9f118bce4 ("dm raid: add raid level takeover support") a new
compatible feature flag was added. Validation for these compat_features
was added but this only passes for new raid mappings with this feature
flag. This causes previously created raid mappings to be failed at import.
Hi,
As it was in the first iteration, this is the A64 support based on the
new sunxi-ng clock framework.
The support for it is quite minimal at the moment, but it should be
fairly easy to add new devices, as most of the design is shared with
older SoCs.
Let me know what you think,
Maxime
From: Andre Przywara
Signed-off-by: Andre Przywara
Acked-by: Rob Herring
Acked-by: Chen-Yu Tsai
[Maxime: Change title prefix to match the usual style]
Signed-off-by: Maxime Ripard
Rename the structures meant to be embedded in other structures to make it
consistent with the mux structure name
Signed-off-by: Maxime Ripard
---
drivers/clk/sunxi-ng/ccu_div.h | 6 +++---
drivers/clk/sunxi-ng/ccu_frac.c | 12 ++--
From: Chao Yu
During free nid allocation, in order to do preallocation, we will tag free
nid entry as allocated one and still leave it in free nid list, for other
allocators who want to grab free nids, it needs to traverse the free nid
list for lookup. It becomes overhead in
From: Chao Yu
Rename free nid cache operation for readability, no functionality change.
Signed-off-by: Chao Yu
---
fs/f2fs/node.c | 28 +---
1 file changed, 17 insertions(+), 11 deletions(-)
diff --git a/fs/f2fs/node.c
From: Chao Yu
Introduce new help __insert_nid_to_list and __remove_nid_from_list to
clean up nid list related codes.
Signed-off-by: Chao Yu
---
fs/f2fs/node.c | 66 --
fs/f2fs/node.h | 5 +
2
> I wonder what's worse - comparing SKU strings - we know that from the MCE
> recovery experience - or poking at maybe nonexistent MSRs? :-)
>
> I guess the latter is cleaner so let's try it.
Vikas got beat up for comparing SKU strings, so the probe method
was offered as an alternative. It's
Hi,
On Tue, Oct 11, 2016 at 09:47:04AM +0200, Pavel Machek wrote:
> Hi, Sebastian!
>
> I got some free cycles to play with n900 and bluetooth. There's still
> some unrelated config option that breaks even the old vesion of
> patches, but I'm ready for more debugging now.
>
> Could I have the
On 10/11/2016 07:10 AM, Yang Ling wrote:
Add watchdog timer specific driver for Loongson1 SoC.
Signed-off-by: Yang Ling
---
V1.1:
Add a little debugging information.
---
drivers/watchdog/Kconfig | 7 ++
drivers/watchdog/Makefile| 1 +
The residue calculation was taking in consideration that dma
transaction status will be always retrieved in the dma callback
used to inform that dma transfer is complete. However this is not
the case for all subsystems that use dma. Some subsystems use a
timer to check the dma status periodically.
As we add more features, it makes sense to skip all the features not
supported by the smart layer together, instead of checking each one
individually. Achieve this by refactoring the plane init loop.
Signed-off-by: Brian Starkey
Acked-by: Liviu Dudau
From: Andre Przywara
The Pine64 is a cost-efficient development board based on the
Allwinner A64 SoC.
There are three models: the basic version with Fast Ethernet and
512 MB of DRAM (Pine64) and two Pine64+ versions, which both
feature Gigabit Ethernet and additional
From: Liviu Dudau
config_valid variable is used to signal the activation of the CVAL
request when the vsync interrupt has fired. malidp_set_and_wait_config_valid()
uses the variable in wait_event_interruptible_timeout without clearing it
first, so the wait is skipped.
While the rational library works great, it doesn't really allow us to add
more constraints, like the minimum.
Remove that in order to be able to deal with the constraints we'll need.
Signed-off-by: Maxime Ripard
---
drivers/clk/sunxi-ng/Kconfig| 3 +--
Different hardware versions have different requirements when it comes to
pitch alignment. Add a function which can be used to check pitch
alignment for a device.
Signed-off-by: Brian Starkey
---
drivers/gpu/drm/arm/malidp_hw.c |3 +++
drivers/gpu/drm/arm/malidp_hw.h |
Allow the CCU drivers to specify a multiplier for their clocks.
Signed-off-by: Maxime Ripard
---
drivers/clk/sunxi-ng/ccu_mult.c | 2 +-
drivers/clk/sunxi-ng/ccu_mult.h | 13 +
drivers/clk/sunxi-ng/ccu_nk.c | 8
On 10/11/2016 12:47 AM, Nicholas Piggin wrote:
On Mon, 10 Oct 2016 07:15:11 -0700
Guenter Roeck wrote:
On 10/09/2016 10:49 PM, Nicholas Piggin wrote:
On Sun, 9 Oct 2016 08:21:21 -0700
Guenter Roeck wrote:
Nicholas,
some of my qemu tests for ppc64
in_interrupt() returns a nonzero value when we are either in an
interrupt or have bh disabled via local_bh_disable(). Since we are
interested in only ignoring coverage from actual interrupts, do a
proper check instead of just calling in_interrupt().
As a result of this change, kcov will start to
Hi Linus,
The following changes since commit 3be7988674ab33565700a37b210f502563d932e6:
Linux 4.8-rc7 (2016-09-18 17:27:41 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git
tags/iommu-updates-v4.9
for you to fetch changes up to
On Tue, Oct 11, 2016 at 03:30:20PM +0200, Arnd Bergmann wrote:
> I've attached the three .config files here, but due to the size I
> don't know if they make it to the list or your inbox. Let me
> know if you get them, and if you are able to reproduce the problem.
>
> The compiler version I used
Linus,
The following changes since commit 3be7988674ab33565700a37b210f502563d932e6:
Linux 4.8-rc7 (2016-09-18 17:27:41 -0700)
are available in the git repository at:
git://git.infradead.org/linux-ubifs.git tags/upstream-4.9-rc1
for you to fetch changes up to
On Mon, Oct 10, 2016 at 9:08 PM, Alexey Kardashevskiy wrote:
> On 11/10/16 02:23, Alexander Duyck wrote:
>> On Wed, Sep 28, 2016 at 10:21 PM, Alexey Kardashevskiy
>> wrote:
>>> There is at least one Chelsio 10Gb card which uses VPD area to store
>>> some custom
On Tue, Oct 11, 2016 at 11:20:41AM -0400, Chris Mason wrote:
>
>
> On 10/11/2016 11:19 AM, Dave Jones wrote:
> > On Tue, Oct 11, 2016 at 04:11:39PM +0100, Al Viro wrote:
> > > On Tue, Oct 11, 2016 at 10:45:08AM -0400, Dave Jones wrote:
> > > > This is from Linus' current tree, with Al's
On Tue, Oct 11, 2016 at 03:54:04PM +0100, Brian Starkey wrote:
> So that userspace can determine what pixel formats are supported for a
> writeback connector's framebuffer, add a pixel format list to writeback
> connectors. This is in the form of an immutable blob containing an array
> of formats,
On Tue, Oct 11, 2016 at 03:53:59PM +0100, Brian Starkey wrote:
> Writeback connectors aren't much use to the fbdev helpers, as they won't
> show anything to the user. Skip them when looking for candidate output
> configurations.
>
> Signed-off-by: Brian Starkey
> ---
>
On 10/11/2016 05:38 PM, Andy Whitcroft wrote:
On Tue, Oct 11, 2016 at 05:04:34PM +0200, Heinz Mauelshagen wrote:
Andy,
good catch.
We should rather check for V190 support only in case any
compat feature flags are actually set.
{
+ if (le32_to_cpu(sb->compat_features) &&
+
Ian Kent writes:
> For the autofs module to be able to reliably check if a dentry is a
> mountpoint in a multiple namespace environment the ->d_manage() dentry
> operation will need to take a path argument instead of a dentry.
Taking a quick look overall I see no issues with
Split out malidp_fini as the opposite of malidp_init. This helps keep
the cleanup paths neat and easier to manage.
Signed-off-by: Brian Starkey
---
drivers/gpu/drm/arm/malidp_drv.c | 12
1 file changed, 8 insertions(+), 4 deletions(-)
diff --git
Add watchdog timer specific driver for Loongson1 SoC.
Signed-off-by: Yang Ling
---
V1.1:
Add a little debugging information.
---
drivers/watchdog/Kconfig | 7 ++
drivers/watchdog/Makefile| 1 +
drivers/watchdog/loongson1_wdt.c | 160
On Tue, Oct 11, 2016 at 9:09 AM, Chris Rorvick wrote:
> I didn't receive your email so I'll try to respond via Paul's.
>>> If this is really bothering you, I guess I could apply this patch for
>>> now. But as I said, this is not solving the actual problem.
>>
>> Bikeshedding:
Check that the framebuffer pitches are appropriately aligned when
checking planes.
Signed-off-by: Brian Starkey
---
drivers/gpu/drm/arm/malidp_planes.c | 15 ++-
1 file changed, 14 insertions(+), 1 deletion(-)
diff --git
Always enable pixel-level alpha blending with the background, so that
buffers which include an alpha channel are displayed correctly.
Signed-off-by: Brian Starkey
---
drivers/gpu/drm/arm/malidp_planes.c | 32 ++--
1 file changed, 26
Save a search through the format lists at commit-time by storing the
internal format ID and number of planes in our plane state.
Signed-off-by: Brian Starkey
---
drivers/gpu/drm/arm/malidp_drv.h|3 +++
drivers/gpu/drm/arm/malidp_planes.c | 27
From: Liviu Dudau
Mali DP driver does not use drm_irq_{un,}install() function so the
drm->irq_enabled flag does not get set automatically.
drm_wait_vblank() checks the value of the flag among other functions.
Signed-off-by: Liviu Dudau
---
Hi,
This
On Tue, Oct 11, 2016 at 03:26:02PM +0100, Brian Starkey wrote:
> From: Liviu Dudau
>
> Mali DP driver does not use drm_irq_{un,}install() function so the
> drm->irq_enabled flag does not get set automatically.
> drm_wait_vblank() checks the value of the flag among other
Andy,
good catch.
We should rather check for V190 support only in case any
compat feature flags are actually set.
I.e.:
diff --git a/drivers/md/dm-raid.c b/drivers/md/dm-raid.c
index 8abde6b..2a39700 100644
--- a/drivers/md/dm-raid.c
+++ b/drivers/md/dm-raid.c
@@ -2258,7 +2258,8 @@ static
On Tue, Oct 11, 2016 at 10:45:08AM -0400, Dave Jones wrote:
> This is from Linus' current tree, with Al's iovec fixups on top.
Those iovec fixups are in the current tree... TBH, I don't see anything
in splice-related stuff that could come anywhere near that (short of
some general memory
On Fri 2016-10-07 12:31:41, Andy Lutomirski wrote:
> On 06/25/2016 09:18 AM, Chen Yu wrote:
> >There is requirement that we need to do some arch-specific
> >operations before putting the nonboot CPUs offline/online.
> >One of the requirements comes from the hibernation resume
> >process on x86_64,
On Tue, Oct 11, 2016 at 6:08 AM, Jan Beulich wrote:
Andrew Cooper 10/10/16 6:44 PM >>>
>>On 10/10/16 01:35, Haozhong Zhang wrote:
>>> Xen hypervisor needs assistance from Dom0 Linux kernel for following tasks:
>>> 1) Reserve an area on NVDIMM
(spoiler alert: another bad gcc bug which is truncating functions...)
On Tue, Oct 11, 2016 at 10:05:41AM -0500, Josh Poimboeuf wrote:
> On Tue, Oct 11, 2016 at 03:30:20PM +0200, Arnd Bergmann wrote:
> > I've attached the three .config files here, but due to the size I
> > don't know if they make
On 10/08/2016 02:05 AM, Hillf Danton wrote:
On Friday, October 07, 2016 5:01 AM Chris Friesen
I have Linux host running as a kvm hypervisor. It's running CentOS. (So the
kernel is based on 3.10 but with loads of stuff backported by RedHat.) I
realize this is not a mainline kernel, but I was
In preparation for adding an atomic version of the disable code, extract
the actual disable operation into a separate function.
Signed-off-by: Brian Starkey
---
drivers/gpu/drm/drm_framebuffer.c | 87 +++--
1 file changed, 54
Writeback connectors aren't much use to the fbdev helpers, as they won't
show anything to the user. Skip them when looking for candidate output
configurations.
Signed-off-by: Brian Starkey
---
drivers/gpu/drm/drm_fb_helper.c |4
1 file changed, 4 insertions(+)
Hi,
This RFC series introduces a new connector type:
DRM_MODE_CONNECTOR_WRITEBACK
It is a follow-on from a previous discussion: [1]
Writeback connectors are used to expose the memory writeback engines
found in some display controllers, which can write a CRTC's
composition result to a memory
From: Chao Yu
We don't need to keep incomplete created inode in cache, so if we fail to
add link into directory during new inode creation, it's better to set
nlink of inode to zero, then we can evict inode immediately. Otherwise
release of nid belong to inode will be delayed
From: Chao Yu
In fsync_node_pages, if f2fs was taged with CP_ERROR_FLAG, make sure bio
cache was flushed before return.
Signed-off-by: Chao Yu
---
fs/f2fs/node.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/fs/f2fs/node.c
From: Chao Yu
In f2fs_fill_super, if there is any IO error occurs during recovery,
cached discard entries will be leaked, in order to avoid this, make
write_checkpoint() handle memory release by itself, besides, move
clear_prefree_segments to write_checkpoint for readability.
From: Chao Yu
f2fs_balance_fs should be called in between node page updating, otherwise
node page count will exceeded far beyond watermark of triggering
foreground garbage collection, result in facing high risk of hitting LFS
allocation failure.
Signed-off-by: Chao Yu
From: Chao Yu
In order to avoid racing problem, make largest extent cache being updated
under lock.
Signed-off-by: Chao Yu
---
fs/f2fs/inode.c | 11 +++
1 file changed, 7 insertions(+), 4 deletions(-)
diff --git a/fs/f2fs/inode.c
From: Chao Yu
If there is no dirty pages in inode, we should give a chance to detach
the inode from global dirty list, otherwise it needs to call another
unnecessary .writepages for detaching.
Signed-off-by: Chao Yu
---
fs/f2fs/data.c| 8 +---
On Tue, Oct 11, 2016 at 04:11:39PM +0100, Al Viro wrote:
> On Tue, Oct 11, 2016 at 10:45:08AM -0400, Dave Jones wrote:
> > This is from Linus' current tree, with Al's iovec fixups on top.
>
> Those iovec fixups are in the current tree...
ah yeah, git quietly dropped my local copy when I
+Bjorn
On Mon, Oct 10, 2016 at 8:33 AM, Rob Herring wrote:
> On Mon, Oct 10, 2016 at 8:17 AM, Laszlo Ersek wrote:
>> Hi,
>>
>> Greg asked me to stick to email with this bug report, so I'm reposting
>> the original kernel bugzilla report to personal addresses,
Hi Linus,
My for-linus-4.9 has our merge window pull:
git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git
for-linus-4.9
This is later than normal because I was tracking down a use-after-free
during btrfs/101 in xfstests. I had hoped to fix up the offending
patch, but wasn't
The generic pin configuration and multiplexing should be preferred now,
even though we still support the old one.
Signed-off-by: Maxime Ripard
---
Documentation/devicetree/bindings/pinctrl/allwinner,sunxi-pinctrl.txt | 16
1 file changed, 16
So far, putting NO_PULL in allwinner,pull was ignored, behaving like if
that property was not there at all.
Obviously, this is not the right thing to do, and in that case, we really
need to just disable the bias.
Acked-by: Chen-Yu Tsai
Signed-off-by: Maxime Ripard
Add the A64 CCU clocks set.
Acked-by: Rob Herring
Signed-off-by: Maxime Ripard
---
Documentation/devicetree/bindings/clock/sunxi-ccu.txt | 1 +-
drivers/clk/sunxi-ng/Kconfig | 11 +-
drivers/clk/sunxi-ng/Makefile
From: Andre Przywara
The Allwinner A64 SoC is a low-cost chip with 4 ARM Cortex-A53 cores
and the typical tablet / TV box peripherals.
The SoC is based on the (32-bit) Allwinner H3 chip, sharing most of
the peripherals and the memory map.
Although the cores are proper
From: Chao Yu
This patch makes sure it returns a positive value instead of a probable
casted negative value as shrink count.
Signed-off-by: Chao Yu
---
fs/f2fs/shrinker.c | 10 ++
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git
From: Chao Yu
Add to show pending allocated nids count in debugfs.
Signed-off-by: Chao Yu
---
fs/f2fs/debug.c | 7 ---
fs/f2fs/f2fs.h | 2 +-
2 files changed, 5 insertions(+), 4 deletions(-)
diff --git a/fs/f2fs/debug.c b/fs/f2fs/debug.c
index
1 - 100 of 1508 matches
Mail list logo