On 9/6/2019 5:19 PM, Andy Shevchenko wrote:
On Thu, Sep 05, 2019 at 10:31:29PM +0200, Martin Blumenstingl wrote:
On Wed, Sep 4, 2019 at 12:11 PM Dilip Kota wrote:
+ phy-names:
+const: pciephy
the most popular choice in Documentation/devicetree/bindings/pci/ is "pcie-phy"
if Rob is happ
On 08/09/2019 17.12, Vinod Koul wrote:
> On 30-07-19, 12:34, Peter Ujfalusi wrote:
>> The metadata is best described as side band data or parameters traveling
>> alongside the data DMAd by the DMA engine. It is data
>> which is understood by the peripheral and the peripheral driver only, the
>>
On 9/6/2019 7:20 PM, Andrew Murray wrote:
On Fri, Sep 06, 2019 at 06:58:11PM +0800, Dilip Kota wrote:
Hi Andrew Murray,
Thanks for the review. Please find my response inline.
On 9/5/2019 6:45 PM, Andrew Murray wrote:
On Wed, Sep 04, 2019 at 06:10:31PM +0800, Dilip Kota wrote:
Add support t
On Sun, Sep 8, 2019 at 6:19 PM Linus Torvalds
wrote:
>
> On Sat, Sep 7, 2019 at 11:08 PM syzbot
> wrote:
> >
> > The bug was bisected to:
> >
> > commit e41d58185f1444368873d4d7422f7664a68be61d
> > Author: Dmitry Vyukov
> > Date: Wed Jul 12 21:34:35 2017 +
> >
> > fault-inject: suppor
Hi Pierre
We are working on a backport 3.14 branch for Chrome projects based on BDW
platform. In the branch 4-channel capture is supported on some platforms but
not all. So we need to add a constraint in the machine driver for machines
don't support this feature.
I checked the for-next branch
Hi Sujeev, all,
Is the code somewhere in a repository for review?>
> Hi Greg Kroah-Hartman\Arnd Bergmann and community
>
> Thank you for all the feedback, I believe I have addressed all the comments
> from previous
> patches. Also, I am excluding mhi network driver in this series. I still have
On 08/09/2019 15.10, Vinod Koul wrote:
> On 08-09-19, 10:47, Peter Ujfalusi wrote:
>>
>>
>> On 06/09/2019 17.18, Peter Ujfalusi wrote:
>>> On systems where multiple DMA controllers available, none Slave (for example
>>> memcpy operation) users can not be described in DT as there is no device
>>>
On 09/07/2019 12:33 AM, Gerald Schaefer wrote:
> On Fri, 6 Sep 2019 11:58:59 +0530
> Anshuman Khandual wrote:
>
>> On 09/05/2019 10:36 PM, Gerald Schaefer wrote:
>>> On Thu, 5 Sep 2019 14:48:14 +0530
>>> Anshuman Khandual wrote:
>>>
> [...]
>> +
>> +#if !defined(__PAGETABLE
Peter Zijlstra wrote:
>
> Paulmck actually has an example of that somewhere; ISTR that particular
> case actually got fixed by GCC, but I'd really _love_ for some compiler
> people (both GCC and LLVM) to state that their respective compilers will
> not do load/store tearing for machine word sized
On Mon, Sep 09, 2019 at 02:06:54PM +0800, Rong Chen wrote:
> Hi Dave,
>
> On 9/9/19 1:32 PM, Dave Chinner wrote:
> > On Mon, Sep 09, 2019 at 09:58:49AM +0800, kernel test robot wrote:
> > > Greeting,
> > >
> > > FYI, we noticed a -71.2% improvement of fsmark.app_overhead due to commit:
> > A nega
On Sun, Sep 08, 2019 at 08:19:21PM -0400, Valdis Klētnieks wrote:
> In that case, rather than removing it, shouldn't we be *adding*
> code to properly set it instead?
Right, setting the UtcOffset fields to 0 is the first step marking
them as invalid for now. This is also why access_time_ms did not
If we are already under list_lock, don't call kmalloc(). Otherwise we
will run into deadlock because kmalloc() also tries to grab the same
lock.
Instead, allocate pages directly. Given currently page->objects has
15 bits, we only need 1 page. We may waste some memory but we only do
so when slub de
Hi,
Mostly some cosmetic comments below, other than that seems fine to me.
On 30/07/2019 12:34, Peter Ujfalusi wrote:
From: Grygorii Strashko
The Ring Accelerator (RINGACC or RA) provides hardware acceleration to
enable straightforward passing of work between a producer and a consumer.
There
Hi Dave,
On 9/9/19 1:32 PM, Dave Chinner wrote:
On Mon, Sep 09, 2019 at 09:58:49AM +0800, kernel test robot wrote:
Greeting,
FYI, we noticed a -71.2% improvement of fsmark.app_overhead due to commit:
A negative improvement? That's somewhat ambiguous...
Sorry for causing the misunderstanding
Currently a device does not belong to any of the numa nodes
(dev->numa_node is NUMA_NO_NODE) when the node id is neither
specified by fw nor by virtual device layer and the device has
no parent device.
According to discussion in [1]:
Even if a device's numa node is not specified, the device really
Hi,
On 27/08/19 9:28 AM, Ramuthevar,Vadivel MuruganX wrote:
> From: Ramuthevar Vadivel Murugan
>
> on Intel's Lightning Mountain(LGM) SoCs QSPI controller do not use
> Direct Memory Access(DMA) and Direct Access Controller(DAC).
>
> This patch introduces to properly disable the DMA and DAC
> fo
On 2019/09/06 19:35, David Hildenbrand wrote:
> On 06.09.19 12:02, Toshiki Fukasawa wrote:
>> Thank you for your feedback.
>>
>> On 2019/09/06 17:45, David Hildenbrand wrote:
>>> On 06.09.19 10:09, Toshiki Fukasawa wrote:
A kernel panic is observed during reading
/proc/kpage{cgroup,count,
On 08/09/2019 15.06, Vinod Koul wrote:
> On 06-09-19, 17:18, Peter Ujfalusi wrote:
>> On systems where multiple DMA controllers available, none Slave (for example
>
> On systems with multiple DMA controllers, non Slave...
Sure.
>> memcpy operation) users can not be described in DT as there is
On 08/09/2019 15.15, Vinod Koul wrote:
> On 06-09-19, 17:18, Peter Ujfalusi wrote:
>> In case the channel is not requested via the slave API, use the
>> of_find_dma_domain() to see if a system default DMA controller is
>> specified.
>>
>> Add new function which can be used by clients to request
On Sun, 2019-09-08 at 12:09 +0100, Jonathan Cameron wrote:
> On Mon, 2 Sep 2019 13:26:02 +
> "Ardelean, Alexandru" wrote:
>
> > On Sun, 2019-09-01 at 21:59 -0300, Rodrigo Carvalho wrote:
> > > Move ADIS16240 driver from staging to mainline.
> > >
> > > The ADIS16240 is a fully integrated dig
On Sun, 8 Sep 2019 at 18:19, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 5.2.14 release.
> There are 94 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Respo
The type of 'chan' is u32 which contain non-negative value.
So 'chan < 0' is statment is always false.
Remove unnecessary comparison statement
Signed-off-by: Austin Kim
---
drivers/scsi/dpt_i2o.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/scsi/dpt_i2o.c b/driver
On Mon, Sep 09, 2019 at 09:58:49AM +0800, kernel test robot wrote:
> Greeting,
>
> FYI, we noticed a -71.2% improvement of fsmark.app_overhead due to commit:
A negative improvement? That's somewhat ambiguous...
> 0e822255f95db400 610125ab1e4b1b48dcffe74d9d8
> --
Hi Luca, Jacopo, Wolfram, Peter,
On 09/08/2019 11:45 PM, Vladimir Zapolskiy wrote:
> Hi Luca, Jacopo, Wolfram, Peter,
>
> On 09/01/2019 05:31 PM, jacopo mondi wrote:
>> Hi Luca,
>>thanks for keep pushing this series! I hope we can use part of this
>> for the (long time) on-going GMSL work...
Hi, RMS and Bruce Perens;
I noticed that recently Grsecurity's Brad Spengler (who sued you, Bruce,
for speaking the truth), decided to "Flex" and basically advertise while
chastising the linux community:
news.ycombinator.com/item?id=20874470
Another poster then pointed out the history of Gr
On Mon, Sep 09, 2019 at 10:18:57AM +0800, Jason Wang wrote:
>
> On 2019/9/8 下午7:05, Michael S. Tsirkin wrote:
> > On Thu, Sep 05, 2019 at 08:27:36PM +0800, Jason Wang wrote:
> > > This is a rework on the commit 7f466032dc9e ("vhost: access vq
> > > metadata through kernel virtual address").
> > >
This is an example script that could be applied to
-next to get compiler coverage testing for a treewide
conversion of __section(foo) to __section("foo")
I compiled an x86 defconfig but the coverage for this
script output, but it's possible an arch or two may have
asm compilation without including
On Sun, Sep 08, 2019 at 08:10:17PM -0700, Hugh Dickins wrote:
Hmm... FWIW, I'd ended up redoing most of the thing, with
hopefully sane carve-up. Differences:
* we really care only about three things having
been set - ->max_blocks, ->max_inodes and ->huge. This
__set_bit() hack is cute,
Hi Katsuhiro
> >> Bad scenario as follows (mclk-fs = 256):
> >> - Initialize sysclk by correct value (Ex. 12.288MHz)
> >> - Codec set constraints of PCM rate by sysclk
> >> 48kHz (1/256), 32kHz (1/384), 24kHz (1/512)
> >> - Play 48kHz sound, it's acceptable
> >> - Syscl
On 9/8/19 10:22 PM, Ondřej Jirman wrote:
> Hello Samuel,
>
> On Mon, Aug 19, 2019 at 10:23:01PM -0500, Samuel Holland wrote:
>> This series adds support for the "hardware message box" in sun8i, sun9i,
>> and sun50i SoCs, used for communication with the ARISC management
>> processor (the platform's
PING
yuzhoujian 于2019年9月3日周二 下午4:56写道：
>
> From: YuZhoujian
>
> Just add '-i' option for perf sched {map|latency|replay|timehist}
>
> Signed-off-by: YuZhoujian
> ---
> tools/perf/Documentation/perf-sched.txt | 7 +++
> tools/perf/builtin-sched.c | 4
> 2 files changed, 1
From: Peng Fan
When registering the PLL, unbypass the PLL.
The PLL has two bypass control bit, BYPASS and EXT_BYPASS.
we will expose EXT_BYPASS to clk driver for mux usage, and keep
BYPASS inside pll14xx usage. The PLL has a restriction that
when M/P change, need to RESET/BYPASS pll to avoid glit
Hi Stephen,
> Subject: Re: [PATCH V2 1/4] clk: imx: pll14xx: avoid glitch when set rate
>
> Quoting Peng Fan (2019-08-26 02:42:14)
> > From: Peng Fan
> >
> > According to PLL1443XA and PLL1416X spec, "When BYPASS is 0 and RESETB
> > is changed from 0 to 1, FOUT starts to output unstable clock un
From: Peng Fan
pll BYPASS bit should be kept inside pll driver for glitchless freq
setting following spec. If exposing the bit, that means pll driver and
clk driver has two paths to touch this bit, which is wrong.
So use EXT_BYPASS bit here.
And drop uneeded set parent, because EXT_BYPASS defau
From: Peng Fan
pll BYPASS bit should be kept inside pll driver for glitchless freq
setting following spec. If exposing the bit, that means pll driver and
clk driver has two paths to touch this bit, which is wrong.
So use EXT_BYPASS bit here.
And drop uneeded set parent, because EXT_BYPASS defau
From: Peng Fan
According to PLL1443XA and PLL1416X spec,
"When BYPASS is 0 and RESETB is changed from 0 to 1, FOUT starts to
output unstable clock until lock time passes. PLL1416X/PLL1443XA may
generate a glitch at FOUT."
So set BYPASS when RESETB is changed from 0 to 1 to avoid glitch.
In the e
From: Peng Fan
V3:
Add cover-letter
V2:
Added patch [2,3,4]/4 and avoid glitch when prepare
There is two bypass bit in the pll, BYPASS and EXT_BYPASS.
There is also a restriction that to avoid glitch, need set BYPASS
bit when RESETB changed from 0 to 1, otherwise there will be glitch.
Howeve
Currently we parse user data byte after byte which leads to
overcomplicating of parsing algorithm. There are no performance
critical users of bitmap_parse_user(), and so we can duplicate
user data to kernel buffer and simply call bitmap_parselist().
This rework lets us unify and simplify bitmap_par
bitmap_parse() is ineffective and full of opaque variables and opencoded
parts. It leads to hard understanding and usage of it. This rework
includes:
- remove bitmap_shift_left() call from the cycle. Now it makes the
complexity of the algorithm as O(nbits^2). In the suggested approach
the in
New version of bitmap_parse() is unified with bitmap_parse_list(),
and therefore:
- weakens rules on whitespaces and commas between hex chunks;
- in addition to \0 allows using \n as the line ending symbol;
- allows passing UINT_MAX or any other big number as the length
of input string instea
New design of inner bitmap_parse() allows to avoid
calculating the size of a null-terminated string.
Reviewed-by: Andy Shevchenko
Signed-off-by: Yury Norov
---
include/linux/cpumask.h | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/include/linux/cpumask.h b/include/linux/
Introduce BITS_TO_U64, BITS_TO_U32 and BITS_TO_BYTES as they are handy
in the following patches (BITS_TO_U32 specifically). Reimplement tools/
version of the macros according to the kernel implementation.
Also fix indentation for BITS_PER_TYPE definition.
Reviewed-by: Andy Shevchenko
Signed-of
New function works like strchrnul() with a length limited strings.
Reviewed-by: Andy Shevchenko
Signed-off-by: Yury Norov
---
include/linux/string.h | 1 +
lib/string.c | 17 +
2 files changed, 18 insertions(+)
diff --git a/include/linux/string.h b/include/linux/stri
The test is derived from bitmap_parselist()
NO_LEN is reserved for use in following patches.
Reviewed-by: Andy Shevchenko
Signed-off-by: Yury Norov
---
lib/test_bitmap.c | 94 ++-
1 file changed, 93 insertions(+), 1 deletion(-)
diff --git a/lib/test_
Hi all,
I'm sorry for long delay with re-submission of this series
As Andy mentioned in review for v3, I switched to isxdigit()
where appropriate. I also removed my Marvell's signed-off-by
since I don't work for them anymore.
Thanks,
Yury
On top of next-20190904.
Similarly to recently revisited
Hello Samuel,
On Mon, Aug 19, 2019 at 10:23:01PM -0500, Samuel Holland wrote:
> This series adds support for the "hardware message box" in sun8i, sun9i,
> and sun50i SoCs, used for communication with the ARISC management
> processor (the platform's equivalent of the ARM SCP). The end goal is to
>
On Sun, 8 Sep 2019 at 18:20, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.19.72 release.
> There are 57 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Resp
On Mon, 9 Sep 2019, Al Viro wrote:
> On Sun, Sep 08, 2019 at 10:46:01PM +0100, Al Viro wrote:
> > On Tue, Sep 03, 2019 at 04:41:22PM +0800, kernel test robot wrote:
> > > Greeting,
> > >
> > > FYI, we noticed a -23.7% regression of vm-scalability.median due to
> > > commit:
> > >
> > >
> > > co
On Sat, Sep 7, 2019 at 2:52 AM Arnd Bergmann wrote:
>
> The intel_pin_to_gpio() function is only called by the
> PM support functions and causes a warning when those are disabled:
>
> drivers/pinctrl/intel/pinctrl-intel.c:841:12: error: unused function
> 'intel_pin_to_gpio' [-Werror,-Wunused-func
On Sun, Sep 08, 2019 at 10:43:02AM +0100, Okash Khawaja wrote:
> Sorry, I have only now got round to working on this. It's not complete
> yet but I have assimilated the feedback and converted subjective
> phrases, like "I think..." into objective statements or put them in
> TODO: so that someone el
On 2019/09/09 9:31, Kuninori Morimoto wrote:
Hi Katsuhiro
This patch set 0Hz to sysclk when shutdown the card.
Some codecs set rate constraints that derives from sysclk. This
mechanism works correctly if machine drivers give fixed frequency.
But simple-audio and audio-graph card set variable
From: Srinivas Pandruvada
From: Srinivas Pandruvada
intel_pstate has two operating modes: active and passive. In "active"
mode, the in-built scaling governor is used and in "passive" mode,
the driver can be used with any governor like "schedutil". In "active"
mode the utilization values from sc
Implement arch_scale_freq_capacity() for 'modern' x86. This function
is used by the scheduler to correctly account usage in the face of
DVFS.
The present patch addresses Intel processors specifically and has positive
performance and performance-per-watt implications for the schedutil cpufreq
gover
This is a resend with of Peter Zijlstra's patch to support frequency
scale-invariance on x86 from May 2018 [see 1]. I've added some modifications
and included performance test results. If Peter doesn't mind, I'm slapping my
name on it :)
The changes from Peter's original implementation are:
1) no
On 2019/9/9 上午10:18, Jason Wang wrote:
On a elder CPU Sandy Bridge without SMAP support. TX PPS doesn't see
any difference.
Why is not Kaby Lake with SMAP off the same as Sandy Bridge?
I don't know, I guess it was because the atomic is l
Sorry, I meant atomic costs less for Kaby Lake.
On 2019/9/7 下午11:03, Jason Gunthorpe wrote:
On Fri, Sep 06, 2019 at 06:02:35PM +0800, Jason Wang wrote:
On 2019/9/5 下午9:59, Jason Gunthorpe wrote:
On Thu, Sep 05, 2019 at 08:27:34PM +0800, Jason Wang wrote:
Hi:
Per request from Michael and Jason, the metadata accelreation is
reverted in thi
From: Song Hui
More than one gpio controllers can share one interrupt, change the
driver to request shared irq.
Signed-off-by: Laurentiu Tudor
Signed-off-by: Alex Marginean
Signed-off-by: Song Hui
---
Changes in v3:
- update the patch description.
Changes in v2:
- delete the c
On 2019/9/8 下午7:05, Michael S. Tsirkin wrote:
On Thu, Sep 05, 2019 at 08:27:36PM +0800, Jason Wang wrote:
This is a rework on the commit 7f466032dc9e ("vhost: access vq
metadata through kernel virtual address").
It was noticed that the copy_to/from_user() friends that was used to
access virtq
On 07/09/19 1:31 AM, Tony Lindgren wrote:
Commit d098913a10f8 ("bus: ti-sysc: Fix clock handling for no-idle
quirks") fixed handling for no-idle quirk modules that are not enabled
by the bootloader.
But it also caused unpaired clockdomain calls that won't allow idling
the system. That's becau
On Thu, 29 Aug 2019, at 16:47, Andrew Jeffery wrote:
> Commit 674fa8daa8c9 ("pinctrl: aspeed-g5: Delay acquisition of regmaps")
> was determined to be a partial fix to the problem of acquiring the LPC
> Host Controller and GFX regmaps: The AST2500 pin controller may need to
> fetch syscon regmap
From: Wanpeng Li
This patch reverts commit 75437bb304b20 (locking/pvqspinlock: Don't wait if
vCPU is preempted), we found great regression caused by this commit.
Xeon Skylake box, 2 sockets, 40 cores, 80 threads, three VMs, each is 80 vCPUs.
The score of ebizzy -M can reduce from 13000-14000 re
On Sun, 8 Sep 2019 at 18:15, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.14.143 release.
> There are 40 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Res
On Sun, 8 Sep 2019 at 18:15, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.9.192 release.
> There are 26 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Resp
The patch title is wrong, fix it in v2, sorry.
On 2019/9/6 22:38, YueHaibing wrote:
> Use devm_platform_ioremap_resource() to simplify the code a bit.
> This is detected by coccinelle.
>
> Signed-off-by: YueHaibing
> ---
> drivers/perf/arm_smmuv3_pmu.c | 5 ++---
> 1 file changed, 2 insertions
Use devm_platform_ioremap_resource() to simplify the code a bit.
This is detected by coccinelle.
Signed-off-by: YueHaibing
---
v2: fix patch title
---
drivers/perf/arm_smmuv3_pmu.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/drivers/perf/arm_smmuv3_pmu.c b/drivers/pe
On (09/06/19 17:32), Petr Mladek wrote:
> > [..]
> > > I mean, really, do we need to keep calling wake up if it
> > > probably never even executed?
> >
> > I guess ratelimiting you are talking about ("if it probably never even
> > executed") would be to check if we have already called wake up on t
On 9/7/19 6:27 PM, Changbin Du wrote:
> This series is a trivial improvment for the layout of 'kernel hacking'
> configuration menu. Now we have many items in it which makes takes
> a little time to look up them since they are not well structured yet.
>
> Early discussion is here:
> https://lkml.o
Function ftrace_lookup_ip() will check empty hash table. So we don't
need extra check outside.
Signed-off-by: Changbin Du
---
v2: fix incorrect code remove.
---
kernel/trace/ftrace.c | 9 ++---
1 file changed, 2 insertions(+), 7 deletions(-)
diff --git a/kernel/trace/ftrace.c b/kernel/trac
Hi Katsuhiro
> This patch set 0Hz to sysclk when shutdown the card.
>
> Some codecs set rate constraints that derives from sysclk. This
> mechanism works correctly if machine drivers give fixed frequency.
>
> But simple-audio and audio-graph card set variable clock rate if
> 'mclk-fs' property
On Sun, 08 Sep 2019 17:35:36 -, Valentin Vidic said:
> sbi parameter not used inside the function so remove it.
> Also cleanup unused variables generated by this change.
Tread carefully with this sort of patch - there's still a lot of places in the
code
where we have matching pairs of exfat_f
On Sun, 08 Sep 2019 16:10:14 -, Valentin Vidic said:
> Not used in the exfat-fuse implementation and spec defines
> this position should hold the value for CreateUtcOffset.
In that case, rather than removing it, shouldn't we be *adding*
code to properly set it instead?
pgp9KZVl0RIgO.pgp
Desc
On Fri, 6 Sep 2019, Mickaël Salaün wrote:
> Furthermore, the security policy can also be delegated to an LSM, either
> a MAC system or an integrity system. For instance, the new kernel
> MAY_OPENEXEC flag closes a major IMA measurement/appraisal interpreter
> integrity gap by bringing the ability
On Sun, Sep 08, 2019 at 08:05:45PM +0800, Changbin Du wrote:
> diff --git a/kernel/trace/trace.h b/kernel/trace/trace.h
> index 005f08629b8b..74162bc4024d 100644
> --- a/kernel/trace/trace.h
> +++ b/kernel/trace/trace.h
> @@ -941,11 +941,6 @@ static inline int ftrace_graph_addr(struct
> ftrace_gra
On Sun, Sep 08, 2019 at 10:46:01PM +0100, Al Viro wrote:
> On Tue, Sep 03, 2019 at 04:41:22PM +0800, kernel test robot wrote:
> > Greeting,
> >
> > FYI, we noticed a -23.7% regression of vm-scalability.median due to commit:
> >
> >
> > commit: 8bb3c61bafa8c1cd222ada602bb94ff23119e738 ("vfs: Conv
On Sat, Sep 7, 2019 at 2:01 PM SeongJae Park wrote:
>
> kunit wrapper script ('kunit.py') receives a sub-command (only 'run' for
> now) as its argument. If no sub-command is given, it prints help
> message and just quit. However, an example command in the kunit
> documentation for a verification
On 09/09/2019 00:30, Boris Ostrovsky wrote:
> On 9/8/19 5:11 PM, Igor Druzhinin wrote:
>> On 08/09/2019 19:28, Boris Ostrovsky wrote:
>>> On 9/6/19 7:00 PM, Igor Druzhinin wrote:
On 06/09/2019 23:30, Boris Ostrovsky wrote:
> Where is MCFG parsed? pci_arch_init()?
>> It happens twice:
>
On 9/8/19 5:11 PM, Igor Druzhinin wrote:
> On 08/09/2019 19:28, Boris Ostrovsky wrote:
>> On 9/6/19 7:00 PM, Igor Druzhinin wrote:
>>> On 06/09/2019 23:30, Boris Ostrovsky wrote:
Where is MCFG parsed? pci_arch_init()?
> It happens twice:
>>> 1) first time early one in pci_arch_init() that
> On 8 Sep 2019, at 22:59, Theodore Y. Ts'o wrote:
>
Hi Ted,
Thank you, for elaborating all this to me! I will try to limit my patches to
the staging tree, until I feel confident enough to tackle a real coding issue
in the kernel.
Thanks,
Sandro V
Hi Prakhar,
On Fri, 2019-09-06 at 16:56 -0700, prsriva wrote:
> On 8/30/19 5:11 PM, Thiago Jung Bauermann wrote:
> > Hello Prakhar,
> >
> > Answering this part from the cover letter:
> >
> >> The code is in most part same as powerpc, i want to get feedback as to
> >> how/correct way to refactor th
From: Sebastian Reichel
nvmem_cell_write's buf argument uses different types based on
the configuration of CONFIG_NVMEM. The function prototype for
enabled NVMEM uses 'void *' type, but the static dummy function
for disabled NVMEM uses 'const char *' instead. Fix the different
behaviour by always
On 9/6/19 1:30 PM, Jorge Ramirez-Ortiz wrote:
As per Documentation/process/submit-checklist.rst, when using a
facility #include the file that defines/declares that facility.
Don't depend on other header files pulling in ones that you use.
Correct, but then also don't include header files yo
On 9/6/19 1:30 PM, Jorge Ramirez-Ortiz wrote:
When an IRQ is present in the dts, the probe function shall fail if
the interrupt can not be registered.
The author intended differently, and did not want registration to fail
in this situation, following the logic that it is better to have a
stand
$1,000,000.00 dollars has been donated to you by Mavis L. Wanczyk who won
the Powerball Jackpot of $758.7 million Dollars. Contact her via Email:
maviswl...@gmail.com for more details
On Mon, Sep 09, 2019 at 12:09:57AM +0200, Mickaël Salaün wrote:
> >>> +rcu_read_lock();
> >>> +ptr = htab_map_lookup_elem(map, &inode);
> >>> +iput(inode);
Wait a sec. You are doing _what_ under rcu_read_lock()?
> >>> +if (IS_ERR(ptr)) {
> >>> +ret = PTR_ERR(ptr);
>
On Fri, Sep 06, 2019 at 04:01:26PM +0200, Peter Zijlstra wrote:
> On Fri, Sep 06, 2019 at 02:42:11PM +0200, Petr Mladek wrote:
> > 7. People would complain when continuous lines become less
> >reliable. It might be most visible when mixing backtraces
> >from all CPUs. Simple sorting by pre
On 31/07/2019 20:46, Mickaël Salaün wrote:
>
> On 27/07/2019 03:40, Alexei Starovoitov wrote:
>> On Sun, Jul 21, 2019 at 11:31:12PM +0200, Mickaël Salaün wrote:
>>> FIXME: 64-bits in the doc
>
> FYI, this FIXME was fixed, just not removed from this message. :)
>
>>>
>>> This new map store arb
On Tue, Sep 03, 2019 at 04:41:22PM +0800, kernel test robot wrote:
> Greeting,
>
> FYI, we noticed a -23.7% regression of vm-scalability.median due to commit:
>
>
> commit: 8bb3c61bafa8c1cd222ada602bb94ff23119e738 ("vfs: Convert ramfs, shmem,
> tmpfs, devtmpfs, rootfs to use the new mount API")
On Fri, Sep 06, 2019 at 02:06:14PM +0200, Nicolas Saenz Julienne wrote:
> @@ -430,7 +454,7 @@ void __init arm64_memblock_init(void)
>
> high_memory = __va(memblock_end_of_DRAM() - 1) + 1;
>
> - dma_contiguous_reserve(arm64_dma32_phys_limit);
> + dma_contiguous_reserve(arm64_dma_ph
On 08/09/2019 19:28, Boris Ostrovsky wrote:
> On 9/6/19 7:00 PM, Igor Druzhinin wrote:
>>
>> On 06/09/2019 23:30, Boris Ostrovsky wrote:
>>>
>>> Where is MCFG parsed? pci_arch_init()?
It happens twice:
>> 1) first time early one in pci_arch_init() that is arch_initcall - that
>> time pci_mmcfg
Dear Sir/Madam,
We are looking to buy your products and partner with your company, can
you please send us your Catalog or your website to learn more about your
products or prices list by email and if we can make some order with you
and start a long-term partnership. Can your company supply u
Hi Sandro,
It's not mentioned in the process documentation (but maybe we should
add this), is that it's up to individual maintainers about whether or
not whitespace cleanups are accepted outside of the staging tree.
That's because whitespace cleanups are a great "training wheel" for
newbies who a
So we probably didn't strictly need an rc8 this release, but with LPC
and the KS conference travel this upcoming week it just makes
everything easier.
And partly because of the extra week, we then had a few fixes that
maybe otherwise would have been delayed and marked for stable. The
most notable
Hi Luca, Jacopo, Wolfram, Peter,
On 09/01/2019 05:31 PM, jacopo mondi wrote:
> Hi Luca,
>thanks for keep pushing this series! I hope we can use part of this
> for the (long time) on-going GMSL work...
>
> I hope you will be patient enough to provide (another :) overview
> of this work during
On Sun, 8 Sep 2019, Vlastimil Babka wrote:
> > On Sat, 7 Sep 2019, Linus Torvalds wrote:
> >
> >>> Andrea acknowledges the swap storm that he reported would be fixed with
> >>> the last two patches in this series
> >>
> >> The problem is that even you aren't arguing that those patches should
> >>
On Sun, Sep 8, 2019 at 4:56 PM Maciej S. Szmigiero
wrote:
>
> On 08.09.2019 15:29, Vitaly Wool wrote:
> > z3fold_page_reclaim()'s retry mechanism is broken: on a second
> > iteration it will have zhdr from the first one so that zhdr
> > is no longer in line with struct page. That leads to crashes
add enable-gpios to describe HWEN pin
Signed-off-by: Andreas Kemnade
---
.../devicetree/bindings/leds/backlight/lm3630a-backlight.yaml | 4
1 file changed, 4 insertions(+)
diff --git
a/Documentation/devicetree/bindings/leds/backlight/lm3630a-backlight.yaml
b/Documentation/devicetree/bind
To be able to handle the HWEN pin of the lm3630a, add
an enable gpio to the driver and a property.
Tested on Kobo Clara HD
Andreas Kemnade (2):
backlight: lm3630a: add an enable gpio for the HWEN pin
dt-bindings: backlight: lm3630a: add enable_gpios
.../leds/backlight/lm3630a-backlight.yaml
For now just enable it in the probe function to allow i2c
access and disable it on remove. Disabling also means resetting
the register values to default.
Tested on Kobo Clara HD.
Signed-off-by: Andreas Kemnade
---
drivers/video/backlight/lm3630a_bl.c | 18 ++
1 file changed, 18
Hi!
> This adds a new function class_kobject_create_and_add() that creates a
> directory in the /sys/class/.
>
> This function is required to create the /sys/class/leds/triggers directory
> that contains all available LED triggers.
Lets not do this. With your fixes (1,2/5), we'll have reasonable
On Sat, Sep 7, 2019 at 10:42 AM Andy Shevchenko
wrote:
>
> On Fri, Aug 23, 2019 at 1:44 AM Rajat Jain wrote:
> >
> > On Thu, Jun 27, 2019 at 8:34 PM Rajat Jain wrote:
> > >
> > > Most modern platforms already have the ACPI device "INT33A1" that could
> > > be used to attach to the driver. Switch
1 - 100 of 523 matches
Mail list logo
