The i2s related clock support is missing from the existing zx296718
clock driver. This patch adds it, so that the upstream ZX I2S driver
can work out.
Signed-off-by: Baoyou Xie
---
drivers/clk/zte/clk-zx296718.c | 4
1 file changed, 4 insertions(+)
diff --git a/drivers/clk/zte/clk-zx296718
G'day,
On 7 Feb 2017 at 01:09:09, Wojciech Ziemba wrote:
> diff --git a/Documentation/devicetree/bindings/power/supply/bq2416x.txt
> b/Documentation/devicetree/bindings/power/supply/bq2416x.txt
> new file mode 100644
> index 000..8f4b814
> --- /dev/null
> +++ b/Documentation/devicetree/bindin
Hello,
I need your assistance in a deal that will be of mutual benefit for the both of
us from Camp Stanley, Stationed in Uijeongbu, South Korea. Please get back to
me for more info.
Thank you for your time.
Sgt. Monica Martinez.
On Tue, 2017-02-07 at 02:23 +, Dexuan Cui wrote:
> Any news on this thread?
>
> The issue is still blocking Linux from booting up normally in my test. :-(
>
> Have we identified the faulty patch?
> If so, at least I can try to revert it to boot up.
It's interesting that you have a reproducib
On Thu, 2 Feb 2017 16:41:38 +0530
Ravi Bangoria wrote:
> The v5 patchset for sdt marker argument support for x86 [1] has
> couple of issues. For example, it still has x86 specific code
> in general code. It lacks support for rNN (with size postfix
> b/w/d), %rsp, %esp, %sil etc. registers and s
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)
> >>
> >>/* Free all pages t
Hi, Minchan,
Minchan Kim writes:
> We changed swap_cluster_info lock from bit_spin_lock to spinlock
> so we need to initialize the spinlock before the using. Otherwise,
> lockdep is broken.
>
> Cc: Tim Chen
> Cc: Huang Ying
> Cc: Hugh Dickins
> Signed-off-by: Minchan Kim
Good catch! Thanks
On Mon, Feb 06, 2017 at 04:47:24PM -0900, Kent Overstreet wrote:
> On Mon, Feb 06, 2017 at 01:53:09PM +0100, Pavel Machek wrote:
> > Still there on v4.9, 36 threads on nokia n900 cellphone.
> >
> > So.. what needs to be done there?
> But, I just got an idea for how to handle this that might be ha
On 2017/2/6 22:49, 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, unsigned long len,
+
On Mon, Feb 06, 2017 at 04:16:55PM +, David Laight wrote:
> From: Stafford Horne
> > Sent: 05 February 2017 07:08
> > This was causing a build failure for openrisc when using musl and
> > gcc 5.4.0 since the file is not available in the toolchain.
> >
> > It doesnt seem this is needed and remo
From: Levy-Cai
Add framebuffer driver for hi3660 SoC, this driver include lcd
driver & Hdmi adv7533/adv7535 driver, support lcd display at
1080p@60 and hdmi display at 1080p@60.
Signed-off-by: cailiwei
---
drivers/video/fbdev/hisi/dss/hdmi/adv75xx.c| 1522
drivers/
From: Levy-Cai
Add framebuffer driver for hi3660 SoC, this driver include lcd
driver & Hdmi adv7533/adv7535 driver, support lcd display at
1080p@60 and hdmi display at 1080p@60.
Signed-off-by: cailiwei
---
drivers/video/fbdev/Kconfig | 11 ++
drivers/video/fbdev/Makefile
From: Levy-Cai
Add framebuffer driver for hi3660 SoC, this driver include lcd
driver & Hdmi adv7533/adv7535 driver, support lcd display at
1080p@60 and hdmi display at 1080p@60.
Signed-off-by: cailiwei
---
drivers/video/fbdev/hisi/dss/hisi_fb_bl.c | 323 +
drivers/video/fbdev/his
From: Levy-Cai
Add framebuffer driver for hi3660 SoC, this driver include lcd
driver & Hdmi adv7533/adv7535 driver, support lcd display at
1080p@60 and hdmi display at 1080p@60.
Signed-off-by: cailiwei
---
drivers/video/fbdev/hisi/dss/hisi_fb_utils.c | 249
drivers/video/fbdev/hisi
From: Levy-Cai
Add framebuffer driver for hi3660 SoC, this driver include lcd
driver & Hdmi adv7533/adv7535 driver, support lcd display at
1080p@60 and hdmi display at 1080p@60.
Signed-off-by: cailiwei
---
arch/arm64/boot/dts/hisilicon/hi3660.dtsi | 48 +++
1 file c
We changed swap_cluster_info lock from bit_spin_lock to spinlock
so we need to initialize the spinlock before the using. Otherwise,
lockdep is broken.
Cc: Tim Chen
Cc: Huang Ying
Cc: Hugh Dickins
Signed-off-by: Minchan Kim
---
Andrew,
I think it's no worth to add this patch to separate commit.
When trying to initiate a dual-stack (ipv4v6) connection, a MC7710, FW
version SWI9200X_03.05.24.00ap answers with an unsupported LSI. Add support
for this LSI.
Also the link_type should be ignored when going idle, otherwise the modem
is stuck in a bad link state.
Tested on MC7710, T-Mobile DE, APN
When the context is deactivated, the link_type is set to 0xff, which
triggers a warning message, and results in a wrong link status, as
the LSI is ignored.
Signed-off-by: Stefan Brüns
---
drivers/net/usb/sierra_net.c | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
diff --gi
If a context is configured as dualstack ("IPv4v6"), the modem indicates
the context activation with a slightly different indication message.
The dual-stack indication omits the link_type (IPv4/v6) and adds
additional address fields.
IPv6 LSIs are identical to IPv4 LSIs, but have a different link ty
From: LiuHailong
Debug interrupts can be taken during regular program or a standard
interrupt, the EA of the instruction causing the interrupt will be
kept in DSRR0.
Kernel will check if this value is between [interrupt_base_book3e,
__end_interrupts].
However, when the kernel build with CONFIG_RE
On Tue, Jan 31, 2017 at 02:36:07PM -0200, Fabio Estevam wrote:
> Building arm allnodefconfig causes the following build warning:
>
> drivers/char/random.c:318:12: warning: 'random_min_urandom_seed' defined but
> not used [-Wunused-variable]
>
> Fix the warning by moving 'random_min_urandom_seed'
On 2017/2/7 7:48, Minchan Kim wrote:
Hi
On Mon, Feb 06, 2017 at 09:28:18AM +0800, zhouxianrong wrote:
On 2017/2/5 22:21, Minchan Kim wrote:
Hi zhouxianrong,
On Fri, Feb 03, 2017 at 04:42:27PM +0800, zhouxianr...@huawei.com wrote:
From: zhouxianrong
test result as listed below:
zero
On 02/06, Michal Hocko wrote:
>On Sat 04-02-17 16:16:04, Ye Xiaolong wrote:
>> On 01/26, Michal Hocko wrote:
>> >On Wed 25-01-17 12:27:06, Ye Xiaolong wrote:
>> >> On 01/24, Michal Hocko wrote:
>[...]
>> >> >perf profiles before and after the patch.
>> >>
>> >> Here is the perf profiles,
>> >
>>
> From: linux-block-ow...@vger.kernel.org [mailto:linux-block-
> ow...@vger.kernel.org] On Behalf Of Dexuan Cui
> Sent: Friday, February 3, 2017 20:23
> To: Hannes Reinecke ; Bart Van Assche
> ; h...@suse.de; ax...@kernel.dk
> Cc: h...@lst.de; linux-kernel@vger.kernel.org; linux-bl...@vger.kernel.o
Boris,
On 1/25/17 16:55, Borislav Petkov wrote:
On Wed, Jan 25, 2017 at 10:46:53AM +0100, Peter Zijlstra wrote:
Which is absolutely insane.
Right,
IMO, the simplest thing to do for your purposes is to embed a struct
amd_iommu pointer into struct perf_amd_iommu at init time so that you
don't
Peter,
On 1/25/17 16:46, Peter Zijlstra wrote:
On Mon, Jan 16, 2017 at 01:23:36AM -0600, Suravee Suthikulpanit wrote:
+ pi = container_of(event->pmu, struct perf_amd_iommu, pmu);
+ hwc->idx = pi->idx;
+ hwc->config = event->attr.config;
+ hwc->ext
On 02/02/2017 02:50 PM, Russell King - ARM Linux wrote:
On Fri, Jan 06, 2017 at 06:11:34PM -0800, Steve Longerbeam wrote:
+/* register an internal subdev as a platform device */
+static struct imx_media_subdev *
+add_internal_subdev(struct imx_media_dev *imxmd,
+ const struct
On 02/02/2017 02:35 PM, Russell King - ARM Linux wrote:
However, "*vfd" contains a struct device, and you _correctly_ set the
release function for "*vfd" to video_device_release via camif_videodev.
However, if you try to rmmod imx-media, then you end up with a kernel
warning that you're freein
On Mon, Feb 06, 2017 at 05:08:17PM -0800, Stephen Boyd wrote:
> On 02/06/2017 05:01 PM, Stephen Boyd wrote:
> > When I compile files with sparse, I get these sorts of warnings:
> >
> > arch/arm64/include/asm/lse.h:14:28: warning: Unknown escape 'l'
> > arch/arm64/include/asm/lse.h:14:37: warning: U
On Mon, Feb 06, 2017 at 01:53:09PM +0100, Pavel Machek wrote:
> On Sat 2016-02-20 21:04:32, Pavel Machek wrote:
> > Hi!
> >
> > > > > > > I know it is normal to spawn 8 threads for every single function,
> > > > > > ...
> > > > > > > but 28 threads?
> > > > > > >
> > > > > > > root 974 0.0
Em Tue, Feb 07, 2017 at 02:10:28AM +0100, Borislav Petkov escreveu:
> From: Borislav Petkov
>
> When using perf stat on an AMD F15h system with the default hw events
> attributes, some of the events don't get counted:
>
> Performance counter stats for 'sleep 1':
>
> 0.749208 tas
On 02/06/2017 08:46 PM, Ulf Hansson wrote:
On 5 February 2017 at 10:34, Elaine Zhang wrote:
On 01/26/2017 05:30 AM, Ulf Hansson wrote:
On 22 January 2017 at 04:34, Elaine Zhang
wrote:
On 01/20/2017 09:16 PM, Ulf Hansson wrote:
On 20 January 2017 at 03:21, Elaine Zhang
wrote:
I
Hi Arnd,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: f7d6040aa45df6ffd9e891114125dc919f18b96b
commit: a76bcf557ef408b368cf26f52a60865bfc27b632 Kbuild: enable
-Wmaybe-uninitialized warning for "make W=1"
date:
Em Tue, Feb 07, 2017 at 02:09:17AM +0100, Borislav Petkov escreveu:
> From: Borislav Petkov
>
> Add helper functions to be able to read/write ints into proc files.
>
> Signed-off-by: Borislav Petkov
> ---
> tools/lib/api/fs/fs.c | 42 ++
> tools/lib/api/
ow, but they are low enough risk for this late in the cycle and
the fixes have waiting users . They have received a build success
notification from the 0day robot, pass the latest ndctl unit tests,
and appeared in next-20170206.
The following changes since commit 7a308bb3016f57e5be11a677d15b821536419d3
Boris,
On 1/23/17 02:55, Borislav Petkov wrote:
@@ -421,46 +427,46 @@ static __init void amd_iommu_pc_exit(void)
};
static __init int
-_init_perf_amd_iommu(struct perf_amd_iommu *perf_iommu, char *name)
+init_one_perf_amd_iommu(struct perf_amd_iommu *perf_iommu, unsigned int idx)
{
i
On Thu, 2 Feb 2017 16:41:43 +0530
Ravi Bangoria wrote:
> 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__com
On Mon, Feb 06, 2017 at 10:47:41AM +0100, Michal Hocko wrote:
> On Fri 03-02-17 13:06:04, Luis R. Rodriguez wrote:
> > On next-20170125 running some kselftest not yet upstream I eventually
> > get a kmemleak splat:
> >
> > unreferenced object 0xa7b1034b4000 (size 16384):
> > comm "driver_dat
On Mon, Feb 06, 2017 at 04:10:11PM -0800, James Bottomley wrote:
> On Mon, 2017-02-06 at 16:52 -0500, J. Bruce Fields wrote:
> > On Mon, Feb 06, 2017 at 07:18:16AM -0800, James Bottomley wrote:
> > > On Mon, 2017-02-06 at 09:50 -0500, Theodore Ts'o wrote:
> > > > On Sun, Feb 05, 2017 at 10:46:23PM
fix warning:
drivers/gpu/drm/rockchip/cdn-dp-reg.c:632:24: warning:
'val[1]' may be used uninitialized in this function [-Wmaybe-uninitialized]
msa_misc = 2 * val[0] + 32 * val[1] +
Signed-off-by: Mark Yao
---
drivers/gpu/drm/rockchip/cdn-dp-reg.c | 2 +-
1 file changed, 1 insertion(+), 1 d
On Tue, 7 Feb 2017 00:06:42 +
Al Viro wrote:
> On Mon, Feb 06, 2017 at 05:17:35PM -0500, Steven Rostedt wrote:
> > From: "Steven Rostedt (VMware)"
> >
> > The likely/unlikely profiler showed that the unlikely around the
> > dentry->d_flags & DCACHE_OP_REVALIDATE was wrong 95% of the time. A
Hi Thomas,
I just now updated my build box from 4.9-rc to 4.10-rc, and picked up
these changes. My machine went from doing:
[0.00] tsc: Fast TSC calibration using PIT
[0.060669] TSC deadline timer enabled
[0.142701] TSC synchronization [CPU#0 -> CPU#1]:
[0.142704] Measured 312
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 ("clk: mvebu: support
> for 98DX3236 SoC") ha
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 ("clk: mvebu: support
for 98DX3236 SoC") hardcoded a fixed value for the main PLL frequenc
On Fri, 3 Feb 2017 15:56:42 +0530
Ravi Bangoria wrote:
> All events from 'perf list', except SDT events, can be directly recorded
> with 'perf record'. But, the flow is little different for SDT events.
> Probe point for SDT event needs to be created using 'perf probe' before
> recording it using
There is interest in adding a Linux driver for TI BQ2416X battery
charger. The driver supports BQ24160 chip, thus can be easily extended
for other BQ2416X family chargers.
Device exposes 'POWER_SUPPLY_PROP_*' properties and a number of knobs
for controlling the charging process as well as sends pow
From: Borislav Petkov
When using perf stat on an AMD F15h system with the default hw events
attributes, some of the events don't get counted:
Performance counter stats for 'sleep 1':
0.749208 task-clock (msec) #0.001 CPUs utilized
1 context-swit
From: Borislav Petkov
Add helper functions to be able to read/write ints into proc files.
Signed-off-by: Borislav Petkov
---
tools/lib/api/fs/fs.c | 42 ++
tools/lib/api/fs/fs.h | 3 +++
2 files changed, 45 insertions(+)
diff --git a/tools/lib/api/fs/f
The firmware API does not scale well: when new features are added we
either add a new exported symbol or extend the arguments of existing
routines. For the later case this means we need to traverse the kernel
with a slew of collateral evolutions to adjust old driver users. The
firmware API is also
Greg,
This v5 drops the driver porting examples in light of the fact simple
cases do not yet benefit from use of the newer API. The API is purposely
introduced bare bones so new features are easier to review.
This v5 embraces the proposed "driver data" name, extends documentation
to cover the dri
This adds a load tester driver test_driver_data a for the new extensible
driver_data loader API, part of firmware_class. This test driver enables
you to build your tests in userspace by exposing knobs of the exported
API to userspace and enables a trigger action to mimic a one time use
of the kerne
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
WIP.sched/core
head: 4906e0da940c919f1669c365cb2e1434bd0cbbe9
commit: 239a7a08abab3068f29746f53d65c834c1c63579 [138/170] sched/headers: Split
out of
config: mips-mips_paravirt_defconfig (attached as .config)
compiler: mips64-
Ok,
here's something (as replies to this message) which looks much more
decent.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
On 02/06/2017 05:01 PM, Stephen Boyd wrote:
> When I compile files with sparse, I get these sorts of warnings:
>
> arch/arm64/include/asm/lse.h:14:28: warning: Unknown escape 'l'
> arch/arm64/include/asm/lse.h:14:37: warning: Unknown escape 'l'
> arch/arm64/include/asm/alternative.h:172:28: warning
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:
> >
> > > +static void optimized_callback(struct optimized_kprobe *op
On Mon, Feb 06, 2017 at 04:58:38PM -0800, Cameron Gutman wrote:
> Set the LED_CORE_SUSPENDRESUME flag on our LED device so the
> LED state will be automatically restored by LED core on resume.
>
> Since Xbox One pads stop flashing only when reinitialized, we'll
> send them the initialization packe
On 02/06, Florian Fainelli wrote:
> On 02/06/2017 02:59 PM, Stephen Boyd wrote:
> > On 02/03, Florian Fainelli wrote:
> >>
> >> We already have another piece of drive code that manipulates registers
> >> in the Bus Interface Unit located in drivers/soc/bcm/brcmstb/biuctrl.c
> >> and which has littl
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 ("clk: mvebu: support
> >> for 98DX3236 SoC") hardcoded a fixed value for the main PLL frequency.
> >> Port code from the Marvell supplie
When I compile files with sparse, I get these sorts of warnings:
arch/arm64/include/asm/lse.h:14:28: warning: Unknown escape 'l'
arch/arm64/include/asm/lse.h:14:37: warning: Unknown escape 'l'
arch/arm64/include/asm/alternative.h:172:28: warning: Unknown escape 'o'
This is because sparse is tryin
Set the LED_CORE_SUSPENDRESUME flag on our LED device so the
LED state will be automatically restored by LED core on resume.
Since Xbox One pads stop flashing only when reinitialized, we'll
send them the initialization packet so they calm down too.
Signed-off-by: Cameron Gutman
---
Sending this
This patch adds thermal driver for ZTE's zx2967 family.
Signed-off-by: Baoyou Xie
---
drivers/thermal/Kconfig | 8 ++
drivers/thermal/Makefile | 1 +
drivers/thermal/zx2967_thermal.c | 258 +++
3 files changed, 267 insertions(+)
create mo
Add the zx2967 thermal drivers as maintained by ARM ZTE
architecture maintainers, as they're parts of the core IP.
Signed-off-by: Baoyou Xie
---
MAINTAINERS | 2 ++
1 file changed, 2 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 4e81e2b..2a84440 100644
--- a/MAINTAINERS
+++ b/MAINT
This patch adds dt-binding documentation for zx2967 family thermal sensor.
Signed-off-by: Baoyou Xie
Acked-by: Rob Herring
Reviewed-by: Shawn Guo
---
.../devicetree/bindings/thermal/zx2967-thermal.txt | 116 +
1 file changed, 116 insertions(+)
create mode 100644 Documentat
On Mon, Feb 6, 2017 at 4:22 PM, Dave Jones wrote:
> On Mon, Feb 06, 2017 at 09:19:24AM +0100, Christoph Hellwig wrote:
> >
> > Double mnt_want_write, no idea why lockdep isn't reporting that for me.
> > Fix below:
>
> Yep, seems to do the trick.
>
> Tested-by: Dave Jones
Christop, mind re-sen
On Sun, Feb 05, 2017 at 05:12:46PM +0100, Mark Brown wrote:
> On Sat, Feb 04, 2017 at 09:45:02AM -0800, Dmitry Torokhov wrote:
> > On Sat, Feb 04, 2017 at 12:48:19PM +0100, Mark Brown wrote:
>
> > > It really shouldn't be either of these things, at least on DT systems.
>
> > But it definitely hap
On Mon, 6 Feb 2017 13:02:29 +
Will Deacon wrote:
> On Sat, Feb 04, 2017 at 05:03:20PM +0800, Hekuang wrote:
> > hi
> >
> > 在 2017/2/3 21:00, Will Deacon 写道:
> > >On Fri, Feb 03, 2017 at 11:06:05AM +, He Kuang wrote:
> > >>This patch changes the 'dwarfnum' to 'offset' in register table, s
+++ Arnd Bergmann [01/02/17 18:00 +0100]:
clang warns about unused inline functions by default:
arch/arm/crypto/aes-cipher-glue.c:68:1: warning: unused function '__inittest'
[-Wunused-function]
arch/arm/crypto/aes-cipher-glue.c:69:1: warning: unused function '__exittest'
[-Wunused-function]
A
On Mon, Feb 06, 2017 at 04:21:18PM -0800, Bjorn Andersson wrote:
> On Fri 03 Feb 15:16 PST 2017, Dmitry Torokhov wrote:
>
> > Make it possible to use the bulk API with optional supplies, by allowing
> > the consumer to marking supplies as optional in the regulator_bulk_data.
> >
> > Based on earl
On 1/9/17 6:28 AM, David Sterba wrote:
> On Fri, Jan 06, 2017 at 12:22:34PM -0500, Joseph Salisbury wrote:
>> A kernel bug report was opened against Ubuntu [0]. This bug was fixed
>> by the following commit in v4.7-rc1:
>>
>> commit 4c63c2454eff996c5e27991221106eb511f7db38
>>
>> Author: Luke Dashj
On Fri, Feb 03, 2017 at 03:59:27PM +0800, Yisheng Xie wrote:
> Change the return type of isolate_movable_page() from bool to int. It
> will return 0 when isolate movable page successfully, and return -EBUSY
> when it isolates failed.
>
> There is no functional change within this patch but prepare
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
WIP.sched/core
head: 8b88220c2b48c511c3dc8210d92a1d99d180dd69
commit: b8dca9f8769ff647742c30f21f5fab0b6a591578 [138/170] sched/headers: Split
out of
config: mips-loongson3_defconfig (attached as .config)
compiler: mips64el-li
On Mon, 2017-02-06 at 12:34 -0700, Ross Zwisler wrote:
> Fix up some incorrect typo-words.
Heh. Thanks. Spelling corrections that aren't
spelled correctly aren't worth much.
> diff --git a/scripts/spelling.txt b/scripts/spelling.txt
[]
> @@ -632,7 +632,7 @@ libaries||libraries
> libary||librar
On Mon, Feb 6, 2017 at 3:27 PM, Luck, Tony wrote:
>> cgroup mode gives a per-CPU breakdown of event and running time, the
>> tool aggregates it into running time vs event count. Both per-cpu
>> breakdown and the aggregate are useful.
>>
>> Piggy-backing on perf's cgroup mode would give us all the
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:
>
> unreferenced object 0x99666ff43b40 (size 192):
> comm "systemd
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 of those
arches.
Signed-off-by: La
Hi,
This is v3 of my series to rename/refactor CONFIG_DEBUG_RODATA
and CONFIG_DEBUG_SET_MODULE_RONX. Among other objections, there shouldn't
be 'debug' in the name since these provide necessary kernel protection.
v3 mostly focuses on changing how the Kconfig dependencies work for the
refactor. Ru
Both of these options are poorly named. The features they provide are
necessary for system security and should not be considered debug only.
Change the names to CONFIG_STRICT_KERNEL_RWX and
CONFIG_STRICT_MODULE_RWX to better describe what these options do.
Signed-off-by: Laura Abbott
---
v3: Mino
On Mon, Feb 06, 2017 at 09:19:24AM +0100, Christoph Hellwig wrote:
> On Mon, Feb 06, 2017 at 01:00:32AM -0500, Dave Jones wrote:
> > This one smells funny to me.
>
> Double mnt_want_write, no idea why lockdep isn't reporting that for me.
> Fix below:
Yep, seems to do the trick.
Tested-by: D
On Sat, 4 Feb 2017 09:52:03 -0500 Tejun Heo wrote:
> SLUB creates a per-cache directory under /sys/kernel/slab which hosts
> a bunch of debug files. Usually, there aren't that many caches on a
> system and this doesn't really matter; however, if memcg is in use,
> each cache can have per-cgroup
On Fri 03 Feb 15:16 PST 2017, Dmitry Torokhov wrote:
> Make it possible to use the bulk API with optional supplies, by allowing
> the consumer to marking supplies as optional in the regulator_bulk_data.
>
> Based on earlier patch by Bjorn Andersson
>
Hi Dmitry,
Rather than fixing my broken pa
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 gmail, but I'll switch to attaching the logs.
>
>
Hi Elaine,
Am Montag, 6. Februar 2017, 10:50:35 CET schrieb Elaine Zhang:
> With the newly introduced clk type for muxes in the grf we now can
> describe some missing clocks, like the clk_gmac2io and clk_gmac2phy
> that selects between clk_mac2io_src and gmac_clkin based on a bit
> set in the gene
On Mon, Feb 06, 2017 at 03:55:20PM -0800, Florian Fainelli wrote:
> Calling phy_read_status() means that we may call into
> genphy_read_status() which in turn will use genphy_update_link() which
> can make changes to phydev->link outside of the state machine's state
> transitions. This is an invali
On Mon, Feb 06, 2017 at 03:55:23PM -0800, Florian Fainelli wrote:
> Calling phy_read_status() means that we may call into
> genphy_read_status() which in turn will use genphy_update_link() which
> can make changes to phydev->link outside of the state machine's state
> transitions. This is an invali
On Mon, 2017-02-06 at 16:52 -0500, J. Bruce Fields wrote:
> On Mon, Feb 06, 2017 at 07:18:16AM -0800, James Bottomley wrote:
> > On Mon, 2017-02-06 at 09:50 -0500, Theodore Ts'o wrote:
> > > On Sun, Feb 05, 2017 at 10:46:23PM -0800, James Bottomley wrote:
> > > > Yes, I know the problem. However,
On Mon, Feb 06, 2017 at 05:17:35PM -0500, Steven Rostedt wrote:
> From: "Steven Rostedt (VMware)"
>
> The likely/unlikely profiler showed that the unlikely around the
> dentry->d_flags & DCACHE_OP_REVALIDATE was wrong 95% of the time. Adding
> trace_printk()s, it revealed that the dentry ops had
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 array of dwc2_hsotg to handle more clocks operation.
>
> Signed
On Mon, Feb 06, 2017 at 06:47:43PM +0100, Luis R. Rodriguez wrote:
> Do we have any test units which can kick off regularly to test against
> such type of regression in the future or is it not worth it?
Yap, it is called: build new kernel and boot it the box :-)
I always try to build and boot all
On Mon, 6 Feb 2017 12:30:38 +0300 Stas Sergeev wrote:
> 05.02.2017 21:31, Andy Lutomirski __:
> > On Sun, Feb 5, 2017 at 2:12 AM, Stas Sergeev wrote:
> >> Currently SS_AUTODISARM is not supported in compatibility
> >> mode, but does not return -EINVAL either. This makes dosemu
> >> built
On 02/06/2017 03:30 PM, Douglas Anderson wrote:
On a Rockchip rk3399-based board during suspend/resume testing, we
found that we could get the console UART into a state where it would
print this to the console a lot:
serial8250: too much work for irq42
Followed eventually by:
NMI watchdo
After 5baecbc 'perf symbols: we can now read separate debug-info files based on
a build ID' and when --symfs option is used perf failed to pick up symbols for
file with the same name between host and sysroot specified by --symfs option.
One can see message like this:
bin/bash with build id 26f0062
Calling phy_read_status() means that we may call into
genphy_read_status() which in turn will use genphy_update_link() which
can make changes to phydev->link outside of the state machine's state
transitions. This is an invalid behavior that is now caught as of
811a919135b9 ("phy state machine: fail
Hi all,
This patch series removes incorrect uses of phy_read_status() which can clobber
the PHY device link while we are executing with the state machine running.
greth was potentially another candidate, but it does funky stuff with
auto-negotation that I am still trying to understand.
Florian F
Calling phy_read_status() means that we may call into
genphy_read_status() which in turn will use genphy_update_link() which
can make changes to phydev->link outside of the state machine's state
transitions. This is an invalid behavior that is now caught as of
811a919135b9 ("phy state machine: fail
Calling phy_read_status() means that we may call into
genphy_read_status() which in turn will use genphy_update_link() which
can make changes to phydev->link outside of the state machine's state
transitions. This is an invalid behavior that is now caught as of
811a919135b9 ("phy state machine: fail
Calling phy_read_status() means that we may call into
genphy_read_status() which in turn will use genphy_update_link() which
can make changes to phydev->link outside of the state machine's state
transitions. This is an invalid behavior that is now caught as off
811a919135b9 ("phy state machine: fai
Hi Frank,
Am Montag, 6. Februar 2017, 09:40:35 CET schrieb Frank Wang:
> On 2017/2/5 17:41, Heiko Stuebner wrote:
> > Am Sonntag, 5. Februar 2017, 10:51:00 CET schrieb Frank Wang:
> >> The original posting on Jan 19th have not received any responses, so I
> >> resend them.
> >>
> >> The Current d
> -Original Message-
> From: Intel-wired-lan [mailto:intel-wired-lan-boun...@lists.osuosl.org] On
> Behalf Of Philippe Reynes
> Sent: Saturday, February 04, 2017 2:49 PM
> To: Kirsher, Jeffrey T ; da...@davemloft.net
> Cc: net...@vger.kernel.org; intel-wired-...@lists.osuosl.org; linux-
> k
On Sun, 5 Feb 2017 10:46:29 -0800 Guenter Roeck wrote:
> On Fri, Jan 27, 2017 at 08:44:30PM +0200, Mike Rapoport wrote:
> > When a non-cooperative userfaultfd monitor copies pages in the background,
> > it may encounter regions that were already unmapped. Addition of
> > UFFD_EVENT_UNMAP allows t
Resend with plain text.
Hi Linus,
On Mon, Feb 6, 2017 at 2:21 AM, Linus Walleij wrote:
> On Tue, Jan 31, 2017 at 8:43 PM, Hoan Tran wrote:
>
>> Next generation of X-Gene SoC's GPIO hardware register map is very
>> similar to DW GPIO. It only differs by a few register addresses.
>> This patch m
101 - 200 of 1064 matches
Mail list logo
