From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 0/5] Kbuild: sync with Linux 3.16-rc1
Date: Wed, 18 Jun 2014 13:49:35 -0400 [thread overview]
Message-ID: <20140618174935.GD26243@bill-the-cat> (raw)
In-Reply-To: <1402912600-22011-1-git-send-email-yamada.m@jp.panasonic.com>
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: <http://lists.denx.de/pipermail/u-boot/attachments/20140618/299c6962/attachment.pgp>
next prev parent reply other threads:[~2014-06-18 17:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-16 9:56 [U-Boot] [PATCH 0/5] Kbuild: sync with Linux 3.16-rc1 Masahiro Yamada
2014-06-16 9:56 ` [U-Boot] [PATCH 1/5] kbuild: move extra gcc checks to scripts/Makefile.extrawarn Masahiro Yamada
2014-06-16 9:56 ` [U-Boot] [PATCH 2/5] kbuild: sync mixed targets handling with Linux 3.16-rc1 Masahiro Yamada
2014-06-16 17:58 ` Jeroen Hofstee
2014-06-17 1:42 ` Masahiro Yamada
2014-06-17 18:45 ` Jeroen Hofstee
2014-06-20 2:17 ` Masahiro Yamada
2014-06-20 2:20 ` Masahiro Yamada
2014-06-16 9:56 ` [U-Boot] [PATCH 3/5] cosmetic: kbuild: clean-up coding style (sync with Linux 3.16-rc1) Masahiro Yamada
2014-06-20 15:58 ` [U-Boot] [U-Boot, " Tom Rini
2014-06-16 9:56 ` [U-Boot] [PATCH 4/5] kbuild: Use relative path when possible Masahiro Yamada
2014-06-17 10:46 ` Masahiro Yamada
2014-06-16 9:56 ` [U-Boot] [PATCH 5/5] scripts: objdiff: sync with Linux 3.16-rc1 Masahiro Yamada
2014-06-18 17:49 ` Tom Rini [this message]
2014-06-19 8:26 ` [U-Boot] [PATCH 0/5] Kbuild: " Masahiro Yamada
2014-06-20 15:54 ` Tom Rini
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=20140618174935.GD26243@bill-the-cat \
--to=trini@ti.com \
--cc=u-boot@lists.denx.de \
/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