All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keller, Jacob E <jacob.e.keller@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [next-queue PATCH v3] fm10k: correctly pack TLV structures and explain reasoning
Date: Tue, 10 Nov 2015 17:38:09 +0000	[thread overview]
Message-ID: <1447177089.6967.1.camel@intel.com> (raw)
In-Reply-To: <1447172869.4094.25.camel@intel.com>

On Tue, 2015-11-10 at 08:27 -0800, Jeff Kirsher wrote:
> On Mon, 2015-11-09 at 14:04 -0800, Jacob Keller wrote:
> > The TLV format for little endian structures is actually 4 byte
> > aligned
> > copy. To this end, we need to add an additional __aligned(4) marker
> > along with __packed to ensure that these structures are actually 4
> > byte
> > aligned and packed correctly. Use of just __packed will not work as
> > this
> > will result in 1byte alignment which is incorrect. Add a comment
> > explaining the reasoning behind why these structures need the
> > special
> > treatment.
> > 
> > Signed-off-by: Jacob Keller <jacob.e.keller@intel.com>
> > ---
> > - v3
> > * use __aligned(4) instead of __attribute__(aligned(4))
> > 
> > Note: this patch replaces both TLV patches currently on the queue
> > as
> > it
> > looks like Jeff had forgotten to remove the earlier one when the
> > subject
> > changed.
> 
> Nope, I just applied the last submitted version of this patch. ?Might
> be helpful if the version actually incremented when you re-submit a
> patch. ?This is the third version of "v3", so techincally this should
> have been v5. :-)

At one point there were two different versions on the queue somehow.

It is difficult to remember the version because git doesn't make it
easy to keep track of the version. I'm currently working on how to
integrate git-notes into my workflow for this sort of thing.

Regards,
Jake

  reply	other threads:[~2015-11-10 17:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-09 22:04 [Intel-wired-lan] [next-queue PATCH v3] fm10k: correctly pack TLV structures and explain reasoning Jacob Keller
2015-11-10 16:27 ` Jeff Kirsher
2015-11-10 17:38   ` Keller, Jacob E [this message]
2015-12-16  3:10     ` Singh, Krishneil K

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=1447177089.6967.1.camel@intel.com \
    --to=jacob.e.keller@intel.com \
    --cc=intel-wired-lan@osuosl.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 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.