On Thu, Jul 2, 2020 at 8:06 PM Linus Torvalds
wrote:
> On Thu, Jul 2, 2020 at 9:51 AM Andreas Gruenbacher
> wrote:
> > Add an IOCB_NOIO flag that indicates to generic_file_read_iter that it
> > shouldn't trigger any filesystem I/O for the actual request or for
> > readahead. This allows to do
This patch fixes a bug which does not let FAN mode to be changed from
sysfs(pwm1_enable). i.e pwm1_enable can not be set to 3, it will always
remain at 0.
This is caused because the device driver handles the result of
"read_u8_from_i2c(client, REG_FAN_CONF1, _reg)" incorrectly. The
driver thinks
On 07/07/2020 15:50, Neil Armstrong wrote:
> The recent GCC compiler is very picky with the VD_H_START() and
> AFBC_DEC_PIXEL_BGN_H() macros, triggering a runtime assert error as:
>
> In function 'meson_overlay_setup_scaler_params',
> inlined from 'meson_overlay_atomic_update' at
>
On Fri, Jul 3, 2020 at 1:55 AM Amit Tomer wrote:
>
> On Fri, Jul 3, 2020 at 12:48 PM Amit Tomer wrote:
> >
> > Hi Rob,
> >
> >
> > > If you already ran 'make dt_binding_check' and didn't see the above
> > > error(s), then make sure dt-schema is up to date:
> > >
> > > pip3 install
On 7/7/20 5:38 AM, Andreas Grünbacher wrote:
> Am Mi., 24. Juni 2020 um 18:48 Uhr schrieb Jens Axboe :
>>
>> On 6/24/20 10:41 AM, Matthew Wilcox wrote:
>>> On Wed, Jun 24, 2020 at 09:35:19AM -0600, Jens Axboe wrote:
On 6/24/20 9:00 AM, Jens Axboe wrote:
> On 6/23/20 7:46 PM, Matthew
On 7/7/20 5:32 AM, Andreas Grünbacher wrote:
>> @@ -2131,6 +2166,11 @@ ssize_t generic_file_buffered_read(struct kiocb *iocb,
>> }
>>
>> readpage:
>> + if (iocb->ki_flags & IOCB_NOWAIT) {
>> + unlock_page(page);
>> +
Hi Akshu,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on pm/linux-next]
[also build test ERROR on linus/master v5.8-rc4 next-20200707]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use as documented
Kerneldoc expects struct documentation to start with "struct $NAME".
Fixes the following W=1 kernel build warning(s):
sound/soc/fsl/fsl_spdif.c:104: warning: cannot understand function prototype:
'struct fsl_spdif_priv '
Cc: Timur Tabi
Cc: Nicolin Chen
Cc: Xiubo Li
Cc: Fabio Estevam
Cc:
Ideally the author or someone 'in the know' should come back and
provide the remainder of the documentation. Until the kerneldoc
checkers have been satisfied, let's just demote the header to a
standard comment block.
Fixes the following W=1 kernel build warning(s):
sound/soc/samsung/pcm.c:127:
Looks as though the result of snd_soc_update_bits() has never been checked.
Fixes the following W=1 kernel build warning(s):
sound/soc/codecs/ak4458.c: In function ‘ak4458_set_dai_mute’:
sound/soc/codecs/ak4458.c:408:16: warning: variable ‘ret’ set but not used
[-Wunused-but-set-variable]
Two descriptions for 'soc' and 'regcache_srpc' were missing. Add them.
Fixes the following W=1 kernel build warning(s):
sound/soc/fsl/fsl_spdif.c:125: warning: Function parameter or member 'soc' not
described in 'fsl_spdif_priv'
sound/soc/fsl/fsl_spdif.c:125: warning: Function parameter or
This set is part of a larger effort attempting to clean-up W=1
kernel builds, which are currently overwhelmingly riddled with
niggly little warnings.
After these patches are applied, the build system no longer
complains about any W=0 nor W=1 level warnings in sound/soc,
when building for Arm.
No attempt has been made to document any of the demoted functions here.
Fixes the following W=1 kernel build warning(s):
sound/soc/fsl/fsl_asrc.c:44: warning: cannot understand function prototype:
'unsigned char input_clk_map_imx35[ASRC_CLK_MAP_LEN] = '
sound/soc/fsl/fsl_asrc.c:78: warning:
This is the only use of kerneldoc in the sourcefile and full
descriptions are not provided.
Fixes the following W=1 kernel build warning(s):
sound/soc/pxa/pxa-ssp.c:186: warning: Function parameter or member 'ssp' not
described in 'pxa_ssp_set_scr'
Cc: Daniel Mack
Cc: Haojian Zhuang
Cc:
Struct headers require a 'struct $NAME' title, all function parameters
require a description and need to be in the format '@.*:', else the
checker gets confused. Also demote one kerneldoc header where no effort
was made to document any of the function's params.
Fixes the following W=1 kernel
Property name descriptions need to match exactly.
Fixes the following W=1 kernel build warning(s):
sound/soc/sunxi/sun4i-spdif.c:178: warning: Function parameter or member
'reg_dac_txdata' not described in 'sun4i_spdif_quirks'
Cc: Maxime Ripard
Cc: Chen-Yu Tsai
Cc: Philipp Zabel
Cc: Andrea
Both issues are likely due to bitrot. Let's bring them up-to-date.
Fixes the following W=1 kernel build warning(s):
sound/soc/uniphier/aio-core.c:107: warning: Function parameter or member
'pll_id' not described in 'aio_chip_set_pll'
sound/soc/uniphier/aio-core.c:107: warning: Excess
No attempt has been made to document the demoted function here.
Fixes the following W=1 kernel build warning(s):
sound/soc/atmel/atmel-pcm-dma.c:55: warning: Function parameter or member
'ssc_sr' not described in 'atmel_pcm_dma_irq'
sound/soc/atmel/atmel-pcm-dma.c:55: warning: Function
On Tue, Jul 07, 2020 at 03:04:10PM +0200, Peter Zijlstra wrote:
> Anyway, let me muck around with that a bit.
How's this? it removes a level of indirection and a bunch of repetition.
It doesn't provide SEQCNT_LOCKTYPE_ZERO() for each LOCKTYPE, but you can
use this one macro for any LOCKTYPE.
No attempt has been made to document any of the demoted functions here.
Fixes the following W=1 kernel build warning(s):
sound/soc/fsl/fsl_ssi.c:380: warning: Function parameter or member 'irq' not
described in 'fsl_ssi_isr'
sound/soc/fsl/fsl_ssi.c:380: warning: Function parameter or member
Fixes the following W=1 kernel build warning(s):
sound/soc/codecs/wm8400.c:443:38: warning: ‘wm8400_dapm_rxvoice_controls’
defined but not used [-Wunused-const-variable=]
443 | static const struct snd_kcontrol_new wm8400_dapm_rxvoice_controls[] = {
| ^~~~
In file
Looks as though they've never been used.
Fixes the following W=1 kernel build warning(s):
In file included from sound/soc/codecs/rt5659.c:25:
In file included from sound/soc/codecs/rt5659.c:25:
sound/soc/codecs/rt5659.c:1232:2: warning: ‘rt5659_ad_monor_asrc_enum’ defined
but not used
Only 2 of the 3 source files which include this headerfile actually
reference 'uni_tdm_hw'. The other source file 'sti_uniperif.c' sees
as it as being unused. Mark it as __maybe_unused to show that this
behaviour is not only known, it's intentional.
Fixes the following W=1 kernel build
This is the only use of kerneldoc in the sourcefile and no
descriptions are provided.
Fixes the following W=1 kernel build warning(s):
sound/soc/soc-ac97.c:402: warning: Function parameter or member 'ops' not
described in 'snd_soc_set_ac97_ops_of_reset'
sound/soc/soc-ac97.c:402: warning:
This is the only use of kerneldoc in the sourcefile and no
descriptions are provided.
Fixes the following W=1 kernel build warning(s):
sound/soc/codecs/tlv320aic26.c:138: warning: Function parameter or member
'dai' not described in 'aic26_mute'
sound/soc/codecs/tlv320aic26.c:138: warning:
Fixes the following W=1 kernel build warning(s):
In file included from include/sound/tlv.h:10,
from sound/soc/codecs/jz4770.c:19:
sound/soc/codecs/jz4770.c:306:35: warning: ‘mic_boost_tlv’ defined but not
used [-Wunused-const-variable=]
306 | static const DECLARE_TLV_DB_SCALE(mic_boost_tlv,
No attempt has been made to document the demoted function here.
Fixes the following W=1 kernel build warning(s):
sound/soc/atmel/atmel_ssc_dai.c:892: warning: Function parameter or member
'ssc_id' not described in 'atmel_ssc_set_audio'
Cc: Codrin Ciubotariu
Cc: Nicolas Ferre
Cc: Alexandre
No attempt has been made to document either of the demoted functions here.
Fixes the following W=1 kernel build warning(s):
sound/soc/fsl/fsl_ssi_dbg.c:90: warning: Function parameter or member 'flag'
not described in 'SIER_SHOW'
sound/soc/fsl/fsl_ssi_dbg.c:90: warning: Function parameter or
Little or no attempt has been made to document any of the demoted functions
here.
Fixes the following W=1 kernel build warning(s):
sound/soc/codecs/rt5631.c:72: warning: Function parameter or member
'component' not described in 'rt5631_write_index'
sound/soc/codecs/rt5631.c:72: warning:
Looks like 'w' has remained unchecked since the driver's inception.
Fixes the following W=1 kernel build warning(s):
sound/soc/ti/omap-mcbsp-st.c: In function ‘omap_mcbsp_st_chgain’:
sound/soc/ti/omap-mcbsp-st.c:145:6: warning: variable ‘w’ set but not used
[-Wunused-but-set-variable]
Peter
Kerneldoc expects parameter documentation to be in the format '@.*: '.
If that convention is not followed, the kerneldoc checker gets confused.
Fixes the following W=1 kernel build warning(s):
sound/soc/codecs/da7210.c:985: warning: Function parameter or member
'codec_dai' not described in
Struct kerneldoc headers need to be prefixed with 'struct $NAME', else
the checker gets confused.
Fixes the following W=1 kernel build warning(s):
sound/soc/fsl/fsl-asoc-card.c:43: warning: cannot understand function
prototype: 'struct codec_priv '
sound/soc/fsl/fsl-asoc-card.c:60: warning:
On Tue, Jul 07, 2020 at 03:37:14PM +0100, Lee Jones wrote:
> This set is part of a larger effort attempting to clean-up W=1
> kernel builds, which are currently overwhelmingly riddled with
> niggly little warnings.
Copying in Pierre again.
signature.asc
Description: PGP signature
Fixes the following W=1 kernel build warning(s):
sound/soc/qcom/qdsp6/q6asm.c:924: warning: Function parameter or member
'codec_profile' not described in 'q6asm_open_write'
Cc: Patrick Lai
Cc: Banajit Goswami
Cc: Srinivas Kandagatla
Cc: Vinod Koul
Signed-off-by: Lee Jones
---
Ideally the author or someone 'in the know' should come back and
provide the remainder of the documentation. Until the kerneldoc
checkers have been satisfied, let's just demote the header to a
standard comment block.
Fixes the following W=1 kernel build warning(s):
Fixes the following W=1 kernel build warning(s):
sound/soc/fsl/fsl_esai.c:86: warning: Function parameter or member 'tx_mask'
not described in 'fsl_esai'
sound/soc/fsl/fsl_esai.c:86: warning: Function parameter or member 'rx_mask'
not described in 'fsl_esai'
Cc: Timur Tabi
Cc: Nicolin Chen
When documenting structure properties, they must match the names exactly.
Fixes the following W=1 kernel build warning(s):
sound/soc/samsung/spdif.c:89: warning: Function parameter or member
'saved_clkcon' not described in 'samsung_spdif_info'
sound/soc/samsung/spdif.c:89: warning: Function
Looks like these have been unchecked since the driver's inception in 2012.
Fixes the following W=1 kernel build warning(s):
sound/soc/ux500/ux500_msp_i2s.c: In function ‘flush_fifo_rx’:
sound/soc/ux500/ux500_msp_i2s.c:398:6: warning: variable ‘reg_val_DR’ set but
not used
On Mon, Jul 6, 2020 at 12:45 PM Ricardo Rivera-Matos
wrote:
>
> Rob
>
> On 7/2/20 3:53 PM, Rob Herring wrote:
> > On Wed, 01 Jul 2020 16:10:42 -0500, Ricardo Rivera-Matos wrote:
> >> From: Dan Murphy
> >>
> >> Convert the battery.txt file to yaml and fix up the examples.
> >>
> >> Signed-off-by:
On Tue, Jul 7, 2020 at 4:36 AM Robin Murphy wrote:
>
> On 2020-06-26 21:04, Jordan Crouse wrote:
> > Add support to create a io-pgtable for use by targets that support
> > per-instance pagetables. In order to support per-instance pagetables the
> > GPU SMMU device needs to have the
On 19.06.2020 12:36, Marek Szyprowski wrote:
> Replace the current hand-crafted code for extracting pages and DMA
> addresses from the given scatterlist by the much more robust
> code based on the generic scatterlist iterators and recently
> introduced sg_table-based wrappers. The resulting code
Andy Duan writes:
> From: Sergey Organov Sent: Monday, July 6, 2020 10:26 PM
>> Code of the form "if(x) x = 0" replaced with "x = 0".
>>
>> Code of the form "if(x == a) x = a" removed.
>>
>> Signed-off-by: Sergey Organov
>> ---
>> drivers/net/ethernet/freescale/fec_ptp.c | 4 +---
>> 1 file
The function quirks_param_set() takes as argument a const char* pointer
to the new value of the usbcore.quirks parameter. It then casts this
pointer to a non-const char* pointer and passes it to the strsep()
function, which overwrites the value.
Fix this by creating a copy of the value using
So far, gfs2 has taken the inode glocks inside the ->readpage and
->readahead address space operations. Since commit d4388340ae0b ("fs:
convert mpage_readpages to mpage_readahead"), gfs2_readahead is passed
the pages to read ahead locked. With that, the current holder of the
inode glock may be
Add an IOCB_NOIO flag that indicates to generic_file_read_iter that it
shouldn't trigger any filesystem I/O for the actual request or for
readahead. This allows to do tentative reads out of the page cache as
some filesystems allow, and to take the appropriate locks and retry the
reads only if the
In the previous version, we could end up calling ->readpage without
checking IOCB_NOIO.
Andreas Gruenbacher (2):
fs: Add IOCB_NOIO flag for generic_file_read_iter
gfs2: Rework read and page fault locking
fs/gfs2/aops.c | 45 +--
fs/gfs2/file.c |
Hi Jason,
On 7/7/2020 3:17 PM, Jason Wang wrote:
>
> On 2020/7/6 下午5:32, Kishon Vijay Abraham I wrote:
>> Hi Jason,
>>
>> On 7/3/2020 12:46 PM, Jason Wang wrote:
>>> On 2020/7/2 下午9:35, Kishon Vijay Abraham I wrote:
Hi Jason,
On 7/2/2020 3:40 PM, Jason Wang wrote:
> On
From: SeongJae Park
DAMON[1] programming interface users can extend DAMON for any address space by
configuring the address-space specific low level primitives with appropriate
ones including their own implementations. However, because the implementation
for the virtual address space is only
From: SeongJae Park
Some users would want to monitor only a part of the entire virtual
memory address space. The '->init_target_regions' callback is therefore
provided, but only programming interface can use it.
For the reason, this commit introduces a new debugfs file,
'init_region'. Users
On Tue, Jul 7, 2020 at 1:05 PM Zhang, Qiang wrote:
> Thanks for you reply Pter, if the patch was add , like you said there are
> more work to do. so need remove the patch from -mm tree.
Please do, I spent some time to understand why I got it (I admit, that
most of it was direct investigation
From: SeongJae Park
This commit updates the damon user space tool to support the initial
monitoring target regions specification.
Signed-off-by: SeongJae Park
---
tools/damon/_damon.py | 39 +++
tools/damon/record.py | 12 +++-
On Tue, Jul 07, 2020 at 09:41:47AM -0400, Steven Rostedt wrote:
> On Tue, 7 Jul 2020 01:54:23 -0700
> Kees Cook wrote:
>
> > "I will whitelist the syscall" -- sounds correct to me (same for
> > "it is whitelisted" or "it is in whitelisting mode").
> >
> > "I will allow-list the syscall" --
From: SeongJae Park
This commit adds more test cases for the new feature, 'init_regions'.
Signed-off-by: SeongJae Park
---
mm/damon-test.h | 53 +
1 file changed, 53 insertions(+)
diff --git a/mm/damon-test.h b/mm/damon-test.h
index
On 7/7/20 7:52 AM, Christian Brauner wrote:
On Tue, Jul 07, 2020 at 06:19:34AM -0400, Paolo Bonzini wrote:
Calling ksft_exit_* results in executing fewer tests than planned, which
is wrong for ksft_exit_skip or suboptimal (because it results in a bail
out) for ksft_exit_fail_msg.
Using
From: SeongJae Park
Now the regions can be explicitly set as users want. Therefore checking
the number of gaps doesn't make sense. Remove the condition.
Signed-off-by: SeongJae Park
---
tools/testing/selftests/damon/_chk_record.py | 6 --
1 file changed, 6 deletions(-)
diff --git
From: SeongJae Park
This commit exports the three essential functions for ramp walk,
'page_lock_anon_vma_read()', 'rmap_walk()', and 'page_rmapping()', to
GPL modules. Those will be used by DAMON for the physical memory
address based access monitoring in the following commit.
Signed-off-by:
From: SeongJae Park
This commit implements the four callbacks (->init_target_regions,
->update_target_regions, ->prepare_access_check, and ->check_accesses)
for the basic access monitoring of the physical memory address space.
By setting the callback pointers to point those, users can easily
From: SeongJae Park
This commit documents the 'initial_regions' feature.
Signed-off-by: SeongJae Park
---
Documentation/admin-guide/mm/damon/usage.rst | 35
1 file changed, 35 insertions(+)
diff --git a/Documentation/admin-guide/mm/damon/usage.rst
From: SeongJae Park
This commit makes the debugfs interface to support the physical memory
monitoring, in addition to the virtual memory monitoring.
Users can do the physical memory monitoring by writing a special
keyword, 'paddr\n' to the 'pids' debugfs file. Then, DAMON will check
the
From: SeongJae Park
This commit allows users to record the data accesses on physical memory
address space by passing 'paddr' as target to 'damo-record'. If the
init regions are given, the regions will be monitored. Else, it will
monitor biggest conitguous 'System RAM' region in '/proc/iomem'
On Tue, Jul 07, 2020 at 04:02:44PM +0200, Pali Rohár wrote:
> On Tuesday 07 July 2020 14:53:11 Lorenzo Pieralisi wrote:
> > On Fri, Jun 19, 2020 at 12:56:18PM +0200, Pali Rohár wrote:
> > > Hello Lorenzo! Could you please review this patch?
> > >
> > > On Monday 01 June 2020 15:03:15 Pali Rohár
From: SeongJae Park
This commit updates the DAMON user space tool (damo-record) for NUMA
specific physical memory monitoring. With this change, users can
monitor accesses to physical memory of specific NUMA node.
Signed-off-by: SeongJae Park
---
tools/damon/_paddr_layout.py | 158
From: SeongJae Park
This commit adds description for the physical memory monitoring usage in
the DAMON document.
Signed-off-by: SeongJae Park
---
Documentation/admin-guide/mm/damon/faq.rst| 7 ++-
Documentation/admin-guide/mm/damon/index.rst | 1 -
On Tue, Jul 07, 2020 at 10:43:10AM +1000, Alexey Kardashevskiy wrote:
> Any luck there? I'd really like to cross this off my todo list :) Thanks,
We had another incident with new net code poking into dma internals
blocking this series. That is now sorted out, so the series is back
on track.
Hi,
On Mon, Jun 22, 2020 at 7:49 AM Douglas Anderson wrote:
>
> From: Ravi Kumar Bokka
>
> This patch adds support for blowing fuses to the qfprom driver if the
> required properties are defined in the device tree.
>
> Signed-off-by: Ravi Kumar Bokka
> Signed-off-by: Douglas Anderson
> ---
>
On 07.07.2020 17:23, Jiri Olsa wrote:
> On Tue, Jul 07, 2020 at 04:24:28PM +0300, Alexey Budankov wrote:
>>
>> On 07.07.2020 16:14, Jiri Olsa wrote:
>>> On Tue, Jul 07, 2020 at 04:07:42PM +0300, Alexey Budankov wrote:
On 06.07.2020 22:34, Jiri Olsa wrote:
> On Mon, Jul 06, 2020 at
On 07/07/2020 15:52, Doug Anderson wrote:
Given that I've resolved previous feedback, I've been assuming that
the series looks fine and we're sitting waiting for Rob Herring's
blessings on the bindings before landing. Is that correct?
That's correct!
--srini
Hi Andrew,
On Tue, Jul 07, 2020 at 04:19:18PM +0200, Andrew Lunn wrote:
> On Mon, Jul 06, 2020 at 08:13:31PM +0200, Maxime Ripard wrote:
> > I came across an issue today on an Allwinner board, but I believe it's a
> > core issue.
> >
> > That board is using the stmac driver together with a phy
I would like to point out that the subject is misleading: This is not
an ABI change. It fixes the contents of the __rseq_abi TLS variable
(as glibc calls it), but that's it.
(Sorry, I should have mentioned this earlier.)
Hi Steve and Tzvetomir,
On Fri, Jul 3, 2020 at 3:57 AM Steven Rostedt wrote:
>
> From: "Tzvetomir Stoyanov (VMware)"
>
> Add the API function tep_load_plugins_hook() to the traceevent API to allow
> tools a common method to load in the plugins that are part of the lib
> traceevent library.
>
>
On 7/7/20 7:27 AM, Vishwas M wrote:
> This patch fixes a bug which does not let FAN mode to be changed from
> sysfs(pwm1_enable). i.e pwm1_enable can not be set to 3, it will always
> remain at 0.
>
> This is caused because the device driver handles the result of
> "read_u8_from_i2c(client,
On Tue, Jul 7, 2020 at 7:25 AM Rob Clark wrote:
>
> On Tue, Jul 7, 2020 at 4:34 AM Robin Murphy wrote:
> >
> > On 2020-06-26 21:04, Jordan Crouse wrote:
> > > Allow a io-pgtable implementation to skip TLB operations by checking for
> > > NULL pointers in the helper functions. It will be up to to
Hi Lorenzo,
On 7/7/20 5:05 PM, Lorenzo Pieralisi wrote:
> On Mon, Jun 15, 2020 at 11:05:56PM +0200, Ansuel Smith wrote:
>> This contains multiple fix for PCIe qcom driver.
>> Some optional reset and clocks were missing.
>> Fix a problem with no PARF programming that cause kernel lock on load.
>>
Replace the existing ringbuffer usage and implementation with
lockless ringbuffer usage. Even though the new ringbuffer does not
require locking, all existing locking is left in place. Therefore,
this change is purely replacing the underlining ringbuffer.
Changes that exist due to the ringbuffer
Hello,
Here is a v4 for the first series to rework the printk
subsystem. The v3 is here [0]. This first series
only replaces the existing ringbuffer implementation. No locking
is removed. The semantics/behavior of printk are kept the same
except for a minor optimization that is reverted (patch
The existing macro VMCOREINFO_OFFSET() can't be used for structures
declared via typedef because "struct" is not part of type definition.
Create another macro for this purpose.
Signed-off-by: John Ogness
Acked-by: Baoquan He
Acked-by: Sergey Senozhatsky
Reviewed-by: Petr Mladek
---
This reverts commit 3ac37a93fa9217e576bebfd4ba3e80edaaeb2289.
This optimization will not apply once the transition to a lockless
printk is complete. Rather than porting this optimization through
the transition only to remove it anyway, just revert it now to
simplify the transition.
Introduce a multi-reader multi-writer lockless ringbuffer for storing
the kernel log messages. Readers and writers may use their API from
any context (including scheduler and NMI). This ringbuffer will make
it possible to decouple printk() callers from any context, locking,
or console constraints.
From: Colin Ian King
Fix smatch warning:
drivers/scsi/lpfc/lpfc_sli.c:15156 lpfc_cq_poll_hdler() warn: inconsistent
indenting
Signed-off-by: Colin Ian King
---
drivers/scsi/lpfc/lpfc_sli.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/scsi/lpfc/lpfc_sli.c
On Fri, Jul 03, 2020 at 02:47:09PM +0900, Namhyung Kim wrote:
> Hello,
>
> On Sat, Jun 27, 2020 at 10:37 PM Changbin Du wrote:
> >
> > The '-g/-G' options have already implied function_graph tracer should be
> > used instead of function tracer. So the extra option '--tracer' can be
> > killed.
>
On 19.06.2020 12:36, Marek Szyprowski wrote:
> The Documentation/DMA-API-HOWTO.txt states that the dma_map_sg() function
> returns the number of the created entries in the DMA address space.
> However the subsequent calls to the dma_sync_sg_for_{device,cpu}() and
> dma_unmap_sg must be called
On 07.07.2020 16:30, Andrzej Hajda wrote:
> On 19.06.2020 12:36, Marek Szyprowski wrote:
>> It is a common operation done by DRM drivers to check the contiguity
>> of the DMA-mapped buffer described by a scatterlist in the
>> sg_table object. Let's add a common helper for this operation.
>>
>>
On Fri, Jul 3, 2020 at 3:57 AM Steven Rostedt wrote:
>
> From: "Tzvetomir Stoyanov (VMware)"
>
> Add tep_plugin_add_option() and tep_plugin_print_options() to lib traceevent
> library that allows plugins to have their own options. For example, the
> function plugin by default does not print the
On 07.07.2020 11:35, Andrzej Hajda wrote:
> Hi,
>
> On 19.06.2020 12:36, Marek Szyprowski wrote:
>> Use common helper for checking the contiguity of the imported dma-buf.
>>
>> Signed-off-by: Marek Szyprowski
Just fixing my signature :)
Reviewed-by: Andrzej Hajda
Regards
Andrzej
On 07.07.2020 11:40, Andrzej Hajda wrote:
> On 19.06.2020 12:36, Marek Szyprowski wrote:
>> The Documentation/DMA-API-HOWTO.txt states that the dma_map_sg() function
>> returns the number of the created entries in the DMA address space.
>> However the subsequent calls to the
On Fri, Jul 3, 2020 at 3:57 AM Steven Rostedt wrote:
>
> From: "Tzvetomir Stoyanov (VMware)"
>
> Implement new traceevent plugin API, which can be used to add new plugins
> directories:
> enum tep_plugin_load_priority {
> TEP_PLUGIN_FIRST,
> TEP_PLUGIN_LAST,
> };
> int
Add jump-label implementation based on the ARM64 version.
Tested on the HiFive Unleashed board.
Signed-off-by: Emil Renner Berthing
---
Changes since RFC:
- Use RISCV_PTR and RISCV_LGPTR macros to match struct jump_table
also in 32bit kernels.
- Remove unneeded branch ? 1 : 0, thanks Björn
-
On Tue, Jul 7, 2020 at 5:03 PM Sungbo Eo wrote:
> On 20. 7. 6. 오후 9:00, Andy Shevchenko wrote:
...
> But I don't really understand what mutex does here. The driver does not
> need consecutive commands, it only sends/receives only one byte at a
> time. And AFAIK each i2c_smbus function is
On Tue, Jul 7, 2020 at 5:34 AM Robin Murphy wrote:
>
> On 2020-06-26 21:04, Jordan Crouse wrote:
> > Support auxiliary domains for arm-smmu-v2 to initialize and support
> > multiple pagetables for a single SMMU context bank. Since the smmu-v2
> > hardware doesn't have any built in support for
On Fri, Jul 3, 2020 at 3:57 AM Steven Rostedt wrote:
>
> From: "Tzvetomir Stoyanov (VMware)"
>
> The printk format specifiers used in event's print format files extend
> the standard printf formats. There are a lot of new options related to
> printing pointers and kernel specific structures.
From: Anand Jain
[ Upstream commit 3752d22fcea160cc2493e34f5e0e41cdd7fdd921 ]
This patch deletes local variable disk_num_bytes as its value
is same as num_bytes in the function cow_file_range().
Signed-off-by: Anand Jain
Reviewed-by: Nikolay Borisov
Reviewed-by: David Sterba
Signed-off-by:
From: Chu Lin
[ Upstream commit 016983d138cbe99a5c0aaae0103ee88f5300beb3 ]
Per the datasheet for max6697, OVERT mask and ALERT mask are different.
For example, the 7th bit of OVERT is the local channel but for alert
mask, the 6th bit is the local channel. Therefore, we can't apply the
same mask
From: Chris Packham
[ Upstream commit cd217f2300793a106b49c7dfcbfb26e348bc7593 ]
The PCA9665 datasheet says that I2CSTA = 78h indicates that SCL is stuck
low, this differs to the PCA9564 which uses 90h for this indication.
Treat either 0x78 or 0x90 as an indication that the SCL line is stuck.
From: Misono Tomohiro
[ Upstream commit 8b97f9922211c44a739c5cbd9502ecbb9f17f6d1 ]
Although it rarely happens, we should call free_capabilities()
if error happens after read_capabilities() to free allocated strings.
Fixes: de584afa5e188 ("hwmon driver for ACPI 4.0 power meters")
Signed-off-by:
From: Shile Zhang
[ Upstream commit 975e155ed8732cb81f55c021c441ae662dd040b5 ]
We added the 'sched_rr_timeslice_ms' SCHED_RR tuning knob in this commit:
ce0d30ae ("sched/rt: Add a tuning knob to allow changing SCHED_RR
timeslice")
... which name suggests to users that it's in
From: Qian Cai
[ Upstream commit a68ee0573991e90af2f1785db309206408bad3e5 ]
There is no need to copy SLUB_STATS items from root memcg cache to new
memcg cache copies. Doing so could result in stack overruns because the
store function only accepts 0 to clear the stat and returns an error for
From: Paul Aurich
commit cc15461c73d7d044d56c47e869a215e49bd429c8 upstream.
Ensure multiuser SMB3 mounts use encryption for all users' tcons if the
mount options are configured to require encryption. Without this, only
the primary tcon and IPC tcons are guaranteed to be encrypted. Per-user
From: Vasily Averin
Could you please push this patch into stable@?
it fixes memory corruption in kernels v3.5 .. v4.10
Lost .data_len definition leads to write beyond end of
struct nf_ct_h323_master. Usually it corrupts following
struct nf_conn_nat, however if nat is not loaded it corrupts
From: Greg Kroah-Hartman
This reverts commit 02c56650f3c118d3752122996d96173d26bb13aa which is
commit f0bd62b64016508938df9babe47f65c2c727d25c upstream.
It causes a number of reported issues and a fix for it has not hit
Linus's tree yet. Revert this to resolve those problems.
Cc: Alexander
From: Hugh Dickins
[ Upstream commit 243bce09c91b0145aeaedd5afba799d81841c030 ]
Chris Murphy reports that a slightly overcommitted load, testing swap
and zram along with i915, splats and keeps on splatting, when it had
better fail less noisily:
gnome-shell: page allocation failure: order:0,
501 - 600 of 1789 matches
Mail list logo
