public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: Sebastian Ott <sebott@linux.ibm.com>
Cc: Peter Oberparleiter <oberpar@linux.ibm.com>,
	Halil Pasic <pasic@linux.ibm.com>,
	Alex Williamson <alex.williamson@redhat.com>,
	Heiko Carstens <heiko.carstens@de.ibm.com>,
	Vasily Gorbik <gor@linux.ibm.com>,
	Christian Borntraeger <borntraeger@de.ibm.com>,
	linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] s390/cio: introduce driver_override on the css bus
Date: Wed, 3 Jul 2019 16:55:06 +0200	[thread overview]
Message-ID: <20190703165506.53d3911c.cohuck@redhat.com> (raw)
In-Reply-To: <20190624091740.1d9c6c1d.cohuck@redhat.com>

On Mon, 24 Jun 2019 09:17:40 +0200
Cornelia Huck <cohuck@redhat.com> wrote:

> On Fri, 21 Jun 2019 18:19:36 +0200 (CEST)
> Sebastian Ott <sebott@linux.ibm.com> wrote:
> 
> > On Thu, 13 Jun 2019, Cornelia Huck wrote:  
> > > Sometimes, we want to control which of the matching drivers
> > > binds to a subchannel device (e.g. for subchannels we want to
> > > handle via vfio-ccw).
> > > 
> > > For pci devices, a mechanism to do so has been introduced in
> > > 782a985d7af2 ("PCI: Introduce new device binding path using
> > > pci_dev.driver_override"). It makes sense to introduce the
> > > driver_override attribute for subchannel devices as well, so
> > > that we can easily extend the 'driverctl' tool (which makes
> > > use of the driver_override attribute for pci).
> > > 
> > > Note that unlike pci we still require a driver override to
> > > match the subchannel type; matching more than one subchannel
> > > type is probably not useful anyway.
> > > 
> > > Signed-off-by: Cornelia Huck <cohuck@redhat.com>    
> > 
> > Reviewed-by: Sebastian Ott <sebott@linux.ibm.com>
> > 
> > Should I take that via our git tree or do you have other patches depending 
> > on this one?
> >   
> 
> No, this patch is stand-alone; everything else is happening in user
> space, so taking it via your tree would be great. Thanks!

Friendly ping (I don't see it on s390/features yet; or is this going
via some other path?)

  reply	other threads:[~2019-07-03 14:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-13 11:08 [PATCH] s390/cio: introduce driver_override on the css bus Cornelia Huck
2019-06-21  9:56 ` Cornelia Huck
2019-06-21 13:37   ` Halil Pasic
2019-06-21 14:05     ` Cornelia Huck
2019-06-21 16:19 ` Sebastian Ott
2019-06-24  7:17   ` Cornelia Huck
2019-07-03 14:55     ` Cornelia Huck [this message]
2019-07-03 15:09       ` Vasily Gorbik
2019-07-03 15:28         ` Cornelia Huck

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190703165506.53d3911c.cohuck@redhat.com \
    --to=cohuck@redhat.com \
    --cc=alex.williamson@redhat.com \
    --cc=borntraeger@de.ibm.com \
    --cc=gor@linux.ibm.com \
    --cc=heiko.carstens@de.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=oberpar@linux.ibm.com \
    --cc=pasic@linux.ibm.com \
    --cc=sebott@linux.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox