From: Dan Carpenter <dan.carpenter@oracle.com>
To: Leon Romanovsky <leon@leon.nu>
Cc: devel@driverdev.osuosl.org,
linux-rdma <linux-rdma@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Mike Marciniszyn <infinipath@intel.com>,
Doug Ledford <dledford@redhat.com>,
Muhammad Falak R Wani <falakreyaz@gmail.com>,
Sean Hefty <sean.hefty@intel.com>,
Hal Rosenstock <hal.rosenstock@gmail.com>
Subject: Re: [PATCH 1/4 v2] staging: ipath: ipath_driver: Use setup_timer
Date: Tue, 27 Oct 2015 12:19:03 +0300 [thread overview]
Message-ID: <20151027091903.GA7340@mwanda> (raw)
In-Reply-To: <CALq1K=J-jEU=-BKjnAEvuxVfMmbPn4-gdj0i4StRbrVy6ho6Ag@mail.gmail.com>
On Sun, Oct 25, 2015 at 01:21:11PM +0200, Leon Romanovsky wrote:
> On Sun, Oct 25, 2015 at 12:17 PM, Muhammad Falak R Wani
> <falakreyaz@gmail.com> wrote:
> Please follow standard naming convention for the patches.
> It should be [PATCH v2 1/4] and not [PATCH 1/4 v2].
Does this matter? It's in a thread so it sorts fine either way.
regards,
dan carpenter
WARNING: multiple messages have this Message-ID (diff)
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Leon Romanovsky <leon@leon.nu>
Cc: Muhammad Falak R Wani <falakreyaz@gmail.com>,
devel@driverdev.osuosl.org,
linux-rdma <linux-rdma@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Mike Marciniszyn <infinipath@intel.com>,
Doug Ledford <dledford@redhat.com>,
Sean Hefty <sean.hefty@intel.com>,
Hal Rosenstock <hal.rosenstock@gmail.com>
Subject: Re: [PATCH 1/4 v2] staging: ipath: ipath_driver: Use setup_timer
Date: Tue, 27 Oct 2015 12:19:03 +0300 [thread overview]
Message-ID: <20151027091903.GA7340@mwanda> (raw)
In-Reply-To: <CALq1K=J-jEU=-BKjnAEvuxVfMmbPn4-gdj0i4StRbrVy6ho6Ag@mail.gmail.com>
On Sun, Oct 25, 2015 at 01:21:11PM +0200, Leon Romanovsky wrote:
> On Sun, Oct 25, 2015 at 12:17 PM, Muhammad Falak R Wani
> <falakreyaz@gmail.com> wrote:
> Please follow standard naming convention for the patches.
> It should be [PATCH v2 1/4] and not [PATCH 1/4 v2].
Does this matter? It's in a thread so it sorts fine either way.
regards,
dan carpenter
next prev parent reply other threads:[~2015-10-27 9:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-25 10:17 [PATCH 1/4 v2] staging: ipath: ipath_driver: Use setup_timer Muhammad Falak R Wani
2015-10-25 10:17 ` Muhammad Falak R Wani
2015-10-25 10:17 ` [PATCH 2/4 v2] staging: ipath: ipath_init_chip: " Muhammad Falak R Wani
2015-10-25 10:17 ` [PATCH 3/4 v2] staging: ipath: ipath_sdma: " Muhammad Falak R Wani
2015-10-25 10:17 ` [PATCH 4/4 v2] staging: ipath: ipath_verbs: " Muhammad Falak R Wani
2015-10-25 11:21 ` [PATCH 1/4 v2] staging: ipath: ipath_driver: " Leon Romanovsky
2015-10-25 11:21 ` Leon Romanovsky
2015-10-27 9:19 ` Dan Carpenter [this message]
2015-10-27 9:19 ` Dan Carpenter
2015-10-27 9:45 ` Leon Romanovsky
2015-10-27 9:45 ` Leon Romanovsky
[not found] ` <CALq1K=LLQd4CjVr=gB68MjLy0=uoY34nJxwTgsaEWtB0vBbUng-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-10-27 11:10 ` Dan Carpenter
2015-10-27 11:10 ` Dan Carpenter
2015-10-27 14:12 ` Muhammad Falak R Wani
2015-10-27 14:12 ` Muhammad Falak R Wani
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=20151027091903.GA7340@mwanda \
--to=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=dledford@redhat.com \
--cc=falakreyaz@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hal.rosenstock@gmail.com \
--cc=infinipath@intel.com \
--cc=leon@leon.nu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=sean.hefty@intel.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.