On 18.09.18 18:15:51, Will Deacon wrote:
> On Tue, Sep 18, 2018 at 11:52:27AM +0200, Robert Richter wrote:
> > On 18.09.18 09:38:05, Will Deacon wrote:
> > > On Mon, Sep 17, 2018 at 07:22:07PM +0200, Robert Richter wrote:
> > > > On 27.08.18 16:33:07, Mian Yousaf Kaukab wrote:
> > > > > Hard-coded
From: Heiko Carstens
Enable support for relative references in jump_label entries.
Signed-off-by: Heiko Carstens
Signed-off-by: Ard Biesheuvel
---
arch/s390/Kconfig | 1 +
arch/s390/include/asm/jump_label.h | 40
arch/s390/kernel/jump_label.c | 11 +
Jump table entries are mostly read-only, with the exception of the
init and module loader code that defuses entries that point into init
code when the code being referred to is freed.
For robustness, it would be better to move these entries into the
ro_after_init section, but clearing the 'code' m
The __jump_table sections emitted into the core kernel and into
each module consist of statically initialized references into
other parts of the code, and with the exception of entries that
point into init code, which are defused at post-init time, these
data structures are never modified.
So let'
To reduce the size taken up by absolute references in jump label
entries themselves and the associated relocation records in the
.init segment, add support for emitting them as relative references
instead.
Note that this requires some extra care in the sorting routine, given
that the offsets chang
Add support for R_X86_64_PC64 relocations, which operate on 64-bit
quantities holding a relative symbol reference. Also remove the
definition of R_X86_64_NUM: given that it is currently unused, it
is unclear what the new value should be.
Signed-off-by: Ard Biesheuvel
---
arch/x86/include/asm/elf
In preparation of switching x86 to use place-relative references for
the code, target and key members of struct jump_entry, replace direct
references to the struct members with invocations of the new accessors.
This will allow us to make the switch by modifying the accessors only.
This incorporate
Similar to the arm64 case, 64-bit x86 can benefit from using relative
references rather than absolute ones when emitting struct jump_entry
instances. Not only does this reduce the memory footprint of the entries
themselves by 33%, it also removes the need for carrying relocation
metadata on relocat
On a randomly chosen distro kernel build for arm64, vmlinux.o shows the
following sections, containing jump label entries, and the associated
RELA relocation records, respectively:
...
[38088] __jump_table PROGBITS 00e19f30
0002ea10 00
In preparation of allowing architectures to use relative references
in jump_label entries [which can dramatically reduce the memory
footprint], introduce abstractions for references to the 'code' and
'key' members of struct jump_entry.
Signed-off-by: Ard Biesheuvel
---
include/linux/jump_label.h
This series implements support for emitting the data structures associated
with jump tables as 32-bit relative references instead of absolute
references, which take up more space on builds that target 64-bit
architectures, or implement self relocation [or both].
This series enables it for arm64 an
> I'm terribly sorry. I didn't manage to review before leaving on
> travel. I'm back next week and then I'll review, OK?
Sure thing, thanks for the heads up!
signature.asc
Description: PGP signature
Christoph Hellwig writes:
>>
>> clear_siginfo(&info);
>> -fill_sigtrap_info(tsk, regs, error_code, si_code, &info);
>> +tsk->thread.trap_nr = X86_TRAP_DB;
>> +tsk->thread.error_code = error_code;
>> +
>> +info.si_signo = SIGTRAP;
>> +info.si_code = si_code;
>> +info
On Wed, Sep 19, 2018 at 3:52 PM, Christophe LEROY
wrote:
>
>
> Le 19/09/2018 à 01:07, Joel Stanley a écrit :
>>
>> This partially reverts faa16bc404d72a5 ("lib: Use existing define with
>> polynomial").
>>
>> The cleanup added a dependency on include/linux, which broke the PowerPC
>> boot wrapper/
On (09/19/18 10:27), He Zhe wrote:
> On 2018年09月19日 09:50, Sergey Senozhatsky wrote:
> > On (09/19/18 01:17), zhe...@windriver.com wrote:
> >> @@ -1048,7 +1048,14 @@ static void __init log_buf_len_update(unsigned size)
> >> /* save requested log_buf_len since it's too early to process it */
> >>
On Wed, 19 Sep 2018 at 05:57, kbuild test robot wrote:
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> master
> head: 5211da9ca526a5adddee1ccd078e6e33a583ab36
> commit: faa16bc404d72a5afb857c924c83a5f691f83386 lib: Use existing define
> with polynomial
> date:
Hello All,
On Tue, Sep 18, 2018 at 06:13:48PM +0800, kbuild test robot wrote:
> Thank you for the patch! Yet something to improve:
>
> [auto build test ERROR on regulator/for-next]
> [also build test ERROR on next-20180913]
> [cannot apply to v4.19-rc4]
> [if your patch is applied to the wrong gi
Hi David,
On Wed, 19 Sep 2018 07:01:00 +0100 David Howells wrote:
>
> Stephen Rothwell wrote:
>
> > > I think the problem is that I haven't allocated system call numbers for
> > > any arches other than x86 - even the x86 syscall numbers are provisional
> > > until the patchset is taken upstream
Mediatek SPI driver modifies some fields (tx_buf, rx_buf, len, tx_dma,
rx_dma) of the spi_transfer* passed in when doing transfer_one and in
interrupt handler. This is somewhat unexpected, and there are some
caller (e.g. Cr50 spi driver) that reuse the spi_transfer for multiple
messages. Add a fiel
Hi all,
Changes since 20180918:
Dropped trees: xarray, ida (temporarily)
The input-current tree gained a build failure so I used the version
from next-20180918.
I still disabled building some samples in the vfs tree.
Non-merge commits (relative to Linus' tree): 4106
4562 files ch
Input to qcom,sd-lines should be between 0 and 3 instead of
1 to 4 as 0 corresponds to BIT(0) which is MI2S_SD0 line.
Bit 1 to 3 corresponds to SD1 to SD3 lines respectively.
Updated documentation for the same.
Signed-off-by: Rohit kumar
---
Documentation/devicetree/bindings/sound/qcom,q6afe.txt
i.MX6ULZ is new SoC of i.MX6 family, compared to i.MX6ULL,
it removes below modules:
- UART5/UART6/UART7/UART8;
- PWM5/PWM6/PWM7/PWM8;
- eCSPI3/eCSPI4;
- CAN1/CAN2;
- FEC1/FEC2;
- I2C3/I2C4;
- EPIT2;
- LCDIF;
- GPT2;
- ADC1;
- TSC;
This patch adds support for i.MX6ULZ and i.MX6ULZ 14x14 EVK
board
Hi, Stefan
Anson Huang
Best Regards!
> -Original Message-
> From: Stefan Wahren
> Sent: Tuesday, September 18, 2018 3:38 PM
> To: Anson Huang ; robh...@kernel.org;
> mark.rutl...@arm.com; shawn...@kernel.org; s.ha...@pengutronix.de;
> ker...@pengutronix.de; Fabio Estevam ;
> li...@armli
This patch adds compatible for i.MX6ULZ 14x14 EVK board.
Signed-off-by: Anson Huang
---
Documentation/devicetree/bindings/arm/fsl.txt | 4
1 file changed, 4 insertions(+)
diff --git a/Documentation/devicetree/bindings/arm/fsl.txt
b/Documentation/devicetree/bindings/arm/fsl.txt
index 968f2
i.MX6ULZ has same CCM IP as i.MX6ULL, and it reuses
i.MX6UL clock driver, this patch adds support for it.
Signed-off-by: Anson Huang
---
drivers/clk/imx/clk-imx6ul.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/clk/imx/clk-imx6ul.c b/drivers/clk/imx/clk-imx6ul.c
This patch set adds i.MX6ULZ SoC support, i.MX6ULZ is a new SoC of
i.MX6 family, compared to i.MX6ULL, it removes below modules:
- UART5/UART6/UART7/UART8;
- PWM5/PWM6/PWM7/PWM8;
- eCSPI3/eCSPI4;
- CAN1/CAN2;
- FEC1/FEC2;
- I2C3/I2C4;
- EPIT2;
- LCDIF;
- GPT2;
The i.MX 6ULZ processor is a high-performance, ultra
cost-efficient consumer Linux processor featuring an
advanced implementation of a single Arm® Cortex®-A7 core,
which operates at speeds up to 900 MHz.
This patch adds basic MSL support for i.MX6ULZ, the
i.MX6ULZ has same soc_id as i.MX6ULL, and
On Tue, Sep 18, 2018 at 07:14:13PM -0400, Steven Rostedt wrote:
>
> Linus (aka Greg),
>
> Vaibhav Nagarnaik found that modifying the ring buffer size could cause
> a huge latency in the system because it does a while loop to free pages
> without releasing the CPU (on non preempt kernels). In a ca
Replying to a very old message, but it's something we
discussed today at the IOLab event so to capture it:
On 11/7/2017 12:55 AM, Long Li wrote:
From: Long Li
---
fs/cifs/file.c| 17 +++--
fs/cifs/smb2pdu.c | 45 -
2 files changed
The new Code of Conduct makes me feel threatened and uncomfortable.
No, really. As a person with (diagnosed) Asperger's, I'm a member of,
objectively, a marginalised minority. Effectively (i.e. this is a massive
oversimplification), I was born without the hard-wired circuitry for
social
int
WARNING: vmlinux.o(.text+0x8aa424): Section mismatch in reference from
the function qcom_cpufreq_kryo_probe() to the function
.init.text:qcom_cpufreq_kryo_get_msm_id()
The function qcom_cpufreq_kryo_probe() references
the function __init qcom_cpufreq_kryo_get_msm_id().
This is often because qcom_cp
Dear,
I am working in financial firm in Asia. I have a business to transfer the sum
of $19.000.000.00 of abandon fund in my office.
If you are,interested in the transaction reply on my email for more details.
Best Regards,
Danny Chan.
Stephen Rothwell wrote:
> > I think the problem is that I haven't allocated system call numbers for
> > any arches other than x86 - even the x86 syscall numbers are provisional
> > until the patchset is taken upstream. I'm not sure of the best way to
> > deal with this - make the samples depende
On 18/09/2018 19:29, Rik van Riel wrote:
> On Tue, 2018-09-18 at 18:04 +0200, Sebastian Andrzej Siewior wrote:
>> On 2018-09-18 17:29:52 [+0200], Paolo Bonzini wrote:
I don't think it matters what the PKRU state is
for kernel threads, since kernel PTEs should not
be using protection
Hi Mark,
Thanks for your comments.
On Tue, 2018-09-18 at 09:30 -0700, Mark Brown wrote:
> On Mon, Sep 17, 2018 at 10:19:21AM +0800, Leilk Liu wrote:
>
> This looks overall pretty good, a few smallish comments below:
>
> Please use subject lines matching the style for the subsystem. This
> mak
Hello Srinivas,
We will add support for vi feedback usecase in sdm845 machine driver
where we have to support 4 channel tx data for a particular backend. We
should probably keep be_hw_params_fixup in respective machine driver for
now to support such requirement.
Thanks,
Rohit
On 9/17/20
some CONFIG_EROFS_FS_XATTR conditions were added because of
the historial Linux kernel compatibility, which are unneeded now.
Signed-off-by: Gao Xiang
---
Hi all,
These are cleanup patches in Chao's erofs-dev test tree for a while.
Many of them are trivial.
In order for all preview patche
> +struct mpx_fault_info
> +{
Normal kernel style would be:
struct mpx_fault_info {
>
> clear_siginfo(&info);
> - fill_sigtrap_info(tsk, regs, error_code, si_code, &info);
> + tsk->thread.trap_nr = X86_TRAP_DB;
> + tsk->thread.error_code = error_code;
> +
> + info.si_signo = SIGTRAP;
> + info.si_code = si_code;
> + info.si_addr = user_mode(regs) ? (
On Tue, Sep 18, 2018 at 03:38:52PM -0700, Darren Hart wrote:
> Hi Linus and Greg,
>
> The following changes since commit 5b394b2ddf0347bef56e50c69a58773c94343ff3:
>
> Linux 4.19-rc1 (2018-08-26 14:11:59 -0700)
>
> are available in the Git repository at:
>
> git://git.infradead.org/linux-pla
WARNING: vmlinux.o(.text+0x4758cc): Section mismatch in reference from
the function kirin_pcie_probe() to the function
.init.text:kirin_add_pcie_port()
The function kirin_pcie_probe() references
the function __init kirin_add_pcie_port().
This is often because kirin_pcie_probe lacks a __init
annotat
Fix the following compile warning:
drivers/soc/qcom/cmd-db.c:194:38: warning: ent.addr may be used uninitialized
in this function [-Wmaybe-uninitialized]
return ret < 0 ? 0 : le32_to_cpu(ent.addr);
drivers/soc/qcom/cmd-db.c:247:38: warning: ent.len may be used uninitialized
in this functi
- Remove never-used DT property
- Refactor code
- Add auto-flow-control support
Dai Okamura (1):
serial: 8250_uniphier: add auto-flow-control support
Masahiro Yamada (2):
serial: 8250_uniphier: remove unused "fifo-size" property
serial: 8250_uniphier: flatten probe function
.../devic
From: Dai Okamura
Add selective auto-flow-control support for UniPhier serial driver.
Signed-off-by: Dai Okamura
Signed-off-by: Masahiro Yamada
---
Documentation/devicetree/bindings/serial/uniphier-uart.txt | 3 +++
drivers/tty/serial/8250/8250_uniphier.c| 3 +++
2 files
The FIFO size of the UART devices is 64 on almost all UniPhier SoCs
with the exception Pro4TV SoC (MN2WS0230), which used 128 FIFO size.
However, Pro4TV SoC was never upstreamed, and out of production.
So, this property has never been used in a useful way.
Let's remove old unused code.
Signed-off
Currently, the DT-related settings are split out to
uniphier_of_serial_setup(), but it turned out to be not nice.
The next commit will add a DT property, but it will not fit in
the helper. Merge the helper into the probe function.
Signed-off-by: Masahiro Yamada
---
drivers/tty/serial/8250/8250
I find the following warning when compiling the kernel.
kernel/sched/psi.c:639:13: warning: 'rq' may be used uninitialized in this
function [-Wmaybe-uninitialized]
struct rq *rq;
Signed-off-by: zhong jiang
---
kernel/sched/psi.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --g
We need to count zero filled pages as well as other pages in zram.
Otherwise, it doesn't match swap page count via pagemap of process
so that memory tracking feature in zram doesn't provide accurate
information.
Cc: Sergey Senozhatsky
Cc: [4.18+]
Signed-off-by: Minchan Kim
---
drivers/block
> "Wolfram" == Wolfram Sang writes:
>> Thanks! I'll take a look at the patches now.
> Ping :)
I'm terribly sorry. I didn't manage to review before leaving on
travel. I'm back next week and then I'll review, OK?
--
Bye, Peter Korsgaard
Hi Boris,
Thanks for your continuous guidance.
> -Original Message-
> From: Borislav Petkov [mailto:b...@alien8.de]
> Sent: Tuesday, September 18, 2018 1:25 PM
> To: Manish Narani
> Cc: robh...@kernel.org; mark.rutl...@arm.com; mche...@kernel.org;
> Michal Simek ; leoyang...@nxp.com;
> s
Hi Boris,
Thanks a lot for the review.
> -Original Message-
> From: Borislav Petkov [mailto:b...@alien8.de]
> Sent: Tuesday, September 18, 2018 1:23 PM
> To: Manish Narani
> Cc: robh...@kernel.org; mark.rutl...@arm.com; mche...@kernel.org;
> Michal Simek ; leoyang...@nxp.com;
> sudeep.ho
On Saturday 01 September 2018 12:43 AM, Andrew F. Davis wrote:
> This macro does nothing and has only one user, remove it.
Tested for gpio interrupts on k2g and da850-lcdk
Tested-by: Keerthy
Acked-by: Keerthy
>
> Signed-off-by: Andrew F. Davis
> ---
> arch/arm/mach-davinci/board-neuros-o
On Saturday 01 September 2018 12:43 AM, Andrew F. Davis wrote:
> These defines, structs and inline functions are used only internally by
> the driver, they do not belong in platform_data. Move them.
Tested for gpio interrupts on k2g and da850-lcdk
Tested-by: Keerthy
Acked-by: Keerthy
>
> S
On Saturday 01 September 2018 12:43 AM, Andrew F. Davis wrote:
> Previously we created a controller structure per bank of GPIO pins. This
> has since been changed to one per controller, but the allocation size
> was not changed. Fix this here.
>
> This also leaves the variable 'nbank' unused, i
Add MFR_ID information, 0x002C, related to the Micron flash.
Currently, MFR_ID 0x0020 is being specified as Micron flash ID but
these are actually CFI ID of STMicro flashes.
Rename SNOR_MFR_MICRON to SNOR_MFR_ST and add entry for
SNOR_MFR_MICRON having CFI ID value of Micron flash.
Add entry of mt
Add entry for mt35xu512aba Micron NOR flash.
This flash is having uniform sector erase size of 128KB, have
support of FSR(flag status register), flash size is 64MB and
supports 4-byte commands.
Signed-off-by: Yogesh Gaur
---
drivers/mtd/spi-nor/spi-nor.c | 3 +++
1 file changed, 3 insertions(+)
Some MICRON related macros in spi-nor domain were ST.
Rename entries related to STMicroelectronics under macro SNOR_MFR_ST.
Added entry of MFR Id for Micron flashes, 0x002C.
Signed-off-by: Yogesh Gaur
---
drivers/mtd/spi-nor/spi-nor.c | 9 ++---
include/linux/mtd/cfi.h | 1 +
include/
On Wed, Sep 19, 2018 at 10:54:10AM +0800, Sean Wang wrote:
> On Tue, 2018-09-18 at 15:07 -0700, Linus Walleij wrote:
> > On Sat, Sep 8, 2018 at 4:07 AM wrote:
> >
> > > v2 and changes since v1:
> >
> > I had trouble applying the last patches in the series so I applied
> > all on an immutable bra
ATTENZIONE;
La cassetta postale ha superato il limite di archiviazione, che è 5 GB come
definiti dall'amministratore, che è attualmente in esecuzione su 10.9GB, non si
può essere in grado di inviare o ricevere nuovi messaggi fino a ri-convalidare
la tua mailbox. Per rinnovare la vostra casella
TO WHOM IT MAY CONCERN
Greetings,
Opportunity for you, I am well recognized and Public Figure occupying a top
Government position in Federal Republic of Nigerian. I am hereby requiring An
International expatriates with professional experience in
On Wednesday 19 September 2018 12:56 AM, Linus Walleij wrote:
> On Fri, Aug 31, 2018 at 12:13 PM Andrew F. Davis wrote:
>
>> Use dev_name to get a unique label and use -1 for a base to get our
>> selection automatically. We pull in all GPIOs per chip now so this
>> does not have the effect of
Hi Linus
On Wed, Sep 19, 2018 at 12:40 AM Linus Walleij wrote:
>
> On Fri, Sep 14, 2018 at 12:08 AM Ricardo Ribalda Delgado
> wrote:
>
> > Current code assumes that the direction is input if direction_input
> > function is set.
> > This might not be the case on GPIOs with programmable direction.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 5211da9ca526a5adddee1ccd078e6e33a583ab36
commit: faa16bc404d72a5afb857c924c83a5f691f83386 lib: Use existing define with
polynomial
date: 8 weeks ago
config: powerpc-skiroot_defconfig (attached as .config)
On Fri, Sep 14, 2018 at 5:10 PM Rafael J. Wysocki wrote:
>
> On Monday, August 20, 2018 11:18:35 AM CEST Pingfan Liu wrote:
> > Consider the shutdown as a system state transition, i.e. something like
> > suspend, hibernate, hence move it under the base/power. (This is a first
> > step to unify the
Enable hidden symbol ARCH_WANT_LIBATA_LEDS so CONFIG_ATA_LEDS can be
used in kernel configuration.
URL: https://lists.openwrt.org/pipermail/openwrt-
devel/2017-March/006582.html
Signed-off-by: Aditya Prayoga
---
arch/arm/mach-mvebu/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arc
From: Daniel Golle
This adds a LED trigger for each ATA port indicating disk activity.
As this is needed only on specific platforms (NAS SoCs and such),
these platforms should define ARCH_WANTS_LIBATA_LEDS if there
are boards with LED(s) intended to indicate ATA disk activity and
need the OS to
Hi everyone,
This series adds support LED trigger for each ATA port indicating disk activity
in Armada 38x. I pick up the work done by Daniel Golle which can be found at [1]
Helios4 which is based on Armada 388, has four LEDs designed to indicate disk
activity on each SATA ports. As the final swi
FYI, we noticed the following commit (built with gcc-7):
commit: 7ffb31888cbaab36ec464fc43ecf5ddecdbd55ac ("[PATCH v7 07/16] x86/pci:
Add Hygon Dhyana support to PCI and north bridge")
url:
https://github.com/0day-ci/linux/commits/Pu-Wen/Add-support-for-Hygon-Dhyana-Family-18h-processor/20180917
Hi Greg,
After merging the tty tree, today's linux-next build (x86_64 allmodconfig)
produced this warning:
drivers/tty/serial/kgdboc.c:134:12: warning: 'kgdboc_option_setup' defined but
not used [-Wunused-function]
static int kgdboc_option_setup(char *opt)
^~~
Intro
On Wed, 19 Sep 2018 11:47:54 +0900
Sergey Senozhatsky wrote:
> On (09/18/18 22:43), Steven Rostedt wrote:
> > > First - switch to u64 size.
> > > Second - check for NULL str.
> > >
> > I think I would switch it around. Check for NULL first, and then switch
> > to u64. It was always an int,
On Tue, 2018-09-18 at 15:07 -0700, Linus Walleij wrote:
> On Sat, Sep 8, 2018 at 4:07 AM wrote:
>
> > v2 and changes since v1:
>
> I had trouble applying the last patches in the series so I applied
> all on an immutable branch (ib-mtk) then merged that into devel
> and added a patch on top to fi
On Tue, Sep 18, 2018 at 05:56:50PM -0700, Rob Herring wrote:
> > > but does need a vendor prefix.
> > vendor prefix? Em ... it's just used in fpga now.
>
> What I mean is make it: csky,support-pulse-signal
Ok. no problem.
Best Regards
Guo Ren
On (09/18/18 22:43), Steven Rostedt wrote:
> > First - switch to u64 size.
> > Second - check for NULL str.
> >
> I think I would switch it around. Check for NULL first, and then switch
> to u64. It was always an int, do we need to backport converting it to
> u64 to stable? The NULL check is a
On Wed, 19 Sep 2018 11:39:32 +0900
Sergey Senozhatsky wrote:
> On (09/19/18 10:27), He Zhe wrote:
> > On 2018年09月19日 09:50, Sergey Senozhatsky wrote:
> > > On (09/19/18 01:17), zhe...@windriver.com wrote:
> > >> @@ -1048,7 +1048,14 @@ static void __init log_buf_len_update(unsigned
> > >> siz
On (09/19/18 10:27), He Zhe wrote:
> On 2018年09月19日 09:50, Sergey Senozhatsky wrote:
> > On (09/19/18 01:17), zhe...@windriver.com wrote:
> >> @@ -1048,7 +1048,14 @@ static void __init log_buf_len_update(unsigned size)
> >> /* save requested log_buf_len since it's too early to process it */
> >>
On 2018年09月19日 09:50, Sergey Senozhatsky wrote:
> On (09/19/18 01:17), zhe...@windriver.com wrote:
>> @@ -1048,7 +1048,14 @@ static void __init log_buf_len_update(unsigned size)
>> /* save requested log_buf_len since it's too early to process it */
>> static int __init log_buf_len_setup(char *
On (09/19/18 01:17), zhe...@windriver.com wrote:
> Add KBUILD_MODNAME to make prints more clear.
No strong opinion. I'm OK with this change.
> And use 'unsigned int' intead of 'unsigned' according to
> checkpatch.pl's suggestion.
I don't think that "unsigned int" is the right thing to use there.
For platforms whose firmwares provide valid module handles
(SMBIOS type 17) in error records, this patch uses the module
handles to locate corresponding DIMMs and enables per-DIMM
error counter update.
Signed-off-by: Fan Wu
Reviewed-by: Tyler Baicar
Reviewed-by: James Morse
Tested-by: Toshi Kan
On Mon, Sep 17, 2018 at 09:26:07AM -0400, Masayoshi Mizuma wrote:
> On Fri, Aug 31, 2018 at 02:55:36AM +, Naoya Horiguchi wrote:
> > On Wed, Aug 29, 2018 at 11:16:30AM -0400, Masayoshi Mizuma wrote:
> > > Hi Horiguchi-san and Pavel
> > >
> > > Thank you for your comments!
> > > The Pavel's add
On 2018/9/19 1:17, Andy Gross wrote:
> On Tue, Sep 18, 2018 at 01:06:48PM +0800, zhong jiang wrote:
>> Fix the following compile warning:
>>
>> drivers/soc/qcom/cmd-db.c:194:38: warning: 'ent.addr' may be used
>> uninitialized in this function [-Wmaybe-uninitialized]
>> return ret < 0 ? 0 : le32
On (09/19/18 01:17), zhe...@windriver.com wrote:
> @@ -1048,7 +1048,14 @@ static void __init log_buf_len_update(unsigned size)
> /* save requested log_buf_len since it's too early to process it */
> static int __init log_buf_len_setup(char *str)
> {
> - unsigned size = memparse(str, &str);
>
On (09/19/18 10:12), Sergey Senozhatsky wrote:
> On (09/18/18 07:06), Guenter Roeck wrote:
> > > So the check either better be
> > >
> > > if (fc->ops && fc->ops->reconfigure)
> > >
> >
> > Since there are multiple instances of fs_context where fc->ops isn't set,
> > this check would be needed
No user of tegra_pinctrl_probe can be built as a module, hence
exporting the symbol is not necessary. Drop EXPORT_SYMBOL_GPL.
Signed-off-by: Stefan Agner
---
drivers/pinctrl/tegra/pinctrl-tegra.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/pinctrl/tegra/pinctrl-tegra.c
b/drivers/
The Tegra pinctrl drivers are always built-in. This allows to use
platform_driver_probe() and mark several functions as __init.
This allows the kernel to free about 1KiB of memory if Tegra
pinctrl drivers are not used.
Signed-off-by: Stefan Agner
---
drivers/pinctrl/tegra/pinctrl-tegra.c| 6
On Wed, Sep 12, 2018 at 07:22:33PM -0700, Dan Williams wrote:
> Commit e8d513483300 "memremap: change devm_memremap_pages interface to
> use struct dev_pagemap" refactored devm_memremap_pages() to allow a
> dev_pagemap instance to be supplied. Passing in a dev_pagemap interface
> simplifies the des
The clocksource watchdog, when running, is scheduled on all the CPUs in
the system sequentially on a round-robin fashion with a period of 0.5s.
A bug in the 4.18 kernel is causing missing ticks when nohz_full
is specified. Under some circumstances, this causes the watchdog to
incorrectly state that
On 2018-09-14 14:40, Michal Hocko wrote:
On Wed 12-09-18 20:12:30, Arun KS wrote:
On 2018-09-12 18:47, Michal Hocko wrote:
> On Wed 12-09-18 22:57:43, Balbir Singh wrote:
> > On Wed, Sep 12, 2018 at 12:38:53PM +0200, Michal Hocko wrote:
> > > On Wed 12-09-18 14:56:45, Arun KS wrote:
> > > > When
The license text is specifying GPL v2 only but the MODULE_LICENSE is set to
GPL which means GNU Public License v2 or later. When MODULE_LICENSE and
boiler plate does not match, go for boiler plate license.
Signed-off-by: Alexandre Belloni
---
drivers/rtc/rtc-test.c | 2 +-
1 file changed, 1 inse
Replace the license boilerplate by an SPDX identifier
Signed-off-by: Alexandre Belloni
---
drivers/rtc/rtc-test.c | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/drivers/rtc/rtc-test.c b/drivers/rtc/rtc-test.c
index 93f1638fb8c8..6c5f09c815e8 100644
--- a/drivers/rtc/rtc-
The default word_size and stride of 1 are correct for the tx4939. Also fix
the nvmem folder name.
Signed-off-by: Alexandre Belloni
---
drivers/rtc/rtc-tx4939.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/rtc/rtc-tx4939.c b/drivers/rtc/rtc-tx4939.c
index 08dbefc
On (09/18/18 17:39), David Howells wrote:
[..]
> -static int legacy_init_fs_context(struct fs_context *fc, struct dentry
> *dentry)
> +int legacy_init_fs_context(struct fs_context *fc, struct dentry *dentry)
> {
> + switch (fc->purpose) {
> + default:
> + fc->fs_private = kzal
The core header file is reserved for the core, stop including it.
Also reorder includes alphabetically.
Signed-off-by: Alexandre Belloni
---
drivers/rtc/rtc-isl1208.c | 7 +++
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/drivers/rtc/rtc-isl1208.c b/drivers/rtc/rtc-isl1208.c
Move rtc_add_group and rtc_add_groups definition to rtc.h that is available
for all RTC drivers.
Signed-off-by: Alexandre Belloni
---
drivers/rtc/rtc-core.h | 14 --
include/linux/rtc.h| 16
2 files changed, 16 insertions(+), 14 deletions(-)
diff --git a/drivers
On (09/18/18 07:06), Guenter Roeck wrote:
> > So the check either better be
> >
> > if (fc->ops && fc->ops->reconfigure)
> >
>
> Since there are multiple instances of fs_context where fc->ops isn't set,
> this check would be needed wherever fc->ops is dereferenced.
Right. If fc is always gu
A few entries are not placed correctly, reorder them.
Signed-off-by: Alexandre Belloni
---
drivers/rtc/Makefile | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/drivers/rtc/Makefile b/drivers/rtc/Makefile
index 5ff2fc0c361a..290c1730fb0a 100644
--- a/drivers/rtc/M
Hi,
In the linux kernel commit 91ab076e3a2f092254fe5231bbfa92b37fd52e38 the
vendor prefix "arctic" was added to vendor-prefixes.txt.
The original change I authored used "arc" not "arctic", and the device
tree bindings were added assuming that prefix in commit
ce9d22573d85341c987f997461ac712e
On Mon, Aug 20, 2018 at 09:52:19PM +, Woodhouse, David wrote:
> On Mon, 2018-08-20 at 14:48 -0700, Linus Torvalds wrote:
> >
> > Of course, after the long (and entirely unrelated) discussion about
> > the TLB flushing bug we had, I'm starting to worry about my own
> > competence, and maybe I'm
On Mon, Sep 17, 2018 at 11:07 AM Dmitry Torokhov
wrote:
>
> On Sun, Sep 16, 2018 at 05:54:33PM -0500, Rob Herring wrote:
> > On Wed, Sep 05, 2018 at 05:26:47PM +0800, Anson Huang wrote:
> > > Add support for wakeup event action, this would allow the device
> > > to configure whether to be a wakeup
On Mon, Sep 17, 2018 at 8:41 AM Guo Ren wrote:
>
> On Mon, Sep 17, 2018 at 07:23:36AM -0700, Rob Herring wrote:
> > On Mon, Sep 17, 2018 at 1:36 AM Guo Ren wrote:
> > >
> > > On Mon, Sep 17, 2018 at 02:23:36AM -0400, Rob Herring wrote:
> > > > On Sun, Sep 16, 2018 at 04:50:03PM +0800, Guo Ren wro
FYI, we noticed the following commit (built with gcc-6):
commit: 8762c83c14e566226b11c68bf01ce7d5d70fee29 ("security: Kill off the
sb_copy_data hook")
https://git.kernel.org/cgit/linux/kernel/git/dhowells/linux-fs.git
btrfs-mount-api
in testcase: trinity
with following parameters:
runt
1 - 100 of 693 matches
Mail list logo
