From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: Alexey Fisher <bug-track@fisher-privat.net>
Cc: linux-kernel@vger.kernel.org, joe@perches.com
Subject: Re: [PATCH 2/2 v2] Unify rest of FAT messages.
Date: Thu, 11 Nov 2010 05:53:32 +0900 [thread overview]
Message-ID: <8739r8q4s3.fsf@devron.myhome.or.jp> (raw)
In-Reply-To: <1289408312.3636.10.camel@mini> (Alexey Fisher's message of "Wed, 10 Nov 2010 17:58:32 +0100")
Alexey Fisher <bug-track@fisher-privat.net> writes:
>> Also, yes. It would be complicate more or less than one FS. And maybe I
>> can understand why you want to concentrate FAT.
>>
>> But I'm afraid to implement for only FAT. If there is not any some sort
>> of agreement by others, it may have to re-implement. If that happen, FAT
>> can be bothered by compatible (or have to maintain both of old and new
>> for a while). Because the notified data are some sort of ABI, IMO.
>>
>> This is why I'm careful about this, and can't say easily - "let's try it
>> on FAT".
>
> I'm not sure if we talk about same thing now :D
> By notification you mean the idea to notify userspace about error?
> correct?
Sure. I was talking about "to notify userspace". :)
> In my previous email i switched the point, it will be to complicate for
> now to work on notification system. For now i'll be happy to see grep
> friendly logs. Same like ext2,3,4 do
>
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=4cf46b67eb6de94532c1bea11d2479d085229d0e
>
> In long term it will be good to have such notification system. So i will
> start new tread about it.
OK, I see. I'll review patches. Looks good though.
Thanks.
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
next prev parent reply other threads:[~2010-11-10 20:53 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-09 16:55 [PATCH 0/2] FAT unified kernel messages Alexey Fisher
2010-11-09 16:55 ` [PATCH 1/2] Introduce fat_msg() for " Alexey Fisher
2010-11-09 17:25 ` Joe Perches
2010-11-09 17:56 ` Wolfram Sang
2010-11-09 18:58 ` [PATCH 1/2] Idd fat_msg() to unified kernel messages for FAT fs Alexey Fisher
2010-11-09 19:43 ` Joe Perches
2010-11-10 10:23 ` [PATCH 1/4] Convert fat_fs_error to use %pV Alexey Fisher
2010-11-10 10:32 ` Andreas Schwab
2010-11-10 10:23 ` [PATCH 2/4] Add fat_msg() function for preformated FAT messages Alexey Fisher
2010-11-10 10:23 ` [PATCH 3/4] Replace all printk with fat_msg() Alexey Fisher
2010-11-10 10:23 ` [PATCH 4/4] Report each FAT mount and mount options Alexey Fisher
2010-11-10 11:33 ` [PATCH 1/2] Idd fat_msg() to unified kernel messages for FAT fs OGAWA Hirofumi
2010-11-09 16:55 ` [PATCH 2/2] Unify rest of FAT messages Alexey Fisher
2010-11-09 19:04 ` [PATCH 2/2 v2] " Alexey Fisher
2010-11-10 11:40 ` OGAWA Hirofumi
2010-11-10 12:41 ` Alexey Fisher
2010-11-10 13:53 ` OGAWA Hirofumi
2010-11-10 15:07 ` Alexey Fisher
2010-11-10 16:40 ` OGAWA Hirofumi
2010-11-10 16:58 ` Alexey Fisher
2010-11-10 20:53 ` OGAWA Hirofumi [this message]
2011-02-24 8:04 ` Alexey Fisher
2011-03-02 14:17 ` OGAWA Hirofumi
2010-11-09 17:03 ` [PATCH 0/2] FAT unified kernel messages Randy Dunlap
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=8739r8q4s3.fsf@devron.myhome.or.jp \
--to=hirofumi@mail.parknet.co.jp \
--cc=bug-track@fisher-privat.net \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome