From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tom Rini Date: Wed, 18 Jun 2014 13:49:35 -0400 Subject: [U-Boot] [PATCH 0/5] Kbuild: sync with Linux 3.16-rc1 In-Reply-To: <1402912600-22011-1-git-send-email-yamada.m@jp.panasonic.com> References: <1402912600-22011-1-git-send-email-yamada.m@jp.panasonic.com> Message-ID: <20140618174935.GD26243@bill-the-cat> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Mon, Jun 16, 2014 at 06:56:35PM +0900, Masahiro Yamada wrote: > > The merge window for Linux 3.16 is closed and Linux 3.16-rc1 is out now. > > During the merge window, various Kbuild-related updates were merged into > the upstream. > > This series imports them to U-Boot. I see you saw there's problems been reported and have moved this to RFC. My thoughts on this right now are that as a rule of thumb we should: 1) If our merge window and kernel merge window line up (say -rc1 kernel came out, and we are -rc1 or haven't yet snapped -rc1), sync up, and stay in sync to release on the kernel side (as close as possible) 2) If our merge windows aren't in sync, just stick with kernel release. Thanks! -- Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 836 bytes Desc: Digital signature URL: