[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.2.20.1701292354160.7496@casper.infradead.org>
Date: Sun, 29 Jan 2017 23:56:38 +0000 (GMT)
From: James Simmons <jsimmons@...radead.org>
To: Joe Perches <joe@...ches.com>
cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
devel@...verdev.osuosl.org,
Andreas Dilger <andreas.dilger@...el.com>,
Oleg Drokin <oleg.drokin@...el.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Lustre Development List <lustre-devel@...ts.lustre.org>,
James Simmons <uja.ornl@...oo.com>
Subject: Re: [PATCH 0/8] staging: lustre: lnet: change wire protocol typedefs
to proper structure
> On Sat, 2017-01-21 at 19:40 -0500, James Simmons wrote:
> > The upstream kernel requires proper structures so
> > convert nearly all the LNet wire protocols typedefs in
> > the LNet core.
>
> Thanks.
>
> Perhaps s/\bWIRE_ATTR\b/__packed/g one day too
I liked to keep that one. The point of WIRE_ATTR isn't to be
some abstraction but to label that struct as something that
goes over the wire. This lets people know that it would break
something if you change that structure. Looks like I need to
send a patch that adds a comment explaning the meaning of
WIRE_ATTR.
Powered by blists - more mailing lists