[PATCH 3/8][v2]usb:fsl:otg: Add support to add/remove usb host driver

Add workqueue to add/remove host driver (outside interrupt context) upon each id change. Signed-off-by: Li Yang Signed-off-by: Ramneek Mehresh --- drivers/usb/host/ehci-fsl.c | 83 ++--- drivers/usb/host/ehci-fsl.h | 20 +++ 2 files changed, 84

[PATCH 8/8][v2]usb:fsl:otg: Add host-gadget drv sync delay

Resolve synchronization issue between host and gadget drivers upon role-reversal. Signed-off-by: Ramneek Mehresh Reviewed-by: Li Yang-R58472 Reviewed-by: Fleming Andrew-AFLEMING Tested-by: Fleming Andrew-AFLEMING --- drivers/usb/phy/phy-fsl-usb.c | 12 +++- 1 file changed, 11

[PATCH 0/8][v2]Add OTG support for FSL socs

Add support for otg for all freescale socs having internal usb phy. Ramneek Mehresh (8): usb:fsl:otg: Make fsl otg driver as tristate usb:fsl:otg: Add controller version based ULPI and UTMI phy usb:fsl:otg: Add support to add/remove usb host driver usb:fsl:otg: Signal host drv when host

Re: [PATCH 2/2] mm/cma_debug: correct size input to bitmap function

On Wed, Jul 15 2015, Joonsoo Kim wrote: > In CMA, 1 bit in bitmap means 1 << order_per_bits pages so > size of bitmap is cma->count >> order_per_bits rather than > just cma->count. This patch fixes it. > > Signed-off-by: Joonsoo Kim Acked-by: Michal Nazarewicz > --- > mm/cma_debug.c | 7

Re: [PATCH 1/2] mm/cma_debug: fix debugging alloc/free interface

On Wed, Jul 15 2015, Joonsoo Kim wrote: > CMA has alloc/free interface for debugging. It is intended that alloc/free > occurs in specific CMA region, but, currently, alloc/free interface is > on root dir due to the bug so we can't select CMA region where alloc/free > happens. > > This patch fixes

[tip:perf/urgent] perf hists browser: Take the --comm, --dsos, etc filters into account

Commit-ID: 9c0fa8dd3d58de8b688fda758eea1719949c7f0a Gitweb: http://git.kernel.org/tip/9c0fa8dd3d58de8b688fda758eea1719949c7f0a Author: Arnaldo Carvalho de Melo AuthorDate: Mon, 13 Jul 2015 08:26:35 -0300 Committer: Arnaldo Carvalho de Melo CommitDate: Mon, 13 Jul 2015 16:06:09 -0300

[tip:perf/urgent] perf symbols: Store if there is a filter in place

Commit-ID: 0bc2f2f7d080561cc484d2d0a162a9396bed3383 Gitweb: http://git.kernel.org/tip/0bc2f2f7d080561cc484d2d0a162a9396bed3383 Author: Arnaldo Carvalho de Melo AuthorDate: Mon, 13 Jul 2015 08:21:57 -0300 Committer: Arnaldo Carvalho de Melo CommitDate: Mon, 13 Jul 2015 08:21:57 -0300

Re: [PATCH 6/6] cputime: Introduce cputime_to_timespec64()/timespec64_to_cputime()

On Wed, 15 Jul 2015, Baolin Wang wrote: > On 15 July 2015 at 18:31, Thomas Gleixner wrote: > > On Wed, 15 Jul 2015, Baolin Wang wrote: > > > >> The cputime_to_timespec() and timespec_to_cputime() functions are > >> not year 2038 safe on 32bit systems due to that the struct timepsec > >> will

Applied "regulator: da9062: Drop owner assignment from platform_driver" to the regulator tree

The patch regulator: da9062: Drop owner assignment from platform_driver 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

Applied "regulator: drivers: Drop owner assignment from i2c_driver" to the regulator tree

The patch regulator: drivers: Drop owner assignment from i2c_driver 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

Re: [patch 1/3] avr32/at32ap: Consolidate chained IRQ handler install/remove

Around Mon 13 Jul 2015 20:31:09 - or thereabout, Thomas Gleixner wrote: > Chained irq handlers usually set up handler data as well. We now have > a function to set both under irq_desc->lock. Replace the two calls > with one. > > Search and conversion was done with coccinelle. > >

Re: [patch 2/3] avr32/at32ap: Use irq_set_handler_locked()

Around Mon 13 Jul 2015 20:31:10 - or thereabout, Thomas Gleixner wrote: > Use irq_set_handler_locked() as it avoids a redundant lookup of the > irq descriptor. > > Search and replacement was done with coccinelle. > > Signed-off-by: Thomas Gleixner > Cc: Jiang Liu > Cc: Julia Lawall > Cc:

[PATCH 5/8][v2]usb:fsl:otg: Modify otg_event to start host drv

Add mechanism to start host driver from inside fsl_otg_even upon each id change interrupt. Signed-off-by: Ramneek Mehresh Reviewed-by: Fleming Andrew-AFLEMING Tested-by: Fleming Andrew-AFLEMING --- drivers/usb/phy/phy-fsl-usb.c | 4 1 file changed, 4 insertions(+) diff --git

[PATCH 4/8][v2]usb:fsl:otg: Signal host drv when host is otg

Set is_otg boolean flag to signal host driver when host is running in context of otg host suspend/resume. Signed-off-by: Ramneek Mehresh --- drivers/usb/phy/phy-fsl-usb.c | 7 ++- include/linux/usb.h | 1 + 2 files changed, 7 insertions(+), 1 deletion(-) diff --git

[PATCH 7/8][v2]usb:fsl:otg: Remove host drv upon otg bring-up

Change have_hcd variable to remove/suspend host driver on completion of otg initialization for otg auto detect. Signed-off-by: Ramneek Mehresh Reviewed-by: Li Yang-R58472 Reviewed-by: Fleming Andrew-AFLEMING Tested-by: Fleming Andrew-AFLEMING --- drivers/usb/host/ehci-fsl.c | 2 ++ 1 file

[PATCH 1/8][v2]usb:fsl:otg: Make fsl otg driver as tristate

Provide option to load fsl otg driver as loadable module. Signed-off-by: Ramneek Mehresh --- drivers/usb/phy/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/usb/phy/Kconfig b/drivers/usb/phy/Kconfig index 869c0cfcad..8a09267 100644 ---

Re: [PATCH 3/3] block: by default, limit maximum discard size to 64MB

On 2015-07-14 17:48, Jens Axboe wrote: On 07/14/2015 02:45 PM, Jens Axboe wrote: On 07/14/2015 02:44 PM, Mike Snitzer wrote: On Tue, Jul 14 2015 at 2:48pm -0400, Jens Axboe wrote: Lots of devices exhibit very high latencies for big discards, hurting reads and writes. By default, limit the

Re: [PATCH 6/6] cputime: Introduce cputime_to_timespec64()/timespec64_to_cputime()

On 15 July 2015 at 18:31, Thomas Gleixner wrote: > On Wed, 15 Jul 2015, Baolin Wang wrote: > >> The cputime_to_timespec() and timespec_to_cputime() functions are >> not year 2038 safe on 32bit systems due to that the struct timepsec >> will overflow in 2038 year. > > And how is this relevant?

Re: [RFC 2/3] arm64: refactor save_stack_trace()

Steve, On 07/15/2015 11:51 AM, Steven Rostedt wrote: On Wed, 15 Jul 2015 09:20:42 +0900 AKASHI Takahiro wrote: On 07/14/2015 10:31 PM, Steven Rostedt wrote: On Tue, 14 Jul 2015 21:47:10 +0900 Jungseok Lee wrote: Is the below example an unexpected result? Entry 17 and 18 are ftrace_call

Re: [PATCH 3/6] security: Introduce security_settime64()

On 15 July 2015 at 18:24, Thomas Gleixner wrote: > On Wed, 15 Jul 2015, Baolin Wang wrote: > >> security_settime() returns a timespec, which is not year 2038 safe > > It returns int, which is year 2038 safe on all systems. Copy and paste > is great, right? > Sorry, will fix that. >> -int

Re: [GIT PULL 0/2] perf/urgent fixes

* Arnaldo Carvalho de Melo wrote: > Hi Ingo, > > Please consider pulling, > > - Arnaldo > > The following changes since commit a833581e372a4adae2319d8dc379493edbc444e9: > > x86, perf: Fix static_key bug in load_mm_cr4() (2015-07-10 10:24:38 +0200) > > are available in the git

Re: [PATCH 20/36] powerpc, thp: remove infrastructure for handling splitting PMDs

"Kirill A. Shutemov" writes: > With new refcounting we don't need to mark PMDs splitting. Let's drop > code to handle this. > > pmdp_splitting_flush() is not needed too: on splitting PMD we will do > pmdp_clear_flush() + set_pte_at(). pmdp_clear_flush() will do IPI as > needed for fast_gup. >

Re: [PATCH 00/36] THP refcounting redesign

"Kirill A. Shutemov" writes: > Hello everybody, > > The THP refcounting has been rebased onto current since-4.1 as requested. > > The goal of patchset is to make refcounting on THP pages cheaper with > simpler semantics and allow the same THP compound page to be mapped with > PMD and PTEs. This

Re: [GIT PULL] x86/ras material for 4.3 queue

* Luck, Tony wrote: > Some of these almost made it into 4.2, then we found a bug and > delayed to fix it. Bug fixes have now been merged back into > the original patch series. > > The following changes since commit d770e558e21961ad6cfdf0ff7df0eb5d7d4f0754: > > Linux 4.2-rc1 (2015-07-05

Re: [PATCH] regulator: core: Fix memory leak in regulator_resolve_supply()

On Wed, Jul 15, 2015 at 10:38:38AM +0200, Javier Martinez Canillas wrote: > On 07/15/2015 10:01 AM, Krzysztof Kozlowski wrote: > > The _regulator_put() reverts more work than create_regulator() did, > > e.g.: module_put and rdev->open_count--. Maybe you need a > > destroy_regulator() function? >

Re: [PULL] vhost: cleanups and fixes

On Wed, Jul 15, 2015 at 01:50:24PM +0300, Michael S. Tsirkin wrote: > The following changes since commit 59a5b0f7bf74f88da6670bcbf924d8cc1e75b1ee: > > virtio-pci: alloc only resources actually used. (2015-06-24 08:15:09 +0200) > > are available in the git repository at: > >

Re: [PATCH perf/core ] [BUGFIX] perf build-test: Add linux/export.h and lib/rbtree.c to MANIFEST

Em Wed, Jul 15, 2015 at 03:07:18PM +0900, Masami Hiramatsu escreveu: > Since linux/export.h and lib/rbtree.c are not listed in MANIFEST, > `make build-test` always fails as below (Note, to get these messages, > I've removed /dev/null redirect in tests/perf-targz-src-pkg); See:

Re: [PATCH v2 3/3] ARM: dts: dra7: Add syscon-pllreset syscon to SATA PHY

Hi Roger, On Tuesday 02 June 2015 02:40 PM, Roger Quadros wrote: > This register is required to be passed to the SATA PHY driver > to workaround errata i783 (SATA Lockup After SATA DPLL Unlock/Relock). > > Signed-off-by: Roger Quadros > Signed-off-by: Sekhar Nori > --- >

Re: perf test LLVM was: Re: [GIT PULL 00/39] perf tools: filtering events using eBPF programs

Em Wed, Jul 15, 2015 at 06:49:40PM +0800, Wangnan (F) escreveu: > On 2015/7/14 23:36, Arnaldo Carvalho de Melo wrote: > >I have the trees cloned and plan to follow these instructions to have this > >test > >passing, to then move on to the next patches, but one request, please change > >the above

Re: [PATCH 0/3] zsmalloc: small compaction improvements

On (07/15/15 09:24), Minchan Kim wrote: > On Wed, Jul 15, 2015 at 09:21:06AM +0900, Sergey Senozhatsky wrote: > > On (07/15/15 01:52), Minchan Kim wrote: > > > > alrighty... again... > > > > > > > > > > > > > > > > /sys/block/zram/compact is a black box. We provide it, we don't > > > > > >

[PATCH 3/5] memcg: get rid of extern for functions in memcontrol.h

From: Michal Hocko Most of the exported functions in this header are not marked extern so change the rest to follow the same style. Reviewed-by: Vladimir Davydov Signed-off-by: Michal Hocko --- include/linux/memcontrol.h | 16 1 file changed, 8 insertions(+), 8 deletions(-)

[PATCH 2/5] memcg: get rid of mem_cgroup_root_css for !CONFIG_MEMCG

The only user is cgwb_bdi_init and that one depends on CONFIG_CGROUP_WRITEBACK which in turn depends on CONFIG_MEMCG so it doesn't make much sense to definte an empty stub for !CONFIG_MEMCG. Moreover ERR_PTR(-EINVAL) is ugly and would lead to runtime crashes if used in unguarded code paths. Better

[PATCH 4/5] memcg: restructure mem_cgroup_can_attach()

From: Tejun Heo Restructure it to lower nesting level and help the planned threadgroup leader iteration changes. This is pure reorganization. Reviewed-by: Vladimir Davydov Signed-off-by: Tejun Heo Cc: Johannes Weiner Acked-by: Michal Hocko --- mm/memcontrol.c | 61

Re: [Intel-gfx] [-next] WARNING at i915_gem_track_fb

On (07/15/15 11:51), Michel Dänzer wrote: > On 14.07.2015 22:41, Sergey Senozhatsky wrote: > > > > sometimes `xset dpms force off' just turns off the panel for a second, > > sometimes -- until I generate a `wakeup' event (key press, etc.) > > FWIW, the former case is because releasing the enter

[PATCH 0/5] expose mem_cgroup + cleanups

Hi, this is just the cleanup portion of the series posted previously here: http://marc.info/?l=linux-kernel=143635871831843. I am still thinking about how to move on regarding mm_struct::owner but this is more tricky than originally anticipated. The cleanup still makes some sense IMO. I have

[PATCH 5/5] memcg, tcp_kmem: check for cg_proto in sock_update_memcg

From: Michal Hocko sk_prot->proto_cgroup is allowed to return NULL but sock_update_memcg doesn't check for NULL. The function relies on the mem_cgroup_is_root check because we shouldn't get NULL otherwise because mem_cgroup_from_task will always return !NULL. All other callers are checking for

[PATCH 1/5] memcg: export struct mem_cgroup

From: Michal Hocko mem_cgroup structure is defined in mm/memcontrol.c currently which means that the code outside of this file has to use external API even for trivial access stuff. This patch exports mm_struct with its dependencies and makes some of the exported functions inlines. This even

Re: [Intel-gfx] [-next] WARNING at i915_gem_track_fb

On (07/14/15 17:11), Daniel Vetter wrote: > Have you forwarded to a more recent -nightly? I just merged a patch which > might have fixed this ... > Hello, yep, I use the most recent -next usually (update it everyday), when it boots. I can't reproduce the problem so far, hopefully the commit you

Re: [PATCH v4 1/2] capabilities: Ambient capabilities

On Tue, 14 Jul 2015, Andy Lutomirski wrote: > = The proposed change = > > This patch adds a fifth capability mask called the ambient mask > (pA). pA does what most people expect pI to do. > This looks good, and I think it will lead to better overall security because people will find

[PATCH] arm64: Split out platform options to separate Kconfig

Let's move out the platform Kconfig entries to a separate file, since these changes usually get moved through arm-soc instead of the arm64 arch tree, and this will lead to fewer conflicts Signed-off-by: Olof Johansson --- Will, Catalin, I'll merge this through arm-soc if I get your acks.

Re: perf test LLVM was: Re: [GIT PULL 00/39] perf tools: filtering events using eBPF programs

On 2015/7/14 23:36, Arnaldo Carvalho de Melo wrote: Em Thu, Jul 09, 2015 at 12:35:03PM +, Wang Nan escreveu: Hi Arnaldo, The following changes since commit 3381a29cbec5447086c0f726ee9a88c02e60becc: bpf tools: Collect map definitions from 'maps' section (2015-07-07 13:41:45 -0300)

Re: 4.2-rc2: early boot memory corruption from FPU rework

* Dave Hansen wrote: > On 05/05/2015 10:49 AM, Ingo Molnar wrote: > > @@ -574,12 +573,10 @@ static void setup_init_fpu_buf(void) > > on_boot_cpu = 0; > > > > /* > > -* Setup init_xstate_buf to represent the init state of > > +* Setup init_xstate_ctx to represent the init state

[PATCH 3.16.y-ckt 001/185] ARM: clk-imx6q: refine sata's parent

3.16.7-ckt15 -stable review patch. If anyone has any objections, please let me know. -- From: Sebastien Szymanski commit da946aeaeadcd24ff0cda9984c6fb8ed2bfd462a upstream. According to IMX6D/Q RM, table 18-3, sata clock's parent is ahb, not ipg. Signed-off-by: Sebastien

[PATCH 3.16.y-ckt 003/185] nfs: take extra reference to fl->fl_file when running a setlk

3.16.7-ckt15 -stable review patch. If anyone has any objections, please let me know. -- From: Jeff Layton commit feaff8e5b2cfc3eae02cf65db7a400b0b9ffc596 upstream. We had a report of a crash while stress testing the NFS client: BUG: unable to handle kernel NULL pointer

[PATCH 3.16.y-ckt 004/185] bridge: fix multicast router rlist endless loop

3.16.7-ckt15 -stable review patch. If anyone has any objections, please let me know. -- From: Nikolay Aleksandrov commit 1a040eaca1a22f8da8285ceda6b5e4a2cb704867 upstream. Since the addition of sysfs multicast router support if one set multicast_router to "2" more than once,

[PATCH 3.16.y-ckt 002/185] KVM: nSVM: Check for NRIPS support before updating control field

3.16.7-ckt15 -stable review patch. If anyone has any objections, please let me know. -- From: Bandan Das commit f104765b4f81fd74d69e0eb161e89096deade2db upstream. If hardware doesn't support DecodeAssist - a feature that provides more information about the intercept in the

[PATCH updated 16/39] perf tests: Add LLVM test for eBPF on-the-fly compiling

Previous patches introduce llvm__compile_bpf() to compile source file to eBPF object. This patch adds testcase to test it. It also tests libbpf by opening generated object after applying next patch which introduces HAVE_LIBBPF_SUPPORT option. Since llvm__compile_bpf() prints long messages which

Re: [PATCH 0/3] Remove ext3 filesystem driver

On 07/15/2015 01:26 PM, Jan Kara wrote: > Hello, > > so I have created this patch set which removes ext3 driver (and some > related support > code) from the kernel. See changelog of patch 2/3 for more details. If noone > objects, > I will queue the series in my tree for the next merge

Re: [RFC PATCH v2] memory-barriers: remove smp_mb__after_unlock_lock()

Hi Paul, On Wed, Jul 15, 2015 at 02:38:20AM +0100, Paul E. McKenney wrote: > On Tue, Jul 14, 2015 at 12:31:44PM -0700, Paul E. McKenney wrote: > > On Tue, Jul 14, 2015 at 03:12:16PM +0100, Will Deacon wrote: > > > On Tue, Jul 14, 2015 at 03:00:14PM +0100, Paul E. McKenney wrote: > > > > On Tue,

[PULL] vhost: cleanups and fixes

The following changes since commit 59a5b0f7bf74f88da6670bcbf924d8cc1e75b1ee: virtio-pci: alloc only resources actually used. (2015-06-24 08:15:09 +0200) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git tags/for_linus for you to fetch

Re: [PATCH 1/3] panic: Disable crash_kexec_post_notifiers if kdump is not available

(2015/07/15 0:40), Vivek Goyal wrote: > On Tue, Jul 14, 2015 at 03:34:30PM +, dwal...@fifo99.com wrote: >> On Tue, Jul 14, 2015 at 11:02:08AM -0400, Vivek Goyal wrote: >>> On Tue, Jul 14, 2015 at 01:59:19PM +, dwal...@fifo99.com wrote: On Mon, Jul 13, 2015 at 08:19:45PM -0500, Eric W.

Re: 4.2-rc2: hitting "file-max limit 8192 reached"

On Tue, Jul 14, 2015 at 08:54:11AM -0700, Dave Hansen wrote: > My laptop has been behaving strangely with 4.2-rc2. Once I log in to my > X session, I start getting all kinds of strange errors from applications > and see this in my dmesg: > > VFS: file-max limit 8192 reached > > Could this

Re: [RFC PATCH v2] memory-barriers: remove smp_mb__after_unlock_lock()

Hi Michael, On Wed, Jul 15, 2015 at 04:06:18AM +0100, Michael Ellerman wrote: > On Tue, 2015-07-14 at 08:31 +1000, Benjamin Herrenschmidt wrote: > > On Mon, 2015-07-13 at 13:15 +0100, Will Deacon wrote: > > > This didn't go anywhere last time I posted it, but here it is again. > > > I'd really

RE: [PATCH] dmaengine: fsl-edma: add PM suspend/resume support

Hi Arnd, Thanks for your review. And can you give me more information? In my opinion, The fsl_edma_pm_state will just be used when CONFIG_PM support. So why not use the #ifdefs to remove the unnecessary code? Since the PM will not be selected in many use cases. Thanks. Best Regards, Yuan Yao

Re: [PATCH] e1000e: Move e1000e_disable_aspm_locked() inside CONFIG_PM

On Tue, 2015-07-14 at 13:54 +1000, Michael Ellerman wrote: > e1000e_disable_aspm_locked() is only used in __e1000_resume() which is > inside CONFIG_PM. So when CONFIG_PM=n we get a "defined but not used" > warning for e1000e_disable_aspm_locked(). > > Move it inside the existing CONFIG_PM block

Re: [PATCH 6/6] cputime: Introduce cputime_to_timespec64()/timespec64_to_cputime()

On Wed, 15 Jul 2015, Baolin Wang wrote: > The cputime_to_timespec() and timespec_to_cputime() functions are > not year 2038 safe on 32bit systems due to that the struct timepsec > will overflow in 2038 year. And how is this relevant? cputime is not based on wall clock time at all. So what has

[PATCH] drm: Fix warning with make xmldocs caused by drm_irq.c

This patch fix following warnings. Warning(.//drivers/gpu/drm/drm_irq.c:1279): No description found for parameter drm_crtc' Warning(.//drivers/gpu/drm/drm_irq.c:1279): Excess function parameter 'crtc' description in 'drm_crtc_vblank_reset' Signed-off-by: Masanari Iida ---

[PATCH 0/3] Remove ext3 filesystem driver

Hello, so I have created this patch set which removes ext3 driver (and some related support code) from the kernel. See changelog of patch 2/3 for more details. If noone objects, I will queue the series in my tree for the next merge window. Jens, are you OK with me merging patch 3/3 or do

[PATCH 1/3] doc: Update doc about journalling layer

Documentation of journalling layer in Documentation/DocBook/filesystems.tmpl speaks about JBD layer. Since that is going away, update the documentation to speak about JBD2. Also update the parts that have changed since someone last touched the document and remove some parts which are just

[PATCH 3/3] block: Remove forced page bouncing under IO

From: Jan Kara JBD layer wrote back data buffers without setting PageWriteback bit. Thus standard mechanism for guaranteeing stable pages under IO did not work. Since JBD is gone now and there is no other user of the functionality, just remove it. CC: Jens Axboe Signed-off-by: Jan Kara ---

Re: [PATCH 3/6] security: Introduce security_settime64()

On Wed, 15 Jul 2015, Baolin Wang wrote: > security_settime() returns a timespec, which is not year 2038 safe It returns int, which is year 2038 safe on all systems. Copy and paste is great, right? > -int security_settime(const struct timespec *ts, const struct timezone *tz); > +int

Re: [PATCH v7 0/4] Compile-time stack validation

* Josh Poimboeuf wrote: > On Tue, Jul 14, 2015 at 12:14:06PM -0500, Josh Poimboeuf wrote: > > Posting a listing of reported warnings in a reply to this email. > > These are the reported stackvalidate warnings on tip/master with my > Fedora-based > config. There were 1399 warnings in 26 .c

[PATCH 3.16.y-ckt 006/185] sctp: fix ASCONF list handling

3.16.7-ckt15 -stable review patch. If anyone has any objections, please let me know. -- From: Marcelo Ricardo Leitner commit 2d45a02d0166caf2627fe91897c6ffc3b19514c4 upstream. ->auto_asconf_splist is per namespace and mangled by functions like sctp_setsockopt_auto_asconf()

[PATCH 3.16.y-ckt 013/185] sctp: Fix race between OOTB responce and route removal

3.16.7-ckt15 -stable review patch. If anyone has any objections, please let me know. -- From: Alexander Sverdlin commit 29c4afc4e98f4dc0ea9df22c631841f9c220b944 upstream. There is NULL pointer dereference possible during statistics update if the route used for OOTB responce

[PATCH 3.16.y-ckt 010/185] neigh: do not modify unlinked entries

3.16.7-ckt15 -stable review patch. If anyone has any objections, please let me know. -- From: Julian Anastasov commit 2c51a97f76d20ebf1f50fef908b986cb051fdff9 upstream. The lockless lookups can return entry that is unlinked. Sometimes they get reference before last

[PATCH 3.16.y-ckt 005/185] net: don't wait for order-3 page allocation

3.16.7-ckt15 -stable review patch. If anyone has any objections, please let me know. -- From: Shaohua Li commit fb05e7a89f500cfc06ae277bdc911b281928995d upstream. We saw excessive direct memory compaction triggered by skb_page_frag_refill. This causes performance issues and

Re: [PATCH v4 3/6] cpufreq: powernv: Register for OCC related opal_message notification

Hi Joel, On 07/15/2015 11:47 AM, Joel Stanley wrote: > Hello, > > On Mon, 2015-07-13 at 19:39 +0530, Shilpasri G Bhat wrote: >> diff --git a/drivers/cpufreq/powernv-cpufreq.c >> b/drivers/cpufreq/powernv-cpufreq.c >> index d0c18c9..1f59958 100644 >> --- a/drivers/cpufreq/powernv-cpufreq.c >>

[PATCH 3.16.y-ckt 012/185] net: phy: fix phy link up when limiting speed via device tree

3.16.7-ckt15 -stable review patch. If anyone has any objections, please let me know. -- From: Mugunthan V N commit eb686231fce3770299760f24fdcf5ad041f44153 upstream. When limiting phy link speed using "max-speed" to 100mbps or less on a giga bit phy, phy never completes auto

[PATCH 3.16.y-ckt 007/185] bridge: fix br_stp_set_bridge_priority race conditions

3.16.7-ckt15 -stable review patch. If anyone has any objections, please let me know. -- From: Nikolay Aleksandrov commit 2dab80a8b486f0a69daca6859519e05781d9 upstream. After the ->set() spinlocks were removed br_stp_set_bridge_priority was left running without any

[PATCH 3.16.y-ckt 017/185] [media] af9013: Don't accept invalid bandwidth

3.16.7-ckt15 -stable review patch. If anyone has any objections, please let me know. -- From: Mauro Carvalho Chehab commit d7b76c91f471413de9ded837bddeca2164786571 upstream. If userspace sends an invalid bandwidth, it should either return EINVAL or switch to auto mode. This

[PATCH 3.16.y-ckt 015/185] [media] s5h1420: fix a buffer overflow when checking userspace params

3.16.7-ckt15 -stable review patch. If anyone has any objections, please let me know. -- From: Mauro Carvalho Chehab commit 12f4543f5d6811f864e6c4952eb27253c7466c02 upstream. The maximum size for a DiSEqC command is 6, according to the userspace API. However, the code allows

[PATCH 3.16.y-ckt 016/185] [media] cx24116: fix a buffer overflow when checking userspace params

3.16.7-ckt15 -stable review patch. If anyone has any objections, please let me know. -- From: Mauro Carvalho Chehab commit 1fa2337a315a2448c5434f41e00d56b01a22283c upstream. The maximum size for a DiSEqC command is 6, according to the userspace API. However, the code allows

[PATCH 3.16.y-ckt 022/185] leds / PM: fix hibernation on arm when gpio-led used with CPU led trigger

3.16.7-ckt15 -stable review patch. If anyone has any objections, please let me know. -- From: Grygorii Strashko commit 084609bf727981c7a2e6e69aefe0052c9d793300 upstream. Setting a dev_pm_ops suspend/resume pair of callbacks but not a set of hibernation callbacks means those

[PATCH 3.16.y-ckt 011/185] tcp: Do not call tcp_fastopen_reset_cipher from interrupt context

3.16.7-ckt15 -stable review patch. If anyone has any objections, please let me know. -- From: Christoph Paasch commit dfea2aa654243f70dc53b8648d0bbdeec55a7df1 upstream. tcp_fastopen_reset_cipher really cannot be called from interrupt context. It allocates the

[PATCH/Resend] namei: Fix warning while make xmldocs caused by namei.c

This patch fix following warnings. Warning(.//fs/namei.c:2422): No description found for parameter 'nd' Warning(.//fs/namei.c:2422): Excess function parameter 'nameidata' description in 'path_mountpoint' Signed-off-by: Masanari Iida --- fs/namei.c | 2 +- 1 file changed, 1 insertion(+), 1

[PATCH 3.16.y-ckt 021/185] intel_pstate: set BYT MSR with wrmsrl_on_cpu()

3.16.7-ckt15 -stable review patch. If anyone has any objections, please let me know. -- From: Joe Konno commit 0dd23f94251f49da99a6cbfb22418b2d757d77d6 upstream. Commit 007bea098b86 (intel_pstate: Add setting voltage value for baytrail P states.) introduced byt_set_pstate()

[PATCH 3.16.y-ckt 018/185] [media] cx24117: fix a buffer overflow when checking userspace params

3.16.7-ckt15 -stable review patch. If anyone has any objections, please let me know. -- From: Mauro Carvalho Chehab commit 82e3b88b679049f043fe9b03991d6d66fc0a43c8 upstream. The maximum size for a DiSEqC command is 6, according to the userspace API. However, the code allows

[PATCH 3.16.y-ckt 009/185] packet: avoid out of bounds read in round robin fanout

3.16.7-ckt15 -stable review patch. If anyone has any objections, please let me know. -- From: Willem de Bruijn commit 468479e6043c84f5a65299cc07cb08a22a28c2b1 upstream. PACKET_FANOUT_LB computes f->rr_cur such that it is modulo f->num_members. It returns the old value

[PATCH 3.16.y-ckt 033/185] w1_therm reference count family data

3.16.7-ckt15 -stable review patch. If anyone has any objections, please let me know. -- From: David Fries commit f7134eea05b2fb4a2c0935f8a540539fff01f3eb upstream. A temperature conversion can take 750 ms and when possible the w1_therm slave driver drops the bus_mutex to

[PATCH 3.16.y-ckt 032/185] KVM: mips: use id_to_memslot correctly

3.16.7-ckt15 -stable review patch. If anyone has any objections, please let me know. -- From: Paolo Bonzini commit 69a1220060c1523fd0515216eaa29e22f133b894 upstream. The argument to KVM_GET_DIRTY_LOG is a memslot id; it may not match the position in the memslots array, which

[PATCH 3.16.y-ckt 025/185] genirq: devres: Fix testing return value of request_any_context_irq()

3.16.7-ckt15 -stable review patch. If anyone has any objections, please let me know. -- From: Axel Lin commit 63781394c540dd9e666a6b21d70b64dd52bce76e upstream. request_any_context_irq() returns a negative value on failure. It returns either IRQC_IS_HARDIRQ or IRQC_IS_NESTED

[PATCH 3.16.y-ckt 024/185] Revert "crypto: talitos - convert to use be16_add_cpu()"

3.16.7-ckt15 -stable review patch. If anyone has any objections, please let me know. -- From: Horia Geant? commit 69d9cd8c592f1abce820dbce7181bbbf6812cfbd upstream. This reverts commit 7291a932c6e27d9768e374e9d648086636daf61c. The conversion to be16_add_cpu() is incorrect

[PATCH 3.16.y-ckt 028/185] mnt: Refactor the logic for mounting sysfs and proc in a user namespace

3.16.7-ckt15 -stable review patch. If anyone has any objections, please let me know. -- From: "Eric W. Biederman" commit 1b852bceb0d111e510d1a15826ecc4a19358d512 upstream. Fresh mounts of proc and sysfs are a very special case that works very much like a bind mount.

[PATCH 3.16.y-ckt 034/185] drm/radeon: take the mode_config mutex when dealing with hpds (v2)

3.16.7-ckt15 -stable review patch. If anyone has any objections, please let me know. -- From: Alex Deucher commit 39fa10f7e21574a70cecf1fed0f9b36535aa68a0 upstream. Since we are messing with state in the worker. v2: drop the changes in the mst worker Signed-off-by: Alex

[PATCH 3.16.y-ckt 029/185] ASoC: wm8955: Fix setting wrong register for WM8955_K_8_0_MASK bits

3.16.7-ckt15 -stable review patch. If anyone has any objections, please let me know. -- From: Axel Lin commit 12c350050538c7dc779c083b7342bfd20f74949c upstream. WM8955_K_8_0_MASK bits is controlled by WM8955_PLL_CONTROL_3 rather than WM8955_PLL_CONTROL_2. Signed-off-by:

[PATCH 3.16.y-ckt 026/185] ASoC: wm8737: Fixup setting VMID Impedance control register

3.16.7-ckt15 -stable review patch. If anyone has any objections, please let me know. -- From: Axel Lin commit 14ba3ec1de043260cecd9e828ea2e3a0ad302893 upstream. According to the datasheet: R10 (0Ah) VMID Impedance Control BIT 3:2 VMIDSEL DEFAULT 00 DESCRIPTION: VMID

[PATCH 3.16.y-ckt 023/185] crypto: talitos - avoid memleak in talitos_alg_alloc()

3.16.7-ckt15 -stable review patch. If anyone has any objections, please let me know. -- From: Horia Geant? commit 5fa7dadc898567ce14d6d6d427e7bd8ce6eb5d39 upstream. Fixes: 1d11911a8c57 ("crypto: talitos - fix warning: 'alg' may be used uninitialized in this function")

[PATCH 3.16.y-ckt 020/185] mtd: fix: avoid race condition when accessing mtd->usecount

3.16.7-ckt15 -stable review patch. If anyone has any objections, please let me know. -- From: Brian Norris commit 073db4a51ee43ccb827f54a4261c0583b028d5ab upstream. On A MIPS 32-cores machine a BUG_ON was triggered because some acesses to mtd->usecount were done without

[PATCH 3.16.y-ckt 019/185] spi: fix race freeing dummy_tx/rx before it is unmapped

3.16.7-ckt15 -stable review patch. If anyone has any objections, please let me know. -- From: Martin Sperl commit 8e76ef88f607174082023f50b87fe12dcdbe5db5 upstream. Fix a race (with some kernel configurations) where a queued master->pump_messages runs and frees dummy_tx/rx

[PATCH 3.16.y-ckt 030/185] scsi_transport_srp: Introduce srp_wait_for_queuecommand()

3.16.7-ckt15 -stable review patch. If anyone has any objections, please let me know. -- From: Bart Van Assche commit be34c62ddf39d1931780b07a6f4241393e4ba2ee upstream. Introduce the helper function srp_wait_for_queuecommand(). Move the definition of scsi_request_fn_active().

[PATCH 3.16.y-ckt 048/185] mnt: Modify fs_fully_visible to deal with locked ro nodev and atime

3.16.7-ckt15 -stable review patch. If anyone has any objections, please let me know. -- From: "Eric W. Biederman" commit 8c6cf9cc829fcd0b179b59f7fe288941d0e31108 upstream. Ignore an existing mount if the locked readonly, nodev or atime attributes are less permissive than the

[PATCH 3.16.y-ckt 036/185] rcu: Correctly handle non-empty Tiny RCU callback list with none ready

3.16.7-ckt15 -stable review patch. If anyone has any objections, please let me know. -- From: "Paul E. McKenney" commit 6e91f8cb138625be96070b778d9ba71ce520ea7e upstream. If, at the time __rcu_process_callbacks() is invoked, there are callbacks in Tiny RCU's callback list,

[PATCH 3.16.y-ckt 040/185] usb: core: Fix USB 3.0 devices lost in NOTATTACHED state after a hub port reset

3.16.7-ckt15 -stable review patch. If anyone has any objections, please let me know. -- From: Robert Schlabbach commit fb6d1f7df5d25299fd7b3e84b72b8851d3634764 upstream. Fix USB 3.0 devices lost in NOTATTACHED state after a hub port reset. Dissolve the function

[PATCH 3.16.y-ckt 041/185] staging: vt6655: device_rx_srv check sk_buff is NULL

3.16.7-ckt15 -stable review patch. If anyone has any objections, please let me know. -- From: Malcolm Priestley commit b5eeed8cb6097c8ea660b6598d36fdbb94065a22 upstream. There is a small chance that pRD->pRDInfo->skb could go NULL while the interrupt is processing. Put NULL

[PATCH 3.16.y-ckt 039/185] staging: rtl8712: prevent buffer overrun in recvbuf2recvframe

3.16.7-ckt15 -stable review patch. If anyone has any objections, please let me know. -- From: Haggai Eran commit cab462140f8a183e3cca0b51c8b59ef715cb6148 upstream. With an RTL8191SU USB adaptor, sometimes the hints for a fragmented packet are set, but the packet length is

[PATCH 3.16.y-ckt 038/185] usb: dwc3: gadget: don't clear EP_BUSY too early

3.16.7-ckt15 -stable review patch. If anyone has any objections, please let me know. -- From: Felipe Balbi commit e18b7975c885bc3a938b9a76daf32957ea0235fa upstream. In case of non-Isochronous transfers, we don't want to clear DWC3_EP_BUSY flag until XferComplete event.

[PATCH 3.16.y-ckt 045/185] SUNRPC: Fix a memory leak in the backchannel code

3.16.7-ckt15 -stable review patch. If anyone has any objections, please let me know. -- From: Trond Myklebust commit 88de6af24f2b48b06c514d3c3d0a8f22fafe30bd upstream. req->rq_private_buf isn't initialised when xprt_setup_backchannel calls xprt_free_allocation. Fixes:

[PATCH 3.16.y-ckt 035/185] usb: dwc3: gadget: return error if command sent to DGCMD register fails

3.16.7-ckt15 -stable review patch. If anyone has any objections, please let me know. -- From: Subbaraya Sundeep Bhatta commit 891b1dc022955d36cf4c0f42d383226a930db7ed upstream. We need to return error to caller if command is not sent to controller succesfully.

[PATCH 3.16.y-ckt 042/185] fixing infinite OPEN loop in 4.0 stateid recovery

3.16.7-ckt15 -stable review patch. If anyone has any objections, please let me know. -- From: Olga Kornievskaia commit e8d975e73e5fa05f983fbf2723120edcf68e0b38 upstream. Problem: When an operation like WRITE receives a BAD_STATEID, even though recovery code clears the

[PATCH 3.16.y-ckt 037/185] ASoC: arizona: Fix noise generator gain TLV

3.16.7-ckt15 -stable review patch. If anyone has any objections, please let me know. -- From: Richard Fitzgerald commit 15575ed544910464715df5c45a44b9732e415b93 upstream. The Arizona codec drivers had an incorrect dB scaling for the noise generator gain that started at 0dB

<    4   5   6   7   8   9   10   11   12   13   >