All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Michal Simek <monstr@monstr.eu>
Cc: Arnd Bergmann <arnd@arndb.de>,
	patchwork-bot+linux-soc@kernel.org,  SoC Team <soc@kernel.org>
Subject: Re: [GIT PULL] arm64: dts: ZynqMP DT changes for v5.15
Date: Tue, 14 Sep 2021 16:21:17 +0200	[thread overview]
Message-ID: <CAK8P3a0ZWxsUrGA2J8d=M-G=0Bbw16XfxuL=Uu=cXvPpMyQkgQ@mail.gmail.com> (raw)
In-Reply-To: <0a30a2dc-047c-94d1-9714-4c2cb70539d7@monstr.eu>

On Tue, Sep 14, 2021 at 4:04 PM Michal Simek <monstr@monstr.eu> wrote:
> On 9/14/21 3:58 PM, Arnd Bergmann wrote:
> >
> > I don't see anything wrong with the contents though, so please rebase on
> > top of v5.15 and resend the branch for 5.16. If there are bugfixes that you
> > want in v5.15, maybe split those out and send them separately for the
> > fixes branch.
>
> ok. Not a problem. When do you start to accepting patches for 5.16?
> Around rc5 or even earlier?

As early as possible, feel free to send the rebased branch right away,
and then send a follow-up for new material later.

I generally prefer to have most of the patches in my tree early on to
avoid the situation of getting too much stuff late during the cycle.
If you have a ton of early patches, and then a few more just before
the merge window as fixups, that's usually fine, but if you
send all the patches late, there is a danger of them missing out.

       Arnd

      reply	other threads:[~2021-09-14 14:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-26 14:36 [GIT PULL] arm64: dts: ZynqMP DT changes for v5.15 Michal Simek
2021-08-26 14:36 ` Michal Simek
2021-08-27 22:10   ` patchwork-bot+linux-soc
2021-09-14 13:58     ` Arnd Bergmann
2021-09-14 14:04       ` Michal Simek
2021-09-14 14:21         ` Arnd Bergmann [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='CAK8P3a0ZWxsUrGA2J8d=M-G=0Bbw16XfxuL=Uu=cXvPpMyQkgQ@mail.gmail.com' \
    --to=arnd@arndb.de \
    --cc=monstr@monstr.eu \
    --cc=patchwork-bot+linux-soc@kernel.org \
    --cc=soc@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.