summaryrefslogtreecommitdiffstats
path: root/kernel/nsproxy.c
diff options
context:
space:
mode:
authorPalmer Dabbelt <palmer@sifive.com>2018-04-20 12:37:14 -0700
committerPalmer Dabbelt <palmer@sifive.com>2018-06-04 13:46:31 -0700
commit3ed45d7ffa565876e627c4716a8b8b4986a471b1 (patch)
tree2dc61937dfbbbdb65f076c8804a32b2065e92de6 /kernel/nsproxy.c
parent29dcea88779c856c7dc92040a0c01233263101d4 (diff)
downloadlinux-3ed45d7ffa565876e627c4716a8b8b4986a471b1.tar.gz
linux-3ed45d7ffa565876e627c4716a8b8b4986a471b1.tar.bz2
linux-3ed45d7ffa565876e627c4716a8b8b4986a471b1.zip
MAINTAINERS: Add myself as a maintainer for SiFive's drivers
There aren't actually any files in the tree that match these patterns right now, but we've just started submitting our drivers so I thought it would be good to make sure there's at least someone at SiFive who's listed as maintaining them. I'm leaving the RISC-V lists on here because: * As of today, all the RISC-V ASICs that people can actually buy are from SiFive -- though hopefully there'll be more soon! * The RTL for many of our devices is open source, so I anticipate these devices might make they way chips from other vendors. * We may standardize some of these devices as part of a RISC-V specification at some point in the future. I'm a bit swamped right now so I might not be the most active maintainer of these drivers, but I think it'd be good to make sure someone who has hardware access gets CC'd on updates to our drivers just as a sanity check. Hopefully that's an OK way to handle this. Signed-off-by: Palmer Dabbelt <palmer@sifive.com>
Diffstat (limited to 'kernel/nsproxy.c')
0 files changed, 0 insertions, 0 deletions