public inbox for linux-kernel@vger.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>
Subject: Re: [Suggestion] drivers/staging/tidspbridge: pr_err and pr_debug for uninitialized buffer (name buf not initialized).
Date: Wed, 26 Dec 2012 09:56:14 +0800	[thread overview]
Message-ID: <50DA593E.9000707@asianux.com> (raw)
In-Reply-To: <CAJ6Av5PqZoW7s94J6MfmiN6kLzYZHH5Cv6qBA+xq65aPO0KA7g@mail.gmail.com>

于 2012年12月24日 22:26, Omar Ramirez Luna 写道:
>>       b: version merging issue:
>> >         in drivers/staging/tidspbridge/core/_tiomap.h
>> >         need use "#include <mach-omap2/cm3xxx.h>" instead of "#include <mach-omap2/cm2xxx_3xxx.h>"
>> >         the macro OMAP3430_CM_AUTOIDLE_PLL has already move from cm2xxx_3xxx.h to cm3xxx.h.
>> >           (it seems arch/arm/mach-omap2/ is not a suitable place for including, but we have to)
>> >         if not change, compiling will be failed.

  also please help checking this issue, thanks.

-- 
Chen Gang

Asianux Corporation

  parent reply	other threads:[~2012-12-26  1:55 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 [this message]
2012-12-26  6:28             ` Omar Ramirez Luna
2012-12-26  6:44               ` Chen Gang

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=50DA593E.9000707@asianux.com \
    --to=gang.chen@asianux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox