From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] arc: axs10x - bump Linux kernel to 4.2 release
Date: Mon, 31 Aug 2015 21:56:10 +0000 [thread overview]
Message-ID: <1441058169.2935.15.camel@synopsys.com> (raw)
In-Reply-To: <87d1y3ryug.fsf@dell.be.48ers.dk>
Hi Peter,
On Mon, 2015-08-31 at 22:23 +0200, Peter Korsgaard wrote:
> > > > > > "Alexey" == Alexey Brodkin <Alexey.Brodkin@synopsys.com> writes:
>
> > Linux kernel 4.2 was finally released, so bumping from
> > 4.2-rc5 to final release.
>
> > Also adding 1 back-ported patch that makes SD/MMC cards usable on AXS boards.
> > This patch will be a part of 4.3 (already in linux-next) and hopefully
> > will make its way in 4.2.1.
>
> > Once that patch appears in 4.2.x it must be removed from here.
>
> > Cc: Peter Korsgaard <peter@korsgaard.com>
> > Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> > Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com>
> > ---
>
> > Hopefully this is not too late for v2015.08 Buildroot release.
> > 4.2 hasjust released and I had to test build on real HW.
> > Sorry for that last moment patch.
>
> Sorry, it is :/
Ooops. That's what happens when people (like me) start to think about
keeping in sync a couple of open source projects.
> You forgot to change the kernel headers to 4.2 as well, and we don't
> have a BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_2 option yet.
It was intentional use of 4.1 headers just because 4.2 headers didn't
exist in buildroot. See http://lists.busybox.net/pipermail/buildroot/2015-August/135336.html
But now we'll have 4.2 headers soon and I will update my defconfigs anyways.
-Alexey
prev parent reply other threads:[~2015-08-31 21:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-31 16:25 [Buildroot] [PATCH] arc: axs10x - bump Linux kernel to 4.2 release Alexey Brodkin
2015-08-31 20:23 ` Peter Korsgaard
2015-08-31 21:56 ` Alexey Brodkin [this message]
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=1441058169.2935.15.camel@synopsys.com \
--to=alexey.brodkin@synopsys.com \
--cc=buildroot@busybox.net \
/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.