All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Denys Dmytriyenko <denis@denix.org>,
	openembedded-core@lists.openembedded.org
Cc: Denys Dmytriyenko <denys@ti.com>
Subject: Re: [PATCH 0/3] Package upgrades
Date: Fri, 30 Mar 2018 09:36:17 +0100	[thread overview]
Message-ID: <1522398977.11431.114.camel@linuxfoundation.org> (raw)
In-Reply-To: <20180329224129.GK2786@denix.org>

On Thu, 2018-03-29 at 18:41 -0400, Denys Dmytriyenko wrote:
> Ping. It's been 10 days - are there any issues with these updates?

We're past feature freeze at this point and M3 was built (finally, and
late). During stabilisation we're only taking upgrades "with a good
reason". Security fixes, bug fixes and issues with maintenance windows
(e.g. bind) are reasons we might see some upgrades going in now but in
general we're holding upgrades until 2.6 opens.

I think Ross has a "post sumo" branch which he may pull some of these
into but I'd really like people to focus on bug fixing for sumo right
now.

Ross is also on vacation so I'll be handling things over the next week
or so (when do I get one?!). I might push a master-next-2.6 to queue
things just to make it clearer what is being deferred. Rebasing can be
a nightmare though.

Cheers,

Richard




  parent reply	other threads:[~2018-03-30  8:37 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-20  1:11 [PATCH 0/3] Package upgrades Denys Dmytriyenko
2018-03-20  1:11 ` [PATCH 1/3] lzip: upgrade 1.19 -> 1.20 Denys Dmytriyenko
2018-03-20  1:11 ` [PATCH 2/3] hdparm: upgrade 9.53 -> 9.55 Denys Dmytriyenko
2018-03-20  1:11 ` [PATCH 3/3] lz4: upgrade 1.7.4 -> 1.8.1.2 Denys Dmytriyenko
2018-03-29 22:41 ` [PATCH 0/3] Package upgrades Denys Dmytriyenko
2018-03-29 23:39   ` Andre McCurdy
2018-03-30  0:17     ` Denys Dmytriyenko
2018-03-30  1:38       ` Khem Raj
2018-03-30  2:34         ` Denys Dmytriyenko
2018-03-30  2:41           ` Khem Raj
2018-03-30  3:30             ` Denys Dmytriyenko
2018-03-30  8:36   ` Richard Purdie [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-05-11  6:48 [PATCH 0/3] Package Upgrades Robert Yang
2015-04-10  8:31 Robert Yang
2014-06-03  1:41 Chen Qi
2014-03-12  1:57 Chen Qi
2013-11-26 12:39 [PATCH 0/3] Package upgrades Cristiana Voicu
2013-10-24 18:29 Marko Lindqvist
2013-08-05  8:28 Cristiana Voicu
2012-12-10  8:08 Constantin Musca
2012-08-23 11:44 Constantin Musca
2012-08-24 18:36 ` Saul Wold
2012-08-14 12:50 Constantin Musca
2012-08-17 21:09 ` Saul Wold
2012-08-13 14:27 Constantin Musca
2012-08-17 20:56 ` Saul Wold

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=1522398977.11431.114.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=denis@denix.org \
    --cc=denys@ti.com \
    --cc=openembedded-core@lists.openembedded.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.