From: Christoph Hellwig <hch@lst.de>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Christoph Hellwig <hch@lst.de>,
laurentiu.tudor@nxp.com, stern@rowland.harvard.edu,
linux-usb@vger.kernel.org, marex@denx.de, leoyang.li@nxp.com,
linux-kernel@vger.kernel.org, robin.murphy@arm.com,
noring@nocrew.org, JuergenUrban@gmx.de
Subject: Re: [PATCH v6 0/5] prerequisites for device reserved local mem rework
Date: Thu, 23 May 2019 09:12:08 +0200 [thread overview]
Message-ID: <20190523071208.GA12312@lst.de> (raw)
In-Reply-To: <20190523070755.GA23832@kroah.com>
On Thu, May 23, 2019 at 09:07:55AM +0200, Greg KH wrote:
> I have no objection for you just taking this whole series as-is, no need
> to worry about merge conflicts with the USB tree, I doubt anything will
> be touching this area of code anytime soon.
>
> So if you want to take it now, feel free to add:
>
> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>
> to all of these.
>
> Or, if you really like/want a branch to pull from, I can do that as
> well, which ever is easiest for you to work with as you all are doing
> the hard work here, not me :)
Nah, I can happily take it. I'll open the dma-mapping tree after -rc2.
next prev parent reply other threads:[~2019-05-23 7:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-22 14:27 [PATCH v6 0/5] prerequisites for device reserved local mem rework laurentiu.tudor
2019-05-22 14:27 ` [PATCH v6 1/5] lib/genalloc.c: Add gen_pool_dma_zalloc() for zeroed DMA allocations laurentiu.tudor
2019-05-22 14:27 ` [PATCH v6 2/5] USB: use genalloc for USB HCs with local memory laurentiu.tudor
2019-05-22 14:27 ` [PATCH v6 3/5] usb: host: ohci-sm501: init genalloc for " laurentiu.tudor
2019-05-22 14:27 ` [PATCH v6 4/5] usb: host: ohci-tmio: " laurentiu.tudor
2019-05-22 14:27 ` [PATCH v6 5/5] USB: drop HCD_LOCAL_MEM flag laurentiu.tudor
2019-05-23 6:56 ` [PATCH v6 0/5] prerequisites for device reserved local mem rework Christoph Hellwig
2019-05-23 7:07 ` Greg KH
2019-05-23 7:12 ` Christoph Hellwig [this message]
2019-05-28 5:58 ` Christoph Hellwig
2019-05-28 6:47 ` Greg KH
2019-05-28 6:52 ` Christoph Hellwig
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=20190523071208.GA12312@lst.de \
--to=hch@lst.de \
--cc=JuergenUrban@gmx.de \
--cc=gregkh@linuxfoundation.org \
--cc=laurentiu.tudor@nxp.com \
--cc=leoyang.li@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=marex@denx.de \
--cc=noring@nocrew.org \
--cc=robin.murphy@arm.com \
--cc=stern@rowland.harvard.edu \
/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.