From: Arnaldo Carvalho de Melo
Another step in the road to elliminate the MAP_{FUNCTION,VARIABLE}
separation, reducing the exposure to these details in the tools using
the symbol APIs.
Cc: Adrian Hunter
Cc: David Ahern
Cc: Jiri Olsa
Cc: Namhyung Kim
Cc: Wang Nan
Link: https://lkml.kernel.or
From: Arnaldo Carvalho de Melo
Out of thread__find_add_map(..., MAP__FUNCTION, ...), idea here is to
continue removing references to MAP__{FUNCTION,VARIABLE} ahead of
getting both types of symbols in the same rbtree, as various places do
two lookups, looking first at MAP__FUNCTION, then at MAP__V
From: Hendrik Brueckner
The output of perf test and perf test list differ because perf test list
does not display subtests. Correct this behavior and also let perf test
list report subtests.
For example:
$ ./perf test 2>&1 |wc -l
65
Without this commit:
$ ./perf test l
From: Arnaldo Carvalho de Melo
To further simplify checking if symbols are available for a given map
and to reduce the number of users of MAP__{FUNCTION,VARIABLE}.
Cc: Adrian Hunter
Cc: David Ahern
Cc: Jiri Olsa
Cc: Namhyung Kim
Cc: Wang Nan
Link: https://lkml.kernel.org/n/tip-iyfoyvbfdti5u
From: Arnaldo Carvalho de Melo
Shorter, should be equivalent code, use it.
Cc: Adrian Hunter
Cc: David Ahern
Cc: Jiri Olsa
Cc: Namhyung Kim
Cc: Wang Nan
Link: https://lkml.kernel.org/n/tip-q90olng8sfkvrnsrwu7xn...@git.kernel.org
Signed-off-by: Arnaldo Carvalho de Melo
---
tools/perf/util/
Hi Sasha,
On Tue, May 1, 2018 at 6:38 PM, Sasha Levin
wrote:
> Working on AUTOSEL, it became even more obvious to me how difficult it is for
> a
> patch to get a proper review. Maintainers found it difficult to keep up with
> the upstream work for their subsystem, and reviewing additional -stabl
On 5/2/18 9:29 AM, Colin King wrote:
From: Colin Ian King
Currently, the check that ret_val is not -ENOENT is always true and
the quirk bit BYT_RY5651_MCLK_EN is never being cleared because ret_val
is always zero at this point from a previous assignment earlier on.
I believe that ret_val should
Hi Sasha,
On Tue, May 1, 2018 at 6:38 PM, Sasha Levin
wrote:
> Working on AUTOSEL, it became even more obvious to me how difficult it is for
> a
> patch to get a proper review. Maintainers found it difficult to keep up with
> the upstream work for their subsystem, and reviewing additional -stabl
From: Arnaldo Carvalho de Melo
Shorter form to figure out if a given map is the kernel one and also
reduces the number of code accessing MAP__{FUNCTION,VARIABLE}, that
should go away at some point.
Cc: Adrian Hunter
Cc: David Ahern
Cc: Jiri Olsa
Cc: Namhyung Kim
Cc: Wang Nan
Link: https://l
From: Jiri Olsa
Adding support to display visual aid 'length strings' to easily spot the
biggest difference in time table.
$ perf stat -r 10 --table perf bench sched pipe
...
Performance counter stats for './perf bench sched pipe' (5 runs):
# Table of individual measurement
From: Jiri Olsa
Add --table option to display time for each run (-r option), like:
$ perf stat --null -r 5 --table perf bench sched pipe
Performance counter stats for './perf bench sched pipe' (5 runs):
# Table of individual measurements:
5.379 (-0.176)
From: Jiri Olsa
Add 'check_2' function to check 2 different files, the 'check' function
stays to check files that differs only in the prefix path.
In upcoming changes we need to check header files in locations which
don't follow the prefix logic.
Signed-off-by: Jiri Olsa
Cc: Alexander Shishkin
From: Ravi Bangoria
User can remove files from cache using --remove/--purge options but both
needs list of files as an argument. It's not convenient when you want to
flush out entire cache. Add an option to purge all files from cache.
Ex,
# perf buildid-cache -l
8a86ef73e44067bca52cc3f6cd3
On Wed, May 02, 2018 at 02:38:42PM +, Andrey Konovalov wrote:
> > Does having a tagged address here makes any difference? I couldn't hit a
> > failure with my simple tests (LD_PRELOAD a library that randomly adds
> > tags to pointers returned by malloc).
>
> I think you're right, follow_page_m
On 05/01/2018 11:59 PM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20180501:
>
on x86_64 randconfig:
CC fs/cifs/smbencrypt.o
drivers/char/ipmi/ipmi_ssif.o: warning: objtool: return_hosed_msg()+0x0:
infinite recursion (objtool bug!)
drivers/char/ipmi/ipmi_ssif.o: warning: objtoo
Quoting Geert Uytterhoeven (2018-04-18 07:50:02)
> Signed-off-by: Geert Uytterhoeven
> Acked-by: Daniel Lezcano
> ---
Applied to clk-next
Quoting Geert Uytterhoeven (2018-04-18 07:50:01)
> The use of of_clk_get_parent_{count,name}() and of_clk_init() is not
> limited to clock providers.
>
> Hence move these helpers into their own header file, so callers that are
> not clock providers no longer have to include .
>
> Suggested-by: St
Quoting Geert Uytterhoeven (2018-04-18 07:50:05)
> A new open coder has crept in since 470b73a38470e8ba ("pinctrl: sunxi:
> Use of_clk_get_parent_count() instead of open coding"), replace it.
>
> of_clk_get_parent_count() was moved to , so include that
> instead of .
>
> Signed-off-by: Geert Uytt
Quoting Chris Wilson (2018-05-02 10:46:07)
> Quoting Matthias Kaehlcke (2018-05-01 19:24:40)
> > Commit 39bf4de89ff7 ("drm/i915: Add -Wall -Wextra to our build, set
> > warnings to full") enabled extra warnings for i915 to spot possible
> > bugs in new code, and then disabled a subset of these warn
Quoting Geert Uytterhoeven (2018-04-18 07:50:04)
> As of_clk_get_parent_count() returns zero on failure, while
> of_count_phandle_with_args() might return a negative error code, this
> also fixes the issue of possibly using a very big number in the
> allocation below.
>
> Signed-off-by: Geert Uytt
Hi Sebastian,
On 02/05/18 12:57, Sebastian Reichel wrote:
> Hi,
>
> I found one more issue, otherwise the driver looks fine to me.
>
> On Wed, May 02, 2018 at 11:53:42AM +0200, Enric Balletbo i Serra wrote:
>> This driver gets various bits of information about what is connected to
>> USB PD port
Quoting Geert Uytterhoeven (2018-04-18 07:50:03)
> As of_clk_get_parent_count() returns zero on failure, while
> of_count_phandle_with_args() might return a negative error code, this
> also fixes the issue of possibly using a negative number in the
> allocation below.
>
> Signed-off-by: Geert Uytt
>>> On 02.05.18 at 17:22, wrote:
> On 05/02/2018 11:01 AM, Jan Beulich wrote:
> On 02.05.18 at 17:00, wrote:
>>> On 05/02/2018 04:16 AM, Jan Beulich wrote:
>>> On 30.04.18 at 18:23, wrote:
> --- a/arch/x86/xen/xen-pvh.S
> +++ b/arch/x86/xen/xen-pvh.S
> @@ -54,6 +54,9 @@
>
On Wed, May 02, 2018 at 11:12:55PM +0800, Tiwei Bie wrote:
> On Wed, May 02, 2018 at 04:51:01PM +0300, Michael S. Tsirkin wrote:
> > On Wed, May 02, 2018 at 03:28:19PM +0800, Tiwei Bie wrote:
> > > On Wed, May 02, 2018 at 10:51:06AM +0800, Jason Wang wrote:
> > > > On 2018年04月25日 13:15, Tiwei Bie w
On Wed, May 02, 2018 at 08:37:53AM -0700, Randy Dunlap wrote:
> On 05/01/2018 11:59 PM, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20180501:
> >
>
> on x86_64 randconfig:
>
> CC fs/cifs/smbencrypt.o
> drivers/char/ipmi/ipmi_ssif.o: warning: objtool: return_hosed_msg()+0x0:
Dear all,
This is a fourth version of a patched to add support for the ChromeOS EC
USBPD charger driver, the driver has been used on Chromebooks kernel for
long time and has been ported now to mainline. The patches were tested
successfully with a Samsung Chromebook Plus and an Pixel 2 Chromebook.
On Wednesday 02 May 2018 07:44 PM, Bartlomiej Zolnierkiewicz wrote:
> Entry for Index 941 has one zero too much. Fix it.
>
Acked-by: Keerthy
> Signed-off-by: Bartlomiej Zolnierkiewicz
> ---
> v2:
> - Fix patch description.
>
> drivers/thermal/ti-soc-thermal/omap5-thermal-data.c |2 +-
>
Check whether this EC instance has USBPD host command support and
instatiate the cros_usbpd-charger driver as a subdevice in such case.
Signed-off-by: Enric Balletbo i Serra
---
Changes in v4: None
Changes in v3: None
Changes in v2:
- [3/3] Use ARRAY_SIZE instead of hardcoded 1.
drivers/mfd/cr
From: Sameer Nanda
This driver gets various bits of information about what is connected to
USB PD ports from the EC and converts that into power_supply properties.
Signed-off-by: Sameer Nanda
Signed-off-by: Enric Balletbo i Serra
Acked-by: Lee Jones
---
Changes in v4:
- [2/3] Drop cros_ec_de
On Wed, 2018-05-02 at 09:45 -0500, Eric W. Biederman wrote:
> Mimi Zohar writes:
>
> > Allow LSMs and IMA to differentiate between the kexec_load and
> > kexec_file_load syscalls by adding an "unnecessary" call to
> > security_kernel_read_file() in kexec_load. This would be similar to the
> > ex
From: Sameer Nanda
The USBPD charger driver gets information from the ChromeOS EC, this
patch adds the USBPD charger definitions needed by this driver.
Signed-off-by: Sameer Nanda
Signed-off-by: Enric Balletbo i Serra
---
Changes in v4: None
Changes in v3:
- [1/3] Use the BIT macro.
Changes
Signed-off-by: Christian Brauner
---
include/linux/statfs.h | 26 +-
1 file changed, 13 insertions(+), 13 deletions(-)
diff --git a/include/linux/statfs.h b/include/linux/statfs.h
index 3142e98546ac..b336c04e793c 100644
--- a/include/linux/statfs.h
+++ b/include/linux/sta
Signed-off-by: Christian Brauner
---
fs/statfs.c| 2 ++
include/linux/statfs.h | 1 +
2 files changed, 3 insertions(+)
diff --git a/fs/statfs.c b/fs/statfs.c
index 61b3063d3921..2fc6f9c3793c 100644
--- a/fs/statfs.c
+++ b/fs/statfs.c
@@ -31,6 +31,8 @@ static int flags_by_mnt(int mnt_
Signed-off-by: Christian Brauner
---
fs/statfs.c| 2 ++
include/linux/statfs.h | 1 +
2 files changed, 3 insertions(+)
diff --git a/fs/statfs.c b/fs/statfs.c
index 5b2a24f0f263..61b3063d3921 100644
--- a/fs/statfs.c
+++ b/fs/statfs.c
@@ -29,6 +29,8 @@ static int flags_by_mnt(int mnt_
Signed-off-by: Christian Brauner
---
include/uapi/linux/fs.h | 33 +
1 file changed, 17 insertions(+), 16 deletions(-)
diff --git a/include/uapi/linux/fs.h b/include/uapi/linux/fs.h
index d2a8313fabd7..9662790a657c 100644
--- a/include/uapi/linux/fs.h
+++ b/includ
Hey,
This is the second resend of this patchset. I'm not sure whether it has
simply been overlooked but the number of people get_maintainer.pl was
rather small and seemed a little random so I added Linus and Christoph,
two people I know that do look at VFS stuff at least from time to time,
althoug
Signed-off-by: Christian Brauner
---
fs/statfs.c| 2 ++
include/linux/statfs.h | 1 +
2 files changed, 3 insertions(+)
diff --git a/fs/statfs.c b/fs/statfs.c
index 35ad0402c9a3..899e899ee84c 100644
--- a/fs/statfs.c
+++ b/fs/statfs.c
@@ -58,6 +58,8 @@ static int calculate_f_flags(str
Signed-off-by: Christian Brauner
---
fs/statfs.c| 10 +-
include/linux/statfs.h | 1 +
2 files changed, 10 insertions(+), 1 deletion(-)
diff --git a/fs/statfs.c b/fs/statfs.c
index 2fc6f9c3793c..35ad0402c9a3 100644
--- a/fs/statfs.c
+++ b/fs/statfs.c
@@ -10,6 +10,7 @@
#incl
If a cgroup has no associated tasks, invoking the OOM killer
won't help release any memory, so respecting the memory.min
can lead to an infinite OOM loop or system stall.
Let's ignore memory.min of unpopulated cgroups.
Signed-off-by: Roman Gushchin
Cc: Johannes Weiner
Cc: Michal Hocko
Cc: Vlad
Memory controller implements the memory.low best-effort memory
protection mechanism, which works perfectly in many cases and
allows protecting working sets of important workloads from
sudden reclaim.
But its semantics has a significant limitation: it works
only as long as there is a supply of recl
On Wed, May 02, 2018 at 04:14:32PM +0200, Bartlomiej Zolnierkiewicz wrote:
> Entry for Index 941 has one zero too much. Fix it.
>
> Signed-off-by: Bartlomiej Zolnierkiewicz
Good catch :)
I'm curious, how did you spot it ?
> ---
> v2:
> - Fix patch description.
>
> drivers/thermal/ti-soc-ther
Hi Lionel,
On 04/23/2018 05:19 PM, Lionel Debieve wrote:
Patches serie add support or RNG, CRYP and CRC IPs for stm32mp157c SoC
and add RNG default support for ev1 board.
Lionel Debieve (4):
ARM: dts: stm32: Add RNG support on stm32mp157c
ARM: dts: stm32: Enable RNG for stm32mp157c-ed1
2018-03-23 6:05 GMT+09:00 Rasmus Villemoes :
> Commit (7840fea200cd "kbuild: Fix computing srcversion for modules")
> fixed the comment above parse_source_files to refer to the new source_
> line, but left this one behind that could still give the impression that
> drivers/net/dummy.c appears in th
Break the read and write paths of the kernel.seccomp.actions_logged
sysctl into separate functions to maintain readability. An upcoming
change will need to audit writes, but not reads, of this sysctl which
would introduce too many conditional code paths on whether or not the
'write' parameter evalu
Seccomp received improved logging controls in v4.14. Applications can opt into
logging of "handled" actions (SECCOMP_RET_TRAP, SECCOMP_RET_TRACE,
SECCOMP_RET_ERRNO) using the SECCOMP_FILTER_FLAG_LOG bit when loading filters.
They can also debug filter matching with the new SECCOMP_RET_LOG action.
A
The function that converts a bitmask of seccomp actions that are
allowed to be logged is currently only used for constructing the display
string for the kernel.seccomp.actions_logged sysctl. That string wants a
space character to be used for the separator between actions.
A future patch will make
Seccomp logging for "handled" actions such as RET_TRAP, RET_TRACE, or
RET_ERRNO can be very noisy for processes that are being audited. This
patch modifies the seccomp logging behavior to treat processes that are
being inspected via the audit subsystem the same as processes that
aren't under inspec
The decision to log a seccomp action will always be subject to the
value of the kernel.seccomp.actions_logged sysctl, even for processes
that are being inspected via the audit subsystem, in an upcoming patch.
Therefore, we need to emit an audit record on attempts at writing to the
actions_logged sy
I'm announcing the release of the 4.16.7 kernel.
All users of the 4.16 kernel series must upgrade.
The updated 4.16.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.16.y
and can be browsed at the normal kernel.org git web browser:
Hi Christian,
On 5/2/2018 5:51 AM, Christian König wrote:
it would be rather nice to have if you could separate out the functions
to detect if peer2peer is possible between two devices.
This would essentially be pci_p2pdma_distance() in the existing
patchset. It returns the sum of the distanc
From: Xiang Chen
In the DQ tasklet processing it is not necessary to take the DQ
lock, as there is no contention between adding slots to the CQ and
removing slots from the matching DQ.
In addition, since we run each DQ in a separate tasklet context,
there would be no possible contention between
It is common to use readl poll timeout helpers in the
driver, so create custom wrappers.
Signed-off-by: John Garry
---
drivers/scsi/hisi_sas/hisi_sas_v3_hw.c | 28 ++--
1 file changed, 22 insertions(+), 6 deletions(-)
diff --git a/drivers/scsi/hisi_sas/hisi_sas_v3_hw.c
From: Xiang Chen
If the SCSI host enters EH, any pending IO will be processed
by SCSI EH. However it is possible that SCSI EH will try to
abort the IO and also at the same time the IO completes in the
driver. In this situation there is a small changes of freeing the
sas_task twice.
Then if anoth
From: Xiaofei Tan
Event95 is used for DFX purpose. The relevant bit for this
interrupt in the ENT_INT_SRC_MSK3 register has been disabled,
so remove the processing.
Signed-off-by: Xiaofei Tan
Signed-off-by: John Garry
---
drivers/scsi/hisi_sas/hisi_sas_v3_hw.c | 9 +
1 file changed, 1
From: Xiaofei Tan
There is an SoC bug of v3 hw development version. When hot-
unplugging a directly attached disk, the PHY down interrupt
may not happen. It is very easy to appear on some boards.
When this issue occurs, the controller will receive many invalid
dword frames, and the "alos" fields
From: Xiang Chen
After the controller is reset, we currently may not honour the
PHY max linkrate set via sysfs, in that after a reset we always
revert to max linkrate of 12Gbps, ignoring the value set via
sysfs.
This patch modifies to policy to set the programmed PHY linkrate,
honouring the max
From: Xiang Chen
As a unconstrained command, a command can be sent to SATA
disk even if SATA disk status is BUSY, ERR or DRQ.
If an ATA reset assert is successful but ATA reset de-assert
fails, then it will retry the reset de-assert. If reset de-
assert retry is successful, we think it is okay
On 05/01/2018 12:25 PM, Paul Moore wrote:
> On Tue, May 1, 2018 at 12:41 PM, Steve Grubb wrote:
>> On Tuesday, May 1, 2018 11:18:55 AM EDT Paul Moore wrote:
>>> On Fri, Apr 27, 2018 at 3:16 PM, Tyler Hicks wrote:
The decision to log a seccomp action will always be subject to the
value o
From: Xiang Chen
When the host is frozen in SCSI EH state, at any point after
the LLDD sets SAS_TASK_STATE_DONE for the sas_task task state,
libsas may free the task; see sas_scsi_find_task().
This puts the LLDD in a difficult position, in that once it
sets SAS_TASK_STATE_DONE for the task state
From: Xiang Chen
There are 28 bytes of protection information record of SSP for
v3 hw, 16 bytes for v2 hw, and probably 24 for v1 hw (forgotten
now).
So use a value big enough in hisi_sas_command_table_ssp.prot to
cover all cases.
Signed-off-by: Xiang Chen
Signed-off-by: John Garry
---
drive
This patchset introduces some misc changes for the
driver. These include:
- fixes for potential problems related to SCSI EH
and device removal races
- fix protection info size for all hw versions
- some SoC bug workarounds
- minor optimisations
- other more minor things
John Garry (2):
scsi: h
We should only have the timer enabled after PHY up after
controller reset, so disable prior to reset.
Signed-off-by: John Garry
Signed-off-by: Xiaofei Tan
---
drivers/scsi/hisi_sas/hisi_sas_main.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/scsi/hisi_sas/hisi_sas_main.c
b/dr
From: Xiang Chen
It is possible to dereference a NULL-pointer in hisi_sas_abort_task()
in special scenario when the device has been removed.
If an SMP task times-out, it will call hisi_sas_abort_task() to
recover. And currently there is a check in hisi_sas_abort_task() to
avoid the situation of
- On May 1, 2018, at 11:53 PM, Daniel Colascione dan...@google.com wrote:
[...]
>
> I think a small enhancement to rseq would let us build a perfect userspace
> mutex, one that spins on lock-acquire only when the lock owner is running
> and that sleeps otherwise, freeing userspace from both sp
Hi Rob
On 05/01/2018 04:56 PM, Rob Herring wrote:
On Thu, Apr 26, 2018 at 06:18:30PM +0200, Ludovic Barre wrote:
From: Ludovic Barre
Exti controller has been differently integrated on stm32mp1 SoC.
A parent irq has only one external interrupt. A hierachy domain could
be used. Handlers are ca
I went ahead and requested a patchwork instance on patchwork.kernel.org
and it's up and running https://patchwork.kernel.org/project/linux-mm/list/
Hopefully someone else will find this useful. It's a nice way to view
Acks/Tested-by for those who pay attention to such things.
Thanks,
Laura
P.S.
On Wed, May 2, 2018 at 9:03 AM Mathieu Desnoyers <
mathieu.desnoy...@efficios.com> wrote:
> - On May 1, 2018, at 11:53 PM, Daniel Colascione dan...@google.com
wrote:
> [...]
> >
> > I think a small enhancement to rseq would let us build a perfect
userspace
> > mutex, one that spins on lock-acq
startup_64() copies kernel (including .data section) to the new place.
It's required for safe in-place decompression.
This is a problem if the original place is referenced: by mistake I've
put 'top_pgtable' into .data section and the address is loaded into CR3.
If the original place gets overwritt
On Wed, May 02, 2018 at 05:42:33PM +0200, Christian Brauner wrote:
> Hey,
>
> This is the second resend of this patchset. I'm not sure whether it has
> simply been overlooked but the number of people get_maintainer.pl was
> rather small and seemed a little random so I added Linus and Christoph,
>
The kernel parameter allows to force kernel to use 4-level paging even
if hardware and kernel support 5-level paging.
The option may be useful to workaround regressions related to 5-level
paging.
Signed-off-by: Kirill A. Shutemov
---
Documentation/admin-guide/kernel-parameters.txt | 3 +++
arc
Hi Rob,
Thanks for the review.
On 27/04/18 22:00, Rob Herring wrote:
> On Tue, Apr 24, 2018 at 10:37:41AM +0200, Enric Balletbo i Serra wrote:
>> In ATF we already wait for DDR dvfs finish, so don't need to do this in
>> kernel, so remove the interrupts properties as is not longer required.
>
>
2018-05-02 20:30 GMT+09:00 Riku Voipio :
> On 23 April 2018 at 22:50, Mathieu Malaterre wrote:
>> Be nice to the user and check env vars KBUILD_BUILD_USER &
>> KBUILD_BUILD_HOST when those are set.
>
> mkdebian sets the maintainer address as "$name <$email>", but this
> patch only sets the email p
2018-04-24 20:08 GMT+09:00 Masahiro Yamada :
> From: Mauro Rossi
>
> 'quet' is replaced by 'quiet' in scripts/genksyms/Makefile
>
> Signed-off-by: Mauro Rossi
> Signed-off-by: Masahiro Yamada
> ---
Applied to linux-kbuild/fixes.
> scripts/genksyms/Makefile | 4 ++--
> 1 file changed, 2 inse
2018-04-24 20:07 GMT+09:00 Masahiro Yamada :
> Commit 73a4f6dbe70a ("kbuild: add LEX and YACC variables") missed to
> update cmd_bison_h somehow.
>
> Signed-off-by: Masahiro Yamada
> ---
Applied to linux-kbuild/fixes.
> scripts/Makefile.lib | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion
Hi Ted,
On Fri, Apr 13, 2018 at 3:30 AM, Theodore Ts'o wrote:
> The crng_init variable has three states:
>
> 0: The CRNG is not initialized at all
> 1: The CRNG has a small amount of entropy, hopefully good enough for
>early-boot, non-cryptographical use cases
> 2: The CRNG is fully initializ
Hi,
On 04/23/2018 11:48 AM, Pierre-Yves MORDRET wrote:
This patch adds STM32MP157C I2C support on STM32MP157C with configs and device
tree.
In the same way I2C4 is enabled for STM32MP157C ED1 Daughter bord.
I2C2/5 is enabled on STM32MP157C EV1 Daughter board on Evaluation board.
---
Version
On Wed, May 02, 2018 at 04:31:09PM +0200, Michel Dänzer wrote:
> > No. __GFP_NOWARN (and gfp_t flags in general) are the wrong interface
> > for dma allocations and just cause problems. I actually plan to
> > get rid of the gfp_t argument in dma_alloc_attrs sooner, and only
> > allow either GFP_K
On Tue, May 1, 2018 at 8:34 PM Linus Torvalds
wrote:
> On Tue, May 1, 2018 at 8:22 PM Dan Williams
> wrote:
> > All that to say that having a typical RAM page covering poisoned pmem
> > would complicate the 'clear badblocks' implementation.
> Ugh, ok.
> I guess the good news is that your patc
fix mistypo
cehck -> check
Signed-off-by: DongJoo Seo
---
arch/x86/mm/pageattr.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/mm/pageattr.c b/arch/x86/mm/pageattr.c
index 3bded76e..3b4cf12 100644
--- a/arch/x86/mm/pageattr.c
+++ b/arch/x86/mm/pageattr.c
@@ -1451,
On Wednesday, May 02, 2018 05:49:31 PM Daniel Lezcano wrote:
> On Wed, May 02, 2018 at 04:14:32PM +0200, Bartlomiej Zolnierkiewicz wrote:
> > Entry for Index 941 has one zero too much. Fix it.
> >
> > Signed-off-by: Bartlomiej Zolnierkiewicz
>
> Good catch :)
Thanks. :)
> I'm curious, how did
hi
On 04/24/2018 09:54 AM, yannick fertre wrote:
This patch-set adds display controller & DSI controller support to
stm32mp157c SOC.
Version 1:
- Initial commit
yannick fertre (2):
ARM: dts: stm32: add ltdc support on stm32mp157c
ARM: dts: stm32: add dsi support on stm32mp157c
arch/ar
On Wed, May 02, 2018 at 07:09:11AM -0500, Justin Forbes wrote:
> Yes, Fedora libgcrypt is carrying a patch which makes it particularly
> painful for us, we have reached out to the libgcrypt maintainer to
> follow up on that end. But as I said before, even without that code
> path (no dracut-fips) w
Quoting Doug Anderson (2018-04-23 22:26:29)
>
> > static const struct of_device_id pmic_spmi_id_table[] = {
> > { .compatible = "qcom,spmi-pmic", .data = (void *)COMMON_SUBTYPE },
> > @@ -54,7 +57,10 @@ static const struct of_device_id pmic_spmi_id_table[] = {
> > { .compatible =
Add the compatibles and PMIC ids for the pm8005, pm8998, and pmi8998
PMICS found on MSM8998 and SDM845 based platforms.
Cc:
Reviewed-by: Rob Herring
Reviewed-by: Doug Anderson
Signed-off-by: Stephen Boyd
---
Changes from v1:
* Picked up review tags
* Reordered lists to be based on id numbe
Hi,
On Fri, Apr 13, 2018 at 7:50 PM, David Collins wrote:
> +- vdd_l26-supply
> +- vdd_lvs1_lvs2-supply
> +- vdd_lvs1_lvs2-supply
> + Usage: optional (PM8998 only)
> + Value type:
> + Definition: phandle of the parent supply regulator of one or more of
> the
> +
Hi,
It looks like perf_event__synthesize_id_index() is dead code in the current
tip
tree. I don't see any invocation of the function anywhere in perf.I
understand why
you'd want to keep the rest of the code related to PERF_RECORD_ID_INDEX
because some perf.data file may have this user-level recor
I'm announcing the release of the 4.14.39 kernel.
All users of the 4.14 kernel series must upgrade.
The updated 4.14.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.14.y
and can be browsed at the normal kernel.org git web browser:
diff --git a/Documentation/virtual/kvm/api.txt
b/Documentation/virtual/kvm/api.txt
index 0f9089416b4c..88ad78c6f605 100644
--- a/Documentation/virtual/kvm/api.txt
+++ b/Documentation/virtual/kvm/api.txt
@@ -1940,6 +1940,9 @@ ARM 32-bit VFP control registers have the following id
bit patterns:
AR
I'm announcing the release of the 4.9.98 kernel.
All users of the 4.9 kernel series must upgrade.
The updated 4.9.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.9.y
and can be browsed at the normal kernel.org git web browser:
diff --git a/Makefile b/Makefile
index ee3e943c3bd9..96d770488ae6 100644
--- a/Makefile
+++ b/Makefile
@@ -1,6 +1,6 @@
VERSION = 4
PATCHLEVEL = 9
-SUBLEVEL = 97
+SUBLEVEL = 98
EXTRAVERSION =
NAME = Roaring Lionus
diff --git a/arch/powerpc/kernel/eeh_driver.c b/arch/powerpc/kernel/eeh_driver.c
diff --git a/Makefile b/Makefile
index bc07a9ec9682..a562ebf4d500 100644
--- a/Makefile
+++ b/Makefile
@@ -1,6 +1,6 @@
VERSION = 3
PATCHLEVEL = 18
-SUBLEVEL = 107
+SUBLEVEL = 108
EXTRAVERSION =
NAME = Diseased Newt
diff --git a/drivers/char/virtio_console.c b/drivers/char/virtio_console.c
ind
I'm announcing the release of the 3.18.108 kernel.
All users of the 3.18 kernel series must upgrade.
The updated 3.18.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-3.18.y
and can be browsed at the normal kernel.org git web browser
diff --git a/Makefile b/Makefile
index 151477d4d5e5..6ec65396a56d 100644
--- a/Makefile
+++ b/Makefile
@@ -1,6 +1,6 @@
VERSION = 4
PATCHLEVEL = 4
-SUBLEVEL = 130
+SUBLEVEL = 131
EXTRAVERSION =
NAME = Blurry Fish Butt
diff --git a/arch/x86/include/uapi/asm/msgbuf.h
b/arch/x86/include/uapi/asm
I'm announcing the release of the 4.4.131 kernel.
All users of the 4.4 kernel series must upgrade.
The updated 4.4.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.4.y
and can be browsed at the normal kernel.org git web browser:
Hi Maxime,
You don't have to handcode the fragments anymore with the new syntax,
and U-Boot makes it really trivial to use if you use the FIT image
format to have multiple overlays bundled in the same image. You can
choose to apply them dynamically, for example based on an EEPROM or
some other m
On Wed, 02 May 2018 16:07:48 +
Daniel Colascione wrote:
> Why couldn't we take a page fault just before schedule? The reason we can't
> take a page fault in atomic context is that doing so might call schedule.
> Here, we're about to call schedule _anyway_, so what harm does it do to
> call so
On 04/28/2018 11:09 AM, Arnd Bergmann wrote:
> On Sat, Apr 28, 2018 at 12:21 AM, Joao Martins
> wrote:
>> On 04/27/2018 09:13 PM, Arnd Bergmann wrote:
>>> diff --git a/arch/x86/kernel/pvclock.c b/arch/x86/kernel/pvclock.c
>>> index 761f6af6efa5..637982efecd8 100644
>>> --- a/arch/x86/kernel/pvcloc
On Wed, May 02, 2018 at 11:39:00AM +0100, Gustavo Pimentel wrote:
> Hi Lorenzo,
>
> On 01/05/2018 15:26, Lorenzo Pieralisi wrote:
> > On Tue, May 01, 2018 at 05:53:59PM +0530, Kishon Vijay Abraham I wrote:
> >> Hi Lorenzo,
> >>
> >> On Tuesday 01 May 2018 05:24 PM, Lorenzo Pieralisi wrote:
> >>> O
On Tue, May 1, 2018 at 3:46 PM, Dmitry Torokhov
wrote:
> "atmel,atmel_mxt_tp" and "atmel,atmel_mxt_ts" are ChromeOS inventions,
> let's replace them with canonical compatible string "atmel,maxtouch".
>
> Signed-off-by: Dmitry Torokhov
I guess the other IDs are in the driver just for non-DT usage
On 05/02/2018 01:12 AM, Jani Nikula wrote:
On Mon, 30 Apr 2018, Larry Finger wrote:
With kernel 4.17.0-rc3, I noted the following warning from driver i915.
kernel: [ cut here ]
kernel: Could not determine valid watermarks for inherited state
kernel: WARNING: CPU: 3 PID:
501 - 600 of 1007 matches
Mail list logo
