linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Coelho, Luciano" <luciano.coelho@intel.com>
To: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"Grumbach, Emmanuel" <emmanuel.grumbach@intel.com>,
	"kvalo@codeaurora.org" <kvalo@codeaurora.org>
Cc: "egrumbach@gmail.com" <egrumbach@gmail.com>
Subject: Re: [PATCH v5 1/7] mei: bus: add client dma interface
Date: Mon, 2 Aug 2021 18:54:06 +0000	[thread overview]
Message-ID: <bfb1a1d3ab7f948c2d1cd3a275e6aa072a7a7838.camel@intel.com> (raw)
In-Reply-To: <SA0PR11MB47524A040AA244F77C38A86AF2EF9@SA0PR11MB4752.namprd11.prod.outlook.com>

On Mon, 2021-08-02 at 18:33 +0000, Grumbach, Emmanuel wrote:
> Hi Kalle,
> 
> > 
> > From: Alexander Usyskin <alexander.usyskin@intel.com>
> > 
> > Expose the client dma mapping via mei client bus interface.
> > The client dma has to be mapped before the device is enabled, therefore we
> > need to create device linking already during mapping and we need to unmap
> > after the client is disable hence we need to postpone the unlink and flush till
> > unmapping or when destroying the device.
> > 
> > Signed-off-by: Alexander Usyskin <alexander.usyskin@intel.com>
> > Co-developed-by: Tomas Winkler <tomas.winkler@intel.com>
> > Signed-off-by: Tomas Winkler <tomas.winkler@intel.com>
> > Signed-off-by: Emmanuel Grumbach <emmanuel.grumbach@intel.com>
> > Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > Link: https://lore.kernel.org/r/20210420172755.12178-1-
> > emmanuel.grumbach@intel.com
> > ---
> 
> This series is assigned to Luca on patchwork besides this patch and the one with
> the vendor commands which are assigned to Johannes.
> I am a bit confused because you seemed to say you want to look at them, so maybe
> they should be assigned to you?
> Moreover the vendor commands patch is meant to be routed through the drivers'
> tree.

Emmanuel, the assignment is done automatically depending on the files
changed.

Since Kalle earlier said that he wants to review and apply these
patches directly to his tree, I'll assign the entire series to him now.

--
Cheers,
Luca.

      reply	other threads:[~2021-08-02 18:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-27  6:51 [PATCH v5 1/7] mei: bus: add client dma interface Emmanuel Grumbach
2021-07-27  6:51 ` [PATCH v5 2/7] iwlwifi: mei: add the driver to allow cooperation with CSME Emmanuel Grumbach
2021-07-27  6:51 ` [PATCH v5 3/7] iwlwifi: mei: add debugfs hooks Emmanuel Grumbach
2021-07-27  6:51 ` [PATCH v5 4/7] iwlwifi: integrate with iwlmei Emmanuel Grumbach
2021-07-27  6:51 ` [PATCH v5 5/7] nl80211: vendor-cmd: add Intel vendor commands for iwlmei usage Emmanuel Grumbach
2021-07-27  6:51 ` [PATCH v5 6/7] iwlwifi: mvm: add vendor commands needed for iwlmei Emmanuel Grumbach
2021-07-27  6:51 ` [PATCH v5 7/7] iwlwifi: mvm: read the rfkill state and feed it to iwlmei Emmanuel Grumbach
2021-08-02 18:33 ` [PATCH v5 1/7] mei: bus: add client dma interface Grumbach, Emmanuel
2021-08-02 18:54   ` Coelho, Luciano [this message]

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=bfb1a1d3ab7f948c2d1cd3a275e6aa072a7a7838.camel@intel.com \
    --to=luciano.coelho@intel.com \
    --cc=egrumbach@gmail.com \
    --cc=emmanuel.grumbach@intel.com \
    --cc=kvalo@codeaurora.org \
    --cc=linux-wireless@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).