From: Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: David Miller <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
Cc: dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
matanb-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org,
saeedm-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org
Subject: Re: [GIT PULL] Please Pull Mellanox Shared Code
Date: Tue, 14 Jun 2016 09:32:38 +0300 [thread overview]
Message-ID: <20160614063238.GM5408@leon.nu> (raw)
In-Reply-To: <20160614.021249.1038979871508877232.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 378 bytes --]
On Tue, Jun 14, 2016 at 02:12:49AM -0400, David Miller wrote:
>
> A bare pull request does not work.
>
> You must post the actual patches so that they can be reviewed
> properly.
Sorry, It was first time attempt to get the sense for the proper procedure.
I will send the patch as a reply to this pull request and my hope that it will
be fine with you.
Thanks.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-06-14 6:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-13 12:03 [GIT PULL] Please Pull Mellanox Shared Code Leon Romanovsky
2016-06-13 13:49 ` Or Gerlitz
2016-06-14 6:12 ` David Miller
[not found] ` <20160614.021249.1038979871508877232.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2016-06-14 6:32 ` Leon Romanovsky [this message]
2016-06-14 6:35 ` Leon Romanovsky
2016-06-14 7:02 ` David Miller
[not found] ` <20160614.030229.1431969399873476358.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2016-06-14 17:16 ` Doug Ledford
2016-06-14 17:34 ` Or Gerlitz
2016-06-14 17:51 ` Leon Romanovsky
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=20160614063238.GM5408@leon.nu \
--to=leon-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org \
--cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=matanb-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=saeedm-VPRAkNaXOzVWk0Htik3J/w@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