On Fri, Mar 29, 2019 at 3:34 PM Baoquan He wrote:
>
> On 03/29/19 at 03:25pm, Pingfan Liu wrote:
> > On Fri, Mar 29, 2019 at 2:27 PM Baoquan He wrote:
> > >
> > > On 03/29/19 at 01:45pm, Pingfan Liu wrote:
> > > > On Fri, Mar 22, 2019 at 4:34 PM Baoquan He wrote:
> > > > >
> > > > > On 03/22/19
dump_blkd_tasks() uses 10 as the max number of blocked
tasks, which are printed. However, it has an argument
which provides that number. So, use the argument value
instead. As all callers currently pass 10 as the number,
there isn't any impact.
Signed-off-by: Neeraj Upadhyay
---
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger
crash:
Reported-and-tested-by:
syzbot+f9f3f388440283da2...@syzkaller.appspotmail.com
Tested on:
commit: 8c2ffd91 Linux 5.1-rc2
git tree:
On Thu, Mar 28, 2019 at 11:19:25PM +, Xing, Cedric wrote:
> > It's certainly making progress. I like the fact that the callback is
> > now unconditional (if non-NULL) rather than being used just in case of
> > certain exit types. But, if we go down this route, let's name and
> > document it
On 28.03.19 17:31, Paolo Bonzini wrote:
> The documentation does not mention how to delete a slot, add the
> information.
>
> Reported-by: Nathaniel McCallum
> Signed-off-by: Paolo Bonzini
> ---
> Documentation/virtual/kvm/api.txt | 18 ++
> 1 file changed, 10 insertions(+), 8
On Fri, Mar 29, 2019 at 09:37:00AM +, Junichi Nomura wrote:
>On 3/29/19 6:16 PM, Borislav Petkov wrote:
>> On Fri, Mar 29, 2019 at 05:05:50PM +0800, Chao Fan wrote:
>>> But in my code, I am not sure which version will be found firstly, so I
>>> write this logical, if ACPI20 found, return
On Fri, Mar 29, 2019 at 09:39:20AM +, Maximilian Heyne wrote:
> Some NVMe devices require specific io and admin timeouts that are
> different from the default, for instance local vs. remote storage.
>
> This patch adds per-device admin and io timeouts to the nvme_ctrl
> structure and replaces
On 28.03.19 18:10, Paolo Bonzini wrote:
> All architectures except MIPS were defining it in the same way,
> and memory slots are handled entirely by common code so there
> is no point in keeping the definition per-architecture.
>
> Signed-off-by: Paolo Bonzini
> ---
>
On Thu, Mar 28, 2019 at 06:21:41PM +0100, Domenico Andreoli wrote:
> On Thu, Mar 28, 2019 at 02:23:33PM +0200, Jarkko Sakkinen wrote:
> > On Wed, Mar 27, 2019 at 09:21:15AM +0100, Domenico Andreoli wrote:
> > > Hi Jarkko,
> > >
> > > my laptop fails to suspend/hibernate since v5.1-rc1, it
On Thu, Mar 28, 2019 at 06:19:26PM +0100, Domenico Andreoli wrote:
> On Fri, Mar 22, 2019 at 12:51:20PM +0200, Jarkko Sakkinen wrote:
> > tpm_chip_start/stop() should be also called for TPM 1.x devices on
> > suspend. Add that functionality back. Do not lock the chip because
> > it is unnecessary
On 29-Mar-19 11:36, Mukesh Ojha wrote:
>
> On 3/29/2019 12:44 AM, Gal Pressman wrote:
>> Commit d901b2760dc6 ("lib/scatterlist: Provide a DMA page iterator")
>> added the sg DMA iterator but a leftover remained in the sg_page_iter
>> documentation, remove it.
>>
>> Cc: Jason Gunthorpe
>>
Some NVMe devices require specific io and admin timeouts that are
different from the default, for instance local vs. remote storage.
This patch adds per-device admin and io timeouts to the nvme_ctrl
structure and replaces all usages of the module parameters in the PCI
NVMe driver with the
Add two sysfs files for reading and updating the admin and io timeouts
of individual NVMe devices. For this, two new nvme_ctrl_ops were added
to update the respective timeouts. This patch implements these ops for
the pci nvme driver. Therefore, only the timeouts for PCI NVMe devices
can be
On Fri, Mar 29, 2019 at 10:13:25AM +0100, Michal Hocko wrote:
> On Fri 29-03-19 16:29:15, Baoquan He wrote:
> > The input parameter 'phys_index' of memory_block_action() is actually
> > the section number, but not the phys_index of memory_block. Fix it.
>
> I have tried to explain that the naming
The input parameter 'phys_index' of memory_block_action() is actually
the section number, but not the phys_index of memory_block. This is
a relict from the past when one memory block could only contain one
section.
Rename it to start_section_nr.
Signed-off-by: Baoquan He
Acked-by: Michal Hocko
Adding Michel and David in the loop who are interested in this topic too.
Le 13/03/2019 à 19:01, Matthew Wilcox a écrit :
On Wed, Mar 13, 2019 at 04:10:14PM +0100, Laurent Dufour wrote:
If this is not too late and if there is still place available, I would like
to attend the MM track and
On 28/03/2019 21:46, Tony Krowiak wrote:
On 3/22/19 10:43 AM, Pierre Morel wrote:
To be able to use the VFIO interface to facilitate the
mediated device memory pinning/unpinning we need to register
a notifier for IOMMU.
While we will start to pin one guest page for the interrupt indicator
> From: Christina Quast [mailto:cqu...@hanoverdisplays.com]
> Sent: Wednesday, March 13, 2019 10:21 PM
>
> In the iMX7d datasheet, the PAD_CTL_DSE_X* values are different from the
> documentation.
>
> Changes since v2:
> * Changed patch title to 'dt-bindings: pinctrl: imx7d:'
>
> Signed-off-by:
On Fri, Mar 29, 2019 at 09:56:37AM +0100, David Hildenbrand wrote:
> Oh okay, so actually the way I guessed it would be now.
>
> While this makes totally sense, I'll have to look how it is currently
> handled, meaning if there is a change. I somewhat remembering that
> delayed struct pages
On 03/29/19 at 10:13am, Michal Hocko wrote:
> On Fri 29-03-19 16:29:15, Baoquan He wrote:
> > The input parameter 'phys_index' of memory_block_action() is actually
> > the section number, but not the phys_index of memory_block. Fix it.
>
> I have tried to explain that the naming is mostly a
Hi Daniel,
On Thursday 28 Mar 2019 at 21:23:35 (+0100), Daniel Lezcano wrote:
> > /**
> > * struct time_in_idle - Idle time stats
> > * @time: previous reading of the absolute time that this cpu was idle
> > @@ -82,7 +70,7 @@ struct time_in_idle {
> > * frequency.
> > * @max_level:
Liran Alon writes:
>> On 28 Mar 2019, at 22:31, Vitaly Kuznetsov wrote:
>>
>> This is embarassing but we have another Windows/Hyper-V issue to workaround
>> in KVM (or QEMU). Hope "RFC" makes it less offensive.
>>
>> It was noticed that Hyper-V guest on q35 KVM/QEMU VM hangs on boot if e.g.
On Fri 29-03-19 16:29:14, Baoquan He wrote:
> The code comment above sparse_add_one_section() is obsolete and
> incorrect, clean it up and write new one.
>
> Signed-off-by: Baoquan He
Acked-by: Michal Hocko
> ---
> v2->v3:
> Normalize the code comment to use '/**' at 1st line of doc
>
Commit 1627314fb54a33e ("perf: Suppress AUX/OVERWRITE records") has an
unintended side-effect of also suppressing all AUX records with no flags
and non-zero size, so all the regular records in the full trace mode.
This breaks some use cases for people.
Fix this by restoring "regular" AUX records.
On Fri 29-03-19 16:29:15, Baoquan He wrote:
> The input parameter 'phys_index' of memory_block_action() is actually
> the section number, but not the phys_index of memory_block. Fix it.
I have tried to explain that the naming is mostly a relict from the past
than really a misleading name
> -Original Message-
> From: Aisheng Dong
> Sent: 2019年3月28日 19:21
> To: Marc Zyngier ; Leonard Crestez
> ; l.st...@pengutronix.de; Richard Zhu
> ; Jacky Bai
> Cc: Fabio Estevam ; Cosmin Samoila
> ; Robin Gong ; Mircea Pop
> ; Daniel Baluta ;
> catalin.mari...@arm.com;
Commit c60f83b813e5 ("perf, pt, coresight: Fix address filters for vmas
with non-zero offset") changes the address filtering logic to communicate
filter ranges to the PMU driver via a single address range object, instead
of having the driver do the final bit of math. That change forgets to take
> From: Angus Ainslie (Purism) [mailto:an...@akkea.ca]
> Sent: Thursday, March 28, 2019 9:38 PM
>
> Fix a typo in the compatible string
>
> Signed-off-by: Angus Ainslie (Purism)
> ---
> arch/arm64/boot/dts/freescale/imx8mq.dtsi | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff
Здравейте!
Ваучерите за храна се нареждат сред любимите социални придобивки на работещите
хора и сред най-предпочитаните начини за стимулиране от работодателите. Те
подобряват ефективността и производителността на Вашите служители.
Благодарение на ваучерите за храна реализирате спестявания –
On Thursday 28 Mar 2019 at 20:51:12 (+0100), Daniel Lezcano wrote:
> On 28/03/2019 18:42, Quentin Perret wrote:
> > Hi Daniel,
> >
> > On Thursday 28 Mar 2019 at 18:27:49 (+0100), Daniel Lezcano wrote:
> >> On 28/03/2019 11:22, Quentin Perret wrote:
> diff --git
In the function divider_recalc_rate The judgment of the return value of
_get_div indicates that the return value of _get_div may be 0.
In order to avoid the divide-by-zero error, add check the return value
of _get_div in the divider_ro_round_rate_parent
Signed-off-by: nixiaoming
---
On 29.03.19 09:56, David Hildenbrand wrote:
> On 29.03.19 09:45, Oscar Salvador wrote:
>> On Thu, Mar 28, 2019 at 04:31:44PM +0100, David Hildenbrand wrote:
>>> Correct me if I am wrong. I think I was confused - vmemmap data is still
>>> allocated *per memory block*, not for the whole added
On 28/03/2019 18:25, Tony Krowiak wrote:
On 3/28/19 12:27 PM, Pierre Morel wrote:
On 28/03/2019 17:12, Tony Krowiak wrote:
On 3/22/19 10:43 AM, Pierre Morel wrote:
When the mediated device is open we setup the relation with KVM
unset it
when the mediated device is released.
s/open we
On 29.03.19 09:45, Oscar Salvador wrote:
> On Thu, Mar 28, 2019 at 04:31:44PM +0100, David Hildenbrand wrote:
>> Correct me if I am wrong. I think I was confused - vmemmap data is still
>> allocated *per memory block*, not for the whole added memory, correct?
>
> No, vmemap data is allocated per
On Fri, 29 Mar 2019 13:50:26 +0530
Vignesh Raghavendra wrote:
> Hi Boris,
>
> On 29/03/19 1:25 AM, Boris Brezillon wrote:
> > On Thu, 28 Mar 2019 16:46:24 +0530
> > Naga Sureshkumar Relli wrote:
> >
> >> Call spi_mem_default_supports_op() first, before calling controller
> >> specific
On 28/03/2019 17:12, Tony Krowiak wrote:
On 3/22/19 10:43 AM, Pierre Morel wrote:
We prepare the interception of the PQAP/AQIC instruction for
the case the AQIC facility is enabled in the guest.
First of all we do not want to change existing behavior when
intercepting AP instructions without
> Great, I would like to see how this works there :-).
>
>> I guess one important thing to mention is that it is no longer possible
>> to remove memory in a different granularity it was added. I slightly
>> remember that ACPI code sometimes "reuses" parts of already added
>> memory. We would
Commit e31f941cf977 ("MAINTAINERS: update list of qcom drivers") had a
typo in the filename, replace the underscore with dash.
Fixes: e31f941cf977 ("MAINTAINERS: update list of qcom drivers")
Reported-by: Joe Perches
Signed-off-by: Amit Kucheria
Reviewed-by: Vinod Koul
Reviewed-by: Mukesh Ojha
Hi,
A gentle ping on this series (mfd + pinctrl patches, DT patches will be
taken in STM32 soc tree).
Regards,
Amelie
On 2/27/19 10:34 AM, Amelie Delaunay wrote:
> This series adds support for STMicroelectronics Multi-Function eXpander
> (STMFX), used on some STM32 discovery and evaluation
> pavel@amd:~/cip$ cat /sys/power/state
> freeze mem disk
> pavel@amd:~/cip$ cat /sys/class/leds/phy0-led/trigger
> none bluetooth-power rfkill-any rfkill-none kbd-scrolllock kbd-numlock
> kbd-capslock kbd-kanalock kbd-shiftlock kbd-altgrlock kbd-ctrllock
> kbd-altlock kbd-shiftllock
On Thu, Mar 28, 2019 at 04:31:44PM +0100, David Hildenbrand wrote:
> Correct me if I am wrong. I think I was confused - vmemmap data is still
> allocated *per memory block*, not for the whole added memory, correct?
No, vmemap data is allocated per memory-resource added.
In case a DIMM, would be a
Simple string comparisons are cheaper than DT lookups, as the latter
involve taking a spinlock and traversing properties.
Hence optimize quirk checks by postponing DT lookups after string
comparisons.
Signed-off-by: Geert Uytterhoeven
---
drivers/gpio/gpiolib-of.c | 11 +--
1 file
Add a IIO driver that reports the angle between the lid and the base for
ChromeOS convertible device.
Tested on eve with ToT EC firmware.
Check driver is loaded and lid angle is correct.
Change-Id: I3506be4a1405f108eebe6c1d3a3dbe975ca00519
Signed-off-by: Gwendal Grignou
---
This patch allows to generate lzma compressed uImage
Signed-off-by: Christophe Leroy
---
arch/powerpc/Kconfig | 1 +
arch/powerpc/boot/Makefile | 2 ++
arch/powerpc/boot/wrapper | 5 -
3 files changed, 7 insertions(+), 1 deletion(-)
diff --git a/arch/powerpc/Kconfig
On 25/03/2019 13:18, Neil Armstrong wrote:
> On 25/03/2019 11:42, Jerome Brunet wrote:
>> While some SoC samples are able to lock with a PLL factor of 55, others
>> samples can't. ATM, a minimum of 60 appears to work on all the samples
>> I have tried, so lets use this value until we have a good
On 29/03/2019 09:39, Jerome Brunet wrote:
> On Wed, 2019-03-27 at 16:13 +0100, Neil Armstrong wrote:
>> The vid_pll_div is a programmable fractional divider, but vendor gives a
>> limited of known configuration value and it's corresponding fraction.
>>
>> Thus when at reset value (0) or unknown
This patch allows to generate bzip2 compressed uImage
Signed-off-by: Christophe Leroy
---
arch/powerpc/Kconfig | 1 +
arch/powerpc/boot/Makefile | 2 ++
arch/powerpc/boot/wrapper | 8 +++-
3 files changed, 10 insertions(+), 1 deletion(-)
diff --git a/arch/powerpc/Kconfig
On Wed, 2019-03-27 at 16:13 +0100, Neil Armstrong wrote:
> The vid_pll_div is a programmable fractional divider, but vendor gives a
> limited of known configuration value and it's corresponding fraction.
>
> Thus when at reset value (0) or unknown value, we cannot determine the
> result rate.
>
Add support for ZII's i.MX7 based Remote Peripheral Unit 2 (RPU2)
board.
Signed-off-by: Andrey Smirnov
Cc: Shawn Guo
Cc: Chris Healy
Cc: Andrew Lunn
Cc: Fabio Estevam
Cc: Rob Herring
Cc: linux-kernel@vger.kernel.org
Cc: devicet...@vger.kernel.org
---
Changes since [v1]:
- Added
Add support for ZII i.MX7 RPU2 board.
Signed-off-by: Andrey Smirnov
Reviewed-by: Rob Herring
Cc: Shawn Guo
Cc: Chris Healy
Cc: Andrew Lunn
Cc: Fabio Estevam
Cc: Rob Herring
Cc: linux-kernel@vger.kernel.org
Cc: devicet...@vger.kernel.org
---
Documentation/devicetree/bindings/arm/fsl.yaml |
Add #io-channel-cells to list of required properties. Needed to be
able to reference that node by phandle.
Signed-off-by: Andrey Smirnov
Cc: Shawn Guo
Cc: Chris Healy
Cc: Andrew Lunn
Cc: Fabio Estevam
Cc: Rob Herring
Cc: linux-kernel@vger.kernel.org
Cc: devicet...@vger.kernel.org
---
Specify #io-channel-cells in ADC nodes. Needed to be able to reference
them by phandle.
Signed-off-by: Andrey Smirnov
Cc: Shawn Guo
Cc: Chris Healy
Cc: Andrew Lunn
Cc: Fabio Estevam
Cc: Rob Herring
Cc: linux-kernel@vger.kernel.org
Cc: devicet...@vger.kernel.org
---
On Thu, Mar 28, 2019 at 8:34 PM Mika Westerberg
wrote:
>
> On Thu, Mar 28, 2019 at 08:19:59PM +0800, Chris Chiu wrote:
> > On Thu, Mar 28, 2019 at 5:38 PM Daniel Drake wrote:
> > >
> > > On Thu, Mar 28, 2019 at 5:17 PM Andy Shevchenko
> > > wrote:
> > > > Hmm... Can you confirm that laptop you
On Fri, Mar 29, 2019 at 09:35:34AM +0100, Daniel Vetter wrote:
> On Thu, Mar 28, 2019 at 05:13:05PM +0100, Paul Kocialkowski wrote:
> > The firstopen DRM driver hook was initially used to perform hardware
> > initialization, which is now considered legacy. Only a single user of
> > firstopen
On 3/29/2019 12:44 AM, Gal Pressman wrote:
Commit d901b2760dc6 ("lib/scatterlist: Provide a DMA page iterator")
added the sg DMA iterator but a leftover remained in the sg_page_iter
documentation, remove it.
Cc: Jason Gunthorpe
Signed-off-by: Gal Pressman
---
include/linux/scatterlist.h |
On Fri 2019-03-29 07:22:53, Greg Kroah-Hartman wrote:
> On Fri, Mar 29, 2019 at 04:09:22AM +0100, Marek Behun wrote:
> > Hello Tejun and Greg,
> >
> > kernfs_fop_open/read/write allocates a buffer for the ->read, ->write,
> > or ->seq_read methods. This buffer is either preallocated or allocated
On Thu, Mar 28, 2019 at 04:09:06PM +0100, David Hildenbrand wrote:
> On 28.03.19 14:43, Oscar Salvador wrote:
> > Hi,
> >
> > since last two RFCs were almost unnoticed (thanks David for the feedback),
> > I decided to re-work some parts to make it more simple and give it a more
> > testing, and
The code comment above sparse_add_one_section() is obsolete and
incorrect, clean it up and write new one.
Signed-off-by: Baoquan He
---
v2->v3:
Normalize the code comment to use '/**' at 1st line of doc
above function.
v1-v2:
Add comments to explain what the returned value means for
each
Implement Fintek F81232 break on/off with LCR register.
It's the same with 16550A LCR register layout.
Signed-off-by: Ji-Ze Hong (Peter Hong)
---
drivers/usb/serial/f81232.c | 29 +++--
1 file changed, 23 insertions(+), 6 deletions(-)
diff --git
The input parameter 'phys_index' of memory_block_action() is actually
the section number, but not the phys_index of memory_block. Fix it.
Signed-off-by: Baoquan He
---
v2->v3:
Rename the parameter to 'start_section_nr' from 'sec'.
drivers/base/memory.c | 7 ---
1 file changed, 4
On Fri, Mar 29, 2019 at 12:02:44AM +, Colin King wrote:
> From: Colin Ian King
>
> Currently the lower 8 bits of ret are being masked and left
> shifted by 8 bits always leaving a result of zero. The mask
> appears to be incorrect and should probably be 0xff00 instead
> of 0xff. Fix this.
Hi Boris,
On 29/03/19 1:25 AM, Boris Brezillon wrote:
> On Thu, 28 Mar 2019 16:46:24 +0530
> Naga Sureshkumar Relli wrote:
>
>> Call spi_mem_default_supports_op() first, before calling controller
>> specific ctlr->supports_op().
>> With this, controller drivers can drop checking the buswidths
On Fri, Mar 29, 2019 at 12:43 AM Colin King wrote:
>
> From: Colin Ian King
>
> When macro PM8001_USE_MSIX is defined there are redundant dead code
> calls to pm8001_chip_intx_interrupt_{enable|disable}. Clean this up
> by compiling in the appropriate enable/disable handlers for the
> defined
On Fri, Mar 29, 2019 at 04:50:18PM +0900, Masahiro Yamada wrote:
> On Tue, Mar 26, 2019 at 12:16 AM Changbin Du wrote:
> >
> > Backspace is not working on some terminal emulators which do not send the
> > key code defined by terminfo. Terminals either send '^H' (8) or '^?' (127).
> > But
Ensure that iov->num_VFs is set before a netlink message is sent
when the number of VFs is changed. Only the path for num_VFs > 0
is affected. The path for num_VFs = 0 is already correct.
Monitoring programs can relie on netlink messages to track interface
change and query their state in /sys.
Cc-ing Sahara
On (03/29/19 16:35), Sergey Senozhatsky wrote:
> 5.1.0-rc2-next-20190329
>
> [8.168722] ==
> [8.168723] WARNING: possible circular locking dependency detected
> [8.168724] 5.1.0-rc2-next-201
On Thu 28-03-19 18:28:36, Shakeel Butt wrote:
> A VCPU of a VM can allocate upto three pages which can be mmap'ed by the
> user space application. At the moment this memory is not charged. On a
> large machine running large number of VMs (or small number of VMs having
> large number of VCPUs),
On Fri, Mar 29, 2019 at 1:48 AM Junge, Terry wrote:
>
> On Thursday, March 28, 2019 6:49 AM Benjamin Tissoires
> wrote:
> >>
> >> Hi Nicolas,
> >>
> >> V4 looks good to me.
> >
> >Looks good to me too.
> >
> >Terry, can I consider this as a formal Rev-by you?
>
> Benjamin,
>
> Yes, thank you.
> On Thu, Mar 28, 2019 at 9:29 AM Andy Lutomirski wrote:
> > Doesn’t this just leak some of the canary to user code through side
> > channels?
>
> Erf, yes, good point. Let's just use prandom and be done with it.
And here I have some numbers on this. Actually prandom turned out to be pretty
On Tue, Mar 26, 2019 at 12:16 AM Changbin Du wrote:
>
> Backspace is not working on some terminal emulators which do not send the
> key code defined by terminfo. Terminals either send '^H' (8) or '^?' (127).
> But currently only '$?' is handled.
Shall I fix '$?' to '^?'
if it is a typo?
>
Hi, Guenter/Shawn
Since DT has been acked, would you pick up this patch series if no
additional comments?
Best Regards!
Anson Huang
> -Original Message-
> From: Rob Herring [mailto:r...@kernel.org]
> Sent: 2019年3月26日 4:37
> To: Anson Huang
> Cc: w...@linux-watchdog.org;
On Thu, Mar 28, 2019 at 05:10:05PM +, Colin King wrote:
> From: Colin Ian King
>
> The return from tty_write_room could potentially be negative if
> a tty write_room driver returns an error number (not that any seem
> to do). Rather than just check for a zero return, also check for
> a -ve
Hi Martin,
On 2019/3/29 2:03, Martin Blumenstingl wrote:
Hi Liang,
[..]
I don't think it is caused by a different NAND type, but i have followed
the some test on my GXL platform. we can see the result from the
attachment. By the way, i don't find any information about this on meson
NFC
Hi Adrian,
On 28/03/19 1:43 PM, Adrian Hunter wrote:
> On 27/03/19 1:47 PM, Faiz Abbas wrote:
>> Hi Adrian,
>>
>> On 27/03/19 4:45 PM, Adrian Hunter wrote:
>>> On 26/03/19 1:00 PM, Faiz Abbas wrote:
commit 5b0d62108b46 ("mmc: sdhci-omap: Add platform specific reset
callback") skips data
On Fri, 08 Mar 2019 06:53:02 PST (-0800), Christoph Hellwig wrote:
On Thu, Mar 07, 2019 at 03:56:34PM -0800, Joe Perches wrote:
IS_ENABLED should generally use CONFIG_ prefaced symbols and
it doesn't appear as if there is a CMODEL_MEDLOW define.
Signed-off-by: Joe Perches
Looks good,
5.1.0-rc2-next-20190329
[8.168722] ==
[8.168723] WARNING: possible circular locking dependency detected
[8.168724] 5.1.0-rc2-next-20190329-dbg-00014-g4d25d68aaf88-dirty #3228 Not
tainted
[8.168725
On 03/29/19 at 03:25pm, Pingfan Liu wrote:
> On Fri, Mar 29, 2019 at 2:27 PM Baoquan He wrote:
> >
> > On 03/29/19 at 01:45pm, Pingfan Liu wrote:
> > > On Fri, Mar 22, 2019 at 4:34 PM Baoquan He wrote:
> > > >
> > > > On 03/22/19 at 03:52pm, Baoquan He wrote:
> > > > > On 03/22/19 at 03:43pm,
On 3/29/2019 4:39 AM, Jann Horn wrote:
sparse complains that LOADED_MM_SWITCHING's definition casts an int to a
pointer:
arch/x86/mm/tlb.c:409:17: warning: non size-preserving integer to pointer
cast
Use a pointer-sized integer constant instead.
Signed-off-by: Jann Horn
Reviewed-by:
Use the runtime-detected denali->nbanks instead of hard-coded
DENALI_NR_BANKS (=4).
The actual number of banks depends on the IP configuration, and
can be less than DENALI_NR_BANKS. It is pointless to touch
registers of unsupported banks.
Signed-off-by: Masahiro Yamada
---
Changes in v4: None
Since (u32 *) can accept an opaque pointer, the explicit casting
from (void *) to (u32 *) is redundant. Change the function argument type
to remove the casts.
Signed-off-by: Masahiro Yamada
---
Changes in v4: None
Changes in v3: None
Changes in v2: None
drivers/mtd/nand/raw/denali.c | 12
As Documentation/process/coding-style.rst says, choose label names
which say what the goto does. The out_ label style is already
used in denali_dt.c. Rename likewise for denali_pci.c
Signed-off-by: Masahiro Yamada
---
Changes in v4: None
Changes in v3: None
Changes in v2: None
Eliminate the following reports from 'scripts/checkpatch.pl --strict'.
CHECK: Prefer kernel type 'u8' over 'uint8_t'
CHECK: Prefer kernel type 'u32' over 'uint32_t'
CHECK: Alignment should match open parenthesis
I slightly changed denali_check_erased_page() to shorten it.
Signed-off-by:
With the recent refactoring, the NAND driver hooks now take a pointer
to nand_chip. Add to_denali() in order to convert (struct nand_chip *)
to (struct denali_nand_info *) directly. It is more useful than the
current mtd_to_denali().
I changed some helper functions to take (struct nand_chip *).
The Denali IP adopts the syndrome page layout (payload and ECC are
interleaved). The *_page_raw() and *_oob() callbacks are complicated
because they must hide the underlying layout used by the hardware,
and always return contiguous in-band and out-of-band data.
Currently, similar code is
Implement ->exec_op(), and remove the deprecated hooks.
Signed-off-by: Masahiro Yamada
---
Changes in v4:
- add denali_exec_in() and denali_exec_out()
- avoid ternary operator to select function
Changes in v3:
- Fix byte-swap in denali_exec_in16()
Changes in v2: None
Currently, this driver sticks to the legacy NAND model because it was
upstreamed before commit 2d472aba15ff ("mtd: nand: document the NAND
controller/NAND chip DT representation"). However, relying on the
dummy_controller is already deprecated.
Switch over to the new controller/chip
Use 'bool' type for the following boolean parameters.
- write (write or read?)
- dma_avail (DMA engine available or not?)
Signed-off-by: Masahiro Yamada
---
Changes in v4: None
Changes in v3: None
Changes in v2:
- Use bool for dma_avail as well
drivers/mtd/nand/raw/denali.c | 23
I took time for the Denali driver to catch up with the latest framework.
- switch over to exec_op() and remove legacy hooks
- separate controller/chips
- various cleanups
Major changes in v4:
- Add denali_exec_out() and denali_exec_in()
in order to make denali_exec_instr() readable
On Fri, Mar 29, 2019 at 2:27 PM Baoquan He wrote:
>
> On 03/29/19 at 01:45pm, Pingfan Liu wrote:
> > On Fri, Mar 22, 2019 at 4:34 PM Baoquan He wrote:
> > >
> > > On 03/22/19 at 03:52pm, Baoquan He wrote:
> > > > On 03/22/19 at 03:43pm, Pingfan Liu wrote:
> > > > > > > +/* parse crashkernel=x@y
On Thu, 28 Mar 2019 23:50:09 PDT (-0700), a...@brainfault.org wrote:
Hi Palmer,
On Fri, Mar 29, 2019 at 11:48 AM Palmer Dabbelt wrote:
On Fri, 22 Mar 2019 06:25:09 PDT (-0700), Christoph Hellwig wrote:
> Looks good,
>
> Reviewed-by: Christoph Hellwig
Thanks. I've added this to my fixes
Hi Miquel,
On Fri, Mar 15, 2019 at 5:34 PM Miquel Raynal wrote:
>
> Hi Masahiro,
>
> Masahiro Yamada wrote on Thu, 14 Mar
> 2019 17:24:41 +0900:
>
> > Hi Miquel,
> >
> > On Tue, Mar 12, 2019 at 10:13 PM Miquel Raynal
> > wrote:
> > >
> > > Hi Masahiro,
> > >
> > > Masahiro Yamada wrote on
There is no need to enable release interrupt and disable depress
interrupt in event check, as a timer is setup for checking these
events rather than interrupts.
Signed-off-by: Anson Huang
---
drivers/input/keyboard/imx_keypad.c | 5 -
1 file changed, 5 deletions(-)
diff --git
There are several scenarios that keyboard can NOT wake up system
from suspend, e.g., if a keyboard is depressed between system
device suspend phase and device noirq suspend phase, the keyboard
ISR will be called and both keyboard depress and release interrupts
will be disabled, then keyboard will
On Fri, Mar 29, 2019 at 07:51:07AM +0100, Marek Behun wrote:
> > If this is just for kernfs, and you have your own filesystem, sure, we
> > can probably do something here. But if this is for sysfs, no, you all
> > need to keep to the "one value per file" rule that we have there
> > please.
>
>
> If this is just for kernfs, and you have your own filesystem, sure, we
> can probably do something here. But if this is for sysfs, no, you all
> need to keep to the "one value per file" rule that we have there
> please.
Greg, the file satisfies the "one value per file" rule. That value is
the
Hi Palmer,
On Fri, Mar 29, 2019 at 11:48 AM Palmer Dabbelt wrote:
>
> On Fri, 22 Mar 2019 06:25:09 PDT (-0700), Christoph Hellwig wrote:
> > Looks good,
> >
> > Reviewed-by: Christoph Hellwig
>
> Thanks. I've added this to my fixes list for the next RC.
I have another RC fix as well:
"[PATCH
Since 25aaa75df1e6 SDMA driver uses clock rates of "ipg" and "ahb"
clock to determine if it needs to configure the IP block as operating
at 1:1 or 1:2 clock ratio (ACR bit in SDMAARM_CONFIG). Specifying both
clocks as IMX5_CLK_SDMA results in driver incorrectly thinking that
ratio is 1:1 which
Since 25aaa75df1e6 SDMA driver uses clock rates of "ipg" and "ahb"
clock to determine if it needs to configure the IP block as operating
at 1:1 or 1:2 clock ratio (ACR bit in SDMAARM_CONFIG). Specifying both
clocks as IMX5_CLK_SDMA results in driver incorrectly thinking that
ratio is 1:1 which
Since 25aaa75df1e6 SDMA driver uses clock rates of "ipg" and "ahb"
clock to determine if it needs to configure the IP block as operating
at 1:1 or 1:2 clock ratio (ACR bit in SDMAARM_CONFIG). Specifying both
clocks as IMX6UL_CLK_SDMA results in driver incorrectly thinking that
ratio is 1:1 which
Since 25aaa75df1e6 SDMA driver uses clock rates of "ipg" and "ahb"
clock to determine if it needs to configure the IP block as operating
at 1:1 or 1:2 clock ratio (ACR bit in SDMAARM_CONFIG). Specifying both
clocks as IMX5_CLK_SDMA results in driver incorrectly thinking that
ratio is 1:1 which
801 - 900 of 920 matches
Mail list logo
