From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Vineet Gupta <Vineet.Gupta1@synopsys.com>
Cc: Grant Likely <grant.likely@secretlab.ca>,
Arnd Bergmann <arnd@arndb.de>,
linux-serial@vger.kernel.org
Subject: Re: [PATCH] serial/arc-uart: Urgent DT related update
Date: Thu, 14 Feb 2013 09:23:04 -0800 [thread overview]
Message-ID: <20130214172304.GA29021@kroah.com> (raw)
In-Reply-To: <511C7C38.7030009@synopsys.com>
On Thu, Feb 14, 2013 at 11:25:04AM +0530, Vineet Gupta wrote:
> > I've taken this now, it will be sent to Linus for 3.9-rc1.
>
> Thanks greg. I understand the tree closing rules' purpose, to let things stabilize
> ahead of merge window - both from mechanical conflicts perspective as well as
> runtime conflicts. However I'm slightly confused here about the process, specially
> as a n00b maintainer and was hoping you could clarify it.
>
> Your announcement of Feb 9th said
>
> >With the release of the 3.8-rc7 kernel, I think it's time to close the
> >TTY/serial tree for new features / cleanups for 3.9. So I'm closing my
> >tree, and will only be applying obvious bugfixes or regressions to it
> >until 3.9-rc1 comes out.
>
> So a bug fix sent on say Feb 11th would have been be applied to your tree to end
> up in 3.9 merge-window pull to Linus- correct or no ?
Yes.
> So in that sense, since Arnd/Grant are deeming this patch as bug fix,
> shouldn't it make into 3.9 merge-window merge.
Yes, and that is where it will be, as I said so above.
> So maybe, it's the criticality of the bug which warrants that. Please
> note that I'm just trying to understand the process here and not
> arguing about patch itself.
>
> >You can keep sending me patches for the tree that don't fit the "bugfix"
> >category, but note that I'll be storing them away to wait for 3.9-rc1
> >comes out, which might be a few weeks, so please be patient.
>
> And once 3.9-rc1 hits, everything becomes 3.10 merge material anyways
> except for bug fixes.
Yes.
Hope this helps,
greg k-h
next prev parent reply other threads:[~2013-02-14 17:23 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-11 6:20 [PATCH 0/4] switch arc-uart to devicetree based probing Vineet Gupta
2013-01-11 6:20 ` Vineet Gupta
2013-01-11 6:20 ` [PATCH 1/4] serial/arc-uart: Don't index with -ve platform_device->id Vineet Gupta
2013-01-11 6:20 ` Vineet Gupta
2013-01-11 6:20 ` [PATCH 2/4] serial/arc-uart: split probe from probe_earlyprintk Vineet Gupta
2013-01-11 6:20 ` Vineet Gupta
2013-01-11 6:20 ` [PATCH 3/4] serial/arc-uart: platform_data order changed Vineet Gupta
2013-01-11 6:20 ` Vineet Gupta
2013-01-11 6:20 ` [PATCH 4/4] serial/arc-uart: switch to devicetree based probing Vineet Gupta
2013-01-11 6:20 ` Vineet Gupta
2013-01-11 11:33 ` Arnd Bergmann
2013-01-11 11:55 ` Vineet Gupta
2013-01-11 11:55 ` Vineet Gupta
2013-01-11 20:17 ` Arnd Bergmann
2013-02-08 23:01 ` Grant Likely
2013-02-08 23:01 ` Grant Likely
2013-02-09 6:45 ` Vineet Gupta
2013-02-09 6:45 ` Vineet Gupta
2013-02-09 9:28 ` Arnd Bergmann
2013-02-11 8:41 ` [PATCH] serial/arc-uart: Urgent DT related update Vineet Gupta
2013-02-11 8:41 ` [PATCH] serial/arc-uart: Miscll DT related updates (Grant's review comments) Vineet Gupta
2013-02-11 8:41 ` Vineet Gupta
2013-02-13 12:37 ` [PATCH] serial/arc-uart: Urgent DT related update Vineet Gupta
2013-02-13 16:38 ` Greg Kroah-Hartman
2013-02-14 5:55 ` Vineet Gupta
2013-02-14 17:23 ` Greg Kroah-Hartman [this message]
2013-02-13 20:47 ` [PATCH 4/4] serial/arc-uart: switch to devicetree based probing Grant Likely
2013-01-16 6:16 ` [PATCH 0/4] switch arc-uart " Greg KH
2013-01-16 6:16 ` Vineet Gupta
2013-01-16 6:16 ` Vineet Gupta
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=20130214172304.GA29021@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Vineet.Gupta1@synopsys.com \
--cc=arnd@arndb.de \
--cc=grant.likely@secretlab.ca \
--cc=linux-serial@vger.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.