public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: gang.chen@asianux•com (Chen Gang)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH] ARM:common: setting saved_state to NULL after kfree
Date: Tue, 29 Jan 2013 21:08:59 +0800	[thread overview]
Message-ID: <5107C9EB.6000803@asianux.com> (raw)
In-Reply-To: <5107B3B1.1030406@asianux.com>


  it is my fault, building failed for not declare sa1111_remove before using.
  I should notice next time (at least, need building).

  if sending patch v2 is welcome, I will do.
    if need additional test, I should try (I try under qemu virtual machine).

  :-)


gchen.


? 2013?01?29? 19:34, Chen Gang ??:
>> > 2. I don't think you tried to build with your patch in place.
>> > 
>> > 
>   it is my fault, just like what you said, I did not try to build.
>   and I should try now.


-- 
Chen Gang

Asianux Corporation

      reply	other threads:[~2013-01-29 13:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-29 11:11 [PATCH] ARM:common: setting saved_state to NULL after kfree Chen Gang
2013-01-29 11:15 ` Russell King - ARM Linux
2013-01-29 11:34   ` Chen Gang
2013-01-29 13:08     ` Chen Gang [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=5107C9EB.6000803@asianux.com \
    --to=gang.chen@asianux$(echo .)com \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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