mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: Shaun Savage <savages@tvlinux.org>
Cc: linux-kernel@vger.kernel.org, torvalds@osdl.org
Subject: Re: CBD Compressed Block Device, New embedded block device
Date: Sat, 21 Jan 2006 13:09:10 -0800	[thread overview]
Message-ID: <20060121130910.5877388c.rdunlap@xenotime.net> (raw)
In-Reply-To: <43D3467C.7010803@tvlinux.org>

On Sun, 22 Jan 2006 00:46:52 -0800 Shaun Savage wrote:

> HI
> 
> Here is a patch for 2.6.14.5 of CBD
> CBD is a compressed block device that is designed to shrink the file 
> system size to 1/3 the original size.  CBD is a block device on a file 
> system so, it also allows for in-field upgrade of file system.  If 
> necessary is also allows for secure booting, with a GRUB patch.
> 
> Reply to email please.

No need to send an entire .config file with it.

In Kconfig help, use "compressed".

I need more help on the BLK_CBD_DEVICE option.
What does it do?

Please fix the indentation after
+#ifndef CBD_PARTITION
in cbd_int.c

Try to limit lines to < 80 characters each.

Use spaces around operators (=, <, >, <=, >=, etc).

Use space after "if", "for", and "while".

Has some funky indenting (use tabs instead of spaces).

Don't use typedefs.
Don't use typedef struct S { ... } S_t;

struct partition_info &
struct cbd_part_hdr seem to expect that ushort, uint,
etc., have fixed sizes, but they can actually vary by
architecture, so you should use known fixed sizes
anywhere that field & struct sizes matter.

Use ALIGN() from kernel.h instead of your own align() macro.

Lots of trailing whitespace.  Don't do that:
Warning: trailing whitespace in lines 41,58,102,104,106,137,198,234 of include/linux/cbd.h
Warning: trailing whitespace in lines 348,355 of drivers/block/Kconfig
Warning: trailing whitespace in lines 32,72,138,158 of drivers/block/cbd_int.c
Warning: trailing whitespace in lines 7,50,95,162,240,318,428,516,613,657,658,669,704,747,797,808,813,817,827,872 of drivers/block/cbd_main.c

Has about 25 gcc warnings when I build it.

---
~Randy

  parent reply	other threads:[~2006-01-21 21:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-22  8:46 Shaun Savage
2006-01-21 19:53 ` Arjan van de Ven
2006-01-21 21:09 ` Randy.Dunlap [this message]
2006-01-21 22:05 ` Alexey Dobriyan
2006-01-21 22:22 ` Matt Mackall
2006-01-22  8:26 ` Pavel Machek
2006-01-23  2:26   ` Shaun Savage
2006-01-22 15:50 ` Phillip Susi
2006-01-22 18:26   ` Jan Engelhardt
2006-01-23 11:34   ` Shaun Savage

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=20060121130910.5877388c.rdunlap@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=savages@tvlinux.org \
    --cc=torvalds@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®