summaryrefslogtreecommitdiff
path: root/fs/jffs2/writev.c
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2019-01-14 05:51:08 +1200
committerLinus Torvalds <torvalds@linux-foundation.org>2019-01-14 05:51:08 +1200
commit72d657dd2115804b93bde4b77e426cc2de70eebf (patch)
tree13f5b1b6e7cebfe80187654563868457b29e9034 /fs/jffs2/writev.c
parentf7c1038bc7597af5d6809c5b3e0352627cef5c07 (diff)
parent735df0ff6ece7b8759a744158f5d246fae4739f4 (diff)
Merge tag 'driver-core-5.0-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core
Pull driver core fixes from Greg KH: "Here is one small sysfs change, and a documentation update for 5.0-rc2 The sysfs change moves from using BUG_ON to WARN_ON, as discussed in an email thread on lkml while trying to track down another driver bug. sysfs should not be crashing and preventing people from seeing where they went wrong. Now it properly recovers and warns the developer. The documentation update removes the use of BUS_ATTR() as the kernel is moving away from this to use the specific BUS_ATTR_RW() and friends instead. There are pending patches in all of the different subsystems to remove the last users of this macro, but for now, don't advertise it should be used anymore to keep new ones from being introduced. Both have been in linux-next with no reported issues" * tag 'driver-core-5.0-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core: Documentation: driver core: remove use of BUS_ATTR sysfs: convert BUG_ON to WARN_ON
Diffstat (limited to 'fs/jffs2/writev.c')
0 files changed, 0 insertions, 0 deletions