From: Or Gerlitz <ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
To: Selvin Xavier
<Selvin.Xavier-iH1Dq9VlAzfQT0dZR+AlfA@public.gmane.org>,
Or Gerlitz <or.gerlitz-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Roland Dreier <roland-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: Steve Wise
<swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>,
"linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH for-next 00/15] Bug fixes for ocrdma driver
Date: Tue, 10 Jun 2014 09:06:31 +0300 [thread overview]
Message-ID: <5396A067.4070501@mellanox.com> (raw)
In-Reply-To: <36AE2E863FF33A4F9FBBE296E34DBC8F3C2B9703-DWYeeINJQrxExQ8dmkPuX0M9+F4ksjoh@public.gmane.org>
On 10/06/2014 04:37, Selvin Xavier wrote:
>
>> -----Original Message-----
>> From: Or Gerlitz [mailto:or.gerlitz-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org]
>> Sent: Tuesday, June 10, 2014 1:15 AM
>> To: Roland Dreier; Selvin Xavier
>> Cc: Steve Wise; linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org; linux-kernel
>> Subject: Re: [PATCH for-next 00/15] Bug fixes for ocrdma driver
>>
>> On Wed, Jun 4, 2014 at 8:06 PM, Roland Dreier <roland-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org> wrote:
>>> On Wed, Jun 4, 2014 at 9:37 AM, Steve Wise
>> <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org> wrote:
>>>> Seems like the subject lines in each patch are getting truncated?
>>> Yes, truncated in patchwork too -- for example:
>>> https://patchwork.kernel.org/patch/4292461/
>>>
>>> Please fix and resend.
>> Roland, from quick looking on this series of fifteen patches, only 1/3 of them
>> (4/5/12/14) have non-empty change-log. I would expect kernel work which
>> goes upstream through linux-rdma to use a bit of higher standards, agree?
>>
>> Selvin, can you sit down and come up with change-logs to your driver
>> updates?
>>
>> Or.
> Or,
>
> Sure, I will post v1 patch set with proper change-logs.
cool, thanks for the quick response
Or.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-06-10 6:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-04 8:52 [PATCH for-next 00/15] Bug fixes for ocrdma driver Selvin Xavier
[not found] ` <fc0ae2c3-2661-48ba-957a-66cbb0cfc33e-3RiH6ntJJkP8BX6JNMqfyFjyZtpTMMwT@public.gmane.org>
2014-06-04 16:37 ` Steve Wise
[not found] ` <538F4B66.6080906-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
2014-06-04 17:06 ` Roland Dreier
2014-06-04 17:38 ` Selvin Xavier
2014-06-09 19:44 ` Or Gerlitz
[not found] ` <CAJZOPZLqmq1XMoyjv0OMTv8iX0Otvo=bm-rrwa3EfupUYgyGKQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-06-10 1:37 ` Selvin Xavier
[not found] ` <36AE2E863FF33A4F9FBBE296E34DBC8F3C2B9703-DWYeeINJQrxExQ8dmkPuX0M9+F4ksjoh@public.gmane.org>
2014-06-10 6:06 ` Or Gerlitz [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-06-04 18:19 Selvin Xavier
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=5396A067.4070501@mellanox.com \
--to=ogerlitz-vpraknaxozvwk0htik3j/w@public.gmane.org \
--cc=Selvin.Xavier-iH1Dq9VlAzfQT0dZR+AlfA@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=or.gerlitz-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=roland-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.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