Some kernel components (ie ARM SMMU drivers) require to look-up
the platform device corresponding to a specific IORT node to
carry out streamid translation.
Platform devices created for ARM SMMU components out of IORT tables
have no fwnode token initialized, in that they do not have any device
tre
On DT based systems, the of_dma_configure() API implements DMA configuration
for a given device. On ACPI systems an API equivalent to of_dma_configure()
is missing which implies that it is currently not possible to set-up DMA
operations for devices through the ACPI generic kernel layer.
This patch
The ACPI IORT table provides data to ARM SMMU drivers to carry out
streamid mappings and the kernel has the infrastructure to implement
it through the iommu_xlate() IORT SMMU operation hook.
By reusing the infrastructure implemented for of_xlate(), this patch
adds the ARM SMMU v3 iommu_xlate() hoo
Device drivers (eg ARM SMMU) need to know if a specific component
is part of the IORT table, so that kernel data structures are not
initialized at initcalls time if the respective component is not
part of the IORT table.
To this end, this patch adds a trivial function that allows detecting
if a gi
When the kernel is configured with no IORT support the compilation
issues the following warnings:
In file included from drivers/irqchip/irq-gic-v3-its-pci-msi.c:19:0:
include/linux/iort.h:28:33: warning: 'struct pci_dev' declared inside
parameter list
u32 iort_pci_get_msi_rid(struct pci_dev *pdev
On systems booting with ACPI that enable the ARM SMMU components
in the kernel config options, the ARM SMMU v3 init function
(ie arm_smmu_init(), that registers the driver and sets-up bus
iommu operations) does not run only because the device tree interface
(of_find_matching_node()) fails to find t
Implement extended BPF JIT for ppc64. We retain the classic BPF JIT for
ppc32 and move ppc64 BE/LE to use the new JIT. Classic BPF filters will
be converted to extended BPF (see convert_filter()) and JIT'ed with the
new compiler.
Most of the existing macros are retained and fixed/enhanced where
ap
DT based systems have a generic kernel API to configure IOMMUs
for devices (ie of_iommu_configure()).
On ARM based ACPI systems, the of_iommu_configure() equivalent can
be implemented atop ACPI IORT kernel API, with the corresponding
functions to map device identifiers to IOMMUs and retrieve the
c
Current bus notifier in ARM64 (__iommu_attach_notifier)
attempts to attach dma_ops to a device on BUS_NOTIFY_ADD_DEVICE
action notification.
This causes issues on ACPI based systems, where PCI devices
can be added before the IOMMUs the devices are attached to
had a chance to be probed, causing fai
Current ARM SMMUv3 probe functions intermingle HW and DT probing in the
initialization functions to detect and programme the ARM SMMU v3 driver
features. In order to allow probing the ARM SMMUv3 with other firmwares
than DT, this patch splits the ARM SMMUv3 init functions into DT and HW
specific po
In ARM ACPI systems, IOMMU components are specified through static
IORT table entries. In order to create platform devices for the
corresponding ARM SMMU components, IORT kernel code should be made
able to parse IORT table entries and create platform devices
dynamically.
This patch adds the generi
In ACPI bases systems, in order to be able to create platform
devices and initialize them for arm-smmu-v3 components, the IORT
infrastructure requires ARM SMMU drivers to initialize a set of
operations that are used by the IORT kernel layer to configure platform
devices for ARM SMMU components in t
The patch
regulator: pfuze100-regulator: Adjust MODULE_DESCRIPTION()
has been applied to the regulator tree at
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 2
The patch
regulator: Kconfig: Mention that PFUZE3000 is also supported
has been applied to the regulator tree at
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next
The patch
regulator: pfuze100-regulator: Remove global variable
has been applied to the regulator tree at
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hou
On Tue, 07 Jun 2016, Peter Griffin wrote:
> On Tue, 07 Jun 2016, Lee Jones wrote:
> > On Tue, 07 Jun 2016, Peter Griffin wrote:
> > > On Fri, 22 Apr 2016, Lee Jones wrote:
> > >
> > > > Each PWM Capture device is allocated a structure to hold its own
> > > > state. During a capture the device may
Break out classic BPF JIT specifics into a separate header in
preparation for eBPF JIT implementation. Note that ppc32 will still need
the classic BPF JIT.
Cc: Matt Evans
Cc: Denis Kirjanov
Cc: Michael Ellerman
Cc: Paul Mackerras
Cc: Alexei Starovoitov
Cc: Daniel Borkmann
Cc: "David S. Mille
PPC64 eBPF JIT compiler.
Enable with:
echo 1 > /proc/sys/net/core/bpf_jit_enable
or
echo 2 > /proc/sys/net/core/bpf_jit_enable
... to see the generated JIT code. This can further be processed with
tools/net/bpf_jit_disasm.
With CONFIG_TEST_BPF=m and 'modprobe test_bpf':
test_bpf: Summary: 305 PA
Similar to the LI32() optimization, if the value can be represented
in 32-bits, use LI32(). Also handle loading a few specific forms of
immediate values in an optimum manner.
Cc: Matt Evans
Cc: Denis Kirjanov
Cc: Michael Ellerman
Cc: Paul Mackerras
Cc: Alexei Starovoitov
Cc: Daniel Borkmann
1. Per the ISA, ADDIS actually uses RT, rather than RS. Though
the result is the same, make the usage clear.
2. The multiply instruction used is a 32-bit multiply. Rename PPC_MUL()
to PPC_MULW() to make the same clear.
3. PPC_STW[U] take the entire 16-bit immediate value and do not require
word-ali
This RFC patch series is v2 of a previous posting:
https://lkml.org/lkml/2016/4/14/702
v1 -> v2:
- Rebased on top of dependencies series [1][2][3](v4.7-rc1)
- Removed IOMMU fwnode generalization
- Implemented ARM SMMU v3 ACPI probing instead of ARM SMMU v2
owing
Current IORT code only allow to map device identifiers to the
corresponding ITS group device id. This is not sufficient, in that
current code does not allow device id mappings to components
that sit between devices and ITS interrupt controllers (eg IOMMUs).
This patch enhances the current IORT ids
ACPI IORT table allows ids translations for PCI devices (through
their respective root complex) and name components (ie components
identified through their ACPI namespace path).
Current IORT code only allows look-up and retrieval of IORT nodes
corresponding to PCI root complexes components; this p
When performing a warm reboot from a system which does not correctly
support ELAN I2C touchpads, the touchpad will sometimes enter standard
mouse mode, cursor then never respond to touchpad event, and making the
driver discard the HID reports and flood dmesg with following error
messages.
"elan_i2c
The empty stub for its_acpi_probe() on !CONFIG_ACPI systems has
a wrong prototype, which causes compilation errors:
drivers/irqchip/irq-gic-v3-its.c: In function 'its_init':
drivers/irqchip/irq-gic-v3-its.c:1762:3: error: too few arguments to
function 'its_acpi_probe'
its_acpi_probe();
^
dri
The existing LI32() macro can sometimes result in a sign-extended 32-bit
load that does not clear the top 32-bits properly. As an example,
loading 0x7fff results in the register containing
0x7fff. While this does not impact classic BPF JIT
implementation (since that only uses the lo
On Tue, Jun 07, 2016 at 08:47:01PM +0800, Xing Zheng wrote:
> On 2016年06月07日 20:06, Mark Brown wrote:
> > OK, then the original name probably makes some sense though really
> > that's such an unusual design that just naming it after the specific
> > board might be better, it's not likely to see an
Hello,
On Tue, Jun 07, 2016 at 04:24:23PM +0900, Masami Hiramatsu wrote:
> On Thu, 2 Jun 2016 18:11:02 -0700
> Omar Sandoval wrote:
>
> > From: Omar Sandoval
> >
> > ftrace is very quick to give up on saving the task command line (see
> > `trace_save_cmdline()`). The workaround for events whi
On 06/05/2016 02:42 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.6.2 release.
There are 121 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be ma
On Tue, 07 Jun 2016, Peter Griffin wrote:
> mmc_select_bus_width() returns bus width (4 or 8) on success or
> zero if unsupported. If bus width is set successfully we then wish
> to switch to HS200 mode.
>
> This avoids the following error message in v4.70-rc2
>
> [2.523674] mmc0: mmc_select
On 06/05/2016 03:22 PM, Greg Kroah-Hartman wrote:
--
NOTE: This is the LAST 4.5.y stable kernel to be released, 4.5.y will be
end-of-life with this release. You should have moved to the 4.6.y
series already.
--
This is the start of the stable review cycle for the
On Sat, Jun 04, 2016 at 01:27:11PM -0400, David Kershner wrote:
> From: Tim Sell
>
> A kernel timer is now used as the vehicle to periodically call the
> channel_interrupt function of registered visor drivers, instead of a
> workqueue.
>
> This simplifies a lot of things by making periodic_work.
Hi,
[auto build test WARNING on next-20160607]
[cannot apply to v4.7-rc2 v4.7-rc1 v4.6-rc7 v4.7-rc2]
[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/Michal-Hocko/mm-oom_reaper-make-sure-that
Hi Tony, Tomi
as you have requested I have created the immutable branch containing the
mach-omap2 touching patches only from the omapdss header cleanup.
As I have mentioned in the v3 cover letter I have the other branch
containing the whole series:
https://www.mail-archive.com/linux-kernel@vger.k
From: Michal Hocko
Tetsuo is worried that mmput_async might still lead to a premature
new oom victim selection due to the following race:
__oom_reap_task exit_mm
find_lock_task_mm
atomic_inc(mm->mm_users) # = 2
task_unlock
t
Minfei Huang writes:
> There is no error number returned if loop driver fails in function
> alloc_disk to add new loop device. Add a correct error number to make
> user notify in this case.
>
> Signed-off-by: Minfei Huang
> ---
> drivers/block/loop.c | 1 +
> 1 file changed, 1 insertion(+)
>
>
On Tue, Jun 07, 2016 at 05:02:32PM +0900, Masami Hiramatsu wrote:
> On Thu, 2 Jun 2016 18:11:03 -0700
> Omar Sandoval wrote:
>
> > From: Omar Sandoval
> >
> > You'd only ever want $comm as a string, but the default is still u64.
> > Push the type parsing later so we can decide based on the act
On Tue 07-06-16 20:30:24, kbuild test robot wrote:
[...]
>mm/oom_kill.c: In function '__oom_reap_task':
> >> mm/oom_kill.c:490:7: warning: passing argument 1 of 'mmget_not_zero' from
> >> incompatible pointer type
> if (!mmget_not_zero(&mm->mm_users)) {
> ^
Sigh... My rate of s
Hi,
[auto build test ERROR on next-20160607]
[cannot apply to v4.7-rc2 v4.7-rc1 v4.6-rc7 v4.7-rc2]
[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/Michal-Hocko/mm-oom_reaper-make-sure-that
On Mon, Jun 6, 2016 at 7:33 PM, Chris Zhong wrote:
> Hi Rob
>
>
> On 06/06/2016 10:27 PM, Rob Herring wrote:
>>
>> On Fri, Jun 03, 2016 at 11:15:08PM +0800, Chris Zhong wrote:
>>>
>>> This patch adds a binding that describes the Rockchip USB Type-C PHY
>>> for rk3399
>>>
>>> Signed-off-by: Chris Z
On Fri, Jun 03, 2016 at 05:58:41PM -0500, Josh Poimboeuf wrote:
> The nr_migrations field is updated independently of CONFIG_SCHEDSTATS,
> so it can be displayed regardless.
>
> Signed-off-by: Josh Poimboeuf
Acked-by: Mel Gorman
--
Mel Gorman
SUSE Labs
On 07/06/16 14:22, Mark Rutland wrote:
On Mon, Jun 06, 2016 at 04:53:58PM +0100, Sudeep Holla wrote:
The System Control Processor (SCP) provides peripheral devices with
power domains that can be enabled and disabled viathe System Control
and Power Interface (SCPI) Message Protocol. Add binding
On Fri, Jun 03, 2016 at 05:58:40PM -0500, Josh Poimboeuf wrote:
> Commit cb2517653fcc ("sched/debug: Make schedstats a runtime tunable
> that is disabled by default") introduced a bug when CONFIG_SCHEDSTATS is
> enabled and the runtime tunable is disabled (which is the default). The
> wait-time, s
Hi all,
sorry I forgot to mentioning that I have not yet add the Makefile.reST
to the root Makefile. To test, please give the srctree environment in the
command line. E.g:
cd /share/linux/Documentation
srctree=/share/linux make -f Makefile.reST books/kernel-doc-HOWTO.html
-- Markus --
Am
Hi Mark,
On 2016年06月07日 21:32, Mark Brown wrote:
On Tue, Jun 07, 2016 at 08:47:01PM +0800, Xing Zheng wrote:
On 2016年06月07日 20:06, Mark Brown wrote:
OK, then the original name probably makes some sense though really
that's such an unusual design that just naming it after the specific
board mig
On 06/05/2016, 11:40 PM, Greg Kroah-Hartman wrote:
> 3.14-stable review patch. If anyone has any objections, please let me know.
>
> --
>
> From: Ben Hutchings
>
> commit feae3ca2e5e1a8f44aa6290255d3d9709985d0b2 upstream.
This is not a SHA of an upstream commit ;).
> Quoting
On Tue, Jun 07, 2016 at 01:47:13PM +, Sell, Timothy C wrote:
> > -Original Message-
> > From: Neil Horman [mailto:nhor...@redhat.com]
> > Sent: Tuesday, June 07, 2016 9:40 AM
> > To: Kershner, David A
> > Cc: cor...@lwn.net; t...@linutronix.de; mi...@redhat.com;
> > h...@zytor.com; gre.
When using efifb with a 16-bit (5:6:5) visual, fbcon's text is rendered
in the wrong colors - e.g. text gray (#aa) is rendered as green
(#50bc50) and neighboring pixels have slightly different values
(such as #50bc78).
The reason is that fbcon loads its 16 color palette through
efifb_setcolreg
The AXI CDMA is a soft ip, which can be programmed to support
32 bit addressing or greater than 32 bit addressing.
When the AXI CDMA ip is configured for 32 bit address space
in simple dma mode the source/destination buffer address is
specified by a single register(18h for Source buffer address an
The AXI DMA is a soft ip, which can be programmed to support
32 bit addressing or greater than 32 bit addressing.
When the AXI DMA ip is configured for 32 bit address space
in simple dma mode the buffer address is specified by a single register
(18h for MM2S channel and 48h for S2MM channel). When
Hi Steve,
Could you please take a look at this?
Thanks,
Namhyung
On Mon, May 23, 2016 at 12:26 AM, Namhyung Kim wrote:
> Currently ftrace_graph_ent{,_entry} and ftrace_graph_ret{,_entry} struct
> can have padding bytes at the end due to alignment in 64-bit data type.
> As these data are record
On Mon, Jun 06, 2016 at 08:37:26PM -0700, Ed Swierk wrote:
> Mysterious TPM behavior can be difficult to track down through all the
> layers of software. Add error messages for conditions that should
> never happen. Also include the manufacturer ID along with other chip
> data printed during init.
Hi Lee,
On Tue, 07 Jun 2016, Lee Jones wrote:
> On Tue, 07 Jun 2016, Peter Griffin wrote:
>
> > mmc_select_bus_width() returns bus width (4 or 8) on success or
> > zero if unsupported. If bus width is set successfully we then wish
> > to switch to HS200 mode.
> >
> > This avoids the following e
On Mon, Jun 06, 2016 at 09:11:18PM -0400, Rik van Riel wrote:
> On Mon, 2016-06-06 at 18:15 -0400, Johannes Weiner wrote:
> > On Mon, Jun 06, 2016 at 05:56:09PM -0400, Rik van Riel wrote:
> > >
> > > On Mon, 2016-06-06 at 15:48 -0400, Johannes Weiner wrote:
> > > >
> > > >
> > > > +void lru_cac
On Tue, Jun 07, 2016 at 04:08:04PM +0800, Zhen Lei wrote:
> v3 -> v4:
> 1. Packed three patches of Kefeng Wang, patch6-8.
> 2. Add 6 new patches(9-15) to enhance the numa on arm64.
>
> v2 -> v3:
> 1. Adjust patch2 and patch5 according to Matthias Brugger's advice, to make
> the
>patches looks
Mario Limonciello [mailto:mario_limoncie...@dell.com]
[...]
> + ret = hex2bin(buf, obj->string.pointer + 9, 6);
> + if (ret < 0 || !is_valid_ether_addr(buf)) {
> + netif_warn(tp, probe, tp->netdev, "Invalid MAC\n");
> + goto amacout;
>
On Tue, Jun 07, 2016 at 02:19:14PM +0200, PaX Team wrote:
> (i believe that) latent entropy is found in more than just interrupt timing,
> there're
> also data dependent computations that can have entropy, either on a single
> system or
> across a population of them.
It's not clear how much data
On Tue, Jun 7, 2016 at 6:27 PM, Leizhen (ThunderTown)
wrote:
>
>
> On 2016/6/7 16:31, Ganapatrao Kulkarni wrote:
>> On Tue, Jun 7, 2016 at 1:38 PM, Zhen Lei wrote:
>>> Some numa nodes may have no memory. For example:
>>> 1. cpu0 on node0
>>> 2. cpu1 on node1
>>> 3. device0 access the momory from
There is no reason in rx_descs property because davinici_cpdma
driver splits pool of descriptors equally between tx and rx channels.
So, this patch series makes driver to use available number of
descriptors for rx channels.
Based on master branch
Since v1:
- separate device tree and driver patche
There is no reason in rx_descs property because davinici_cpdma
driver splits pool of descriptors equally between tx and rx channels.
That is, if number of descriptors 256, 128 of them are for rx
channels. While receiving, the descriptor is freed to the pool and
then allocated with new skb. And if i
On Sun, May 29, 2016 at 6:17 PM, Kuthonuzo Luruo
wrote:
> This patch adds new tests for KASAN double-free error detection when the
> same slab object is concurrently deallocated.
>
> Signed-off-by: Kuthonuzo Luruo
> ---
>
> Changes in v4:
> - There are *no* changes for v4.
>
> Changes in v3:
> -
Hi Wolfram,
On Jun 05 2016 or thereabouts, Wolfram Sang wrote:
> Hi Benjamin,
>
> > this is mostly a resubmission of the v6 with the acks, tested-by and few
> > typos
> > here and there.
>
> I actually reviewed v6 but got an NMI so writing the mails fell through
> the cracks :( Sorry about that
There is no reason to hold s/w dependent parameter in device tree.
Even more, there is no reason in this parameter because davinici_cpdma
driver splits pool of descriptors equally between tx and rx channels
anyway.
Signed-off-by: Ivan Khoronzhuk
---
Documentation/devicetree/bindings/net/cpsw.txt
On Mon, Jun 06, 2016 at 08:37:27PM -0700, Ed Swierk wrote:
> Some TPMs violate their own advertised command durations. This is much
> easier to debug with data about how long each command actually takes
> to complete. Add debug messages that can be enabled by running
>
> echo -n 'module tpm +p'
> -Original Message-
> From: Neil Horman [mailto:nhor...@redhat.com]
> Sent: Tuesday, June 07, 2016 9:40 AM
> To: Kershner, David A
> Cc: cor...@lwn.net; t...@linutronix.de; mi...@redhat.com;
> h...@zytor.com; gre...@linuxfoundation.org; Arfvidson, Erik; Sell, Timothy
> C; hof...@osadl.org;
On 07/06/16 16:04, Felipe Balbi wrote:
>
> Hi,
>
> Roger Quadros writes:
>>> But you said I must run an unnecessary OTG state machine, even thought it
>>> has nothing to do with my system, only because the two sides of my port
>>> mux device is a host and peripheral controller.
>>
>> We have a m
From: "Su, Xuemin"
There is a corner case in which udp packets belonging to a same
flow are hashed to different socket when hslot->count changes from 10
to 11:
1) When hslot->count <= 10, __udp_lib_lookup() searches udp_table->hash,
and always passes 'daddr' to udp_ehashfn().
2) When hslot->cou
Em Tue, Jun 07, 2016 at 06:26:13PM +0900, Taeung Song escreveu:
> The config set is prepared by collecting
> all configs from config files (i.e. user config
> ~/.perfconfig and system config $(sysconfdir)/perfconfig)
> so the config set contains all config key-value pairs.
>
> We need to use it as
On 07/06/16 16:09, Felipe Balbi wrote:
>
> Hi,
>
> (guys, please make sure to break lines at 80-columns)
>
> Roger Quadros writes:
>> @@ -2853,6 +2852,23 @@ static irqreturn_t dwc3_interrupt(int irq, void
>> *_evt)
>>int dwc3_gadget_init(struct dwc3 *dwc)
>>{
>>
On 06/07/2016 02:30 AM, Jan Beulich wrote:
> Reads following writes with all address bits set to 1 should return all
> changeable address bits as one, not the BAR size (nor, as was the case
> for the upper half of 64-bit BARs, the high half of the region's end
> address). Presumably this didn't cau
On 06/05/2016 11:58 PM, Ji-Ze Hong (Peter Hong) wrote:
Adds watchdog enable support for Fintek F81866 Super-IO chip to
Fintek wdt driver (f71808e_wdt)
Tested and verified on iBASE MI802 Industrial PC
Datasheet references:
http://www.alldatasheet.com/datasheet-pdf/pdf/459085/FINTEK/F81866AD-I.ht
On Tue, Jun 07, 2016 at 11:26:29AM +0200, Michal Hocko wrote:
> On Mon 06-06-16 18:15:50, Johannes Weiner wrote:
> [...]
> > The last hunk in the patch (obscured by showing the label instead of
> > the function name as context)
>
> JFYI my ~/.gitconfig has the following to workaround this:
> [diff
From: Gustavo Padovan
We don't have any user of this function anymore, let's remove it.
Signed-off-by: Gustavo Padovan
---
drivers/gpu/drm/drm_irq.c | 31 ++-
include/drm/drmP.h| 2 --
2 files changed, 6 insertions(+), 27 deletions(-)
diff --git a/drivers/
From: Gustavo Padovan
We don't need to use &radeon_crtc->base there as crtc is available
in the function.
Signed-off-by: Gustavo Padovan
---
drivers/gpu/drm/radeon/radeon_display.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/radeon/radeon_display.c
b/dr
From: Gustavo Padovan
Replace the legacy drm_vblank_{on,off}() with the new helper functions.
Signed-off-by: Gustavo Padovan
---
drivers/gpu/drm/amd/amdgpu/dce_v10_0.c | 4 ++--
drivers/gpu/drm/amd/amdgpu/dce_v11_0.c | 4 ++--
drivers/gpu/drm/amd/amdgpu/dce_v8_0.c | 4 ++--
3 files changed, 6
From: Gustavo Padovan
We don't need to use &amdgpu_crtc->base there as crtc is available
in the function.
Signed-off-by: Gustavo Padovan
---
drivers/gpu/drm/amd/amdgpu/amdgpu_display.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_display
Add support for JMP_CALL_X (tail call) introduced by commit 04fd61ab36ec
("bpf: allow bpf programs to tail-call other bpf programs").
bpf_tail_call() arguments:
ctx - context pointer passed to next program
array - pointer to map which type is BPF_MAP_TYPE_PROG_ARRAY
index - index inside ar
From: Gustavo Padovan
Replace the legacy drm_send_vblank_event(), drm_arm_vblank_event() and
drm_vblank_{get,put}() with the new helper functions.
v2: add crtc to nouveau_page_flip_state (comment from Mario Kleiner)
Signed-off-by: Gustavo Padovan
Signed-off-by: Gustavo Padovan
---
drivers/g
From: Gustavo Padovan
Replace the legacy drm_vblank_{on,off}() with the new helper functions.
Signed-off-by: Gustavo Padovan
---
drivers/gpu/drm/radeon/atombios_crtc.c | 4 ++--
drivers/gpu/drm/radeon/radeon_legacy_crtc.c | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
diff --
On 06/07/2016 02:31 AM, Jan Beulich wrote:
> - drop unused function parameter of read_dev_bar()
> - drop rom_init() (now identical to bar_init())
> - fold read_dev_bar() into its now single caller
> - simplify determination of 64-bit memory resource
> - use const and unsigned
>
> Signed-off-by: Jan
On Mon, Jun 06, 2016 at 10:20:31PM -0400, Rik van Riel wrote:
> On Mon, 2016-06-06 at 15:48 -0400, Johannes Weiner wrote:
> > When the splitlru patches divided page cache and swap-backed pages
> > into separate LRU lists, the pressure balance between the lists was
> > biased to account for the fact
Em Ter, 2016-06-07 às 20:29 +0900, Masahiro Yamada escreveu:
> 2016-06-07 19:48 GMT+09:00 Michal Marek :
> >
> > On 2016-06-07 12:03, Masahiro Yamada wrote:
> > >
> > > 2016-06-07 18:58 GMT+09:00 Michal Marek :
> > > >
> > > > On 2016-06-07 11:38, Michal Marek wrote:
> > > > >
> > > > > On 2016
Change the dc_timer function to be static as it is not used outside
this driver. This fixes the following warning:
drivers/clocksource/timer-digicolor.c:66:24: warning: symbol 'dc_timer' was not
declared. Should it be static?
Signed-off-by: Ben Dooks
---
Cc: Daniel Lezcano
Cc: Thomas Gleixner
> OK. I'll try to fetch those pending patches on patchwork and see how the
> merge would behave.
Thanks. If you have time for a bit of a reviewing eye on them, this
would also be much appreciated :)
signature.asc
Description: PGP signature
From: Gustavo Padovan
Replace the legacy drm_vblank_{on,off}() with the new helper functions.
Signed-off-by: Gustavo Padovan
---
drivers/gpu/drm/gma500/gma_display.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/gma500/gma_display.c
b/drivers/gpu/drm/gma5
From: Gustavo Padovan
As they are not used anywhere outside drm_irq.c make them static.
Signed-off-by: Gustavo Padovan
---
drivers/gpu/drm/drm_irq.c | 7 ++-
include/drm/drmP.h| 2 --
2 files changed, 2 insertions(+), 7 deletions(-)
diff --git a/drivers/gpu/drm/drm_irq.c b/drivers
From: Gustavo Padovan
We don't have any user of this function anymore, let's remove it.
Signed-off-by: Gustavo Padovan
---
drivers/gpu/drm/drm_irq.c | 39 ---
include/drm/drmP.h| 2 --
2 files changed, 8 insertions(+), 33 deletions(-)
diff --git a/
Hi Guenter,
Am Dienstag, 7. Juni 2016, 06:19:45 schrieb Guenter Roeck:
> On Tue, Jun 7, 2016 at 2:54 AM, Heiko Stübner wrote:
> > Hi Frank,
> >
> > Am Montag, 6. Juni 2016, 17:20:04 schrieb Frank Wang:
> >> The newer SoCs (rk3366, rk3399) take a different usb-phy IP block
> >> than rk3288 and be
>>> On 07.06.16 at 16:06, wrote:
> On 06/07/2016 02:30 AM, Jan Beulich wrote:
>> Reads following writes with all address bits set to 1 should return all
>> changeable address bits as one, not the BAR size (nor, as was the case
>> for the upper half of 64-bit BARs, the high half of the region's end
On Mon, Jun 06, 2016 at 10:34:43PM -0400, Rik van Riel wrote:
> On Mon, 2016-06-06 at 15:48 -0400, Johannes Weiner wrote:
> > Currently, scan pressure between the anon and file LRU lists is
> > balanced based on a mixture of reclaim efficiency and a somewhat
> > vague
> > notion of "value" of havin
On Tue, Jun 07, 2016 at 08:45:40AM +0530, Bhaktipriya Shridhar wrote:
> alloc_workqueue replaces deprecated create_workqueue().
>
> A dedicated workqueue has been used since the workqueue
> acpi_thermal_pm_queue with workitem &tz->thermal_check_work
> (maps to acpi_thermal_check_fn), is involved i
From: Gustavo Padovan
As they are not used anywhere outside drm_irq.c make them static.
Signed-off-by: Gustavo Padovan
---
drivers/gpu/drm/drm_irq.c | 10 ++
include/drm/drmP.h| 2 --
2 files changed, 2 insertions(+), 10 deletions(-)
diff --git a/drivers/gpu/drm/drm_irq.c b/d
On Tue, Jun 07, 2016 at 08:17:05PM +0800, Baolin Wang wrote:
> Now some cipher hardware engines prefer to handle bulk block rather than one
> sector (512 bytes) created by dm-crypt, cause these cipher engines can handle
> the intermediate values (IV) by themselves in one bulk block. This means we
>
On 06/07/2016 04:39 AM, Catalin Marinas wrote:
On Mon, Jun 06, 2016 at 12:09:49PM -0500, Shaun Tancheff wrote:
I'm pretty sure it is missing a bio_put() after submit_bio_wait().
Please excuse the hack-y patch but I think you need to do something
like this ...
(Note tabs eaten by gmail).
diff -
On Tue, Jun 07, 2016 at 09:25:50AM +0900, Minchan Kim wrote:
> Hi Johannes,
>
> Thanks for the nice work. I didn't read all patchset yet but the design
> makes sense to me so it would be better for zram-based on workload
> compared to as is.
Thanks!
> On Mon, Jun 06, 2016 at 03:48:27PM -0400, Jo
The driver does not export armada_370_xp_timer_syscore_ops so
make it static to fix the following warning:
drivers/clocksource/time-armada-370-xp.c:249:20: warning: symbol
'armada_370_xp_timer_syscore_ops' was not declared. Should it be static?
Signed-off-by: Ben Dooks
---
Cc: Daniel Lezcano
C
Em Mon, 30 May 2016 20:29:14 +0800
Tiffany Lin escreveu:
> ==
> Introduction
> ==
>
> The purpose of this series is to add the driver for video codec hw embedded
> in the Mediatek's MT8173 SoCs.
> Mediatek Video Codec is able to handle video decoding of in a range of
>
On Wed, Jun 01, 2016 at 09:59:20PM +0200, Peter Zijlstra wrote:
> On Mon, May 23, 2016 at 11:58:46AM +0100, Morten Rasmussen wrote:
> > In the current find_idlest_group()/find_idlest_cpu() search we end up
> > calling find_idlest_cpu() in a sched_group containing only one cpu in
> > the end. Checki
Hi Ben,
On mar., juin 07 2016, Ben Dooks wrote:
> The driver does not export armada_370_xp_timer_syscore_ops so
> make it static to fix the following warning:
>
> drivers/clocksource/time-armada-370-xp.c:249:20: warning: symbol
> 'armada_370_xp_timer_syscore_ops' was not declared. Should it b
Michal Hocko wrote:
> > To be honest, I don't think we need to apply this pile.
>
> So you do not think that the current pile is making the code easier to
> understand and more robust as well as the semantic more consistent?
Right. It is getting too complicated for me to understand.
Below patch
401 - 500 of 1210 matches
Mail list logo
