public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
* [PATCH 0/2] NFS - fix some _maxsz and _sz #defines
@ 2024-12-04  2:53 NeilBrown
  2024-12-04  2:53 ` [PATCH 1/2] NFS: fix open_owner_id_maxsz and related fields NeilBrown
  2024-12-04  2:53 ` [PATCH 2/2] NFS: move _maxsz and _sz #defines to the function which they describe NeilBrown
  0 siblings, 2 replies; 5+ messages in thread
From: NeilBrown @ 2024-12-04  2:53 UTC (permalink / raw)
  To: Trond Myklebust, Anna Schumaker; +Cc: David Disseldorp, linux-nfs

The first patch fixes some _maxsz that are now wrong since a patch of
mine which changed for format of NFSv4.0 open-owners.

I think this inconsistency might have been easier to avoid if the
#define was closer to the code that it describes.  So the second patch
moves most of these #defines close to the code.  That requires moving
all the "encode" function after the "decode" functions.

So maybe the second patch is too intrusive to be worth it - it is just
an RFC patch.  The first patch is much less intrusive.

Thanks,
NeilBrown

 [PATCH 1/2] NFS: fix open_owner_id_maxsz and related fields.
 [PATCH 2/2] NFS: move _maxsz and _sz #defines to the function which

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2024-12-04 14:04 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2024-12-04  2:53 [PATCH 0/2] NFS - fix some _maxsz and _sz #defines NeilBrown
2024-12-04  2:53 ` [PATCH 1/2] NFS: fix open_owner_id_maxsz and related fields NeilBrown
2024-12-04  2:53 ` [PATCH 2/2] NFS: move _maxsz and _sz #defines to the function which they describe NeilBrown
2024-12-04 12:26   ` kernel test robot
2024-12-04 14:03   ` kernel test robot

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox