Re: [PATCH] hfsplus: don't modify journaled volume

Roman Zippel <[email protected]> wrote:
>
> +		} else if (vhdr->attributes & cpu_to_be32(HFSPLUS_VOL_JOURNALED)) {
>  +			printk("HFS+-fs: Filesystem is marked journaled, leaving read-only.\n");
>  +			sb->s_flags |= MS_RDONLY;
>  +			*flags |= MS_RDONLY;

These sorts of printks should have an explicit facility level, no?
-
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] hfsplus: don't modify journaled volume
    • From: Anton Altaparmakov <[email protected]>

• References:
  • [PATCH] hfsplus: don't modify journaled volume
    • From: Roman Zippel <[email protected]>

• Prev by Date: Re: 2.6 series kernels panic on boot at PCI probe with 450nx
• Next by Date: Re: [PATCH] mm: poison struct page for ptlock
• Previous by thread: [PATCH] hfsplus: don't modify journaled volume
• Next by thread: Re: [PATCH] hfsplus: don't modify journaled volume
• 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]