* Arnaldo Carvalho de Melo wrote:
> Em Fri, Feb 03, 2017 at 03:56:42PM +0530, Ravi Bangoria escreveu:
> > After patch:
> > $ perf record -a -e sdt_glib:idle__add
> > event syntax error: 'sdt_glib:idle__add'
> > \___ unknown tracepoint
> >
> > Error: File /sys/
* Ard Biesheuvel wrote:
> From: David Howells
>
> Add the definitions for shim and image security database, both of which
> are used widely in various Linux distros.
>
> Signed-off-by: Josh Boyer
> Signed-off-by: David Howells
> Cc: Matt Fleming
> Signed-off-by: Ard Biesheuvel
That's not
On 2017/02/07 10:05AM, Masami Hiramatsu wrote:
> On Sat, 4 Feb 2017 01:09:49 +0530
> "Naveen N. Rao" wrote:
>
> > Hi Michael,
> > Thanks for the review! I'll defer to Anju on most of the aspects, but...
> >
> > On 2017/02/01 09:53PM, Michael Ellerman wrote:
> > > Anju T Sudhakar writes:
> > >
If last avail idx is not equal to cached avail idx, we're sure there's
still available buffers in the virtqueue so there's no need to re-read
avail idx. So let's skip this to avoid unnecessary userspace memory
access and memory barrier. Pktgen test show about 3% improvement on rx
pps.
Signed-off-b
* Masami Hiramatsu wrote:
> Since tracing/*probe_events will accept a probe definition
> up to 4096 - 2 ('\n' and '\0') bytes, it must show 4094 instead
> of 4096 in warning message.
>
> Signed-off-by: Masami Hiramatsu
> ---
> kernel/trace/trace_probe.c |3 ++-
> 1 file changed, 2 inserti
Fix build errors after removing DEBUG definition.
Signed-off-by: Minghsiu Tsai
---
drivers/media/platform/mtk-vcodec/mtk_vcodec_dec.c | 9 -
drivers/media/platform/mtk-vcodec/vdec_vpu_if.c| 5 ++---
drivers/media/platform/mtk-vcodec/venc_vpu_if.c| 4 +---
3 files changed, 7 inser
On Mon 2017-02-06 10:47:45, Laura Abbott wrote:
> On 02/03/2017 01:08 PM, Kees Cook wrote:
> > On Fri, Feb 3, 2017 at 12:29 PM, Russell King - ARM Linux
> > wrote:
> >> On Fri, Feb 03, 2017 at 11:45:56AM -0800, Kees Cook wrote:
> >>> On Fri, Feb 3, 2017 at 9:52 AM, Laura Abbott wrote:
> diff
These two debug messages are missing the trailing newline.
Signed-off-by: He Kuang
---
tools/perf/util/bpf-loader.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/tools/perf/util/bpf-loader.c b/tools/perf/util/bpf-loader.c
index 36c8611..bc6bc70 100644
--- a/tools/perf/u
Since HAVE_KPROBES can be enabled in arm64, this patch introduces
regs_query_register_offset() to convert register name to offset for
arm64, so the BPF prologue feature is ready to use.
Signed-off-by: He Kuang
---
tools/perf/arch/arm64/Makefile | 1 +
tools/perf/arch/arm64/util/dwarf-r
* Ingo Molnar wrote:
>
> * Christoph Hellwig wrote:
>
> > On Mon, Feb 06, 2017 at 02:28:21PM +0100, Ingo Molnar wrote:
> > > Move the following task->mm helper APIs into a new header file,
> > > , to further reduce the size and complexity
> > > of :
> >
> > Is there any good reason why they
Hi Jaegeuk,
On 2017/1/29 11:58, Jaegeuk Kim wrote:
> Hi Chao,
>
> On 01/24, Chao Yu wrote:
>
> ...
>
>>
>> -error = read_all_xattrs(inode, ipage, &base_addr);
>> +error = lookup_all_xattrs(inode, ipage, index, len, name,
>> +&entry, &base_addr);
>> if
* Borislav Petkov wrote:
> On Mon, Feb 06, 2017 at 02:18:32PM +0100, Robert Richter wrote:
>
> > Isn't there the danger the previous watchdog state is never restored if for
> > some reason perf got killed? So maybe have some other task running that
> > restores it once perf is gone.
>
> Curre
Hi Jaegeuk,
Happy Chinese New Year! :)
On 2017/1/24 12:35, Jaegeuk Kim wrote:
> Hi Chao,
>
> On 01/22, Chao Yu wrote:
>> In scenario of intensively node allocation, free nids will be ran out
>> soon, then it needs to stop to load free nids by traversing NAT blocks,
>> in worse case, if NAT block
On 2017年02月06日 01:15, Christoph Hellwig wrote:
We don't really need struct virtio_pci_vq_info, as most field in there
are redundant:
- the vq backpointer is not strictly neede to start with
- the entry in the vqs list is not needed - the generic virtqueue already
has list, we only need
On Tue 07-02-17 09:51:50, Dave Chinner wrote:
> On Mon, Feb 06, 2017 at 07:47:43PM +0100, Michal Hocko wrote:
> > On Mon 06-02-17 10:32:37, Darrick J. Wong wrote:
[...]
> > > I prefer to keep the "...yet we are likely to be under GFP_NOFS..."
> > > wording of the old comment because it captures the
On 2017年02月06日 01:15, Christoph Hellwig wrote:
This lets IRQ layer handle dispatching IRQs to separate handlers for the
case where we don't have per-VQ MSI-X vectors, and allows us to greatly
simplify the code based on the assumption that we always have interrupt
vector 0 (legacy INTx or config
On Mon, Feb 06, 2017 at 03:18:42PM +0100, Miklos Szeredi wrote:
> But I think it's breakable in the same way: if the deadlocked request
> is aborted, the fault will release the page lock as well as mmap_sem,
> and from there things will resolve themselves.
Right you are - original holder of ->mma
* Laura Abbott wrote:
>
> There are multiple architectures that support CONFIG_DEBUG_RODATA and
> CONFIG_SET_MODULE_RONX. These options also now have the ability to be
> turned off at runtime. Move these to an architecture independent
> location and make these options def_bool y for almost all
On Mon, Feb 06, 2017 at 11:28:20AM +0800, Baoyou Xie wrote:
> + Shawn
>
> On 6 February 2017 at 11:26, Baoyou Xie wrote:
>
> > This patch adds i2c controller driver for ZTE's zx2967 family.
> >
> > Signed-off-by: Baoyou Xie
Reviewed-by: Shawn Guo
On Mon, Feb 06, 2017 at 04:55:55PM -0600, Rob Herring wrote:
> On Mon, Feb 6, 2017 at 5:08 AM, Thierry Reding
> wrote:
> > On Mon, Feb 06, 2017 at 11:07:42AM +0100, Daniel Vetter wrote:
> >> On Mon, Feb 6, 2017 at 10:35 AM, Thierry Reding
> >> wrote:
> >>
> >> > > > > +EXPORT_SYMBOL(tinydrm_disa
On Tue, Feb 07, 2017 at 08:28:16AM +1000, Dave Airlie wrote:
> >
> > I definitely don't want that we don't attempt this. But brought from years
> > of experience, I recommend to merge first (with pre-refactoring already
> > applied, but helpers only extracted, not yet at the right spot), and then
>
Hi James,
On Mon, Feb 06, 2017 at 10:38:48PM -0800, James Bottomley wrote:
> On Mon, 2017-02-06 at 23:26 +0100, Willy Tarreau wrote:
(...)
> > We don't have the referenced commit above in 3.10 so we should be
> > safe. Additionally I checked that neither 4.4 nor 3.12 have them
> > either, so tha
On Mon, Feb 06, 2017 at 08:23:36PM +0100, Noralf Trønnes wrote:
>
> Den 06.02.2017 10.17, skrev Thierry Reding:
> > On Tue, Jan 31, 2017 at 05:03:13PM +0100, Noralf Trønnes wrote:
> > > tinydrm provides helpers for very simple displays that can use
> > > CMA backed framebuffers and need flushing o
Hi Andrew,
On Mon, Feb 06, 2017 at 12:16:44AM +0900, Minchan Kim wrote:
> From: zhouxianrong
>
> the idea is that without doing more calculations we extend zero pages
> to same element pages for zram. zero page is special case of
> same element page with zero element.
>
> 1. the test is done un
Hi Mark,
Thanks for reviving this series and sorry for not taking care of it
myself. Please see some comments inline.
On Tue, Feb 7, 2017 at 3:09 PM, Mark Yao wrote:
> From: Tomasz Figa
>
> The API is not suitable for subsystems consisting of multiple devices
> and requires severe hacks to use
On Mon, Feb 06, 2017 at 08:56:25PM -0800, Guenter Roeck wrote:
> On 02/06/2017 02:48 PM, Willy Tarreau wrote:
> > On Mon, Feb 06, 2017 at 06:46:39AM -0800, Guenter Roeck wrote:
> > > > An updated patch was pushed here :
> > > >
> > > >
> > > > https://kernel.org/pub/linux/kernel/v3.x/stable-rev
On Mon, 2017-02-06 at 23:26 +0100, Willy Tarreau wrote:
> Hi Sathya,
>
> On Mon, Feb 06, 2017 at 09:21:44AM -0700, Sathya Prakash Veerichetty
> wrote:
> > Willy,
> > I think this patch had a problem and later modified to a different
> > blocking mechanism. Could you please pull in the latest chan
On Fri, 2017-01-27 at 14:07 -0600, Rob Herring wrote:
> On Fri, Jan 20, 2017 at 04:18:41PM +0800, Chunfeng Yun wrote:
> > add a new compatible string for "mt2712", and move reference clock
> > into each port node;
> >
> > Signed-off-by: Chunfeng Yun
> > ---
> > .../devicetree/bindings/phy/phy-mt
booting the guest.
>
> With next-20170203 (mentioned in my mail last Friday), I got the same
> calltrace as Hannes.
>
> With today's linux-next (next-20170206), actually the calltrace changed to
> the below.
> [ 122.023036] ? remove_wait_queue+0x70/0x70
> [ 122.
On Tue, 07 Feb 2017 05:33:05 +0100,
Takashi Sakamoto wrote:
>
> On Feb 3 2017 16:24, Takashi Iwai wrote:
> > On Thu, 02 Feb 2017 04:45:48 +0100,
> > Takashi Sakamoto wrote:
> >>
> >> I'm _strongly_ interested in your two patches, because it has a
> >> potentiality to purge ASoC abuse of TLV featur
On Mon, Feb 06, 2017 at 10:52:12PM +0100, Rafael J. Wysocki wrote:
> On Monday, February 06, 2017 10:20:41 PM Lukas Wunner wrote:
> > On Mon, Feb 06, 2017 at 11:54:05AM -0600, Bjorn Helgaas wrote:
> > > On Mon, Feb 06, 2017 at 06:54:37AM +0100, Lukas Wunner wrote:
> > > > Since commit 68db9bc81436
On Mon, Feb 06, 2017 at 04:15:02PM -0600, Bjorn Helgaas wrote:
> On Mon, Feb 06, 2017 at 10:20:41PM +0100, Lukas Wunner wrote:
> > On Mon, Feb 06, 2017 at 11:54:05AM -0600, Bjorn Helgaas wrote:
> > > What is the hotplug event that causes generation of this wakeup event?
> >
> > If you had read all
Due to the reference clock comes from 26M oscillator directly
on mt8173, and it is a fixed-clock in DTS which always turned
on, we ignore it before. But on some platforms, it comes
from PLL, and need be controlled, so here add it, no matter
it is a fixed-clock or not.
Signed-off-by: Chunfeng Yun
Make the reference clock optional for DTS backward compatibility
and ignore the error if it does not exist.
Signed-off-by: Chunfeng Yun
---
drivers/usb/host/xhci-mtk.c | 11 +--
1 file changed, 9 insertions(+), 2 deletions(-)
diff --git a/drivers/usb/host/xhci-mtk.c b/drivers/usb/host
Make the reference clock optional for DTS backward compatibility
and ignore the error if it does not exist.
Signed-off-by: Chunfeng Yun
---
drivers/usb/mtu3/mtu3_plat.c | 11 +--
1 file changed, 9 insertions(+), 2 deletions(-)
diff --git a/drivers/usb/mtu3/mtu3_plat.c b/drivers/usb/mt
drm_mm_insert_node_generic and drm_mm_remove_node may access same
resource with list ops, it's not threads safe, so protect this context
with mutex lock.
Fix bug:
[49451.856244]
==
[49451.856350] BUG: KASAN: wild-memory-access on add
From: Tomasz Figa
The API is not suitable for subsystems consisting of multiple devices
and requires severe hacks to use it. To mitigate this, this patch
implements allocation and address space management locally by using
helpers provided by DRM framework, like other DRM drivers do, e.g.
Tegra.
From: Shunqian Zheng
Rockchip DRM used the arm special API, arm_iommu_*(), to attach
iommu for ARM32 SoCs. This patch convert to common iommu API
so it would support ARM64 like RK3399.
Since previous patch added support for direct IOMMU address space
management, there is no need to use DMA API a
Some iommu patches on the series[0] "iommu/rockchip: Fix bugs and
enable on ARM64" already landed, So drm/rockchip related patches [1] and [2]
ready to landed, this series just rebase them to lastest drm-next.
And fix some bugs for drm/rockchip drm_mm
[0]: http://www.spinics.net/lists/arm-kernel/
The return value of iommu_map_sg is size_t, it's unsigned,
So check ret < 0 is wrong.
And if iommu_map_sg is error, it's return value is zero, but
rockchip_gem_iommu_map feel the zero return value is success,
bug happen:
[5.227458] [drm:rockchip_gem_iommu_map] *ERROR* failed to map buffer: 0
Please ignore this series of patches, due to the first version have been
merged into usb-next branch except DTS's one[PACH 4/6].
This will cause mtu3 probe failure, so I will send new patches based on
usb-next branch.
sorry
On Mon, 2017-02-06 at 17:29 +0800, Chunfeng Yun wrote:
> Due to the refer
On Mon, Feb 6, 2017 at 10:24 PM, Vinod Koul wrote:
> On Mon, Feb 06, 2017 at 05:31:15PM +0530, Anup Patel wrote:
>
>> >> +
>> >> +/* SBA C_MDATA helper macros */
>> >> +#define SBA_C_MDATA_LOAD_VAL(__bnum0)((__bnum0) & 0x3)
>> >> +#define SBA_C_MDATA_WRITE_VAL(__bnum0)
Hi all,
Changes since 20170206:
The tty tree lost its build failure.
The akpm tree gained a conflict against the net-next tree.
Non-merge commits (relative to Linus' tree): 7711
8737 files changed, 327880 insertions(+), 163014 dele
There are many SDT markers in powerpc whose uprobe definition goes
beyond current MAX_CMDLEN, especially when target filename is long
and sdt marker has long list of arguments. For example, definition
of sdt marker
method__compile__end: 8@17 8@9 8@10 -4@8 8@7 -4@6 8@5 -4@4 1@37(28)
from file
On Mon, Feb 6, 2017 at 8:09 PM, Jens Axboe wrote:
> On 02/06/2017 05:14 PM, James Bottomley wrote:
>> On Sun, 2017-02-05 at 21:13 -0800, Dan Williams wrote:
>>> On Sun, Feb 5, 2017 at 1:13 AM, Christoph Hellwig wrote:
Dan,
can you please quote your emails? I can't find any content
On Fri 03 Feb 10:36 PST 2017, Georgi Djakov wrote:
> Add the RPM Clock Controller DT node for msm8974-based platforms, so that
> drivers can use the clocks provided by the RPM processor.
>
> Signed-off-by: Georgi Djakov
Reviewed-by: Bjorn Andersson
Regards,
Bjorn
> ---
> arch/arm/boot/dts/q
The core configuration is the only difference between mt8173 and mt8176.
Like what arm/juno and marvell/armada-ap806 did, this change splits
mt8173.dtsi into mt817x.dtsi and mt8173.dtsi. mt817x.dtsi defines the
common blocks for mt8173 and mt8176. mt8173.dtsi and mt8176.dtsi
describe mt8173 and mt8
Hi Andrew,
Today's linux-next merge of the akpm tree got a conflict in:
drivers/net/can/flexcan.c
between commits:
9eb7aa891101 ("can: flexcan: add quirk FLEXCAN_QUIRK_ENABLE_EACEN_RRS")
b3cf53e988ce ("can: flexcan: add support for timestamp based rx-offload")
from the net-next tree and
Thanks Masami for the review.
On Tuesday 07 February 2017 08:41 AM, Masami Hiramatsu wrote:
> On Thu, 2 Feb 2017 16:41:41 +0530
> Ravi Bangoria wrote:
>
>> SDT marker argument is in N@OP format. N is the size of argument and
>> OP is the actual assembly operand. OP is arch dependent component an
From: Guan Ben
Make the EN2 pin optional. This is useful for boards,
which have this pin fix wired, for example to ground.
Signed-off-by: Guan Ben
Signed-off-by: Mark Jonas
Signed-off-by: Heiko Schocher
---
.../devicetree/bindings/net/nfc/trf7970a.txt | 4 ++--
drivers/nfc/trf7970a.
From: Guan Ben
extend the pwm-beeper driver to support customized frequency
for SND_BELL from device tree.
Signed-off-by: Guan Ben
Signed-off-by: Mark Jonas
[h...@denx.de: adapted to 4.10-rc7]
Signed-off-by: Heiko Schocher
---
.../devicetree/bindings/input/pwm-beeper.txt | 3 ++
dri
Add the documentation to avoid PHY lane swapping. This is a boolean
entry to notify the phy device drivers that the TX/RX lanes NO need
to be swapped.
The use case for this binding mostly happens after wrong HW
configuration of PHY IC during bootstrap.
Signed-off-by: Lukasz Majewski
---
Changes
This patch adds support for enabling or disabling the lane swapping (called
"port mirroring" in PHY's CFG4 register) feature of the DP83867 TI's PHY
device.
One use case is when bootstrap configuration enables this feature (because
of e.g. LED_0 wrong wiring) so then one needs to disable it in sof
The DP83867 when not properly bootstrapped - especially with LED_0 pin -
can enter N/A MODE4 for "port mirroring" feature.
To provide normal operation of the PHY, one needs not only to explicitly
disable the port mirroring feature, but as well stop some IC internal
testing (which disables RGMII co
On Tue 31 Jan 04:35 PST 2017, Loic Pallardy wrote:
> Associated clock is prepared in st_rproc_parse_dt function.
> it should be unprepared in case of error during probing.
>
> Signed-off-by: Loic Pallardy
Applied patch 1 and 2.
Regards,
Bjorn
Hi Joerg,
[auto build test ERROR on linus/master]
[also build test ERROR on v4.10-rc7]
[cannot apply to iommu/next next-20170206]
[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/Joerg-Roedel/Let
On Tue 24 Jan 15:13 PST 2017, Sarangdhar Joshi wrote:
> The rproc_add_virtio_devices() requests firmware asynchronously and
> triggers boot if the auto_boot flag is set. However, this
> asynchronous call seems to be redundant for non auto-boot scenario
> since the rproc_boot() would call request_f
Hi Matthew,
On Mon, Feb 06, 2017 at 06:49:02AM -0800, Matthew Wilcox wrote:
>
> [adding linux-arch to see if anyone there wants to do an optimised
> version of memfill for their CPU]
>
> On Mon, Feb 06, 2017 at 12:16:44AM +0900, Minchan Kim wrote:
> > +static inline void zram_fill_page(char *ptr
Hi Boris,
2016-12-14 16:06 GMT+09:00 Boris Brezillon :
> On Wed, 14 Dec 2016 09:31:01 +0900
> Masahiro Yamada wrote:
>
>> - "This functions return ..." -> "This function returns ..."
>> - "I you want ..." -> "If you want ..."
>>
>> Signed-off-by: Masahiro Yamada
>
> Acked-by: Boris Brezillon
On Tue, Feb 07, 2017 at 11:24:40AM +0800, zhouxianrong wrote:
>
>
> On 2017/2/7 10:54, Minchan Kim wrote:
> >On Tue, Feb 07, 2017 at 10:20:57AM +0800, zhouxianrong wrote:
> >
> >< snip >
> >
> 3. the below should be modified.
>
> static inline bool zram_meta_get(struct zram *zram)
>
On 02/06/2017 02:48 PM, Willy Tarreau wrote:
On Mon, Feb 06, 2017 at 06:46:39AM -0800, Guenter Roeck wrote:
An updated patch was pushed here :
https://kernel.org/pub/linux/kernel/v3.x/stable-review/patch-3.10.105-rc2.gz
Better, but unfortunately there is now a different build error.
Build
Hi Joerg,
[auto build test ERROR on linus/master]
[also build test ERROR on v4.10-rc7]
[cannot apply to iommu/next next-20170206]
[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/Joerg-Roedel/Let
Peter,
On 1/23/17 19:33, Peter Zijlstra wrote:
On Mon, Jan 16, 2017 at 01:23:30AM -0600, Suravee Suthikulpanit wrote:
static void perf_iommu_read(struct perf_event *event)
{
- u64 count = 0ULL;
- u64 prev_raw_count = 0ULL;
- u64 delta = 0ULL;
+ u64 count, prev;
+
Add a missing character in the function description.
s/bringin /bringing /
Signed-off-by: Dou Liyang
---
arch/x86/kernel/apic/apic.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/kernel/apic/apic.c b/arch/x86/kernel/apic/apic.c
index 5b7e43e..b9c282d 100644
--- a/a
On Thu 02 Feb 16:04 PST 2017, Sarangdhar Joshi wrote:
> SCM call to check whether Peripheral Authentication Service (PAS)
> is supported returns false for ADSP. Drop this call from the driver
> so that the probe() function succeeds for ADSP PIL device.
>
Applied, thanks
Regards,
Bjorn
> Signed
Hi Joerg,
[auto build test ERROR on linus/master]
[also build test ERROR on v4.10-rc7]
[cannot apply to iommu/next next-20170206]
[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/Joerg-Roedel/Let
Hi Satendra,
As long as I review, this patch becomes worse than your previous
patches, because at least two topics are accumulated to the patch:
* Code refactoring to aggregate several functions.
* Add new ioctl(2) command to handle several elements in one operation.
In this case, patches with
Hi Dave,
> Hi,
> On 02/06/2017 08:24 AM, Lukasz Majewski wrote:
> > Hi Dave,
> >
> >> On 02/03/2017 09:24 AM, Lukasz Majewski wrote:
> >>> The "opp_high" property brings support for 1.5 GHz CPU frequency
> >>> for TI's am57xx line of processors.
> >>>
> >>> Signed-off-by: Lukasz Majewski
> >>> -
On Tue, Jan 10, 2017 at 04:57:32PM +, Colin King wrote:
> From: Colin Ian King
>
> res is assigned to sizeof(ctx), however, this is unused and res
> is updated later on without that assigned value to res ever being
> used. Remove this redundant assignment.
>
> Fixes CoverityScan CID#1395546
On 06-02-17, 13:51, Markus Mayer wrote:
> From: Markus Mayer
>
> Add the MIPS CPUfreq driver. This driver currently supports CPUfreq on
> BMIPS5xxx-based SoCs.
>
> Signed-off-by: Markus Mayer
> ---
> drivers/cpufreq/Kconfig | 10 +++
> drivers/cpufreq/Makefile| 1 +
> driver
On 06-02-17, 13:51, Markus Mayer wrote:
> From: Markus Mayer
>
> Enable all applicable CPUfreq options.
>
> Signed-off-by: Markus Mayer
> ---
> arch/mips/configs/bmips_stb_defconfig | 8
> 1 file changed, 8 insertions(+)
>
> diff --git a/arch/mips/configs/bmips_stb_defconfig
> b/arc
On Wed, Feb 01, 2017 at 09:32:09PM +0100, Richard Weinberger wrote:
> When a completion is declared on-stack we have to use
> COMPLETION_INITIALIZER_ONSTACK().
>
> Fixes: 0b81d07790726 ("fs crypto: move per-file encryption from f2fs
> tree to fs/crypto")
> Signed-off-by: Richard Weinberger
Thank
On 06-02-17, 13:51, Markus Mayer wrote:
> From: Markus Mayer
>
> Ran "make savedefconfig" to bring bmips_stb_defconfig up to date.
>
> Signed-off-by: Markus Mayer
> ---
> arch/mips/configs/bmips_stb_defconfig | 8 ++--
> 1 file changed, 2 insertions(+), 6 deletions(-)
>
> diff --git a/arc
On 06-02-17, 03:03, Paul Gortmaker wrote:
> None of the Kconfigs for any of these drivers are tristate,
> meaning that they currently are not being built as a module by anyone.
>
> Lets remove the modular code that is essentially orphaned, so that
> when reading the drivers there is no doubt they
On 02/06/2017 05:14 PM, James Bottomley wrote:
> On Sun, 2017-02-05 at 21:13 -0800, Dan Williams wrote:
>> On Sun, Feb 5, 2017 at 1:13 AM, Christoph Hellwig wrote:
>>> Dan,
>>>
>>> can you please quote your emails? I can't find any content
>>> inbetween all these quotes.
>>
>> Sorry, I'm using g
It is possible for dev_pm_opp_find_freq_exact() to return errors. It was
all fine earlier as dev_pm_opp_get_voltage() had a check within it to
check for invalid OPPs, but dev_pm_opp_put() doesn't have any similar
checks and the callers need to make sure OPP is valid before calling
them.
Also updat
It is possible for dev_pm_opp_find_freq_exact() to return errors. It was
all fine earlier as dev_pm_opp_get_voltage() had a check within it to
check for invalid OPPs, but dev_pm_opp_put() doesn't have any similar
checks and the callers need to make sure OPP is valid before calling
them.
Also updat
There isn't much the user can do on seeing these warnings, as the
hardware is actually okay. dev_err suits much better here.
Signed-off-by: Viresh Kumar
---
drivers/thermal/cpu_cooling.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/drivers/thermal/cpu_cooling.
There isn't much the user can do on seeing this warning, as the hardware
is actually okay. dev_err suits much better here.
Signed-off-by: Viresh Kumar
---
drivers/thermal/devfreq_cooling.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/thermal/devfreq_cooling.c
There is no need to check for IS_ERR() as we are looking for a very
particular error value here. Drop the first check.
Reported-by: Dan Carpenter
Signed-off-by: Viresh Kumar
---
drivers/thermal/devfreq_cooling.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/thermal
Hi,
This series contains minor fixes/cleanups for thermal cooling drivers.
V1->V2:
- s/dev_warn/dev_err (Rafael)
- Two new patches to make similar (^^) change at other places
Viresh Kumar (5):
thermal: devfreq: Simplify expression
thermal: devfreq_cooling: Replace dev_warn with dev_err
the
On 06-02-17, 13:02, Rafael J. Wysocki wrote:
> On Monday, February 06, 2017 03:56:28 PM Viresh Kumar wrote:
> > It is possible for dev_pm_opp_find_freq_exact() to return errors. It was
> > all fine earlier as dev_pm_opp_get_voltage() had a check within it to
> > check for invalid OPPs, but dev_pm_o
The code in _regulator_get() got a bit confusing over time, with control
flow jumping to a label from couple of places. Let's untangle it a bit by
doing the following:
1. Make handling of missing supplies and substituting them with dummy
regulators more explicit:
- check if we not have full const
On Mon, Jan 30, 2017 at 04:57:13PM -0800, Dmitry Torokhov wrote:
> When converting a driver to managed resources it is desirable to be able to
> manage all resources in the same fashion. This change allows managing clock
> prepared and enabled state in the same way we manage many other resources.
>
On 02/05, Christoph Hellwig wrote:
> On Mon, Jan 16, 2017 at 09:32:20AM -0800, Christoph Hellwig wrote:
> > On Fri, Jan 13, 2017 at 11:12:11AM -0800, Jaegeuk Kim wrote:
> > > Previously, I've done to issue discard bios asynchronously. But the
> > > problem that
> > > I've got is that was not enoug
From: Cong Wang
Date: Mon, 6 Feb 2017 16:32:14 -0800
> On Fri, Feb 3, 2017 at 1:20 PM, Luis R. Rodriguez wrote:
>> When we igmpv3_add_delrec() we kzalloc the pmc, but when users
>> calligmpv3_del_delrec() we never free the pmc. This was caught
>> by the following kmemleak splat:
>>
>> unrefe
On systems where GIC support two security states, both the register
GICR_WAKE and GICD_IGROUPR accesses are RAZ/WI from non-secure.
The function gic_enable_redist() to wake/sleep redistributor is not
harmful at all, but it is confusing looking at the code. The current
code checks the single securit
The commit ccd9432a5c 'irqchip/gicv3: Remove disabling redistributor
and group1 non-secure interrupts' was introduced to avoid GICR sleep
and wakeup steps on systems where GIC support two security states.
Unfortunately code was using the incorrect (GICD_CTLR.DS) information
to know GIC security sta
Just one comment,
the subject should be
[PATCH] Thermal: imx_thermal : Fix possible NULL derefrence
On Mon, 2017-01-30 at 10:34 +0530, Shailendra Verma wrote:
> of_device_get_match_data could return NULL, and so can cause
> a NULL pointer dereference later.
>
> Signed-off-by: Shailendra Verma
On 2017/2/7 10:54, Minchan Kim wrote:
On Tue, Feb 07, 2017 at 10:20:57AM +0800, zhouxianrong wrote:
< snip >
3. the below should be modified.
static inline bool zram_meta_get(struct zram *zram)
@@ -495,11 +553,17 @@ static void zram_meta_free(struct zram_meta *meta, u64
disksize)
In the context of recovering from crash,
rproc_trigger_recovery() does rproc_shutdown() followed
by rproc_boot(). The remoteproc resources are cleaned up
in rproc_shutdown() and immediately reallocated in
rproc_boot() which is an unnecessary overhead.
Furthermore, we want the memory regions to be
Hi Heiko, John and Greg,
On 2017/2/7 8:06, Heiko Stuebner wrote:
Hi Frank,
Am Sonntag, 5. Februar 2017, 10:51:01 CET schrieb Frank Wang:
Originally, dwc2 just handle one clock named otg, however, it may have
two or more clock need to manage for some new SoCs, so this adds
change clk to clk's a
Since tracing/*probe_events will accept a probe definition
up to 4096 - 2 ('\n' and '\0') bytes, it must show 4094 instead
of 4096 in warning message.
Signed-off-by: Masami Hiramatsu
---
kernel/trace/trace_probe.c |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/kernel/tr
On Thu, 2 Feb 2017 16:41:40 +0530
Ravi Bangoria wrote:
> 'perf probe' is failing for sdt markers whose arguments has rNN
> (with postfix b/w/d), %rsp, %esp, %sil etc. registers. Add renaming
> logic for these registers.
>
Looks good to me.
Acked-by: Masami Hiramatsu
Thanks!
> Signed-off-by
On Mon, Feb 06, 2017 at 02:00:51PM +0200, Jani Nikula wrote:
> On Mon, 06 Feb 2017, changbin...@intel.com wrote:
> > From: Changbin Du
> >
> > Prompt user how to quickly jump to the item he/she is interested in.
>
> :o
>
> All these years. I... I didn't know. Thanks!
>
aha, me too! You know, bac
On Thu, 2 Feb 2017 16:41:41 +0530
Ravi Bangoria wrote:
> SDT marker argument is in N@OP format. N is the size of argument and
> OP is the actual assembly operand. OP is arch dependent component and
> hence it's parsing logic also should be placed under tools/perf/arch/.
>
Ok, I have one questi
On Mon, Feb 06, 2017 at 07:42:11AM -0700, Jim Davis wrote:
> On Mon, Feb 6, 2017 at 12:46 AM, wrote:
> > From: Changbin Du
> >
> > Kernel menuconfig support direct jumping function from the search
> > result. This is a very convenient feature but not documented. So
> > add a short description to
On 07/02/17 14:25, Chris Packham wrote:
> On 07/02/17 14:13, Chris Packham wrote:
>> On 07/02/17 14:03, Stephen Boyd wrote:
>>> On 02/06, Chris Packham wrote:
On 07/02/17 12:14, Stephen Boyd wrote:
> On 02/03, Chris Packham wrote:
>> The initial implementation in commit e120c17a70e5 ("
This patch adds zx296718 SoC support for ZTE's i2s controller driver.
Signed-off-by: Baoyou Xie
---
sound/soc/zte/zx-i2s.c | 45 +++--
1 file changed, 35 insertions(+), 10 deletions(-)
diff --git a/sound/soc/zte/zx-i2s.c b/sound/soc/zte/zx-i2s.c
index ed7
This patch documents the devicetree for the ZTE's zx296718
I2S audio controller.
Signed-off-by: Baoyou Xie
---
Documentation/devicetree/bindings/sound/zte,zx-i2s.txt | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/Documentation/devicetree/bindings/sound/zte,zx-i2s.txt
1 - 100 of 1064 matches
Mail list logo
