On Sun, 17 Jun 2018 15:46:49 +0200,
Stefan Agner wrote:
>
> Currently a variable of type enum CT_AMIXER_CTL is used for enum
> CT_SUM_CTL values. This leads to warnings when using clang:
> sound/pci/ctxfi/ctmixer.c:945:32: warning: implicit conversion from
> enumeration type
> 'enum
The API got renamed for consistency and the old name will
be removed once the last users are gone.
Signed-off-by: Arnd Bergmann
---
include/sound/pcm.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/sound/pcm.h b/include/sound/pcm.h
index 5d5daa190b08..f566611f0fef
On Mon, Jun 18, 2018 at 12:42 PM, Emmanuel Vadot wrote:
> The RIoTboard debug uart is connected to serial1.
> Add a chosen property in the DTS so OS knows what serial port to use for
> the console.
>
> Signed-off-by: Emmanuel Vadot
Reviewed-by: Fabio Estevam
On Mon, Jun 18, 2018 at 5:07 PM, Pavel Machek wrote:
> Hi!
>
>> get_monotonic_boottime() is deprecated, so let's convert this to
>> the simpler ktime_get_boot_ns().
>>
>> Signed-off-by: Arnd Bergmann
>
> Have you tested it?
No, only build-tested.
>> diff --git
On Mon, Jun 18, 2018 at 5:44 PM Mika Westerberg
wrote:
>
> The commit 9aaa3b8b4c56 ("thunderbolt: Add support for preboot ACL")
> introduced boot_acl attribute but missed the fact that now userspace
> needs to poll the attribute constantly to find out whether it has
> changed or not. Fix this by
On Mon, Jun 18, 2018 at 01:28:54PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> After merging the xarray tree, today's linux-next build (x86_64
> allmodconfig) produced this warning:
>
> WARNING: modpost: missing MODULE_LICENSE() in lib/test_xarray.o
>
> Introduced by commit
>
> d968f529e39f
Am Montag, den 18.06.2018, 17:42 +0200 schrieb Emmanuel Vadot:
> The RIoTboard debug uart is connected to serial1.
> Add a chosen property in the DTS so OS knows what serial port to use for
> the console.
>
> > Signed-off-by: Emmanuel Vadot
> ---
> arch/arm/boot/dts/imx6dl-riotboard.dts | 4
On Mon, Jun 18, 2018 at 04:54:40PM +0100, Will Deacon wrote:
> On Mon, Jun 18, 2018 at 11:19:10AM +0100, Mark Rutland wrote:
> > /**
> > - * atomic64_add_unless - add unless the number is a given value
> > + * atomic64_fetch_add_unless - add unless the number is a given value
> > * @v: pointer
On Mon, 18 Jun 2018 18:03:17 +0200
Lucas Stach wrote:
> Am Montag, den 18.06.2018, 17:42 +0200 schrieb Emmanuel Vadot:
> > The RIoTboard debug uart is connected to serial1.
> > Add a chosen property in the DTS so OS knows what serial port to use for
> > the console.
> >
> > > Signed-off-by:
On Mon, 11 Jun 2018 15:47:12 -0700, Florian Fainelli
wrote:
> The i2c controller should use IRQ_TYPE_LEVEL_HIGH instead of
> IRQ_TYPE_NONE.
>
> Fixes: 0f9f27a36d09 ("ARM: dts: NSP: Add I2C support to the DT")
> Signed-off-by: Florian Fainelli
> ---
Applied to devicetree/fixes, thanks!
--
On Mon, Jun 18, 2018 at 11:19:01AM +0100, Mark Rutland wrote:
> This series contains a few cleanups of the atomic API, fixing
> inconsistencies between atomic_* and atomic64_*, and minimizing
> repetition in arch code. This is nicer for arch code, and the improved
> regularity will help when
On Mon, 11 Jun 2018 15:47:14 -0700, Florian Fainelli
wrote:
> The i2c and PCIe controllers had an incorrect type which should have
> been set to IRQ_TYPE_LEVEL_HIGH, fix that.
>
> Fixes: b9099ec754b5 ("ARM: dts: Add Broadcom Hurricane 2 DTS include file")
> Signed-off-by: Florian Fainelli
>
On Mon, 11 Jun 2018 15:53:40 -0700, Florian Fainelli
wrote:
> The i2c controller should be using IRQ_TYPE_LEVEL_HIGH, fix that.
>
> Fixes: bb097e3e0045 ("ARM: dts: BCM5301X: Add I2C support to the DT")
> Signed-off-by: Florian Fainelli
> ---
Applied to devicetree/fixes, thanks!
--
Florian
On Mon, Jun 18, 2018 at 8:07 AM, Gustavo A. R. Silva
wrote:
> Hi Steve,
>
> While doing some static analysis I came across the following piece of code at
> fs/cifs/smb2pdu.c:2017:
>
> 2017if (n_iov > 2) {
> 2018struct create_context *ccontext =
> 2019
Hi Arnd,
I love your patch! Yet something to improve:
[auto build test ERROR on powerpc/next]
[also build test ERROR on v4.18-rc1 next-20180618]
[cannot apply to m68k/for-next]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https
On Mon, Jun 18, 2018 at 09:50:33AM -0700, Dan Williams wrote:
> On Sun, Jun 17, 2018 at 8:27 PM, Stephen Rothwell
> wrote:
> > Hi all,
> >
> > After merging the xarray tree, today's linux-next build (powerpc
> > ppc64_defconfig) failed like this:
[...]
> > from the nvdimm tree.
> >
> > Willy
On Mon, Jun 18 2018 at 11:23 -0600, Douglas Anderson wrote:
Children of RPMh will need access to cmd_db. Rather than having each
child have code to check if cmd_db is ready let's add the check to
RPMh.
Suggested-by: Stephen Boyd
Signed-off-by: Douglas Anderson
Acked-by: Lina Iyer
---
This
Hi,
On Mon, Jun 18, 2018 at 6:37 AM, Raju P L S S S N
wrote:
> From: "Raju P.L.S.S.S.N"
[ ... ]
> This set of patches add the ability for platform drivers to make use of shared
> resources in newer Qualcomm SoCs like SDM845. Resources that are shared
> between
> multiple processors in a SoC
Hardware Info
-
Processor - Broadcom BCM4709C0KFEBG dual-core @ 1.4 GHz
Switch - BCM53012 in BCM4709C0KFEBG & external BCM53125
DDR3 RAM- 256 MB
Flash - 128 MB (Toshiba TC58BVG0S3HTA00)
2.4GHz - BCM4366 4×4 2.4/5G single chip 802.11ac SoC
ATENCIÓN;
Su buzón ha superado el límite de almacenamiento, que es de 5 GB definidos por
el administrador, quien actualmente está ejecutando en 10.9GB, no puede ser
capaz de enviar o recibir correo nuevo hasta que vuelva a validar su buzón de
correo electrónico. Para revalidar su buzón de
On Mon, Jun 18, 2018 at 11:19:08AM +0100, Mark Rutland wrote:
> Currently architecture must implement atomic_fetch_add_unless(), with
> common code providing atomic_add_unless(). Architectures must also
> implement atmic64_add_unless() directly, with no corresponding
> atomic64_fetch_add_unless().
On 06/18/2018 08:13 AM, Keno Fischer wrote:
>>> 4) Catch the fault thrown by xsaves/xrestors in this situation, update
>>> XCR0, redo the xsaves/restores, put XCR0 back and continue
>>> execution after the faulting instruction.
>>
>> I'm worried about the kernel pieces that go digging in
On Mon, 11 Jun 2018 15:47:13 -0700, Florian Fainelli
wrote:
> The interrupts for the PCIe controllers should all be of type
> IRQ_TYPE_LEVEL_HIGH instead of IRQ_TYPE_NONE.
>
> Fixes: d71eb9412088 ("ARM: dts: NSP: Add MSI support on PCI")
> Fixes: 522199029fdc ("ARM: dts: NSP: Fix PCIE DT
On 06/12/2018 01:21 PM, Ray Jui wrote:
> This patch series fixes incorrect interrupt types for I2C and PCIe in DT
> for Broadcom Cygnus, NS2, and Stingray SoCs
>
> This patch series is based off v4.17 and is available on GIHUB:
> repo: https://github.com/Broadcom/arm64-linux.git
> branch:
On Wed, Jun 13, 2018 at 12:29:48AM -0700, Joel Fernandes wrote:
> (I'm actually not working this week, but still thought of replying :))
>
> On Wed, Jun 13, 2018 at 02:57:11PM +0800, kernel test robot wrote:
> >
> > FYI, we noticed the following commit (built with gcc-4.9):
> >
> > commit:
On Tue, Jun 12, 2018 at 05:07:37PM +0800, Zhizhou Zhang wrote:
> We can't call function trace hook before setup percpu offset.
> When entering secondary_start_kernel(), percpu offset has not
> been initialized. So this lead hotplug malfunction.
> Here is the flow to reproduce this bug:
>
> echo
On 6/17/2018 11:03 PM, Lee Jones wrote:
On Thu, 14 Jun 2018, Jae Hyun Yoo wrote:
[...]
+Example:
+ peci-bus@0 {
0?
Because the actual reg value of the peci bus is reg = <0x0 0x60> but
anyway it's an example.
+ #address-cells = <1>;
+ #size-cells = <0>;
Dear Friend,
I am Mr.Arouna Sali the head of file department of Bank of
Africa(B.O.A) here in Burkina Faso / Ouagadougou. In my department we
discover an abandoned sum of (US$18 million US Dollars) in an account
that belongs to one of our foreign customer who died along with his
family in plane
On 06/18/2018 07:42 AM, Keno Fischer wrote:
>> But, in any case, so how is this supposed to work?
>>
>> // get features we are disabling into values matching the
>> // hardware "init state".
>> __asm__("XRSTOR %reg1,%reg2", ...);
>> prctl(PRCTL_SET_XCR0, something);
Remove leading 0x from recently introduced unit addresses to fix DTC
warnings:
Warning (unit_address_format): /soc/sysmmu@0x1504: unit name should not
have leading "0x"
Signed-off-by: Krzysztof Kozlowski
---
arch/arm64/boot/dts/exynos/exynos5433.dtsi | 4 ++--
1 file changed, 2
The decon, decon_tv and dsi nodes have only one child port so
address/size mappings are not necessary. This fixes DTC warnings like:
Warning (graph_child_address): /soc/decon@1380/ports:
graph node has single child node 'port@0', #address-cells/#size-cells
are not necessary
This adjusts the allocator calls to use 2-factor argument call style, as
done treewide already for improved defense against allocation overflows.
Signed-off-by: Kees Cook
---
drivers/bus/ti-sysc.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/bus/ti-sysc.c
PCIe downtraining happens when both the device and PCIe port are
capable of a larger bus width or higher speed than negotiated.
Downtraining might be indicative of other problems in the system, and
identifying this from userspace is neither intuitive, nor straigh
forward.
The easiest way to
> index 17383f9677fa..032b9a1ba8e1 100644
> --- a/arch/x86/mm/init_64.c
> +++ b/arch/x86/mm/init_64.c
> @@ -731,6 +731,8 @@ kernel_physical_mapping_init(unsigned long paddr_start,
> pgd_changed = true;
> }
>
> + sync_direct_mapping();
> +
> if (pgd_changed)
>
On Mon, Jun 18 2018 at 07:37 -0600, Raju P L S S S N wrote:
From: Lina Iyer
Sending RPMH requests and waiting for response from the controller
through a callback is common functionality across all platform drivers.
To simplify drivers, add a library functions to create RPMH client and
send
Hi Tony,
> Am 18.06.2018 um 13:51 schrieb Tony Lindgren :
>
> * Christ van Willegen [180618 10:01]:
>>> --- a/drivers/pinctrl/core.c
>>> +++ b/drivers/pinctrl/core.c
>>> + if (!strcmp(function, gname))
>>
>>
>> This could never fail? gname guaranteed to never == NULL?
If there
On Tue, Jun 12, 2018 at 11:08:31PM +0200, Maciej S. Szmigiero wrote:
> That was the solution before this patch series version (6) - there was
> a variable holding the CPU equivalence table size for the late loader,
> but you didn't like it:> Instead of adding yet another global var which needs
>
> Unfortunately, that is insufficient. Almost difference in CPU behavior
> between the replayer
> and the replayee. In particular, the problems for rr here are
> 1) xgetbv, which can introduce differing register contents (and if
> code branches on this,
> potentially differences in control
On Mon, Jun 18, 2018 at 02:22:40PM +1000, NeilBrown wrote:
>
> Unfortunately the patch for adding list_for_each_entry_from_rcu()
> wasn't the final patch after all review. It is functionally
> correct but the documentation was incomplete.
>
> This patch adds this missing documentation which
Commit e1739e86f0cb9c48e8745a610e6981a4e24cadad breaks reading
the wlf,ldoena property from device tree. This causes ldo1 to
stay off and thus arizona device detection to fail:
[4.495958] of_get_named_gpiod_flags: parsed 'wlf,reset' property of node '/s
oc/spi@7e204000/wm5102@1[0]' - status
Gustavo,
Thx for pointing this out. Let me know if this patch addresses what
you found. Code is experimental mount option but extremely important
to get right due to move away from SMB1/CIFS which had posix
extensions.
On Mon, Jun 18, 2018 at 11:55 AM, Steve French wrote:
> On Mon, Jun 18,
On Wed, Jun 13, 2018 at 05:34:03AM -0700, wi...@infradead.org wrote:
> Allocate agent IDs from a global IDR instead of an atomic variable.
> This eliminates the possibility of reusing an ID which is already in
> use after 4 billion registrations. We limit the assigned ID to be less
> than 2^24 as
From: Douglas Anderson
In commit ca04d9d3e1b1 ("phy: qcom-qusb2: New driver for QUSB2 PHY on
Qcom chips") you can see a call like:
devm_nvmem_cell_get(dev, NULL);
Note that the cell ID passed to the function is NULL. This is because
the qcom-qusb2 driver is expected to work only on systems
Use sign_extend32 kernel function instead of code duplication,
Safe also for 16 bit. and remove declaration of bits variable not needed.
Signed-off-by: Karim Eshapa
---
drivers/staging/iio/accel/adis16240.c | 11 ++-
1 file changed, 2 insertions(+), 9 deletions(-)
diff --git
When building a 64-bit 4.18-rc1 kernel with a 32-bit userland, I
noticed that stack protection was silently disabled. Adding -m64 in
gcc-x86_64-has-stack-protector.sh fixed that, similar to what has been
noticed in commit 2a61f4747eea ("stack-protector: test compiler
capability in Kconfig and
Hi Christoph,
Thanks for looking at this...
On 06/18/2018 12:56 AM, Christoph Hellwig wrote:
> On Sat, Jun 16, 2018 at 06:25:10PM -0700, john.hubb...@gmail.com wrote:
>> From: John Hubbard
>>
>> This fixes a few problems that come up when using devices (NICs, GPUs,
>> for example) that want to
On Wed, Jun 13, 2018 at 06:37:07PM +, Dave Hansen wrote:
> On 06/12/2018 07:39 AM, Kirill A. Shutemov wrote:
> > Kernel need to have a way to access encrypted memory. We are going to
> "The kernel needs"...
>
> > use per-KeyID direct mapping to facilitate the access with minimal
> > overhead.
On 06/18/2018 06:34 AM, Kirill A. Shutemov wrote:
> On Wed, Jun 13, 2018 at 06:43:08PM +, Dave Hansen wrote:
>>> diff --git a/arch/x86/include/asm/mktme.h b/arch/x86/include/asm/mktme.h
>>> index efc0d4bb3b35..d6edcabacfc7 100644
>>> --- a/arch/x86/include/asm/mktme.h
>>> +++
Hi Geert,
On 18/06/18 16:58, Geert Uytterhoeven wrote:
Hi Greg,
On Mon, Jun 18, 2018 at 8:06 AM Greg Ungerer wrote:
Booting a ColdFire m68k core with MMU enabled causes a "bad page state"
oops since commit 1d40a5ea01d5 ("mm: mark pages in use for page tables"):
BUG: Bad page state in
+Cc: Stephen
On Mon, Jun 18, 2018 at 3:54 PM, Hans de Goede wrote:
> Hi,
>
> On 18-06-18 10:43, Hans de Goede wrote:
>>
>> Hi,
>>
>> On 18-06-18 01:58, youling257 wrote:
>>>
>>> Add touchscreen info for the ONDA V891W Dual OS tablet
>>
>>
>> Nitpick: still missing a period '.' at the end, this
Hi Martin,
On Sun, 10 Jun 2018 15:31:27 +0200, Martin Kaiser
wrote:
> The v21 version of the NAND flash controller contains a Spare Area Size
> Register (SPAS) at offset 0x10. Its setting defaults to the maximum
> spare area size of 218 bytes. The size that is set in this register is
> used by
getnstimeofday64() is deprecated in favor of the ktime_get() family.
The direct replacement would be ktime_get_real_ts64(), but we only need
the seconds value, and it seems better to use boottime than real time
to avoid unexpected behavior with a concurrent settimeofday().
ktime_get_seconds()
Em Sat, Jun 16, 2018 at 10:20:21AM -0700, Yonghong Song escreveu:
>
>
> On 6/16/18 5:26 AM, Arnaldo Carvalho de Melo wrote:
> > Hi Wang, Yogong,
> >
> > While reviewing the BTF patches for pahole, I updated llvm/clang
> > to HEAD and then building perf with clang embedded I noticed this,
On Mon, Jun 18, 2018 at 01:59:18PM +, Dave Hansen wrote:
> On 06/18/2018 06:34 AM, Kirill A. Shutemov wrote:
> > On Wed, Jun 13, 2018 at 06:43:08PM +, Dave Hansen wrote:
> >>> diff --git a/arch/x86/include/asm/mktme.h b/arch/x86/include/asm/mktme.h
> >>> index efc0d4bb3b35..d6edcabacfc7
The get_seconds() call is deprecated because it overflows on 32-bit
architectures. The algorithm in rcu_torture_stall() can deal with
the overflow, but another problem here is that using a CLOCK_REALTIME
stamp can lead to a false-positive stall warning when a settimeofday()
happens concurrently.
Take an effort to recode the arm64 vdso code from assembler to C
previously submitted by Andrew Pinski , rework
it for use in both arm and arm64, overlapping any optimizations
for each architecture. But instead of landing it in arm64, land the
result into lib/vdso and unify both implementations to
Take an effort to recode the arm64 vdso code from assembler to C
previously submitted by Andrew Pinski , rework
it for use in both arm and arm64, overlapping any optimizations
for each architecture. But instead of landing it in arm64, land the
result into lib/vdso and unify both implementations to
The following 23 patches are rebased and resent, and represent a
rewrite of the arm and arm64 vDSO into C, adding support for arch32
(32-bit user space hosted 64-bit kernels) and into a common library
that other (arm, or non-arm) architectures may utilize.
[PATCH v5 01/12] arm: vdso: rename
Take an effort to recode the arm64 vdso code from assembler to C
previously submitted by Andrew Pinski , rework
it for use in both arm and arm64, overlapping any optimizations
for each architecture. But instead of landing it in arm64, land the
result into lib/vdso and unify both implementations to
>> 4) Catch the fault thrown by xsaves/xrestors in this situation, update
>> XCR0, redo the xsaves/restores, put XCR0 back and continue
>> execution after the faulting instruction.
>
> I'm worried about the kernel pieces that go digging in the XSAVE data
> getting confused more than the
Two different regulators are defined with the same name and label but
distinct properties.
The first definition was added with the first board dts and the second
was added when upstream added flexcan support.
Looking at schematics it is indeed gpio2 14 connected to the STB pin of
the CAN
From: youling257
Add touchscreen info for hardware revision "v3" of the ONDA V891W Dual
OS tablet.
Reported-and-tested-by: youling257
Signed-off-by: Hans de Goede
---
Changes in v5:
-Replaced youlin's S-o-b with mine since youlin does not want to use his
real name and I certify that he has
A lot of code is using allocation of bitmaps using BITS_PER_LONG() macro and
sizeof(unsigned long) operator. The readability suffers because of this.
The series introduces three helpers, i.e. bitmap_alloc(), bitmap_zalloc() and
bitmap_free(), to make it more cleaner.
Patch 1 is a preparatory to
From: Lina Iyer
Platform drivers need make a lot of resource state requests at the same
time, say, at the start or end of an usecase. It can be quite
inefficient to send each request separately. Instead they can give the
RPMH library a batch of requests to be sent and wait on the whole
From: "Raju P.L.S.S.S.N"
Changes in v11:
- move rpmh_request to rpmh-internal.h
- Associate rpmh_ctrl to rsc_drv
- Remove EXPORT_SYMBOL for rpmh_tx_done
- Remove IS_ERR check for ctrlr
- Remove rsc_drv instance from rpmh_ctrlr
- Initialize cache & batch cache in probe
Changes in v10:
- Remove
From: Lina Iyer
Sleep and wake requests are sent when the application processor
subsystem of the SoC is entering deep sleep states like in suspend.
These requests help lower the system power requirements when the
resources are not in use.
Sleep and wake requests are written to the TCS slots but
From: Lina Iyer
Add controller driver for QCOM SoCs that have hardware based shared
resource management. The hardware IP known as RSC (Resource State
Coordinator) houses multiple Direct Resource Voter (DRV) for different
execution levels. A DRV is a unique voter on the state of a shared
From: Lina Iyer
Log sent RPMH requests and interrupt responses in FTRACE.
Signed-off-by: Lina Iyer
Signed-off-by: Raju P.L.S.S.S.N
Reviewed-by: Steven Rostedt (VMware)
---
Changes in v7:
- varible name changes and white space
Changes in v6:
- struct tcs_response was
From: Lina Iyer
Platform drivers that want to send a request but do not want to block
until the RPMH request completes have now a new API -
rpmh_write_async().
The API allocates memory and send the requests and returns the control
back to the platform driver. The tx_done callback from the
From: Lina Iyer
Active state requests are sent immediately to the RSC controller, while
sleep and wake state requests are cached in this driver to avoid taxing
the RSC controller repeatedly. The cached values will be sent to the
controller when the rpmh_flush() is called.
Generally, flushing is
From: Lina Iyer
Some RSCs may only have sleep and wake TCS, i.e, there is no dedicated
TCS for active mode request, but drivers may still want to make active
requests from these RSCs. In such cases re-purpose the wake TCS to send
active state requests.
The requirement for this is that the
On 2018/6/18 6:09 PM, Florian Schmaus wrote:
> Fixes an error condition reported by checkpatch.pl which is caused by
> assigning a variable in an if condition.
>
> Signed-off-by: Florian Schmaus
> ---
> drivers/md/bcache/super.c | 16 +++-
> 1 file changed, 11 insertions(+), 5
> But forward bisection (when bug is fixed) unfortunately won't work
> because these commits are not connected to HEAD. And forward bisection
> is very important, otherwise who will bring order to all these
> hundreds of open bugs?
> https://syzkaller.appspot.com/
Bisection isn't so important
Hi Richard,
2018-06-18 16:22 GMT+09:00 Richard Weinberger :
> Am Freitag, 15. Juni 2018, 03:18:52 CEST schrieb Masahiro Yamada:
>> This commit improves the ->setup_data_interface() hook.
>>
>> The denali_setup_data_interface() needs the frequency of clk_x
>> and the ratio of clk_x / clk.
>>
>>
Hi Boris,
On 18.06.2018 13:59, Boris Brezillon wrote:
> Hi Stefan,
>
> On Mon, 18 Jun 2018 12:51:52 +0200
> Stefan Agner wrote:
>
>> On 18.06.2018 11:58, Boris Brezillon wrote:
>> > On Sun, 17 Jun 2018 22:45:59 +0200
>> > Stefan Agner wrote:
>> >
>> >> Changes definitly calm down, most
Take an effort from the previous 9 patches to recode the arm64 vdso
code from assembler to C previously submitted by
Andrew Pinski , rework it for use in both arm and
arm64, overlapping any optimizations for each architecture. But
instead of landing it in arm64, land the result into lib/vdso and
From: Kevin Brodsky
If the compat vDSO is enabled, we need to set AT_SYSINFO_EHDR in the
auxiliary vector of compat processes to the address of the vDSO code
page, so that the dynamic linker can find it (just like the regular vDSO).
Note that we cast context.vdso to Elf64_Off, instead of
On 6/18/18 7:31 AM, Arnaldo Carvalho de Melo wrote:
Em Sat, Jun 16, 2018 at 10:20:21AM -0700, Yonghong Song escreveu:
On 6/16/18 5:26 AM, Arnaldo Carvalho de Melo wrote:
Hi Wang, Yogong,
While reviewing the BTF patches for pahole, I updated llvm/clang
to HEAD and then building
Em Mon, Jun 18, 2018 at 08:10:27AM -0700, Yonghong Song escreveu:
> On 6/18/18 7:31 AM, Arnaldo Carvalho de Melo wrote:
> > Em Sat, Jun 16, 2018 at 10:20:21AM -0700, Yonghong Song escreveu:
> > > There is an interface change in llvm 7.0 (trunk) for function
> > >
The following changes since commit 716a685fdb89942a50c4138141027e38336a895f:
Merge branch 'x86-hyperv-for-linus' of
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip (2018-06-04 21:37:30
-0700)
are available in the Git repository at:
git://github.com/kleikamp/linux-shaggy.git
Hi Steve,
While doing some static analysis I came across the following piece of code at
fs/cifs/smb2pdu.c:2017:
2017if (n_iov > 2) {
2018struct create_context *ccontext =
2019(struct create_context *)iov[n_iov-1].iov_base;
2020
On Wed, Jun 13, 2018 at 06:41:21PM +, Dave Hansen wrote:
> On 06/12/2018 07:39 AM, Kirill A. Shutemov wrote:
> > arch/x86/include/asm/mktme.h | 6 +
> > arch/x86/mm/init_64.c| 6 +
> > arch/x86/mm/mktme.c | 444 +++
> > 3 files changed, 456
-Original Message-
From: Boris Brezillon [mailto:boris.brezil...@bootlin.com]
Sent: Friday, June 15, 2018 7:26 PM
To: Yogesh Narayan Gaur ; Fabio Estevam
; David Wolfe ; dw...@infradead.org
Cc: rich...@nod.at; Prabhakar Kushwaha ; Han Xu
; linux-kernel@vger.kernel.org;
From: Lina Iyer
Add device binding documentation for Qualcomm Technology Inc's RPMH RSC
driver. The driver is used for communicating resource state requests for
shared resources.
Cc: devicet...@vger.kernel.org
Signed-off-by: Lina Iyer
Reviewed-by: Rob Herring
---
Changes in v8:
-
On Wed, Jun 13, 2018 at 06:46:34PM +, Dave Hansen wrote:
> On 06/12/2018 07:39 AM, Kirill A. Shutemov wrote:
> > Add new config option to enabled/disable Multi-Key Total Memory
> > Encryption support.
> >
> > MKTME uses MEMORY_PHYSICAL_PADDING to reserve enough space in per-KeyID
> > direct
Some misannotations cropped up in this cycle's merges;
the fixes are trivial. Do you prefer it in one commit, or
split into per-driver pieces?
Signed-off-by: Al Viro
---
diff --git a/drivers/android/binder.c b/drivers/android/binder.c
index 95283f3bb51c..7fbb86215809 100644
---
Hi Boris,
On Wed, 13 Jun 2018 14:32:36 +0530, Abhishek Sahu
wrote:
> Positive return value from read_oob() is making false BAD
> blocks. For some of the NAND controllers, OOB bytes will be
> protected with ECC and read_oob() will return number of bitflips.
> If there is any bitflip in ECC
The I2S mux clock can be used to select the I2S input clock. The
available parents are the peripheral and the generated clocks.
Signed-off-by: Codrin Ciubotariu
---
Changes in v5:
- specified clock's parent;
- added a newline before adding the clock's compatible string;
From: Cyrille Pitchen
This patch adds DT nodes for I2S0 and I2S1. It also adds an alias for
each I2S node.
Signed-off-by: Cyrille Pitchen
[codrin.ciubota...@microchip.com: added phandle to new mux clock]
Signed-off-by: Codrin Ciubotariu
---
The bindings for the I2S node are applied to
This patch adds two clock muxes for the two I2S
buses present on sama5d2 platforms.
Signed-off-by: Codrin Ciubotariu
---
arch/arm/boot/dts/sama5d2.dtsi | 18 ++
1 file changed, 18 insertions(+)
diff --git a/arch/arm/boot/dts/sama5d2.dtsi b/arch/arm/boot/dts/sama5d2.dtsi
index
Hi Dave,
thank you for your thorough comments, replies inline:
On Mon, Jun 18, 2018 at 8:47 AM, Dave Hansen
wrote:
> On 06/16/2018 05:33 PM, Keno Fischer wrote:
>> For my use case, it would be sufficient to simply disallow
>> any value of XCR0 with "holes" in it,
> But what if the hardware you
The commit 9aaa3b8b4c56 ("thunderbolt: Add support for preboot ACL")
introduced boot_acl attribute but missed the fact that now userspace
needs to poll the attribute constantly to find out whether it has
changed or not. Fix this by sending notification to the userspace
whenever the boot_acl
Take an effort to recode the arm64 vdso code from assembler to C
previously submitted by Andrew Pinski , rework
it for use in both arm and arm64, overlapping any optimizations
for each architecture. But instead of landing it in arm64, land the
result into lib/vdso and unify both implementations to
From: Kevin Brodsky
AArch32 processes are currently installed a special [vectors] page that
contains the sigreturn trampolines and the kuser helpers, at the fixed
address mandated by the kuser helpers ABI.
Having both functionalities in the same page has become problematic,
because:
* It makes
From: Mark Salyzyn
Add time() vdso support to match up with existing support in the x86's
vdso. Currently benefitting arm and arm64 which uses the common
vgettimeofday.c implementation. On arm provides about a ~14 fold
improvement in speed over the straight syscall, and about a ~5 fold
From: Kevin Brodsky
AArch32 processes are currently installed a special [vectors] page that
contains the sigreturn trampolines and the kuser helpers, at the fixed
address mandated by the kuser helpers ABI.
Having both functionalities in the same page has become problematic,
because:
* It makes
The RIoTboard debug uart is connected to serial1.
Add a chosen property in the DTS so OS knows what serial port to use for
the console.
Signed-off-by: Emmanuel Vadot
---
arch/arm/boot/dts/imx6dl-riotboard.dts | 4
1 file changed, 4 insertions(+)
diff --git
Hi Chris,
On Mon, 18 Jun 2018 16:52:54 +1200, Chris Packham
wrote:
> Some Micron NAND chips (MT29F1G08ABAFAWP-ITE:F) report 00 00 for the
> revision number field of the ONFI parameter page. Rather than rejecting
> these outright assume ONFI version 1.0 if the revision number is 00 00.
>
On Mon, Jun 18, 2018 at 12:54:29PM +, Dave Hansen wrote:
> On 06/18/2018 03:07 AM, Kirill A. Shutemov wrote:
> > On Wed, Jun 13, 2018 at 06:20:10PM +, Dave Hansen wrote:
> >>> +int page_keyid(const struct page *page)
> >>> +{
> >>> + if (mktme_status != MKTME_ENABLED)
> >>> +
501 - 600 of 2166 matches
Mail list logo
