From: Scott Wood <scottwood@freescale.com>
To: Andy Fleming <afleming@gmail.com>
Cc: "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"Kumar Gala" <galak@kernel.crashing.org>,
Alex Perez <aperez@alexperez.com>
Subject: Re: [PATCH v2] powerpc/85xx: Add support for Varisys Cyrus board
Date: Thu, 10 Sep 2015 21:13:44 -0500 [thread overview]
Message-ID: <1441937624.2909.42.camel@freescale.com> (raw)
In-Reply-To: <CAKWjMd4YqAA1f0QzGxT1Hr+e_ceft2RHEUH649R5cfZ293t4eQ@mail.gmail.com>
On Thu, 2015-09-10 at 21:06 -0500, Andy Fleming wrote:
> On Thu, Sep 10, 2015 at 8:53 PM, Scott Wood <scottwood@freescale.com> wrote:
> > On Thu, 2015-09-10 at 20:51 -0500, Andy Fleming wrote:
> > > ping? I'd love if this could go in for 4.3
> >
> > It's way too late for 4.3.
> >
> > -Scott
>
> Argh. I was hoping that, as it's a one-line change to existing code it
> might be able to sneak in.
It's hard to call it "sneaking in" when a new pull request chain has to be
created just for one patch. :-P
Non-bugfixes need to be in my pull request to Michael before the merge window
opens (and thus submitted long enough before that for me to have a chance to
do a review/apply/build-test session), not a couple days before the merge
window closes. Why does it matter if this is in 4.3 versus 4.4?
-Scott
next prev parent reply other threads:[~2015-09-11 2:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-02 6:36 [PATCH] powerpc/85xx: Add support for Varisys Cyrus board Andy Fleming
2015-09-02 16:53 ` Scott Wood
2015-09-02 17:23 ` Andy Fleming
2015-09-02 17:42 ` Scott Wood
2015-09-02 17:43 ` Scott Wood
2015-09-02 18:07 ` [PATCH v2] " Andy Fleming
2015-09-11 1:51 ` Andy Fleming
2015-09-11 1:53 ` Scott Wood
2015-09-11 2:06 ` Andy Fleming
2015-09-11 2:13 ` Scott Wood [this message]
2015-09-11 2:38 ` Andy Fleming
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=1441937624.2909.42.camel@freescale.com \
--to=scottwood@freescale.com \
--cc=afleming@gmail.com \
--cc=aperez@alexperez.com \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@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;
as well as URLs for NNTP newsgroup(s).