Pavel Tatashin writes:
>> About PPC64, your patchset fixes the issue as the population gets followed
>> by a
>> sparse_init_one_section().
>>
>> It can be seen here:
>>
>> Before:
>>
>> kernel: vmemmap_populate f000..f0004000, node 0
>> kernel: * f000..f
Export sdhci tuning function symbols which are used by other SD Host
controller driver modules.
Signed-off-by: ernest.zhang
---
Changes in V7:
Export sdhci tuning function symbols
Changes in V1~V6
N/A
---
drivers/mmc/host/sdhci.c | 12
drivers/mmc/host/sdhci.h | 5
Add MSI interrupt support if the SD host device can support MSI interrupt.
Signed-off-by: ernest.zhang
---
Changes in V7:
N/A
Changes in V6:
1. Move change log to correct place.
2. Reduce unneeded pr_info prints.
3. In function sdhci_pci_o2_probe_slot, remove usin
O2 SD Host HS200 mode clock frequency current is 208MHz, should be changed
to 200MHz to meet specification.
Signed-off-by: ernest.zhang
---
Change in V7:
Change HS200 mode clock frequency from 208MHz to 200MHz to meet
Specification.
Change in V1~V6:
N/A
---
drivers/mmc/h
Add hardware tuning function instead of software tuning because O2/Bayhub
SD host controller support hardware tuning.
Signed-off-by: ernest.zhang
---
Changes in V7:
Move V6 change item 1 to a seperate patch.
Changes in V6:
1. From module 'sdhci' export the symbols 'sdhci_start_tu
When use eMMC as boot device, the eMMC signaling voltage is tied to 1.8v
fixed output voltage, bios can set o2 sd host controller PCI configuration
register 0x308 bit4 to 1 to let driver skip 3.3v signaling voltage and
direct use 1.8v singling voltage in eMMC initialize process.
Signed-off-by: ern
From: Yi Wang
There are two tab at the end of function trigger_dyntick_cpu(),
so remove one and correct indentation.
Signed-off-by: Yi Wang
Reviewed-by: Jiang Biao
---
kernel/time/timer.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/time/timer.c b/kernel/time/tim
Users of SPI device drivers may rely on 'actual_length', so it is
important that information is correctly reported. One example would be
spi_mem_exec_op() which will fail if 'actual_length' doesn't match
requested transfer length. To fix the problem, add necessary code to
populate 'actual_length'.
Olof Johansson writes:
> It's a known issue due to dependencies with a driver tree. :(
>
> Robert, this is unfortunate. What's the dependent patches? We can pick
> them up in our tree as duplicates if needed.
I'd rather postpone one of the patches, as I explained in the pull request.
As Stephen n
Hi, Fabio
Anson Huang
Best Regards!
> -Original Message-
> From: Fabio Estevam [mailto:feste...@gmail.com]
> Sent: Sunday, July 15, 2018 12:13 AM
> To: Anson Huang
> Cc: Linus Walleij ; open list:GPIO SUBSYSTEM
> ; linux-kernel ;
> dl-linux-imx
> Subject: Re: [PATCH] gpio: mxc: add pow
On Sat 14-07-18 06:18:58, Tetsuo Handa wrote:
> On 2018/07/13 23:26, Michal Hocko wrote:
> > On Thu 12-07-18 14:34:00, David Rientjes wrote:
> > [...]
> >> diff --git a/mm/oom_kill.c b/mm/oom_kill.c
> >> index 0fe4087d5151..e6328cef090f 100644
> >> --- a/mm/oom_kill.c
> >> +++ b/mm/oom_kill.c
> >>
GPIO registers could lose context on i.MX7D,
when enter LPSR mode, the whole SoC will be
powered off except LPSR domain, GPIO banks
will lose context in this case, need to restore
the context after resume from LPSR mode.
This patch adds GPIO save/restore for those necessary
registers, and put the
From: Mahesh Salgaonkar
One of the primary issues with Firmware Assisted Dump (fadump) on Power
is that it needs a large amount of memory to be reserved. On large
systems with TeraBytes of memory, this reservation can be quite
significant.
In some cases, fadump fails if the memory reserved is in
From: Mahesh Salgaonkar
For fadump to work successfully there should not be any holes in reserved
memory ranges where kernel has asked firmware to move the content of old
kernel memory in event of crash. Now that fadump reserved memory is marked
as movable zone, this memory area is now not protec
From: Mahesh Salgaonkar
fadump fails to register when there are holes in reserved memory area.
This can happen if user has hot-removed a memory that falls in the fadump
reserved memory area. Throw a meaningful error message to the user in
such case.
Signed-off-by: Mahesh Salgaonkar
---
arch/po
From: Mahesh Salgaonkar
Add an interface to allow a custom reserved memory to be marked as
ZONE_MOVABLE. This will help some subsystem's to convert their reserved
memory region into ZONE_MOVABLE so that the memory can still be available
to user applications.
The approach is based on Joonsoo Kim'
One of the primary issues with Firmware Assisted Dump (fadump) on Power
is that it needs a large amount of memory to be reserved. This reserved
memory is used for saving the contents of old crashed kernel's memory before
fadump capture kernel uses old kernel's memory area to boot. However, This
res
Hi Jerome
On 2018/7/11 21:45, Jerome Brunet wrote:
On Wed, 2018-07-11 at 21:41 +0800, Jian Hu wrote:
+static struct clk_regmap g12a_mpll0 = {
+ .data = &(struct clk_regmap_gate_data){
+ .offset = HHI_MPLL_CNTL1,
+ .bit_idx = 31,
+ },
+ .hw.init = &(
Hello Stephen,
On 7/13/2018 1:55 PM, spa...@codeaurora.org wrote:
On 2018-07-13 01:11, Stephen Boyd wrote:
Quoting Taniya Das (2018-07-12 10:21:33)
++ Display driver team,
On 7/9/2018 8:36 PM, Stephen Boyd wrote:
> Quoting Taniya Das (2018-07-09 02:34:07)
>>
>>
>> On 7/9/2018 1:07 PM, Stephen
SPDX headers updated for common/branch/pll/regmap files.
Signed-off-by: Taniya Das
---
drivers/clk/qcom/clk-alpha-pll.c | 10 +-
drivers/clk/qcom/clk-alpha-pll.h | 14 ++
drivers/clk/qcom/clk-branch.c| 10 +-
drivers/clk/qcom/clk-branch.h| 14 ++
d
Hi Ted,
After merging the random tree, today's linux-next build (arm
multi_v7_defconfig) produced this warning:
drivers/char/random.c: In function 'write_pool.constprop':
drivers/char/random.c:1912:11: warning: 't' may be used uninitialized in this
function [-Wmaybe-uninitialized]
buf[i] ^=
Fix the spelling of 'varibles' -> 'variables' in
shadows->vars.txt file.
Signed-off-by: Kamalesh Babulal
---
Documentation/livepatch/shadow-vars.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/livepatch/shadow-vars.txt
b/Documentation/livepatch/shadow-vars.
Hi Paul,
> > --- linux-jhogan-test.orig/fs/binfmt_elf.c 2018-03-21 17:14:55.0
> > +
> > +++ linux-jhogan-test/fs/binfmt_elf.c 2018-05-09 23:25:50.742255000
> > +0100
> > @@ -1739,7 +1739,7 @@ static int fill_thread_core_info(struct
> > const struct user_regset *re
QUPv3 clocks support DFS and thus register the RCGs which require support
for the same.
Signed-off-by: Taniya Das
---
drivers/clk/qcom/gcc-sdm845.c | 25 +
1 file changed, 25 insertions(+)
diff --git a/drivers/clk/qcom/gcc-sdm845.c b/drivers/clk/qcom/gcc-sdm845.c
index 0
Dynamic Frequency switch is a feature of clock controller by which request
from peripherals allows automatic switching frequency of input clock
without SW intervention. There are various performance levels associated
with a root clock. When the input performance state changes, the source
clocks and
[v3]
* Rename clk_rcg2_calculate_m_and_n with clk_rcg2_calculate_freq, as this
function would now calculate the frequency.
* Rename dfs_freq_tbl to freq_tbl.
* Remove the logic to remove duplicate frequencies.
* Remove recalc_rate & set_rate clock ops.
* clk_rcg2_dfs_ops clock ops is
Hello Stephen,
Thanks for your review comments.
On 7/9/2018 12:34 PM, Stephen Boyd wrote:
Quoting Taniya Das (2018-06-28 04:47:30)
Dynamic Frequency switch is a feature of clock controller by which request
from peripherals allows automatic switching frequency of input clock.
There are various
On 12-07-18, 23:35, Taniya Das wrote:
> +static int qcom_cpu_resources_init(struct platform_device *pdev,
> +struct device_node *np, unsigned int cpu)
> +{
> + struct cpufreq_qcom *c;
> + struct resource res;
> + struct device *dev = &pdev->dev;
> + u
On 12-07-18, 23:35, Taniya Das wrote:
> The CPUfreq HW present in some QCOM chipsets offloads the steps necessary
> for changing the frequency of CPUs. The driver implements the cpufreq
> driver interface for this hardware engine.
>
> Signed-off-by: Saravana Kannan
> Signed-off-by: Taniya Das
>
GPC registers are NOT continuous, some registers are
reserved and accessing them from userspace will trigger
external abort, add regmap register access table to
avoid below abort:
root@imx6slevk:~# cat /sys/kernel/debug/regmap/20dc000.gpc/registers
[ 108.480477] Unhandled fault: imprecise externa
On Sat, Jul 7, 2018 at 4:00 PM, Souptick Joarder wrote:
> Use new return type vm_fault_t for fault handler
> ext4_filemap_fault.
>
> Signed-off-by: Souptick Joarder
Any comment on this patch ?
> ---
> fs/ext4/ext4.h | 2 +-
> fs/ext4/inode.c | 8
> 2 files changed, 5 insertions(+), 5
On 05-07-18, 10:39, Viresh Kumar wrote:
> Allow cooling devices sharing same trip point with same contribution
> value to share the cooling map as well. Otherwise the same information
> will be duplicated for each device sharing the trip point.
>
> Signed-off-by: Viresh Kumar
> ---
> Documentati
On 29-06-18, 11:49, Viresh Kumar wrote:
> Hi,
>
> This series improves the OPP core (and a bit of genpd core as well) to
> support multiple phandles in the "required-opps" property, which are
> only used for multiple power-domains per device for now.
>
> We still don't propagate the changes to ma
On 13-07-18, 16:36, Srinivas Kandagatla wrote:
> During discussion regarding card re-binding when components unregister
> and register back at https://lkml.org/lkml/2018/7/9/785 it was suggested
> that component framework can be added into core to provide this feature.
>
> With this new changes th
When using unknown pti boot options other than on/off/auto, we
select auto silently, which is sometimes confusing. Add warning for
unknown pti boot options like we do in
spectre_v2_select_mitigation().
Signed-off-by: Jiang Biao
---
arch/x86/mm/pti.c | 10 +-
1 file changed, 5 insertions(
pti_user_pagetable_walk_p4d() may return NULL, we should check the
return value to avoid NULL pointer dereference.
Signed-off-by: Jiang Biao
---
arch/x86/mm/pti.c | 7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/arch/x86/mm/pti.c b/arch/x86/mm/pti.c
index 4d418e7..be9e5b
pti_set_kernel_image_nonglobal() is only used in pti.c, make it
static.
Signed-off-by: Jiang Biao
---
arch/x86/mm/pti.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/mm/pti.c b/arch/x86/mm/pti.c
index bb6f608..a76b2cc 100644
--- a/arch/x86/mm/pti.c
+++ b/arch/x86/m
Addresses passed in pti_user_pagetable_walk_*() are not supposed to
change at runtime, make them const to aviod future slipups.
Signed-off-by: Jiang Biao
---
arch/x86/mm/pti.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/arch/x86/mm/pti.c b/arch/x86/mm/pti.c
index a3
pti_user_pagetable_walk_pmd() may return NULL, we should check the
return value in pti_user_pagetable_walk_pte() to avoid NULL pointer
dereference like it is checked in pti_clone_pmds().
Signed-off-by: Jiang Biao
---
arch/x86/mm/pti.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
dif
This is a short series of fixes and cleanups found when reading the
code, no functional changes.
Jiang Biao (5):
x86/pti: check the return value of pti_user_pagetable_walk_p4d
x86/pti: check the return value of pti_user_pagetable_walk_pmd
x86/pti: make pti_set_kernel_image_nonglobal static
On 10-07-18, 15:59, Greg KH wrote:
> On Mon, Jul 02, 2018 at 02:19:47PM +0530, Viresh Kumar wrote:
> > From: Waldemar Rymarkiewicz
> >
> > Original commit c5c2a97b3ac7 ("PM / OPP: Update voltage in case freq ==
> > old_freq").
Looking for this ^^ information ?
> Always give me a hint as to wha
> now need to dive in deep into the actual implementation. Simple question: is
> this a bug?
These are derived events from MEM_TRANS_RETIRED.LOAD_LATENCY, which is in
the SDM. It's not a bug. In general the event lists used by perf are
newer versions than what is in the SDM.
-Andi
In preparing to remove all stack VLA usage from the kernel[1], this
removes the discouraged use of AHASH_REQUEST_ON_STACK in favor of
the smaller SHASH_DESC_ON_STACK by converting from ahash-wrapped-shash
to direct shash. The stack allocation will be made a fixed size in a
later patch to the crypto
In the quest to remove all stack VLA usage from the kernel[1], this
removes the discouraged use of AHASH_REQUEST_ON_STACK by switching to
shash directly and allocating the descriptor in heap memory (which should
be fine: the tfm has already been allocated there too).
[1]
https://lkml.kernel.org/r
On Mon, Jul 16, 2018 at 11:09 AM, Shakeel Butt wrote:
> On Sun, Jul 15, 2018 at 6:50 PM Yafang Shao wrote:
>>
>> On Sun, Jul 15, 2018 at 11:04 PM, Shakeel Butt wrote:
>> > On Sun, Jul 15, 2018 at 1:02 AM Yafang Shao wrote:
>> >>
>> >> On Sun, Jul 15, 2018 at 2:34 PM, Shakeel Butt wrote:
>> >>
Hi Jae,
In originally, we reserved these register bits for debug purpose. But for some
error handling case, we found it is also useful to help to clarify some error
conditions. So driver also can use these fields information to check something.
As for how driver use these information in their co
Hi, Bjorn, Lorenzo,
could you kindly take a look at this serial?
thanks.
On Mon, 2018-07-02 at 15:57 +0800, honghui.zh...@mediatek.com wrote:
> From: Honghui Zhang
>
> This patchset includes misc patchs:
>
> The first patch fixup the mtk_pcie_find_port logical which will cause system
> could
Hello,
syzbot found the following crash on:
HEAD commit:483d835c8189 Add linux-next specific files for 20180713
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=13689bb240
kernel config: https://syzkaller.appspot.com/x/.config?x=60e5ac2478928314
dashb
On Sun, Jul 15, 2018 at 6:50 PM Yafang Shao wrote:
>
> On Sun, Jul 15, 2018 at 11:04 PM, Shakeel Butt wrote:
> > On Sun, Jul 15, 2018 at 1:02 AM Yafang Shao wrote:
> >>
> >> On Sun, Jul 15, 2018 at 2:34 PM, Shakeel Butt wrote:
> >> > On Sat, Jul 14, 2018 at 10:26 PM Yafang Shao
> >> > wrote:
On Thu, 12 Jul 2018, at 05:51, Rob Herring wrote:
> On Wed, Jul 04, 2018 at 12:14:26PM +0300, Tomer Maimon wrote:
> > Added device tree binding documentation for Nuvoton BMC
> > NPCM7xx BIOS Post Code (BPC).
> > The NPCM7xx BPC monitoring two configurable I/O addresses
> > written by the host on Lo
On Fri, Jul 13, 2018 at 07:58:25PM -0700, Linus Torvalds wrote:
> On Fri, Jul 13, 2018 at 6:51 PM Alan Stern wrote:
> >
> > The point being that the scenarios under discussion in this thread all
> > fall most definitely into the "Non-standard usage; you'd better know
> > exactly what you're doing"
FYI, we noticed the following commit (built with gcc-4.9):
commit: 3f96d20fafb19e6dd869362ace53662b06e6f6c1 ("[PATCH] debugobjects:
Disable lockdep tracking of debugobjects internal locks")
url:
https://github.com/0day-ci/linux/commits/Waiman-Long/debugobjects-Disable-lockdep-tracking-of-debugo
On Mon, Jul 16, 2018 at 12:03:39AM +0200, Ingo Molnar wrote:
>
> * Jann Horn wrote:
>
> > - A malicious user can pass an arbitrary file to a setuid binary as
> > stdin/stdout/stderr. When the setuid binary (expecting stdin/stdout to
> > be something normal, like a proper file or a pipe) then ca
On Mon, Jul 16, 2018 at 11:23:43AM +1000, NeilBrown wrote:
>
> kmem_cache_free() directly. For this, I need rhashtable to be safe if
> an object is deleted and immediately re-inserted into the same hash
> chain.
This means that
rcu_read_lock();
A = rhashtable_lookup();
us
On 14 July 2018 at 14:29, Pavel Machek wrote:
>
>> @@ -446,4 +455,14 @@ static inline void
>> led_classdev_notify_brightness_hw_changed(
>> struct led_classdev *led_cdev, enum led_brightness brightness) { }
>> #endif
>>
>> +/**
>> + * struct led_pattern - brigheness value in a pattern
>
>
On 2018/7/13 4:34, Hamish Martin wrote:
Hi Xiubo,
Tested-by: Hamish Martin
I see these were already merged into Linus' tree but I wanted to let you
know that I tested v4.18-rc4 (which contains these three patches) and
the issue which led to my original series is still fixed and this patch
seri
On 2018/7/14 20:47, Dominique Martinet wrote:
> jiangyiwen wrote on Sat, Jul 14, 2018:
>> On 2018/7/14 17:05, Dominique Martinet wrote:
>>> jiangyiwen wrote on Sat, Jul 14, 2018:
When client has multiple threads that issue io requests all the
time, and the server has a very good performan
On Sun, Jul 15, 2018 at 11:04 PM, Shakeel Butt wrote:
> On Sun, Jul 15, 2018 at 1:02 AM Yafang Shao wrote:
>>
>> On Sun, Jul 15, 2018 at 2:34 PM, Shakeel Butt wrote:
>> > On Sat, Jul 14, 2018 at 10:26 PM Yafang Shao wrote:
>> >>
>> >> On Sun, Jul 15, 2018 at 12:25 PM, Shakeel Butt
>> >> wrote
On Sun, Jul 15, 2018 at 6:33 PM Jann Horn wrote:
>
> +Linus, Andy, Al from the other thread
>
> On Mon, Jul 16, 2018 at 12:03 AM Ingo Molnar wrote:
> >
> > BTW., a naive question: would it make sense to simply disallow 'special'
> > fds to be passed to setuid binaries, and fix any user-space that
+Linus, Andy, Al from the other thread
On Mon, Jul 16, 2018 at 12:03 AM Ingo Molnar wrote:
> * Jann Horn wrote:
>
> > - A malicious user can pass an arbitrary file to a setuid binary as
> > stdin/stdout/stderr. When the setuid binary (expecting stdin/stdout to
> > be something normal, like a pr
Hi Dominique,
On 2018/7/12 15:01, Dominique Martinet wrote:
> piaojun wrote on Thu, Jul 12, 2018:
>> In p9_read_work(), we use spin_lock for client->lock, but misuse
>> spin_lock_irqsave for it in p9_fid_create(). As p9_client lock won't be
>> locked in irq context, so spin_lock is enough. And tha
On Mon, Jul 16 2018, Herbert Xu wrote:
> On Mon, Jul 16, 2018 at 09:57:11AM +1000, NeilBrown wrote:
>>
>> Some users of rhashtable might need to change the key
>> of an object and move it to a different location in the table.
>> Other users might want to allocate objects using
>> SLAB_TYPESAFE_BY
* Rik van Riel wrote:
> On Mon, 2018-07-16 at 00:59 +0200, Ingo Molnar wrote:
> > * Rik van Riel wrote:
> >
> > > The mm_struct always contains a cpumask bitmap, regardless of
> > > CONFIG_CPUMASK_OFFSTACK. That means the first step can be to
> > > simplify things, and simply have one bitmask
* Rik van Riel wrote:
> On Mon, 2018-07-16 at 01:04 +0200, Ingo Molnar wrote:
> > * Rik van Riel wrote:
> >
> > > + /*
> > > + * Stop remote flushes for the previous mm.
> > > + * Skip the idle task; we never send init_mm TLB
> > > flushing IPIs,
> > > + * b
* Prakhya, Sai Praneeth wrote:
> > > diff --git a/arch/x86/platform/efi/quirks.c
> > > b/arch/x86/platform/efi/quirks.c index 36c1f8b9f7e0..6af39dc40325
> > > 100644
> > > --- a/arch/x86/platform/efi/quirks.c
> > > +++ b/arch/x86/platform/efi/quirks.c
> > > @@ -105,12 +105,11 @@ early_param("ef
On 07/15/2018 07:22 AM, Jacek Anaszewski wrote:
On 07/15/2018 12:39 AM, Pavel Machek wrote:
On Sun 2018-07-15 00:29:25, Pavel Machek wrote:
On Sun 2018-07-15 00:02:57, Jacek Anaszewski wrote:
Hi Pavel,
On 07/14/2018 11:20 PM, Pavel Machek wrote:
Hi!
It also drew my attention to the issue o
Hi Alexander,
I've rearranged your reply slightly :)
On Sat, 14 Jul 2018, at 00:44, Alexander Amelkin wrote:
>
> So I'm writing this to support your position in this discussion and to
> let Rob and other reviewers know that this feature is actually needed.
Thanks.
So to summarise some other r
On Mon, Jul 16, 2018 at 09:57:11AM +1000, NeilBrown wrote:
>
> Some users of rhashtable might need to change the key
> of an object and move it to a different location in the table.
> Other users might want to allocate objects using
> SLAB_TYPESAFE_BY_RCU which can result in the same memory alloca
On 14/07/2018 05:09, Wolfram Sang wrote:
I2C is open drain, so set up the GPIO accordingly.
Signed-off-by: Wolfram Sang
---
drivers/i2c/busses/i2c-designware-master.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/i2c/busses/i2c-designware-master.c
b/drivers/i2c
The cephfs part (patch 2~5) looks good for me.
Regards
Yan, Zheng
On Sat, Jul 14, 2018 at 4:21 AM Arnd Bergmann wrote:
>
> ceph_mdsc_create_request() is one of the last callers of the
> deprecated current_kernel_time() as well as timespec_trunc().
>
> This changes it to use the timespec64 based
Hi Linus,
Not actually back online fully, but I've managed to find a few minutes
to pull in all the fixes that were meant for rc5 but have leaked over.
There are two AGP fixes in here, as well as a bunch of mostly amdgpu
fixes, along with a sun4i build fix, two armada fixes and some tegra
fixes,
On Sun, Jul 15, 2018 at 4:50 PM, Olof Johansson wrote:
> On Sun, Jul 15, 2018 at 4:13 PM, Stephen Rothwell
> wrote:
>> Hi all,
>>
>> After merging the arm-soc tree, today's linux-next build (x86_64
>> allmodconfig) failed like this:
>>
>> sound/arm/pxa2xx-pcm-lib.c: In function '__pxa2xx_pcm_ope
Hello,
syzbot found the following crash on:
HEAD commit:37b5dca2898d Merge tag 'rtc-4.18-2' of git://git.kernel.or..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=12204d6240
kernel config: https://syzkaller.appspot.com/x/.config?x=25856fac4e580aa7
da
Hello,
syzbot found the following crash on:
HEAD commit:37b5dca2898d Merge tag 'rtc-4.18-2' of git://git.kernel.or..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=12aaf3b240
kernel config: https://syzkaller.appspot.com/x/.config?x=25856fac4e580aa7
da
On Sat, Jul 14, 2018 at 07:59:09PM -0700, Kees Cook wrote:
> On Sat, Jul 14, 2018 at 7:44 PM, Herbert Xu
> wrote:
> > On Fri, Jul 13, 2018 at 08:07:10PM -0700, Kees Cook wrote:
> >>
> >> On a plane today I started converting all these to shash. IIUC, it
> >> just looks like this (apologies for wh
On Fri, Jul 13, 2018 at 11:25:16PM -0700, Davidlohr Bueso wrote:
> rhashtable_init() currently does not take into account the user-passed
> min_size parameter unless param->nelem_hint is set as well. As such,
> the default size (number of buckets) will always be HASH_DEFAULT_SIZE
> even if the smal
On Tue, Jul 10 2018, David Miller wrote:
> From: NeilBrown
> Date: Fri, 06 Jul 2018 17:11:32 +1000
>
>> rhashtable_walk_last_seen() returns the object returned by
>> the previous rhashtable_walk_next(), providing it is still in the
>> table (or was during this grace period).
>> This works even if
Some users of rhashtable might need to change the key
of an object and move it to a different location in the table.
Other users might want to allocate objects using
SLAB_TYPESAFE_BY_RCU which can result in the same memory allocation
being used for a different (type-compatible) purpose and similar
On Wed, Jul 11 2018, David Miller wrote:
> From: David Miller
> Date: Wed, 11 Jul 2018 22:46:58 -0700 (PDT)
>
>> From: NeilBrown
>> Date: Fri, 06 Jul 2018 17:08:35 +1000
>>
>>>
>>> Some users of rhashtable might need to change the key
>>> of an object and move it to a different location in the
On Sun, Jul 15, 2018 at 4:13 PM, Stephen Rothwell wrote:
> Hi all,
>
> After merging the arm-soc tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> sound/arm/pxa2xx-pcm-lib.c: In function '__pxa2xx_pcm_open':
> sound/arm/pxa2xx-pcm-lib.c:129:6: error: 'pxad_filter_fn' und
On Mon, 2018-07-16 at 00:59 +0200, Ingo Molnar wrote:
> * Rik van Riel wrote:
>
> > The mm_struct always contains a cpumask bitmap, regardless of
> > CONFIG_CPUMASK_OFFSTACK. That means the first step can be to
> > simplify things, and simply have one bitmask at the end of the
> > mm_struct for t
> > diff --git a/arch/x86/platform/efi/quirks.c
> > b/arch/x86/platform/efi/quirks.c index 36c1f8b9f7e0..6af39dc40325
> > 100644
> > --- a/arch/x86/platform/efi/quirks.c
> > +++ b/arch/x86/platform/efi/quirks.c
> > @@ -105,12 +105,11 @@ early_param("efi_no_storage_paranoia",
> > setup_storage_paran
On Mon, 2018-07-16 at 01:04 +0200, Ingo Molnar wrote:
> * Rik van Riel wrote:
>
> > + /*
> > +* Stop remote flushes for the previous mm.
> > +* Skip the idle task; we never send init_mm TLB
> > flushing IPIs,
> > +* but the bitmap manipulation can cau
Commit-ID: 38ac0287b7f4f3922e25fd8f81db67f2c13d16bb
Gitweb: https://git.kernel.org/tip/38ac0287b7f4f3922e25fd8f81db67f2c13d16bb
Author: Ard Biesheuvel
AuthorDate: Wed, 11 Jul 2018 11:40:40 +0200
Committer: Ingo Molnar
CommitDate: Mon, 16 Jul 2018 00:43:12 +0200
fbdev/efifb: Honour UEFI
Commit-ID: 7e1550b8f2081cccdfa9f1cf1e54cbc4d720af7f
Gitweb: https://git.kernel.org/tip/7e1550b8f2081cccdfa9f1cf1e54cbc4d720af7f
Author: Ard Biesheuvel
AuthorDate: Wed, 11 Jul 2018 11:40:39 +0200
Committer: Ingo Molnar
CommitDate: Mon, 16 Jul 2018 00:43:12 +0200
efi: Drop type and attri
Commit-ID: 3d7ee348aa4127a7893c11261da9b76371a970e6
Gitweb: https://git.kernel.org/tip/3d7ee348aa4127a7893c11261da9b76371a970e6
Author: Ard Biesheuvel
AuthorDate: Wed, 11 Jul 2018 11:40:38 +0200
Committer: Ingo Molnar
CommitDate: Mon, 16 Jul 2018 00:43:12 +0200
efi/libstub/arm: Add opt
Commit-ID: f5dcc214aae29a68b37b2b4183f7171724e7b02d
Gitweb: https://git.kernel.org/tip/f5dcc214aae29a68b37b2b4183f7171724e7b02d
Author: Sai Praneeth
AuthorDate: Wed, 11 Jul 2018 11:40:37 +0200
Committer: Ingo Molnar
CommitDate: Mon, 16 Jul 2018 00:43:12 +0200
efi: Remove the declaratio
Commit-ID: 7bb497092a34a2bbb16bad5385a0487dee18a769
Gitweb: https://git.kernel.org/tip/7bb497092a34a2bbb16bad5385a0487dee18a769
Author: Arnd Bergmann
AuthorDate: Wed, 11 Jul 2018 11:40:36 +0200
Committer: Ingo Molnar
CommitDate: Mon, 16 Jul 2018 00:43:12 +0200
efi/cper: Avoid using get
Commit-ID: 3eb420e70d879ce0e6bf752accf5cdedb0a59de8
Gitweb: https://git.kernel.org/tip/3eb420e70d879ce0e6bf752accf5cdedb0a59de8
Author: Sai Praneeth
AuthorDate: Wed, 11 Jul 2018 11:40:35 +0200
Committer: Ingo Molnar
CommitDate: Mon, 16 Jul 2018 00:43:12 +0200
efi: Use a work queue to i
Commit-ID: 90a2186b7df183c2fd35f724d0d16a0c10fac9b2
Gitweb: https://git.kernel.org/tip/90a2186b7df183c2fd35f724d0d16a0c10fac9b2
Author: Ingo Molnar
AuthorDate: Wed, 11 Jul 2018 11:40:33 +0200
Committer: Ingo Molnar
CommitDate: Mon, 16 Jul 2018 00:43:05 +0200
efi/x86: Clean up the eboot
Commit-ID: 5a58bc1b1edc18a9edff606ec99e6f6b723975f4
Gitweb: https://git.kernel.org/tip/5a58bc1b1edc18a9edff606ec99e6f6b723975f4
Author: Sai Praneeth
AuthorDate: Wed, 11 Jul 2018 11:40:34 +0200
Committer: Ingo Molnar
CommitDate: Mon, 16 Jul 2018 00:43:12 +0200
efi/x86: Use non-blocking
Commit-ID: 8d4c00dc38a8aa30dae8402955e55e7b34e74bc8
Gitweb: https://git.kernel.org/tip/8d4c00dc38a8aa30dae8402955e55e7b34e74bc8
Author: Xunlei Pang
AuthorDate: Mon, 9 Jul 2018 22:58:43 +0800
Committer: Ingo Molnar
CommitDate: Mon, 16 Jul 2018 00:28:31 +0200
sched/cputime: Ensure accura
Commit-ID: bdc9c3e5ed953441a46ef3acd81c783d591c9a96
Gitweb: https://git.kernel.org/tip/bdc9c3e5ed953441a46ef3acd81c783d591c9a96
Author: Masahiro Yamada
AuthorDate: Mon, 9 Jul 2018 21:07:21 +0900
Committer: Ingo Molnar
CommitDate: Mon, 16 Jul 2018 00:25:10 +0200
x86/build: Remove old -f
Commit-ID: 788faab70d5a882693286b8d5022779559c79904
Gitweb: https://git.kernel.org/tip/788faab70d5a882693286b8d5022779559c79904
Author: Tobias Tefke
AuthorDate: Mon, 9 Jul 2018 12:57:15 +0200
Committer: Ingo Molnar
CommitDate: Mon, 16 Jul 2018 00:21:03 +0200
perf, tools: Use correct ar
Commit-ID: 45f5519ec55e75af3565dd737586d3b041834f71
Gitweb: https://git.kernel.org/tip/45f5519ec55e75af3565dd737586d3b041834f71
Author: Peter Zijlstra
AuthorDate: Thu, 5 Jul 2018 14:36:17 +0200
Committer: Ingo Molnar
CommitDate: Mon, 16 Jul 2018 00:16:29 +0200
sched/cpufreq: Clarify su
Commit-ID: af0fffd9300b97d8875aa745bc78e2f6fdb3c1f0
Gitweb: https://git.kernel.org/tip/af0fffd9300b97d8875aa745bc78e2f6fdb3c1f0
Author: Sebastian Andrzej Siewior
AuthorDate: Fri, 6 Jul 2018 15:06:15 +0200
Committer: Ingo Molnar
CommitDate: Mon, 16 Jul 2018 00:16:29 +0200
sched/core: Re
Commit-ID: 5fd778915ad29184a5ff8eb82d1118f6916b79e4
Gitweb: https://git.kernel.org/tip/5fd778915ad29184a5ff8eb82d1118f6916b79e4
Author: Vincent Guittot
AuthorDate: Thu, 28 Jun 2018 17:45:14 +0200
Committer: Ingo Molnar
CommitDate: Mon, 16 Jul 2018 00:16:29 +0200
sched/sysctl: Remove un
Commit-ID: 092b31aa2048cf7561a39697974adcd147fbb27b
Gitweb: https://git.kernel.org/tip/092b31aa2048cf7561a39697974adcd147fbb27b
Author: Dan Williams
AuthorDate: Sun, 8 Jul 2018 13:46:17 -0700
Committer: Ingo Molnar
CommitDate: Mon, 16 Jul 2018 00:05:05 +0200
x86/asm/memcpy_mcsafe: Fix
Commit-ID: bbb62c0b024a1c721232667fa1d625cf6b3a555b
Gitweb: https://git.kernel.org/tip/bbb62c0b024a1c721232667fa1d625cf6b3a555b
Author: Vincent Guittot
AuthorDate: Thu, 28 Jun 2018 17:45:13 +0200
Committer: Ingo Molnar
CommitDate: Mon, 16 Jul 2018 00:16:29 +0200
sched/core: Remove the
Commit-ID: 523e979d31648112bad07f427c183525c0258c75
Gitweb: https://git.kernel.org/tip/523e979d31648112bad07f427c183525c0258c75
Author: Vincent Guittot
AuthorDate: Thu, 28 Jun 2018 17:45:12 +0200
Committer: Ingo Molnar
CommitDate: Mon, 16 Jul 2018 00:16:25 +0200
sched/core: Use PELT fo
1 - 100 of 257 matches
Mail list logo
