From: Paul Mundt <lethal@linux-sh.org>
To: Nobuhiro Iwamatsu <nobuhiro.iwamatsu.yj@renesas.com>
Cc: linux-sh@vger.kernel.org, linux-kernel@vger.kernel.org,
eric.dumazet@gmail.com
Subject: Re: [PATCH] sh: Fix build alloc_thread_info_node function
Date: Thu, 24 Mar 2011 06:25:12 +0000 [thread overview]
Message-ID: <20110324062511.GA18002@linux-sh.org> (raw)
In-Reply-To: <1300945660-8323-1-git-send-email-nobuhiro.iwamatsu.yj@renesas.com>
On Thu, Mar 24, 2011 at 02:47:40PM +0900, Nobuhiro Iwamatsu wrote:
> By commit b6a84016bd2598e35ead635147fa53619982648d,
> alloc_thread_info was replaced by alloc_thread_info_node.
> However, the change of the function name and the addition of the argument
> were incomplete.
>
> Signed-off-by: Nobuhiro Iwamatsu <nobuhiro.iwamatsu.yj@renesas.com>
> CC: Eric Dumazet <eric.dumazet@gmail.com>
Applied, thanks.
WARNING: multiple messages have this Message-ID (diff)
From: Paul Mundt <lethal@linux-sh.org>
To: Nobuhiro Iwamatsu <nobuhiro.iwamatsu.yj@renesas.com>
Cc: linux-sh@vger.kernel.org, linux-kernel@vger.kernel.org,
eric.dumazet@gmail.com
Subject: Re: [PATCH] sh: Fix build alloc_thread_info_node function
Date: Thu, 24 Mar 2011 15:25:12 +0900 [thread overview]
Message-ID: <20110324062511.GA18002@linux-sh.org> (raw)
In-Reply-To: <1300945660-8323-1-git-send-email-nobuhiro.iwamatsu.yj@renesas.com>
On Thu, Mar 24, 2011 at 02:47:40PM +0900, Nobuhiro Iwamatsu wrote:
> By commit b6a84016bd2598e35ead635147fa53619982648d,
> alloc_thread_info was replaced by alloc_thread_info_node.
> However, the change of the function name and the addition of the argument
> were incomplete.
>
> Signed-off-by: Nobuhiro Iwamatsu <nobuhiro.iwamatsu.yj@renesas.com>
> CC: Eric Dumazet <eric.dumazet@gmail.com>
Applied, thanks.
next prev parent reply other threads:[~2011-03-24 6:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-24 5:47 [PATCH] sh: Fix build alloc_thread_info_node function Nobuhiro Iwamatsu
2011-03-24 5:47 ` Nobuhiro Iwamatsu
2011-03-24 6:25 ` Paul Mundt [this message]
2011-03-24 6:25 ` Paul Mundt
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=20110324062511.GA18002@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=eric.dumazet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=nobuhiro.iwamatsu.yj@renesas.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.