From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: Arnd Bergmann <arnd@arndb.de>, Christoph Hellwig <hch@lst.de>,
Linus Walleij <linus.walleij@linaro.org>,
Ludovic Barre <ludovic.barre@st.com>,
"# 4.0+" <stable@vger.kernel.org>
Subject: Re: patch "driver core: platform: Initialize dma_parms for platform devices" added to char-misc-testing
Date: Wed, 1 Apr 2020 10:21:31 +0200 [thread overview]
Message-ID: <20200401082131.GA2023796@kroah.com> (raw)
In-Reply-To: <CAPDyKFo2SZKDfv9oGpRXrYi-y26jRVPqDd5Xa4XX+7xVAwo-qg@mail.gmail.com>
On Wed, Apr 01, 2020 at 10:12:28AM +0200, Ulf Hansson wrote:
> On Wed, 1 Apr 2020 at 08:07, Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> >
> > On Tue, Mar 31, 2020 at 08:43:25PM +0200, Ulf Hansson wrote:
> > > On Thu, 26 Mar 2020 at 15:58, <gregkh@linuxfoundation.org> wrote:
> > > >
> > > >
> > > > This is a note to let you know that I've just added the patch titled
> > > >
> > > > driver core: platform: Initialize dma_parms for platform devices
> > > >
> > > > to my char-misc git tree which can be found at
> > > > git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git
> > > > in the char-misc-testing branch.
> > > >
> > > > The patch will show up in the next release of the linux-next tree
> > > > (usually sometime within the next 24 hours during the week.)
> > > >
> > > > The patch will be merged to the char-misc-next branch sometime soon,
> > > > after it passes testing, and the merge window is open.
> > > >
> > > > If you have any questions about this process, please let me know.
> > >
> > > Greg, would you mind dropping this one and the other patch for the amba bus?
> > >
> > > I just sent out a new version (v2), addressing an issue for the
> > > platform device when used for OF based platforms.
> > >
> > > If you prefer to not rebase/drop patches from your branch, I can send
> > > an incremental change on top instead, whatever you prefer.
> >
> > I will just revert these and then send it all on to Linus later today.
> > That way you can have the longer development cycle for better testing.
>
> Alright!
>
> Actually, reverting wasn't really necessary as the patches didn't
> break anything, just that v1 did fix the complete range of the
> problems.
This late in the cycle, reverting is probably best :)
prev parent reply other threads:[~2020-04-01 8:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-26 14:58 patch "driver core: platform: Initialize dma_parms for platform devices" added to char-misc-testing gregkh
2020-03-31 18:43 ` Ulf Hansson
2020-04-01 6:07 ` Greg Kroah-Hartman
2020-04-01 8:12 ` Ulf Hansson
2020-04-01 8:21 ` Greg Kroah-Hartman [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=20200401082131.GA2023796@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=hch@lst.de \
--cc=linus.walleij@linaro.org \
--cc=ludovic.barre@st.com \
--cc=stable@vger.kernel.org \
--cc=ulf.hansson@linaro.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).