All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chen Gang <gang.chen@asianux.com>
To: Omar Ramirez Luna <omar.ramirez@copitl.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	eballetbo@iseebcn.com
Subject: Re: [Suggestion] drivers/staging/tidspbridge: pr_err and pr_debug for uninitialized buffer (name buf not initialized).
Date: Wed, 26 Dec 2012 14:44:34 +0800	[thread overview]
Message-ID: <50DA9CD2.70607@asianux.com> (raw)
In-Reply-To: <CAJ6Av5PkPa_20xUYjd1h71ajZOoDxjw2sGKUrfEjb4SuoFc4bg@mail.gmail.com>

于 2012年12月26日 14:28, Omar Ramirez Luna 写道:
> 
> I also sent a patch for this:
> 
> http://www.mail-archive.com/linux-omap@vger.kernel.org/msg82565.html
> 
> However, I just saw this one which was sent 6 days ago:
> 
> https://patchwork.kernel.org/patch/1895081/
> 
> The latter includes the new header file, mine just the definitions
> needed, any approach is fine by me as they both fix the compile break.
> 
> Cheers,
> 
> Omar
> 
> 

  ok, thanks

by the way:
  the suggestion is sent in 2012-12-14 which is earlier than 2012-12-19
    ref: http://www.gossamer-threads.com/lists/linux/kernel/1646629
         at 3rd reply.

  :-)

-- 
Chen Gang

Asianux Corporation

      reply	other threads:[~2012-12-26  6:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-12  9:48 [Suggestion] drivers/staging/tidspbridge: pr_err and pr_debug for uninitialized buffer (name buf not initialized) Chen Gang
2012-12-12 10:02 ` Chen Gang
2012-12-12 10:12   ` Fwd: " Chen Gang
2012-12-13 18:25     ` Omar Ramirez Luna
2012-12-14  1:30       ` Chen Gang
2012-12-24 14:26         ` Omar Ramirez Luna
2012-12-26  1:52           ` Chen Gang
2012-12-26  1:56           ` Chen Gang
2012-12-26  6:28             ` Omar Ramirez Luna
2012-12-26  6:44               ` 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=50DA9CD2.70607@asianux.com \
    --to=gang.chen@asianux.com \
    --cc=eballetbo@iseebcn.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=omar.ramirez@copitl.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.