There can be multiple IC tasks using the IRT, so the IRT needs
a separate use counter. Create a private ipu_irt_enable() to
enable the IRT module when any IC task requires rotation, and
ipu_irt_disable() when a task no longer needs the IRT.
Signed-off-by: Steve Longerbeam
---
v3: no changes
v2:
The image converter kernel API supports conversion contexts and
job queues, so we should allow more than one handle to the IC, so
that multiple users can add jobs to the queue.
Note however that users that control the IC manually (that do not
use the image converter APIs but setup the IC task by h
The CSI data format was being programmed incorrectly for the
1x16 media bus formats. The CSI data format for 16-bit must
be bayer/generic (CSI_SENS_CONF_DATA_FMT_BAYER).
Suggested-by: Carsten Resch
Signed-off-by: Steve Longerbeam
---
v3: no changes
v2: no changes
---
drivers/gpu/ipu-v3/ipu-cs
UBIFS uses full names to work with xattrs, therefore we have to use
xattr_full_name() to obtain the xattr prefix as string.
Cc:
Cc: Andreas Gruenbacher
Fixes: 2b88fc21ca ("ubifs: Switch to generic xattr handlers")
Signed-off-by: Richard Weinberger
---
fs/ubifs/xattr.c | 5 -
1 file changed
Adds the Video Deinterlacer (VDIC) unit.
Signed-off-by: Steve Longerbeam
---
v3:
- renamed and exported ipu_vdi_set_top_field_man() to
ipu_vdi_set_field_order(). Args include std and field to determine
correct field order.
- exported ipu_vdi_set_motion().
- ipu_vdi_setup() does not need to
This patch implements complete image conversion support to ipu-ic,
with tiling to support scaling to and from images up to 4096x4096.
Image rotation is also supported.
The internal API is subsystem agnostic (no V4L2 dependency except
for the use of V4L2 fourcc pixel formats).
Callers prepare for
From: Sunil Kovvuri
Date: Mon, 1 Aug 2016 00:44:08 +0800
> A gentle reminder.
>
> David,
> Let me know if I need to resubmit the patches on top of latest net-next.
> Will do that.
Your patches are marked appropriately in patchwork and tell you everything
you need to know about the state of your
On Fri, Jul 29, 2016 at 6:45 PM, Rafał Miłecki wrote:
> From: Rafał Miłecki
>
> This clock is present on cheaper Northstar devices like BCM53573 or
> BCM47189 using Corex-A7. This driver uses PMU (Power Management Unit)
> to calculate clock rate and allows using it in a generic (clk_*) way.
>
> S
As the IPU has combined limitations across multiple crtcs, and as that
can't be communicated to userspace at the moment, reorder the crtcs to
allow support to two Full-HD monitors by avoiding assigning two
monitors to a single IPU.
Cc: Enric Balletbo i Serra
Cc: Philipp Zabel
Cc: Rob Herring
Cc
Devicetree bindings documentation for the GE B850v3 LVDS/DP++
display bridge.
Cc: Javier Martinez Canillas
Cc: Enric Balletbo i Serra
Cc: Philipp Zabel
Cc: Rob Herring
Cc: Fabio Estevam
Signed-off-by: Peter Senna Tschudin
---
Unchanged from V2.
Changes from V1:
- Replaced '_' by '-' in nod
The series adds a driver that creates a drm_bridge and a drm_connector for the
LVDS to DP++ display bridge of the GE B850v3.
There are two physical bridges on the video signal pipeline: a STDP4028(LVDS to
DP) and a STDP2690(DP to DP++). The hardware and firmware made it complicated
for this bindi
On 07/31/2016 12:42 PM, Steve Longerbeam wrote:
> In this version:
>
> - API changes to ipu-vdi.c in "gpu: ipu-v3: Add Video Deinterlacer unit".
> - "gpu: ipu-v3: Add FSU channel linking support" is new but based on
> previous patch "gpu: ipu-v3: Add IDMA channel linking support".
>
> No other ch
Add support to attach a drm_bridge to imx-ldb in addition to
existing support to attach a LVDS panel.
This patch does a simple code refactoring by moving code
from for_each_child_of_node iterator to a new function named
imx_ldb_panel_ddc(). This was necessary to allow the panel ddc
code to run onl
Add a driver that create a drm_bridge and a drm_connector for the LVDS
to DP++ display bridge of the GE B850v3.
There are two physical bridges on the video signal pipeline: a
STDP4028(LVDS to DP) and a STDP2690(DP to DP++). The hardware and
firmware made it complicated for this binding to compris
Configures the GE B850v3 LVDS/DP++ bridge on the dts file.
Cc: Javier Martinez Canillas
Cc: Enric Balletbo i Serra
Cc: Philipp Zabel
Cc: Rob Herring
Cc: Fabio Estevam
Signed-off-by: Peter Senna Tschudin
---
Unchanged from V2.
Changes from V1:
- Replaced '_' by '-' in node names or compatib
On Fri, Jul 29, 2016 at 07:48:00AM +0200, Jean-Francois Moine wrote:
> On Thu, 28 Jul 2016 22:07:05 +0200
> Maxime Ripard wrote:
>
> > > > Let me know what you think,
> > >
> > > I don't see the interest to have common code for 32bits and 64bits.
> > > The clock driver of a SoC will never evolve
Hi,
On Fri, Jul 29, 2016 at 12:01:09AM +0200, Ondřej Jirman wrote:
> On 28.7.2016 23:00, Maxime Ripard wrote:
> > Hi Ondrej,
> >
> > On Thu, Jul 28, 2016 at 01:27:05PM +0200, Ondřej Jirman wrote:
> >> Hi Maxime,
> >>
> >> I don't have your sunxi-ng clock patches in my mailbox, so I'm replying
> >
Remove *befs_sb and just call BEFS_SB(sb) directly, since the returned
value by this function is only used once.
Signed-off-by: Salah Triki
---
fs/befs/datastream.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/fs/befs/datastream.c b/fs/befs/datastream.c
index b68b6f9..34
off is reinitialized by befs_read_datastream, so no need to init it with
zero in the beginning of befs_bt_read_node.
Signed-off-by: Salah Triki
---
fs/befs/btree.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/befs/btree.c b/fs/befs/btree.c
index e59ad20..a0e8cfa 100644
ret is initialized to -EIO and is never modified, so remove ret and use
-EIO directly.
Signed-off-by: Salah Triki
---
fs/befs/linuxvfs.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/fs/befs/linuxvfs.c b/fs/befs/linuxvfs.c
index 2b68c81..c57f831 100644
--- a/fs/befs/linux
node_off is unconditionally set to bt_super.root_node_ptr, so no need to
init it to zero.
Signed-off-by: Salah Triki
---
fs/befs/btree.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/befs/btree.c b/fs/befs/btree.c
index f33fc6c..3cb97e8 100644
--- a/fs/befs/btree.c
+++ b
There is no need to init res, since it will be overwitten later by
befs_fblock2brun().
Signed-off-by: Salah Triki
---
fs/befs/linuxvfs.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/befs/linuxvfs.c b/fs/befs/linuxvfs.c
index 6bc5b40..2b68c81 100644
--- a/fs/befs/linuxvf
There is no need to set *value, it will be overwritten later.
Signed-off-by: Salah Triki
---
fs/befs/btree.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/fs/befs/btree.c b/fs/befs/btree.c
index a0e8cfa..f33fc6c 100644
--- a/fs/befs/btree.c
+++ b/fs/befs/btree.c
@@ -348,8 +348,6 @@ befs_f
On Sun, 2016-07-31 at 14:17 +0200, Robert Jarzmik wrote:
> The commit 9bf448c66d4b ("ARM: pxa: use generic gpio operation instead of
> gpio register") from Oct 17, 2011, leads to the following static checker
> warning:
> arch/arm/mach-pxa/spitz_pm.c:172 spitz_charger_wakeup()
> warn: double lef
On Sun, Jul 31, 2016 at 09:46:53AM -0700, Kees Cook wrote:
> On Sat, Jul 30, 2016 at 8:42 AM, Jason Cooper wrote:
> > To date, all callers of randomize_range() have set the length to 0, and
> > check for a zero return value. For the current callers, the only way
> > to get zero returned is if end
Hi Eric,
On 07/29/2016 08:05 PM, Eric W. Biederman wrote:
"Michael Kerrisk (man-pages)" writes:
Hi Eric,
On 07/28/2016 02:56 PM, Eric W. Biederman wrote:
"Michael Kerrisk (man-pages)" writes:
On 07/26/2016 10:39 PM, Andrew Vagin wrote:
On Tue, Jul 26, 2016 at 09:17:31PM +0200, Michael K
On Tue, 26 Jul, at 03:55:24PM, Andy Lutomirski wrote:
> As currently configured, my laptop cannot boot any existing kernel
> because the real mode trampoline can't be reserved. The ranges in
> which it could live are rejected by the kernel: one is EFI boot
> services data and the other is above th
Hi,
On 31.7.2016 12:31, Maxime Ripard wrote:
> Hi,
>
> On Fri, Jul 29, 2016 at 12:01:09AM +0200, Ondřej Jirman wrote:
>> On 28.7.2016 23:00, Maxime Ripard wrote:
>>> Hi Ondrej,
>>>
>>> On Thu, Jul 28, 2016 at 01:27:05PM +0200, Ondřej Jirman wrote:
Hi Maxime,
I don't have your sunxi
Hi Joe,
Joe Perches writes:
> trivially:
>> diff --git a/arch/arm/mach-pxa/corgi_pm.c b/arch/arm/mach-pxa/corgi_pm.c
> []
>> @@ -131,15 +131,13 @@ static int corgi_should_wakeup(unsigned int
>> resume_on_alarm)
>> return is_resume;
>> }
>>
>> -static unsigned long corgi_charger_wakeup(vo
Salil Kapur :
> I was looking at v3.12. Can we submit patches for stable versions?
It has already been fixed in 3.12.8 as 56399d8b44beae5b80e1eda0350ab6af72baf4d0
("netpoll: Fix missing TXQ unlock and and OOPS.") by davem.
3.12.8 dates back to 2014/01. The current 3.12.x version is 3.12.62.
--
On 07/27/2016 01:17 PM, Rasmus Villemoes wrote:
On 2016-07-21 02:31, Guenter Roeck wrote:
On Thu, Jul 21, 2016 at 12:08:52AM +0200, Rasmus Villemoes wrote:
I hear you. "configure hardware" is a slippery term, though. After all,
one would typically configure the initial timeout in hardware, just
On Mon, 2016-08-01 at 00:04 +0200, Robert Jarzmik wrote:
> Joe Perches writes:
[]
> > These might be better without the automatic use of ret
> >
> > return !gpio_get_value(CORGI_GPIO_AC_IN) ||
> > !gpio_get_value(CORGI_GPIO_KEY_INT) ||
> > !gpio_get_value(CORGI_GPIO_WAKE
Hi Daniel,
On Fri, Jul 29, 2016 at 06:10:02AM -0400, Daniel Micay wrote:
> > > In the Project Zero Stagefright post
> > > (http://googleprojectzero.blogspot.com/2015/09/stagefrightened.html)
> > > , we see that the linear allocation of memory combined with the
> > > low number of bits in the initi
On Sat, Jul 30, 2016 at 12:31:40PM -0500, Eric W. Biederman wrote:
> Cyrill Gorcunov writes:
>
> > On Mon, Jul 25, 2016 at 02:56:43PM -0500, Eric W. Biederman wrote:
> > ...
> >> >>
> >> >> Also there is a big fat bug in prctl_set_mm_exe_file. It doesn't
> >> >> validate that the new file is a a
On 2016-07-29 23:25, Rob Herring wrote:
> On Wed, Jul 27, 2016 at 10:43:26AM +0200, Peter Rosin wrote:
>> Handle i2c gates similarly to how i2c arbitrators are handled.
>> This gets rid of a pointless 'reg' property for i2c gates.
>>
>> I.e. this new and more compact style
>>
>> some-gate {
On Sun, Jul 31, 2016 at 3:43 PM, Cyrill Gorcunov wrote:
> On Sat, Jul 30, 2016 at 12:31:40PM -0500, Eric W. Biederman wrote:
>> Cyrill Gorcunov writes:
>>
>> > On Mon, Jul 25, 2016 at 02:56:43PM -0500, Eric W. Biederman wrote:
>> > ...
>> >> >>
>> >> >> Also there is a big fat bug in prctl_set_mm
On Mon, Jul 25, 2016 at 04:59:17PM +0200, Pali Rohár wrote:
> On Friday 22 July 2016 10:12:19 Peter Hutterer wrote:
> > On Thu, Jul 21, 2016 at 11:04:29AM +0200, Pali Rohár wrote:
> > > On Thursday 21 July 2016 10:54:21 Pavel Machek wrote:
> > > > On Thu 2016-07-21 16:42:41, Peter Hutterer wrote:
>
On Mon, Jul 25, 2016 at 11:56:51AM -0400, Theodore Ts'o wrote:
> As a reminder, please suggest topics and nominations (including
> potentially self-nominations) by the end of this week, if at all
> possible. Also please check the nominations list:
>
> https://goo.gl/79tJFx
Thanks for all
From: Rafael J. Wysocki
The PID-base P-state selection algorithm used by intel_pstate for
Core processors is based on very weak foundations. Namely, its
decisions are mostly based on the values of the APERF and MPERF
feedback registers and it only estimates the actual utilization to
check if it
From: Rafael J. Wysocki
Modify the schedutil cpufreq governor to boost the CPU frequency
if the UUF_IO flag is passed to it via cpufreq_update_util().
If that happens, the frequency is set to the maximum during
the first update after receiving the UUF_IO flag and then the
boost is reduced by hal
From: Peter Zijlstra
Since the schedutil governor is part of the scheduler proper, it can
access scheduler data directly.
This allows us to remove the util and max arguments of
cpufreq_update_util(), since only the schedutil governor will use
those, which leads to some text reduction:
43595
From: Rafael J. Wysocki
All of the callers of cpufreq_update_util() check whether or not
cpu_of(rq) is equal to smp_processor_id() before calling it and pass
rq_clock(rq) to it as the time argument, so rework it to take a
runqueue pointer as the argument and move the cpu_of(rq) check and
the rq_c
From: Rafael J. Wysocki
After dropping the util and max arguments of cpufreq_update_util(),
the cpufreq_trigger_update() wrapper around it is pointless, so drop
it and call cpufreq_update_util() directly instead.
Signed-off-by: Rafael J. Wysocki
---
kernel/sched/deadline.c |4 ++--
kernel/
Hi,
Admittedly, this hasn't been tested yet, so no promises and you have been
warned. It builds, though (on x86-64 at least).
At this point I'm looking for general feedback mostly: does the direction make
sense or is there any reason why it can't work (that I'm not seeing), is it
acceptable and
From: Rafael J. Wysocki
Testing indicates that it is possible to improve performace
significantly without increasing energy consumption too much by
teaching cpufreq governors to bump up the CPU performance level if
the in_iowait flag is set for the task in enqueue_task_fair().
For this purpose,
From: Rafael J. Wysocki
It is useful to know the reason why cpufreq_update_util() has just
been called, so add a flags argument to it and to the ->func()
callback in struct update_util_data.
Update all of the users of them accordingly and use the flags
argument for marking updates coming from th
Hi Robin,
> -Original Message-
> From: Robin Murphy [mailto:robin.mur...@arm.com]
> Sent: Saturday, July 30, 2016 2:06 AM
> To: 이광우(LEE KWANGWOO) MS SW; Russell King - ARM Linux; Catalin Marinas; Will
> Deacon; Mark Rutland;
> linux-arm-ker...@lists.infradead.org
> Cc: 김현철(KIM HYUNCHUL) M
Sorry I didn't notice earlier - my 3.18/4.1 build scripts were broken.
arch/mips/kernel/setup.c: In function 'arch_mem_init':
arch/mips/kernel/setup.c:689:2: error: implicit declaration of function
'reserve_bootmem_region'
Offending commit is 1dd0964204277108e ("MIPS: Reserve nosave data for
h
When a fault in ___copy_from_user happens, the function
copy_from_user_fixup is called. It calls the function compute_size that
reads the faulting address from current_thread_info()->fault_address and
determines how many bytes were copied.
There are multiple ___copy_from_user implementations for v
When a fault happens in the function ___copy_in_user, it returns 1. Then,
we call a function copy_in_user_fixup that determines how much data were
left uncopied and it returns this value.
The function copy_in_user_fixup reads the faulting address from
current_thread_info()->fault_address and check
[ again, this time with Sasha's new e-mail address, and updated ]
Build failures in v3.18.38 and 4.1.29:
mips builds:
arch/mips/kernel/setup.c: In function 'arch_mem_init':
arch/mips/kernel/setup.c:689:2: error: implicit declaration of function
'reserve_bootmem_region'
Offending commit is 1dd
v1->v2: change nr_cpus to maxcpus
SMP dump-capture kernel is useful to improve the performance of kdump in
some cases. So add the description of bringing up SMP dump-capture kernel.
Signed-off-by: Zhou Wenjian
---
Documentation/kdump/kdump.txt | 6 ++
1 file changed, 6 insertions(+)
diff -
> > It's very hard to quantify the benefits of fine-grained
> > randomization,
>
> ? N = # of possible addresses. The bigger N is, the more chances the
> attacker will trip up before finding what they were looking for.
If the attacker is forcing the creation of many objects with a function
poin
Hi, Benjamin
> From: Benjamin Tissoires [mailto:benjamin.tissoi...@redhat.com]
> Subject: [PATCH v2] ACPI / button: remove pointer to old lid_sysfs on
> unbind
>
> When we removed the procfs dir on error or if the driver is
> unbound, the two variables acpi_lid_dir and acpi_button_dir
> were not
On Thu, 28 Jul 2016, Kees Cook wrote:
> On Mon, Jul 11, 2016 at 6:59 PM, Kees Cook wrote:
> > On Mon, Jul 11, 2016 at 5:56 PM, Mickaël Salaün wrote:
> >> Hi,
> >>
> >> This series fix the recent seccomp update for the User-mode Linux
> >> architecture
> >> (32-bit and 64-bit) since commit 26703
The following changes since commit 3fc9d690936fb2e20e180710965ba2cc3a0881f8:
Merge branch 'for-4.8/drivers' of git://git.kernel.dk/linux-block (2016-07-26
15:37:51 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/rusty/linux.git
tags/modules-next
Hi Mike,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: c9b95e5961c0294e0efffeaa847c1a1e6369204c
commit: 4e1b2d52a80d79296a5d899d73249748dea71a53 block, fs, drivers: remove
REQ_OP compat defs and related code
date:
On 7/30/2016 05:44, Rob Herring wrote:
On Fri, Jul 29, 2016 at 03:54:08PM +0800, Songjun Wu wrote:
DT binding documentation for ISC driver.
Signed-off-by: Songjun Wu
---
Changes in v7: None
Changes in v6:
- Add "iscck" and "gck" to clock-names.
Changes in v5:
- Add clock-output-names.
Cha
2016-07-29 17:10 GMT+09:00 Marc Zyngier :
> On 29/07/16 04:53, Masahiro Yamada wrote:
>> Hi.
>>
>>
>> I noticed my board would not work any more
>> when pulling recent updates.
>>
>>
>> I did "git-bisect" and I found the following commit is it.
>
> It would help if you did post the log showing the
On Sat, Jul 30, 2016 at 1:57 AM, John Stultz wrote:
>
> With the patch reverted, and the system working, I see:
>
> # ip rule ls
> 0: from all lookup local
> 1: from all fwmark 0xc/0xd lookup legacy_system
> 13000: from all fwmark 0x10063/0x1 lookup local_network
> 13000:
From: yuanjian
Add pwm driver for HiSilicon BVT SOCs
Reviewed-by: Jiancheng Xue
Signed-off-by: Jian Yuan
---
.../devicetree/bindings/pwm/pwm-hibvt.txt | 18 ++
drivers/pwm/Kconfig| 10 +
drivers/pwm/Makefile | 1 +
dri
Hi Maxime,
On 26/07/16 21:30, Maxime Ripard wrote:
> Hi,
>
> Here is the previous A64 patches made by Andre [1], reworked to use
> the new sunxi-ng clock framework.
>
> This uses the current H3 clock code, as both are really similar. The
> first patches are just meant to rework slightly the H3 c
So this feels wrong to me, can you guys please explain:
On Sun, Jul 31, 2016 at 9:02 PM, Rusty Russell wrote:
>
> Ben Hutchings (3):
> module: Invalidate signatures on force-loaded modules
> module: Disable MODULE_FORCE_LOAD when MODULE_SIG_FORCE is enabled
forcing a load and SIG_FOR
On Sun, Jul 31, 2016 at 8:23 PM, Wu, Songjun wrote:
>
>
> On 7/30/2016 05:44, Rob Herring wrote:
>>
>> On Fri, Jul 29, 2016 at 03:54:08PM +0800, Songjun Wu wrote:
>>>
>>> DT binding documentation for ISC driver.
>>>
>>> Signed-off-by: Songjun Wu
>>> ---
>>>
>>> Changes in v7: None
>>> Changes in
On 07/29/2016 04:38 PM, Tomeu Vizoso wrote:
On 5 April 2016 at 04:06, Yakir Yang wrote:
Hi Daniel,
On 03/31/2016 06:15 PM, Daniel Vetter wrote:
On Mon, Feb 15, 2016 at 07:08:05PM +0800, Yakir Yang wrote:
Hi all,
The Samsung Exynos eDP controller and Rockchip RK3288 eDP controller
shar
add Hisilicon BVT I2C controller driver support.
Signed-off-by: Pan Wen
---
change log
v3:
Add a SoC specific compatible string.
v2:
1)Fixed a compile error.
2)Dropped the clock-names property.
.../devicetree/bindings/i2c/i2c-hibvt.txt | 24 +
drivers/i2c/busses/Kconfig
Hi, Alex
On 2016/7/30 1:11, Alex Williamson wrote:
On Tue, 19 Jul 2016 15:52:45 +0800
Zhou Jie wrote:
From: Chen Fan
An empty commit log is unacceptable for all but the most trivial
patches.
There's also no sign-off on this patch.
Sorry. I should note it.
I also don't know why we need
Hi, Alex
On 2016/7/30 1:12, Alex Williamson wrote:
On Tue, 19 Jul 2016 15:32:43 +0800
Zhou Jie wrote:
From: Chen Fan
During aer err occurs and resume do following to
protect device from being accessed.
1. Make config space read only.
2. Disable INTx/MSI Interrupt.
3. Do nothing for bar regi
On Fri, Jul 29, 2016 at 01:06:48PM -0700, Matthias Kaehlcke wrote:
> Hi Peter,
>
> Thanks for your work on this, a few comments inline
>
>
> On 07/20/2016 02:40 AM, Peter Chen wrote:
>
> >...
> >
> >+static int pwrseq_generic_on(struct device_node *np, struct pwrseq *pwrseq)
> >+{
> >
> >...
>
On Do, 2016-07-28 at 11:30 -0700, Kees Cook wrote:
> On Tue, Jul 12, 2016 at 5:48 AM, James Morris wrote:
> > On Sat, 9 Jul 2016, Mickaël Salaün wrote:
> >
> >> Fixes: a1db74209483 ("module: replace copy_module_from_fd with kernel
> >> version")
> >>
> >> Signed-off-by: Mickaël Salaün
> >> Cc: M
Hi,
While investigating a strange OOM issue on the 3.18.x branch (which
turned out to be already fixed by 52c84a95), I've noticed a strange
difference in Dirty/Writeback fields in /proc/meminfo depending on
kernel version. I'm wondering whether this is expected ...
I've bisected the change t
Hi Serge,
[auto build test WARNING on ntb/ntb-next]
[cannot apply to v4.7 next-20160729]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Serge-Semin/ntb-Asynchronous-NTB-devices-support/20160728-
Sorry.
An inline function will be inserted into the calling function. Why
"Assigning NULL to parmeter dcb has no effect outside of the
inlined function." ?
On Sun, Jul 31, 2016 at 6:07 PM, Heinrich Schuchardt wrote:
> Assigning NULL to parmeter dcb has no effect outside of the
> inlined function.
[+cc from "Enable use of Solid State Hybrid Drives"
https://lkml.org/lkml/2014/10/29/698 ]
On Thu, 28 Jul 2016, Martin K. Petersen wrote:
> > "Eric" == Eric Wheeler writes:
> Eric> [...] This may imply that
> Eric> we need a new way to flag cache bypass from userspace [...]
> Eric> S
I have a business proposal for you contact me for more info
在 2016/7/30 5:34, Rob Herring 写道:
On Fri, Jul 29, 2016 at 09:22:05AM +0800, Shawn Lin wrote:
This patch adds a binding that describes the Rockchip PCIe PHY
found on Rockchip SoCs PCIe interface.
Signed-off-by: Shawn Lin
---
Changes in v4: None
Changes in v3:
- rename the node to pcie_phy: pc
Hi Jon,
2016-07-29 17:31 GMT+09:00 Jon Hunter :
>
> On 29/07/16 04:53, Masahiro Yamada wrote:
>> Hi.
>>
>> I noticed my board would not work any more
>> when pulling recent updates.
>>
>> I did "git-bisect" and I found the following commit is it.
>>
>> commit 1e2a7d78499ec8859d2b469051b7b80bad3b08
Hi Linus,
The following changes since commit 8714f8f5fe396ca513ccaaac2304497439c181fb:
Merge branch 'for-linus' of git://git.kernel.dk/linux-block
(2016-06-11 18:42:59 -0700)
are available in the git repository at:
git://git.linaro.org/landing-teams/working/fujitsu/integration.git
mailbox-f
move the driver from drivers/soc/fsl/qe to drivers/irqchip,
merge qe_ic.h and qe_ic.c into irq-qeic.c.
Signed-off-by: Zhao Qiang
---
Changes for v2:
- modify the subject and commit msg
Changes for v3:
- merge .h file to .c, rename it with irq-qeic.c
Changes for v4:
- modif
The codes of qe_ic init from a variety of platforms are redundant,
merge them to a common function and put it to irqchip/irq-qeic.c
For non-p1021_mds mpc85xx_mds boards, use "qe_ic_init(np, 0,
qe_ic_cascade_low_mpic, qe_ic_cascade_high_mpic);" instead of
"qe_ic_init(np, 0, qe_ic_cascade_muxed_mpic
qeic_of_init just get device_node of qeic from dtb and call qe_ic_init,
pass the device_node to qe_ic_init.
So merge qeic_of_init into qe_ic_init to get the qeic node in
qe_ic_init.
Signed-off-by: Zhao Qiang
---
Changes for v2:
- modify subject and commit msg
- return 0 and add pu
On Sun, Jul 31, 2016 at 6:44 PM, Nadim almas wrote:
> This patch compresses two lines in to a single line in file
> ion.c
> if immediate return statement is found.It also removes variable
> ret as it is no longer needed.
>
> ne using script Coccinelle. And coccinelle uses following semantic
> patc
Hi Bjorn,
On 2016/7/30 0:48, Bjorn Helgaas wrote:
Hi Shawn,
You fixed some of the things I mentioned, but not all, and you
over-fixed some things, leading to issues.
On Fri, Jul 29, 2016 at 10:48:13AM +0800, Shawn Lin wrote:
This patch adds Rockchip PCIe controller support found
on RK3399 Soc
在 2016/7/29 17:21, Ulf Hansson 写道:
On 29 July 2016 at 06:14, Shawn Lin wrote:
We need to enable the power domain manually while probing as the
power policy will turn off the pd which is not referenced. Otherwise
I assume you are going to use the generic PM domain (genpd)?
yes.
If so, thi
Building an X86_64 kernel with W=1 throws a total of 9,948 lines of warnings of
this form for both 32bit and 64bit syscall tables. Given that the entire rest
of the build for my config only generates 8,375 lines of output, this is a big
reduction in the warnings generated.
./arch/x86/include/gener
Building with W=1 generates some 350 lines of warnings of the form:
kernel/bpf/core.c: In function '__bpf_prog_run':
kernel/bpf/core.c:476:33: warning: initialized field overwritten
[-Woverride-init]
[BPF_ALU | BPF_ADD | BPF_X] = &&ALU_ADD_X,
^~
kernel/bpf/core
Sean,
On 07/30/2016 03:16 AM, Sean Paul wrote:
Instead of just preparing the panel on bind, actually prepare/unprepare
during modeset/disable. The panel must be prepared in order to read hpd
status, so we need to refcount the prepares in order to ensure we don't
accidentally turn the panel off a
Suppress a bunch of warnings of the form:
fs/proc/task_mmu.c: In function 'show_smap_vma_flags':
fs/proc/task_mmu.c:635:22: warning: initialized field overwritten [-Wt
override-init]
[ilog2(VM_READ)] = "rd",
^~~~
fs/proc/task_mmu.c:635:22: note: (near initialization for '
From: zhuyj
Date: Mon, 1 Aug 2016 10:57:20 +0800
> Sorry.
> An inline function will be inserted into the calling function. Why
> "Assigning NULL to parmeter dcb has no effect outside of the
> inlined function." ?
It doesn't do anything to "dcb" in the calling function, that's not
how inlining wo
From: Chunhao Lin
Date: Fri, 29 Jul 2016 16:37:53 +0800
> v2:
> use "struct device *d = &tp->pci_dev->dev" instead of "struct pci_dev *pdev =
> tp->pci_dev"
>
> v1:
> This series of patches fix 3 runtime pm related issues that are listed below.
Series applied, thanks.
From: Valdis Kletnieks
Date: Sun, 31 Jul 2016 23:27:33 -0400
> Building with W=1 generates some 350 lines of warnings of the form:
>
> kernel/bpf/core.c: In function '__bpf_prog_run':
> kernel/bpf/core.c:476:33: warning: initialized field overwritten
> [-Woverride-init]
>[BPF_ALU | BPF_ADD
In commit d8152bf85d2c057fc39c3e20a4d623f524d9f09c:
("clocksource/drivers/mips-gic-timer: Convert init function to return error")
several return values were added to a void function resulting in:
clocksource/mips-gic-timer.c: In function 'gic_clocksource_of_init':
clocksource/mips-gic-timer.c
From: Sunil Kovvuri
Date: Mon, 1 Aug 2016 08:59:16 +0530
> Understood but unfortunately I don't see these patches in patchwork.
> http://patchwork.ozlabs.org/project/netdev/list/?submitter=&state=*&q=thunderx&archive=both&delegate=
> http://patchwork.ozlabs.org/project/netdev/list/?submitter=6215
Sean,
On 07/30/2016 03:16 AM, Sean Paul wrote:
Instead of just preparing the panel on bind, actually prepare/unprepare
during modeset/disable. The panel must be prepared in order to read hpd
status, so we need to refcount the prepares in order to ensure we don't
accidentally turn the panel off a
On Thu, 28 Jul 2016 16:07:16 -0700
Andrey Smirnov wrote:
> Factor out a small bit of common code in machine_restart(),
> machine_power_off() and machine_halt().
>
> Signed-off-by: Andrey Smirnov
> ---
>
> No changes compared to v1.
>
> arch/powerpc/kernel/setup-common.c | 23 ++--
Understood but unfortunately I don't see these patches in patchwork.
http://patchwork.ozlabs.org/project/netdev/list/?submitter=&state=*&q=thunderx&archive=both&delegate=
http://patchwork.ozlabs.org/project/netdev/list/?submitter=62159&state=*&q=&archive=both&delegate=
Thanks,
Sunil.
On Mon, Aug
When building with W=1, we get these warnings:
drivers/ata/libata-scsi.c: In function 'ata_mselect_caching':
drivers/ata/libata-scsi.c:3637:28: warning: suggest parentheses around
comparison in operand of '&' [-Wparentheses]
if (mpage[i + 2] & 0xfb != buf[i] & 0xfb) {
~
From: Heinrich Schuchardt
Date: Sun, 31 Jul 2016 11:30:58 +0200
> phy_data has to be set to zero to avoid undefined
> behavior.
In your opinion.
phy_data is only used in conditions where it has been initialized
in this function.
Therefore, please read the function carefully instead of just hav
From: Heinrich Schuchardt
Date: Sun, 31 Jul 2016 11:39:28 +0200
> i is defined as int but output as %u several times.
> Change the definition to unsigned.
>
> Signed-off-by: Heinrich Schuchardt
I hate changes like this.
The canonical way to loop over a value is to use a signed integer,
named
On Thu, 28 Jul 2016 16:07:17 -0700
Andrey Smirnov wrote:
> Call out to all restart handlers that were added via
> register_restart_handler() API when restarting the machine.
>
> Signed-off-by: Andrey Smirnov
> ---
>
> No changes compared to v1
>
> arch/powerpc/kernel/setup-common.c | 4
101 - 200 of 250 matches
Mail list logo