Re: [PATCH 1/2] LogFS proper

On Wed, May 09, 2007 at 01:10:09AM +0200, J??rn Engel wrote:
> 
> The remaining question is how to deal with kernel-only code that uses
> be64.  Convert that to __be64 as well?  Or introduce be64 in
> include/linix/types.h instead?

I say leave it alone for now, it's not that common :)

thanks,

greg k-h
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Follow-Ups:
- Re: [PATCH 1/2] LogFS proper
  - From: Jörn Engel <[email protected]>

References:
- [PATCH 0/2] LogFS take two
  - From: Jörn Engel <[email protected]>
- [PATCH 1/2] LogFS proper
  - From: Jörn Engel <[email protected]>
- Re: [PATCH 1/2] LogFS proper
  - From: Thomas Gleixner <[email protected]>
- Re: [PATCH 1/2] LogFS proper
  - From: Jörn Engel <[email protected]>
- Re: [PATCH 1/2] LogFS proper
  - From: "Pekka Enberg" <[email protected]>
- Re: [PATCH 1/2] LogFS proper
  - From: Jörn Engel <[email protected]>
- Re: [PATCH 1/2] LogFS proper
  - From: Greg KH <[email protected]>
- Re: [PATCH 1/2] LogFS proper
  - From: Jörn Engel <[email protected]>

Prev by Date: Re: [patch 3/4] split usermodehelper setup from execution
Next by Date: Re: [PATCH 3/3] AFS: Implement basic file write support
Previous by thread: Re: [PATCH 1/2] LogFS proper
Next by thread: Re: [PATCH 1/2] LogFS proper
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]