public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Ming Lei <tom.leiming@gmail.com>, Axel Lin <axel.lin@ingics.com>
Cc: "Russell King - ARM Linux" <linux@arm.linux.org.uk>,
	"Jonathan Austin" <jonathan.austin@arm.com>,
	"Michal Marek" <mmarek@suse.cz>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: kernel BUG at kernel/kallsyms.c:222!
Date: Tue, 10 Dec 2013 16:47:40 +1030	[thread overview]
Message-ID: <87iouxjkl7.fsf@rustcorp.com.au> (raw)
In-Reply-To: <CACVXFVPrTWrC443vGpVGy-eH_hDQMN1HxCeC_iJ2uJ3Y=rnBwA@mail.gmail.com>

Ming Lei <tom.leiming@gmail.com> writes:

> Hi Axel,
>
> I am fine to resend it to RMK's patch system, but I am not sure
> if Russell would like to host it.
>
> Maybe it is better to push it via Rusty's tree since the change is only
> on scripts/, and it doesn't depend on the 1st one.
>
> Rusty, could you pick up the patch with title of
> "scripts/link-vmlinux.sh: only filter kernel symbols for arm"?

OK, and I added the correct Fixes: line so the stable people can track
it properly:

Cc: <stable@vger.kernel.org>
Cc: Rusty Russell <rusty@rustcorp.com.au>
Fixes: f6537f2f0eba4eba3354e48dbe3047db6d8b6254
Singed-off-by: Ming Lei <tom.leiming@gmail.com>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>

BTW, you misspelled Signed-off-by :)

Applied,
Rusty.


>
> Thanks,
> --
> Ming Lei
>
> On Mon, Dec 2, 2013 at 9:57 AM, Axel Lin <axel.lin@ingics.com> wrote:
>> 2013/11/13 Ming Lei <tom.leiming@gmail.com>:
>>> Hi Axel,
>>>
>>> On Wed, Nov 13, 2013 at 5:58 PM, Axel Lin <axel.lin@ingics.com> wrote:
>>>>
>>>> Hi Ming,
>>>> You missed "; then" in the end of if statement in your patch.
>>>>
>>>> So I got below error with your patch:
>>>> scripts/link-vmlinux.sh: line 87: syntax error near unexpected token `fi'
>>>> make: *** [vmlinuxclean] Error 2
>>>
>>> Thanks for your test, and I have fixed it and post a formal one for merge,
>>> and you can find these two patches on arm list, but forget to Cc you, sorry
>>> for that.
>>
>> Hi Ming,
>> Both your patch and Jonathan's patch are still not in linux-next.
>> Any chance to resend the patchs to RMK's patch system?
>>
>> Thanks,
>> Axel
>
>
>
> -- 
> Ming Lei

  reply	other threads:[~2013-12-10  7:14 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-07  1:53 kernel BUG at kernel/kallsyms.c:222! Axel Lin
2013-11-07  2:04 ` Ming Lei
2013-11-07  2:18   ` Axel Lin
2013-11-07  2:36     ` Ming Lei
2013-11-07  2:47       ` Axel Lin
2013-11-07  4:37         ` Ming Lei
2013-11-07  8:36           ` Axel Lin
2013-11-07 23:44             ` Rusty Russell
2013-11-08  0:45               ` Ming Lei
2013-11-08  4:20                 ` Axel Lin
2013-11-08  7:13                   ` Ming Lei
2013-11-11  0:23                     ` Rusty Russell
2013-11-11  6:43                       ` Axel Lin
2013-11-11  7:53                         ` Ming Lei
2013-11-11  8:37                           ` Axel Lin
2013-11-11  9:57                             ` Ming Lei
2013-11-11 10:41                               ` Ming Lei
2013-11-11 17:15                                 ` Jonathan Austin
2013-11-11 19:32                                   ` Russell King - ARM Linux
2013-11-12  3:22                                     ` Ming Lei
2013-11-12 17:36                                       ` Jonathan Austin
2013-11-13  4:41                                         ` Ming Lei
2013-11-13  9:58                                       ` Axel Lin
2013-11-13 11:30                                         ` Ming Lei
2013-12-02  1:57                                           ` Axel Lin
2013-12-02  2:08                                             ` Ming Lei
2013-12-10  6:17                                               ` Rusty Russell [this message]
2013-11-11  8:01                         ` Uwe Kleine-König
2013-11-08  3:56               ` Axel Lin

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=87iouxjkl7.fsf@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=axel.lin@ingics.com \
    --cc=jonathan.austin@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=mmarek@suse.cz \
    --cc=tom.leiming@gmail.com \
    --cc=u.kleine-koenig@pengutronix.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