mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Boris Brezillon <boris.brezillon@bootlin.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Greg KH <gregkh@linuxfoundation.org>,
	Arnd Bergmann <arnd@arndb.de>,
	wsa@the-dreams.de, Vitor.Soares@synopsys.com, pgaj@cadence.com,
	rafalc@cadence.com,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] Addition of the I3C subsystem in 4.20 (5.0)?
Date: Fri, 2 Nov 2018 18:45:18 +0100	[thread overview]
Message-ID: <20181102184518.60531378@bbrezillon> (raw)
In-Reply-To: <CAHk-=wg3r8QmJGKep9PK-8o3HM1-4aJJqQKsGaZJAk93Ad1pNw@mail.gmail.com>

Hello Linus,

On Thu, 1 Nov 2018 09:27:20 -0700
Linus Torvalds <torvalds@linux-foundation.org> wrote:

> On Wed, Oct 31, 2018 at 10:35 PM Boris Brezillon
> <boris.brezillon@bootlin.com> wrote:
> >
> > 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?) :-).
> 
> Regardless of any other issues, this is now too late in the merge
> window for me to accept.
> 
> Yes, the merge window is two weeks, but that's not because people
> should send me pull requests for two weeks. A large part of it is that
> it takes time to merge stuff, and I want to have time in the later
> part of the merge window for things I have to look at and ponder.

Ok, I didn't know that.

> 
> So that's why I want new stuff to be ready *before* the merge window,
> and I want to see the actual pull requests early. The two weeks is not
> for development and to let people delay things a bit, it's to make it
> possible to synchronize and to work out issues.

Noted, and sorry for the inconvenience.

Regards,

Boris

      reply	other threads:[~2018-11-02 17:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-01  5:35 Boris Brezillon
2018-11-01 11:33 ` Greg Kroah-Hartman
2018-11-01 12:29   ` Boris Brezillon
2018-11-01 16:27 ` Linus Torvalds
2018-11-02 17:45   ` Boris Brezillon [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=20181102184518.60531378@bbrezillon \
    --to=boris.brezillon@bootlin.com \
    --cc=Vitor.Soares@synopsys.com \
    --cc=arnd@arndb.de \
    --cc=gregkh@linuxfoundation.org \
    --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

all inboxes | Powered by JetHome®