DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Wojciech Andralojc <wojciechx.andralojc@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v3] Patch introducing API to read/write Intel Architecture Model Specific Registers (MSR)...
Date: Thu, 21 Jan 2016 10:34:02 +0100	[thread overview]
Message-ID: <10612540.M6GzLfbW36@xps13> (raw)
In-Reply-To: <1453364287-37283-1-git-send-email-wojciechx.andralojc@intel.com>

Hi,

2016-01-21 08:18, Wojciech Andralojc:
> Patch reworked.
> 
> Signed-off-by: Wojciech Andralojc <wojciechx.andralojc@intel.com>

It cannot be applied without a proper commit log.

Please reword also the title to make it shorter and similar to
what you can find in the git history.
You can find some help in the doc:
	http://dpdk.org/doc/guides/contributing/patches.html#commit-messages-subject-line

  reply	other threads:[~2016-01-21  9:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-17 12:12 [dpdk-dev] [PATCH] Patch introducing API to read/write Intel Architecture Model Specific Registers (MSR), rte_msr_read and rte_msr_write functions Wojciech Andralojc
     [not found] ` <3FD2C4106EAA5C43838688C653B6E2AFDB8422@IRSMSX103.ger.corp.intel.com>
2016-01-06 17:33   ` Jerin Jacob
2016-01-20 10:56 ` [dpdk-dev] [PATCH v2] Patch introducing API to read/write Intel Architecture Model Specific Registers (MSR) Wojciech Andralojc
2016-01-20 11:25   ` Ananyev, Konstantin
2016-01-21  8:18     ` [dpdk-dev] [PATCH v3] " Wojciech Andralojc
2016-01-21  9:34       ` Thomas Monjalon [this message]
2016-01-21 10:38       ` Panu Matilainen
2016-01-21 10:51         ` Ananyev, Konstantin
2016-01-22 10:05           ` Panu Matilainen
2016-01-22 11:05             ` Ananyev, Konstantin
2016-01-22 11:37               ` Andralojc, WojciechX

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=10612540.M6GzLfbW36@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=dev@dpdk.org \
    --cc=wojciechx.andralojc@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).