On 6/29/19 8:10 AM, Dmitry Osipenko wrote:
28.06.2019 5:12, Sowjanya Komatineni пишет:
This patch adds system suspend and resume support for Tegra210
clocks.
All the CAR controller settings are lost on suspend when core power
goes off.
This patch has implementation for saving and restoring
On 6/29/19 8:46 AM, Dmitry Osipenko wrote:
28.06.2019 5:12, Sowjanya Komatineni пишет:
This patch adds support for Tegra pinctrl driver suspend and resume.
During suspend, context of all pinctrl registers are stored and
on resume they are all restored to have all the pinmux and pad
On 7/4/19 3:40 AM, Dmitry Osipenko wrote:
04.07.2019 10:31, Linus Walleij пишет:
On Sat, Jun 29, 2019 at 5:58 PM Dmitry Osipenko wrote:
Oh, also what about GPIO-pinctrl suspend resume ordering .. is it okay that
pinctrl
will be resumed after GPIO? Shouldn't a proper pin-muxing be selected
On 7/12/19 12:12 PM, Yang Shi wrote:
On 7/11/19 2:07 PM, Qian Cai wrote:
On Wed, 2019-07-10 at 17:16 -0700, Yang Shi wrote:
Hi Qian,
Thanks for reporting the issue. But, I can't reproduce it on my
machine.
Could you please share more details about your test? How often did you
run into
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Linus,
Please pull powerpc updates for 5.3.
A bit of a small batch for us, just due to me not getting the time to review
things. Only one conflict that I'm aware of, in our pgtable.h, resolution is
simply to take both sides.
cheers
The
Hi Linus,
This pull request includes changes to let percpu_ref release the backing
percpu memory earlier after it has been switched to atomic in cases
where the percpu ref is not revived. This will help recycle percpu
memory earlier in cases where the refcounts are pinned for prolonged
periods of
The function posix_acl_create() applies the umask only if the inode
has no ACL (= NULL) or if ACLs are not supported by the filesystem
driver (= -EOPNOTSUPP).
However, this happens only after after the IS_POSIXACL() check
succeeeded. If the superblock doesn't enable ACL support, umask will
never
This sets MS_POSIXACL only if ACL support is really enabled, instead
of always setting MS_POSIXACL if the NFS protocol version
theoretically supports ACL.
The code comment says "We will [apply the umask] ourselves", but that
happens in posix_acl_create() only if the kernel has POSIX ACL
support.
The function ext4_init_acl() calls posix_acl_create() which is
responsible for applying the umask. But without
CONFIG_EXT4_FS_POSIX_ACL, ext4_init_acl() is an empty inline function,
and nobody applies the umask.
This fixes a bug which causes the umask to be ignored with O_TMPFILE
on ext4:
Make IS_POSIXACL() return false if POSIX ACL support is disabled and
ignore SB_POSIXACL/MS_POSIXACL.
Never skip applying the umask in namei.c and never bother to do any
ACL specific checks if the filesystem falsely indicates it has ACLs
enabled when the feature is completely disabled in the
On Fri, Jul 12, 2019 at 05:27:15PM -0700, Linus Torvalds wrote:
> On Fri, Jul 12, 2019 at 11:02 AM Darrick J. Wong wrote:
> >
> > The branch merges cleanly against this morning's HEAD and survived an
> > overnight run of xfstests. The merge was completely straightforward, so
> > please let me
As commit 1e0221374e30 ("mips: vdso: drop unnecessary cc-ldoption")
explained, these flags are supported by the minimal required version
of binutils.
Signed-off-by: Masahiro Yamada
---
Makefile | 6 ++
arch/arm/vdso/Makefile| 3 +--
The Lichee Zero Plus is a core board made by Sipeed, with a microUSB
connector on it, TF slot or WSON8 SD chip, optional eMMC or SPI Flash.
It has a gold finger connector for expansion, and UART is available from
reserved pins w/ 2.54mm pitch. The board can use either SoChip S3 or
Allwinner V3L
Lichee zero plus is a core board made by Sipeed, which includes on-board
TF slot or SMT SD NAND, and optional SPI NOR or eMMC, a UART debug
header, a microUSB slot and a gold finger connector for expansion. It
can use either Sochip S3 or Allwinner S3L SoC.
Add the basic device tree for the core
The Allwinner S3/S3L/V3 SoCs all share the same die with the V3s SoC,
but with more GPIO wired out of the package.
Add DTSI files for these SoCs. The DTSI file for V3 just replaces the
pinctrl compatible string, and the S3/S3L DTSI files just include the V3
DTSI file.
Signed-off-by: Icenowy
We developed a coccinelle SmPL to detect sound/soc/samsung/odroid.c and
found some use-after-free problems.
This patch series fixes those problems.
Wen Yang (2):
ASoC: samsung: odroid: fix an use-after-free issue for codec
ASoC: samsung: odroid: fix a double-free issue for cpu_dai
Allwinner V3 has the same main die with V3s, but with more pins wired.
There's a I2S bus on V3 that is not available on V3s.
Add the V3-only peripheral's clocks and reset to the V3s CCU driver,
bound to a new V3 compatible string. The driver name is not changed
because it's part of the device
The cpu_dai variable is still being used after the of_node_put() call,
which may result in double-free:
of_node_put(cpu_dai);---> released here
ret = devm_snd_soc_register_card(dev, card);
if (ret < 0) {
...
goto err_put_clk_i2s;--> jump to
The codec variable is still being used after the of_node_put() call,
which may result in use-after-free.
Fixes: bc3cf17b575a ("ASoC: samsung: odroid: Add support for secondary CPU DAI")
Signed-off-by: Wen Yang
Cc: Krzysztof Kozlowski
Cc: Sangbeom Kim
Cc: Sylwester Nawrocki
Cc: Liam Girdwood
The user manual of V3/V3s/S3 declares a PLL_DDR1, however it's forgot
when developing the V3s CCU driver.
Add back the missing PLL_DDR1.
Fixes: d0f11d14b0bc ("clk: sunxi-ng: add support for V3s CCU")
Signed-off-by: Icenowy Zheng
---
No changes since v1.
drivers/clk/sunxi-ng/ccu-sun8i-v3s.c |
The MMC2 clock slices are currently not defined in V3s CCU driver, which
makes MMC2 not working.
Fix this issue.
Fixes: d0f11d14b0bc ("clk: sunxi-ng: add support for V3s CCU")
Signed-off-by: Icenowy Zheng
---
New patch in v4.
drivers/clk/sunxi-ng/ccu-sun8i-v3s.c | 3 +++
1 file changed, 3
Despite Allwinner V3 and V3s shares the same die, one peripheral (I2S)
is only available on V3, and thus the clocks is not declared for V3s
CCU.
Add a V3 CCU compatible string to the binding to prepare for a CCU
driver that provide I2S clock on V3, but not on V3s.
Signed-off-by: Icenowy Zheng
Introduce the GPIO pins that is only available on V3 (not on V3s) to the
V3s pinctrl driver.
Signed-off-by: Icenowy Zheng
---
Changes in v4:
- Removed bogus alignment change.
Changes in v3:
- Fixed code alignment.
- Fixed LVDS function number.
Changes in v2:
- Dropped the driver rename patch
This patchset tries to add support for Allwinner V3/S3L and Sochip S3.
Allwinner V3/V3s/S3L and Sochip S3 share the same die, but with
different package. V3 is BGA w/o co-packaged DDR, V3s is QFP w/ DDR2,
S3L is BGA w/ DDR2 and S3 is BGA w/ DDR3. (S3 and S3L is compatible
for pinout, but because
DEAR CUSTOMERS
We are happy to inform you about our new SMTP SERVER
today I would like to introduce you to a page that provides services for
UNLIMITED SENDER
We offer all the services that you desire now? 15x Domain Inbox SMTP
please check
The KBUILD_ARFLAGS addition in arch/powerpc/Makefile has never worked
in a useful way because it is always overridden by the following code
in the top Makefile:
# use the deterministic mode of AR if available
KBUILD_ARFLAGS := $(call ar-option,D)
The code in the top Makefile was added in
On Fri, 12 Jul 2019 at 18:04, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 5.2.1 release.
> There are 61 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.
>
>
On Fri, 12 Jul 2019 at 17:56, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 5.1.18 release.
> There are 138 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.
>
>
On Fri, 12 Jul 2019 at 17:52, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.19.59 release.
> There are 91 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.
>
>
On Thu, Jul 11, 2019 at 6:50 PM Masahiro Yamada
wrote:
> GCC 8 added this flag.
> So, it will be eventually all solved in the GCC world.
Ack.
> Clang has not supported it yet...
That's what it appeared like. I've bugged our Clang-loving toolchain
folks to see if we can get parity.
> Trimming
On Fri, Jul 12, 2019 at 02:17:44PM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.1.18 release.
> There are 138 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
On 7/11/19 10:47 PM, Hillf Danton wrote:
>
> On Thu, 11 Jul 2019 02:42:56 +0800 Mike Kravetz wrote:
>>
>> It is quite easy to hit the condition where:
>> nr_reclaimed == 0 && nr_scanned == 0 is true, but we skip the previous test
>>
> Then skipping check of __GFP_RETRY_MAYFAIL makes no sense in
On Fri, Jul 12, 2019 at 11:23:19AM +0200, Samuel Thibault wrote:
> Hello,
>
> To readers of the linux-speakup: could you help on this so we can get
> Speakup in mainline? Neither Okash or I completely know what user
> consequences the files in /sys/accessibility/speakup/ have, so could
> people
This is a call for proposals for the 3 day networking track at the
Linux Plumbers Conference in Lisbon, which will be happening on
September 9th-11th, 2019.
We are seeking talks of 40 minutes in length (including Q & A),
optionally accompanied by papers of 2 to 10 pages in length. The
papers,
From: Qian Cai
Date: Fri, 12 Jul 2019 20:27:09 -0400
> Actually, GCC would consider it a const with -O2 optimized level because it
> found that it was never modified and it does not understand it is a module
> parameter. Considering the following code.
>
> # cat const.c
> #include
>
>
The pull request you sent on Fri, 12 Jul 2019 10:18:44 -0500:
> git://git.kernel.org/pub/scm/linux/kernel/git/teigland/linux-dlm.git dlm-5.3
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/964a4eacef67503a1154f7e0a75f52fbdce52022
Thank you!
--
Deet-doot-dot, I am a
The pull request you sent on Fri, 12 Jul 2019 10:04:46 +0200:
> git://github.com/martinetd/linux tags/9p-for-5.3
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/23bbbf5c1fb3ddf104c2ddbda4cc24ebe53a3453
Thank you!
--
Deet-doot-dot, I am a bot.
On Fri, Jul 12, 2019 at 1:08 AM Dominique Martinet
wrote:
>
> Just noticed this typo in version number here, should I make a new tag
> with the correct text?
No need, The important part is the signature itself, the typo will be
embedded in the merge commit (as part of the merge signature) but
The pull request you sent on Fri, 12 Jul 2019 11:02:05 -0700:
> git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git tags/xfs-5.3-merge-12
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/4ce9d181ebe53abbca5f450b8a2984b8c3a38f26
Thank you!
--
Deet-doot-dot, I am a bot.
The pull request you sent on Thu, 11 Jul 2019 07:18:25 -0700:
> git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git
> tags/vfs-fix-ioctl-checking-3
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/5010fe9f095414b959fd6fda63986dc90fd0c419
Thank you!
--
Deet-doot-dot, I
On Fri, Jul 12, 2019 at 11:02 AM Darrick J. Wong wrote:
>
> The branch merges cleanly against this morning's HEAD and survived an
> overnight run of xfstests. The merge was completely straightforward, so
> please let me know if you run into anything weird.
Hmm. I don't know what you merged
> On Jul 12, 2019, at 6:46 PM, David Miller wrote:
>
> From: Qian Cai
> Date: Fri, 12 Jul 2019 15:23:21 -0400
>
>> The commit d66acc39c7ce ("bitops: Optimise get_order()") introduced a
>> problem for the be2net driver as "rx_frag_size" could be a module
>> parameter that can be changed
On Sat, 6 Jul 2019, Salvatore Mesoraca wrote:
> Adding documentation for S.A.R.A. LSM.
It would be good if you could add an operational overview to help people
understand how it works in practice, e.g. setting policies for binaries
via sara-xattr and global config via saractl (IIUC). It's
On Fri, 2019-07-12 at 15:36 -0700, David Miller wrote:
> From: Arnd Bergmann
> Date: Fri, 12 Jul 2019 11:06:33 +0200
>
> > The cudbg_collect_mem_region() and cudbg_read_fw_mem() both use several
> > hundred kilobytes of kernel stack space.
Several hundred 'kilo' bytes?
I hope not.
If a common DT binding is pointing to a child DT node of a particular
parent DT node, don't add device links for such DT references. This is
because, by definition, a child node can't be a functional dependency for
the parent node.
Signed-off-by: Saravana Kannan
---
drivers/of/platform.c | 17
A parent device can have child devices that it adds when it probes. But
this probing of the parent device can happen way after kernel init is done
-- for example, when the parent device's driver is loaded as a module.
In such cases, if the child devices depend on a supplier in the system, we
need
Default busses also have devices created for them. But there's no point
in creating device links for them. It's especially wasteful as it'll
cause the traversal of the entire device tree and also spend a lot of
time checking and figuring out that creating those links isn't allowed.
So check for
This sync_state driver/bus callback is called once all the consumers
of a supplier have probed successfully.
This allows the supplier device's driver/bus to sync the supplier
device's state to the software state with the guarantee that all the
consumers are actively managing the resources
Similar to creating functional dependency links from clock and
interconnect DT bindings, also create functional dependency links from
regulator DT bindings.
Signed-off-by: Saravana Kannan
---
drivers/of/platform.c | 83 ++-
1 file changed, 51
When multiple devices are added after kernel init, some suppliers could be
added before their consumer devices get added. In these instances, the
supplier devices could get their sync_state callback called right after
they probe because the consumers haven't had a chance to create device
links to
The driver core/bus adding dependencies by default makes sure that
suppliers don't sync the hardware state with software state before all the
consumers have their drivers loaded (if they are modules) and are probed.
However, when the bus incorrectly adds dependencies that it shouldn't have
added,
stable-rc/linux-4.19.y boot: 122 boots: 4 failed, 117 passed with 1 offline
(v4.19.58-92-gd66f8e7f112f)
Full Boot Summary:
https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.19.y/kernel/v4.19.58-92-gd66f8e7f112f/
Full Build Summary:
Add device-links to track functional dependencies between devices
after they are created (but before they are probed) by looking at
their common DT bindings like clocks, interconnects, etc.
Having functional dependencies automatically added before the devices
are probed, provides the following
When devices are added, the bus might want to create device links to track
functional dependencies between supplier and consumer devices. This
tracking of supplier-consumer relationship allows optimizing device probe
order and tracking whether all consumers of a supplier are active. The
add_links
When multiple child devices are populated using of_platform_populate()
after kernel init, there could be supplier-consumer dependencies between
the child devices.
Wait for all the devices to be added and linked before calling sync_state()
on all the suppliers.
Signed-off-by: Saravana Kannan
---
While most phandle references in common bindings point to the supplier
device node, there are also common bindings where the phandle can
pointing to a child node of the supplier device node.
Therefore, when trying to find the supplier device that corresponds to a
supplier phandle, we need to make
On Sat, 6 Jul 2019, Salvatore Mesoraca wrote:
> Creation of the S.A.R.A. cred blob management "API".
> In order to allow S.A.R.A. to be stackable with other LSMs, it doesn't use
> the "security" field of struct cred, instead it uses an ad hoc field named
> security_sara.
> This solution is
On Fri, Jul 12, 2019 at 03:40:40PM -0400, Joel Fernandes wrote:
> On Fri, Jul 12, 2019 at 10:46:30AM -0700, Paul E. McKenney wrote:
> > On Fri, Jul 12, 2019 at 01:06:31PM -0400, Joel Fernandes wrote:
> > > On Fri, Jul 12, 2019 at 09:45:31AM -0700, Paul E. McKenney wrote:
> > > > On Fri, Jul 12,
From: Sultan Alsawaf
Allocating pages with __get_free_page is slower than going through the
slab allocator to grab free pages out from a pool.
These are the results from running the code at the bottom of this
message:
[1.278602] speedtest: __get_free_page: 9 us
[1.278606] speedtest:
The pull request you sent on Fri, 12 Jul 2019 12:07:27 -0600:
> git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest
> tags/linux-kselftest-5.3-rc1
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/8487d8229990e6eacaf1c854a113c9d16b7b596c
Thank you!
--
The pull request you sent on Fri, 12 Jul 2019 23:04:31 +0200:
> git://git.kernel.org/pub/scm/linux/kernel/git/arnd/asm-generic.git
> tags/asm-generic-5.3
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/5f26f1143678d0fed8115afdcc0de99ee7cc9675
Thank you!
--
The pull request you sent on Thu, 11 Jul 2019 15:56:54 +0200:
> git://git.infradead.org/users/hch/dma-mapping.git tags/dma-mapping-5.3
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/9e3a25dc992dd9f3170fb643bdd95da5ca9c5576
Thank you!
--
Deet-doot-dot, I am a bot.
The pull request you sent on Thu, 11 Jul 2019 14:32:18 -0400:
> https://lore.kernel.org/lkml/20190709195358.25af2...@canb.auug.org.au/ .
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/16c97650a56abdd067f7da079007b7e00b307083
Thank you!
--
Deet-doot-dot, I am a bot.
The pull request you sent on Sat, 13 Jul 2019 02:50:05 +0900:
> git://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild.git
> tags/kbuild-v5.3
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/39ceda5ce1b002e30563fcb8ad1bb5ac8e4d59ee
Thank you!
--
The pull request you sent on Sat, 13 Jul 2019 02:54:42 +0900:
> git://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild.git
> tags/kconfig-v5.3
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/106f1466e7e7057ec6f4dc9516c13ea8cb9dffa0
Thank you!
--
The pull request you sent on Fri, 12 Jul 2019 19:44:24 +0200:
> https://git.kernel.org/pub/scm/virt/kvm/kvm.git tags/for-linus
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/39d7530d7494b4e47ba1856e741f513dafd17e3d
Thank you!
--
Deet-doot-dot, I am a bot.
The pull request you sent on Fri, 12 Jul 2019 16:39:34 +0200:
> git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git tags/s390-5.3-2
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/aabfea8dc91cf5b220d2ed85e8f6395a9b140371
Thank you!
--
Deet-doot-dot, I am a
On Fri, Jul 12, 2019 at 10:51:31AM +0200, KarimAllah Ahmed wrote:
>Do not mark regions that are marked with nomap to be present, otherwise
>these memblock cause unnecessarily allocation of metadata.
>
>Cc: Andrew Morton
>Cc: Pavel Tatashin
>Cc: Oscar Salvador
>Cc: Michal Hocko
>Cc: Mike
Looks good,
Reviewed-by: Sagi Grimberg
On 7/12/19 1:55 AM, Peter Zijlstra wrote:
On Thu, Jul 11, 2019 at 11:53:12AM -0700, Bart Van Assche wrote:
On 7/10/19 3:09 PM, Peter Zijlstra wrote:
One thing I mentioned when Thomas did the unwinder API changes was
trying to move lockdep over to something like stackdepot.
We can't directly
From: Qian Cai
Date: Fri, 12 Jul 2019 15:23:21 -0400
> The commit d66acc39c7ce ("bitops: Optimise get_order()") introduced a
> problem for the be2net driver as "rx_frag_size" could be a module
> parameter that can be changed while loading the module.
Why is this a problem?
> That commit checks
At release_thread(), ->mm is NULL; and it is fine for the former mm to
still have an LDT. Delete this check in process_64.c, similar to
commit 2684927c6b93 ("[PATCH] x86: Deprecate useless bug"), which did the
same in process_32.c.
Signed-off-by: Jann Horn
---
arch/x86/kernel/process_64.c | 12
errno_to_nvme_status() doesn't take into account the case
when errno=0, all other use cases only call it if there is actually
an error.
Presently, nvmet_file_flush() always returns a call to
errno_to_nvme_status() so, even if it is successful, it will
return NVME_SC_INTERNAL.
This bug was found
From: Jiangfeng Xiao
Date: Fri, 12 Jul 2019 21:16:24 +0800
> Use devm_platform_ioremap_resource instead of
> devm_ioremap_resource. Make the code simpler.
>
> Signed-off-by: Jiangfeng Xiao
Applied.
From: Arnd Bergmann
Date: Fri, 12 Jul 2019 11:06:33 +0200
> The cudbg_collect_mem_region() and cudbg_read_fw_mem() both use several
> hundred kilobytes of kernel stack space. One gets inlined into the other,
> which causes the stack usage to be combined beyond the warning limit
> when building
From: Chris Packham
Date: Fri, 12 Jul 2019 10:41:15 +1200
> tipc_named_node_up() creates a skb list. It passes the list to
> tipc_node_xmit() which has some code paths that can call
> skb_queue_purge() which relies on the list->lock being initialised.
>
> The spin_lock is only needed if the
On 7/13/19 12:17 AM, Jakub Jankowski wrote:
> On 2019-07-12, Alexey Izbyshev wrote:
>
>> On 7/12/19 8:46 PM, Alexey Dobriyan wrote:
>>> The proper fix to all /proc/*/cmdline problems is to revert
>>>
>>> f5b65348fd77839b50e79bc0a5e536832ea52d8d
>>> proc: fix missing final NUL in
From: Denis Efremov
Date: Wed, 10 Jul 2019 21:03:24 +0300
> The variables phy_basic_ports_array, phy_fibre_port_array and
> phy_all_ports_features_array are declared static and marked
> EXPORT_SYMBOL_GPL(), which is at best an odd combination.
> Because the variables were decided to be a part of
One of the gfp flags used to show that a page is movable is
__GFP_HIGHMEM. Currently z3fold_alloc() fails when __GFP_HIGHMEM is
passed. Now that z3fold pages are movable, we allow __GFP_HIGHMEM. We
strip the movability related flags from the call to kmem_cache_alloc()
for our slots since it is a
From: Arnd Bergmann
Date: Wed, 10 Jul 2019 10:00:33 +0200
> dma_addr_t may be 64-bit wide on 32-bit architectures, so it is not
> valid to cast between it and a pointer:
>
> drivers/net/ethernet/ti/davinci_cpdma.c: In function 'cpdma_chan_submit_si':
>
On 12/07/2019 19:45, Mauro Carvalho Chehab wrote:
> Brad Love escreveu:
>
>> On 04/07/2019 05.33, Marc Gonzalez wrote:
>>
>>> +#define CMD_SETUP(cmd, args, rlen) \
>>> + cmd_setup(cmd, args, sizeof(args) - 1, rlen)
>>> +
>>
>> This is only a valid helper if args is a null terminated string.
I just built v5.1 and v5.2 from source, without the Arch patches, and
get the same result: 5.1 boots and 5.2 doesn't. I tried adding
ignore_loglevel, but still just get a blinking cursor. So it's
definitely a regression.
I can have a go at bisecting this if it would help? Or is there
something
On 7/12/19 6:19 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 5.2.1 release.
There are 61 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.
Responses should be made
On 7/12/19 6:18 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.19.59 release.
There are 91 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.
Responses should be made
On 7/12/19 6:17 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 5.1.18 release.
There are 138 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.
Responses should be made
On Fri, Jun 28, 2019 at 2:01 PM Zhihao Cheng wrote:
>
> The UBI device can be attached to a MTD device via fastmap by setting
> CONFIG_MTD_UBI_FASTMAP to 'y' (If there already exists a fastmap on the
> UBI device). To support some debugging scenarios, attaching process by
> fastmap can be
On Fri, Jul 12, 2019 at 02:43:28PM -0700, Linus Torvalds wrote:
> On Fri, Jul 12, 2019 at 2:37 PM Linus Torvalds
> wrote:
> >
> > My bad. Will apply the fix properly.
>
> Ok, _now_ your fix is finally in my tree. D'oh.
>
> Linus
Great, thank you for the quick response! :)
Nathan
On Fri, Jul 12, 2019 at 2:11 PM Andrew Morton wrote:
>
> On Fri, 12 Jul 2019 08:49:07 -0400 Qian Cai wrote:
> >
> > https://lore.kernel.org/linux-mm/20190617151252.GF16810@rapoport-lnx/
>
> That's already merged - it went in via the arm64 tree I think.
No. Only the
On Fri, Jul 12, 2019 at 2:37 PM Linus Torvalds
wrote:
>
> My bad. Will apply the fix properly.
Ok, _now_ your fix is finally in my tree. D'oh.
Linus
On 12/07/2019 17:47, Brad Love wrote:
> On 04/07/2019 05.33, Marc Gonzalez wrote:
>
>> Refactor the command setup code, and let the compiler determine
>> the size of each command.
>>
>> Reviewed-by: Jonathan Neuschäfer
>> Signed-off-by: Marc Gonzalez
>> ---
>> Changes from v1:
>> - Use a real
On Fri, Jul 12, 2019 at 2:09 PM Nathan Chancellor
wrote:
>
> Doesn't look like this made it into the merge, as I currently see that
> same error with arm64 allyesconfig.
Duh.
Because I had fixed up the actual definition of that function during
the merge, I thought I had handled it all
On 2019-07-12, Alexey Izbyshev wrote:
On 7/12/19 8:46 PM, Alexey Dobriyan wrote:
The proper fix to all /proc/*/cmdline problems is to revert
f5b65348fd77839b50e79bc0a5e536832ea52d8d
proc: fix missing final NUL in get_mm_cmdline() rewrite
On Fri, Jul 12, 2019 at 2:07 AM Arnd Bergmann wrote:
>
> The mpi library contains some rather old inline assembly statements
> that produce a lot of warnings for 32-bit x86, such as:
>
> lib/mpi/mpih-div.c:76:16: error: invalid use of a cast in a inline asm
> context requiring an l-value: remove
On Fri, 12 Jul 2019 12:59:45 +0200 Arnd Bergmann wrote:
> On Thu, Jul 11, 2019 at 2:41 AM Andrew Morton
> wrote:
> >
> >
> > From: Yang Shi
> > Subject: mm: shrinker: make shrinker not depend on memcg kmem
> >
> > Currently shrinker is just allocated and can work when memcg kmem is
> >
On Fri, 12 Jul 2019 08:49:07 -0400 Qian Cai wrote:
> Actually, this patch is slightly off. There is one delta need to apply (ignore
> the part in pgtable.h which has already in mainline via the commit
> 615c48ad8f42
> "arm64/mm: don't initialize pgd_cache twice") in.
>
>
On Fri, Jul 12, 2019 at 09:40:23AM +0200, Greg KH wrote:
> On Fri, Jul 12, 2019 at 09:36:23AM +0200, Greg KH wrote:
> > The following changes since commit f2c7c76c5d0a443053e94adb9f0918fa2fb85c3a:
> >
> > Linux 5.2-rc3 (2019-06-02 13:55:33 -0700)
> >
> > are available in the Git repository at:
The following changes since commit f2c7c76c5d0a443053e94adb9f0918fa2fb85c3a:
Linux 5.2-rc3 (2019-06-02 13:55:33 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/arnd/asm-generic.git
tags/asm-generic-5.3
for you to fetch changes up to
When running ltp's oom test with kmemleak enabled, the below warning was
triggerred since kernel detects __GFP_NOFAIL & ~__GFP_DIRECT_RECLAIM is
passed in:
WARNING: CPU: 105 PID: 2138 at mm/page_alloc.c:4608
__alloc_pages_nodemask+0x1c31/0x1d50
Modules linked in: loop dax_pmem dax_pmem_core
To enable burst clock mode, add the fsl,burst-clk-enable
property to the weim bus's devicetree node.
Example:
weim: weim@21b8000 {
compatible = "fsl,imx6q-weim";
reg = <0x021b8000 0x4000>;
clocks = < 196>;
#address-cells = <2>;
#size-cells = <1>;
An optional devicetree property was added to the imx-weim driver,
which if present instructs it to operate in burst clock mode.
Update the dt-bindings to reflect this.
Signed-off-by: Sven Van Asbroeck
---
Documentation/devicetree/bindings/bus/imx-weim.txt | 4
1 file changed, 4
1 - 100 of 853 matches
Mail list logo
