From: Vinod Koul <vinod.koul@intel.com>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: Vegard Nossum <vegard.nossum@gmail.com>,
Wenzhong Sun <wenzhong.sun@intel.com>,
ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] Nominating Fengguang Wu - 0-day
Date: Sun, 31 Jul 2016 23:02:15 +0530 [thread overview]
Message-ID: <20160731173214.GO9681@localhost> (raw)
In-Reply-To: <20160731063558.GA3493@wfg-t540p.sh.intel.com>
On Sun, Jul 31, 2016 at 02:35:58PM +0800, Fengguang Wu wrote:
> >
> >How about linux-next ?
>
> linux-next could be perfectly supported, however in a different
> "rebase" way than the "merges" for RC kernels.
>
> Suppose there are 100 branches based on -rc2 and another 100 branches
> on -rc3. We can typically merge most of the 200 branches onto -rc3,
> since there are relatively few changes between -rc2 and -rc3.
Since linux-next already contains all maintainer branches slated for -next,
merging that won't help much and seems tedious. I think 0day should just
runs tests on top of linux-next everyday and report, if not done already.
--
~Vinod
next prev parent reply other threads:[~2016-07-31 17:24 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-25 19:01 Luis R. Rodriguez
2016-07-25 20:23 ` Alexandre Belloni
2016-07-26 3:10 ` Vinod Koul
2016-07-26 8:16 ` Laurent Pinchart
2016-07-26 8:56 ` Vinod Koul
2016-07-28 13:20 ` Fengguang Wu
2016-07-27 14:50 ` Fengguang Wu
2016-07-28 16:15 ` Laurent Pinchart
2016-07-28 20:53 ` Fengguang Wu
2016-07-28 20:59 ` Laurent Pinchart
2016-07-28 22:38 ` Dmitry Torokhov
2016-07-29 16:26 ` Vinod Koul
2016-07-28 23:07 ` Fengguang Wu
2016-07-28 23:33 ` Luis R. Rodriguez
2016-07-29 0:09 ` Fengguang Wu
2016-07-29 15:12 ` Bjorn Helgaas
2016-07-30 17:05 ` Luis R. Rodriguez
2016-07-30 17:24 ` Guenter Roeck
2016-07-31 6:35 ` Fengguang Wu
2016-07-31 17:32 ` Vinod Koul [this message]
2016-08-01 13:35 ` Fengguang Wu
2016-07-28 23:38 ` Jiri Kosina
2016-07-31 11:16 ` Fengguang Wu
2016-07-29 2:00 ` Steven Rostedt
2016-07-29 2:26 ` Fengguang Wu
2016-07-27 14:41 ` Fengguang Wu
2016-07-28 17:15 ` Guenter Roeck
2016-07-28 17:21 ` Dmitry Vyukov
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=20160731173214.GO9681@localhost \
--to=vinod.koul@intel.com \
--cc=fengguang.wu@intel.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=vegard.nossum@gmail.com \
--cc=wenzhong.sun@intel.com \
/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