On 2018-04-12 12:19, Miquel Raynal wrote:
Hi Abhishek,
On Thu, 12 Apr 2018 12:03:58 +0530, Abhishek Sahu
wrote:
On 2018-04-10 14:29, Miquel Raynal wrote:
> Hi Abhishek,
> > On Wed, 4 Apr 2018 18:12:19 +0530, Abhishek Sahu
> wrote:
> >> The NAND flash controller generates ECC uncorrectable e
Han,
On 15.03.2018 16:39, Stefan Agner wrote:
> On March 15, 2018 4:36:20 PM GMT+01:00, Boris Brezillon
> wrote:
>>Hi,
>>
>>On Sun, 4 Mar 2018 21:06:01 +0100
>>Stefan Agner wrote:
>>
>>> Add support for specified ECC strength/size using device tree
>>> properties nand-ecc-strength/nand-ecc-step
Hi Geert,
On Wed, Apr 11, 2018 at 10:39:19AM +0200, Geert Uytterhoeven wrote:
> Hi Simon,
>
> On Wed, Apr 11, 2018 at 10:22 AM, Simon Horman wrote:
> > On Tue, Apr 10, 2018 at 05:53:47PM +0200, Geert Uytterhoeven wrote:
...
> >> @@ -217,6 +236,9 @@ static int vfio_platform_call_reset(struct
>
On 2018-04-10 14:42, Miquel Raynal wrote:
Hi Abhishek,
On Wed, 4 Apr 2018 18:12:20 +0530, Abhishek Sahu
wrote:
parse_read_errors can be called with only oob buf also in which
case data_buf will be NULL. If data_buf is NULL, then don’t
treat this page as completely erased in case of ECC unco
On 04/11/2018 03:56 PM, Roman Gushchin wrote:
> On Wed, Apr 11, 2018 at 03:16:08PM +0200, Vlastimil Babka wrote:
>> [+CC linux-api]
>>
>> On 03/05/2018 02:37 PM, Roman Gushchin wrote:
>>> This patch introduces a concept of indirectly reclaimable memory
>>> and adds the corresponding memory counter
Hi Abhishek,
On Thu, 12 Apr 2018 12:03:58 +0530, Abhishek Sahu
wrote:
> On 2018-04-10 14:29, Miquel Raynal wrote:
> > Hi Abhishek,
> > > On Wed, 4 Apr 2018 18:12:19 +0530, Abhishek Sahu
> > wrote:
> > >> The NAND flash controller generates ECC uncorrectable error
> >> first in case of
The STMicroelectronics STM32 Inter-Processor Communication Controller
(IPCC) is used for communicating data between two processors.
It provides a non blocking signaling mechanism to post and retrieve
communication data in an atomic way.
Signed-off-by: Fabien Dessenne
Signed-off-by: Ludovic Barre
Add a binding for the STMicroelectronics STM32 IPCC block exposing a
mailbox mechanism between two processors.
Signed-off-by: Fabien Dessenne
Signed-off-by: Ludovic Barre
Reviewed-by: Rob Herring
---
.../devicetree/bindings/mailbox/stm32-ipcc.txt | 47 ++
1 file changed
The STMicroelectronics STM32 Inter-Processor Communication Controller
(IPCC) is used for communicating data between two processors.
It provides a non blocking signaling mechanism to post and retrieve
communication data in an atomic way.
Changes since v4:
- add Rob's 'Reviewed-by' in dt bindings
C
On Thu, 2018-04-12 at 08:22 +0200, Julia Lawall wrote:
> On Wed, 11 Apr 2018, Joe Perches wrote:
> > On Wed, 2018-04-11 at 09:29 -0700, Andrew Morton wrote:
> > > We already have some 500 bools-in-structs
> >
> > I got at least triple that only in include/
> > so I expect there are at probably an
Add the Fixes, CC stable tags.
---8<---
During freeing of the internal buffers used by the DRBG, set the pointer
to NULL. It is possible that the context with the freed buffers is
reused. In case of an error during initialization where the pointers
do not yet point to allocated memory, the NULL v
Am Donnerstag, 29. März 2018, 22:45:59 CEST schrieb Richard Weinberger:
> While the function will never returns, gcc will warns.
> Add a return statement to make gcc happy.
> Before f44f1e7da7c8 we never noticed because gcc knows that longjmp does
> not return.
>
> arch/um/os-Linux/skas/process.c:
Am Donnerstag, 5. April 2018, 23:21:02 CEST schrieb Hernán Gonzalez:
> This option restores the DEBUG_BUGVERBOSE functionality as it was
> previous to commit 9a93848fe787 ("x86/debug: Implement __WARN() using
> UD0").
>
> Signed-off-by: Hernán Gonzalez
Applied.
Thanks,
//richard
On 2018-04-10 14:29, Miquel Raynal wrote:
Hi Abhishek,
On Wed, 4 Apr 2018 18:12:19 +0530, Abhishek Sahu
wrote:
The NAND flash controller generates ECC uncorrectable error
first in case of completely erased page. Currently driver
applies the erased page detection logic for other operation
err
On Wed, Apr 11, 2018 at 01:03:59PM +0100, Robin Murphy wrote:
> On 10/04/18 21:59, Sinan Kaya wrote:
>> Code is expecing to observe the same number of buffers returned from
>> dma_map_sg() function compared to sg_alloc_table_from_pages(). This
>> doesn't hold true universally especially for systems
On 2018-04-12 13:13, Vivek Gautam wrote:
On 4/12/2018 6:27 AM, c...@codeaurora.org wrote:
On 2018-04-09 19:28, Vivek Gautam wrote:
Hi Can,
On 3/27/2018 12:48 PM, Can Guo wrote:
Add UFS PHY support to make SDM845 UFS work with common PHY
framework.
Signed-off-by: Can Guo
---
drivers/phy/
On Wed, 11 Apr 2018, Joe Perches wrote:
> (Adding Julia Lawall)
>
> On Wed, 2018-04-11 at 09:29 -0700, Andrew Morton wrote:
> > We already have some 500 bools-in-structs
>
> I got at least triple that only in include/
> so I expect there are at probably an order
> of magnitude more than 500 in t
On Fri, Apr 06, 2018 at 11:12:42AM -0700, Dmitry Torokhov wrote:
> UI_SET_LEDBIT ioctl() causes the following KASAN splat when used with
> led > LED_CHARGING:
>
> [ 1274.663418] BUG: KASAN: slab-out-of-bounds in
> input_leds_connect+0x611/0x730 [input_leds]
> [ 1274.663426] Write of size 8 at add
On Wed 11-04-18 17:09:25, Naoya Horiguchi wrote:
> Hi everyone,
>
> I wrote patches introducing separate vm event counters for hugepage migration
> (both for hugetlb and thp.)
> Hugepage migration is different from normal page migration in event frequency
> and/or how likely it succeeds, so mainta
Hi James，
thanks for this mail.
On 2018/4/10 22:15, James Morse wrote:
> Hi Dongjiu Geng,
>
> On 09/04/18 22:36, Dongjiu Geng wrote:
>> 1. Detect whether KVM can set set guest SError syndrome
>> 2. Support to Set VSESR_EL2 and inject SError by user space.
>> 3. Support live migration to keep S
On Wed, Apr 11, 2018 at 10:38:07PM -0700, Christoph Hellwig wrote:
> On Thu, Apr 05, 2018 at 09:29:42PM +0100, David Howells wrote:
> > Fix warnings raised by checker, including:
> >
> > (*) Warnings raised by unequal comparison for the purposes of sorting,
> > where the endianness doesn't m
On Wed, Apr 11, 2018 at 09:28:54AM +0200, Takashi Iwai wrote:
> > But we should try a GFP_DMA32 allocation first, so this is a bit
> > surprising.
>
> Hm, do we really try that?
> Through a quick glance, dma_alloc_coherent_gfp_flags() gives GFP_DMA32
> only when coherent mask <= DMA_BIT_MASK(32);
The following changes since commit b284d4d5a6785f8cd07eda2646a95782373cd01e:
Merge tag 'ceph-for-4.17-rc1' of git://github.com/ceph/ceph-client
(2018-04-10 12:25:30 -0700)
are available in the Git repository at:
git://git.infradead.org/users/hch/dma-mapping.git tags/dma-mapping-4.17-2
for
From: Fengguang Wu
Use drm_*_get() and drm_*_put() helpers instead of drm_*_reference() and
drm_*_unreference() helpers.
Generated by: scripts/coccinelle/api/drm-get-put.cocci
Fixes: 6784ac15bc68 ("drm: Add ASPEED GFX driver")
Signed-off-by: Fengguang Wu
Signed-off-by: Julia Lawall
---
tre
From: Fengguang Wu
Remove unneeded semicolon.
Generated by: scripts/coccinelle/misc/semicolon.cocci
Fixes: 6784ac15bc68 ("drm: Add ASPEED GFX driver")
Signed-off-by: Fengguang Wu
Signed-off-by: Julia Lawall
---
aspeed_gfx_drv.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
---
On 2018-04-02 18:00, Vivek Gautam wrote:
Hi Can,
On 3/2/2018 1:48 PM, Can Guo wrote:
From: Venkat Gopalakrishnan
Qcom ufs controller v3.1.0 supports 2 lanes, add support
to configure 2 lanes during phy initialization.
Signed-off-by: Venkat Gopalakrishnan
Signed-off-by: Subhash Jadavani
Si
On Thu, Apr 05, 2018 at 09:29:42PM +0100, David Howells wrote:
> Fix warnings raised by checker, including:
>
> (*) Warnings raised by unequal comparison for the purposes of sorting,
> where the endianness doesn't matter:
>
> fs/afs/addr_list.c:246:21: warning: restricted __be16 degrades to
Hi, Peng!
On 04/12/2018 05:21 AM, Peng Fan wrote:
Hi Oleksandr,
Just have a question, is this drm/xen-front stuff orthogonal to xen shared
coprocessor framework for gpu, or are they exclusive?
They are orthogonal
Thanks,
Peng.
On 4/12/2018 6:27 AM, c...@codeaurora.org wrote:
On 2018-04-09 19:28, Vivek Gautam wrote:
Hi Can,
On 3/27/2018 12:48 PM, Can Guo wrote:
Add UFS PHY support to make SDM845 UFS work with common PHY framework.
Signed-off-by: Can Guo
---
drivers/phy/qualcomm/phy-qcom-qmp.c | 130
++
On 12 April 2018 12:05:03 AM IST, Greg Kroah-Hartman
wrote:
>This is the start of the stable review cycle for the 3.18.105 release.
>There are 121 patches in this series, all will be posted as a response
>to this one. If anyone has any issues with these being applied, please
>let me know.
>
>Res
Hi, Linus,
On 三, 2018-04-11 at 17:01 -0700, Linus Torvalds wrote:
> On Wed, Apr 11, 2018 at 1:41 AM, Zhang Rui
> wrote:
> >
> >
> > Please pull from
> > git://git.kernel.org/pub/scm/linux/kernel/git/rzhang/linux.git
> > next
> Pulled, and then immediately unpulled again.
>
> The code causes
Dear James,
Thanks for this mail and sorry for my late response.
2018-02-16 1:55 GMT+08:00 James Morse :
> Hi gengdongjiu, liu jun
>
> On 05/02/18 11:24, gengdongjiu wrote:
[]
>>
>>> Is the emulated SError routed following the routing rules for HCR_EL2.{AMO,
>>> TGE}?
>>
>> Yes, it is
2018-04-12 11:31 GMT+09:00 Masahiro Yamada :
> The property of the legacy mode for the eMMC PHY turned out to
> be worng. Some eMMC devices are unstable due to the set-up/hold
> timing violation. Correct the delay value.
Reminder for myself:
Fix a type worng -> wrong
--
Best Regards
Masah
Hi Jia-Ju,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on ide/master]
[also build test ERROR on v4.16 next-20180411]
[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
From: Dave Gerlach
Some hwmods will not properly assert signals to the PRCM after a
context loss if no driver is present which leads to issues with suspend.
This can be caused by the SYSCONFIG register not being programmed
correctly by default or a softreset being needed before the module will
id
From: Dave Gerlach
After an RTC+DDR cycle we lose sram context so emif pm functions present
in sram are lost. We can check if the first byte of the original
code in DDR contains the same first byte as the code in sram, and if
they do not match we know we have lost context and must recopy the
func
From: Russ Dill
The powerdomain control registers are stored in the WKUP powerdomain on
AM33XX/AM43XX, which is lost on RTC-only suspend and also hibernate. This
adds context save and restore functions for those registers.
Sometimes the powerdomain state does not need to change,
perhaps we only n
From: Russ Dill
This adds a pair of context save/restore functions to save/restore the
state of a set of pinctrl registers. This simplifies some of the AM33XX
PM code as some of the pinctrl registers are lost when the per power
domain loses power. The pincrtl code can perform the necessary
save/r
From: Russ Dill
It isn't much of a win, and with hibernation, everything loses context.
So Drop the concept of certain power domains not being able to lose
context.
Signed-off-by: Russ Dill
Signed-off-by: Keerthy
---
arch/arm/mach-omap2/powerdomain.c | 41 -
From: Russ Dill
These registers are part of the wkup domain and are lost during RTC only
suspend and also hibernation, so storing/restoring their state is
necessary.
Signed-off-by: Russ Dill
Signed-off-by: Keerthy
---
arch/arm/mach-omap2/control.c | 84
Add the save and restore for clksrc as part of suspend and resume
so that it saves the counter value and restores. This is needed in
modes like rtc+ddr in self-refresh not doing this stalls the time.
Signed-off-by: Keerthy
---
arch/arm/mach-omap2/timer.c | 37
From: Dave Gerlach
Commit 2dc983c565e0 ("gpio/omap: cleanup prepare_for_idle and
resume_after_idle") introduces omap2_gpio_prepare_for_idle and
omap2_gpio_resume_after_idle to properly configure gpios that are used
as wake sources. When entering off mode, omap2_gpio_prepare_for_idle
can set a fla
From: Dave Gerlach
When the RTC lock and unlock functions were introduced it was likely
assumed that they would always be called from irq enabled context, hence
the use of local_irq_disable/enable. This is no longer true as the
RTC+DDR path makes a late call during the suspend path after irqs
hav
From: Russ Dill
It isn't much of a win, and with hibernation, everything loses context.
Signed-off-by: Russ Dill
Signed-off-by: Keerthy
---
drivers/gpio/gpio-omap.c| 38 -
include/linux/platform_data/gpio-omap.h | 1 -
2 files changed, 14 inser
From: Dave Gerlach
There are two registers on am43x needed for IO daisy chain wake to work
properly, however currently after an RTC+DDR cycle they are lost. We
must take care to save and restore these before and after entering RTC
mode otherwise IO daisy chain wake will stop working from DeepSlee
From: Russ Dill
This is used to support suspend modes like RTC-only and hibernate where
the state of the registers controlling clockdomains is lost.
Signed-off-by: Russ Dill
Signed-off-by: Dave Gerlach
Signed-off-by: Keerthy
---
arch/arm/mach-omap2/clockdomain.c | 46
From: Tero Kristo
These registers are part of the wkup domain and are lost during RTC only
suspend and also hibernation, so storing/restoring their state is
necessary.
Signed-off-by: Tero Kristo
Signed-off-by: Keerthy
---
arch/arm/mach-omap2/control.c | 94
RTC plus DDR in self-refresh is power a saving mode where in the entire
system including the different voltage rails from PMIC are shutdown except
the ones feeding on to RTC and DDR. DDR is kept in self-refresh hence the
contents are preserved. RTC ALARM2 is connected to PMIC_EN line once
we the AL
From: Russ Dill
This is used to support suspend modes like RTC-only and hibernate where
the state of these registers is lost.
After the PRCM loses context in the case of an RTC+DDR cycle omap_hwmod
attempts to return all hwmods to their previous state, however certain
hwmods cannot just be disab
AFS series posted by dhowells depended upon lookup_one_len()
rework; now that prereq is in the mainline, that series had been
rebased on top of it and got some exposure and testing...
The following changes since commit fd3b36d275660c905da9900b078eea341847d5e4:
Merge branch 'work.namei'
On 04/11/2018 07:51 PM, Jae Hyun Yoo wrote:
On 4/11/2018 5:34 PM, Guenter Roeck wrote:
On 04/11/2018 02:59 PM, Jae Hyun Yoo wrote:
Hi Guenter,
Thanks a lot for sharing your time. Please see my inline answers.
On 4/10/2018 3:28 PM, Guenter Roeck wrote:
On Tue, Apr 10, 2018 at 11:32:11AM -0700
Hi all,
Please do not add any v4.18 destined stuff to your linux-next included
trees until after v4.17-rc1 has been released.
Changes since 20180411:
The parisc-hd tree lost its build failure.
Non-merge commits (relative to Linus' tree): 1143
1201 files changed, 42273 insertions(+),
Hi Amelie,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on robh/for-next]
[also build test WARNING on v4.16]
[cannot apply to next-20180411]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https
On Wed, Apr 11, 2018 at 9:24 AM, David Howells wrote:
>
> (*) CONFIG_LOCK_DOWN_KERNEL
>
> This makes lockdown available and applies it to all the points that
> need to be locked down if the mode is set. Lockdown mode can be
> enabled by providing:
>
> lockdown=1
By doing
On Wed, Apr 11, 2018 at 1:33 PM, Greg KH wrote:
> On Wed, Apr 11, 2018 at 09:09:16PM +0100, David Howells wrote:
>> Greg KH wrote:
>>
>> > Why not just disable debugfs entirely? This half-hearted way to sorta
>> > lock it down is odd, it is meant to not be there at all, nothing in your
>> > norm
On 4/11/2018 5:34 PM, Guenter Roeck wrote:
On 04/11/2018 02:59 PM, Jae Hyun Yoo wrote:
Hi Guenter,
Thanks a lot for sharing your time. Please see my inline answers.
On 4/10/2018 3:28 PM, Guenter Roeck wrote:
On Tue, Apr 10, 2018 at 11:32:11AM -0700, Jae Hyun Yoo wrote:
This commit adds PECI
When Linux runs as a guest VM in Hyper-V and Hyper-V adds the virtual PCI
bus to the guest, Hyper-V always provides unique PCI domain.
commit 4a9b0933bdfc ("PCI: hv: Use device serial number as PCI domain")
overrode unique domain with the serial number of the first device added to
the virtual PCI
The property of the legacy mode for the eMMC PHY turned out to
be worng. Some eMMC devices are unstable due to the set-up/hold
timing violation. Correct the delay value.
Signed-off-by: Masahiro Yamada
---
arch/arm64/boot/dts/socionext/uniphier-ld11.dtsi | 2 +-
arch/arm64/boot/dts/socionext/u
On 12/04/2018 09:48, Jia-Ju Bai wrote:
b53_switch_reset_gpio() is never called in atomic context.
The call chain ending up at b53_switch_reset_gpio() is:
[1] b53_switch_reset_gpio() <- b53_switch_reset() <-
b53_reset_switch() <- b53_setup()
b53_switch_reset_gpio() is set as ".setup" in str
On 2018/4/12 10:21, arvindY wrote:
On Thursday 12 April 2018 07:00 AM, Jia-Ju Bai wrote:
On 2018/4/12 0:16, James Bottomley wrote:
On Wed, 2018-04-11 at 23:39 +0800, Jia-Ju Bai wrote:
de4x5_hw_init() is never called in atomic context.
de4x5_hw_init() is only called by de4x5_pci_probe(),
On 4/10/2018 9:02 PM, Laura Abbott wrote:
> There's an ongoing effort to remove VLAs from the kernel
> (https://lkml.org/lkml/2018/3/7/621) to eventually turn on -Wvla.
> The test already pre-allocates some buffers with kmalloc so turn
> the two VLAs in to pre-allocated kmalloc buffers.
>
> Signed
On Thursday 12 April 2018 07:00 AM, Jia-Ju Bai wrote:
On 2018/4/12 0:16, James Bottomley wrote:
On Wed, 2018-04-11 at 23:39 +0800, Jia-Ju Bai wrote:
de4x5_hw_init() is never called in atomic context.
de4x5_hw_init() is only called by de4x5_pci_probe(), which is only
set as ".probe" in stru
Hi Oleksandr,
Just have a question, is this drm/xen-front stuff orthogonal to xen shared
coprocessor framework for gpu, or are they exclusive?
Thanks,
Peng.
> Subject: [Xen-devel] [PATCH v6 0/1] drm/xen-front: Add support for Xen PV
> display frontend
>
> From: Oleksandr Andrushchenko
>
> Hell
On 4/11/2018 4:52 AM, Joel Stanley wrote:
On 11 April 2018 at 04:02, Jae Hyun Yoo wrote:
This commit adds PECI bus/adapter node of AST24xx/AST25xx into
aspeed-g4 and aspeed-g5.
The patches to the device trees get merged by the ASPEED maintainer
(me). Once you have the bindings reviewed you c
For LD20, the bit 5 of the offset 0x200c turned out to be a USB3
reset. The hardware document says it is the GIO reset despite LD20
has no GIO bus, confusingly.
Also, fix confusing comments for PXs3.
Signed-off-by: Masahiro Yamada
---
drivers/reset/reset-uniphier.c | 6 +++---
1 file changed,
On 04/09/2018 11:03 AM, Jia-Ju Bai wrote:
pcistub_probe() is never called in atomic context.
This function is only set as ".probe" in struct pci_driver.
Despite never getting called from atomic context,
pcistub_probe() calls kmalloc() with GFP_ATOMIC,
which does not sleep for allocation.
GFP_A
Hi Joel,
On 4/11/2018 4:52 AM, Joel Stanley wrote:
On 11 April 2018 at 04:02, Jae Hyun Yoo wrote:
This commit adds a dt-bindings document of PECI adapter driver for Aspeed
We try to capitalise ASPEED.
Got it. Will capitalize all Aspeed words.
AST24xx/25xx SoCs.
---
.../devicetree/bind
On Wed, Apr 11, 2018 at 11:57:30AM -0700, Paul E. McKenney wrote:
> On Wed, Apr 11, 2018 at 09:56:44PM +0800, Boqun Feng wrote:
> > Although all flavors of RCU are annotated correctly with lockdep
> > annotations as recursive read locks, the 'check' parameter for their
> > calls to lock_acquire() i
Hi Joel,
On 4/11/2018 4:52 AM, Joel Stanley wrote:
Hi Jae,
On 11 April 2018 at 04:02, Jae Hyun Yoo wrote:
This commit adds documents of generic PECI bus, adapter and client drivers.
Signed-off-by: Jae Hyun Yoo
Reviewed-by: Haiyue Wang
Reviewed-by: James Feist
Reviewed-by: Vernon Mauery
C
Hello Joel,
Thanks for sharing your time. Please see my answers inline.
On 4/11/2018 4:51 AM, Joel Stanley wrote:
Hello Jae,
On 11 April 2018 at 04:02, Jae Hyun Yoo wrote:
This commit adds PECI adapter driver implementation for Aspeed
AST24xx/AST25xx.
The driver is looking good!
It looks
On Wed, Apr 11, 2018 at 07:29:40PM -0500, Kim Phillips wrote:
> On Thu, 12 Apr 2018 08:31:09 +0900
> Namhyung Kim wrote:
>
> > Hello,
>
> Hi,
>
> > On Wed, Apr 11, 2018 at 06:07:52PM -0500, Kim Phillips wrote:
> > > ---
> > > It's not clear to me what the specific intent of the original commit
Hi Vivek,
On 2018/4/11 13:15, Vivek Gautam wrote:
> Hi Yisheng,
>
>
> On 4/11/2018 6:52 AM, Yisheng Xie wrote:
>> Hi Tomasz,
>>
>> On 2018/4/10 21:14, Tomasz Figa wrote:
>>> Hi Yisheng,
>>>
>>> Sorry, I think we missed your question here.
>>>
>>> On Wed, Mar 28, 2018 at 3:12 PM Yisheng Xie wrot
From: Howard McLauchlan
uprobes cannot successfully attach to binaries located in a directory
mounted with overlayfs.
To verify, create directories for mounting overlayfs
(upper,lower,work,merge), move some binary into merge/ and use readelf
to obtain some known instruction of the binary. I used
Linus,
A few clean ups and bug fixes
- Replace open coded "ARRAY_SIZE()" with macro
- Updates to uprobes
- Bug fix for perf event filter on error path
Please pull the latest ktest-v4.17-2 tree, which can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-ktest.git
From: Ravi Bangoria
tu->offset is unsigned long, not a pointer, thus %lx should
be used to print it, not the %px.
Link:
http://lkml.kernel.org/r/20180315082756.9050-1-ravi.bango...@linux.vnet.ibm.com
Cc: sta...@vger.kernel.org
Acked-by: Masami Hiramatsu
Fixes: 0e4d819d0893 ("trace_uprobe: Dis
From: Ravi Bangoria
Simplify probes_seq_show() function. No change in output
before and after patch.
Link:
http://lkml.kernel.org/r/20180315082756.9050-2-ravi.bango...@linux.vnet.ibm.com
Acked-by: Masami Hiramatsu
Signed-off-by: Ravi Bangoria
Signed-off-by: Steven Rostedt (VMware)
---
kern
From: "Steven Rostedt (VMware)"
There's some inconsistency with what to set the output parameter filterp
when passing to create_filter(..., struct event_filter **filterp).
Whatever filterp points to, should be NULL when calling this function. The
create_filter() calls create_filter_start() with
On 2018/4/12 0:19, Florian Fainelli wrote:
On 04/11/2018 12:14 AM, Jia-Ju Bai wrote:
On 2018/4/11 13:30, Phil Reid wrote:
On 11/04/2018 09:51, Jia-Ju Bai wrote:
b53_switch_reset_gpio() is never called in atomic context.
The call chain ending up at b53_switch_reset_gpio() is:
[1] b53_switch
Hi, I find CONFIG_X86_RESERVE_LOW=64 in my system, so trim_low_memory_range()
will reserve low 64kb memory. But efi_free_boot_services() will free it to
buddy system again later because BIOS set the type to EFI_BOOT_SERVICES_CODE.
Here is the log:
...
efi: mem03: type=3, attr=0xf, range=[0x000
b53_switch_reset_gpio() is never called in atomic context.
The call chain ending up at b53_switch_reset_gpio() is:
[1] b53_switch_reset_gpio() <- b53_switch_reset() <-
b53_reset_switch() <- b53_setup()
b53_switch_reset_gpio() is set as ".setup" in struct dsa_switch_ops.
This function is not c
2018-04-12 0:20 GMT+02:00 Gabriel C :
> 2018-04-11 20:35 GMT+02:00 Jean-Marc Valin :
>> On 04/11/2018 05:37 AM, Christian König wrote:
With your patches my EPYC box is unusable with 4.15++ kernels.
The whole Desktop is acting weird. This one is using
an Cape Verde PRO [Radeon HD 77
On Wed, Apr 11, 2018 at 6:34 PM, Dmitry V. Levin wrote:
>
> There is a clear pattern of sneaking in ABI changes using innocently
> looking commit messages.
Yes, this siginfo stuff has been a mess.
Eric - this needs to stop. Or we need to revert all that garbage entirely.
Send a fix. And stop ch
Add UFS PHY support to make SDM845 UFS work with common PHY framework.
Signed-off-by: Can Guo
Reviewed-by: Vivek Gautam
---
drivers/phy/qualcomm/phy-qcom-qmp.c | 130 +---
drivers/phy/qualcomm/phy-qcom-qmp.h | 8 +++
2 files changed, 127 insertions(+), 11 delet
This patch series adds support for UFS QMP PHY on SDM845 and the
compatible string for it. This patch series depends on the current
proposed QMP V3 USB3 UNI PHY support for sdm845 driver [1] and also based
on the DT bindings for the QMP V3 USB3 PHYs based dirver [2]. This series
can only be merged
Update the compatible string for UFS QMP PHY on SDM845.
Signed-off-by: Can Guo
Reviewed-by: Vivek Gautam
Reviewed-by: Rob Herring
---
Documentation/devicetree/bindings/phy/qcom-qmp-phy.txt | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/p
On 4/10/2018 5:03 PM, Bjorn Helgaas wrote:
>> DPC and AER should attempt recovery in the same way, except the
>> cases where system is with hotplug enabled.
> What's the connection with hotplug? I see from the patch that for
> hotplug bridges you remove the tree below the bridge, and otherwise
> y
RongQing reported that there are some X2APIC id 0x in his machine's
ACPI MADT table, which made the number of possible CPU inaccuracy.
The reason is that the ACPI X2APIC parser has no sanity check for
apicid 0x, which is an invalid id in all APIC types. See
"Intel® 64 Architecture
You can build a kernel in a cross compiling environment that doesn't have perl
in the $PATH. Commit 429f7a062e3b broke that for 32 bit arm. Fix it.
Signed-off-by: Rob Landley
---
arch/arm/boot/compressed/Makefile |9 -
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git a/ar
Hi,
On Mon, Apr 09, 2018 at 06:22:53PM +0300, Dmitry V. Levin wrote:
> There seems to be a regression in v4.16 on ppc compat very similar
> to sparc compat regression reported earlier at
> https://marc.info/?l=linux-sparc&m=151501500704383 .
>
> The symptoms are exactly the same: the same signal_
On 2018/4/11 23:04, Ulf Hansson wrote:
On 11 April 2018 at 04:46, Jia-Ju Bai wrote:
wbsd_init() is never called in atomic context.
The call chains ending up at wbsd_init() are:
[1] wbsd_init() <- wbsd_probe()
[2] wbsd_init() <- wbsd_pnp_probe()
wbsd_probe() is set as ".probe" in struct plat
On 2018/4/12 0:16, James Bottomley wrote:
On Wed, 2018-04-11 at 23:39 +0800, Jia-Ju Bai wrote:
de4x5_hw_init() is never called in atomic context.
de4x5_hw_init() is only called by de4x5_pci_probe(), which is only
set as ".probe" in struct pci_driver.
Despite never getting called from atomic
Do as the swim3 driver does and just return -ENOTTY.
Cc: Geert Uytterhoeven
Cc: linux-m...@lists.linux-m68k.org
Signed-off-by: Finn Thain
---
drivers/block/amiflop.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/block/amiflop.c b/drivers/block/amiflop.c
index 3a
On 2018-04-09 19:28, Vivek Gautam wrote:
Hi Can,
On 3/27/2018 12:48 PM, Can Guo wrote:
Add UFS PHY support to make SDM845 UFS work with common PHY framework.
Signed-off-by: Can Guo
---
drivers/phy/qualcomm/phy-qcom-qmp.c | 130
+---
drivers/phy/qualcomm/p
Matthew,
Please Cced relevant people so they know what's going on the problem
they spent on much time. Everyone doesn't keep an eye on mailing list.
On Tue, Apr 10, 2018 at 11:03:18PM -0700, Matthew Wilcox wrote:
> From: Matthew Wilcox
>
> v1->v2:
> - Added review/ack tags (thanks!)
> - Switc
The resource size is 0x2000 == end - start + 1.
Therefore end == start + 0x2000 - 1.
Cc: Laurent Vivier
Cc: sta...@vger.kernel.org # v4.14+
Tested-by: Stan Johnson
Signed-off-by: Finn Thain
Acked-by: Laurent Vivier
Reviewed-by: Geert Uytterhoeven
---
arch/m68k/mac/config.c | 2 +-
1 file cha
In the floppy_find() function in swim.c is a call to
get_disk(swd->unit[drive].disk). The actual parameter to this call
can be a NULL pointer when drive == swd->floppy_count. This causes
an oops in get_disk().
Data read fault at 0x0198 in Super Data (pc=0x1be5b6)
BAD KERNEL BUSERR
Oops: 00
For reasons I don't understand, calling ioremap() then iounmap() on
the SWIM MMIO region causes a hang on 68030 (but not on 68040).
~# modprobe swim_mod
SWIM floppy driver Version 0.2 (2008-10-30)
SWIM device not found !
watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [modprobe:285]
Modules link
Wakko Warner wrote:
> Ming Lei wrote:
> > Sure, thanks for your sharing.
> >
> > Wakko, could you test the following patch and see if there is any
> > difference?
> >
> > --
> > diff --git a/drivers/target/target_core_pscsi.c
> > b/drivers/target/target_core_pscsi.c
> > index 0d99b242e82e..61471
Rename floppy_type macros to make them more consistent with the scsi_type
macros, which are named after classes of models with similar memory maps.
The documentation for LC-class machines has the IO devices at offsets
from $50F0 . Use these addresses (consistent with mac_scsi resources)
becaus
Cc: Laurent Vivier
Cc: Jens Axboe
Cc: sta...@vger.kernel.org # v4.14+
Fixes: 103db8b2dfa5 ("[PATCH] swim: stop sharing request queue across multiple
gendisks")
Tested-by: Stan Johnson
Signed-off-by: Finn Thain
Acked-by: Laurent Vivier
Reviewed-by: Geert Uytterhoeven
---
drivers/block/swim.c
1 - 100 of 1466 matches
Mail list logo
