On 23/07/2019 02.38, Joe Perches wrote:
> Several uses of strlcpy and strscpy have had defects because the
> last argument of each function is misused or typoed.
>
> Add macro mechanisms to avoid this defect.
>
> stracpy (copy a string to a string array) must have a string
> array as the first ar
On Tue, Jul 16, 2019 at 01:43:31PM +, Pramod Kumar wrote:
> ls1046afrwy board is based on nxp ls1046a SoC.
> Board support's 4GB ddr memory, i2c, microSD card,
> serial console,qspi nor flash,ifc nand flash,qsgmii network interface,
> usb 3.0 and serdes interface to support two x1gen3 pcie inte
On Tue, Jul 16, 2019 at 01:43:27PM +, Pramod Kumar wrote:
> Add "fsl,ls1046a-frwy" bindings for ls1046afrwy board based on ls1046a SoC
>
> Signed-off-by: Vabhav Sharma
> Signed-off-by: Pramod Kumar
> Reviewed-by: Rob Herring
Applied, thanks.
Add SPDX identifiers to all remaining files in mt76/
Signed-off-by: Ryder Lee
---
drivers/net/wireless/mediatek/mt76/agg-rx.c | 13 +
drivers/net/wireless/mediatek/mt76/debugfs.c| 13 +
drivers/net/wireless/mediatek/mt76/dma.c| 13 +
Hi Dmitry,
at 16:17, Dmitry Torokhov wrote:
Hi Kai-Heng,
On Mon, Jul 22, 2019 at 03:40:55PM +0800, Kai-Heng Feng wrote:
There are some new HP laptops with Elantech touchpad don't support
multitouch.
Currently we use ETP_NEW_IC_SMBUS_HOST_NOTIFY() to check if SMBus is
supported, but in addit
Only when calling the poll syscall the first time can user
receive POLLPRI correctly. After that, user always fails to
acquire the event signal.
Reproduce case:
1. Get the monitor code in Documentation/accounting/psi.txt
2. Run it, and wait for the event triggered.
3. Kill and restart the process.
On Mon, 22 Jul 2019, Davidlohr Bueso wrote:
> ping (with the merge window now closed).
-ENOSUCHPATCH
Can you please repost?
Thanks,
tglx
* Johannes Berg [190723 05:08]:
> Hi,
>
> > Looks like this one crept back as the fix is missing from v5.3-rc1.
> >
> > Forgot to include in the pull request?
>
> More like forgot to send the pull request, my bad. I eventually realized
> a couple of days ago and it'll be coming upstream soon. S
On Tue, 23 Jul 2019, Masahiro Yamada wrote:
> Right.
> I was able to build with ld.gold
>
> So, we can use gold, depending on the kernel configuration.
That's exactly the problem. It breaks with random kernel configurations
which is not acceptable except for people who know what they are doing.
Hello Steven,
On 07/22/2019 09:11 PM, Steven Price wrote:
> This is a slight reworking and extension of my previous patch set
> (Convert x86 & arm64 to use generic page walk), but I've continued the
> version numbering as most of the changes are the same. In particular
> this series ends with a ge
Hello,
syzbot found the following crash on:
HEAD commit:7b5cf701 Merge branch 'sched-urgent-for-linus' of git://gi..
git tree: net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=145c4d3460
kernel config: https://syzkaller.appspot.com/x/.config?x=9aec8cb13b5f7389
da
Hello,
syzbot found the following crash on:
HEAD commit:66b5f1c4 net-ipv6-ndisc: add support for RFC7710 RA Captiv..
git tree: bpf-next
console output: https://syzkaller.appspot.com/x/log.txt?x=15513e7860
kernel config: https://syzkaller.appspot.com/x/.config?x=9aec8cb13b5f7389
da
Hello,
syzbot found the following crash on:
HEAD commit:12185dfe bonding: Force slave speed check after link state..
git tree: net
console output: https://syzkaller.appspot.com/x/log.txt?x=1299b07c60
kernel config: https://syzkaller.appspot.com/x/.config?x=9aec8cb13b5f7389
dashboa
commit 963545357202 ("fuse: reduce allocation size for splice_write")
changed size of bufs array, so first BUG_ON should be corrected too.
Second BUG_ON become useless, first one also includes the second check:
any unsigned nbuf value cannot be less than 0.
Fixes: 963545357202 ("fuse: reduce alloc
On Mon, Jul 15, 2019 at 12:43:04PM +0200, Guido Günther wrote:
> Now that the driver is in linux-next as of 20190624 let's have a DT node
> for the i.MX8MQ and enable it on the Librem 5 devkit.
>
> Changes from v1:
> - Add Acked-by: form Angus, thanks!
You do not need to send a new version for ju
The isolate counting is pecpu counter so it would be not huge gain
to work them by batch. Rather than complicating to make them batch,
let's make it more stright-foward via adding the counting logic
into [isolate|putback]_lru_page API.
* v1
* fix accounting bug - Hillf
Link: http://lkml.kernel.o
There are many common parts between MADV_COLD and MADV_PAGEOUT.
This patch factor them out to save code duplication.
Suggested-by: Johannes Weiner
Acked-by: Michal Hocko
Signed-off-by: Minchan Kim
---
mm/madvise.c | 193 ---
1 file changed, 46 in
When a process expects no accesses to a certain memory range
for a long time, it could hint kernel that the pages can be
reclaimed instantly but data should be preserved for future use.
This could reduce workingset eviction so it ends up increasing
performance.
This patch introduces the new MADV_P
The local variable references in shrink_page_list is PAGEREF_RECLAIM_CLEAN
as default. It is for preventing to reclaim dirty pages when CMA try to
migrate pages. Strictly speaking, we don't need it because CMA didn't allow
to write out by .may_writepage = 0 in reclaim_clean_pages_from_list.
Moreov
This patch is part of previous series:
https://lore.kernel.org/lkml/20190531064313.193437-1-minc...@kernel.org/
Originally, it was created for external madvise hinting feature.
https://lkml.org/lkml/2019/5/31/463
Michal wanted to separte the discussion from external hinting interface
so this patch
Hi,
On Mon, Jul 15, 2019 at 01:12:45PM +0100, Sean Young wrote:
> On Sun, Jul 14, 2019 at 04:32:22PM +0200, Clément Péron wrote:
> > Hi Sean,
> >
> > You acked the whole v3 series but this patch has been introduced in v5
> > could you ack this one too?
>
> Acked-by: Sean Young
So who's tree sh
When a process expects no accesses to a certain memory range, it could
give a hint to kernel that the pages can be reclaimed when memory pressure
happens but data should be preserved for future use. This could reduce
workingset eviction so it ends up increasing performance.
This patch introduces
On Mon, Jul 15, 2019 at 02:55:43AM +, Peng Fan wrote:
> From: Peng Fan
>
> The AUDIO PLL max support 650M, so the original clk settings violate
> spec. This patch makes the output 786432000 -> 393216000,
> and 722534400 -> 361267200 to aligned with NXP vendor kernel without any
> impact on au
--
Guten Tag.
Benötigen Sie ein dringendes Darlehen für Geschäft, Investition und
Projekt?
Wir können Ihre Kreditgenehmigung in weniger als 24 Stunden bearbeiten.
Und unsere Darlehensverzinsung beträgt 1,3% jährlich.
Kontaktieren Sie uns jetzt, indem Sie sich unten bewerben:
Vollständiger N
CPUFREQ_NOTIFY is going to get removed soon, lets use
CPUFREQ_CREATE_POLICY instead of that here. CPUFREQ_CREATE_POLICY is
called only once (which is exactly what we want here) for each cpufreq
policy when it is first created.
Signed-off-by: Viresh Kumar
---
drivers/base/arch_topology.c | 2 +-
Update documentation with the recent policy notifier updates.
Signed-off-by: Viresh Kumar
---
Documentation/cpu-freq/core.txt | 16
1 file changed, 4 insertions(+), 12 deletions(-)
diff --git a/Documentation/cpu-freq/core.txt b/Documentation/cpu-freq/core.txt
index 55193e680250
The cpufreq core now takes the min/max frequency constraints via QoS
requests and the CPUFREQ_ADJUST notifier shall get removed later on.
Switch over to using the QoS request for maximum frequency constraint
for windfarm_cpufreq_clamp driver.
Signed-off-by: Viresh Kumar
---
drivers/macintosh/wi
The cpufreq core now takes the min/max frequency constraints via QoS
requests and the CPUFREQ_ADJUST notifier shall get removed later on.
Switch over to using the QoS request for maximum frequency constraint
for acpi driver.
Signed-off-by: Viresh Kumar
---
drivers/acpi/processor_driver.c | 44
No driver makes reference to these events now, remove them and the code
related to them.
Signed-off-by: Viresh Kumar
---
drivers/cpufreq/cpufreq.c | 36 +++-
include/linux/cpufreq.h | 6 ++
2 files changed, 9 insertions(+), 33 deletions(-)
diff --git a/dri
This reverts commit f9f41e3ef99ac9d4e91b07634362e393fb929aad.
We have a new use case for policy create/remove notifiers (for
allocating/freeing QoS requests per policy), lets add them back.
Signed-off-by: Viresh Kumar
---
drivers/cpufreq/cpufreq.c | 15 ++-
include/linux/cpufreq.h
Hello,
Now that cpufreq core supports taking QoS requests for min/max cpu
frequencies, lets migrate rest of the users to using them instead of the
policy notifiers.
The CPUFREQ_NOTIFY and CPUFREQ_ADJUST events of the policy notifiers are
removed as a result, but we have to add CPUFREQ_CREATE_POLI
The cpufreq core now takes the min/max frequency constraints via QoS
requests and the CPUFREQ_ADJUST notifier shall get removed later on.
Switch over to using the QoS request for maximum frequency constraint
for cpu_cooling driver.
Signed-off-by: Viresh Kumar
---
drivers/thermal/cpu_cooling.c |
The cpufreq core now takes the min/max frequency constraints via QoS
requests and the CPUFREQ_ADJUST notifier shall get removed later on.
Switch over to using the QoS request for maximum frequency constraint
for ppc_cbe_cpufreq driver.
Signed-off-by: Viresh Kumar
---
drivers/cpufreq/ppc_cbe_cpu
Hi Joel,
On Mon, Jul 22, 2019 at 05:32:04PM -0400, Joel Fernandes (Google) wrote:
> The page_idle tracking feature currently requires looking up the pagemap
> for a process followed by interacting with /sys/kernel/mm/page_idle.
> This is quite cumbersome and can be error-prone too. If between
cum
Forget this patchset. I sent out a new 3 patches.
Thanks
Alex
在 2019/7/22 下午3:38, Alex Shi 写道:
> The irqtime_account_process_tick path was introduced for precise ns irq
> time account from commit abb74cefa9c6 ("sched: Export ns irqtimes
> through /proc/stat") while account_process_tick still u
On Tue, Jul 09, 2019 at 05:20:03PM +0300, Abel Vesa wrote:
> There is no strong reason for this to use CLK_OF_DECLARE instead
> of being a platform driver. Plus, this will now be aligned with the
> other i.MX8M clock drivers which are platform drivers.
>
> In order to make the clock provider a pla
Check the 'current' task in account_idle_ticks is meaningless. So we
could remove irqtime_account_idle_ticks and unify this function.
Signed-off-by: Alex Shi
Cc: Ingo Molnar
Cc: Peter Zijlstra
Cc: Frederic Weisbecker
Cc: Wanpeng Li
Cc: Thomas Gleixner
Cc: linux-kernel@vger.kernel.org
---
ke
The irqtime_account_process_tick path was introduced for precise ns irq
time account from commit abb74cefa9c6 ("sched: Export ns irqtimes
through /proc/stat") while account_process_tick still use jiffes. This
divide isn't necessary especially now both paths are ns precison.
Move out the irqtime_ac
According the comments before this line:
* ksoftirqd time do not get accounted in cpu_softirq_time.
And process in irqtime_account_irq()
I guess the original attempt is to account ksoftirqd into
system time instead of softirq time.
Signed-off-by: Alex Shi
Cc: Ingo Molnar
Cc: Peter Zijlstra
Cc:
On Thu, Jul 11, 2019 at 06:11:50PM +0300, Abel Vesa wrote:
> Now that the i.MX6 and i.MX7 clock drivers have been switched to clk_hw based,
> we can remove the clk based API that is not used by any i.MX clock driver.
>
> The following APIs are going away now:
> - imx_clk_busy_divider
> - imx_clk_b
The "uio_netx" driver is not used in conjunction with the removed netX SoC
support.
It is used to handle netX-Based PCI(e) cards
(https://www.hilscher.com/products/product-groups/pc-cards/) plugged into a PC
or any kind of embedded hardware.
So a removal of this driver would render those extens
On Mon, Jul 22, 2019 at 03:34:13PM -0700, john.hubb...@gmail.com wrote:
> +enum pup_flags_t {
> + PUP_FLAGS_CLEAN = 0,
> + PUP_FLAGS_DIRTY = 1,
> + PUP_FLAGS_LOCK = 2,
> + PUP_FLAGS_DIRTY_LOCK= 3,
> +};
Well, the enum defeats the ease of just being able
On 7/19/2019 10:34 AM, Vinod Koul wrote:
On 05-07-19, 11:45, Sameer Pujar wrote:
Hi Vinod,
What are your final thoughts regarding this?
Hi sameer,
Sorry for the delay in replying
On this, I am inclined to think that dma driver should not be involved.
The ADMAIF needs this configuration and
On Mon, Jul 22, 2019 at 03:11:33PM +0100, Mark Rutland wrote:
> The naming of pgtable_page_{ctor,dtor}() seems to have confused a few
> people, and until recently arm64 used these erroneously/pointlessly for
> other levels of page table.
>
> To make it incredibly clear that these only apply to the
From: Jia He
Commit b92df1de5d28 ("mm: page_alloc: skip over regions of invalid pfns
where possible") optimized the loop in memmap_init_zone(). But it causes
possible panic on x86 due to specific memory mapping on x86_64 which will
skip valid pfns as well, so Daniel Vacek reverted it later.
But
From: Jia He
After skipping some invalid pfns in memmap_init_zone(), there is still
some room for improvement.
E.g. if pfn and pfn+1 are in the same memblock region, we can simply pfn++
instead of doing the binary search in memblock_next_valid_pfn.
Furthermore, if the pfn is in a gap of two mem
Here is new version of "[PATCH v11 0/3] remain and optimize
memblock_next_valid_pfn on arm and arm64" from Jia He, which is suggested
by Ard to respin this patch set [1].
In the new version, I squashed patch 1/3 and patch 2/3 in v11 into
one patch, fixed a bug for possible out of bound accessing t
On Wed, Jul 10, 2019 at 04:13:37AM +, Fancy Fang wrote:
> Rename 'lcdif' pixel clock related names to 'disp' names, since:
>
> First, the lcdif pixel clock is not supplied to LCDIF controller
> directly, but to some LPCG clock in display mix. So rename it to
> 'disp' pixel clock is more accura
On 2019/7/23 下午1:02, Michael S. Tsirkin wrote:
On Tue, Jul 23, 2019 at 11:55:28AM +0800, Jason Wang wrote:
On 2019/7/22 下午4:02, Michael S. Tsirkin wrote:
On Mon, Jul 22, 2019 at 01:21:59PM +0800, Jason Wang wrote:
On 2019/7/21 下午6:02, Michael S. Tsirkin wrote:
On Sat, Jul 20, 2019 at 03:08:
The fix was sent last morning my time:
https://marc.info/?l=linux-scsi&m=156378725427719&w=2
ping (with the merge window now closed).
On Wed, Jul 17, 2019 at 03:14:57PM -0700, Suren Baghdasaryan wrote:
> Hi Minchan,
> Couple comments inline.
> Thanks!
>
> On Sun, Jul 14, 2019 at 4:34 PM Minchan Kim wrote:
> >
> > When a process expects no accesses to a certain memory range, it could
> > give a hint to kernel that the pages can
On 2019/7/23 下午1:01, Michael S. Tsirkin wrote:
On Tue, Jul 23, 2019 at 12:01:40PM +0800, Jason Wang wrote:
On 2019/7/22 下午4:08, Michael S. Tsirkin wrote:
On Mon, Jul 22, 2019 at 01:24:24PM +0800, Jason Wang wrote:
On 2019/7/21 下午8:18, Michael S. Tsirkin wrote:
On Sun, Jul 21, 2019 at 06:02:
> On 22 Jul 2019, at 06.31, Minwoo Im wrote:
>
>>> @@ -,27 +1112,27 @@ static int nvm_init(struct nvm_dev *dev)
>>> int ret = -EINVAL;
>>>
>>> if (dev->ops->identity(dev)) {
>>> - pr_err("nvm: device could not be identified\n");
>>> + pr_err("device could not be i
> -Original Message-
> From: Ondrej Mosnacek [mailto:omosn...@redhat.com]
> Sent: Monday, July 22, 2019 6:48 PM
> To: Gote, Nitin R
> Cc: Kees Cook ; kernel-
> harden...@lists.openwall.com; Paul Moore ;
> Stephen Smalley ; Eric Paris ;
> SElinux list ; Linux kernel mailing list ker...@v
Fix a crash with multipath activated. It happends when ANA log
page is larger than MDTS and because of that ANA is disabled.
The driver then tries to access unallocated buffer when connecting
to a nvme target. The signature is as follows:
[ 300.433586] nvme nvme0: ANA log page size (8208) larger
On Tue, Jul 09, 2019 at 09:19:17AM +0200, Stefan Riedmueller wrote:
> This patchstack adjusts the already existing naming for the PHYTEC
> phyBOARD-Segin to the PHYTEC naming scheme that is already used with the
> phyCORE-i.MX 6 and the phyBOARD-Mira.
>
> Furthermore it introduces some small fixes
On Mon 22 Jul 22:14 PDT 2019, Vinod Koul wrote:
> On 23-07-19, 10:38, Amit Kucheria wrote:
> > On Mon, Jul 22, 2019 at 6:06 PM Vinod Koul wrote:
> > >
> > > Unit name is supposed to be a number, using a macro with hex value is
> >
> > /s/name/address?
>
> Right, will fix.
>
> > > not recommend
From: Sultan Alsawaf
In order to prevent redundant entry creation by racing against itself,
mb_cache_entry_create scans through a hash-list of all current entries
in order to see if another allocation for the requested new entry has
been made. Furthermore, it allocates memory for a new entry befo
On 7/22/19 6:02 PM, Andrew Morton wrote:
On Mon, 22 Jul 2019 09:25:09 +0200 Vlastimil Babka wrote:
since there may be pages off LRU temporarily. We should migrate other
pages if MPOL_MF_MOVE* is specified. Set has_unmovable flag if some
paged could not be not moved, then return -EIO for m
On Mon, Jul 22, 2019 at 2:42 AM Christoph Hellwig wrote:
>
> memremap.c implements MM functionality for ZONE_DEVICE, so it really
> should be in the mm/ directory, not the kernel/ one.
>
> Signed-off-by: Christoph Hellwig
Acked-by: Dan Williams
On Mon, 2019-07-22 at 19:42 -0700, Guenter Roeck wrote:
> On 7/22/19 4:45 PM, James Bottomley wrote:
> > [linux-scsi added to cc]
> > On Mon, 2019-07-22 at 15:21 -0700, Guenter Roeck wrote:
> > > On Sun, Jul 21, 2019 at 02:33:38PM -0700, Linus Torvalds wrote:
> > >
> > > [ ... ]
> > > >
> > > > G
On 23/07/19 1:31 AM, Alan Cooper wrote:
> I'm having a problem with a new SD/MMC controller and PHY in our
> latest SoC's. The issue I'm seeing is that I can't switch into HS400
> mode. This looks like something the driver is doing that doesn't meet
> the JEDEC spec. In the "HS400 timing mode selec
On 23-07-19, 10:38, Amit Kucheria wrote:
> On Mon, Jul 22, 2019 at 6:06 PM Vinod Koul wrote:
> >
> > Unit name is supposed to be a number, using a macro with hex value is
>
> /s/name/address?
Right, will fix.
> > not recommended, so add the value in unit name.
> >
> > arch/arm64/boot/dts/qcom/s
As clocks are registered their parents are resolved and the parent_map
is updated to cache the clk_core objects of each existing parent.
But in the event of a clock being unregistered this cache will carry
dangling pointers if not invalidated, so do this for all children of the
clock being unregist
On Mon, Jul 22, 2019 at 6:06 PM Vinod Koul wrote:
>
> Unit name is supposed to be a number, using a macro with hex value is
/s/name/address?
> not recommended, so add the value in unit name.
>
> arch/arm64/boot/dts/qcom/sdm845-cheza.dtsi:966.16-969.4: Warning
> (unit_address_format): /soc@0/spm
Mikhail Gavrilov writes:
> On Mon, 22 Jul 2019 at 12:53, Huang, Ying wrote:
>>
>> Yes. This is quite complex. Is the transparent huge page enabled in
>> your system? You can check the output of
>>
>> $ cat /sys/kernel/mm/transparent_hugepage/enabled
>
> always [madvise] never
>
>> And, whethe
Hi,
> Looks like this one crept back as the fix is missing from v5.3-rc1.
>
> Forgot to include in the pull request?
More like forgot to send the pull request, my bad. I eventually realized
a couple of days ago and it'll be coming upstream soon. Sorry about
that.
johannes
On Tue, Jul 23, 2019 at 11:55:28AM +0800, Jason Wang wrote:
>
> On 2019/7/22 下午4:02, Michael S. Tsirkin wrote:
> > On Mon, Jul 22, 2019 at 01:21:59PM +0800, Jason Wang wrote:
> > > On 2019/7/21 下午6:02, Michael S. Tsirkin wrote:
> > > > On Sat, Jul 20, 2019 at 03:08:00AM -0700, syzbot wrote:
> > >
On Tue, Jul 23, 2019 at 12:01:40PM +0800, Jason Wang wrote:
>
> On 2019/7/22 下午4:08, Michael S. Tsirkin wrote:
> > On Mon, Jul 22, 2019 at 01:24:24PM +0800, Jason Wang wrote:
> > > On 2019/7/21 下午8:18, Michael S. Tsirkin wrote:
> > > > On Sun, Jul 21, 2019 at 06:02:52AM -0400, Michael S. Tsirkin w
On Mon, 2019-07-22 at 21:35 -0700, Andrew Morton wrote:
> On Mon, 22 Jul 2019 17:38:15 -0700 Joe Perches wrote:
>
> > Several uses of strlcpy and strscpy have had defects because the
> > last argument of each function is misused or typoed.
> >
> > Add macro mechanisms to avoid this defect.
> >
On Mon, 22 Jul 2019 17:38:15 -0700 Joe Perches wrote:
> Several uses of strlcpy and strscpy have had defects because the
> last argument of each function is misused or typoed.
>
> Add macro mechanisms to avoid this defect.
>
> stracpy (copy a string to a string array) must have a string
> array
Hi,
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag,
fixing commit: 240c35a3783a kvm: x86: Use task structs fpu field for user.
The bot has tested the following trees: v5.2.2, v5.1.19.
v5.2.2: Build OK!
v5.1.19: Failed to apply! Possible dependenci
Hi All,
Am facing some issues getting CPU limiting working with cgroups v2. Pl read on
for the details; a solution is much appreciated!
Env: 5.0.0 Linux kernel on x86_64 Fedora 29
When attempting to setup CPU limiting using cgroups v2, I effectively
disabled cgroups v1 by passing
cgroup_no_v1=
Hi all,
Changes since 20190722:
The v4l-dvb tree gained a build failure for which I applied a patch.
The drm-intel tree gained a conflict against the kspp-gustavo tree.
Non-merge commits (relative to Linus' tree): 1453
1509 files changed, 143742 insertions(+), 24819 dele
Commit 415008af3219 ("docs-rst: convert lsm from DocBook to ReST")
removed the last users of this macro.
Signed-off-by: Masahiro Yamada
---
scripts/Kbuild.include | 3 ---
1 file changed, 3 deletions(-)
diff --git a/scripts/Kbuild.include b/scripts/Kbuild.include
index 12666fc922ea..10ba926ae2
On Tue, 2019-07-16 at 09:50 +0800, CK Hu wrote:
> Hi, Weiyi:
>
> On Mon, 2019-07-15 at 17:07 +0800, Weiyi Lu wrote:
> > On Mon, 2019-07-15 at 16:07 +0800, CK Hu wrote:
> > > Hi, Weiyi:
> > >
> > > On Mon, 2019-07-01 at 16:57 +0800, CK Hu wrote:
> > > > Hi, Weiyi:
> > > >
> > > > On Thu, 2019-06-
On 2019/7/22 下午4:08, Michael S. Tsirkin wrote:
On Mon, Jul 22, 2019 at 01:24:24PM +0800, Jason Wang wrote:
On 2019/7/21 下午8:18, Michael S. Tsirkin wrote:
On Sun, Jul 21, 2019 at 06:02:52AM -0400, Michael S. Tsirkin wrote:
On Sat, Jul 20, 2019 at 03:08:00AM -0700, syzbot wrote:
syzbot has bi
On 2019/7/22 下午4:02, Michael S. Tsirkin wrote:
On Mon, Jul 22, 2019 at 01:21:59PM +0800, Jason Wang wrote:
On 2019/7/21 下午6:02, Michael S. Tsirkin wrote:
On Sat, Jul 20, 2019 at 03:08:00AM -0700, syzbot wrote:
syzbot has bisected this bug to:
commit 7f466032dc9e5a61217f22ea34b2df932786bbfc
On 7/22/19 8:24 PM, Masanari Iida wrote:
> This patch fixes some spelling typos in config-bisect.pl
>
> Signed-off-by: Masanari Iida
Acked-by: Randy Dunlap
Thanks.
> ---
> tools/testing/ktest/config-bisect.pl | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/tools
23.07.2019 6:31, Sowjanya Komatineni пишет:
>
> On 7/22/19 8:25 PM, Dmitry Osipenko wrote:
>> 23.07.2019 6:09, Sowjanya Komatineni пишет:
>>> On 7/22/19 8:03 PM, Dmitry Osipenko wrote:
23.07.2019 4:52, Sowjanya Komatineni пишет:
> On 7/22/19 6:41 PM, Dmitry Osipenko wrote:
>> 23.07.20
On Tue, 23 Jul 2019 at 11:21, Chunyan Zhang wrote:
>
> On Tue, 23 Jul 2019 at 11:05, Baolin Wang wrote:
> >
> > Hi Ulf,
> >
> > On Mon, 22 Jul 2019 at 19:54, Ulf Hansson wrote:
> > >
> > > On Wed, 17 Jul 2019 at 04:29, Baolin Wang wrote:
> > > >
> > > > In sdhci_runtime_resume_host() function,
On 7/22/19 8:25 PM, Dmitry Osipenko wrote:
23.07.2019 6:09, Sowjanya Komatineni пишет:
On 7/22/19 8:03 PM, Dmitry Osipenko wrote:
23.07.2019 4:52, Sowjanya Komatineni пишет:
On 7/22/19 6:41 PM, Dmitry Osipenko wrote:
23.07.2019 4:08, Dmitry Osipenko пишет:
23.07.2019 3:58, Dmitry Osipenko
arg2 will never < 0, for its type is 'unsigned long'. So negative
judgment is meaningless.
Signed-off-by: Yang Xu
---
kernel/sys.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/kernel/sys.c b/kernel/sys.c
index 2969304c29fe..399457d26bef 100644
--- a/kernel/sys.c
+++
Hi Rob,
>
> Re: [PATCH v5 2/2] dt-bindings: mtd: Document Macronix raw NAND
controller bindings
>
> On Wed, Jul 03, 2019 at 03:15:44PM +0800, Mason Yang wrote:
> > Document the bindings used by the Macronix raw NAND controller.
> >
> > Signed-off-by: Mason Yang
> > ---
> > Documentation/d
23.07.2019 6:09, Sowjanya Komatineni пишет:
>
> On 7/22/19 8:03 PM, Dmitry Osipenko wrote:
>> 23.07.2019 4:52, Sowjanya Komatineni пишет:
>>> On 7/22/19 6:41 PM, Dmitry Osipenko wrote:
23.07.2019 4:08, Dmitry Osipenko пишет:
> 23.07.2019 3:58, Dmitry Osipenko пишет:
>> 21.07.2019 22:4
This patch fixes some spelling typos in config-bisect.pl
Signed-off-by: Masanari Iida
---
tools/testing/ktest/config-bisect.pl | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/tools/testing/ktest/config-bisect.pl
b/tools/testing/ktest/config-bisect.pl
index 72525426654b..
On Tue, 23 Jul 2019 at 11:05, Baolin Wang wrote:
>
> Hi Ulf,
>
> On Mon, 22 Jul 2019 at 19:54, Ulf Hansson wrote:
> >
> > On Wed, 17 Jul 2019 at 04:29, Baolin Wang wrote:
> > >
> > > In sdhci_runtime_resume_host() function, we will always do software reset
> > > for all, which will cause Spreadt
Hi Russell, Stefano
> Subject: [PATCH] arm: xen: mm: use __GPF_DMA32 for arm64
Any comments?
>
> arm64 shares some code under arch/arm/xen, including mm.c.
> However ZONE_DMA is removed by commit
> ad67f5a6545("arm64: replace ZONE_DMA with ZONE_DMA32").
> So to ARM64, need use __GFP_DMA32.
>
>
Tegra's APB DMA engine updates words counter after each transferred burst
of data, hence it can report transfer's residual with more fidelity which
may be required in cases like audio playback. In particular this fixes
audio stuttering during playback in a chromium web browser. The patch is
based o
Now Terga20 and Tegra30 EMC drivers should provide clock-rounding
functionality using the new Tegra-CLK driver API.
Acked-by: Peter De Schrijver
Signed-off-by: Dmitry Osipenko
---
drivers/memory/tegra/tegra20-emc.c | 50 --
1 file changed, 48 insertions(+), 2 deletio
Turned out that it could take over a millisecond under some circumstances,
like running on a very low CPU/memory frequency. TRM says that handshake
happens when there is a "safe" moment, but not explains exactly what that
moment is. Apparently at least memory should be idling and thus the low
frequ
The "interruptible" variant may error out, the "uninterruptible" not.
Signed-off-by: Dmitry Osipenko
---
drivers/memory/tegra/tegra20-emc.c | 6 +-
1 file changed, 1 insertion(+), 5 deletions(-)
diff --git a/drivers/memory/tegra/tegra20-emc.c
b/drivers/memory/tegra/tegra20-emc.c
index da75
The driver expects certain debug features to be disabled in order to
work properly. Let's disable them explicitly for consistency and to not
rely on a boot state.
Acked-by: Peter De Schrijver
Signed-off-by: Dmitry Osipenko
---
drivers/memory/tegra/tegra20-emc.c | 17 -
1 file ch
A proper External Memory Controller clock rounding and parent selection
functionality is required by the EMC drivers, it is not available using
the generic clock implementation because only the Memory Controller driver
is aware of what clock rates are actually available for a particular
device. EMC
Add binding for the NVIDIA Tegra30 SoC Memory Controller.
Signed-off-by: Dmitry Osipenko
---
.../memory-controllers/nvidia,tegra30-mc.yaml | 173 ++
1 file changed, 173 insertions(+)
create mode 100644
Documentation/devicetree/bindings/memory-controllers/nvidia,tegra30-mc.yaml
The Tegra30 binding will actually differ from the Tegra124 a tad, in
particular the EMEM configuration description. Hence rename the binding
to Tegra124 during of the conversion to YAML.
Signed-off-by: Dmitry Osipenko
---
.../nvidia,tegra124-mc.yaml | 156 ++
..
Timing control debug features should be disabled at a boot time, but you
never now and hence it's better to disable them explicitly because some of
those features are crucial for the driver to do a proper thing.
Acked-by: Peter De Schrijver
Signed-off-by: Dmitry Osipenko
---
drivers/memory/tegr
Introduce driver for the External Memory Controller (EMC) found on Tegra30
chips, it controls the external DRAM on the board. The purpose of this
driver is to program memory timing for external memory on the EMC clock
rate change.
Acked-by: Peter De Schrijver
Signed-off-by: Dmitry Osipenko
---
During boot print how many memory timings got the driver and what's the
RAM code. This is a very useful information when something is wrong with
boards memory timing.
Suggested-by: Marc Dietrich
Signed-off-by: Dmitry Osipenko
---
drivers/memory/tegra/tegra20-emc.c | 7 +++
1 file changed, 7
1 - 100 of 1180 matches
Mail list logo
