From: Chen Gang <gang.chen@asianux.com>
To: Omar Ramirez Luna <omar.ramirez@copitl.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Greg KH <gregkh@linuxfoundation.org>
Subject: Re: [Suggestion] drivers/staging/tidspbridge: strcpy and strncpy, src length checking issue.
Date: Wed, 26 Dec 2012 09:54:18 +0800 [thread overview]
Message-ID: <50DA58CA.2060700@asianux.com> (raw)
In-Reply-To: <CAJ6Av5NtM06aTsGzE+4cYH-TM2fkN3Ek0f=OuR=_abDtta1FDA@mail.gmail.com>
于 2012年12月24日 22:27, Omar Ramirez Luna 写道:
> Hi Gchen,
>
> On Mon, Dec 17, 2012 at 8:40 PM, Chen Gang <gang.chen@asianux.com> wrote:
>> Hello Omar Ramirez Luna:
>>
>> excuse me to bother you (maybe you are busy in these days).
>> please help checking this suggestion when you have free time.
>
> Yes, I'm checking your suggestions, I was a little busy last week, for
> the compile breaks I had a patch but I was waiting for them to show on
> staging 3.8-rc1.
>
ok, I should wait for some days, at least.
:-)
>> By the way:
>> this week, I need work for 2 patches which relative with usb sub-system.
>> if still get no reply for tidspbridge until next week.
>> I should work for it, it is my duty (since I have provided 'suggestion' to it).
>> "work for it" means:
>> if tidspbridge is still useful
>> I need construct relative environments for unit test.
>> then provide relative patches.
>> else (useless)
>> I need delete it from Open Source.
>> (since it can not pass compiling, and no response from *@ti.com, it almost means useless)
>
> Please DON'T assume it's useless if you don't get replies from @ti.com .
ok.
--
Chen Gang
Asianux Corporation
next prev parent reply other threads:[~2012-12-26 1:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-14 3:50 [Suggestion] drivers/staging/tidspbridge: strcpy and strncpy, src length checking issue Chen Gang
2012-12-18 2:40 ` Chen Gang
2012-12-18 5:03 ` Chen Gang
2012-12-24 14:27 ` Omar Ramirez Luna
2012-12-26 1:54 ` Chen Gang [this message]
2012-12-31 3:28 ` Chen Gang
2013-01-05 11:16 ` Omar Ramirez Luna
2013-01-05 11:17 ` Omar Ramirez Luna
2013-01-05 11:24 ` 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=50DA58CA.2060700@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