From: Guenter Roeck <linux@roeck-us.net>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
Richard Henderson <rth@twiddle.net>,
Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
Matt Turner <mattst88@gmail.com>,
linux-kernel@vger.kernel.org, linux-alpha@vger.kernel.org
Subject: Re: [PATCH 0/2] alpha: fix build failure
Date: Mon, 14 Sep 2015 16:22:16 -0700 [thread overview]
Message-ID: <20150914232216.GA14502@roeck-us.net> (raw)
In-Reply-To: <20150914142955.89422b158c598ef5bb8cc74d@linux-foundation.org>
On Mon, Sep 14, 2015 at 02:29:55PM -0700, Andrew Morton wrote:
> On Mon, 14 Sep 2015 14:22:08 -0700 Guenter Roeck <linux@roeck-us.net> wrote:
>
> > On Mon, Sep 14, 2015 at 05:19:27PM +0530, Sudip Mukherjee wrote:
> > > We were getting build failure on allmodconfig. Mainly two causes
> > > ioremap_uc was not defined and __delay was not exported.
> > >
> > I already submitted patches to fix those problems some 6+ weeks ago.
> > Hope you'll have more luck.
>
> I have both of these patches queued for 4.3. Cc'ing me is a way of
> preventing stuff from falling through cracks..
>
Ok, I'll do that next time.
> But I didn't tag these patches for -stable backport. Should I have
> done so? If 4.2 is busted on alpha then I guess "yes".
>
No, this only affects 4.3-rc1 and -next.
Guenter
next prev parent reply other threads:[~2015-09-14 23:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-14 11:49 [PATCH 0/2] alpha: fix build failure Sudip Mukherjee
2015-09-14 11:49 ` [PATCH 1/2] alpha: io: define ioremap_uc Sudip Mukherjee
2015-09-14 11:49 ` [PATCH 2/2] alpha: lib: export __delay Sudip Mukherjee
2015-09-14 21:22 ` [PATCH 0/2] alpha: fix build failure Guenter Roeck
2015-09-14 21:29 ` Andrew Morton
2015-09-14 23:22 ` Guenter Roeck [this message]
2015-09-15 8:21 ` Sudip Mukherjee
2015-09-15 13:28 ` Guenter Roeck
2015-09-15 13:50 ` Sudip Mukherjee
2015-09-15 14:26 ` Guenter Roeck
2015-09-16 5:58 ` Sudip Mukherjee
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=20150914232216.GA14502@roeck-us.net \
--to=linux@roeck-us.net \
--cc=akpm@linux-foundation.org \
--cc=ink@jurassic.park.msu.ru \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mattst88@gmail.com \
--cc=rth@twiddle.net \
--cc=sudipm.mukherjee@gmail.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 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.