All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: fangxiaozhi 00110321 <fangxiaozhi@huawei.com>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
	zihan@huawei.com, Lin.Lei@huawei.com, neil.yi@huawei.com,
	wangyuhua@huawei.com, huqiao36@huawei.com, balbi@ti.com,
	mdharm-usb@one-eyed-alien.net, sebastian@breakpoint.cc
Subject: Re: [PATCH 1/1]linux-usb:Define a new macro for USB storage match rules
Date: Thu, 24 Jan 2013 14:06:37 -0800	[thread overview]
Message-ID: <20130124220637.GA3873@kroah.com> (raw)
In-Reply-To: <fe6cc3d21db9.1db9fe6cc3d2@huawei.com>

On Wed, Jan 23, 2013 at 02:04:52PM +0800, fangxiaozhi 00110321 wrote:
> From: fangxiaozhi <huananhu@huawei.com>
> 
> 1. Define a new macro for USB storage match rules: 
>     matching with Vendor ID and interface descriptors.
> 
> Signed-off-by: fangxiaozhi <huananhu@huawei.com>
> --------------------------------------------------------------------

You sent me two patches, both marked with [1/1], yet they have to be
applied in a specific order.  Which one?  I don't think you want me to
guess :)

Please put the proper order in the patch number, i.e. [1/2], [2/2], and
so on.  If you use git, it will generate these patches, and the numbers,
automatically for you.  Same thing for quilt.  I strongly recommend you
use a tool like this to get this stuff right.

Please resend both of them properly.

thanks,

greg k-h

  reply	other threads:[~2013-01-24 22:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-23  6:04 [PATCH 1/1]linux-usb:Define a new macro for USB storage match rules fangxiaozhi 00110321
2013-01-24 22:06 ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-01-05  2:53 fangxiaozhi 00110321

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=20130124220637.GA3873@kroah.com \
    --to=greg@kroah.com \
    --cc=Lin.Lei@huawei.com \
    --cc=balbi@ti.com \
    --cc=fangxiaozhi@huawei.com \
    --cc=huqiao36@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mdharm-usb@one-eyed-alien.net \
    --cc=neil.yi@huawei.com \
    --cc=sebastian@breakpoint.cc \
    --cc=wangyuhua@huawei.com \
    --cc=zihan@huawei.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.