From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
openbmc@lists.ozlabs.org
Subject: Re: [GIT PULL v2] FSI updates for 4.17
Date: Tue, 12 Jun 2018 22:40:06 +1000 [thread overview]
Message-ID: <37ef3ba288b02c1e291a0da8f3ee666e0d7e75c7.camel@kernel.crashing.org> (raw)
In-Reply-To: <20180612114442.GB5777@kroah.com>
On Tue, 2018-06-12 at 13:44 +0200, Greg Kroah-Hartman wrote:
>
> > We are in regression only mode even before -rc1 these days ? including
> > for code that is basically completely unused upstream (which is what
> > this is trying to fix) ? :-) That's rather full-on ...
>
> For code that goes into -rc1, it has to be in linux-next _BEFORE_ -final
> comes out. That's been the rule for years, you should know that...
Oh I know and I also know that the rule was always somewhat flexible
for "new" drivers ;-) But heh, it's not biggie.
> > Anyway no biggie, it will just slow down some getting some of the other
> > drivers I suppose, though we can always explicitly list the dependency
> > on this tag to work around it.
>
> There should not be a rush here, remember, kernel development does not
> have deadlines :)
Sort-of, it does make things difficult to have so much crap piling up
out of tree or in vendor trees as you well know, so the faster that
pile is sorted, the better everybody is. But I can deal with the
dependencies for 4.19 (assuming we get the 2 or 3 other drivers I want
to see upstream lined up as well in the next few weeks).
Cheers,
Ben.
next prev parent reply other threads:[~2018-06-12 12:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-12 4:14 [GIT PULL] FSI updates Benjamin Herrenschmidt
2018-06-12 6:20 ` Greg Kroah-Hartman
2018-06-12 10:23 ` Benjamin Herrenschmidt
2018-06-12 10:54 ` [GIT PULL v2] FSI updates for 4.17 Benjamin Herrenschmidt
2018-06-12 11:18 ` Greg Kroah-Hartman
2018-06-12 11:25 ` Benjamin Herrenschmidt
2018-06-12 11:44 ` Greg Kroah-Hartman
2018-06-12 12:40 ` Benjamin Herrenschmidt [this message]
2018-07-07 15:03 ` Greg Kroah-Hartman
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=37ef3ba288b02c1e291a0da8f3ee666e0d7e75c7.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=openbmc@lists.ozlabs.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
all inboxes | Powered by JetHome®