On Wed, Jun 12, 2019 at 03:33:02PM +0200, David Hildenbrand wrote: > s390x crypto is one of the rare modules that returns -EOPNOTSUPP instead of > -ENODEV in case HW support is not available. > > Convert to -ENODEV, so e.g., systemd's systemd-modules-load.service > ignores this error properly. > > v2 -> v3: > - "s390/pkey: Use -ENODEV instead of -EOPNOTSUPP" > -- Also convert pkey_clr2protkey() as requested by Harald > - Add r-b's (thanks!) > > v1 -> v2: > - Include > -- "s390/crypto: ghash: Use -ENODEV instead of -EOPNOTSUPP" > -- "s390/crypto: prng: Use -ENODEV instead of -EOPNOTSUPP" > -- "s390/crypto: sha: Use -ENODEV instead of -EOPNOTSUPP" > > Cc: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> > Cc: "David S. Miller" <davem@xxxxxxxxxxxxx> > Cc: Heiko Carstens <heiko.carstens@xxxxxxxxxx> > Cc: Vasily Gorbik <gor@xxxxxxxxxxxxx> > Cc: Christian Borntraeger <borntraeger@xxxxxxxxxx> > Cc: Harald Freudenberger <freude@xxxxxxxxxxxxx> > Cc: Cornelia Huck <cohuck@xxxxxxxxxx> > > David Hildenbrand (4): > s390/pkey: Use -ENODEV instead of -EOPNOTSUPP > s390/crypto: ghash: Use -ENODEV instead of -EOPNOTSUPP > s390/crypto: prng: Use -ENODEV instead of -EOPNOTSUPP > s390/crypto: sha: Use -ENODEV instead of -EOPNOTSUPP Should I pick these up so they can go upstream via the s390 tree?