Provides helper functions for drivers that have a simple display
pipeline. Plane, crtc and encoder are collapsed into one entity.
Cc: jsa...@ti.com
Signed-off-by: Noralf Trønnes
---
Changes since v3:
- (struct drm_simple_display_pipe *)->funcs should be const
Changes since v2:
- Drop Kconfig kn
Ping, since the 4.7 merge window is opening soon and I haven't received
too much feedback on this version of the patch series based on 4.6-rc1.
1. Patch 09/13 for timer ticks was acked by Daniel Lezcano and is standalone,
so could be taken into the relevant trees. I'm not sure if it should go
Historically for Rockchip devices we've relied on the power-on
default (or perhaps the firmware setting) to get the correct drive
phase for dw_mmc devices. This worked OK for the most part, but:
* Relying on the setting just "being right" is a bit fragile.
* As soon as there is an instance where
Hi Robin,
On 5/12/2016 1:08 PM, Robin Murphy wrote:
Hi Luke,
On 12/05/16 16:34, Luke Starrett wrote:
Hi Robin,
I pulled this in to a userspace test app expecting that the __uint128_t
type might cause GCC to emit 'ldp'. Seems like that was that your
intent based on your commit note. Instead
On 05/10/2016 08:57 AM, Borislav Petkov wrote:
> On Tue, May 10, 2016 at 02:43:58PM +0100, Matt Fleming wrote:
>> Is it not possible to maintain some kind of kernel virtual address
>> mapping so memremap*() and friends can figure out when to twiddle the
>> mapping attributes and map with/without en
On Thu, May 12, 2016 at 08:25:23PM +0200, Noralf Trønnes wrote:
> Provides helper functions for drivers that have a simple display
> pipeline. Plane, crtc and encoder are collapsed into one entity.
>
> Cc: jsa...@ti.com
> Signed-off-by: Noralf Trønnes
> ---
>
> Changes since v3:
> - (struct drm_
On 5/12/2016 6:30 AM, Christian Lamparter wrote:
> On Thursday, May 12, 2016 01:55:44 PM Arnd Bergmann wrote:
>> On Thursday 12 May 2016 11:58:18 Christian Lamparter wrote:
>> Detecting the endianess of the
>> device is probably the best future-proof solution, but it's also
>> considera
Hello Sergei,
[we already talked about this patch in #armlinux, I'm now just
forwarding my comments on the list. Background was that I sent an easier
and less complete patch with the same idea. See
http://patchwork.ozlabs.org/patch/621418/]
[added Linus Walleij to Cc, there is a question for you/
On Thu, May 12, 2016 at 08:06:07PM +0800, Kefeng Wang wrote:
> After patch "of/platform: Add common method to populate default bus",
> it is possible for arch code to remove unnecessary callers about the
> of_platform_populate with default match table.
s/about the/of/ ?
> Cc: Yoshinori Sato
> Cc
Reviewed-by: "Kirill A. Shutemov"
Signed-off-by: Andrea Arcangeli
Andrea,
Perhaps add a V in the subject for subsequent submissions as well as
version change control in email after the ---.
I happened to know the differences, but others might not.
This patch also solves the >= 4.5-rc1 IB
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git for-linus
to receive updates for the input subsystem.
Changelog:
-
Chris Diamand (1):
Input: byd - update copyright header
H. Nikolaus Schaller (1):
Input: twl6040-vibra - fix
Nice Kedar!
Is this getting applied? I would really like to see this get into the mainline.
thanks,
Paul
On Thu, Apr 7, 2016 at 1:29 AM, Kedareswara rao Appana
wrote:
> This patch adds support for the AXI Direct Memory Access (AXI DMA)
> core in the existing vdma driver, AXI DMA Core is a
> sof
Hello Laxman,
On Mon, May 2, 2016 at 8:17 AM, Laxman Dewangan wrote:
[snip]
> diff --git a/drivers/pinctrl/tegra/pinctrl-tegra210-io-pad.c
> b/drivers/pinctrl/tegra/pinctrl-tegra210-io-pad.c
> new file mode 100644
> index 000..ab06c71
> --- /dev/null
> +++ b/drivers/pinctrl/tegra/pinctrl-t
Hi Noralf,
Thank you for the patches.
For 1/3 and 2/3,
Reviewed-by: Laurent Pinchart
On Thursday 12 May 2016 20:25:20 Noralf Trønnes wrote:
> This patchset adds various helpers that was originally part of the
> tinydrm patchset.
>
> Essentially it adds 2 functions:
> - drm_fb_cma_create_with_
This is currently an RFC because the patch applies to Linus head, but
needs altering for the vfs tree, so I'll respin and resend after the
merge window closes.
My use case for this is that I run a lot of unprivileged architectural
emulation containers on my system using user namespaces. Details h
On Thu, May 12, 2016 at 11:34:45AM -0600, Jason Gunthorpe wrote:
On Thu, May 12, 2016 at 10:18:27AM -0700, Dennis Dalessandro wrote:
There is also a driver software version being exported via a sysfs
file. This is needed so that user space applications (psm) can
determine if it needs to do ioct
Hi Kamal,
seems using a toolchain with gcc 6.1 creates funny new issues like this:
In file included from include/linux/compiler.h:54:0,
from include/uapi/linux/stddef.h:1,
from include/linux/stddef.h:4,
from ./include/uapi/linux/posix_types.h:4,
> -Original Message-
> From: Pali Rohár [mailto:pali.ro...@gmail.com]
> Sent: Thursday, May 12, 2016 3:41 AM
> To: Limonciello, Mario
> Cc: ker...@kempniu.pl; mj...@srcf.ucam.org; dvh...@infradead.org; linux-
> ker...@vger.kernel.org; platform-driver-...@vger.kernel.org
> Subject: Re: [P
This allows any subtree to be uid/gid shifted and bound elsewhere. It
does this by operating simlarly to overlayfs, except that since
there's only a single underlying layer, all dentry lookups go through
this. Its primary use is for shifting the underlying uids of
filesystems used to support unpr
Hi Benjamin,
On Thu, May 12, 2016 at 05:07:54PM +0200, Benjamin Tissoires wrote:
> This is a basic driver for the Surface 3. I am not so sure it will work
> with any firmwares as most values are encoded, but given that I only have
> access to my current device with its firmware and I don't have th
On 05/12/2016 11:57 AM, Tony Lindgren wrote:
> * Eduard Gavin [160509 07:43]:
>> Dear Nishanth,
>> In igepV5 the LDO7 is connected to:
>> VDDA_DSIPORTA - ball AA33
>> VDDA_DSIPORTC - ball AE33
>> VDDA_HDMI - ball AN25
>> LDO4 is connected to:
>> VPP1 - ball AD9
>
> Thanks for
On Thu, May 12, 2016 at 03:07:38PM -0400, Dennis Dalessandro wrote:
> >>There is also a driver software version being exported via a sysfs
> >>file. This is needed so that user space applications (psm) can
> >>determine if it needs to do ioctl() or write().
> >
> >Why? Don't do this, just call ioct
jffs2 requires device, so the field fs_flags of the structure
file_system_type must be initialized to FS_REQUIRES_DEV.
Signed-off-by: Salah Triki
---
fs/jffs2/super.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/fs/jffs2/super.c b/fs/jffs2/super.c
index 0a9a114..fd24af9 100644
--- a/fs/jf
On Thu, May 12, 2016 at 11:43:32AM -0600, Jason Gunthorpe wrote:
On Thu, May 12, 2016 at 10:18:47AM -0700, Dennis Dalessandro wrote:
+ case HFI1_IOCTL_EP_INFO:
+ case HFI1_IOCTL_EP_ERASE_CHIP:
+ case HFI1_IOCTL_EP_ERASE_RANGE:
+ case HFI1_IOCTL_EP_READ_RANGE:
+ case
From: Álvaro Fernández Rojas
This patch adds support for defining memory-mapped GPIOs which
are compatible with the existing gpio-mmio interface. The generic
library provides support for many memory-mapped GPIO controllers
that are found in various on-board FPGA and ASIC solutions that
are used t
This is PATCH v5 for KASLR memory implementation for x86_64.
Recent changes:
Add performance information on commit.
Add details on PUD alignment.
Add information on testing against the KASLR bypass exploit.
Rebase on next-20160511 and merge recent KASLR changes.
Integrate feedb
Minor change that allows early boot physical mapping of PUD level virtual
addresses. The current implementation expect the virtual address to be
PUD aligned. For KASLR memory randomization, we need to be able to
randomize the offset used on the PUD table.
It has no impact on current usage.
Signed
Move the KASLR entropy functions in x86/libray to be used in early
kernel boot for KASLR memory randomization.
Signed-off-by: Thomas Garnier
---
Based on next-20160511
---
arch/x86/boot/compressed/kaslr.c | 77 +++---
arch/x86/include/asm/kaslr.h | 6 +++
arch/x8
Randomizes the virtual address space of kernel memory sections (physical
memory mapping, vmalloc & vmemmap) for x86_64. This security feature
mitigates exploits relying on predictable kernel addresses. These
addresses can be used to disclose the kernel modules base addresses or
corrupt specific str
Add a new option (CONFIG_RANDOMIZE_MEMORY_PHYSICAL_PADDING) to define
the padding used for the physical memory mapping section when KASLR
memory is enabled. It ensures there is enough virtual address space when
CONFIG_MEMORY_HOTPLUG is used. The default value is 10 terabytes. If
CONFIG_MEMORY_HOTPL
On Thu, May 12, 2016 at 12:58:30PM -0500, Andy Gross wrote:
> On Thu, May 12, 2016 at 11:48:43AM +0530, Abhishek Sahu wrote:
> > On Thu, May 12, 2016 at 12:13:47AM -0500, Andy Gross wrote:
> > > On Wed, May 11, 2016 at 11:04:17PM +0530, Abhishek Sahu wrote:
> > >
> > >
> > >
> > > > > In q
Using the software based channel scan mechanism from mac80211 keeps us
offline for 10-15 second, we should instead issue a start_scan/end_scan
on each channel reducing this time.
Signed-off-by: Bjorn Andersson
---
With this implementation I see a reduction of throughput for about 1-2 seconds
wit
On Thu, May 12, 2016 at 03:27:27PM -0400, Dennis Dalessandro wrote:
> >I thought we agreed to get rid of this as well? It certainly does not
> >belong here, and as a general rule, I don't think ioctls should be
> >doing capable tests..
>
> Yeah. I left it in this patch set because this just "ports
On 05/03/2016 10:30 AM, Florian Westphal wrote:
> a trans_start struct member exists twice:
> - in struct net_device (legacy)
> - in struct netdev_queue
>
> Instead of open-coding dev->trans_start usage to obtain the current
> trans_start value, use dev_trans_start() instead.
>
> This is not exac
On 05/12/2016 08:19 AM, Michal Hocko wrote:
On Thu 12-05-16 14:12:04, Peter Zijlstra wrote:
On Wed, May 11, 2016 at 08:03:46PM +0200, Michal Hocko wrote:
I still cannot say I would understand why the pending
RWSEM_WAITING_BIAS matters but I would probably need to look at the code
again with a c
> On 12.05.2016, at 20:15, Eric Anholt wrote:
>
> ker...@martin.sperl.org writes:
>
>> From: Martin Sperl
>>
>> As the sdram clock is a critical clock to the system
>> the minimal bcm2835-sdram driver claims (and enables)
>> this clock and also exposes the corresponding sdram
>> registers vi
On 05/12/2016 03:40 PM, Jason Gunthorpe wrote:
> On Thu, May 12, 2016 at 03:27:27PM -0400, Dennis Dalessandro wrote:
>>> I thought we agreed to get rid of this as well? It certainly does not
>>> belong here, and as a general rule, I don't think ioctls should be
>>> doing capable tests..
>>
>> Yeah.
Hi Dave,
Tried to do my xfs homework first!
On Fri, May 06, 2016 at 12:50:36PM +1000, Dave Chinner wrote:
> On Thu, May 05, 2016 at 11:24:35PM +0100, Djalal Harouni wrote:
> > On Thu, May 05, 2016 at 10:23:14AM +1000, Dave Chinner wrote:
> > > On Wed, May 04, 2016 at 04:26:46PM +0200, Djalal Haro
On 02/05/16 13:17, Laxman Dewangan wrote:
> NVIDIA Tegra210 supports the IO pads which can operate at 1.8V
> or 3.3V I/O voltage levels. Also the IO pads can be configured
> for power down state if it is not used. SW needs to configure the
> voltage level of IO pads based on IO rail voltage and it
Future patches will emit warnings if rq_clock() is called before
update_rq_clock() inside a rq_pin_lock()/rq_unpin_lock() pair.
Since there is only one caller of idle_balance() we can push the
unpin/repin there.
Cc: Peter Zijlstra
Cc: Ingo Molnar
Cc: Mike Galbraith
Cc: Mel Gorman
Cc: Yuyang D
There's no diagnostic checks for figuring out when we've accidentally
missed update_rq_clock() calls. Let's add some by piggybacking on the
rq_*pin_lock() wrappers.
The idea behind the diagnostic checks is that upon pining rq lock the
rq clock should be updated, via update_rq_clock(), before anybo
rq_clock() is called from sched_info_{depart,arrive}() after resetting
RQCF_ACT_SKIP but prior to a call to update_rq_clock().
In preparation for pending patches that check whether the rq clock has
been updated inside of a pin context before rq_clock() is called, move
the reset of rq->clock_skip_u
detach_task_cfs_rq() may indirectly call rq_clock() to inform the
cpufreq code that the rq utilisation has changed. In which case, we
need to update the rq clock.
Cc: Peter Zijlstra
Cc: Ingo Molnar
Cc: Mel Gorman
Cc: Mike Galbraith
Cc: Yuyang Du
Cc: Byungchul Park
Cc: Rik van Riel
Cc: Frede
In preparation for adding diagnostic checks to catch missing calls to
update_rq_clock(), provide wrappers for (re)pinning and unpinning
rq->lock.
Because the pending diagnostic checks allow state to be maintained in
rq_flags across pin contexts, swap the 'struct pin_cookie' arguments
for 'struct r
There are currently no runtime diagnostic checks for detecting when we
have inadvertently missed a call to update_rq_clock() before accessing
rq_clock().
The idea in these patches, which came from Peter, is to piggyback on
the rq->lock pin/unpin context to detect when we expected (and failed)
to s
On May 12 2016 or thereabouts, Dmitry Torokhov wrote:
> Hi Benjamin,
>
> On Thu, May 12, 2016 at 05:07:54PM +0200, Benjamin Tissoires wrote:
> > This is a basic driver for the Surface 3. I am not so sure it will work
> > with any firmwares as most values are encoded, but given that I only have
> >
On Thu, May 12, 2016 at 01:25:08PM -0600, Jason Gunthorpe wrote:
On Thu, May 12, 2016 at 03:07:38PM -0400, Dennis Dalessandro wrote:
>>There is also a driver software version being exported via a sysfs
>>file. This is needed so that user space applications (psm) can
>>determine if it needs to do
On Thu, 2016-05-12 at 21:51 +0200, Benjamin Tissoires wrote:
> Which leads to an other question: do you think we should call it
> surface_ts_spi.c instead of ntrig_spi? I am not sure this will work
> with any other Ntrig/SPI device...
N-Trig got bought by Microsoft, so it's unlikely that this migh
On Thu, May 12, 2016 at 09:51:22PM +0200, Benjamin Tissoires wrote:
> On May 12 2016 or thereabouts, Dmitry Torokhov wrote:
> > On Thu, May 12, 2016 at 05:07:54PM +0200, Benjamin Tissoires wrote:
> > > +static int __maybe_unused ntrig_spi_suspend(struct device *dev)
> > > +{
> > > + struct spi_devi
Hi Kamal,
I found it and backported the upstream commit
cb984d101b30eb7478d32df56a0023e4603cba7f to 3.19 series.
kind regards
Philip Müller
-
Manjaro Project Lead
diff -Npur linux-3.19.orig/include/linux/compiler-gcc3.h linux-3.19/include/linux/compiler-gcc3.h
--- linux-3.19.
On Wed, May 11, 2016 at 11:33:38AM -0700, James Bottomley wrote:
> On Wed, 2016-05-11 at 17:42 +0100, Djalal Harouni wrote:
> > On Tue, May 10, 2016 at 04:36:56PM -0700, James Bottomley wrote:
[...]
> > Hmm anyway you are mounting this on behalf of filesystems, so if you
> > add the recursive thin
On Thu, May 12, 2016 at 4:11 AM, David Howells wrote:
> Hi James,
>
> Can you pass this patch on to Linus immediately please?
I took it directly, since we're close to final release.
Linus
From: Arnaldo Carvalho de Melo
To fix the build on Fedora Rawhide (gcc 6.0.0 20160311 (Red Hat 6.0.0-0.17):
CC /tmp/build/perf/arch/x86/util/dwarf-regs.o
arch/x86/util/dwarf-regs.c:66:36: error: 'x86_32_regoffset_table' defined but
not used [-Werror=unused-const-variable=]
static
9f448cd3cbcec8995935e60b27802ae56aac8cc0:
perf/core: Disable the event on a truncated AUX record (2016-05-12 14:46:11
+0200)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git
tags/perf-urgent-for-mingo-20160512
for you to fetch changes up to
From: Steven Rostedt
At the end of process_filter(), collapse_tree() was changed to update
the parg parameter, but the reassignment after the call wasn't removed.
What happens is that the "current_op" gets modified and freed and parg
is assigned to the new allocated argument. But after the call
From: Arnaldo Carvalho de Melo
We were showing a hardcoded default value for the kernel.perf_event_paranoid
sysctl, now that it became more paranoid (1 -> 2 [1]), this would need to be
updated, instead show the current value:
[acme@jouet linux]$ perf record ls
Error:
You may not have permi
From: Arnaldo Carvalho de Melo
Now with the default for the kernel.perf_event_paranoid sysctl being 2 [1]
we need to fall back to :u, i.e. to set perf_event_attr.exclude_kernel
to 1.
Before:
[acme@jouet linux]$ perf record usleep 1
Error:
You may not have permission to collect stats.
C
From: Arnaldo Carvalho de Melo
After 0161028b7c8a ("perf/core: Change the default paranoia level to 2")
'perf stat' fails for users without CAP_SYS_ADMIN, so just use
'perf_evsel__fallback()' to have the same behaviour as 'perf record',
i.e. set perf_event_attr.exclude_kernel to 1.
Now:
[acme
From: Arnaldo Carvalho de Melo
The readdir() function is thread safe as long as just one thread uses a
DIR, which is the case in thread_map, so, to avoid breaking the build
with glibc-2.23.90 (upcoming 2.24), use it instead of readdir_r().
See: http://man7.org/linux/man-pages/man3/readdir.3.html
From: Arnaldo Carvalho de Melo
The readdir() function is thread safe as long as just one thread uses a
DIR, which is the case when synthesizing events for pre-existing threads
by traversing /proc, so, to avoid breaking the build with glibc-2.23.90
(upcoming 2.24), use it instead of readdir_r().
On 12 May 2016 at 14:32, Abhishek Sahu wrote:
> On Thu, May 12, 2016 at 12:58:30PM -0500, Andy Gross wrote:
>> On Thu, May 12, 2016 at 11:48:43AM +0530, Abhishek Sahu wrote:
>> > On Thu, May 12, 2016 at 12:13:47AM -0500, Andy Gross wrote:
>> > > On Wed, May 11, 2016 at 11:04:17PM +0530, Abhishek S
From: Arnaldo Carvalho de Melo
If not, tell the user that:
config/Makefile:273: Old libdw.h, finding variables at given 'perf probe'
point will not work, install elfutils-devel/libdw-dev >= 0.157
And return -ENOTSUPP in die_get_var_range(), failing features that
need it, like the one pointed
On Wed, 2016-05-11 at 14:56 -0700, Eric Dumazet wrote:
> On Wed, 2016-05-11 at 08:55 +0200, Peter Zijlstra wrote:
> > On Tue, May 10, 2016 at 03:51:37PM -0700, Eric Dumazet wrote:
> > > diff --git a/kernel/softirq.c b/kernel/softirq.c
> > > index 17caf4b63342..22463217e3cf 100644
> > > --- a/kernel
From: Arnaldo Carvalho de Melo
The readdir() function is thread safe as long as just one thread uses a
DIR, which is the case when parsing tracepoint event definitions, to
avoid breaking the build with glibc-2.23.90 (upcoming 2.24), use it
instead of readdir_r().
See: http://man7.org/linux/man-p
From: Arnaldo Carvalho de Melo
The readdir() function is thread safe as long as just one thread uses a
DIR, which is the case in 'perf script', so, to avoid breaking the build
with glibc-2.23.90 (upcoming 2.24), use it instead of readdir_r().
See: http://man7.org/linux/man-pages/man3/readdir.3.h
On Thu, 2016-05-12 at 19:02 +0300, Meelis Roos wrote:
> This is from a dual-AthlonMP 32-bit x86 system with onboard Adaptec
> SCSI
> controller, once during bootup.
>
> [4.896307]
> =
> ===
> [4.896471] UBSAN: Und
On 04/21/2016 07:13 AM, Hans Westgaard Ry wrote:
> IPoIB collects statistics of traffic including number of packets
> sent/received, number of bytes transferred, and certain errors. This
> patch makes these statistics available to be queried by ethtool.
>
> Signed-off-by: Hans Westgaard Ry
> Revi
On Thu, 12 May 2016 18:53:11 +0200 Michal Hocko wrote:
> Andrew,
> do you think this should go in in the next merge window or should I
> repost after rc1 is out? I do not mind one way or the other. I would
> obviously would like to get them in sooner rather than later but I can
> certainly live w
On 05/11/2016 06:04 PM, Peter Hurley wrote:
/* Grant an infinite number of read locks to the readers at the front
@@ -306,16 +312,11 @@ static inline bool rwsem_can_spin_on_owner(struct
rw_semaphore *sem)
rcu_read_lock();
owner = READ_ONCE(sem->owner);
- if (!owner
On Wed, May 11, 2016 at 04:57:47PM -0700, Andy Lutomirski wrote:
> The framebuffer mapping virtual address leaks information about the
> kernel memory layout. Stop logging it.
>
> Cc: Peter Jones
> Cc: Jean-Christophe Plagniol-Villard
> Cc: Tomi Valkeinen
> Cc: linux-fb...@vger.kernel.org
> Cc
For your attention:
Hoping that you are fine today!!
For a formal introduction, I am a United Nations Official here in the UK, I
held a very good position as an Assistant Financial Officer (Fund Approval &
Claim Department).
It is with a great honor and I am privileged to contact you today, Al
On 5/12/16 7:09 AM, Arnaldo Carvalho de Melo wrote:
Em Thu, May 12, 2016 at 08:43:12AM +, He Kuang escreveu:
Symfs dir and buildid dir are two places that perf looks into for
symbols, currently, if symfs dir is given, buildid-cache is skipped.
In the cross-platform perf record/script scenar
On Thu, May 12, 2016 at 10:20:09PM +0200, Marc Haber wrote:
> Hi David,
>
> On Sat, Apr 23, 2016 at 07:52:46PM +0100, Dr. David Alan Gilbert wrote:
> > Hmm, your problem does sound like bad hardware, but
> > If you've got a nice reliable crash, can you try turning transparent huge
> > pages
>
> jffs2 requires device, so the field fs_flags of the structure
> file_system_type must be initialized to FS_REQUIRES_DEV.
No, it doesn't require a device. Or even CONFIG_BLOCK.
--
dwmw2
Hi David,
On Sat, Apr 23, 2016 at 07:52:46PM +0100, Dr. David Alan Gilbert wrote:
> Hmm, your problem does sound like bad hardware, but
> If you've got a nice reliable crash, can you try turning transparent huge
> pages
> off on the host;
>echo never > /sys/kernel/mm/transparent_hugepage/
Hi,
[auto build test WARNING on next-20160512]
[cannot apply to tip/x86/core v4.6-rc7 v4.6-rc6 v4.6-rc5 v4.6-rc7]
[if your patch is applied to the wrong git tree, please drop us a note to help
improving the system]
url:
https://github.com/0day-ci/linux/commits/Thomas-Garnier/x86-boot-KASLR
* Nishanth Menon [160512 12:21]:
> On 05/12/2016 11:57 AM, Tony Lindgren wrote:
> > + * LDO7 is used for HDMI: VDDA_DSIPORTA - ball AA33, VDDA_DSIPORTC - ball
> > AE33
> > + * VDDA_HDMI - ball AN25. LDO4 is: VPP1 - ball AD9.
>
> We should set ldo4_reg as 2v as well (default in omap5-board-common
On Thu, May 12, 2016 at 03:05:39PM -0500, Andy Gross wrote:
> On 12 May 2016 at 14:32, Abhishek Sahu wrote:
> > On Thu, May 12, 2016 at 12:58:30PM -0500, Andy Gross wrote:
> >> On Thu, May 12, 2016 at 11:48:43AM +0530, Abhishek Sahu wrote:
> >> > On Thu, May 12, 2016 at 12:13:47AM -0500, Andy Gros
Holger Hoffstätte googlemail.com> writes:
>
> On 11/11/15 23:08, Holger Hoffstätte wrote:
> > On 11/11/15 22:29, Jens Axboe wrote:
> >> On 11/11/2015 08:21 AM, Holger Hoffstätte wrote:
> >>>
> >>> The loop driver always declares the rotational flag of its device as
> >>> rotational, even when th
The compressed kernel is built with -fPIC/-fPIE so that it can run in any
location a bootloader happens to put it. However, since ELF relocation
processing is not happening (and all the relocation information has
already been stripped at link time), none of the code can use data
relocations (e.g. s
On 05/12/2016 03:53 PM, Dennis Dalessandro wrote:
> On Thu, May 12, 2016 at 01:25:08PM -0600, Jason Gunthorpe wrote:
>> On Thu, May 12, 2016 at 03:07:38PM -0400, Dennis Dalessandro wrote:
>>> >>There is also a driver software version being exported via a sysfs
>>> >>file. This is needed so that use
> jffs2 requires device, so the field fs_flags of the structure
> file_system_type must be initialized to FS_REQUIRES_DEV.
No, it doesn't require a device. Or even CONFIG_BLOCK.
--
dwmw2
Em Thu, May 12, 2016 at 02:23:37PM -0600, David Ahern escreveu:
> On 5/12/16 7:09 AM, Arnaldo Carvalho de Melo wrote:
> > Em Thu, May 12, 2016 at 08:43:12AM +, He Kuang escreveu:
> > > Symfs dir and buildid dir are two places that perf looks into for
> > > symbols, currently, if symfs dir is gi
On Thu, May 12, 2016 at 11:24:02PM +0300, Kirill A. Shutemov wrote:
> http://lkml.kernel.org/r/1463070742-18401-1-git-send-email-aarca...@redhat.com
Is this in v4.6-rc7?
If so, can I just test v4.6-rc7?
If not so, would it be a valid approach to first check plain v4.6-rc7
and then patched v4.6-r
On Thursday, May 12, 2016 11:40:28 AM John Youn wrote:
> On 5/12/2016 6:30 AM, Christian Lamparter wrote:
> > On Thursday, May 12, 2016 01:55:44 PM Arnd Bergmann wrote:
> >> On Thursday 12 May 2016 11:58:18 Christian Lamparter wrote:
> >> Detecting the endianess of the
> >> device is probab
On 05/12/2016 09:24 AM, Catalin Marinas wrote:
On Thu, May 12, 2016 at 08:27:08AM -0700, David Daney wrote:
On 05/12/2016 02:49 AM, Catalin Marinas wrote:
On Wed, May 11, 2016 at 05:06:13PM -0700, David Daney wrote:
On 05/11/2016 03:39 AM, Catalin Marinas wrote:
[...]
I wonder whether you c
On Thu, May 12, 2016 at 10:34:57PM +0200, Marc Haber wrote:
> On Thu, May 12, 2016 at 11:24:02PM +0300, Kirill A. Shutemov wrote:
> > http://lkml.kernel.org/r/1463070742-18401-1-git-send-email-aarca...@redhat.com
>
> Is this in v4.6-rc7?
No.
> If so, can I just test v4.6-rc7?
>
> If not so, wou
* Nishanth Menon [160506 06:39]:
> Palmas Regulator is an exception and does not follow the standard
> "vin-supply" common definitions for all regulators, as a result of this,
> the input supplies are not reported to regulator framework, with the
> obvious result of not being appropriately mapped.
On Thu, 2016-05-12 at 22:07 +0200, Paolo Abeni wrote:
> > > static inline bool ksoftirqd_running(void)
> > > {
> > > return __this_cpu_read(ksoftirqd)->state == TASK_RUNNING;
>
> here something like:
>
> struct task_struct *tsk = __this_cpu_read(ksoftirqd);
> return tsk && (tsk->
On Thursday 12 May 2016 22:39:36 Christian Lamparter wrote:
> On Thursday, May 12, 2016 11:40:28 AM John Youn wrote:
> > On 5/12/2016 6:30 AM, Christian Lamparter wrote:
> > > On Thursday, May 12, 2016 01:55:44 PM Arnd Bergmann wrote:
> > >>
> > >> If I recall correctly, the rough consensus was to
* Javier Martinez Canillas [160506 14:28]:
> Hello Enric,
>
> On Fri, May 6, 2016 at 5:22 PM, Enric Balletbo i Serra
> wrote:
> > Hi Javier,
> >
> > On 06/05/16 23:07, Javier Martinez Canillas wrote:
> >> Hello Enric,
> >>
> >> On Fri, May 6, 2016 at 5:02 PM, Enric Balletbo i Serra
> >> wrote:
From: Haishuang Yan
Date: Wed, 11 May 2016 18:48:31 +0800
> Do not include attribute IFLA_GRE_TOS.
>
> Signed-off-by: Haishuang Yan
Applied.
From: Haishuang Yan
Date: Wed, 11 May 2016 18:48:32 +0800
> When dealing with WCCP in gre6 tunnel, it sets the wrong tpi->protocol,
> that is, ETH_P_IP instead of ETH_P_IPV6 for the encapuslated traffic.
>
> Signed-off-by: Haishuang Yan
Applied.
On 5/12/2016 1:39 PM, Christian Lamparter wrote:
> On Thursday, May 12, 2016 11:40:28 AM John Youn wrote:
>> On 5/12/2016 6:30 AM, Christian Lamparter wrote:
>>> On Thursday, May 12, 2016 01:55:44 PM Arnd Bergmann wrote:
On Thursday 12 May 2016 11:58:18 Christian Lamparter wrote:
Dete
A patch that went into Linux-4.4 to fix big-endian mode on a Lantiq
MIPS system unfortunately broke big-endian operation on PowerPC
APM82181 as reported by Christian Lamparter, and likely other
systems.
It actually introduced multiple issues:
- it broke big-endian ARM kernels: any machine that wa
From: Arnd Bergmann
Date: Wed, 11 May 2016 22:13:23 +0200
> I tried to fix this before, but my previous fix was incomplete
> and we can still get the same link error in randconfig builds
> because of the way that Kconfig treats the
>
> default y if MVNETA=y && MVNETA_BM_ENABLE
>
> line th
On Thu, 2016-05-12 at 13:49 -0700, Eric Dumazet wrote:
> On Thu, 2016-05-12 at 22:07 +0200, Paolo Abeni wrote:
>
> > > > static inline bool ksoftirqd_running(void)
> > > > {
> > > > return __this_cpu_read(ksoftirqd)->state == TASK_RUNNING;
> >
> > here something like:
> >
> > struct
A recent patch added a stub function for acpi_video_get_levels when
CONFIG_ACPI_VIDEO is disabled. However, this is marked as 'static'
and causes a warning about an unused function whereever the header
gets included:
In file included from ../drivers/gpu/drm/radeon/radeon_acpi.c:28:0:
include/acpi/
On ARM64, the mtk-pmic-wrap driver causes a harmless warning:
mtk-pmic-wrap.c:1062:16: warning: large integer implicitly truncated to
unsigned type [-Woverflow]
mtk-pmic-wrap.c:1074:16: warning: large integer implicitly truncated to
unsigned type [-Woverflow]
mtk-pmic-wrap.c:1086:16: warning: la
The newly added nps irqchip driver causes build warnings on ARM64.
include/soc/nps/common.h: In function 'nps_host_reg_non_cl':
include/soc/nps/common.h:148:9: warning: cast to pointer from integer of
different size [-Wint-to-pointer-cast]
As the driver is only used on ARC, we don't need to see
601 - 700 of 871 matches
Mail list logo
