Enabling -Wvla found another variable-length array with randconfig
testing:
drivers/mtd/maps/sa1100-flash.c: In function 'sa1100_setup_mtd':
drivers/mtd/maps/sa1100-flash.c:224:10: error: ISO C90 forbids variable length
array 'cdev' [-Werror=vla]
Dynamically allocate the cdev array passed to
Enabling -Wvla found another variable-length array with randconfig
testing:
drivers/mtd/maps/sa1100-flash.c: In function 'sa1100_setup_mtd':
drivers/mtd/maps/sa1100-flash.c:224:10: error: ISO C90 forbids variable length
array 'cdev' [-Werror=vla]
Dynamically allocate the cdev array passed to
Hi Ard,
On Sun, Nov 4, 2018 at 5:15 AM Ard Biesheuvel wrote:
>
> This reverts commit 80463f1b7bf9f822fd3495139bcf3ef254fdca10, because
> it breaks the bindeb-pkg build target in the following way:
>
> ...
> LD [M] sound/soc/rockchip/snd-soc-rk3399-gru-sound.ko
> LD [M]
Hi Ard,
On Sun, Nov 4, 2018 at 5:15 AM Ard Biesheuvel wrote:
>
> This reverts commit 80463f1b7bf9f822fd3495139bcf3ef254fdca10, because
> it breaks the bindeb-pkg build target in the following way:
>
> ...
> LD [M] sound/soc/rockchip/snd-soc-rk3399-gru-sound.ko
> LD [M]
Hi Zhenzhong,
On Fri, Nov 2, 2018 at 8:26 PM Zhenzhong Duan wrote:
>
> Running 'make O=/build/kernel binrpm-pkg' failed with below two errors.
>
> Makefile:600: include/config/auto.conf: No such file or directory
>
> + cp make -C /mnt/root/kernel O=/build/kernel image_name make -f
>
Hi Zhenzhong,
On Fri, Nov 2, 2018 at 8:26 PM Zhenzhong Duan wrote:
>
> Running 'make O=/build/kernel binrpm-pkg' failed with below two errors.
>
> Makefile:600: include/config/auto.conf: No such file or directory
>
> + cp make -C /mnt/root/kernel O=/build/kernel image_name make -f
>
Ard Biesheuvel reports bindeb-pkg with O= option is broken in the
following way:
...
LD [M] sound/soc/rockchip/snd-soc-rk3399-gru-sound.ko
LD [M] sound/soc/rockchip/snd-soc-rockchip-pcm.ko
LD [M] sound/soc/rockchip/snd-soc-rockchip-rt5645.ko
LD [M]
Ard Biesheuvel reports bindeb-pkg with O= option is broken in the
following way:
...
LD [M] sound/soc/rockchip/snd-soc-rk3399-gru-sound.ko
LD [M] sound/soc/rockchip/snd-soc-rockchip-pcm.ko
LD [M] sound/soc/rockchip/snd-soc-rockchip-rt5645.ko
LD [M]
Zhenzhong Duan reported that running 'make O=/build/kernel binrpm-pkg'
failed with the following errors:
Running 'make O=/build/kernel binrpm-pkg' failed with below two errors.
Makefile:600: include/config/auto.conf: No such file or directory
+ cp make -C /mnt/root/kernel O=/build/kernel
Zhenzhong Duan reported that running 'make O=/build/kernel binrpm-pkg'
failed with the following errors:
Running 'make O=/build/kernel binrpm-pkg' failed with below two errors.
Makefile:600: include/config/auto.conf: No such file or directory
+ cp make -C /mnt/root/kernel O=/build/kernel
Dear Friend,
I know that this mail will come to you as a surprise as we have never
met before, but need not to worry as I am contacting you independently
of my investigation and no one is informed of this communication.
I need your urgent assistance in transferring the sum of $11.3million
Dear Friend,
I know that this mail will come to you as a surprise as we have never
met before, but need not to worry as I am contacting you independently
of my investigation and no one is informed of this communication.
I need your urgent assistance in transferring the sum of $11.3million
This patch adds the Spreadtrum SC27XX serial PMICs fuel gauge support,
which is used to calculate the battery capacity.
Original-by: Yuanjiang Yu
Signed-off-by: Baolin Wang
Acked-by: Linus Walleij
---
Changes from v6:
- Use DIV_ROUND_CLOSEST macro to simplify code.
Changes from v5:
- Save
This patch adds the Spreadtrum SC27XX serial PMICs fuel gauge support,
which is used to calculate the battery capacity.
Original-by: Yuanjiang Yu
Signed-off-by: Baolin Wang
Acked-by: Linus Walleij
---
Changes from v6:
- Use DIV_ROUND_CLOSEST macro to simplify code.
Changes from v5:
- Save
Add one field for 'struct power_supply_battery_info' to present the battery
factory internal resistance.
Signed-off-by: Baolin Wang
Reviewed-by: Linus Walleij
---
Changes from v6:
- None.
Changes from v5:
- None.
Changes from v4:
- None.
Changes from v3:
- New patch in v3, which splits
The internal resistance of a battery is not a constant in its life cycle,
this varies over the age of the battery or temperature and so on. But we
just want use one constant battery internal resistance to estimate the
battery capacity. Thus this patch introduces one property to present
the battery
The internal resistance of a battery is not a constant in its life cycle,
this varies over the age of the battery or temperature and so on. But we
just want use one constant battery internal resistance to estimate the
battery capacity. Thus this patch introduces one property to present
the battery
Add one field for 'struct power_supply_battery_info' to present the battery
factory internal resistance.
Signed-off-by: Baolin Wang
Reviewed-by: Linus Walleij
---
Changes from v6:
- None.
Changes from v5:
- None.
Changes from v4:
- None.
Changes from v3:
- New patch in v3, which splits
We have introduced some battery properties to present the OCV table
temperatures and OCV capacity table values. Thus this patch add OCV
temperature and OCV table for battery information, as well as providing
some helper functions to use the OCV capacity table for users.
Signed-off-by: Baolin Wang
This patch adds the binding documentation for Spreadtrum SC27XX series PMICs
fuel gauge unit device, which is used to calculate the battery capacity.
Signed-off-by: Baolin Wang
Reviewed-by: Linus Walleij
Reviewed-by: Rob Herring
---
Changes from v6:
- None.
Changes from v5:
- None.
Changes
Some battery driver will use the open circuit voltage (OCV) value to look
up the corresponding battery capacity percent in one certain degree Celsius.
Thus this patch provides some battery properties to present the OCV table
temperatures and OCV capacity table values.
Suggested-by: Sebastian
We have introduced some battery properties to present the OCV table
temperatures and OCV capacity table values. Thus this patch add OCV
temperature and OCV table for battery information, as well as providing
some helper functions to use the OCV capacity table for users.
Signed-off-by: Baolin Wang
This patch adds the binding documentation for Spreadtrum SC27XX series PMICs
fuel gauge unit device, which is used to calculate the battery capacity.
Signed-off-by: Baolin Wang
Reviewed-by: Linus Walleij
Reviewed-by: Rob Herring
---
Changes from v6:
- None.
Changes from v5:
- None.
Changes
Some battery driver will use the open circuit voltage (OCV) value to look
up the corresponding battery capacity percent in one certain degree Celsius.
Thus this patch provides some battery properties to present the OCV table
temperatures and OCV capacity table values.
Suggested-by: Sebastian
On 11/3/18 2:34 AM, Greg Kroah-Hartman wrote:
4.18-stable review patch. If anyone has any objections, please let me know.
This patch has a problem. I am working on a fix for that. Please
do not include it in the stable release. Thanks.
--
[ Upstream commit
On 11/3/18 2:34 AM, Greg Kroah-Hartman wrote:
4.18-stable review patch. If anyone has any objections, please let me know.
This patch has a problem. I am working on a fix for that. Please
do not include it in the stable release. Thanks.
--
[ Upstream commit
One cause of decoding errors is un-synchronized side-band data. Timestamps
are needed to debug such cases. TSC packet timestamps are logged. Log also
MTC and CYC timestamps.
Signed-off-by: Adrian Hunter
---
tools/perf/util/intel-pt-decoder/intel-pt-decoder.c | 4
1 file changed, 4
One cause of decoding errors is un-synchronized side-band data. Timestamps
are needed to debug such cases. TSC packet timestamps are logged. Log also
MTC and CYC timestamps.
Signed-off-by: Adrian Hunter
---
tools/perf/util/intel-pt-decoder/intel-pt-decoder.c | 4
1 file changed, 4
More event information is useful for debugging, especially MMAP events.
Signed-off-by: Adrian Hunter
---
tools/perf/util/intel-pt-decoder/intel-pt-log.c | 5 +
tools/perf/util/intel-pt-decoder/intel-pt-log.h | 1 +
tools/perf/util/intel-pt.c | 16 +---
3
More event information is useful for debugging, especially MMAP events.
Signed-off-by: Adrian Hunter
---
tools/perf/util/intel-pt-decoder/intel-pt-log.c | 5 +
tools/perf/util/intel-pt-decoder/intel-pt-log.h | 1 +
tools/perf/util/intel-pt.c | 16 +---
3
When multiple domains per device has been enabled by the
device driver, the device will tag the default PASID for
the domain to all DMA traffics out of the subset of this
device; and the IOMMU should translate the DMA requests
in PASID granularity.
This extends the
When multiple domains per device has been enabled by the
device driver, the device will tag the default PASID for
the domain to all DMA traffics out of the subset of this
device; and the IOMMU should translate the DMA requests
in PASID granularity.
This extends the
Hi
Here is a couple of small patches to add more information to the Intel PT
debug log.
Adrian Hunter (2):
perf intel-pt: Add more event information to debug log
perf intel-pt: Add MTC and CYC timestamps to debug log
tools/perf/util/intel-pt-decoder/intel-pt-decoder.c | 4
Hi
Here is a couple of small patches to add more information to the Intel PT
debug log.
Adrian Hunter (2):
perf intel-pt: Add more event information to debug log
perf intel-pt: Add MTC and CYC timestamps to debug log
tools/perf/util/intel-pt-decoder/intel-pt-decoder.c | 4
On 10/18/18 3:19 AM, Jan Kara wrote:
> On Thu 11-10-18 20:53:34, John Hubbard wrote:
>> On 10/11/18 6:23 PM, John Hubbard wrote:
>>> On 10/11/18 6:20 AM, Jason Gunthorpe wrote:
On Thu, Oct 11, 2018 at 10:49:29AM +0200, Jan Kara wrote:
[...]
> Well, put_page() cannot assert page is not
On 10/18/18 3:19 AM, Jan Kara wrote:
> On Thu 11-10-18 20:53:34, John Hubbard wrote:
>> On 10/11/18 6:23 PM, John Hubbard wrote:
>>> On 10/11/18 6:20 AM, Jason Gunthorpe wrote:
On Thu, Oct 11, 2018 at 10:49:29AM +0200, Jan Kara wrote:
[...]
> Well, put_page() cannot assert page is not
On 10/22/18 12:43 PM, Jason Gunthorpe wrote:
> On Thu, Oct 11, 2018 at 06:23:24PM -0700, John Hubbard wrote:
>> On 10/11/18 6:20 AM, Jason Gunthorpe wrote:
>>> On Thu, Oct 11, 2018 at 10:49:29AM +0200, Jan Kara wrote:
>>>
> This is a real worry. If someone uses a mistaken put_page() then how
On 10/22/18 12:43 PM, Jason Gunthorpe wrote:
> On Thu, Oct 11, 2018 at 06:23:24PM -0700, John Hubbard wrote:
>> On 10/11/18 6:20 AM, Jason Gunthorpe wrote:
>>> On Thu, Oct 11, 2018 at 10:49:29AM +0200, Jan Kara wrote:
>>>
> This is a real worry. If someone uses a mistaken put_page() then how
On 10/13/18 9:47 AM, Christoph Hellwig wrote:
> On Sat, Oct 13, 2018 at 12:34:12AM -0700, John Hubbard wrote:
>> In patch 6/6, pin_page_for_dma(), which is called at the end of
>> get_user_pages(),
>> unceremoniously rips the pages out of the LRU, as a prerequisite to using
>> either of the
On 10/13/18 9:47 AM, Christoph Hellwig wrote:
> On Sat, Oct 13, 2018 at 12:34:12AM -0700, John Hubbard wrote:
>> In patch 6/6, pin_page_for_dma(), which is called at the end of
>> get_user_pages(),
>> unceremoniously rips the pages out of the LRU, as a prerequisite to using
>> either of the
On Mon, Nov 05, 2018 at 02:58:07PM +0800, Vincent Chen wrote:
> Many thanks for kinds of comments. I quickly synthesize the comments and
> list them as below.
> 1. The kernel image shall include all vendor-specific code.
I fundamentally disagree with this… and think it should be the contrary.
1.
On Mon, Nov 05, 2018 at 02:58:07PM +0800, Vincent Chen wrote:
> Many thanks for kinds of comments. I quickly synthesize the comments and
> list them as below.
> 1. The kernel image shall include all vendor-specific code.
I fundamentally disagree with this… and think it should be the contrary.
1.
FYI, we noticed the following commit (built with gcc-6):
commit: 0e9446c35a80931044b6d8d2d74a9cabd248539f ("xarray: Add range store
functionality")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
in testcase: trinity
with following parameters:
runtime: 300s
FYI, we noticed the following commit (built with gcc-6):
commit: 0e9446c35a80931044b6d8d2d74a9cabd248539f ("xarray: Add range store
functionality")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
in testcase: trinity
with following parameters:
runtime: 300s
On Fri, Nov 02, 2018 at 01:48:57AM +0800, Karsten Merker wrote:
> On Wed, Oct 31, 2018 at 10:27:05AM -0700, Palmer Dabbelt wrote:
> > On Wed, 31 Oct 2018 04:16:10 PDT (-0700), a...@brainfault.org wrote:
> > > On Wed, Oct 31, 2018 at 4:06 PM Vincent Chen
> > > wrote:
> > > >
> > > > RISC-V
On Fri, Nov 02, 2018 at 01:48:57AM +0800, Karsten Merker wrote:
> On Wed, Oct 31, 2018 at 10:27:05AM -0700, Palmer Dabbelt wrote:
> > On Wed, 31 Oct 2018 04:16:10 PDT (-0700), a...@brainfault.org wrote:
> > > On Wed, Oct 31, 2018 at 4:06 PM Vincent Chen
> > > wrote:
> > > >
> > > > RISC-V
On 18-11-01 08:59:08, Waiman Long wrote:
> On 10/31/2018 11:20 PM, Yi Sun wrote:
> > On 18-10-31 18:15:39, Peter Zijlstra wrote:
> >> On Wed, Oct 31, 2018 at 11:07:22AM -0400, Waiman Long wrote:
> >>> On 10/31/2018 10:10 AM, Peter Zijlstra wrote:
> On Wed, Oct 31, 2018 at 09:54:17AM +0800, Yi
On 18-11-01 08:59:08, Waiman Long wrote:
> On 10/31/2018 11:20 PM, Yi Sun wrote:
> > On 18-10-31 18:15:39, Peter Zijlstra wrote:
> >> On Wed, Oct 31, 2018 at 11:07:22AM -0400, Waiman Long wrote:
> >>> On 10/31/2018 10:10 AM, Peter Zijlstra wrote:
> On Wed, Oct 31, 2018 at 09:54:17AM +0800, Yi
On Sun 04-11-18 07:44:56, Yangtao Li wrote:
> WARN_ON() already contains an unlikely(), so it's not necessary to use
> unlikely.
We should just get rid of this ugliness altogether. It no longer serves
its purpose. This is a historical artifact from 2005 where do_brk
was called outside of the
On Sun 04-11-18 07:44:56, Yangtao Li wrote:
> WARN_ON() already contains an unlikely(), so it's not necessary to use
> unlikely.
We should just get rid of this ugliness altogether. It no longer serves
its purpose. This is a historical artifact from 2005 where do_brk
was called outside of the
Steve Kemp wrote:
> This is an interesting idea, and an evolution since the initial
> approach which was submitted based upon xattr attributes. I still
> find the idea of using attributes simpler to manage though, since
> they're easy to add, and audit for.
>
> I suspect the biggest objection
Steve Kemp wrote:
> This is an interesting idea, and an evolution since the initial
> approach which was submitted based upon xattr attributes. I still
> find the idea of using attributes simpler to manage though, since
> they're easy to add, and audit for.
>
> I suspect the biggest objection
Greetings Thomas,
On 11/04/2018 11:05 PM, Thomas Gleixner wrote:
> Eial,
>
> On Thu, 1 Nov 2018, Eial Czerwacki wrote:
>
>> Subject: x86/build: Build VSMP support only if CONFIG_PCI is selected
>
> That's not what the patch does, right?
>
you are correct, I'll resend it with a more
Greetings Thomas,
On 11/04/2018 11:05 PM, Thomas Gleixner wrote:
> Eial,
>
> On Thu, 1 Nov 2018, Eial Czerwacki wrote:
>
>> Subject: x86/build: Build VSMP support only if CONFIG_PCI is selected
>
> That's not what the patch does, right?
>
you are correct, I'll resend it with a more
We will need these going forward in hotpath, i.e. from within
dev_pm_genpd_set_performance_state().
Lets fetch and save them while the OPP tables are added.
Signed-off-by: Viresh Kumar
---
drivers/base/power/domain.c | 23 +--
include/linux/pm_domain.h | 2 ++
2 files
Quoting Amit Nischal (2018-08-12 23:33:07)
> +
> +static int gpu_cc_sdm845_probe(struct platform_device *pdev)
> +{
> + struct regmap *regmap;
> + unsigned int value, mask;
> + int ret;
> +
> + regmap = qcom_cc_map(pdev, _cc_sdm845_desc);
> + if (IS_ERR(regmap))
> +
Hi,
This series adds performance state propagation support in genpd core.
The propagation happens from the sub-domains to their masters. More
details can be found in the individual commit logs.
This is tested on hikey960 by faking power domains in such a way that
the CPU devices have two power
Introduce a new helper dev_pm_opp_xlate_performance_state() which will
be used to translate from pstate of a device to another one.
Initially this will be used by genpd to find pstate of a master domain
using its sub-domain's pstate.
Signed-off-by: Viresh Kumar
---
drivers/opp/core.c | 49
This commit updates genpd core to start propagating performance state
updates to master domains that have their set_performance_state()
callback set.
A genpd handles two type of performance states now. The first one is the
performance state requirement put on the genpd by the devices and
We will need these going forward in hotpath, i.e. from within
dev_pm_genpd_set_performance_state().
Lets fetch and save them while the OPP tables are added.
Signed-off-by: Viresh Kumar
---
drivers/base/power/domain.c | 23 +--
include/linux/pm_domain.h | 2 ++
2 files
Quoting Amit Nischal (2018-08-12 23:33:07)
> +
> +static int gpu_cc_sdm845_probe(struct platform_device *pdev)
> +{
> + struct regmap *regmap;
> + unsigned int value, mask;
> + int ret;
> +
> + regmap = qcom_cc_map(pdev, _cc_sdm845_desc);
> + if (IS_ERR(regmap))
> +
Hi,
This series adds performance state propagation support in genpd core.
The propagation happens from the sub-domains to their masters. More
details can be found in the individual commit logs.
This is tested on hikey960 by faking power domains in such a way that
the CPU devices have two power
Introduce a new helper dev_pm_opp_xlate_performance_state() which will
be used to translate from pstate of a device to another one.
Initially this will be used by genpd to find pstate of a master domain
using its sub-domain's pstate.
Signed-off-by: Viresh Kumar
---
drivers/opp/core.c | 49
This commit updates genpd core to start propagating performance state
updates to master domains that have their set_performance_state()
callback set.
A genpd handles two type of performance states now. The first one is the
performance state requirement put on the genpd by the devices and
Separate out _genpd_set_performance_state() and
_genpd_reeval_performance_state() from
dev_pm_genpd_set_performance_state() to handle performance state update
related stuff. This will be used by a later commit.
Signed-off-by: Viresh Kumar
---
drivers/base/power/domain.c | 104
Separate out _genpd_set_performance_state() and
_genpd_reeval_performance_state() from
dev_pm_genpd_set_performance_state() to handle performance state update
related stuff. This will be used by a later commit.
Signed-off-by: Viresh Kumar
---
drivers/base/power/domain.c | 104
Quoting Amit Nischal (2018-08-12 23:33:04)
> For some of the GDSCs, there is a requirement to enable/disable the
> few clocks before turning on/off the gdsc power domain. Add support
> for the same by specifying a list of clk_hw pointers per gdsc and
> enable/disable them along with power domain
Quoting Amit Nischal (2018-08-12 23:33:04)
> For some of the GDSCs, there is a requirement to enable/disable the
> few clocks before turning on/off the gdsc power domain. Add support
> for the same by specifying a list of clk_hw pointers per gdsc and
> enable/disable them along with power domain
On Mon, Nov 5, 2018 at 4:18 AM Jiri Olsa wrote:
>
> On Sat, Nov 03, 2018 at 06:36:21PM +0900, Xin Long wrote:
> > On Fri, Nov 2, 2018 at 7:26 PM Jiri Olsa wrote:
> > >
> > > On Fri, Nov 02, 2018 at 03:36:13PM +0900, Xin Long wrote:
> > > > On upstream kernel(4.19) or RHEL-8 kernel(4.18.0):
> > >
On Mon, Nov 5, 2018 at 4:18 AM Jiri Olsa wrote:
>
> On Sat, Nov 03, 2018 at 06:36:21PM +0900, Xin Long wrote:
> > On Fri, Nov 2, 2018 at 7:26 PM Jiri Olsa wrote:
> > >
> > > On Fri, Nov 02, 2018 at 03:36:13PM +0900, Xin Long wrote:
> > > > On upstream kernel(4.19) or RHEL-8 kernel(4.18.0):
> > >
Hi Matias,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 651022382c7f8da46cb4872a545ee1da6d097d2a
commit: 73569e11032fc5a9b314b6351632cfca7793afd5 lightnvm: remove dependencies
on BLK_DEV_NVME and PCI
date: 4
Hi Matias,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 651022382c7f8da46cb4872a545ee1da6d097d2a
commit: 73569e11032fc5a9b314b6351632cfca7793afd5 lightnvm: remove dependencies
on BLK_DEV_NVME and PCI
date: 4
Commit-ID: b068621a53f92f42400581d69ad0e84c56620b0a
Gitweb: https://git.kernel.org/tip/b068621a53f92f42400581d69ad0e84c56620b0a
Author: Randy Dunlap
AuthorDate: Sun, 4 Nov 2018 14:03:56 -0800
Committer: Ingo Molnar
CommitDate: Mon, 5 Nov 2018 07:05:45 +0100
Documentation/x86: Fix typo
Commit-ID: b068621a53f92f42400581d69ad0e84c56620b0a
Gitweb: https://git.kernel.org/tip/b068621a53f92f42400581d69ad0e84c56620b0a
Author: Randy Dunlap
AuthorDate: Sun, 4 Nov 2018 14:03:56 -0800
Committer: Ingo Molnar
CommitDate: Mon, 5 Nov 2018 07:05:45 +0100
Documentation/x86: Fix typo
On Mon, Nov 05, 2018 at 07:59:13AM +0300, Vasily Averin wrote:
>
>
> On 11/5/18 3:50 AM, Huang, Ying wrote:
> > Vasily Averin writes:
> >
> >> commit a2468cc9bfdf ("swap: choose swap device according to numa node")
> >> increased size of swap_info_struct up to 44 Kbytes, now it requires
> >>
On Mon, Nov 05, 2018 at 07:59:13AM +0300, Vasily Averin wrote:
>
>
> On 11/5/18 3:50 AM, Huang, Ying wrote:
> > Vasily Averin writes:
> >
> >> commit a2468cc9bfdf ("swap: choose swap device according to numa node")
> >> increased size of swap_info_struct up to 44 Kbytes, now it requires
> >>
Commit-ID: f75d651587f719a813ebbbfeee570e6570731d55
Gitweb: https://git.kernel.org/tip/f75d651587f719a813ebbbfeee570e6570731d55
Author: Randy Dunlap
AuthorDate: Sun, 4 Nov 2018 18:40:14 -0800
Committer: Ingo Molnar
CommitDate: Mon, 5 Nov 2018 07:05:04 +0100
resource/docs: Fix new
Commit-ID: f75d651587f719a813ebbbfeee570e6570731d55
Gitweb: https://git.kernel.org/tip/f75d651587f719a813ebbbfeee570e6570731d55
Author: Randy Dunlap
AuthorDate: Sun, 4 Nov 2018 18:40:14 -0800
Committer: Ingo Molnar
CommitDate: Mon, 5 Nov 2018 07:05:04 +0100
resource/docs: Fix new
On Sun, Nov 04, 2018 at 01:28:06PM -0800, Guenter Roeck wrote:
> __node_distance is used by nvme, resulting in:
>
> ERROR: "__node_distance" [drivers/nvme/host/nvme-core.ko] undefined!
>
> when trying to build nvme as module.
>
> Fixes: f333444708f8 ("nvme: take node locality into account when
On Sun, Nov 04, 2018 at 01:28:06PM -0800, Guenter Roeck wrote:
> __node_distance is used by nvme, resulting in:
>
> ERROR: "__node_distance" [drivers/nvme/host/nvme-core.ko] undefined!
>
> when trying to build nvme as module.
>
> Fixes: f333444708f8 ("nvme: take node locality into account when
On Sun, 4 Nov 2018 13:28:06 -0800
Guenter Roeck wrote:
> __node_distance is used by nvme, resulting in:
>
> ERROR: "__node_distance" [drivers/nvme/host/nvme-core.ko] undefined!
>
> when trying to build nvme as module.
>
> Fixes: f333444708f8 ("nvme: take node locality into account when
On Sun, 4 Nov 2018 13:28:06 -0800
Guenter Roeck wrote:
> __node_distance is used by nvme, resulting in:
>
> ERROR: "__node_distance" [drivers/nvme/host/nvme-core.ko] undefined!
>
> when trying to build nvme as module.
>
> Fixes: f333444708f8 ("nvme: take node locality into account when
Commit-ID: e1ff516a56ad56c476b47795d3811eef79d25fbe
Gitweb: https://git.kernel.org/tip/e1ff516a56ad56c476b47795d3811eef79d25fbe
Author: Yi Wang
AuthorDate: Mon, 5 Nov 2018 08:50:13 +0800
Committer: Ingo Molnar
CommitDate: Mon, 5 Nov 2018 07:03:59 +0100
sched/fair: Fix a comment in
Commit-ID: e1ff516a56ad56c476b47795d3811eef79d25fbe
Gitweb: https://git.kernel.org/tip/e1ff516a56ad56c476b47795d3811eef79d25fbe
Author: Yi Wang
AuthorDate: Mon, 5 Nov 2018 08:50:13 +0800
Committer: Ingo Molnar
CommitDate: Mon, 5 Nov 2018 07:03:59 +0100
sched/fair: Fix a comment in
Hi all,
Commit
bf4d4ba7d970 ("cifs: update internal module version number for cifs.ko")
is missing a Signed-off-by from its author and committer.
--
Cheers,
Stephen Rothwell
pgpwC0LnYhEkJ.pgp
Description: OpenPGP digital signature
Hi all,
Commit
bf4d4ba7d970 ("cifs: update internal module version number for cifs.ko")
is missing a Signed-off-by from its author and committer.
--
Cheers,
Stephen Rothwell
pgpwC0LnYhEkJ.pgp
Description: OpenPGP digital signature
Hi all,
Changes since 20181102:
Non-merge commits (relative to Linus' tree): 418
585 files changed, 22874 insertions(+), 5819 deletions(-)
I have created today's linux-next tree at
Hi all,
Changes since 20181102:
Non-merge commits (relative to Linus' tree): 418
585 files changed, 22874 insertions(+), 5819 deletions(-)
I have created today's linux-next tree at
On Sat, Nov 3, 2018 at 6:22 PM Jonathan Cameron
wrote:
>
> On Wed, 31 Oct 2018 10:29:59 +0800
> Chen-Yu Tsai wrote:
>
> > On Mon, Oct 29, 2018 at 9:10 PM Quentin Schulz
> > wrote:
> > >
> > > Hi Jonathan,
> > >
> > > On Sun, Oct 28, 2018 at 03:40:11PM +, Jonathan Cameron wrote:
> > > > On
On Sat, Nov 3, 2018 at 6:22 PM Jonathan Cameron
wrote:
>
> On Wed, 31 Oct 2018 10:29:59 +0800
> Chen-Yu Tsai wrote:
>
> > On Mon, Oct 29, 2018 at 9:10 PM Quentin Schulz
> > wrote:
> > >
> > > Hi Jonathan,
> > >
> > > On Sun, Oct 28, 2018 at 03:40:11PM +, Jonathan Cameron wrote:
> > > > On
Hi Matthew,
On Sun, Nov 4, 2018 at 2:06 PM Mike Rapoport wrote:
>
> On Sat, Nov 03, 2018 at 05:02:36AM -0700, Matthew Wilcox wrote:
> > On Sat, Nov 03, 2018 at 10:35:04AM +0530, Souptick Joarder wrote:
> > > Page fault handlers are supposed to return VM_FAULT codes,
> > > but some drivers/file
Hi Matthew,
On Sun, Nov 4, 2018 at 2:06 PM Mike Rapoport wrote:
>
> On Sat, Nov 03, 2018 at 05:02:36AM -0700, Matthew Wilcox wrote:
> > On Sat, Nov 03, 2018 at 10:35:04AM +0530, Souptick Joarder wrote:
> > > Page fault handlers are supposed to return VM_FAULT codes,
> > > but some drivers/file
On 11/5/18 8:10 AM, kernel test robot wrote:
> FYI, we noticed the following commit (built with gcc-7):
>
> commit: 1ee5ee5ec39e53af9bcd215f4d127b21d579f700 ("[PATCH 3/7] ext4 resize:
> missing brelse() in case success in add_new_gdb()")
yes, you're right, this patch was wrong and it was dropped
On 11/5/18 8:10 AM, kernel test robot wrote:
> FYI, we noticed the following commit (built with gcc-7):
>
> commit: 1ee5ee5ec39e53af9bcd215f4d127b21d579f700 ("[PATCH 3/7] ext4 resize:
> missing brelse() in case success in add_new_gdb()")
yes, you're right, this patch was wrong and it was dropped
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 651022382c7f8da46cb4872a545ee1da6d097d2a
commit: 2ce7135adc9ad081aa3c49744144376ac74fea60 psi: cgroup support
date: 9 days ago
config: x86_64-randconfig-s1-11051307 (attached as .config)
compiler: gcc-6
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 651022382c7f8da46cb4872a545ee1da6d097d2a
commit: 2ce7135adc9ad081aa3c49744144376ac74fea60 psi: cgroup support
date: 9 days ago
config: x86_64-randconfig-s1-11051307 (attached as .config)
compiler: gcc-6
On 11/5/18 3:57 AM, Huang, Ying wrote:
> Vasily Averin writes:
>
>> Currently newly allocated swap_info_struct can be quickly freed.
>> This patch avoid uneccessary high-order page allocation and helps
>> to decrease the memory pressure.
>
> I think swapon/swapoff are rare operations, so it
On 11/5/18 3:57 AM, Huang, Ying wrote:
> Vasily Averin writes:
>
>> Currently newly allocated swap_info_struct can be quickly freed.
>> This patch avoid uneccessary high-order page allocation and helps
>> to decrease the memory pressure.
>
> I think swapon/swapoff are rare operations, so it
Vasily Averin writes:
> On 11/5/18 3:50 AM, Huang, Ying wrote:
>> Vasily Averin writes:
>>
>>> commit a2468cc9bfdf ("swap: choose swap device according to numa node")
>>> increased size of swap_info_struct up to 44 Kbytes, now it requires
>>> 4th order page.
>>
>> Why swap_info_struct could
Vasily Averin writes:
> On 11/5/18 3:50 AM, Huang, Ying wrote:
>> Vasily Averin writes:
>>
>>> commit a2468cc9bfdf ("swap: choose swap device according to numa node")
>>> increased size of swap_info_struct up to 44 Kbytes, now it requires
>>> 4th order page.
>>
>> Why swap_info_struct could
1 - 100 of 860 matches
Mail list logo
