FYI, we noticed the below changes on
https://git.linaro.org/people/ard.biesheuvel/linux-arm kallsyms-text-relative
commit 06862f34f614bb6ff6a9fc9c4b0d849e2ee2018d ("kallsyms: add support for
relative offsets in kallsyms address table")
Hi, Shawn.
On 01/21/2016 03:52 PM, Shawn Lin wrote:
> dw_mmc already use mmc_of_parse to get "broken-cd" property,
> but it considered "broken-cd" to be a quirk in its driver. We
> don't need this quirk here, and just take what we need from
> mmc->caps.
I have reverted the previous version, this
On 2016/1/22 0:35, rkrc...@redhat.com wrote:
2016-01-21 13:44+0800, Yang Zhang:
On 2016/1/21 13:41, Wu, Feng wrote:
From: Yang Zhang [mailto:yang.zhang...@gmail.com]
We may have different understanding on PI mode. My understanding is if
we set the IRTE to PI format, than the subsequent
On 21 January 2016 at 18:51, Mark Rutland wrote:
> On Thu, Jan 21, 2016 at 04:48:57PM +0800, Zhaoyang Huang wrote:
>> Hi Mark,
>
> Hi,
>
>> Do you have any suggestion on how to sync the GIC operation from
>> kernel and psci parallelly? Thanks!
>
> I'm not sure what you mean.
>
> What problem are
> -Original Message-
> From: rkrc...@redhat.com [mailto:rkrc...@redhat.com]
> Sent: Friday, January 22, 2016 1:21 AM
> To: Wu, Feng
> Cc: Yang Zhang ; pbonz...@redhat.com; linux-
> ker...@vger.kernel.org; k...@vger.kernel.org
> Subject: Re: [PATCH v3 2/4] KVM: x86: Use vector-hashing to
Add phy driver for the Rockchip DisplayPort PHY module. This
is required to get DisplayPort working in Rockchip SoCs.
Signed-off-by: Yakir Yang
Reviewed-by: Heiko Stuebner
---
Changes in v13: None
Changes in v12:
- Re-order the include headers file alphabetically in phy-rockchip-dp.c (Jingoo)
RK3288 need some special registers setting, we can separate
them out by the dev_type of plat_data.
Signed-off-by: Yakir Yang
---
Changes in v13: None
Changes in v12: None
Changes in v11: None
Changes in v10: None
Changes in v9: None
Changes in v8: None
Changes in v7: None
Changes in v6: None
On Mon, Jan 04, 2016 at 12:31:58PM -0800, Kees Cook wrote:
> On Wed, Dec 23, 2015 at 1:34 PM, Luis R. Rodriguez
> wrote:
> > In order to try to help phase out user mode helpers this makes no use of
> > the old user mode helper code *at all*, and if we wish to can easily
> > phase this code out
Some edp screen do not have hpd signal, so we can't just return
failed when hpd plug in detect failed.
This is an hardware property, so we need add a devicetree property
"analogix,need-force-hpd" to indicate this sutiation.
Signed-off-by: Yakir Yang
Acked-by: Rob Herring
Tested-by: Javier
This change just make a little clean to make code more like
drm core expect, move hdp detect code from bridge->enable(),
and place them into connector->detect().
Note: Gustavo Padovan try to remove the controller and phy
power on function in bind time at bellow commit:
drm/exynos: do not
Turn off the panel power in suspend time would help to reduce
power waste.
Signed-off-by: Yakir Yang
---
Changes in v13: None
Changes in v12: None
Changes in v11: None
Changes in v10: None
Changes in v9: None
Changes in v8: None
Changes in v7: None
Changes in v6: None
Changes in v5: None
Changes
Display Port monitor could support kinds of mode which indicate
in monitor edid, not just one single display resolution which
defined in panel or devivetree property display timing.
Note: Gustavo Padovan try to remove the controller and phy
power on function in bind time at bellow commit:
It may caused a dead lock if we flush the hpd work in bridge disable time.
The normal flow would like:
IN --> DRM IOCTL
1. Acquire crtc_ww_class_mutex (DRM IOCTL)
IN --> analogix_dp_bridge
2. Acquire hpd work lock (Flush hpd work)
3. HPD work already in idle, no need
After exynos_dp have been split the common IP code into analogix_dp driver,
the analogix_dp driver have deprecated some Samsung platform properties which
could be dynamically parsed from EDID/MODE/DPCD message, so this is an update
for Exynos DTS file for dp-controller.
Beside the backward
Rockchip have three clocks for dp controller, we leave pclk_edp
to analogix_dp driver control, and keep the sclk_edp_24m and
sclk_edp in platform driver.
Signed-off-by: Yakir Yang
Tested-by: Heiko Stuebner
---
Changes in v13:
- Use .enable instead of preprare/commit in encoder_helper_funcs
There are some IP limit on rk3288 that only support 4 physical lanes
of 2.7/1.6 Gbps/lane, so seprate them out by device_type flag.
Signed-off-by: Yakir Yang
Tested-by: Javier Martinez Canillas
---
Changes in v13: None
Changes in v12: None
Changes in v11: None
Changes in v10:
- Remove the
Add dt binding documentation for rockchip display port PHY.
Signed-off-by: Yakir Yang
Acked-by: Rob Herring
Reviewed-by: Heiko Stuebner
---
Changes in v13: None
Changes in v12: None
Changes in v11:
- Correct the title of this rockchip dp phy document(Rob)
- Add the ack from Rob Herring
Rockchip DP driver is a helper driver of analogix_dp coder driver,
so most of the DT property should be descriped in analogix_dp document.
Signed-off-by: Yakir Yang
Acked-by: Rob Herring
Reviewed-by: Heiko Stuebner
---
Changes in v13: None
Changes in v12: None
Changes in v11: None
Changes in
Analogix dp driver is split from exynos dp driver, so we just
make an copy of exynos_dp.txt, and then simplify exynos_dp.txt
Beside update some exynos dtsi file with the latest change
according to the devicetree binding documents.
Signed-off-by: Yakir Yang
Acked-by: Rob Herring
---
Changes in
Both hsync/vsync polarity and interlace mode can be parsed from
drm display mode, and dynamic_range and ycbcr_coeff can be judge
by the video code.
But presumably Exynos still relies on the DT properties, so take
good use of mode_fixup() in to achieve the compatibility hacks.
Signed-off-by:
link_rate and lane_count already configured in analogix_dp_set_link_train(),
so we don't need to config those repeatly after training finished, just
remove them out.
Beside Display Port 1.2 already support 5.4Gbps link rate, the maximum sets
would change from {1.62Gbps, 2.7Gbps} to {1.62Gbps,
Fix some obvious alignment problems, like alignment and line
over 80 characters problems, make this easy to be maintained
later.
Signed-off-by: Yakir Yang
Acked-by: Jingoo Han
Reviewed-by: Krzysztof Kozlowski
Tested-by: Javier Martinez Canillas
---
Changes in v13: None
Changes in v12:
- Add
Hi all,
The Samsung Exynos eDP controller and Rockchip RK3288 eDP controller
share the same IP, so a lot of parts can be re-used. I split the common
code into bridge directory, then rk3288 and exynos only need to keep
some platform code. Cause I can't find the exact IP name of exynos dp
> -Original Message-
> From: Radim Krčmář [mailto:rkrc...@redhat.com]
> Sent: Friday, January 22, 2016 12:20 AM
> To: Wu, Feng
> Cc: pbonz...@redhat.com; linux-kernel@vger.kernel.org;
> k...@vger.kernel.org
> Subject: Re: [PATCH v3 1/4] KVM: Recover IRTE to remapped mode if the
>
Hello Krzysztof,
On 01/21/2016 10:00 PM, Krzysztof Kozlowski wrote:
On 22.01.2016 05:23, Javier Martinez Canillas wrote:
The driver has some hard-coded values such as the minimum delay needed
before a RTC update or the mask used for the sec/min/hour/etc registers.
Use a data structure that
On Mon, Jan 04, 2016 at 03:48:29PM -0500, Josh Boyer wrote:
> On Wed, Dec 23, 2015 at 4:34 PM, Luis R. Rodriguez
> wrote:
> > From: David Howells
> >
> > We'll be folding in some more checks on fw_read_file_contents(),
> > this will make the success case easier to follow.
> >
> > Signed-off-by:
Greg,
Due to Mimi's awesome work on generalizing a common VFS file read [0] as
described as possible in the commit log below this patch will be dropped in
preference for Mimi's VFS work to go in first.
Mimi,
since your generic VFS routine is pretty much identical to fw_read_file()
defined here
Hi Heiko,
On 01/22/2016 03:11 AM, Heiko Stuebner wrote:
Hi Yakir,
Am Dienstag, 19. Januar 2016, 18:04:53 schrieb Yakir Yang:
Rockchip have three clocks for dp controller, we leave pclk_edp
to analogix_dp driver control, and keep the sclk_edp_24m and
sclk_edp in platform driver.
On 2016/1/21 23:41, Arnaldo Carvalho de Melo wrote:
But... I think that the unflexible original code has a bug, one that makes it
not work when using gcc6 :-\
So I think we should make it build in gcc6, using that patch (or does it
have some other problem?) so that at least doing what we can
On Thu, Dec 24, 2015 at 06:26:39AM +0800, kbuild test robot wrote:
> reproduce: make htmldocs
> >> drivers/base/firmware_class.c:1336: warning: No description found for
> >> parameter 'sysdata'
> 1331/**
> 1332 * release_sysdata_file: - release the resource associated with
>
Hi, Shawn.
Applied this.
Thanks!
Best Regards,
Jaehoon Chung
On 01/21/2016 05:06 PM, Shawn Lin wrote:
> This patch remove struct block_settings since
> it never be used anywhere.
>
> Signed-off-by: Shawn Lin
> ---
>
> include/linux/mmc/dw_mmc.h | 8
> 1 file changed, 8 deletions(-)
On Thursday, January 21, 2016 10:49:58 AM Juri Lelli wrote:
> [+Punit, Javi]
>
> Hi Rafael,
>
> On 21/01/16 02:46, Rafael J. Wysocki wrote:
> > On Wednesday, January 20, 2016 05:39:14 PM Steve Muckle wrote:
> > > On 01/20/2016 05:22 PM, Rafael J. Wysocki wrote:
> > > > One comment here (which
This patch does use of more emacs functionalities which deliver to the
user indentation, commenting and white space highlighting.
As known tabs are the higher law and the prior elisp code enforces
that law for any lineup indentation.
However some trees have specific rules about line continuation
On Thursday, January 21, 2016 11:19:29 AM Sudeep Holla wrote:
> Commit 51164251f5c3 ("sched / idle: Drop default_idle_call() fallback
> from call_cpuidle()") made find_deepest_state() return non-negative
> value and check all the states with index > 0. Also a result,
> find_deepest_state() returns
On Thu, Jan 21, 2016 at 2:51 PM, Keith Busch wrote:
>
> My apologies for the trouble. I trust it really is broken, but I don't
> quite see how. The patch supposedly splits the transfer to the max size
> the request queue says it allows. How does the max allowed size end up
> an invalid multiple?
The WinSystems EBC-C384 has an onboard watchdog timer. The timeout range
supported by the watchdog timer is 1 second to 255 minutes. Timeouts
under 256 seconds have a 1 second resolution, while the rest have a 1
minute resolution.
This driver adds watchdog timer support for this onboard watchdog
On 01/21/2016 04:52 AM, Jan Kara wrote:
> On Wed 20-01-16 13:39:01, Shaohua Li wrote:
>> On Wed, Jan 20, 2016 at 10:19:26PM +0100, Jan Kara wrote:
>>> Hello,
>>>
>>> a friend of mine started seeing crashes with 3.18.25 kernel - once
>>> appropriate load is put on the machine it crashes within
On 2016年01月22日 02:19, John Keeping wrote:
If DRM_FBDEV_EMULATION is not selected in the config then we can save a
bit of space by not including the framebuffer code.
Signed-off-by: John Keeping
---
On Thu, 21 Jan 2016 17:52:51 +0100, Daniel Vetter wrote:
On Thu, Jan 21, 2016 at 01:53:46PM
On 22.01.2016 05:23, Javier Martinez Canillas wrote:
> Documentation/timers/timers-howto.txt suggest to use usleep_range()
> instead of msleep() for small msec (1ms - 20ms) since msleep() will
> often sleep for 20ms for any value in that range.
>
> This is fine in this case since 16ms is the
On 22.01.2016 05:23, Javier Martinez Canillas wrote:
> The driver has some hard-coded values such as the minimum delay needed
> before a RTC update or the mask used for the sec/min/hour/etc registers.
>
> Use a data structure that contains these values and pass as driver data
> using the platform
On 01/21/2016 12:19 PM, Jon Medhurst (Tixy) wrote:
On Thu, 2016-01-21 at 09:39 -0800, Laura Abbott wrote:
On 01/21/2016 03:57 AM, Jon Medhurst (Tixy) wrote:
From: Liviu Dudau
ion_buffer_create() will allocate a buffer and then create a DMA
mapping for it, but it forgot to set the length of
On 22.01.2016 05:23, Javier Martinez Canillas wrote:
> It is better to use the ARRAY_SIZE() macro instead of the array length
> to avoid bugs if the array is later changed and the length not updated.
>
> Signed-off-by: Javier Martinez Canillas
> Reviewed-by: Krzysztof Kozlowski
>
> ---
Tested
On Thu, Jan 21, 2016 at 07:53:10PM +0800, Xiangliang Yu wrote:
> Resend V5 for more convenient pick up.
> Main changes in V5
> Only change Signed-off-by to Reviewed-by.
Included in the NTB git tree.
Thanks,
Jon
>
> Xiangliang Yu (1):
> [Resend patch V5] NTB: Add support for AMD PCI-Express
On Thu, 2016-01-21 at 16:58 +0200, Kalle Valo wrote:
> Hi,
>
> I have quite a lot of random cleanup patches from new developers waiting
> in my queue:
>
> https://patchwork.kernel.org/project/linux-wireless/list/?state=10=25621=date
>
> (Not all of them are cleanup patches, there are also few
On 22.01.2016 05:23, Javier Martinez Canillas wrote:
> The function is always returning zero even in case of failures since
> the ret value was not propagated to the callers. Fix the error path.
>
> Reported-by: Krzysztof Kozlowski
> Signed-off-by: Javier Martinez Canillas
> ---
>
> Changes in
On 01/21/16 16:25, Luis R. Rodriguez wrote:
>>
>> Basically, if the hardware is enumerable using standard PC mechanisms (PCI,
>> ACPI) and doesn't need a special boot flow it should use type 0.
>
> I can extend the documentation as part of this to be clear.
>
> I will note though that this
On 21/01/2016 19:38, Doug Smythies wrote:
new = (old * 2037 + load * (2048 - 2037)) / 2048
new = (1862 * 2037 + 2048 * (2048 - 2037)) / 2048
new = 1862
So, the 100% load will always be shown as 91% (double the old limit).
Math seems sound, but the fact is that the load on all my test machines
Just hit this on Linus' current tree.
[ INFO: suspicious RCU usage. ]
4.4.0-think+ #1 Tainted: GW
---
./arch/x86/include/asm/msr-trace.h:47 suspicious rcu_dereference_check() usage!
other info that might help us debug this:
RCU used illegally from idle
Chris Mason wrote on 2016/01/21 12:06 -0500:
On Thu, Jan 14, 2016 at 10:07:31PM -0500, Dave Jones wrote:
I just hit a bunch of instances of this spew..
This is on Linus' tree from a few hours ago
==
BUG: KASAN: use-after-free in
On 2016-01-22 01:15, Prarit Bhargava wrote:
> Some systems erroneously set the maximum time window field of
> MSR_PKG_POWER_INFO register to 0. This results in a user not being able
> to set the time windows for the package. In some cases, however, RAPL
> will still continue to work with a small
On 2016-01-22 01:15, Prarit Bhargava wrote:
> The MSR_PKG_POWER_INFO register (Intel ASDM, section 14.9.3
> "Package RAPL Domain") provides a maximum time window which the
> system can support. This window is read-only and is currently
> not examined when setting the time windows for the package.
On Tue, 19 Jan 2016 09:25:25 -0500 Matthew Wilcox
wrote:
> Before diving into the important modifications, I add Andrew Morton's
> radix tree test harness to the tree in patches 1 & 2. It was absolutely
> invaluable in catching some of my bugs.
(cc Shuah for tools/testing/selftests)
Cool,
On Thu, Jan 21, 2016 at 03:56:35PM -0800, H. Peter Anvin wrote:
> On 01/21/16 14:25, Luis R. Rodriguez wrote:
> > On Thu, Jan 21, 2016 at 1:37 PM, Konrad Rzeszutek Wilk
> > wrote:
> >>> Sure, do we know if that ICC compatible? Do we care? There are a
> >>> series of ICC hacks put in place on
On Wed, Jan 20, 2016 at 2:20 PM, H. Peter Anvin wrote:
> On January 20, 2016 2:12:49 PM PST, "Luis R. Rodriguez"
> wrote:
>>On Wed, Jan 20, 2016 at 1:41 PM, H. Peter Anvin wrote:
>>> On 01/20/16 13:33, Luis R. Rodriguez wrote:
That's correct for PV and PVH, likewise when qemu is
Hi all,
On Thu, 21 Jan 2016 07:38:59 +1100 Stephen Rothwell
wrote:
>
> On Wed, 20 Jan 2016 15:09:47 +0100 Takashi Iwai wrote:
> >
> > On Sat, 16 Jan 2016 09:51:29 +0100,
> > Takashi Iwai wrote:
> > >
> > > There are a few ways to fix this, but all are not comfortable.
> > >
> > > A.
he system]
>
> url:
> https://github.com/0day-ci/linux/commits/Douglas-Anderson/usb-dwc2-host-Fix-and-speed-up-all-the-stuff-especially-with-splits/20160121-131414
> config: x86_64-randconfig-x019-01201142 (attached as .config)
> reproduce:
> # save the attached .config to
On Thu, Jan 21, 2016 at 11:52 AM, H. Peter Anvin wrote:
> On 01/21/16 11:50, H. Peter Anvin wrote:
>>
>> Right... we already do that.
>>
>> I don't even think you need to initialize any tables. At least on i386,
>> we have to do this in assembly code. However, it is just a simple table
>> walk.
Signed-off-by: Mario Limonciello
---
drivers/platform/x86/alienware-wmi.c | 32
1 file changed, 32 insertions(+)
diff --git a/drivers/platform/x86/alienware-wmi.c
b/drivers/platform/x86/alienware-wmi.c
index e66c34d..eccd547 100644
---
This allows configuration the system for wakeup with a controller.
Signed-off-by: Mario Limonciello
---
drivers/platform/x86/alienware-wmi.c | 103 ++-
1 file changed, 102 insertions(+), 1 deletion(-)
diff --git a/drivers/platform/x86/alienware-wmi.c
Signed-off-by: Mario Limonciello
---
drivers/platform/x86/alienware-wmi.c | 44
1 file changed, 29 insertions(+), 15 deletions(-)
diff --git a/drivers/platform/x86/alienware-wmi.c
b/drivers/platform/x86/alienware-wmi.c
index 1e1e594..dcd4f81 100644
---
Signed-off-by: Mario Limonciello
---
drivers/platform/x86/alienware-wmi.c | 114 ---
1 file changed, 93 insertions(+), 21 deletions(-)
diff --git a/drivers/platform/x86/alienware-wmi.c
b/drivers/platform/x86/alienware-wmi.c
index dcd4f81..e6f6322 100644
---
I've got some extensions for the alienware-wmi driver that have
been introduced for a few new platforms and can be controlled via the WMI
interface.
Mario Limonciello (4):
Add support for new platform, X51-R3
Add support for alienware graphics amplifier
Add support for deep sleep control.
On 01/21/2016 06:47 PM, H. Peter Anvin wrote:
> Well, and as you can see from the build robot because a lot of those
> drivers simply don't compile on 64-bit systems. If nothing else you
> would have to push the 32-bit tests downward in the config dependency tree.
>
> -hpa
Yes, you're
Hi,
On Thu, Jan 21, 2016 at 05:41:57PM -0500, Tejun Heo wrote:
> Hello, Shaohua.
>
> On Thu, Jan 21, 2016 at 02:24:51PM -0800, Shaohua Li wrote:
> > > Have you tried with some level, say 5, of nesting? IIRC, how it
> > > implements hierarchical control is rather braindead (and yeah I'm
> > >
On 01/21/16 14:25, Luis R. Rodriguez wrote:
> On Thu, Jan 21, 2016 at 1:37 PM, Konrad Rzeszutek Wilk
> wrote:
>>> Sure, do we know if that ICC compatible? Do we care? There are a
>>> series of ICC hacks put in place on ipxe's original solution which
>>> I've folded in, it seems that works but if
From: Reilly Grant
The new USBDEVFS_DROP_PRIVILEGES ioctl allows a process to voluntarily
relinquish the ability to issue other ioctls that may interfere with
other processes and drivers that have claimed an interface on the
device.
Signed-off-by: Reilly Grant
Signed-off-by: Emilio López
---
Em Thu, Jan 21, 2016 at 01:07:10PM +0900, Namhyung Kim escreveu:
> On Wed, Jan 20, 2016 at 09:52:45PM -0300, Arnaldo Carvalho de Melo wrote:
> > Em Sun, Jan 17, 2016 at 01:03:08AM +0900, Namhyung Kim escreveu:
> > > When symbol sort key is not given, it doesn't show any item other than
> > > exit.
On 01/21/16 15:43, William Breathitt Gray wrote:
> On 01/21/2016 02:40 PM, H. Peter Anvin wrote:
>> CONFIG_ISA is mainly used to exclude drivers that are for ISA-specific
>> devices.
>>
>> However, PC/104 is indeed an actual ISA parallel bus, and as you say
>> widely used in embedded systems.
On 01/21/2016 02:40 PM, H. Peter Anvin wrote:
> CONFIG_ISA is mainly used to exclude drivers that are for ISA-specific
> devices.
>
> However, PC/104 is indeed an actual ISA parallel bus, and as you say
> widely used in embedded systems. However, I would like to see if there
> are anything
>From: Josh Poimboeuf [mailto:jpoim...@redhat.com]
>
>The kretprobe_trampoline_holder() wrapper around kretprobe_trampoline()
>isn't used anywhere and adds some unnecessary frame pointer instructions
>which never execute. Instead, just make kretprobe_trampoline() a proper
>ELF function.
>
Looks
On Thu, Jan 21, 2016 at 3:22 PM, Jann Horn wrote:
> On Mon, Jan 11, 2016 at 02:57:50PM -0800, Kees Cook wrote:
>> Normally, when a user can modify a file that has setuid or setgid bits,
>> those bits are cleared when they are not the file owner or a member
>> of the group. This is enforced when
Maybe a label attribute would help, I don't know.
-hpa
On 01/21/16 14:56, Borislav Petkov wrote:
>
> so this is silly: we're basically jumping after the JMP instruction
> itself. So that will be the case on !X86_BUG_SYSRET_SS_ATTRS CPUs.
> Still a two-byte and now even a useless JMP.
>
> The right thing to do would be to generate a NOP simply.
>
On 01/19/2016 09:31 AM, Peter Zijlstra wrote:
> On Sun, Jan 10, 2016 at 03:55:13PM -0500, Sasha Levin wrote:
>> Hi all,
>>
>> While fuzzing with trinity inside a KVM tools guest, running the latest -next
>> kernel, I've hit the following warning:
>>
>> [ 3494.030114] UBSAN: Undefined behaviour in
On Mon, Jan 11, 2016 at 02:57:50PM -0800, Kees Cook wrote:
> Normally, when a user can modify a file that has setuid or setgid bits,
> those bits are cleared when they are not the file owner or a member
> of the group. This is enforced when using write and truncate but not
> when writing to a
Hi Linus,
Can you please pull the changes from the tag below? This is the
second update for XFS that I mentioned in the original pull request
last week. It contains a revert for a suspend regression in 4.4 and
a fix for a long standing log recovery issue that has been further
exposed by all the
On Thu, 21 Jan 2016 14:55:00 -0800 Kees Cook wrote:
> IIUC, this means that the relocation work done after decompression now
> doesn't have to do relocation updates for all these values, which
> means a smaller relocation table as well.
Makes sense, thanks. I altered the changelog
: Similar
On 01/21/2016 04:03 PM, John Stultz wrote:
> David Herrmann mailed me pointing out that one of the
> changes that landed in 4.5-rc broke users of ADJ_SETOFFSET
> when used with ADJ_NANO.
>
> I've implemented a fix to this issue and also introduced
> more unit tests to validate these going
On Thu, 21 Jan 2016, Tetsuo Handa wrote:
> I consider phases for managing system-wide OOM events as follows.
>
> (1) Design and use a system with appropriate memory capacity in mind.
>
> (2) When (1) failed, the OOM killer is invoked. The OOM killer selects
> an OOM victim and allow
On Thu, Jan 21, 2016 at 03:09:15PM +0800, Yuan Yao wrote:
> new compatible string: "fsl,ls2080a-qspi".
>
> Signed-off-by: Yuan Yao
> ---
> Changed in v3:
> Add the modifier for new compatible string like:
> "fsl,ls2080a-dspi" followed by "fsl,ls2085a-dspi"
>
> Changed in v2:
> Update my email
On Thu, 21 Jan 2016, Mika Penttilä wrote:
> Recent changes (4.4.0+) in module loader triggered oops on ARM :
>
> The module in question is in-tree module :
> drivers/misc/ti-st/st_drv.ko
>
> The BUG is here :
>
> [ 53.638335] [ cut here ]
> [ 53.642967] kernel BUG at
On Thu, Jan 21, 2016 at 03:09:16PM +0800, Yuan Yao wrote:
> new compatible string: "fsl,ls2080a-qspi".
>
> Signed-off-by: Yuan Yao
> ---
> Changed in v3:
> Add the modifier for new compatible string like:
> "fsl,ls2080a-qspi" followed by "fsl,ls1021a-qspi"
>
> Changed in v2:
> Update my email
On Thu, Jan 21, 2016 at 03:09:18PM +0800, Yuan Yao wrote:
> Add optional properties for QSPI:
> big-endian
> if the register is big endian on this platform.
>
> Signed-off-by: Yuan Yao
> ---
> Changed in v3:
> No changes.
>
> Changed in v2:
> Update my email to
> ---
>
On Thu, Jan 21, 2016 at 08:32:09PM +0800, Shawn Lin wrote:
> rk3368 dtsi file add dw-mshc compatible "rockchip,rk3368-dw-mshc"
> but didn't add it into rockchip-dw-mshc.txt.
>
> Signed-off-by: Shawn Lin
> ---
>
> Documentation/devicetree/bindings/mmc/rockchip-dw-mshc.txt | 1 +
> 1 file
On Thu, Jan 21, 2016 at 02:02:39PM -0800, Gayatri Kammela wrote:
> Adding these pr_info and pr_err definitions so as to allow code to be
> compiled successfully for testing in userspace, since the printk has
> been replaced by pr_info and pr_err in algos.c
>
> Absence of these definitions result
Add some simple tests to check both valid and invalid
offsets when using adjtimex's ADJ_SETOFFSET method.
Cc: Sasha Levin
Cc: Richard Cochran
Cc: Thomas Gleixner
Cc: Prarit Bhargava
Cc: Harald Hoyer
Cc: Kay Sievers
Cc: David Herrmann
Cc: Shuah Khan
Signed-off-by: John Stultz
---
David Herrmann mailed me pointing out that one of the
changes that landed in 4.5-rc broke users of ADJ_SETOFFSET
when used with ADJ_NANO.
I've implemented a fix to this issue and also introduced
more unit tests to validate these going forward.
Thomas: Can you queue the first patch for
Recently, in commit 37cf4dc3370f
("time: Verify time values in adjtimex ADJ_SETOFFSET to avoid overflow")
I forgot to check if the timeval being passed was actually a
timespec (as is signaled with ADJ_NANO).
This resulted in that patch breaking ADJ_SETOFFSET users who set
ADJ_NANO, by rejecting
[trying to use git request-pull; result looks more or less sane, AFAICT...]
Embarrassing braino fix + pipe page accounting + fixing an eyesore in
find_filesystem() (checking that s1 is equal to prefix of s2 of given length
can be done in many ways, but "compare strlen(s1) with length and then do
The callable functions created with the FOP* and FASTOP* macros are
missing ELF function annotations, which confuses tools like stacktool.
Properly annotate them.
This adds some additional labels to the assembly, but the generated
binary code is unchanged (with the exception of instructions which
Add a CONFIG_STACK_VALIDATION option which will run "stacktool check"
for each .o file to ensure the validity of its stack metadata.
Signed-off-by: Josh Poimboeuf
---
Makefile | 5 -
arch/Kconfig | 6 ++
lib/Kconfig.debug | 12
On 01/21/2016 04:29 AM, Ding Tianhong wrote:
I build a script to create several process for ioctl loop calling,
the ioctl will calling the kernel function just like:
xx_ioctl {
...
rtnl_lock();
function();
rtnl_unlock();
...
}
The function may sleep several ms, but will not halt, at the same
xen_adjust_exception_frame() is a callable function, but is missing the
ELF function type, which confuses tools like stacktool.
Properly annotate it to be a callable function. The generated code is
unchanged.
Signed-off-by: Josh Poimboeuf
Cc: Konrad Rzeszutek Wilk
Cc: Boris Ostrovsky
Cc:
If a hypercall is inlined at the beginning of a function, gcc can insert
the call instruction before setting up a stack frame, which breaks frame
pointer convention if CONFIG_FRAME_POINTER is enabled and can result in
a bad stack trace.
Force a stack frame to be created if CONFIG_FRAME_POINTER is
xen_irq_enable_direct(), xen_restore_fl_direct(), and check_events() are
callable non-leaf functions which don't honor CONFIG_FRAME_POINTER,
which can result in bad stack traces.
Create stack frames for them when CONFIG_FRAME_POINTER is enabled.
Signed-off-by: Josh Poimboeuf
Cc: Konrad
Add a new stacktool ignore macro, STACKTOOL_IGNORE_FUNC, which can be
used to tell stacktool to skip validation of a function.
Signed-off-by: Josh Poimboeuf
---
MAINTAINERS | 1 +
arch/x86/kernel/vmlinux.lds.S | 5 -
include/linux/stacktool.h | 23
do_suspend_lowlevel() is a callable non-leaf function which doesn't
honor CONFIG_FRAME_POINTER, which can result in bad stack traces.
Create a stack frame for it when CONFIG_FRAME_POINTER is enabled.
Signed-off-by: Josh Poimboeuf
Acked-by: Pavel Machek
Acked-by: Rafael J. Wysocki
Reviewed-by:
The frame pointer (rbp) is getting clobbered in
sha1_mb_mgr_submit_avx2() before a function call, which can mess up
stack traces. Use r12 instead.
Signed-off-by: Josh Poimboeuf
---
arch/x86/crypto/sha-mb/sha1_mb_mgr_submit_avx2.S | 8
1 file changed, 4 insertions(+), 4 deletions(-)
sha1_mb_mgr_flush_avx2() and sha1_mb_mgr_submit_avx2() both allocate a
lot of stack space which is never used. Also, many of the registers
being saved aren't being clobbered so there's no need to save them.
Signed-off-by: Josh Poimboeuf
---
arch/x86/crypto/sha-mb/sha1_mb_mgr_flush_avx2.S | 32
A function created with the PV_CALLEE_SAVE_REGS_THUNK macro doesn't set
up a new stack frame before the call instruction, which breaks frame
pointer convention if CONFIG_FRAME_POINTER is enabled and can result in
a bad stack trace. Also, the thunk functions aren't annotated as ELF
callable
101 - 200 of 1696 matches
Mail list logo
