Replace the two negative flags that are always used together with a
single positive flag that indicates the writeback capability instead
of two related non-capabilities. Also remove the pointless wrappers
to just check the flag.
Signed-off-by: Christoph Hellwig
---
fs/9p/vfs_file.c|
The raid5 and raid10 drivers currently update the read-ahead size,
but not the optimal I/O size on reshape. To prepare for deriving the
read-ahead size from the optimal I/O size make sure it is updated
as well.
Signed-off-by: Christoph Hellwig
---
drivers/md/raid10.c | 22 ++
Set up a readahead size by default, as very few users have a good
reason to change it.
Signed-off-by: Christoph Hellwig
Acked-by: David Sterba [btrfs]
Acked-by: Richard Weinberger [ubifs, mtd]
---
block/blk-core.c | 1 -
drivers/mtd/mtdcore.c | 1 +
fs/9p/vfs_super.c | 4 ++--
fs/afs/
The BDI_CAP_STABLE_WRITES is one of the few bits of information in the
backing_dev_info shared between the block drivers and the writeback code.
To help untangling the dependency replace it with a queue flag and a
superblock flag derived from it. This also helps with the case of e.g.
a file system
There is no point in trying to call bdev_read_page if SWP_SYNCHRONOUS_IO
is not set, as the device won't support it.
Signed-off-by: Christoph Hellwig
---
mm/page_io.c | 18 ++
1 file changed, 10 insertions(+), 8 deletions(-)
diff --git a/mm/page_io.c b/mm/page_io.c
index ccda767
Generate the queue_sysfs_entry given that we have all the required
information for it, and rename the generated show and store methods
to match the other ones in the file.
Signed-off-by: Christoph Hellwig
Reviewed-by: Johannes Thumshirn
---
block/blk-sysfs.c | 31 +--
On 7/24/20 7:06 AM, Vaishnav M A wrote:
> Attached is a patch for the mikroBUS driver which helps to
> instantiate an add-on board device on a mikrobus port by fetching
> the device identifier manifest binary from an EEPROM on-board
> the device. mikroBUS is an add-on board socket standard by
> Mik
Hi Jens,
this series contains a bunch of different BDI cleanups. The biggest item
is to isolate block drivers from the BDI in preparation of changing the
lifetime of the block device BDI in a follow up series.
Changes since v2:
- fix a rw_page return value check
- fix up various changelogs
C
Just checking SB_I_CGROUPWB for cgroup writeback support is enough.
Either the file system allocates its own bdi (e.g. btrfs), in which case
it is known to support cgroup writeback, or the bdi comes from the block
layer, which always supports cgroup writeback.
Signed-off-by: Christoph Hellwig
Rev
Drivers shouldn't really mess with the readahead size, as that is a VM
concept. Instead set it based on the optimal I/O size by lifting the
algorithm from the md driver when registering the disk. Also set
bdi->io_pages there as well by applying the same scheme based on
max_sectors.
Signed-off-by
On Sun, Jul 26, 2020 at 07:50:12PM +0530, Aditya Jain wrote:
> Cleaning up messy multiline function declarations in hal_phy_cfg.h
>
> This patch is a continuation of patch "Clean up function declarations"
This should be merged with that patch, no reason to make it separate.
>
> Signed-off-by: A
This adds full 802.1q VLAN support to the qca8k, allowing the use of
vlan_filtering and more complicated bridging setups than allowed by
basic port VLAN support.
Tested with a number of untagged ports with separate VLANs and then a
trunk port with all the VLANs tagged on it.
v2:
- Return sensible
On Sun, 2020-07-26 at 09:45 +0200, SeongJae Park wrote:
> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
[]
> @@ -721,6 +721,7 @@ sub read_word_corrections {
> my %deprecated_terms_fix;
> read_word_corrections($deprecated_terms_file, \%deprecated_terms_fix);
> my $deprecated_terms =
+Enric
Hello Alexandre,
Thanks for the series.
On Wed, 20 May 2020 at 05:27, Alexandre Courbot wrote:
>
> This series adds support for the encoder present on MT8183. It is very similar
> to the one in MT8173, but with different capabilities and using a new firmware
> interface (SCP, while MT817
On Fri, Jul 24, 2020 at 09:14:26AM +0200, Juri Lelli wrote:
> Hi,
>
> On 07/07/20 00:04, Peng Liu wrote:
> > 'commit 840d719604b0 ("sched/deadline: Update rq_clock of later_rq when
> > pushing a task")'
> > introduced the update_rq_clock() to fix the "used-before-update" bug.
> >
> > 'commit f49
Hi Alexandre,
Last review on my side, this series looks mostly good.
On Mon, 13 Jul 2020 at 03:09, Alexandre Courbot wrote:
>
> Different chips have different supported bitrate ranges. Move the list
s/bitrate ranges/formats
> of supported formats to the platform data, and split the output and
Randy Dunlap a écrit :
Drop duplicated words in arch/powerpc/ header files.
How did you detect them ? Do you have some script for tgat, or you
just read all comments ?
Cc: Michael Ellerman
You say you Cc Michael, but in fact you don't ... Allthough he is the
powerpc maintainer
Ch
Adjust spacing in macro definitions to align them and improve
readbility
Signed-off-by: Aditya Jain
---
drivers/staging/rtl8723bs/include/hal_phy_cfg.h | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/staging/rtl8723bs/include/hal_phy_cfg.h
b/drivers/staging/rtl
Clean up multiline function declartions in hal_phy_cfg.h
to improve code readablility
Signed-off-by: Aditya Jain
---
.../staging/rtl8723bs/include/hal_phy_cfg.h | 44 ---
1 file changed, 9 insertions(+), 35 deletions(-)
diff --git a/drivers/staging/rtl8723bs/include/hal_phy_cf
Cleaning up messy multiline function declarations in hal_phy_cfg.h
This patch is a continuation of patch "Clean up function declarations"
Signed-off-by: Aditya Jain
---
.../staging/rtl8723bs/include/hal_phy_cfg.h | 56 ++-
1 file changed, 16 insertions(+), 40 deletions(-)
dif
Fixing ERROR: "foo *bar" should be "foo *bar" in hal_phy_cfg.h
as reported by checkpatch.pl
Signed-off-by: Aditya Jain
---
.../staging/rtl8723bs/include/hal_phy_cfg.h| 18 +-
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/drivers/staging/rtl8723bs/include/h
Hi all,
The following series of patches fixes code style issues in
the file staging/drivers/rtl8723bs/include/hal_phy_cfg.h
Regards,
Aditya Jain
Em Thu, May 14, 2020 at 03:39:42PM -0500, Josh Poimboeuf escreveu:
> On Fri, Mar 08, 2019 at 10:17:47AM -0800, Davidlohr Bueso wrote:
> > On Thu, 07 Mar 2019, Arnaldo Carvalho de Melo wrote:
> > > You forgot to update tools/perf/Documentation/perf-bench.txt, and please
> > > take a look at tools/pe
Quoting Alex Williamson (2020-07-26 14:30:52)
> On Sun, 26 Jul 2020 17:49:07 +1000
> Geoffrey McRae wrote:
>
> > Hi All,
> >
> > The commit 22540ca3d00d2990a4148a13b92209c3dc5422db causes a Windows KVM
> > guest running under QEMU with a VFIO passthrough GPU to randomly stall
> > when using th
Add devicetree binding document for ADXRS290, a dual-axis MEMS gyroscope.
Reviewed-by: Rob Herring
Signed-off-by: Nishant Malpani
---
No changes in v4.
No changes in v3.
Changes in v2:
- use 'const' instead of 'enum' while setting the compatible string
since only a single item is expect
ADXRS290 is a high performance MEMS pitch and roll (dual-axis in-plane)
angular rate sensor (gyroscope) designed for use in stabilization
applications. It also features an internal temperature sensor and
programmable high-pass and low-pass filters.
Add support for ADXRS290 in direct-access mode fo
On 26/07/20 5:45 pm, Jonathan Cameron wrote:
On Fri, 24 Jul 2020 16:31:59 +0530
Nishant Malpani wrote:
ADXRS290 is a high performance MEMS pitch and roll (dual-axis in-plane)
angular rate sensor (gyroscope) designed for use in stabilization
applications. It also features an internal temperat
Linus,
I was greatly confused and tried to confuse you.
Somehow I misunderstood your last version and didn't bother to read it
again until now.
Sorry for noise and thanks for your explanations.
Oleg.
On 07/25, Linus Torvalds wrote:
>
> On Sat, Jul 25, 2020 at 12:28 PM Oleg Nesterov wrote:
>
On 26/07/20 1:33 pm, Andy Shevchenko wrote:
On Fri, Jul 24, 2020 at 2:02 PM Nishant Malpani
wrote:
ADXRS290 is a high performance MEMS pitch and roll (dual-axis in-plane)
angular rate sensor (gyroscope) designed for use in stabilization
applications. It also features an internal temperature
The following commit has been merged into the core/entry branch of tip:
Commit-ID: aadfc2f957cb470a5a7e52cc41a2fa86e784bcd2
Gitweb:
https://git.kernel.org/tip/aadfc2f957cb470a5a7e52cc41a2fa86e784bcd2
Author:Ingo Molnar
AuthorDate:Sat, 25 Jul 2020 11:19:51 +02:00
Committer:
Ingo Molnar writes:
> The noinstr attribute is to be specified before the return type in the
> same way 'inline' is used.
>
> Similar cases were recently fixed for x86, via:
>
> 7f6fa101dfac: ("x86: Correct noinstr qualifiers")
>
> These 2 cases were carried over by the new generic entry code.
Ingo Molnar writes:
> The __secure_computing() callback only exists on CONFIG_SECCOMP=y,
No. There is a stub function for the SECCOMP=n case.
> and on architectures that have CONFIG_HAVE_ARCH_SECCOMP_FILTER.
which is a prerequiste for converting over.
> Instead of complicating the #ifdef withi
> > +void i2c_free_slave_host_notify_device(struct i2c_client *client)
> > +{
> > + i2c_slave_unregister(client);
> > + kfree(client->dev.platform_data);
> > + i2c_unregister_device(client);
> > +}
> > +EXPORT_SYMBOL_GPL(i2c_free_slave_host_notify_device);
>
> Sidenote: With my recent serie
On Sat, Jul 25, 2020 at 11:45 PM Alexandre Courbot
wrote:
>
> On Thu, Jul 16, 2020 at 5:23 AM Ezequiel Garcia
> wrote:
> >
> > Now that slice invariant parameters have been moved,
> > the driver no longer needs this control, so drop it.
> >
> > Signed-off-by: Ezequiel Garcia
> > ---
> > driver
On 2020-07-26 23:32, Geoffrey McRae wrote:
On 2020-07-26 23:30, Alex Williamson wrote:
On Sun, 26 Jul 2020 17:49:07 +1000
Geoffrey McRae wrote:
Hi All,
The commit 22540ca3d00d2990a4148a13b92209c3dc5422db causes a Windows
KVM
guest running under QEMU with a VFIO passthrough GPU to randoml
On 2020-07-26 23:30, Alex Williamson wrote:
On Sun, 26 Jul 2020 17:49:07 +1000
Geoffrey McRae wrote:
Hi All,
The commit 22540ca3d00d2990a4148a13b92209c3dc5422db causes a Windows
KVM
guest running under QEMU with a VFIO passthrough GPU to randomly stall
when using the GPU leading to the g
On Sun, 26 Jul 2020 17:49:07 +1000
Geoffrey McRae wrote:
> Hi All,
>
> The commit 22540ca3d00d2990a4148a13b92209c3dc5422db causes a Windows KVM
> guest running under QEMU with a VFIO passthrough GPU to randomly stall
> when using the GPU leading to the guest assuming that the driver has
> hun
On 2020/7/26 19:21, Alexander A. Klimov wrote:
> Rationale:
> Reduces attack surface on kernel devs opening the links for MITM
> as HTTPS traffic is much harder to manipulate.
>
> Signed-off-by: Alexander A. Klimov
> ---
> Continuing my work started at 93431e0607e5 with unmaintained stuff accord
Change subject to:
RISC-V: KVM: kernel mmio read/write support
Also add 1-2 sentences of commit description.
On Fri, Jul 24, 2020 at 2:25 PM Yifei Jiang wrote:
>
> Signed-off-by: Yifei Jiang
> Signed-off-by: Mingwang Li
> ---
> arch/riscv/kvm/vcpu_exit.c | 38 -
`-- include-linux-irqflags.h:error:expected-expression-before-)-token
|-- x86_64-randconfig-c002-20200726
| `-- include-linux-irqflags.h:error:expected-expression-before-)-token
`-- x86_64-rhel-7.6-kselftests
`-- include-linux-irqflags.h:error:expected-expression-before-)-token
elapsed time: 1600m
Convert the textual documentation of Device Tree bindings for the
Ingenic JZ47xx SoCs battery to YAML.
Signed-off-by: Artur Rojek
---
.../bindings/power/supply/ingenic,battery.txt | 31 -
.../power/supply/ingenic,battery.yaml | 67 +++
2 files changed, 67 insertio
On Fri, Jul 24, 2020 at 2:25 PM Yifei Jiang wrote:
>
> Signed-off-by: Yifei Jiang
> Signed-off-by: Mingwang Li
> ---
> arch/riscv/kvm/vcpu_exit.c | 38 --
> 1 file changed, 32 insertions(+), 6 deletions(-)
>
> diff --git a/arch/riscv/kvm/vcpu_exit.c b/arch/ri
On Sun, Jul 26, 2020 at 12:00:37PM +0300, Andy Shevchenko wrote:
> On Sun, Jul 26, 2020 at 6:14 AM Stafford Horne wrote:
> >
> > The return type of functions _inb, _inw and _inl are all u16 which looks
> > wrong. This patch makes them u8, u16 and u32 respectively.
> >
> > The original commit text
..
> >
> > > > + if (ret < 0)
> > > > + return ret;
> > > > +
> > > > + for (i = 0; i < num_ch; i++) {
> > > > + channels[i] = (struct
> > iio_chan_spec)ONE_BIT_ADC_DAC_CHANNEL(i +
> > > > + offset,
Please change subject to:
"RISC-V: KVM: enable ioeventfd capability"
Also add 1-2 sentences of commit description.
On Fri, Jul 24, 2020 at 2:25 PM Yifei Jiang wrote:
>
> Signed-off-by: Yifei Jiang
> Signed-off-by: Mingwang Li
> ---
> arch/riscv/kvm/Kconfig | 2 ++
> arch/riscv/kvm/Makefile |
On 7/24/20 7:06 AM, Vaishnav M A wrote:
> Attached is a patch for the mikroBUS driver which helps to
> instantiate an add-on board device on a mikrobus port by fetching
> the device identifier manifest binary from an EEPROM on-board
> the device. mikroBUS is an add-on board socket standard by
> Mik
On Thu, Jul 23, 2020 at 09:56:34PM +0200, Wolfram Sang wrote:
> On Wed, Jul 22, 2020 at 03:00:21PM -0700, Douglas Anderson wrote:
> > When I have KASAN enabled on my kernel and I start stressing the
> > touchscreen my system tends to hang. The touchscreen is one of the
> > only things that does a
Hi Rajendra,
On 7/23/20 2:26 PM, Rajendra Nayak wrote:
> Add support to add OPP tables and perf voting on the OPP powerdomain.
> This is needed so venus votes on the corresponding performance state
> for the OPP powerdomain along with setting the core clock rate.
>
> Signed-off-by: Rajendra Nayak
On Wed, 22 Jul 2020 00:25:48 +0530
Nishant Malpani wrote:
> Hello Jonathan,
>
> Thanks a lot for the detailed review. Comments inline...
>
...
>
> >>> +#define ADXRS290_REG_SN0 0x04 /* Serial Number Registers, 4 bytes */
> >>> +#define ADXRS290_REG_DATAX0 0x08 /* Roll Rate o/p Data Regs,
On Mon, 20 Jul 2020 16:51:33 +0300
Alexandru Ardelean wrote:
> From: Lars-Peter Clausen
>
> Make sure that the trigger function stubs are all static inline.
> Otherwise we might see compiler warnings about declared but unused
> functions.
>
> Fixes 77712e5fbe2e4: ("Staging: iio: Staticise non-
On Tue, 21 Jul 2020 01:16:55 +0200
Paul Cercueil wrote:
> Hi Jonathan,
>
> Le sam. 15 févr. 2020 à 18:32, Jonathan Cameron a
> écrit :
> > On Mon, 10 Feb 2020 19:54:38 -0300
> > Paul Cercueil wrote:
> >
> >> Implement write_raw by converting the value if writing the scale, or
> >> just c
On Wed, Jul 15, 2020 at 12:09:01PM +0100, Lad Prabhakar wrote:
> Document i2c controller for RZ/G2H (R8A774E1) SoC, which is compatible
> with R-Car Gen3 SoC family.
>
> Signed-off-by: Lad Prabhakar
> Reviewed-by: Marian-Cristian Rotariu
>
Applied to for-next, thanks!
signature.asc
Descript
On Wed, Jul 15, 2020 at 12:09:02PM +0100, Lad Prabhakar wrote:
> Document IIC controller for RZ/G2H (R8A774E1) SoC, which is compatible
> with R-Car Gen3 SoC family.
>
> Signed-off-by: Lad Prabhakar
> Reviewed-by: Marian-Cristian Rotariu
>
Applied to for-next, thanks!
signature.asc
Descript
On Mon, 20 Jul 2020 16:52:37 +0300
Alexandru Ardelean wrote:
> The change is mostly cosmetic. When looking into the menuconfig help of the
> ad8366 driver, the HMC1119 chip should also show up (since the driver
> supports it).
>
> Signed-off-by: Alexandru Ardelean
Applied
> ---
> drivers/iio/
On Wed, 22 Jul 2020 10:30:03 +0300
Alexandru Ardelean wrote:
> From: Stefan Popa
>
> The driver does not have a struct of_device_id table, but supported
> devices are registered via Device Trees. This patch adds OF device ID
> table.
>
> Signed-off-by: Stefan Popa
> Signed-off-by: Alexandru A
On Wed, 22 Jul 2020 10:25:46 +0300
Alexandru Ardelean wrote:
> The change is mostly stylistic. The table should be indented with tabs
> instead of spaces.
>
> Signed-off-by: Alexandru Ardelean
Applied
> ---
>
> Changelog v1 -> v2:
> * remove trailing comma at null terminator
>
> drivers/iio
On Wed, 22 Jul 2020 10:22:01 +0300
Alexandru Ardelean wrote:
> The driver pretty much uses device managed functions. The only left-over is
> the iio_device_register() function, which also requires an action-or-reset
> hook to disable the regulator on the remove and error path.
>
> Signed-off-by:
On Mon, 20 Jul 2020 13:22:40 -0700
Guenter Roeck wrote:
> A follow-up patch will extend the number of errors reported by
> cros_ec_cmd_xfer_status(). Specifically, the function will return
> -EOPNOTSUPP if a command is not supported by the EC. Prepare for it.
>
> Cc: Yu-Hsuan Hsu
> Cc: Prashant
onfig-r036-20200726 (attached as .config)
compiler: arm-linux-gnueabi-gcc (GCC) 9.3.0
reproduce (this is a W=1 build):
wget
https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O
~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to l
On Fri, 24 Jul 2020 16:31:59 +0530
Nishant Malpani wrote:
> ADXRS290 is a high performance MEMS pitch and roll (dual-axis in-plane)
> angular rate sensor (gyroscope) designed for use in stabilization
> applications. It also features an internal temperature sensor and
> programmable high-pass and
On Sun, Jul 26, 2020 at 02:14:34PM +1000, Nicholas Piggin wrote:
> Excerpts from Peter Zijlstra's message of July 26, 2020 6:26 am:
> > Which is 'funny' when it interleaves like:
> >
> > local_irq_disable();
> > ...
> > local_irq_enable()
> > trace_hardirqs_on();
> >
> >
Rationale:
Reduces attack surface on kernel devs opening the links for MITM
as HTTPS traffic is much harder to manipulate.
Signed-off-by: Alexander A. Klimov
---
Continuing my work started at 93431e0607e5 with unmaintained stuff according
to:
perl scripts/get_maintainer.pl --nogit{,-fallback}
On Sun, Jul 26, 2020 at 01:40:46PM +0200, Konrad Dybcio wrote:
> >Horrible global symbol name. Who calls this?
>
> Welcome to development on qcom platforms :D
Yeah, I have seen :(
> >This is the last patch in
> >the series, so if there is no user for this, please don't export it.
>
> Other dow
On Sun, Jul 26, 2020 at 02:14:34PM +1000, Nicholas Piggin wrote:
> > Now, x86, and at least arm64 call nmi_enter() before
> > trace_hardirqs_off(), but AFAICT Power never did that, and that's part
> > of the problem. nmi_enter() does lockdep_off() and that _used_ to also
> > kill IRQ tracking.
>
>
Rationale:
Reduces attack surface on kernel devs opening the links for MITM
as HTTPS traffic is much harder to manipulate.
Signed-off-by: Alexander A. Klimov
---
Continuing my work started at 93431e0607e5 with unmaintained stuff according
to:
perl scripts/get_maintainer.pl --nogit{,-fallback}
On Fri, 24 Jul 2020 14:33:24 -0700
Stephen Boyd wrote:
> These patches are only related because I'm looking at this driver. The
> first one resends the DT binding for the driver that was merged in
> v5.8-rc1 with a small change to update for proper regulators. The second
> patch fixes a few print
Hi,
On 24.07.20 15:41, Daniel Wagner wrote:
Known issues:
sigwaittest with hackbench as workload is able to trigger a crash on x86_64,
the same as reported for the v4.4.220-rt196 release. As it turns
out it was not triggered by BPF.
https://paste.opensuse.org/view/raw/58939248
On Sat, Jul 25, 2020 at 03:07:50PM -0700, Paul E. McKenney wrote:
> On Sat, Jul 25, 2020 at 10:21:31PM +0200, pet...@infradead.org wrote:
> > On Sat, Jul 25, 2020 at 10:10:13PM +0200, pet...@infradead.org wrote:
> > > On Sat, Jul 25, 2020 at 12:39:09PM -0700, Paul E. McKenney wrote:
> >
> > > > Th
On Fri, 24 Jul 2020 18:40:26 -0600
Daniel Campello wrote:
> This patch brings back fixes on v9 of initial patch that got dropped
> when v8 was taken instead.
Oops. Not quite sure what happened there and I can't even find a record
of me saying I was applying v8. Sorry about that.
> - Updated
On Fri, Jul 24, 2020 at 6:47 AM Amir Goldstein wrote:
>
> On Fri, Jul 24, 2020 at 5:45 AM Rong Chen wrote:
> >
> >
> >
> > On 7/21/20 11:59 PM, Amir Goldstein wrote:
> > > On Tue, Jul 21, 2020 at 3:15 AM kernel test robot
> > > wrote:
> > >> Greeting,
> > >>
> > >> FYI, we noticed a -9.5% regre
onfig-c001-20200726 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-14) 9.3.0
reproduce (this is a W=1 build):
# save the attached .config to linux build tree
make W=1 ARCH=i386
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot
All e
ERROR: modpost: "__cpu_logical_map" [drivers/cpufreq/tegra194-cpufreq.ko]
undefined!
ARM64 tegra194-cpufreq driver use cpu_logical_map, export
__cpu_logical_map to fix build issue.
I wonder why like other instances in the drivers, the mpidr is not get
directly from the cpu. The cpufreq_driver
Hi Greg, thanks for your review!
>Why do we need this noise in the kernel log?
I guess it could be left there as a debug print? Knowing your hardware
revision seems like a good, but yeah, not a necessary thing.
>You can drop the GPL boilerplate text and add a proper SPDX line at the
>top.
Seems
list_for_each_safe is able to handle an empty list.
The only effect of avoiding the loop is not initializing the
index variable.
Drop list_empty tests in cases where these variables are not
used.
The semantic patch that makes this change is as follows:
(http://coccinelle.lip6.fr/)
@@
expression
list_for_each_entry is able to handle an empty list.
The only effect of avoiding the loop is not initializing the
index variable.
Drop list_empty tests in cases where these variables are not
used.
Note that list_for_each_entry is defined in terms of list_first_entry,
which indicates that it should
list_for_each_entry is able to handle an empty list.
The only effect of avoiding the loop is not initializing the
index variable.
Drop list_empty tests in cases where these variables are not
used.
Note that list_for_each_entry is defined in terms of list_first_entry,
which indicates that it should
list_for_each_entry_safe is able to handle an empty list.
The only effect of avoiding the loop is not initializing the
index variable.
Drop list_empty tests in cases where these variables are not
used.
Note that list_for_each_entry_safe is defined in terms of
list_first_entry, which indicates that
list_for_each_entry is able to handle an empty list.
The only effect of avoiding the loop is not initializing the
index variable.
Drop list_empty tests in cases where these variables are not
used.
Note that list_for_each_entry is defined in terms of list_first_entry,
which indicates that it should
list_for_each_safe is able to handle an empty list.
The only effect of avoiding the loop is not initializing the
index variable.
Drop list_empty tests in cases where these variables are not
used.
The semantic patch that makes this change is as follows:
(http://coccinelle.lip6.fr/)
@@
expression
The various list iterators are able to handle an empty list.
The only effect of avoiding the loop is not initializing some
index variables.
Drop list_empty tests in cases where these variables are not
used.
The semantic patch that makes these changes is as follows:
(http://coccinelle.lip6.fr/)
@
list_for_each_entry{_safe} is able to handle an empty list.
The only effect of avoiding the loop is not initializing the
index variable.
Drop list_empty tests in cases where these variables are not
used.
Note that list_for_each_entry{_safe} is defined in terms of
list_first_entry, which indicates
Hello.
On 20.07.2020 19:04, Dmitry Monakhov wrote:
commit db37a34c563b ("block, bfq: get a ref to a group when adding it
to a service tree")
introduce leak forbfq_group and blkcg_gq objects because of get/put
imbalance. See trace balow:
-> blkg_alloc
-> bfq_pq_alloc
-> bfqg_get (+1)
->bf
Clean up cpu-feature-overrides, which only repeat the default.
Signed-off-by: Thomas Bogendoerfer
---
arch/mips/include/asm/mach-dec/cpu-feature-overrides.h | 1 -
arch/mips/include/asm/mach-ip27/cpu-feature-overrides.h | 3 ---
arch/mips/include/asm/mach-ip30/cpu-feature-overrides.h
On Sun, Jul 26, 2020 at 01:12:06PM +0200, Konrad Dybcio wrote:
> From: Xiaozhe Shi
>
> Add the REVID device driver. The REVID driver will print out the PMIC
> revision at probe time.
Why do we need this noise in the kernel log?
> --- /dev/null
> +++ b/drivers/soc/qcom/qpnp-revid.c
> @@ -0,0 +1,
With this case:
aplay -Dhw:x 16khz.wav 24khz.wav
There is sound distortion for 24khz.wav. The reason is that setting
PLL of WM8962 with set_bias_level function, the bias level is not
changed when 24khz.wav is played, then the PLL won't be reset, the
clock is not correct, so distortion happens.
The
Rationale:
Reduces attack surface on kernel devs opening the links for MITM
as HTTPS traffic is much harder to manipulate.
Signed-off-by: Alexander A. Klimov
---
Continuing my work started at 93431e0607e5 with unmaintained stuff according
to:
perl scripts/get_maintainer.pl --nogit{,-fallback}
From: Sebastian Gottschall
> Sent: 25 July 2020 16:42
> >> i agree. i just can say that i tested this patch recently due this
> >> discussion here. and it can be changed by sysfs. but it doesnt work for
> >> wifi drivers which are mainly using dummy netdev devices. for this i
> >> made a small pat
This commit adds support for the MDP5 IP on Snapdragon
636/660.
Signed-off-by: Konrad Dybcio
---
drivers/gpu/drm/msm/disp/mdp5/mdp5_cfg.c | 105 +++
1 file changed, 105 insertions(+)
diff --git a/drivers/gpu/drm/msm/disp/mdp5/mdp5_cfg.c
b/drivers/gpu/drm/msm/disp/mdp5/mdp5_
Add missing halt_check, hwcg_reg and hwcg_bit properties.
These were likely omitted when porting the driver upstream.
Signed-off-by: Konrad Dybcio
---
drivers/clk/qcom/gcc-sdm660.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/clk/qcom/gcc-sdm660.c b/drivers/clk/qcom/gcc-sdm660.
This commit adds support for the MDP5 IP on Snapdragon
630. The configuration is different from SDM660's, as
the latter one has two DSI outputs.
Signed-off-by: Konrad Dybcio
---
drivers/gpu/drm/msm/disp/mdp5/mdp5_cfg.c | 93
1 file changed, 93 insertions(+)
diff --git a
From: Xiaozhe Shi
Add the REVID device driver. The REVID driver will print out the PMIC
revision at probe time.
Signed-off-by: Xiaozhe Shi
[konradyb...@gmail.com: Fast-forward the driver from kernel 4.14 to 5.8,
convert binding to yaml]
Signed-off-by: Konrad Dybcio
---
.../bindings/soc/qcom/q
This also applies to sdm630/636 and their SDA
counterparts.
Signed-off-by: Konrad Dybcio
---
drivers/gpu/drm/msm/dsi/dsi_cfg.c | 21 +
drivers/gpu/drm/msm/dsi/dsi_cfg.h | 1 +
2 files changed, 22 insertions(+)
diff --git a/drivers/gpu/drm/msm/dsi/dsi_cfg.c
b/drivers/gpu/dr
The following changes since commit 3e543a4d30014d45b6bb5d2095554be02153cefc:
Merge tag 'char-misc-5.8-rc6' of
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc into master
(2020-07-16 11:26:40 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/ke
These SoCs make use of the 14nm phy, but at different
addresses than other 14nm units.
Signed-off-by: Konrad Dybcio
---
.../devicetree/bindings/display/msm/dsi.txt| 1 +
drivers/gpu/drm/msm/dsi/phy/dsi_phy.c | 2 ++
drivers/gpu/drm/msm/dsi/phy/dsi_phy.h | 1 +
drivers/gp
Hi!
This series brings most of the changes that have been
brought to sdm630/636/660 SoCs apart from device tree
part (I cannot add anything unless some [1] smmu quirks
are merged.. blame qcom!)
So far, the platform is shaping up nicely, though some
peripherals seem to be living their own lives (I
The following changes since commit ba47d845d715a010f7b51f6f89bae32845e6acb7:
Linux 5.8-rc6 (2020-07-19 15:41:18 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git
tags/driver-core-5.8-rc7
for you to fetch changes up to 29c4a5
QUSB on these SoCs actually uses *almost* the same
configuration that msm8996 does, so we can reuse
the phy_cfg from there with just a single change
(se clock scheme).
Signed-off-by: Konrad Dybcio
---
Documentation/devicetree/bindings/phy/qcom,qusb2-phy.yaml | 1 +
drivers/phy/qualcomm/phy-qcom-
Signed-off-by: Konrad Dybcio
---
Documentation/devicetree/bindings/usb/qcom,dwc3.yaml | 1 +
drivers/usb/dwc3/dwc3-qcom.c | 1 +
2 files changed, 2 insertions(+)
diff --git a/Documentation/devicetree/bindings/usb/qcom,dwc3.yaml
b/Documentation/devicetree/bindings/usb/qco
This will be required in order to support the
modem upstream.
Signed-off-by: Konrad Dybcio
---
drivers/clk/qcom/gcc-sdm660.c | 1 +
include/dt-bindings/clock/qcom,gcc-sdm660.h | 1 +
2 files changed, 2 insertions(+)
diff --git a/drivers/clk/qcom/gcc-sdm660.c b/drivers/clk/qcom/gcc
The following changes since commit ba47d845d715a010f7b51f6f89bae32845e6acb7:
Linux 5.8-rc6 (2020-07-19 15:41:18 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git
tags/staging-5.8-rc7
for you to fetch changes up to faaff976566400
401 - 500 of 640 matches
Mail list logo
