From: Cornelia Huck <cohuck@redhat.com>
To: Vineeth Vijayan <vneethv@linux.vnet.ibm.com>
Cc: Peter Oberparleiter <oberpar@linux.ibm.com>,
Vineeth Vijayan <vneethv@linux.ibm.com>,
linux-s390@vger.kernel.org, Eric Farman <farman@linux.ibm.com>,
Halil Pasic <pasic@linux.ibm.com>,
Boris Fiuczynski <fiuczy@linux.ibm.com>
Subject: Re: [RFD] uevent handling for subchannels
Date: Tue, 15 Sep 2020 12:31:01 +0200 [thread overview]
Message-ID: <20200915123101.0861b091.cohuck@redhat.com> (raw)
In-Reply-To: <923020f2-e722-a6ba-fcb4-08dd8228fc00@linux.vnet.ibm.com>
On Tue, 15 Sep 2020 12:25:32 +0200
Vineeth Vijayan <vneethv@linux.vnet.ibm.com> wrote:
> Hi Conny,
> Thank you for the ping. This is pending for a long time and we just resumed
> looking at this approach. Me and Peter had a short discussion on this and we
> are trying to do some cleaning as well on the CIO layer while working
> with the
> new approach.
>
> There are few uncertainties with the new approach, which we would like
> to clarify
> and i am trying to test it.For example, the impact on the way
> cio-console driver works.
Yes, the console might be fun.
> So, as discussed with Peter, let me make a smaller draft which will
> consolidate
> your approach and the "cleaning" part that we would like to do.
>
> As mentioned, i will resume working on this and get back to you with
> myfindings.
Thanks for the update; I'll do my best to find some time to look at any
patches you send.
next prev parent reply other threads:[~2020-09-15 10:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-03 10:40 [RFD] uevent handling for subchannels Cornelia Huck
2020-04-17 12:38 ` Cornelia Huck
2020-04-20 15:29 ` Vineeth Vijayan
2020-04-23 14:52 ` Vineeth Vijayan
2020-04-23 16:20 ` Cornelia Huck
2020-04-27 10:10 ` Peter Oberparleiter
2020-04-30 10:43 ` Cornelia Huck
2020-06-29 11:56 ` Cornelia Huck
2020-07-01 9:23 ` Cornelia Huck
2020-09-14 11:46 ` Cornelia Huck
2020-09-15 10:25 ` Vineeth Vijayan
2020-09-15 10:31 ` Cornelia Huck [this message]
2020-04-23 15:55 ` Halil Pasic
2020-04-23 16:27 ` 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=20200915123101.0861b091.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=farman@linux.ibm.com \
--cc=fiuczy@linux.ibm.com \
--cc=linux-s390@vger.kernel.org \
--cc=oberpar@linux.ibm.com \
--cc=pasic@linux.ibm.com \
--cc=vneethv@linux.ibm.com \
--cc=vneethv@linux.vnet.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.