From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Boris Brezillon <boris.brezillon@bootlin.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Arnd Bergmann <arnd@arndb.de>, Wolfram Sang <wsa@the-dreams.de>,
Vitor Soares <Vitor.Soares@synopsys.com>,
Przemyslaw Gaj <pgaj@cadence.com>,
Rafal Ciepiela <rafalc@cadence.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] Addition of the I3C subsystem in 4.20 (5.0)?
Date: Thu, 1 Nov 2018 12:33:30 +0100 [thread overview]
Message-ID: <20181101113330.GB11109@kroah.com> (raw)
In-Reply-To: <20181101063523.26bdbe28@bbrezillon>
On Thu, Nov 01, 2018 at 06:35:23AM +0100, Boris Brezillon wrote:
> Hello Greg, Linus,
>
> Greg, I didn't get your feedback on v10 of the i3c patchset [1] where I
> was asking if you'd agree to have this framework merged in 4.20 (I know
> you were busy with the 4.19 release and after that the Kernel Summit, so
> that's not a surprise), so I'm sending this PR. It's really not an attempt
> to bypass you, more like a ping that, if positively acknowledged, might
> lead to inclusion of the I3C framework in 4.20 (5.0?) :-).
>
> Please let me know if you're opposed to the idea.
>
> Regards,
>
> Boris
>
> [1]https://lkml.org/lkml/2018/10/26/552
The last set of patches was sent way too late for this -rc cycle so I
was going to review them again once 4.20-rc1 was out.
Also you do not have an ack from the DT maintainers yet, which would be
required as well, right?
So I don't think this can be merged just yet, sorry.
greg k-h
next prev parent reply other threads:[~2018-11-01 11:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-01 5:35 [GIT PULL] Addition of the I3C subsystem in 4.20 (5.0)? Boris Brezillon
2018-11-01 11:33 ` Greg Kroah-Hartman [this message]
2018-11-01 12:29 ` Boris Brezillon
2018-11-01 16:27 ` Linus Torvalds
2018-11-02 17:45 ` Boris Brezillon
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=20181101113330.GB11109@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Vitor.Soares@synopsys.com \
--cc=arnd@arndb.de \
--cc=boris.brezillon@bootlin.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pgaj@cadence.com \
--cc=rafalc@cadence.com \
--cc=torvalds@linux-foundation.org \
--cc=wsa@the-dreams.de \
/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).