Linux-PCI Archive on lore.kernel.org
 help / color / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Nicholas Johnson <nicholas.johnson-opensource@outlook.com.au>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	"mika.westerberg@linux.intel.com"
	<mika.westerberg@linux.intel.com>,
	"corbet@lwn.net" <corbet@lwn.net>
Subject: Re: [PATCH v2 0/4] PCI: Patch series to support Thunderbolt without any BIOS support
Date: Mon, 11 Mar 2019 12:53:26 -0500
Message-ID: <20190311175325.GI214730@google.com> (raw)
In-Reply-To: <PS2P216MB0642DA40B66B36581A238EF580480@PS2P216MB0642.KORP216.PROD.OUTLOOK.COM>

On Mon, Mar 11, 2019 at 04:22:47PM +0000, Nicholas Johnson wrote:
> 
> If possible, please try to include this in the upcoming release. I have 
> been slow in getting PATCH v2 out but overall, it should not be too much 
> to do.

Quick primer on the Linux development model: Major releases, e.g.,
v5.0, happen about every 9-10 weeks.  Subsystem maintainers typically
review and merge patches into their -next branches for about eight
weeks before the major release.

The first two weeks after a release are the merge window, during which
subsystem maintainers ask Linus to merge those -next branches into the
mainline.

Between the closing of the merge window and the next major release,
subsystem maintainers (1) ask Linus to merge fixes for regressions or
problems introduced during the merge window, and (2) accumulate
patches on their -next branches for the *next* merge window.

v5.0 was released a week ago, which means the v5.1 merge window is
half over.  Linus merged the PCI changes for v5.1 over the weekend, so
by default, PCI changes that weren't included in that merge will be
aiming for the v5.2 merge window.  Small fixes for regressions and
things we broke during the merge window can be merged any time, but we
have to be able to defend them as being critical enough to merge
outside the merge window.

See Documentation/process/2.Process.rst for more details.

Bjorn

      reply index

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-11 16:22 Nicholas Johnson
2019-03-11 17:53 ` Bjorn Helgaas [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=20190311175325.GI214730@google.com \
    --to=helgaas@kernel.org \
    --cc=corbet@lwn.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    --cc=nicholas.johnson-opensource@outlook.com.au \
    /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

Linux-PCI Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-pci/0 linux-pci/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-pci linux-pci/ https://lore.kernel.org/linux-pci \
		linux-pci@vger.kernel.org
	public-inbox-index linux-pci

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-pci


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git