From: Greg KH <greg@kroah.com>
To: Alexander Kochetkov <al.kochet@gmail.com>
Cc: stable@vger.kernel.org, nathan_lynch@mentor.com
Subject: Re: [PATCH 0/3] Patches to apply to v4.1-stable
Date: Sat, 12 Sep 2015 08:51:14 -0700 [thread overview]
Message-ID: <20150912155114.GD29944@kroah.com> (raw)
In-Reply-To: <F636D424-3FCA-4F89-9730-A111C48B0611@gmail.com>
On Sat, Sep 12, 2015 at 02:59:50PM +0300, Alexander Kochetkov wrote:
>
> > 11 september. 2015 г., 9:11, Greg KH <greg@kroah.com> *:
> >
> > All now applied, thanks.
> >
> > greg k-h
>
> Hello Geg,
>
> Thank you for your hard work!
>
> Please apply also 3473f26592c1c "ARM: 8405/1: VDSO: fix regression
> with toolchains lacking ld.bfd executable» on top of already applied VDSO patches.
>
> Here is comment from Nathan Lynch:
> > Since they fix a build regression with certain toolchains[*], I agree
> > with putting the ARM VDSO patches (#1 and #2 from this thread) into
> > 4.1-stable, as long as 3473f26592c1c "ARM: 8405/1: VDSO: fix regression
> > with toolchains lacking ld.bfd executable" is applied immediately
> > afterward, since it fixes a problem introduced by #2.
Now added, thanks.
greg k-h
prev parent reply other threads:[~2015-09-12 15:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-15 0:32 [PATCH 0/3] Patches to apply to v4.1-stable Alexander Kochetkov
2015-08-15 0:32 ` [PATCH 1/3] ARM: 8385/1: VDSO: group link options Alexander Kochetkov
2015-08-19 21:05 ` Nathan Lynch
2015-08-15 0:32 ` [PATCH 2/3] ARM: 8384/1: VDSO: force use of BFD linker Alexander Kochetkov
2015-08-15 0:32 ` [PATCH 3/3] ARM: v7 setup function should invalidate L1 cache Alexander Kochetkov
2015-08-15 8:00 ` Russell King - ARM Linux
2015-08-15 10:50 ` Alexander Kochetkov
2015-08-15 10:50 ` [PATCH] ARM: invalidate L1 before enabling coherency Alexander Kochetkov
2015-09-11 6:11 ` [PATCH 0/3] Patches to apply to v4.1-stable Greg KH
2015-09-12 11:59 ` Alexander Kochetkov
2015-09-12 15:51 ` Greg KH [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=20150912155114.GD29944@kroah.com \
--to=greg@kroah.com \
--cc=al.kochet@gmail.com \
--cc=nathan_lynch@mentor.com \
--cc=stable@vger.kernel.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.