From: Chen Gang F T <chen.gang.flying.transformer@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Sedat Dilek <sedat.dilek@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Tomas Winkler <tomas.winkler@intel.com>,
arnd@arndb.de, alan@linux.intel.com,
linux-kernel@vger.kernel.org
Subject: Re: [char-misc-next V2] mei: drop the warning when cl is not initialized during unlinking
Date: Tue, 15 Jan 2013 09:46:46 +0800 [thread overview]
Message-ID: <50F4B506.8000509@gmail.com> (raw)
In-Reply-To: <20130114151220.GA20610@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 797 bytes --]
于 2013年01月14日 23:12, Greg KH 写道:
> If you think you can do better than that, wonderful, I would love for
> you to start out reviewing code and helping with handling stuff like
> that. Please do so before complaining about anything.
it seems, he is not complaining, maybe for him, he has to treat it as
an urgent thing.
and for every member, it is necessary to have a rest, so can keep our
contributes (work) with efficiency and sustainable.
so, please give more understanding with each other, so can make our
cooperation better and better.
by the way:
maybe it is necessary to think of a backup working flow to process
such kind of issues: "how to make the negative effect lowest, when
important members have to have a necessary rest".
--
Chen Gang
Flying Transformer
[-- Attachment #2: chen_gang_flying_transformer.vcf --]
[-- Type: text/x-vcard, Size: 67 bytes --]
begin:vcard
fn:Chen Gang
n:;Chen Gang
version:2.1
end:vcard
prev parent reply other threads:[~2013-01-15 1:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-10 15:32 [char-misc-next V2] mei: drop the warning when cl is not initialized during unlinking Tomas Winkler
2013-01-14 14:14 ` Sedat Dilek
2013-01-14 14:32 ` Greg KH
2013-01-14 14:55 ` Sedat Dilek
2013-01-14 15:12 ` Greg KH
2013-01-14 15:34 ` Sedat Dilek
2013-01-15 1:46 ` Chen Gang F T [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=50F4B506.8000509@gmail.com \
--to=chen.gang.flying.transformer@gmail.com \
--cc=alan@linux.intel.com \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sedat.dilek@gmail.com \
--cc=tomas.winkler@intel.com \
--cc=torvalds@linux-foundation.org \
/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