From: David Miller <davem@davemloft.net>
To: C.Fries@motorola.com, qcf001@motorola.com
Cc: netdev@vger.kernel.org, stable@kernel.org
Subject: Re: usbnet suspend issue
Date: Tue, 05 Jul 2011 18:11:16 -0700 (PDT) [thread overview]
Message-ID: <20110705.181116.1721142618197349978.davem@davemloft.net> (raw)
In-Reply-To: <CADuEq9DosCUpw9CnLrgQPXFojeCqEy-BHfZd1_BgvRJdFFQ9Ow@mail.gmail.com>
Patch submitted as binary attachment instead of plain text inline that
we can read and evaluate directly in our mail clients.
Also, if you submit this as a binary attachment, automated patch
management tools, such as patchwork, we use cannot track the patch.
Sorry, this is not the proper way to submit a patch.
Also get rid of the "Change-Id:" in your commit message, it has
no meaning.
prev parent reply other threads:[~2011-07-06 1:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CADuEq9DkdMixSyOAHNvJa5z4uuasekr=9xkE2jHnE-vpMvj3-Q@mail.gmail.com>
[not found] ` <201107051149.59963.oliver@neukum.org>
[not found] ` <CADuEq9BkW8iHQjacohGJUZzwh--ZrqVEKYa4DzftH9XnMc=JNw@mail.gmail.com>
2011-07-05 18:43 ` Fwd: usbnet suspend issue Chris Fries
2011-07-06 1:11 ` David Miller [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=20110705.181116.1721142618197349978.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=C.Fries@motorola.com \
--cc=netdev@vger.kernel.org \
--cc=qcf001@motorola.com \
--cc=stable@kernel.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