Jiri Kosina
cd598d2129
Merge branch 'for-5.17/thrustmaster' into for-linus
2022-01-10 09:59:32 +01:00
Jiri Kosina
f771656344
Merge branch 'for-5.17/magicmouse' into for-linus
...
- proper batter reporting for hid-magicmouse USB-connected devices (José Expósito)
2022-01-10 09:58:34 +01:00
Jiri Kosina
50ae0cfc28
Merge branch 'for-5.17/logitech' into for-linus
...
- add Filipe Laíns as a code reviewer for hid-logitech family of drivers
2022-01-10 09:57:51 +01:00
Jiri Kosina
3551a3ff82
Merge branch 'for-5.17/letsketch' into for-linus
...
- new driver to support for LetSketch device (Hans de Goede)
2022-01-10 09:56:57 +01:00
Jiri Kosina
906095af85
Merge branch 'for-5.17/i2c-hid' into for-linus
...
- PM wakeup support for i2c-hid driver (Matthias Kaehlcke)
2022-01-10 09:56:27 +01:00
Jiri Kosina
c524559acd
Merge branch 'for-5.17/hidraw' into for-linus
...
- locking performance improvement for hidraw code (André Almeida)
2022-01-10 09:55:44 +01:00
Jiri Kosina
fce0d27584
Merge branch 'for-5.17/apple' into for-linus
...
- Apple Magic Keyboard support improvements (José Expósito, Alex Henrie,
Benjamin Berg)
2022-01-10 09:54:31 +01:00
Jiri Kosina
8a2094d679
Merge branch 'for-5.17/core' into for-linus
...
- support for USI style pens (Tero Kristo, Mika Westerberg)
- quirk for devices that need inverted X/Y axes (Alistair Francis)
- small core code cleanups and deduplication (Benjamin Tissoires)
2022-01-10 09:49:13 +01:00
Yuezhang.Mo
3d966521a8
exfat: fix missing REQ_SYNC in exfat_update_bhs()
...
If 'dirsync' is enabled, all directory updates within the
filesystem should be done synchronously. exfat_update_bh()
does as this, but exfat_update_bhs() does not.
Reviewed-by: Andy.Wu <Andy.Wu@sony.com >
Reviewed-by: Aoyama, Wataru <wataru.aoyama@sony.com >
Reviewed-by: Kobayashi, Kento <Kento.A.Kobayashi@sony.com >
Reviewed-by: Sungjong Seo <sj1557.seo@samsung.com >
Signed-off-by: Yuezhang.Mo <Yuezhang.Mo@sony.com >
Signed-off-by: Namjae Jeon <linkinjeon@kernel.org >
2022-01-10 11:00:04 +09:00
Yuezhang.Mo
c71510b3fa
exfat: remove argument 'sector' from exfat_get_dentry()
...
No any function uses argument 'sector', remove it.
Reviewed-by: Andy.Wu <Andy.Wu@sony.com >
Reviewed-by: Aoyama, Wataru <wataru.aoyama@sony.com >
Acked-by: Sungjong Seo <sj1557.seo@samsung.com >
Signed-off-by: Yuezhang.Mo <Yuezhang.Mo@sony.com >
Signed-off-by: Namjae Jeon <linkinjeon@kernel.org >
2022-01-10 11:00:03 +09:00
Namjae Jeon
1ed147e29e
exfat: move super block magic number to magic.h
...
Move exfat superblock magic number from local definition to magic.h.
It is also needed by userspace programs that call fstatfs().
Acked-by: Christian Brauner <christian.brauner@ubuntu.com >
Signed-off-by: Namjae Jeon <linkinjeon@kernel.org >
2022-01-10 11:00:03 +09:00
Christophe Vu-Brugier
92fba084b7
exfat: fix i_blocks for files truncated over 4 GiB
...
In exfat_truncate(), the computation of inode->i_blocks is wrong if
the file is larger than 4 GiB because a 32-bit variable is used as a
mask. This is fixed and simplified by using round_up().
Also fix the same buggy computation in exfat_read_root() and another
(correct) one in exfat_fill_inode(). The latter was fixed another way
last month but can be simplified by using round_up() as well. See:
commit 0c336d6e33 ("exfat: fix incorrect loading of i_blocks for
large files")
Fixes: 98d917047e ("exfat: add file operations")
Cc: stable@vger.kernel.org # v5.7+
Suggested-by: Matthew Wilcox <willy@infradead.org >
Reviewed-by: Sungjong Seo <sj1557.seo@samsung.com >
Signed-off-by: Christophe Vu-Brugier <christophe.vu-brugier@seagate.com >
Signed-off-by: Namjae Jeon <linkinjeon@kernel.org >
2022-01-10 11:00:02 +09:00
Christophe Vu-Brugier
7dee6f57d7
exfat: reuse exfat_inode_info variable instead of calling EXFAT_I()
...
Also add a local "struct exfat_inode_info *ei" variable to
exfat_truncate() to simplify the code.
Signed-off-by: Christophe Vu-Brugier <christophe.vu-brugier@seagate.com >
Signed-off-by: Namjae Jeon <linkinjeon@kernel.org >
2022-01-10 11:00:02 +09:00
Christophe Vu-Brugier
8cf058834b
exfat: make exfat_find_location() static
...
Make exfat_find_location() static.
Signed-off-by: Christophe Vu-Brugier <christophe.vu-brugier@seagate.com >
Signed-off-by: Namjae Jeon <linkinjeon@kernel.org >
2022-01-10 11:00:01 +09:00
Christophe Vu-Brugier
6fa96cd5ad
exfat: fix typos in comments
...
Fix typos in comments.
Signed-off-by: Christophe Vu-Brugier <christophe.vu-brugier@seagate.com >
Signed-off-by: Namjae Jeon <linkinjeon@kernel.org >
2022-01-10 11:00:01 +09:00
Christophe Vu-Brugier
e21a28bbcc
exfat: simplify is_valid_cluster()
...
Simplify is_valid_cluster().
Signed-off-by: Christophe Vu-Brugier <christophe.vu-brugier@seagate.com >
Signed-off-by: Namjae Jeon <linkinjeon@kernel.org >
2022-01-10 11:00:00 +09:00
Eric Biggers
f029cedb9b
MAINTAINERS: add entries for block layer documentation
...
Include Documentation/block/ and Documentation/ABI/stable/sysfs-block in
the "BLOCK LAYER" maintainers file entry.
Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org >
Reviewed-by: Hannes Reinecke <hare@suse.de >
Reviewed-by: Martin K. Petersen <martin.petersen@oracle.com >
Reviewed-by: Bart Van Assche <bvanassche@acm.org >
Signed-off-by: Eric Biggers <ebiggers@google.com >
Link: https://lore.kernel.org/r/20211209003833.6396-9-ebiggers@kernel.org
Signed-off-by: Jens Axboe <axboe@kernel.dk >
2022-01-09 18:59:10 -07:00
Eric Biggers
208e4f9c00
docs: block: remove queue-sysfs.rst
...
This has been replaced by Documentation/ABI/stable/sysfs-block, which is
the correct place for sysfs documentation.
Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org >
Reviewed-by: Hannes Reinecke <hare@suse.de >
Reviewed-by: Martin K. Petersen <martin.petersen@oracle.com >
Reviewed-by: Bart Van Assche <bvanassche@acm.org >
Signed-off-by: Eric Biggers <ebiggers@google.com >
Link: https://lore.kernel.org/r/20211209003833.6396-8-ebiggers@kernel.org
Signed-off-by: Jens Axboe <axboe@kernel.dk >
2022-01-09 18:59:10 -07:00
Eric Biggers
8bc2f7c670
docs: sysfs-block: document virt_boundary_mask
...
/sys/block/<disk>/queue/virt_boundary_mask is completely undocumented.
Document it.
Reviewed-by: Bart Van Assche <bvanassche@acm.org >
Signed-off-by: Eric Biggers <ebiggers@google.com >
Link: https://lore.kernel.org/r/20211209003833.6396-7-ebiggers@kernel.org
Signed-off-by: Jens Axboe <axboe@kernel.dk >
2022-01-09 18:59:10 -07:00
Eric Biggers
1163010418
docs: sysfs-block: document stable_writes
...
/sys/block/<disk>/queue/stable_writes is completely undocumented.
Document it.
Reviewed-by: Bart Van Assche <bvanassche@acm.org >
Signed-off-by: Eric Biggers <ebiggers@google.com >
Link: https://lore.kernel.org/r/20211209003833.6396-6-ebiggers@kernel.org
Signed-off-by: Jens Axboe <axboe@kernel.dk >
2022-01-09 18:59:10 -07:00
Eric Biggers
849ab826e1
docs: sysfs-block: fill in missing documentation from queue-sysfs.rst
...
sysfs documentation is supposed to go in Documentation/ABI/.
However, /sys/block/<disk>/queue/* are documented in
Documentation/block/queue-sysfs.rst, and sometimes redundantly in
Documentation/ABI/stable/sysfs-block too.
Let's consolidate this documentation into Documentation/ABI/.
Therefore, copy the relevant docs from queue-sysfs.rst into sysfs-block.
This primarily means adding the 25 missing files that were documented in
queue-sysfs.rst only, as well as mentioning the RO/RW status of files.
Documentation/ABI/ requires "Date" and "Contact" fields. For the Date
fields, I used the date of the commit which added support for each file.
For the "Contact" fields, I used linux-block.
Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org >
Reviewed-by: Hannes Reinecke <hare@suse.de >
Reviewed-by: Martin K. Petersen <martin.petersen@oracle.com >
Reviewed-by: Bart Van Assche <bvanassche@acm.org >
Signed-off-by: Eric Biggers <ebiggers@google.com >
Link: https://lore.kernel.org/r/20211209003833.6396-5-ebiggers@kernel.org
Signed-off-by: Jens Axboe <axboe@kernel.dk >
2022-01-09 18:59:10 -07:00
Eric Biggers
8b0551a74b
docs: sysfs-block: add contact for nomerges
...
The nomerges file was missing a "Contact" entry. Use linux-block.
Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org >
Reviewed-by: Hannes Reinecke <hare@suse.de >
Reviewed-by: Martin K. Petersen <martin.petersen@oracle.com >
Reviewed-by: Bart Van Assche <bvanassche@acm.org >
Signed-off-by: Eric Biggers <ebiggers@google.com >
Link: https://lore.kernel.org/r/20211209003833.6396-4-ebiggers@kernel.org
Signed-off-by: Jens Axboe <axboe@kernel.dk >
2022-01-09 18:59:10 -07:00
Eric Biggers
07c9093c42
docs: sysfs-block: sort alphabetically
...
Sort the documentation for the files alphabetically by file path so that
there is a logical order and it's clear where to add new files.
With two small exceptions, this patch doesn't change the documentation
itself and just reorders it:
- In /sys/block/<disk>/<part>/stat, I replaced <part> with <partition>
to be consistent with the other files.
- The description for /sys/block/<disk>/<part>/stat referred to another
file "above", which I reworded.
Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org >
Reviewed-by: Hannes Reinecke <hare@suse.de >
Reviewed-by: Martin K. Petersen <martin.petersen@oracle.com >
Reviewed-by: Bart Van Assche <bvanassche@acm.org >
Signed-off-by: Eric Biggers <ebiggers@google.com >
Link: https://lore.kernel.org/r/20211209003833.6396-3-ebiggers@kernel.org
Signed-off-by: Jens Axboe <axboe@kernel.dk >
2022-01-09 18:59:10 -07:00
Eric Biggers
ae7a7a5349
docs: sysfs-block: move to stable directory
...
The block layer sysfs ABI is widely used by userspace software and is
considered stable.
Reviewed-by: Martin K. Petersen <martin.petersen@oracle.com >
Reviewed-by: Bart Van Assche <bvanassche@acm.org >
Signed-off-by: Eric Biggers <ebiggers@google.com >
Link: https://lore.kernel.org/r/20211209003833.6396-2-ebiggers@kernel.org
Signed-off-by: Jens Axboe <axboe@kernel.dk >
2022-01-09 18:59:10 -07:00
Ming Lei
9d497e2941
block: don't protect submit_bio_checks by q_usage_counter
...
Commit cc9c884dd7 ("block: call submit_bio_checks under q_usage_counter")
uses q_usage_counter to protect submit_bio_checks for avoiding IO after
disk is deleted by del_gendisk().
Turns out the protection isn't necessary, because once
blk_mq_freeze_queue_wait() in del_gendisk() returns:
1) all in-flight IO has been done
2) all new IO will be failed in __bio_queue_enter() because
q_usage_counter is dead, and GD_DEAD is set
3) both disk and request queue instance are safe since caller of
submit_bio() guarantees that the disk can't be closed.
Once submit_bio_checks() needn't the protection of q_usage_counter, we can
move submit_bio_checks before calling blk_mq_submit_bio() and
->submit_bio(). With this change, we needn't to throttle queue with
holding one allocated request, then precise driver tag or request won't be
wasted in throttling. Meantime we can unify the bio check for both bio
based and request based driver.
Cc: Christoph Hellwig <hch@lst.de >
Signed-off-by: Ming Lei <ming.lei@redhat.com >
Link: https://lore.kernel.org/r/20220104134223.590803-1-ming.lei@redhat.com
Signed-off-by: Jens Axboe <axboe@kernel.dk >
2022-01-09 18:54:52 -07:00
Colin Ian King
00f5117c5f
hwmon: (nzxt-smart2) make array detect_fans_report static const
...
Don't populate the read-only array detect_fans_report on the stack but
instead it static const. Also makes the object code a little smaller.
Signed-off-by: Colin Ian King <colin.i.king@gmail.com >
Link: https://lore.kernel.org/r/20220109194558.45811-1-colin.i.king@gmail.com
Signed-off-by: Guenter Roeck <linux@roeck-us.net >
2022-01-09 17:10:58 -08:00
Rob Herring
8650381f33
dt-bindings: net: Add missing properties used in examples
...
With 'unevaluatedProperties' support implemented, the following warnings
are generated in the net bindings:
Documentation/devicetree/bindings/net/qca,ar71xx.example.dt.yaml: ethernet@19000000: Unevaluated properties are not allowed ('qca,ethcfg' was unexpected)
Documentation/devicetree/bindings/net/stm32-dwmac.example.dt.yaml: ethernet@40028000: Unevaluated properties are not allowed ('reg-names', 'snps,pbl' were unexpected)
Documentation/devicetree/bindings/net/ti,cpsw-switch.example.dt.yaml: mdio@1000: Unevaluated properties are not allowed ('clocks', 'clock-names' were unexpected)
Documentation/devicetree/bindings/net/ti,k3-am654-cpsw-nuss.example.dt.yaml: mdio@f00: Unevaluated properties are not allowed ('clocks', 'clock-names' were unexpected)
Add the missing properties/nodes as necessary.
Cc: "David S. Miller" <davem@davemloft.net >
Cc: Jakub Kicinski <kuba@kernel.org >
Cc: "Andreas Färber" <afaerber@suse.de >
Cc: Manivannan Sadhasivam <mani@kernel.org >
Cc: Maxime Coquelin <mcoquelin.stm32@gmail.com >
Cc: Alexandre Torgue <alexandre.torgue@foss.st.com >
Cc: Nobuhiro Iwamatsu <nobuhiro1.iwamatsu@toshiba.co.jp >
Cc: Cristian Ciocaltea <cristian.ciocaltea@gmail.com >
Cc: "G. Jaya Kumaran" <vineetha.g.jaya.kumaran@intel.com >
Cc: Oleksij Rempel <o.rempel@pengutronix.de >
Cc: Christophe Roullier <christophe.roullier@foss.st.com >
Cc: Grygorii Strashko <grygorii.strashko@ti.com >
Cc: netdev@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org
Cc: linux-actions@lists.infradead.org
Cc: linux-stm32@st-md-mailman.stormreply.com
Signed-off-by: Rob Herring <robh@kernel.org >
Link: https://lore.kernel.org/r/20211206174153.2296977-1-robh@kernel.org
2022-01-09 19:09:36 -06:00
Rob Herring
1d01efaf18
dt-bindings: net: snps,dwmac: Enable burst length properties for more compatibles
...
With 'unevaluatedProperties' support implemented, the properties
'snps,pbl', 'snps,txpbl', and 'snps,rxpbl' are not allowed in the
examples for some of the DWMAC versions:
Documentation/devicetree/bindings/net/intel,dwmac-plat.example.dt.yaml: ethernet@3a000000: Unevaluated properties are not allowed ('snps,pbl', 'mdio0' were unexpected)
Documentation/devicetree/bindings/net/stm32-dwmac.example.dt.yaml: ethernet@5800a000: Unevaluated properties are not allowed ('reg-names', 'snps,pbl' were unexpected)
Documentation/devicetree/bindings/net/stm32-dwmac.example.dt.yaml: ethernet@40028000: Unevaluated properties are not allowed ('reg-names', 'snps,pbl' were unexpected)
Documentation/devicetree/bindings/net/stm32-dwmac.example.dt.yaml: ethernet@40027000: Unevaluated properties are not allowed ('reg-names', 'snps,pbl' were unexpected)
Documentation/devicetree/bindings/net/toshiba,visconti-dwmac.example.dt.yaml: ethernet@28000000: Unevaluated properties are not allowed ('snps,txpbl', 'snps,rxpbl', 'mdio0' were unexpected)
This appears to be an oversight, so fix it by allowing the properties
on the v3.50a, v4.10a, and v4.20a versions of the DWMAC.
Cc: "David S. Miller" <davem@davemloft.net >
Cc: Jakub Kicinski <kuba@kernel.org >
Cc: Alexandre Torgue <alexandre.torgue@foss.st.com >
Cc: Giuseppe Cavallaro <peppe.cavallaro@st.com >
Cc: Jose Abreu <joabreu@synopsys.com >
Cc: netdev@vger.kernel.org
Signed-off-by: Rob Herring <robh@kernel.org >
Reviewed-by: Thierry Reding <treding@nvidia.com >
Link: https://lore.kernel.org/r/20211206174147.2296770-1-robh@kernel.org
2022-01-09 19:09:35 -06:00
Rob Herring
ad31ce56c4
dt-bindings: net: mdio: Allow any child node name
...
An MDIO bus can have devices other than ethernet PHYs on it, so it
should allow for any node name rather than just 'ethernet-phy'.
Cc: Andrew Lunn <andrew@lunn.ch >
Cc: Heiner Kallweit <hkallweit1@gmail.com >
Cc: Russell King <linux@armlinux.org.uk >
Cc: "David S. Miller" <davem@davemloft.net >
Cc: Jakub Kicinski <kuba@kernel.org >
Cc: Florian Fainelli <f.fainelli@gmail.com >
Cc: netdev@vger.kernel.org
Signed-off-by: Rob Herring <robh@kernel.org >
Reviewed-by: Thierry Reding <treding@nvidia.com >
Acked-by: Florian Fainelli <f.fainelli@gmail.com >
Link: https://lore.kernel.org/r/20211206174139.2296497-1-robh@kernel.org
2022-01-09 19:09:35 -06:00
Jakub Kicinski
8aaaf2f3af
Merge git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net
...
Merge in fixes directly in prep for the 5.17 merge window.
No conflicts.
Signed-off-by: Jakub Kicinski <kuba@kernel.org >
2022-01-09 17:00:17 -08:00
Christian Schoenebeck
15e2721b19
net/9p: show error message if user 'msize' cannot be satisfied
...
If user supplied a large value with the 'msize' option, then
client would silently limit that 'msize' value to the maximum
value supported by transport. That's a bit confusing for users
of not having any indication why the preferred 'msize' value
could not be satisfied.
Link: https://lkml.kernel.org/r/783ba37c1566dd715b9a67d437efa3b77e3cd1a7.1640870037.git.linux_oss@crudebyte.com
Reported-by: Vivek Goyal <vgoyal@redhat.com >
Signed-off-by: Christian Schoenebeck <linux_oss@crudebyte.com >
Signed-off-by: Dominique Martinet <asmadeus@codewreck.org >
2022-01-10 10:00:09 +09:00
Christian Schoenebeck
deadd8746e
MAINTAINERS: 9p: add Christian Schoenebeck as reviewer
...
Volunteering as reviewer for 9p patches. As I am quite familiar with the
9p code base in the Linux kernel already, plus being current maintainer
of 9p in QEMU this move probably makes sense.
Link: https://lkml.kernel.org/r/E1n4jXv-000445-GK@lizzy.crudebyte.com
Signed-off-by: Christian Schoenebeck <linux_oss@crudebyte.com >
[Dominique: reworded description]
Signed-off-by: Dominique Martinet <asmadeus@codewreck.org >
2022-01-10 10:00:09 +09:00
Christian Brauner
3cb6ee9914
9p: only copy valid iattrs in 9P2000.L setattr implementation
...
The 9P2000.L setattr method v9fs_vfs_setattr_dotl() copies struct iattr
values without checking whether they are valid causing unitialized
values to be copied. The 9P2000 setattr method v9fs_vfs_setattr() method
gets this right. Check whether struct iattr fields are valid first
before copying in v9fs_vfs_setattr_dotl() too and make sure that all
other fields are set to 0 apart from {g,u}id which should be set to
INVALID_{G,U}ID. This ensure that they can be safely sent over the wire
or printed for debugging later on.
Link: https://lkml.kernel.org/r/20211129114434.3637938-1-brauner@kernel.org
Link: https://lkml.kernel.org/r/000000000000a0d53f05d1c72a4c%40google.com
Cc: Eric Van Hensbergen <ericvh@gmail.com >
Cc: Latchesar Ionkov <lucho@ionkov.net >
Cc: Dominique Martinet <asmadeus@codewreck.org >
Cc: stable@kernel.org
Cc: v9fs-developer@lists.sourceforge.net
Reported-by: syzbot+dfac92a50024b54acaa4@syzkaller.appspotmail.com
Signed-off-by: Christian Brauner <christian.brauner@ubuntu.com >
[Dominique: do not set a/mtime with just ATTR_A/MTIME as discussed]
Signed-off-by: Dominique Martinet <asmadeus@codewreck.org >
2022-01-10 10:00:09 +09:00
Zhang Mingyu
a7a427d154
9p: Use BUG_ON instead of if condition followed by BUG.
...
This issue was detected with the help of Coccinelle.
Link: https://lkml.kernel.org/r/20211112092547.9153-1-zhang.mingyu@zte.com.cn
Reported-by: Zeal Robot <zealci@zte.com.cn >
Signed-off-by: Zhang Mingyu <zhang.mingyu@zte.com.cn >
Signed-off-by: Dominique Martinet <asmadeus@codewreck.org >
2022-01-10 10:00:09 +09:00
Thomas Weißschuh
019641d1b5
net/p9: load default transports
...
Now that all transports are split into modules it may happen that no
transports are registered when v9fs_get_default_trans() is called.
When that is the case try to load more transports from modules.
Link: https://lkml.kernel.org/r/20211103193823.111007-5-linux@weissschuh.net
Signed-off-by: Thomas Weißschuh <linux@weissschuh.net >
[Dominique: constify v9fs_get_trans_by_name argument as per patch1v2]
Signed-off-by: Dominique Martinet <asmadeus@codewreck.org >
2022-01-10 10:00:09 +09:00
Thomas Weißschuh
99aa673e29
9p/xen: autoload when xenbus service is available
...
Link: https://lkml.kernel.org/r/20211103193823.111007-4-linux@weissschuh.net
Signed-off-by: Thomas Weißschuh <linux@weissschuh.net >
Signed-off-by: Dominique Martinet <asmadeus@codewreck.org >
2022-01-10 10:00:09 +09:00
Thomas Weißschuh
1c582c6dc4
9p/trans_fd: split into dedicated module
...
This allows these transports only to be used when needed.
Link: https://lkml.kernel.org/r/20211103193823.111007-3-linux@weissschuh.net
Signed-off-by: Thomas Weißschuh <linux@weissschuh.net >
[Dominique: Kconfig NET_9P_FD: -depends VIRTIO, +default NET_9P]
Signed-off-by: Dominique Martinet <asmadeus@codewreck.org >
2022-01-10 09:58:30 +09:00
Qin Jian
0bbeb64cb0
dt-bindings: vendor-prefixes: Add Sunplus
...
Add vendor prefix for Sunplus Technology Co., Ltd. (http://www.sunplus.com )
Acked-by: Rob Herring <robh@kernel.org >
Signed-off-by: Qin Jian <qinjian@cqplus1.com >
Signed-off-by: Rob Herring <robh@kernel.org >
Link: https://lore.kernel.org/r/2e74a1339a5ea54d92fdc4d1998a2b169e23b82b.1640154492.git.qinjian@cqplus1.com
2022-01-09 18:56:48 -06:00
Benjamin Yim
208dd45d8d
tcp: tcp_send_challenge_ack delete useless param skb
...
After this parameter is passed in, there is no usage, and deleting it will
not bring any impact.
Reviewed-by: Eric Dumazet <edumazet@google.com >
Signed-off-by: Benjamin Yim <yan2228598786@gmail.com >
Link: https://lore.kernel.org/r/20220109130824.2776-1-yan2228598786@gmail.com
Signed-off-by: Jakub Kicinski <kuba@kernel.org >
2022-01-09 16:52:21 -08:00
Christophe JAILLET
0959a82ab3
net/qla3xxx: Remove useless DMA-32 fallback configuration
...
As stated in [1], dma_set_mask() with a 64-bit mask never fails if
dev->dma_mask is non-NULL.
So, if it fails, the 32 bits case will also fail for the same reason.
So, if dma_set_mask_and_coherent() succeeds, 'pci_using_dac' is known to be
1.
Simplify code and remove some dead code accordingly.
[1]: https://lkml.org/lkml/2021/6/7/398
Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr >
Link: https://lore.kernel.org/r/3011689e8c77d49d7e44509d5a8241320ec408c5.1641754134.git.christophe.jaillet@wanadoo.fr
Signed-off-by: Jakub Kicinski <kuba@kernel.org >
2022-01-09 16:52:21 -08:00
Christophe JAILLET
7ac2d77c97
rocker: Remove useless DMA-32 fallback configuration
...
As stated in [1], dma_set_mask() with a 64-bit mask never fails if
dev->dma_mask is non-NULL.
So, if it fails, the 32 bits case will also fail for the same reason.
Simplify code and remove some dead code accordingly.
[1]: https://lkml.org/lkml/2021/6/7/398
Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr >
Link: https://lore.kernel.org/r/9ba2d13099d216f3df83e50ad33a05504c90fe7c.1641744274.git.christophe.jaillet@wanadoo.fr
Signed-off-by: Jakub Kicinski <kuba@kernel.org >
2022-01-09 16:52:21 -08:00
Christophe JAILLET
004464835b
hinic: Remove useless DMA-32 fallback configuration
...
As stated in [1], dma_set_mask() with a 64-bit mask never fails if
dev->dma_mask is non-NULL.
So, if it fails, the 32 bits case will also fail for the same reason.
Simplify code and remove some dead code accordingly.
[1]: https://lkml.org/lkml/2021/6/7/398
Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr >
Link: https://lore.kernel.org/r/23541c28df8d0dcd3663b5dbe0f76af71e70e9cc.1641743855.git.christophe.jaillet@wanadoo.fr
Signed-off-by: Jakub Kicinski <kuba@kernel.org >
2022-01-09 16:52:21 -08:00
Christophe JAILLET
e20a471256
lan743x: Remove useless DMA-32 fallback configuration
...
As stated in [1], dma_set_mask() with a 64-bit mask never fails if
dev->dma_mask is non-NULL.
So, if it fails, the 32 bits case will also fail for the same reason.
Simplify code and remove some dead code accordingly.
[1]: https://lkml.org/lkml/2021/6/7/398
Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr >
Link: https://lore.kernel.org/r/ef548716606f257939df9738a801f15b6edf2568.1641743405.git.christophe.jaillet@wanadoo.fr
Signed-off-by: Jakub Kicinski <kuba@kernel.org >
2022-01-09 16:52:21 -08:00
Christophe JAILLET
cfcfc8f5a5
net: enetc: Remove useless DMA-32 fallback configuration
...
As stated in [1], dma_set_mask() with a 64-bit mask never fails if
dev->dma_mask is non-NULL.
So, if it fails, the 32 bits case will also fail for the same reason.
Simplify code and remove some dead code accordingly.
[1]: https://lkml.org/lkml/2021/6/7/398
Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr >
Link: https://lore.kernel.org/r/dbecd4eb49a9586ee343b5473dda4b84c42112e9.1641742884.git.christophe.jaillet@wanadoo.fr
Signed-off-by: Jakub Kicinski <kuba@kernel.org >
2022-01-09 16:52:20 -08:00
Christophe JAILLET
030f9ce8c7
cxgb4vf: Remove useless DMA-32 fallback configuration
...
As stated in [1], dma_set_mask() with a 64-bit mask never fails if
dev->dma_mask is non-NULL.
So, if it fails, the 32 bits case will also fail for the same reason.
So, if dma_set_mask_and_coherent() succeeds, 'pci_using_dac' is known to be
1.
Simplify code and remove some dead code accordingly.
[1]: https://lkml.org/lkml/2021/6/7/398
Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr >
Link: https://lore.kernel.org/r/b14986ea39cea2ca9a6cd0476a3fc167c853ee67.1641736772.git.christophe.jaillet@wanadoo.fr
Signed-off-by: Jakub Kicinski <kuba@kernel.org >
2022-01-09 16:52:20 -08:00
Christophe JAILLET
7fc7fc5da6
cxgb4: Remove useless DMA-32 fallback configuration
...
As stated in [1], dma_set_mask() with a 64-bit mask never fails if
dev->dma_mask is non-NULL.
So, if it fails, the 32 bits case will also fail for the same reason.
So, if dma_set_mask_and_coherent() succeeds, 'highdma' is known to be true.
Simplify code and remove some dead code accordingly.
[1]: https://lkml.org/lkml/2021/6/7/398
Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr >
Link: https://lore.kernel.org/r/56db10d53be0897ff1be5f37d64b91cb7e1d932c.1641736387.git.christophe.jaillet@wanadoo.fr
Signed-off-by: Jakub Kicinski <kuba@kernel.org >
2022-01-09 16:52:20 -08:00
Christophe JAILLET
544bdad074
cxgb3: Remove useless DMA-32 fallback configuration
...
As stated in [1], dma_set_mask() with a 64-bit mask never fails if
dev->dma_mask is non-NULL.
So, if it fails, the 32 bits case will also fail for the same reason.
So, if dma_set_mask_and_coherent() succeeds, 'pci_using_dac' is known to be
1.
Simplify code and remove some dead code accordingly.
[1]: https://lkml.org/lkml/2021/6/7/398
Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr >
Link: https://lore.kernel.org/r/a0e2539aefb0034091aca02c98440ea9459f1258.1641736234.git.christophe.jaillet@wanadoo.fr
Signed-off-by: Jakub Kicinski <kuba@kernel.org >
2022-01-09 16:52:20 -08:00
Christophe JAILLET
3aa440503b
bnx2x: Remove useless DMA-32 fallback configuration
...
As stated in [1], dma_set_mask() with a 64-bit mask never fails if
dev->dma_mask is non-NULL.
So, if it fails, the 32 bits case will also fail for the same reason.
Moreover, dma_set_mask_and_coherent() returns 0 or -EIO, so the return
code of the function can be used directly.
Finally, inline bnx2x_set_coherency_mask() because it is now only a wrapper
for a single dma_set_mask_and_coherent() call.
Simplify code and remove some dead code accordingly.
[1]: https://lkml.org/lkml/2021/6/7/398
Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr >
Link: https://lore.kernel.org/r/29608a525876afddceabf8f11b2ba606da8748fc.1641730747.git.christophe.jaillet@wanadoo.fr
Signed-off-by: Jakub Kicinski <kuba@kernel.org >
2022-01-09 16:52:19 -08:00
Christophe JAILLET
948f6b297f
et131x: Remove useless DMA-32 fallback configuration
...
As stated in [1], dma_set_mask() with a 64-bit mask never fails if
dev->dma_mask is non-NULL.
So, if it fails, the 32 bits case will also fail for the same reason.
Moreover, dma_set_mask_and_coherent() returns 0 or -EIO, so the return
code of the function can be used directly. There is no need to 'rc = -EIO'
explicitly.
Simplify code and remove some dead code accordingly.
[1]: https://lkml.org/lkml/2021/6/7/398
Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr >
Link: https://lore.kernel.org/r/b9aa46e7e5a5aa61f56aac5ea439930f41ad9946.1641726804.git.christophe.jaillet@wanadoo.fr
Signed-off-by: Jakub Kicinski <kuba@kernel.org >
2022-01-09 16:52:19 -08:00
Christophe JAILLET
942e78916f
be2net: Remove useless DMA-32 fallback configuration
...
As stated in [1], dma_set_mask() with a 64-bit mask never fails if
dev->dma_mask is non-NULL.
So, if it fails, the 32 bits case will also fail for the same reason.
So if dma_set_mask_and_coherent() succeeds, 'netdev->features' will have
NETIF_F_HIGHDMA in all cases. Move the assignment of this feature in
be_netdev_init() instead be_probe() which is a much logical place.
Simplify code and remove some dead code accordingly.
[1]: https://lkml.org/lkml/2021/6/7/398
Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr >
Link: https://lore.kernel.org/r/637696d7141faa68c29fc34b70f9aa67d5e605f0.1641718999.git.christophe.jaillet@wanadoo.fr
Signed-off-by: Jakub Kicinski <kuba@kernel.org >
2022-01-09 16:52:19 -08:00