From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: ttuttle <ttuttle@chromium.org>
Cc: linux-serial@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [PATCH] qcserial: several fixes
Date: Wed, 1 Feb 2012 12:43:41 -0800 [thread overview]
Message-ID: <20120201204341.GA28366@kroah.com> (raw)
In-Reply-To: <20120201203950.GA14586@google.com>
On Wed, Feb 01, 2012 at 03:39:50PM -0500, ttuttle wrote:
> 1. Remove the unused "debug" parameter.
> 2. Add several new serial devices.
> 3. Disable autosuspend, as it has been flaky.
> 4. Log if we find too many altsettings.
>
> Signed-off-by: ttuttle <ttuttle@chromium.org>
Can you split this up into 4 different patches, as you are doing 4
different things?
Remember, one patch per "thing you do".
Also, I need a "real" name in the signed-off-by area, odds are "ttuttle"
is not your "full" name, right?
thanks,
greg k-h
prev parent reply other threads:[~2012-02-01 20:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-01 20:39 [PATCH] qcserial: several fixes ttuttle
2012-02-01 20:43 ` Greg Kroah-Hartman [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=20120201204341.GA28366@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=ttuttle@chromium.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;
as well as URLs for NNTP newsgroup(s).