Hello,
I encountered a regression in current (post-5.0) mainline kernel which I
bisected to commit 1aec4211204d ("parport: daisy: use new parport device
model"). Running "modprobe parport_pc" hangs up:
tweed:~ # ps ax | grep modprobe
1206 pts/0D+ 0:00 modprobe parport_pc
1209 ?S
On Tue, Mar 12, 2019 at 10:11 PM Tetsuo Handa
wrote:
>
> On 2019/03/13 2:15, Dmitry Vyukov wrote:
> >> Also, this bisection is finding multiple different crash patterns, which
> >> suggests that the crashed tests are not giving correct feedback to syzbot.
> >
> > Treating different crashes as just
On Wed, Mar 13, 2019 at 8:26 AM Kees Cook wrote:
>
> On Mon, Mar 11, 2019 at 1:42 PM syzbot
> wrote:
> > C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17ee410b20
> > [...]
> > [ cut here ]
> > Bad or missing usercopy whitelist? Kernel memory exposure attemp
Hi Matthias,
On 2019-03-12 22:29, Matthias Kaehlcke wrote:
+DT folks
Please add them in future versions (script/scripts/get_maintainer.pl
should have listed them)
[Harish] -- Will add them in new version of patches.
On Tue, Mar 12, 2019 at 05:52:59PM +0530, Harish Bandi wrote:
This patch
On Mon, Mar 11, 2019 at 1:42 PM syzbot
wrote:
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17ee410b20
> [...]
> [ cut here ]
> Bad or missing usercopy whitelist? Kernel memory exposure attempt detected
> from SLAB object 'fanotify_event' (offset 40, size
Hi Matthias,
On 2019-03-12 21:59, Matthias Kaehlcke wrote:
Hi Harish,
On Tue, Mar 12, 2019 at 05:52:58PM +0530, Harish Bandi wrote:
Added new compatible for wcn3998 and corresponding voltage
and current values to wcn3998 compatible.
Changed driver code to support wcn3998
Signed-off-by: Hari
On 2019-03-12 12:47, MyungJoo Ham wrote:
From: Saravana Kannan
If the new governor fails to start, switch back to old governor so
that the
devfreq state is not left in some weird limbo.
[Mjungjoo: assume fatal on revert failure and set df->governor to
NULL]
Signed-off-by: Sibi Sankar
Sign
On Tue, Mar 12, 2019 at 12:59:34PM -0700, Mike Kravetz wrote:
> On 3/11/19 2:36 AM, Peter Xu wrote:
> >
> > The "kvm" entry is a bit special here only to make sure that existing
> > users like QEMU/KVM won't break by this newly introduced flag. What
> > we need to do is simply set the "unprivileg
On Tue, Mar 12, 2019 at 3:45 PM Aubrey Li wrote:
>
> On Tue, Mar 12, 2019 at 7:36 AM Subhra Mazumdar
> wrote:
> >
> >
> > On 3/11/19 11:34 AM, Subhra Mazumdar wrote:
> > >
> > > On 3/10/19 9:23 PM, Aubrey Li wrote:
> > >> On Sat, Mar 9, 2019 at 3:50 AM Subhra Mazumdar
> > >> wrote:
> > >>> expec
On 13.03.19 00:54, Andrew Jeffery wrote:
>
> For the ASPEED bits:
>
> Acked-by: Andrew Jeffery
>
shall I split the patch ?
--mtx
--
Enrico Weigelt, metux IT consult
Free software and Linux embedded engineering
i...@metux.net -- +49-151-27565287
If the driver is active till late suspend, where runtime PM cannot run,
force suspend is essential in such case to put the device in low power
state. Thus pm_runtime_force_suspend and pm_runtime_force_resume are
used as system sleep callbacks during system wide PM transitions.
Signed-off-by: Samee
adma driver is using pm_clk_*() interface for managing clock resources.
With this it is observed that clocks remain ON always. This happens on
Tegra devices which use BPMP co-processor to manage clock resources,
where clocks are enabled during prepare phase. This is necessary because
clocks to BPMP
Ping !!
> -Original Message-
> From: Nava kishore Manne
> Sent: Tuesday, March 5, 2019 3:12 PM
> To: 'Rob Herring'
> Cc: mark.rutl...@arm.com; Michal Simek ; Rajan Vaja
> ; linux-arm-ker...@lists.infradead.org; linux-
> ker...@vger.kernel.org; devicet...@vger.kernel.org; Jolly Shah
> ; ch
Zdravstvujte Vas interesuyut klientskie bazy dannyh?
Currently we use the page->lru list for maintaining lists of slabs. We
have a list_head in the page structure (slab_list) that can be used for
this purpose. Doing so makes the code cleaner since we are not
overloading the lru list.
The slab_list is part of a union within the page struct (include
Currently we use the page->lru list for maintaining lists of slabs. We
have a list_head in the page structure (slab_list) that can be used for
this purpose. Doing so makes the code cleaner since we are not
overloading the lru list.
The slab_list is part of a union within the page struct (include
SLUB allocator makes heavy use of ifdef/endif pre-processor macros.
The pairing of these statements is at times hard to follow e.g. if the
pair are further than a screen apart or if there are nested pairs. We
can reduce cognitive load by adding a comment to the endif statement of
form
#ifd
We now use the slab_list list_head instead of the lru list_head. This
comment has become stale.
Remove stale comment from page struct slab_list list_head.
Signed-off-by: Tobin C. Harding
---
include/linux/mm_types.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/li
Currently we use the page->lru list for maintaining lists of slabs. We
have a list_head in the page structure (slab_list) that can be used for
this purpose. Doing so makes the code cleaner since we are not
overloading the lru list.
The slab_list is part of a union within the page struct (include
Currently the slab allocators (ab)use the struct page 'lru' list_head.
We have a list head for slab allocators to use, 'slab_list'.
Clean up all three allocators by using the 'slab_list' list_head instead
of overloading the 'lru' list_head.
Patch 1 - Makes no code changes, adds comments to #endi
--
Goedendag,
Het is ons een genoegen u te schrijven met betrekking tot het
verstrekken van leningen per postadvertentie. Simple Federal Credit
Union, We opereren onder een korte, duidelijke en begrijpelijke algemene
voorwaarden. We verstrekken leningen tegen een lage rente van 3%.
Hi,
Thanks for the work on this system call! I am interested in making use
of it in my process supervisor. It works pretty well and avoids the
long-standing issue of PID reuse.
One thing that instantly came to mind is to be able to delegate killing
to some third process depending on the conf
On 10/03/19 8:36 PM, Axel Lin wrote:
This driver is using devm_regulator_register() so it is not necessary
to save *rdev for clean up. Actually the pmic->rdev[id] is not used now.
Reviewed-by: Keerthy
Signed-off-by: Axel Lin
---
drivers/regulator/palmas-regulator.c | 12
On 01/03/19 11:46 AM, Axel Lin wrote:
LP87565_BUCK_0 is missed, fix it.
Fixes: f0168a9bf ("regulator: lp87565: Add support for lp87565 PMIC regulators")
Signed-off-by: Axel Lin
---
Hi J Keerthy,
While reading the code, it seems strange that LP87565_BUCK_0 is never used.
So current code only
aconnect bus driver is using pm_clk_*() interface for managing clocks.
With this, clocks seem to be always ON. This happens on Tegra devices
which use BPMP co-processor to manage clock resources, where clocks
are enabled during prepare phase. This is necessary because calls to
BPMP are always block
pm_runtime_force_suspend() and pm_runtime_force_resume() are used as system
sleep noirq suspend and resume callbacks. If the driver is active till late
suspend, where runtime PM cannot run, force suspend is essential for the
device. This makes sure that the device is put into low power state during
crashkernel=x@y option may fail to reserve the required memory region if
KASLR puts kernel into the region. To avoid this uncertainty, making KASLR
skip the required region.
Signed-off-by: Pingfan Liu
Cc: Thomas Gleixner
Cc: Ingo Molnar
Cc: Borislav Petkov
Cc: "H. Peter Anvin"
Cc: Baoquan He
On Tue, 12 Mar 2019 at 22:44, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.19.29 release.
> There are 149 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.
>
> Re
On Tue, 12 Mar 2019 at 22:47, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.14.106 release.
> There are 135 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.
>
> R
On Tue, 12 Mar 2019 at 22:48, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.9.163 release.
> There are 96 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
On Sat, Mar 2, 2019 at 7:33 PM Pierre-Jean Texier wrote:
>
> PMIC swbst regulator is used for the MikroBUS socket (pin +5V).
>
> We have to set the regulator to "boot-on" and "always-on"
> to output a voltage of 5V on this socket.
>
> Signed-off-by: Pierre-Jean Texier
Reviewed-by: Fabio Estevam
Oren,
On 3/11/19 6:38 PM, Suthikulpanit, Suravee wrote:
> However, looking a bit more closely, I notice the logic in
> svm_deliver_avic_intr()
> should also have been changed from kvm_vcpu_wake_up() to kvm_vcpu_kick()
> since the latter will result in clearing the IRR bit for the IPI vector
> whe
Request to backport 0237199186e7a4aa5310741f0a6498a20c820fd7 to 4.14 branch
Thanks!
Alec
On 3/7/2019 11:46 PM, Sowjanya Komatineni wrote:
On 3/6/2019 6:30 PM, Adrian Hunter wrote:
On 2/03/19 7:20 AM, Sowjanya Komatineni wrote:
This patch adds a quirk for setting CMD_TIMING to 1 in descriptor for
DCMD with R1B response type to allow the command to be sent to device
during data act
On (03/12/19 16:15), John Ogness wrote:
> > I suggest the following way forward (separate patchsets):
> >
> > 1. Replace log buffer (least controversial thing)
>
> Yes. I will post a series that only implements the ringbuffer using your
> simplified API. That will be enough to remove printk_sa
On (03/12/19 13:38), Petr Mladek wrote:
> > Hmm. OK. So one of the things with printk is that it's fully sequential.
> > We call console drivers one by one. Slow consoles can affect what appears
> > on the fast consoles; fast console have no impact on slow ones.
> >
> > call_console_drivers()
The commit f1dd2cd13c4b ("mm, memory_hotplug: do not associate hotadded
memory to zones until online") introduced move_pfn_range_to_zone() which
calls memmap_init_zone() during onlining a memory block.
memmap_init_zone() will reset pagetype flags and makes migrate type to
be MOVABLE.
However, in _
Andrew you will not be pushing this patchset in 5.1 ?
Cheers,
Jérôme
Hi Rob,
Thanks for your reply, I have some questions on that:
在 2019/3/12 下午8:28, Rob Herring 写道:
On Tue, Mar 12, 2019 at 4:16 AM Jiaxun Yang wrote:
Add devicetree skeleton for ls1b and ls1c
Signed-off-by: Jiaxun Yang
---
+/ {
+ model = "Loongson LS1B";
+ compatible = "loongson
On Tue, Mar 12, 2019 at 1:34 PM Dave Chinner wrote:
>
> On Tue, Mar 12, 2019 at 12:30:52PM -0700, Dan Williams wrote:
> > On Tue, Mar 12, 2019 at 12:06 PM Jerome Glisse wrote:
> > > On Tue, Mar 12, 2019 at 09:06:12AM -0700, Dan Williams wrote:
> > > > On Tue, Mar 12, 2019 at 8:26 AM Jerome Glisse
On Tue, Mar 12, 2019 at 05:46:51PM -0700, Dan Williams wrote:
> On Tue, Mar 12, 2019 at 5:10 PM Jerome Glisse wrote:
> >
> > On Tue, Mar 12, 2019 at 02:52:14PM -0700, Andrew Morton wrote:
> > > On Tue, 12 Mar 2019 12:30:52 -0700 Dan Williams
> > > wrote:
> > >
> > > > On Tue, Mar 12, 2019 at 12:
On Tue, Mar 12, 2019 at 5:10 PM Jerome Glisse wrote:
>
> On Tue, Mar 12, 2019 at 02:52:14PM -0700, Andrew Morton wrote:
> > On Tue, 12 Mar 2019 12:30:52 -0700 Dan Williams
> > wrote:
> >
> > > On Tue, Mar 12, 2019 at 12:06 PM Jerome Glisse wrote:
> > > > On Tue, Mar 12, 2019 at 09:06:12AM -0700
On 3/12/19 8:30 AM, Ira Weiny wrote:
On Wed, Mar 06, 2019 at 03:54:55PM -0800, john.hubb...@gmail.com wrote:
From: John Hubbard
Introduces put_user_page(), which simply calls put_page().
This provides a way to update all get_user_pages*() callers,
so that they call put_user_page(), instead of
On Tue, Mar 12, 2019 at 1:19 PM Angus Ainslie wrote:
>
> Hi Andrey,
>
> On 2019-03-11 19:35, Andrey Smirnov wrote:
> > On Mon, Mar 11, 2019 at 2:35 PM Angus Ainslie (Purism)
> > wrote:
> >>
> >> These are the TMU nodes from the NXP vendor kernel
> >>
> >
> > Hey Angus,
> >
> > TMU block supports
On Tue, Mar 12, 2019 at 02:52:14PM -0700, Andrew Morton wrote:
> On Tue, 12 Mar 2019 12:30:52 -0700 Dan Williams
> wrote:
>
> > On Tue, Mar 12, 2019 at 12:06 PM Jerome Glisse wrote:
> > > On Tue, Mar 12, 2019 at 09:06:12AM -0700, Dan Williams wrote:
> > > > On Tue, Mar 12, 2019 at 8:26 AM Jerom
> Make both variables static.
"pti_set_kernel_image_nonglobal(void)" is an awfully funny looking
variable. ;)
> Signed-off-by: Valdis Kletnieks
>
> ---
> diff --git a/arch/x86/mm/pti.c b/arch/x86/mm/pti.c
> index 4fee5c3003ed..139b28a01ce4 100644
> --- a/arch/x86/mm/pti.c
> +++ b/arch/x86/mm/pt
On Tue, 12 Mar 2019, at 00:26, Enrico Weigelt, metux IT consult wrote:
> Formatting of Kconfig files doesn't look so pretty, so let the
> Great White Handkerchief come around and clean it up.
>
> Signed-off-by: Enrico Weigelt, metux IT consult
> ---
> arch/arm/Kconfig | 24 ++
On Tue, Mar 12, 2019 at 3:18 PM Linus Torvalds
wrote:
>
> On Tue, Mar 12, 2019 at 8:13 AM Richard Weinberger wrote:
> >
> > git://git.infradead.org/linux-ubifs.git tags/upstream-5.1-rc1
>
> Pulling this thing is taking forever for me. I can _ping_ the site,
> but the "git pull" has been hanging
On Wed, Mar 06, 2019 at 03:54:55PM -0800, john.hubb...@gmail.com wrote:
> From: John Hubbard
>
> Introduces put_user_page(), which simply calls put_page().
> This provides a way to update all get_user_pages*() callers,
> so that they call put_user_page(), instead of put_page().
So I've been runn
On Mon, Mar 11, 2019 at 7:06 AM Georgi Djakov wrote:
>
> Include the device tree header for the on-chip interconnect endpoint
> resources on sdm845 devices. This will allow using the "interconnects"
> property in DT nodes to describe the interconnect path resources they use.
>
> The sdm845 interco
On Wed, Mar 13, 2019 at 09:11:13AM +1100, Dave Chinner wrote:
> On Tue, Mar 12, 2019 at 03:39:33AM -0700, Ira Weiny wrote:
> > IMHO I don't think that the copy_file_range() is going to carry us through
> > the
> > next wave of user performance requirements. RDMA, while the first, is not
> > the
45189a1998e00f6375ebd49d1e18161acddd73de:
selinux: fix avc audit messages (2019-02-05 12:34:33 -0500)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/pcmoore/selinux.git
tags/selinux-pr-20190312
for you to fetch changes up to
Rename the misspelled struct 'qca_bardrate' to 'qca_baudrate'
Signed-off-by: Matthias Kaehlcke
---
drivers/bluetooth/btqca.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/bluetooth/btqca.h b/drivers/bluetooth/btqca.h
index c72c56ea7480..6fdc25d7bba7 100644
--- a/dri
stable-rc/linux-4.9.y boot: 92 boots: 1 failed, 91 passed
(v4.9.162-97-g605129cbbd38)
Full Boot Summary:
https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.9.y/kernel/v4.9.162-97-g605129cbbd38/
Full Build Summary:
https://kernelci.org/build/stable-rc/branch/linux-4.9.y/kernel/v4.9.162-9
On Tue, Mar 12, 2019 at 2:53 PM David Hildenbrand wrote:
>
> On 12.03.19 22:13, Alexander Duyck wrote:
> > On Tue, Mar 12, 2019 at 12:46 PM Nitesh Narayan Lal
> > wrote:
> >>
> >> On 3/8/19 4:39 PM, Alexander Duyck wrote:
> >>> On Fri, Mar 8, 2019 at 11:39 AM Nitesh Narayan Lal
> >>> wrote:
>
On Tue, Mar 12, 2019 at 2:53 PM Nathan Chancellor
wrote:
>
> After LLVM revision r355672 [1], all known working kernel configurations
> fail to link [2]:
>
> ld: init/do_mounts.o: in function `prepare_namespace':
> do_mounts.c:(.init.text+0x5ca): undefined reference to `bcmp'
> ld: do_mounts.c:(.i
On Tue, 12 Mar 2019 23:46:11 +0100, Pali Rohar said:
> Can you identify in which commit was introduced this problem? If yes,
> then Fixes: keyword should be added into commit message.
I admit not knowing how long that's been there - I mostly found myself
with a large amount of free time, a good s
On Tue, Mar 12, 2019 at 09:33:44AM +0100, 'Dmitry Vyukov' via syzkaller-bugs
wrote:
> On Tue, Mar 12, 2019 at 7:25 AM Andrew Morton
> wrote:
> >
> > On Tue, 12 Mar 2019 07:08:38 +0100 Dmitry Vyukov wrote:
> >
> > > On Tue, Mar 12, 2019 at 12:37 AM Andrew Morton
> > > wrote:
> > > >
> > > > On
On Tuesday 12 March 2019 07:26:06 Valdis Klētnieks wrote:
> Building with W=1 complains:
> CC [M] drivers/platform/x86/dell-rbtn.o
> drivers/platform/x86/dell-rbtn.c:345:5: warning: no previous prototype for
> 'dell_rbtn_notifier_register' [-Wmissing-prototypes]
> 345 | int dell_rbtn_notifier
stable-rc/linux-4.14.y boot: 105 boots: 1 failed, 103 passed with 1
untried/unknown (v4.14.105-136-gf881675936ef)
Full Boot Summary:
https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.14.y/kernel/v4.14.105-136-gf881675936ef/
Full Build Summary:
https://kernelci.org/build/stable-rc/branc
Similar to the memcg's vmstats_percpu, per-memcg per-node stats
consists of percpu- and atomic counterparts, and we do expect
that both coexist during the whole life-cycle of the memcg.
To prepare for a premature release of percpu per-node data,
let's pretend that lruvec_stat_cpu is a rcu-protecte
It's possible to remove a big chunk of the redundant code by making
memcg_flush_offline_percpu() to take cpumask as an argument and flush
percpu data on all cpus belonging to the mask instead of all possible cpus.
Then memcg_hotplug_cpu_dead() can call it with a single CPU bit set.
This approach
Similar to memcg-level statistics, per-node data isn't expected
to be hot after cgroup removal. Switching over to atomics and
prematurely releasing percpu data helps to reduce the memory
footprint of dying cgroups.
Signed-off-by: Roman Gushchin
Acked-by: Johannes Weiner
---
include/linux/memcon
A cgroup can remain in the dying state for a long time, being pinned in the
memory by any kernel object. It can be pinned by a page, shared with other
cgroup (e.g. mlocked by a process in the other cgroup). It can be pinned
by a vfs cache object, etc.
Mostly because of percpu data, the size of a m
Prepare to handle premature release of memcg->vmstats_percpu data.
Currently it's a generic pointer which is expected to be non-NULL
during the whole life time of a memcg. Switch over to the
rcu-protected pointer, and carefully check it for being non-NULL.
This change is a required step towards dy
Flush percpu stats and events data to corresponding before releasing
percpu memory.
Although per-cpu stats are never exactly precise, dropping them on
floor regularly may lead to an accumulation of an error. So, it's
safer to flush them before releasing.
To minimize the number of atomic updates,
Spill percpu stats and events data to corresponding before releasing
percpu memory.
Although per-cpu stats are never exactly precise, dropping them on
floor regularly may lead to an accumulation of an error. So, it's
safer to sync them before releasing.
To minimize the number of atomic updates, l
To reduce the memory footprint of a dying memory cgroup, let's
release massive percpu data (vmstats_percpu) as early as possible,
and use atomic counterparts instead.
A dying cgroup can remain in the dying state for quite a long
time, being pinned in memory by any reference. For example,
if a page
Hi Dmitry,
On Tue, Mar 12, 2019 at 09:21:09AM +0100, 'Dmitry Vyukov' via syzkaller-bugs
wrote:
> On Tue, Mar 12, 2019 at 7:43 AM Eric Biggers wrote:
> >
> > On Mon, Mar 11, 2019 at 11:25:41PM -0700, Andrew Morton wrote:
> > > On Tue, 12 Mar 2019 07:08:38 +0100 Dmitry Vyukov
> > > wrote:
> > >
The pull request you sent on Tue, 12 Mar 2019 16:08:52 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git
> for-5.1-part2-tag
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/92825b0298ca6822085ef483f914b6e0dea9bf66
Thank you!
--
Deet-doot-dot, I
The pull request you sent on Tue, 12 Mar 2019 18:50:17 +0100:
> https://github.com/ceph/ceph-client.git tags/ceph-for-5.1-rc1
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/2b0a80b0d0bb0a3db74588279bf851b28c6c4705
Thank you!
--
Deet-doot-dot, I am a bot.
https://kor
The pull request you sent on Tue, 12 Mar 2019 15:50:59 -0400:
> git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git
> tags/ext4_for_linus
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/a5adcfcad55d5f034b33f79f1a873229d1e77b24
Thank you!
--
Deet-doot-dot, I
The pull request you sent on Tue, 12 Mar 2019 11:46:27 +:
> git://git.linux-nfs.org/projects/trondmy/linux-nfs.git tags/nfs-for-5.1-1
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/1fbf3e48123d701584bc75ccac67ef2fe412ac4c
Thank you!
--
Deet-doot-dot, I am a bot.
The pull request you sent on Tue, 12 Mar 2019 10:03:09 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/vfs.git
> tags/ovl-update-5.1
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/f88c5942cfaf7d55e46d395136cccaca65b2e3bf
Thank you!
--
Deet-doot-dot,
The pull request you sent on Tue, 12 Mar 2019 09:44:49 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse.git
> tags/fuse-update-5.1
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/dfee9c257b102d7c0407629eef2ed32e152de0d2
Thank you!
--
Deet-doot-do
The pull request you sent on Tue, 12 Mar 2019 14:23:59 -0400:
> git://linux-nfs.org/~bfields/linux.git tags/nfsd-5.1
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/ebc551f2b8f905eca0e25c476c1e5c098cd92103
Thank you!
--
Deet-doot-dot, I am a bot.
https://korg.wiki.ke
On Tue, Mar 12, 2019 at 8:13 AM Richard Weinberger wrote:
>
> git://git.infradead.org/linux-ubifs.git tags/upstream-5.1-rc1
Pulling this thing is taking forever for me. I can _ping_ the site,
but the "git pull" has been hanging for a while.
I really tjhink people need to stop using infradead.o
On Tue, Mar 12, 2019 at 03:39:33AM -0700, Ira Weiny wrote:
> IMHO I don't think that the copy_file_range() is going to carry us through the
> next wave of user performance requirements. RDMA, while the first, is not the
> only technology which is looking to have direct access to files. XDP is
> a
Currently, we have to boot RISCV64 kernel from a 2MB aligned physical
address and RISCV32 kernel from a 4MB aligned physical address. This
constraint is because initial pagetable setup (i.e. setup_vm()) maps
entire RAM using hugepages (i.e. 2MB for 3-level pagetable and 4MB for
2-level pagetable).
This patch adds rv32_defconfig for 32bit systems. The only
difference between rv32_defconfig and defconfig is that
rv32_defconfig has CONFIG_ARCH_RV32I=y.
Signed-off-by: Anup Patel
---
arch/riscv/configs/rv32_defconfig | 84 +++
1 file changed, 84 insertions(+)
crea
The setup_vm() must access kernel symbols in a position independent way
because it will be called from head.S with MMU off.
If we compile kernel with cmodel=medany then PC-relative addressing will
be used in setup_vm() to access kernel symbols so it works perfectly fine.
Although, if we compile k
From: Anup Patel
This patchset primarily extends initial page table setup using fixmap
to boot Linux RISC-V kernel (64bit and 32bit) from any 4KB aligned address.
We also add 32bit defconfig to allow people to try 32bit Linux RISC-V
kernel as well.
The patchset is tested on SiFive Unleashed boar
Quoting Patrick Wildt (2019-03-12 13:59:22)
> On Tue, Mar 12, 2019 at 01:39:50PM -0700, Stephen Boyd wrote:
> > Quoting Patrick Wildt (2019-03-12 00:36:54)
> > > On Fri, Mar 08, 2019 at 07:29:05AM -0800, Stephen Boyd wrote:
> > > > It's mostly about making sure that any existing dtbs don't have the
On Tue, Mar 12, 2019 at 09:53:28PM +, Michael Kelley wrote:
> From: gre...@linuxfoundation.org Sent: Tuesday,
> March 12, 2019 2:47 PM
> > >
> > > Michael Kelley (2):
> > > Drivers: hv: Move Hyper-V clockevents code to new clocksource driver
> > > Drivers: hv: Move Hyper-V clocksource co
On 3/11/19 4:31 AM, Pierre Morel wrote:
On 08/03/2019 23:43, Tony Krowiak wrote:
On 2/22/19 10:29 AM, Pierre Morel wrote:
When the device is remove, we must make sure to
clear the interruption and reset the AP device.
We also need to clear the CRYCB of the guest.
Signed-off-by: Pierre Morel
On Monday 03/11 at 14:33 +0100, Petr Mladek wrote:
> On Fri 2019-03-01 16:48:19, Calvin Owens wrote:
> > This patch embeds a device struct in the console struct, and registers
> > them on a "console" bus so we can expose attributes in sysfs.
> >
> > Currently, most drivers declare static console s
On Tue, Mar 12, 2019 at 02:19:15PM -0700, James Bottomley wrote:
> I mean in the sequence
>
> flush_dcache_page(page);
> flush_dcache_page(page);
>
> The first flush_dcache_page did all the work and the second it a
> tightly pipelined no-op. That's what I mean by there not really being
> a doubl
After LLVM revision r355672 [1], all known working kernel configurations
fail to link [2]:
ld: init/do_mounts.o: in function `prepare_namespace':
do_mounts.c:(.init.text+0x5ca): undefined reference to `bcmp'
ld: do_mounts.c:(.init.text+0x5e6): undefined reference to `bcmp'
ld: init/initramfs.o: in
From: gre...@linuxfoundation.org Sent: Tuesday,
March 12, 2019 2:47 PM
> >
> > Michael Kelley (2):
> > Drivers: hv: Move Hyper-V clockevents code to new clocksource driver
> > Drivers: hv: Move Hyper-V clocksource code to new clocksource driver
>
> You have two different patches that do dif
On 12.03.19 22:13, Alexander Duyck wrote:
> On Tue, Mar 12, 2019 at 12:46 PM Nitesh Narayan Lal wrote:
>>
>> On 3/8/19 4:39 PM, Alexander Duyck wrote:
>>> On Fri, Mar 8, 2019 at 11:39 AM Nitesh Narayan Lal
>>> wrote:
On 3/8/19 2:25 PM, Alexander Duyck wrote:
> On Fri, Mar 8, 2019 at 11:
On Tue, 12 Mar 2019 12:30:52 -0700 Dan Williams
wrote:
> On Tue, Mar 12, 2019 at 12:06 PM Jerome Glisse wrote:
> > On Tue, Mar 12, 2019 at 09:06:12AM -0700, Dan Williams wrote:
> > > On Tue, Mar 12, 2019 at 8:26 AM Jerome Glisse wrote:
> [..]
> > > > Spirit of the rule is better than blind app
From: Kangjie Lu
Date: Tue, 12 Mar 2019 02:43:18 -0500
> of_get_phy_mode may fail and return a negative error code;
> the fix checks the return value of of_get_phy_mode and
> returns NULL of it fails.
>
> Signed-off-by: Kangjie Lu
Applied with Fixes: tag added.
On Tue, Mar 12, 2019 at 09:42:09PM +, Michael Kelley wrote:
> This patch series moves Hyper-V clock/timer code to a separate Hyper-V
> clocksource driver. Previously, Hyper-V clock/timer code and data
> structures were mixed in with other Hyper-V code in the ISA independent
> drivers/hv code as
Code for the Hyper-V specific clocksources is currently mixed
in with other Hyper-V code. Move the code to a Hyper-V specific
driver in the "clocksource" directory, while separating out
ISA dependencies so that the new clocksource driver is ISA
independent. Update the Hyper-V initialization code to
Clockevents code for Hyper-V synthetic timers is currently mixed
in with other Hyper-V code. Move the code to a Hyper-V specific
driver in the "clocksource" directory. Update the VMbus driver
to call initialization and cleanup routines since the Hyper-V
synthetic timers are not independently enumer
This patch series moves Hyper-V clock/timer code to a separate Hyper-V
clocksource driver. Previously, Hyper-V clock/timer code and data
structures were mixed in with other Hyper-V code in the ISA independent
drivers/hv code as well as in arch dependent code. The new Hyper-V
clocksource driver is I
On 3/3/19 9:09 PM, Halil Pasic wrote:
On Fri, 22 Feb 2019 16:29:56 +0100
Pierre Morel wrote:
We need to associate the ap_vfio_queue, which will hold the
per queue information for interrupt with a matrix mediated device
which hold the configuration and the way to the CRYCB.
[..]
+static int v
Linus Torvalds writes:
> On Wed, Mar 6, 2019 at 5:29 AM Petr Mladek wrote:
>>
>> I wonder if it is "normal" to get panic() when the system is rebooted
>> using "reboot -f". I looks a bit weird to me.
>
> No, a panic is never normal (except possibly for test modules etc, of course).
>
>> Now, "re
On Tue, 12 Mar 2019 15:03:52 +0100 Bartosz Golaszewski
wrote:
> wt., 12 mar 2019 o 14:59 Khalid Aziz napisał(a):
> >
> > On 3/12/19 7:28 AM, Bartosz Golaszewski wrote:
> > > From: Bartosz Golaszewski
> > >
> > > The mm variable is set but unused. Remove it.
> >
> > It is used. Look further dow
Neil Armstrong writes:
> On 07/03/2019 16:13, Neil Armstrong wrote:
>> From: Jerome Brunet
>>
>> Add the always on UART pinctrl setting to the g12a soc DT and
>> use it for the u200 reference design
>>
>> Signed-off-by: Jerome Brunet
>> Signed-off-by: Neil Armstrong
>> ---
>> .../arm64/boot
1 - 100 of 1222 matches
Mail list logo
