netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Cc: davem@davemloft.net,
	Anjali Singhai Jain <anjali.singhai@intel.com>,
	netdev@vger.kernel.org, gospo@redhat.com, sassmann@redhat.com,
	Jesse Brandeburg <jesse.brandeburg@intel.com>
Subject: Re: [net-next 09/14] i40e: Enable all PCTYPEs except FCOE for RSS.
Date: Sat, 07 Dec 2013 11:36:25 -0800	[thread overview]
Message-ID: <1386444985.2195.8.camel@jtkirshe-mobl> (raw)
In-Reply-To: <52A3812F.4070701@cogentembedded.com>

[-- Attachment #1: Type: text/plain, Size: 1428 bytes --]

On Sat, 2013-12-07 at 23:12 +0300, Sergei Shtylyov wrote:
> On 12/07/2013 09:16 PM, Jeff Kirsher wrote:
> 
> >>> From: Anjali Singhai Jain <anjali.singhai@intel.com>
> 
> >>> RSS can steer packets based on recognition of all
> >>> sorts of different headers.  Enable some more of them.
> 
> >>> Change-Id: I2264dedae66fb0bceca6fb6e772e050e3ca8efc8
> 
> >>      This line has no place in the upstream patches, and I'm seeing
> it
> >> in
> >> several patches of this series.
> 
> > This is an internal hash id, so that we can track upstream changes
> back
> > to internal git tree changes.  I did verify that this was acceptable
> and
> > is being used in the kernel in upstream patches before pushing this
> > information.
> 
>     First time I hear about that. Its use is constantly denied in
> linux-usb at 
> least. Maybe netdev has its own rules regarding this though...

Take a look at `git log --format=oneline --grep="Change-Id"`
You will see there are instances in arch as well as in wireless and in
other areas as well.  So we are not doing something new or the only ones
using this tag.

Google appears to be using it as well based the following information:
https://gerrit-documentation.storage.googleapis.com/Documentation/2.7/user-changeid.html
Places using gerrit:
http://code.google.com/p/gerrit/wiki/ShowCases
This is the largest example of a "Change-Id:" tag that I know of.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2013-12-07 19:36 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-07  2:17 [net-next 00/14][pull request] Intel Wired LAN Driver Updates Jeff Kirsher
2013-12-07  2:17 ` [net-next 01/14] i40e: separate TSYNVALID and TSYNINDX fields in Rx descriptor Jeff Kirsher
2013-12-07 21:33   ` Or Gerlitz
2013-12-07 21:40     ` Jeff Kirsher
2013-12-09 19:33       ` Keller, Jacob E
2013-12-07  2:17 ` [net-next 02/14] i40e: check multi-bit state correctly Jeff Kirsher
2013-12-07  2:17 ` [net-next 03/14] i40e: get media type during link info Jeff Kirsher
2013-12-07  2:17 ` [net-next 04/14] i40e: Add flag for L2 VEB filtering Jeff Kirsher
2013-12-07  2:17 ` [net-next 05/14] i40e: enable early hardware support Jeff Kirsher
2013-12-07  2:17 ` [net-next 06/14] i40e: whitespace Jeff Kirsher
2013-12-07  2:17 ` [net-next 07/14] i40e: Bump version Jeff Kirsher
2013-12-07  2:17 ` [net-next 08/14] i40e: refactor reset code Jeff Kirsher
2013-12-07  2:17 ` [net-next 09/14] i40e: Enable all PCTYPEs except FCOE for RSS Jeff Kirsher
2013-12-07 18:00   ` Sergei Shtylyov
2013-12-07 18:16     ` Jeff Kirsher
2013-12-07 20:12       ` Sergei Shtylyov
2013-12-07 19:36         ` Jeff Kirsher [this message]
2013-12-07 21:20           ` Sergei Shtylyov
2013-12-07 20:55             ` Jeff Kirsher
2013-12-09 22:05               ` Or Gerlitz
2013-12-10  7:22                 ` Or Gerlitz
2013-12-08  6:09     ` David Miller
2013-12-07  2:17 ` [net-next 10/14] i40e: only set up the rings to be used Jeff Kirsher
2013-12-07  2:17 ` [net-next 11/14] i40e: clear test state bit after all ethtool tests Jeff Kirsher
2013-12-07  2:17 ` [net-next 12/14] i40e: refactor " Jeff Kirsher
2013-12-07  2:17 ` [net-next 13/14] i40e: add num_VFs message Jeff Kirsher
2013-12-07  2:17 ` [net-next 14/14] i40e: Add a new variable to track number of pf instances Jeff Kirsher
2013-12-10  0:21 ` [net-next 00/14][pull request] Intel Wired LAN Driver Updates David Miller

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=1386444985.2195.8.camel@jtkirshe-mobl \
    --to=jeffrey.t.kirsher@intel.com \
    --cc=anjali.singhai@intel.com \
    --cc=davem@davemloft.net \
    --cc=gospo@redhat.com \
    --cc=jesse.brandeburg@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=sassmann@redhat.com \
    --cc=sergei.shtylyov@cogentembedded.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).