From: Dan Williams <email@example.com> To: Ranjani Sridharan <firstname.lastname@example.org> Cc: Greg KH <email@example.com>, Jason Gunthorpe <firstname.lastname@example.org>, Mark Brown <email@example.com>, Takashi Iwai <firstname.lastname@example.org>, Pierre-Louis Bossart <email@example.com>, Jeff Kirsher <firstname.lastname@example.org>, David Miller <email@example.com>, Netdev <firstname.lastname@example.org>, linux-rdma <email@example.com>, firstname.lastname@example.org, email@example.com, Fred Oh <firstname.lastname@example.org>, email@example.com Subject: Re: [net-next v4 10/12] ASoC: SOF: Introduce descriptors for SOF client Date: Mon, 6 Jul 2020 16:02:57 -0700 [thread overview] Message-ID: <CAPcyv4g9xCMh5cQF0qbObpHX5ckMK_SWPO12BcXF2ijn8MnckA@mail.gmail.com> (raw) In-Reply-To: <firstname.lastname@example.org> On Thu, Jul 2, 2020 at 6:44 AM Ranjani Sridharan <email@example.com> wrote: [..] > > > Hi Jason, > > > > > > We're addressing the naming in the next version as well. We've had > > > several people reject the name virtual bus and we've narrowed in on > > > "ancillary bus" for the new name suggesting that we have the core > > > device that is attached to the primary bus and one or more sub- > > > devices > > > that are attached to the ancillary bus. Please let us know what you > > > think of it. > > > > I'm thinking that the primary person who keeps asking you to create > > this > > "virtual bus" was not upset about that name, nor consulted, so why > > are > > you changing this? :( > > > > Right now this feels like the old technique of "keep throwing crap at > > a > > maintainer until they get so sick of it that they do the work > > themselves..." > > Hi Greg, > > It wasnt our intention to frustrate you with the name change but in the > last exchange you had specifically asked for signed-off-by's from other > Intel developers. In that process, one of the recent feedback from some > of them was about the name being misleading and confusing. > > If you feel strongly about the keeping name "virtual bus", please let > us know and we can circle back with them again. Hey Greg, Feel free to blame me for the naming thrash it was part of my internal review feedback trying to crispen the definition of this facility. I was expecting the next revision to come with the internal reviewed-by and an explanation of all the items that were changed during that review. Ranjani, is the next rev ready to go out with the review items identified? Let's just proceed with the current direction of the review tags that Greg asked for, name changes and all, and iterate the next details on the list with the new patches in hand.
next prev parent reply other threads:[~2020-07-06 23:03 UTC|newest] Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-20 7:02 [net-next v4 00/12][pull request] 100GbE Intel Wired LAN Driver Updates 2020-05-19 Jeff Kirsher 2020-05-20 7:02 ` [net-next v4 01/12] Implementation of Virtual Bus Jeff Kirsher 2020-05-21 14:57 ` Parav Pandit 2020-05-21 17:43 ` gregkh 2020-05-21 20:10 ` Jason Gunthorpe 2020-05-20 7:02 ` [net-next v4 02/12] ice: Create and register virtual bus for RDMA Jeff Kirsher 2020-05-20 7:02 ` [net-next v4 03/12] ice: Complete RDMA peer registration Jeff Kirsher 2020-05-20 7:02 ` [net-next v4 04/12] ice: Support resource allocation requests Jeff Kirsher 2020-05-20 7:02 ` [net-next v4 05/12] ice: Enable event notifications Jeff Kirsher 2020-05-20 7:02 ` [net-next v4 06/12] ice: Allow reset operations Jeff Kirsher 2020-05-20 7:02 ` [net-next v4 07/12] ice: Pass through communications to VF Jeff Kirsher 2020-05-20 7:02 ` [net-next v4 08/12] i40e: Move client header location Jeff Kirsher 2020-05-20 7:02 ` [net-next v4 09/12] i40e: Register a virtbus device to provide RDMA Jeff Kirsher 2020-05-20 7:02 ` [net-next v4 10/12] ASoC: SOF: Introduce descriptors for SOF client Jeff Kirsher 2020-05-20 7:20 ` Greg KH 2020-05-20 12:54 ` Jason Gunthorpe 2020-05-20 12:57 ` Jason Gunthorpe 2020-05-21 21:11 ` Ranjani Sridharan 2020-05-21 23:34 ` Jason Gunthorpe 2020-05-22 14:29 ` Pierre-Louis Bossart 2020-05-22 14:55 ` Jason Gunthorpe 2020-05-22 15:33 ` Pierre-Louis Bossart 2020-05-22 17:10 ` Jason Gunthorpe 2020-05-22 18:35 ` Pierre-Louis Bossart 2020-05-22 18:40 ` Jason Gunthorpe 2020-05-22 18:48 ` Pierre-Louis Bossart 2020-05-22 19:44 ` Jason Gunthorpe 2020-05-22 21:05 ` Pierre-Louis Bossart 2020-06-29 20:59 ` Mark Brown 2020-05-23 6:23 ` Greg KH 2020-05-23 19:41 ` Pierre-Louis Bossart 2020-05-24 6:35 ` Greg KH 2020-05-26 13:15 ` Pierre-Louis Bossart 2020-05-26 13:37 ` Takashi Iwai 2020-05-27 7:17 ` Greg KH 2020-05-27 14:05 ` Pierre-Louis Bossart 2020-06-29 20:33 ` Mark Brown 2020-06-29 22:59 ` Jason Gunthorpe 2020-06-29 23:13 ` Kirsher, Jeffrey T 2020-06-30 10:31 ` Mark Brown 2020-06-30 11:32 ` Jason Gunthorpe 2020-06-30 14:16 ` Mark Brown 2020-06-30 17:24 ` Ranjani Sridharan 2020-06-30 17:27 ` Jason Gunthorpe 2020-07-01 9:50 ` Mark Brown 2020-07-01 23:32 ` Jason Gunthorpe 2020-07-02 11:15 ` Mark Brown 2020-07-02 12:11 ` Jason Gunthorpe 2020-07-02 12:20 ` Mark Brown 2020-07-01 6:59 ` Greg KH 2020-07-02 13:43 ` Ranjani Sridharan 2020-07-06 23:02 ` Dan Williams [this message] 2020-07-07 14:16 ` Greg KH 2020-05-25 16:55 ` Jason Gunthorpe 2020-06-29 20:21 ` Mark Brown 2020-06-29 17:36 ` Mark Brown 2020-05-20 7:02 ` [net-next v4 11/12] ASoC: SOF: Create client driver for IPC test Jeff Kirsher 2020-05-20 7:22 ` Greg KH 2020-05-20 12:56 ` Jason Gunthorpe 2020-05-27 20:18 ` Ranjani Sridharan 2020-05-28 0:12 ` Jason Gunthorpe 2020-05-28 1:40 ` Ranjani Sridharan 2020-05-28 10:45 ` Greg KH 2020-06-29 20:37 ` Mark Brown 2020-05-20 7:02 ` [net-next v4 12/12] ASoC: SOF: ops: Add new op for client registration Jeff Kirsher 2020-05-20 7:23 ` Greg KH 2020-05-20 7:17 ` [net-next v4 00/12][pull request] 100GbE Intel Wired LAN Driver Updates 2020-05-19 Greg KH 2020-05-20 7:25 ` Kirsher, Jeffrey T 2020-05-20 9:08 ` Greg KH
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=CAPcyv4g9xCMh5cQF0qbObpHX5ckMK_SWPO12BcXF2ijn8MnckA@mail.gmail.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [net-next v4 10/12] ASoC: SOF: Introduce descriptors for SOF client' \ /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
This is a public inbox, see mirroring instructions on how to clone and mirror all data and code used for this inbox