Resources modeled as power domains in linux kernel can be used to warm the
SoC(eg. mx power domain on sdm845). To support this feature, introduce a
generic power domain warming device driver that can be plugged into the
thermal framework (The thermal framework itself requires further
modifiction
Certain resources modeled as a generic power domain in linux kernel can be
used to warm up the SoC (mx power domain on sdm845) if the temperature
falls below certain threshold. These power domains can be considered as
thermal warming devices. (opposite of thermal cooling devices).
In kernel,
This patch series converts i.MX and MXS mmc binding to json-schema,
fix some minor issues in original binding doc, such as node name should be
'mmc',
compatible name for i.MX27, reg/interrupts should be required properties etc..
Compared to V1, this patch series adds "unevaluatedProperties:
Convert the MXS MMC binding to DT schema format using json-schema
Signed-off-by: Anson Huang
---
Changes since V1:
- add "unevaluatedProperties: false".
---
Documentation/devicetree/bindings/mmc/mxs-mmc.txt | 27 --
Documentation/devicetree/bindings/mmc/mxs-mmc.yaml | 58
Convert the i.MX ESDHC binding to DT schema format using json-schema
Signed-off-by: Anson Huang
---
Changes since V1:
- add "unevaluatedProperties: false".
---
.../devicetree/bindings/mmc/fsl-imx-esdhc.txt | 67 ---
.../devicetree/bindings/mmc/fsl-imx-esdhc.yaml | 124
Convert the i.MX MMC binding to DT schema format using json-schema
Signed-off-by: Anson Huang
---
Changes since V1:
- add "unevaluatedProperties: false".
---
.../devicetree/bindings/mmc/fsl-imx-mmc.txt| 23 --
.../devicetree/bindings/mmc/fsl-imx-mmc.yaml | 53
Convert the i.MXDI RTC binding to DT schema format using json-schema
Signed-off-by: Anson Huang
---
Changes since V1:
- add "additionalProperties: false".
---
.../devicetree/bindings/rtc/imxdi-rtc.txt | 20 --
.../devicetree/bindings/rtc/imxdi-rtc.yaml | 44
On Thu, Jun 4, 2020 at 3:44 AM Kees Cook wrote:
>
> On Thu, Jun 04, 2020 at 03:23:28AM +0200, Sedat Dilek wrote:
> > what is the base for your patchset?
>
> Hi! This was actually on Linus's latest tree (which is basically -next),
> mostly because I figured this might be a bit of an RFC but if it
On Wed, 2020-06-03 at 18:40 -0700, Kees Cook wrote:
> On Wed, Jun 03, 2020 at 05:02:29PM -0700, Joe Perches wrote:
> > On Wed, 2020-06-03 at 16:32 -0700, Kees Cook wrote:
> > > Using uninitialized_var() is dangerous as it papers over real bugs[1]
> > > (or can in the future), and suppresses
On Thu, Jun 04, 2020 at 03:23:28AM +0200, Sedat Dilek wrote:
> what is the base for your patchset?
Hi! This was actually on Linus's latest tree (which is basically -next),
mostly because I figured this might be a bit of an RFC but if it was
clean enough, it might actually make the merge window (I
According to the datasheet of pl330:
Example 2-1 Using DMAGO with the debug instruction registers
1. Create a program for the DMA channel
2. Store the program in a region of system memory
3. Poll the DBGSTATUS Register to ensure that the debug is idle
4. Write to the DBGINST0 Register
5. Write
Convert the i.MX7ULP clock binding to DT schema format using json-schema,
the original binding doc is actually for two clock modules(SCG and PCC),
so split it to two binding docs, and the MPLL(mipi PLL) is NOT supposed
to be in clock module, so remove it from binding doc as well.
Signed-off-by:
Convert the qoriq thermal binding to DT schema format using json-schema
Signed-off-by: Anson Huang
---
Changes since V4:
- add "additionalProperties: false"
---
.../devicetree/bindings/thermal/qoriq-thermal.txt | 71 -
.../devicetree/bindings/thermal/qoriq-thermal.yaml |
On Wed, Jun 03, 2020 at 05:02:29PM -0700, Joe Perches wrote:
> On Wed, 2020-06-03 at 16:32 -0700, Kees Cook wrote:
> > Using uninitialized_var() is dangerous as it papers over real bugs[1]
> > (or can in the future), and suppresses unrelated compiler warnings
> > (e.g. "unused variable"). If the
On Wed, Jun 03, 2020 at 07:28:53AM -0700, Andi Kleen wrote:
> > Its time cost is about 800 nanoseconds on a 2C/4T platform and
> > 2~3 microseconds on a 2S/36C/72T server in normal case, and in
> > worst case where vm_committed_as's spinlock is under severe
> > contention, it costs 30~40
On 2020/6/4 4:33, Sean Christopherson wrote:
Unconditionally return true when querying the validity of
MSR_IA32_PERF_CAPABILITIES so as to defer the validity check to
intel_pmu_{get,set}_msr(), which can properly give the MSR a pass when
the access is initiated from host userspace.
Regardless
Hi Rafael,
Thanks for your reply !
On 2020/6/3 21:39, Rafael J. Wysocki wrote:
> On Wed, Jun 3, 2020 at 9:52 AM Viresh Kumar wrote:
>>
>> On 02-06-20, 11:34, Xiongfeng Wang wrote:
>>> Hi Viresh,
>>>
>>> Sorry to disturb you about another problem as follows.
>>>
>>> CPPC use the increment of
Hi,
On 2020-06-03 19:04:17 -0600, Jens Axboe wrote:
> > The workload that triggers the bug within a few seconds is postgres
> > doing a parallel sequential scan of a large table (and aggregating the
> > data, but that shouldn't matter). In the triggering case that boils down
> > to 9 processes
Hi all,
On Tue, 2 Jun 2020 12:09:57 +1000 Stephen Rothwell
wrote:
>
> Hi all,
>
> Today's linux-next merge of the net-next tree got a conflict in:
>
> Documentation/devicetree/bindings/arm/mediatek/mediatek,pericfg.txt
>
> between commit:
>
> 7b9e111a5216 ("dt-bindings: clock: mediatek:
Hi David,
On Mon, 1 Jun 2020 20:30:34 -0600 David Ahern wrote:
>
> On 6/1/20 5:20 PM, Stephen Rothwell wrote:
> > Hi Dave,
> >
> > On Mon, 11 May 2020 13:00:15 +1000 Stephen Rothwell
> > wrote:
> >>
> >> Today's linux-next merge of the ipsec-next tree got conflicts in:
> >>
> >>
在 2020/6/3 23:33, Josh Poimboeuf 写道:
On Wed, Jun 03, 2020 at 10:06:07PM +0800, Wangshaobo (bobo) wrote:
To be honest, I don't remember what I meant by sibling calls. They
don't even leave anything on the stack.
For noreturns, the code might be laid out like this:
func1:
...
On Tue, Jun 02, 2020 at 06:10:41PM -0700, Sargun Dhillon wrote:
> Previously there were two chunks of code where the logic to receive file
> descriptors was duplicated in net. The compat version of copying
> file descriptors via SCM_RIGHTS did not have logic to update cgroups.
> Logic to change
On Thu, Jun 4, 2020 at 1:32 AM Kees Cook wrote:
>
> Using uninitialized_var() is dangerous as it papers over real bugs[1]
> (or can in the future), and suppresses unrelated compiler warnings
> (e.g. "unused variable"). If the compiler thinks it is uninitialized,
> either simply initialize the
On Wed, Jun 3, 2020 at 6:11 PM maobibo wrote:
>
> On architectures that manage the access bit in hardware, access bit is
> set at the beginning even if there is no memory access. On MIPS system
> access bit is not set at the beginning, it is set in page fault handling.
I had a hard time parsing
Hi all,
On Tue, 2 Jun 2020 12:17:35 +1000 Stephen Rothwell
wrote:
>
> Hi all,
>
> After merging the net-next tree, today's linux-next build (powerpc
> ppc64_defconfig) produced this warning:
>
> drivers/net/ethernet/chelsio/cxgb4/cxgb4_uld.c:666:13: warning:
> 'cxgb4_uld_in_use' defined but
On Fri, 29 May 2020, WANG Xuerui wrote:
> On 2020/5/29 17:29, yuanjunqing wrote:
>
> >> diff --git a/arch/mips/kernel/mcount.S b/arch/mips/kernel/mcount.S
> >> index cff52b283e03..cd5545764e5f 100644
> >> --- a/arch/mips/kernel/mcount.S
> >> +++ b/arch/mips/kernel/mcount.S
> >> @@ -87,8 +87,15
I test linux next kernel atomisp driver,
i have RIP: 0010:gmin_subdev_add.cold+0x318/0x327
[atomisp_gmin_platform] problem.
<4>[ 14.682805] atomisp_gmin_platform: module is from the staging
directory, the quality is unknown, you have been warned.
<4>[ 14.689979] atomisp_ov2680: module is
On Wed, Jun 03, 2020 at 05:13:36PM -0700, Linus Torvalds wrote:
> On Wed, Jun 3, 2020 at 4:24 PM Christian Brauner
> wrote:
> >
> > Ok, here's what I have. Does the below look somewhat sane?
>
> Probably. Needs lots of testing. But this one looks wrong:
Right, there's a patch for a test-suite
On 06/04/2020 05:00 AM, Linus Torvalds wrote:
> On Tue, Jun 2, 2020 at 5:55 AM Thomas Bogendoerfer
> wrote:
>>
>> Bibo Mao (4):
>> mm/memory.c: Add memory read privilege on page fault handling
>
> Hmm. That's a horribly named commit, but can you clarify why this
> didn't just use the
On Thu, Jun 4, 2020 at 2:59 AM Arnd Bergmann wrote:
>
> On Wed, Jun 3, 2020 at 7:04 PM Rich Felker wrote:
> > On Wed, Jun 03, 2020 at 08:49:54AM -0500, Rob Landley wrote:
> > > make ARCH=$i distclean defconfig headers_install \
> > >
> > > On the bright side, the resulting fruitbasket.tar.xz
On 6/3/20 6:59 PM, Andres Freund wrote:
> Hi,
>
> I was trying to benchmark the benefits of this for the io_uring using
> postgres I am working on. The initial results where quite promising
> (reducing cpu usage significantly, to lower than non-uring sync io). But
> unfortunately trying another
On Wed, Jun 03, 2020 at 11:54:14PM +0200, Roelof Berg wrote:
> Corrected the MAC_CR configuration bits for 1 GBit operation. The data
> sheet allows MAC_CR(2:1) to be 10 and also 11 for 1 GBit/s speed, but
> only 10 works correctly.
>
> Devices tested:
> Microchip Lan7431, fixed-phy mode
>
The mm-of-the-moment snapshot 2020-06-03-17-54 has been uploaded to
http://www.ozlabs.org/~akpm/mmotm/
mmotm-readme.txt says
README for mm-of-the-moment:
http://www.ozlabs.org/~akpm/mmotm/
This is a snapshot of my -mm patch queue. Uploaded at random hopefully
more than once a week.
You
Hi Oliver,
Sorry for the late reply. I totally lost track of this thread. :/
Please, see my comments below...
On 5/12/20 08:30, Oliver Hartkopp wrote:
>
>
> On 2020-05-07 20:51, Gustavo A. R. Silva wrote:
>> The current codebase makes use of the zero-length array language
>> extension to the
Hi Kees,
On Thu, Jun 4, 2020 at 1:32 AM Kees Cook wrote:
>
> Using uninitialized_var() is dangerous as it papers over real bugs[1]
> (or can in the future), and suppresses unrelated compiler warnings
> (e.g. "unused variable"). If the compiler thinks it is uninitialized,
> either simply
On 6/3/20 4:25 PM, Valentin Schneider wrote:
On 03/06/20 20:58, Russell King - ARM Linux admin wrote:
On Wed, Jun 03, 2020 at 09:24:56PM +0200, Vincent Guittot wrote:
On Wed, 3 Jun 2020 at 20:45, Russell King - ARM Linux admin
wrote:
It's a start. I'm still wondering whether I should
The pull request you sent on Wed, 3 Jun 2020 20:31:27 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git uaccess.comedi
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/2e63f6ce7ed2c4ff83ba30ad9ccad422289a6c63
Thank you!
--
Deet-doot-dot, I am a bot.
The pull request you sent on Wed, 3 Jun 2020 20:26:15 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.splice
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/ae03c53d005ef8a1e0253ad67b7b62103ea1fae6
Thank you!
--
Deet-doot-dot, I am a bot.
On Wed, 2020-06-03 at 16:19 -0700, Kees Cook wrote:
> My codespell dictionary has a lot of capitalized words. For example:
>
> MSDOS->MS-DOS
>
> Since checkpatch uses case-insensitive matching, I get an undefined
> variable warning and then empty suggestions for things like this:
>
> Use of
On Thu Jun 04 20, Lu Baolu wrote:
Hi Joerg,
On 6/2/20 5:26 PM, Joerg Roedel wrote:
Hi,
two small patches to move the Intel and AMD IOMMU drivers into their own
subdirectory under drivers/iommu/ to make the file structure a bit less
cluttered.
Does the MAINTAINERS file need to update?
Best
On 6/3/20 6:23 PM, Thomas Gleixner wrote:
kernel test robot writes:
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/l...@lists.01.org
#!/bin/bash
kernel=$1
initrd=yocto-x86_64-trinity.cgz
wget --no-clobber
On Wed, Jun 03, 2020 at 01:56:20PM -0700, James Bottomley wrote:
> The store of state_in_sysfs is already done in kobject_add_internal().
> It's an existing flag people already use to tell if the kobject has
> been exposed in sysfs. However, it's set after the sysfs directory
> creation
Hi--
Here are a few comments for you.
On 5/26/20 4:03 AM, Emanuele Giuseppe Esposito wrote:
> Html docs for a complete documentation of the stats_fs API,
> filesystem and usage.
>
> Signed-off-by: Emanuele Giuseppe Esposito
> ---
> Documentation/filesystems/index.rst| 1 +
>
config: arm64-randconfig-r016-20200603 (attached as .config)
compiler: clang version 11.0.0 (https://github.com/llvm/llvm-project
16437992cac249f6fe1efd392d20e3469b47e39e)
reproduce (this is a W=1 build):
wget
https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O
~/bin
Hi Joerg,
On 6/2/20 5:26 PM, Joerg Roedel wrote:
Hi,
two small patches to move the Intel and AMD IOMMU drivers into their own
subdirectory under drivers/iommu/ to make the file structure a bit less
cluttered.
Does the MAINTAINERS file need to update?
Best regards,
baolu
Regards,
Hi Linus,
The following changes since commit 8f3d9f354286745c751374f5f1fcafee6b3f3136:
Linux 5.7-rc1 (2020-04-12 12:35:55 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/chrome-platform/linux.git
tags/tag-chrome-platform-for-v5.8
for you to
On Wed, Jun 3, 2020 at 4:24 PM Christian Brauner
wrote:
>
> Ok, here's what I have. Does the below look somewhat sane?
Probably. Needs lots of testing. But this one looks wrong:
> +int __close_range(unsigned fd, unsigned max_fd, unsigned int flags)
> {
> + if ((max_fd + 1) >=
On Wed, Jun 3, 2020 at 6:19 PM Denis Efremov wrote:
>
> Allow user to use alternative implementations of compression tools,
> such as pigz, pbzip2, pxz. For example, multi-threaded tools to
> speed up the build:
> $ make GZIP=pigz BZIP2=pbzip2
>
> Variables _GZIP, _BZIP2, _LZOP are used
On Tue, Jun 02, 2020 at 11:42:12AM -0700, Brendan Shanks wrote:
> Add emulation/spoofing of SLDT and STR for both 32- and 64-bit
> processes.
>
> Wine users have found a small number of Windows apps using SLDT that
> were crashing when run on UMIP-enabled systems.
>
> Reported-by: Andreas
On 3/6/20 9:57 pm, wanghai (M) wrote:
kfree(cr) can be called when
kobject_put()-->kobject_release()-->kobject_cleanup()-->kobj_type->release()
is called. The kobj_type here is afu_config_record_type
Of course, I missed that.
In that case
Acked-by: Andrew Donnellan
Thanks for the fix!
On Wed, Jun 03, 2020 at 11:39:41AM +0800, Shengjiu Wang wrote:
> Obtained with:
> $ make W=1
>
> sound/soc/fsl/fsl_easrc.c:403: warning: Function parameter or member 'easrc'
> not described in 'fsl_easrc_normalize_filter'
> sound/soc/fsl/fsl_easrc.c:403: warning: Function parameter or member
>
On Wed, Jun 03, 2020 at 11:39:40AM +0800, Shengjiu Wang wrote:
> Obtained with:
> $ make W=1
>
> sound/soc/fsl/fsl_easrc.c: In function 'fsl_easrc_set_rs_ratio':
> sound/soc/fsl/fsl_easrc.c:182:15: warning: variable 'int_bits' set but not
> used [-Wunused-but-set-variable]
> unsigned int
On Wed, Jun 03, 2020 at 11:39:39AM +0800, Shengjiu Wang wrote:
> Obtained with:
> $ make W=1
>
> sound/soc/fsl/fsl_easrc.c:967:5: warning: no previous prototype for function
> 'fsl_easrc_config_context' [-Wmissing-prototypes]
> int fsl_easrc_config_context(struct fsl_asrc *easrc, unsigned int
On Wed, 2020-06-03 at 16:32 -0700, Kees Cook wrote:
> Using uninitialized_var() is dangerous as it papers over real bugs[1]
> (or can in the future), and suppresses unrelated compiler warnings
> (e.g. "unused variable"). If the compiler thinks it is uninitialized,
> either simply initialize the
On 2020-06-03 16:32, Kees Cook wrote:
> Using uninitialized_var() is dangerous as it papers over real bugs[1]
> (or can in the future), and suppresses unrelated compiler warnings
> (e.g. "unused variable"). If the compiler thinks it is uninitialized,
> either simply initialize the variable or make
On Wed, Jun 3, 2020 at 4:42 PM Kees Cook wrote:
>
> On Tue, Jun 02, 2020 at 06:10:40PM -0700, Sargun Dhillon wrote:
> > Sargun Dhillon (4):
> > fs, net: Standardize on file_receive helper to move fds across
> > processes
> > pid: Use file_receive helper to copy FDs
>
> The fixes (that
Hi all,
On Mon, 11 May 2020 09:24:48 +1000 Stephen Rothwell
wrote:
>
> Today's linux-next merge of the mips tree got a conflict in:
>
> arch/mips/loongson2ef/Kconfig
>
> between commit:
>
> bbd7ffdbef68 ("clk: Allow the common clk framework to be selectable")
>
> from the clk tree and
On Thu, Feb 6, 2020 at 10:42 PM Nathan Chancellor
wrote:
>
> On Wed, Feb 05, 2020 at 07:25:59AM +0100, Christophe Leroy wrote:
> >
> >
> > Le 05/02/2020 à 01:50, Fangrui Song a écrit :
> > > A PC-relative relocation (R_PPC_REL16_LO in this case) referencing a
> > > preemptible symbol in a -shared
> -Original Message-
> From: Mark Brown
> Sent: Wednesday, June 3, 2020 8:43 PM
> To: Steve Lee
> Cc: lgirdw...@gmail.com; pe...@perex.cz; ti...@suse.com;
> ckee...@opensource.cirrus.com; ge...@linux-m68k.org;
> r...@opensource.wolfsonmicro.com; shumi...@realtek.com;
>
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
for-next
Head SHA1: daceabf1b494c9e40a93fcc323b1258f557f65a1
Tom Zanussi (1):
tracing/doc: Fix ascii-art in histogram-design.rst
Documentation/trace/histogram-design.rst | 48
1
s which already has
> Ira's patches and it booted fine. I've used sparc32_defconfig to build
> the kernel and qemu-system-sparc with default machine and CPU.
>
>
> Mike, am I wrong? Do you think the kmap() patches are still causing issues?
>
For my part, all I can say is that -next is in pretty bad shape right now.
The summary of my tests says:
Build results:
total: 151 pass: 130 fail: 21
Qemu test results:
total: 430 pass: 375 fail: 55
sparc32 smp images in next-20200603 still crash for me with a spinlock
recursion. s390 images hang early in boot. Several others (alpha, arm64,
various ppc) don't even compile. I can run some more bisects over time,
but this is becoming a full-time job :-(.
Guenter
On Tue, Jun 02, 2020 at 06:10:40PM -0700, Sargun Dhillon wrote:
> Sargun Dhillon (4):
> fs, net: Standardize on file_receive helper to move fds across
> processes
> pid: Use file_receive helper to copy FDs
The fixes (that should add open-coded cgroups stuff) should be separate
patches so
On Wed, Jun 03, 2020 at 04:04:31PM -0700, Joe Perches wrote:
> more odd uses (mostly in comments)
>
> $ git grep -P -oh '\bIS_ENABLED\s*\(\s*\w+\s*\)'| \
> sed -r 's/\s+//g'| \
> grep -v '(CONFIG_' | \
> sort | uniq -c | sort -rn
I think a missed a bunch because my grep was messy. :) This
On Wed, Jun 03, 2020 at 03:00:05PM -0700, Casey Schaufler wrote:
> On 6/3/2020 2:02 PM, Alexei Starovoitov wrote:
> > On Wed, Jun 03, 2020 at 10:37:47AM -0700, Linus Torvalds wrote:
> >> On Wed, Jun 3, 2020 at 10:20 AM Casey Schaufler
> >> wrote:
> >>> We could have inode->i_security be the
On Tue, Jun 2, 2020 at 8:31 PM Linus Torvalds
wrote:
> Side note since you mention performance work: in the past when I've
> looked at SELinux performance (generally as part of pathname lookup
> etc VFS loads), the biggest cost by far was that all the SELinux data
> structures take a ton of cache
Using uninitialized_var() is dangerous as it papers over real bugs[1]
(or can in the future), and suppresses unrelated compiler warnings (e.g.
"unused variable"). If the compiler thinks it is uninitialized, either
simply initialize the variable or make compiler changes. As a precursor
to
CAUTION: This email originated from outside of the organization. Do not click
links or open attachments unless you can confirm the sender and know the
content is safe.
On Tue, May 19, 2020 at 11:27:50PM +, Anchal Agarwal wrote:
> From: Munehisa Kamata
>
> S4 power
Using uninitialized_var() is dangerous as it papers over real bugs[1]
(or can in the future), and suppresses unrelated compiler warnings (e.g.
"unused variable"). If the compiler thinks it is uninitialized, either
simply initialize the variable or make compiler changes. As a precursor
to
Using uninitialized_var() is dangerous as it papers over real bugs[1]
(or can in the future), and suppresses unrelated compiler warnings
(e.g. "unused variable"). If the compiler thinks it is uninitialized,
either simply initialize the variable or make compiler changes.
As recommended[2] by[3]
Using uninitialized_var() is dangerous as it papers over real bugs[1]
(or can in the future), and suppresses unrelated compiler warnings (e.g.
"unused variable"). If the compiler thinks it is uninitialized, either
simply initialize the variable or make compiler changes. As a precursor
to
Using uninitialized_var() is dangerous as it papers over real bugs[1]
(or can in the future), and suppresses unrelated compiler warnings (e.g.
"unused variable"). If the compiler thinks it is uninitialized, either
simply initialize the variable or make compiler changes. As a precursor
to
Using uninitialized_var() is dangerous as it papers over real bugs[1]
(or can in the future), and suppresses unrelated compiler warnings (e.g.
"unused variable"). If the compiler thinks it is uninitialized, either
simply initialize the variable or make compiler changes. As a precursor
to
Using uninitialized_var() is dangerous as it papers over real bugs[1]
(or can in the future), and suppresses unrelated compiler warnings
(e.g. "unused variable"). If the compiler thinks it is uninitialized,
either simply initialize the variable or make compiler changes.
In preparation for
Using uninitialized_var() is dangerous as it papers over real bugs[1]
(or can in the future), and suppresses unrelated compiler warnings (e.g.
"unused variable"). If the compiler thinks it is uninitialized, either
simply initialize the variable or make compiler changes. As a precursor
to
Using uninitialized_var() is dangerous as it papers over real bugs[1]
(or can in the future), and suppresses unrelated compiler warnings (e.g.
"unused variable"). If the compiler thinks it is uninitialized, either
simply initialize the variable or make compiler changes. As a precursor
to
At truncate, there is a problem of incorrect updating in the file entry
pointer instead of stream entry. This will cause the problem of
overwriting the time field of the file entry to new_size. Fix it to
update stream entry.
Fixes: 98d917047e8b ("exfat: add file operations")
Cc:
Using uninitialized_var() is dangerous as it papers over real bugs[1]
(or can in the future), and suppresses unrelated compiler warnings
(e.g. "unused variable"). If the compiler thinks it is uninitialized,
either simply initialize the variable or make compiler changes.
As recommended[2] by[3]
Using uninitialized_var() is dangerous as it papers over real bugs[1]
(or can in the future), and suppresses unrelated compiler warnings
(e.g. "unused variable"). If the compiler thinks it is uninitialized,
either simply initialize the variable or make compiler changes.
I preparation for
On Wed, 3 Jun 2020 15:44:06 -0600
Jonathan Corbet wrote:
> Commit 632dcc2c75ef ("irqchip: Add Loongson PCH MSI controller")
> appears to suffer from a lack of copy-and-paste fixup, with the
> result that the KConfig description describes the wrong device.
> Avoid potential user confusion by
On Thu, Jun 04, 2020 at 01:58:00AM +0530, Vaibhav Jain wrote:
> Hi Ira,
>
> Thanks again for reviewing this patch. My Response below:
>
> Ira Weiny writes:
>
> > On Tue, Jun 02, 2020 at 01:51:49PM -0700, 'Ira Weiny' wrote:
> >> On Tue, Jun 02, 2020 at 03:44:37PM +0530, Vaibhav Jain wrote:
> >
On Tue, Jun 02, 2020 at 05:08:22PM -0700, Linus Torvalds wrote:
> On Tue, Jun 2, 2020 at 4:33 PM Christian Brauner
> wrote:
> > >
> > > And maybe this _did_ get mentioned last time, and I just don't find
> > > it. I also don't see anything like that in the patches, although the
> > > flags
On Mon, Jun 01, 2020 at 09:52:22PM -0700, Joerg Roedel wrote:
> Track at which levels in the page-table entries were modified by
> vmap/vunmap.
>
> After the page-table has been modified, use that information do decide
> whether the new arch_sync_kernel_mappings() needs to be called.
>
>
On Thu, Jun 04, 2020 at 12:34:04AM +0530, Vaibhav Jain wrote:
> Hi Ira,
>
> Thanks for reviewing this patch. My responses below:
>
> Ira Weiny writes:
>
> > On Tue, Jun 02, 2020 at 03:44:38PM +0530, Vaibhav Jain wrote:
> >> This patch implements support for PDSM request 'PAPR_PDSM_HEALTH'
> >>
My codespell dictionary has a lot of capitalized words. For example:
MSDOS->MS-DOS
Since checkpatch uses case-insensitive matching, I get an undefined
variable warning and then empty suggestions for things like this:
Use of uninitialized value $typo_fix in concatenation (.) or string at
> -Original Message-
> From: linux-acpi-ow...@vger.kernel.org ow...@vger.kernel.org> On Behalf Of Rafael J. Wysocki
> Sent: Wednesday, June 3, 2020 6:04 AM
> To: Gustavo A. R. Silva ; Kaneda, Erik
>
> Cc: Moore, Robert ; Wysocki, Rafael J
> ; Len Brown ; ACPI Devel
> Maling List ; open
On Wed, Jun 03, 2020 at 04:23:25PM +0200, Joerg Roedel wrote:
> > > + */
> > > + io_bytes = (exit_info_1 >> 4) & 0x7;
> > > + ghcb_count = sizeof(ghcb->shared_buffer) / io_bytes;
> > > +
> > > + op_count= (exit_info_1 & IOIO_REP) ? regs->cx : 1;
> > > +
Hi Marcel,
Thanks for your review. V2 was uploaded to address these 3 comments.
Regards,
Miao
On Wed, Jun 3, 2020 at 10:59 AM Marcel Holtmann wrote:
>
> Hi Miao-chen,
>
> > This adds the request handler of MGMT_OP_READ_ADV_MONITOR_FEATURES
> > command. Since the controller-based monitoring is
On Tue, 2 Jun 2020 21:40:58 -0400
Yan Zhao wrote:
> On Tue, Jun 02, 2020 at 01:34:35PM -0600, Alex Williamson wrote:
> > I'm not at all happy with this. Why do we need to hide the migration
> > sparse mmap from the user until migration time? What if instead we
> > introduced a new
On Wed, 2020-06-03 at 15:40 -0700, Kees Cook wrote:
> The IS_ENABLED() use was missing the CONFIG_ prefix which would have
> lead to skipping this code.
>
> Fixes: 3ad1f3a33286 ("pwm: Implement some checks for lowlevel drivers")
> Signed-off-by: Kees Cook
> ---
> drivers/pwm/core.c | 2 +-
> 1
This notifies management sockets on MGMT_EV_ADV_MONITOR_ADDED event.
The following test was performed.
- Start two btmgmt consoles, issue a btmgmt advmon-add command on one
console and observe a MGMT_EV_ADV_MONITOR_ADDED event on the other
Signed-off-by: Miao-chen Chou
---
Changes in v2: None
This adds the request handler of MGMT_OP_ADD_ADV_PATTERNS_MONITOR command.
Note that the controller-based monitoring is not yet in place. This tracks
the content of the monitor without sending HCI traffic, so the request
returns immediately.
The following manual test was performed.
- Issue btmgmt
This adds the request handler of MGMT_OP_READ_ADV_MONITOR_FEATURES
command. Since the controller-based monitoring is not yet in place, this
report only the supported features but not the enabled features.
The following test was performed.
- Issuing btmgmt advmon-features.
Signed-off-by:
This notifies management sockets on MGMT_EV_ADV_MONITOR_REMOVED event.
The following test was performed.
- Start two btmgmt consoles, issue a btmgmt advmon-remove command on one
console and observe a MGMT_EV_ADV_MONITOR_REMOVED event on the other.
Signed-off-by: Miao-chen Chou
---
Changes in
This adds the request handler of MGMT_OP_REMOVE_ADV_MONITOR command.
Note that the controller-based monitoring is not yet in place. This
removes the internal monitor(s) without sending HCI traffic, so the
request returns immediately.
The following test was performed.
- Issue btmgmt advmon-remove
This adds support for Advertisement Monitor API. Here are the commands
and events added.
- Read Advertisement Monitor Feature command
- Add Advertisement Pattern Monitor command
- Remove Advertisement Monitor command
- Advertisement Monitor Added event
- Advertisement Monitor Removed event
This calls hci_update_background_scan() when there is any update on the
advertisement monitors. If there is at least one advertisement monitor,
the filtering policy of scan parameters should be 0x00. This also reports
device found mgmt events if there is at least one monitor.
The following cases
On Wed, Jun 03, 2020 at 11:41:42PM +0530, Vaibhav Jain wrote:
> Hi Ira,
>
> Thanks for reviewing this patch. My responses below:
>
> Ira Weiny writes:
>
...
> >> + *
> >> + * Payload Version:
> >> + *
> >> + * A 'payload_version' field is present in PDSM header that indicates a
> >>
On Tue, May 19, 2020 at 11:37:01AM +0530, Krishna Manikandan wrote:
> MSM Mobile Display Subsytem (MDSS) encapsulates sub-blocks
> like DPU display controller, DSI etc. Add YAML schema
> for the device tree bindings for the same.
>
> Signed-off-by: Krishna Manikandan
>
> Changes in v2:
>
The IS_ENABLED() use was missing the CONFIG_ prefix which would have
lead to skipping this code.
Fixes: 3ad1f3a33286 ("pwm: Implement some checks for lowlevel drivers")
Signed-off-by: Kees Cook
---
drivers/pwm/core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
CAUTION: This email originated from outside of the organization. Do not
click links or open attachments unless you can confirm the sender and know the
content is safe.
On 5/19/20 7:26 PM, Anchal Agarwal wrote:
> From: Munehisa Kamata
>
> Add Xen PVHVM specific system core
101 - 200 of 1155 matches
Mail list logo
