All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chen Gang <gang.chen@asianux.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: jhovold@gmail.com, Jiri Slaby <jslaby@suse.cz>,
	mferrell@uplogix.com,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: USB: mos7840: looping issue: avoid the return value overriden by looping
Date: Tue, 02 Apr 2013 09:03:08 +0800	[thread overview]
Message-ID: <515A2E4C.8050409@asianux.com> (raw)
In-Reply-To: <20130401193721.GA13712@kroah.com>


  thank you for spending your time for this patch, especially you are
very busy.

  next time, I should send patch with more careful, so can let other
members work with more efficiency.

  excuse me, the next 2-3 days, I have to do another urgent things
within my company, so I will send our patch v2 within this week (if our
patch is urgent, too, please tell me, and I should try to send it in time).

  welcome any suggestions or completions. thanks.


On 2013年04月02日 03:37, Greg KH wrote:
> Please use a "real" error value, or even better yet, use the error value
> returned from the call here.
> 

  ok, I will do.

> And please identify the driver you are modifying in the Subject: line,
> like I have changed this one to.

  ok, thanks.

  and next, I should use such kind of format for any sub systems.



-- 
Chen Gang

Asianux Corporation

      reply	other threads:[~2013-04-02  1:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-01  2:52 [Suggestion] drivers/usb/serial: looping issue: return value may override by looping Chen Gang
2013-04-01  3:05 ` Greg KH
2013-04-01  3:21   ` Chen Gang
2013-04-01  3:50   ` [PATCH] drivers/usb/serial: looping issue: avoid the return value overriden " Chen Gang
2013-04-01 19:37     ` USB: mos7840: " Greg KH
2013-04-02  1:03       ` 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=515A2E4C.8050409@asianux.com \
    --to=gang.chen@asianux.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jhovold@gmail.com \
    --cc=jslaby@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mferrell@uplogix.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.