From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: richard -rw- weinberger <richard.weinberger@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] allow to create a minix3fs with a blocksize != 1K
Date: Thu, 10 May 2012 00:20:35 +0200 [thread overview]
Message-ID: <4FAAEDB3.5060104@gmail.com> (raw)
In-Reply-To: <CAFLxGvxAd9HFJuG_GdkzZvfSp1EBNcg1S4v6O3dNpRMKRX45Rw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1982 bytes --]
On 10.05.2012 00:08, richard -rw- weinberger wrote:
> On Thu, May 10, 2012 at 12:04 AM, Vladimir 'φ-coder/phcoder'
> Serbinenko <phcoder@gmail.com> wrote:
>> Yes, I've already noticed this and resent it to the util-linux list.
>> Do you know if linux-kernel is the right list for my other patches like
>> wrong minixfs block allocation check or AFFS race condition? It seems
>> they've all been ignored.
> Not really.
> At least send them to linux-fsdevel too.
Done
> Please read MAINTAINERS and Documentation/SubmittingPatches and
> use checkpatch.pl/get_maintainer.pl.
get_maintainer pointed to this list for minix and ufs (output at the end
of message). And for UFS the maintainer e-mail is likely to be abandoned
(mail.ru e-mails were popular in 90's but are mostly abandoned now). If
noone answers the patches on linux-fsdevel I'll try CC maintainers directly.
Will read files when time permits.
Thank you very much for the info.
$ ./scripts/get_maintainer.pl -f fs/ufs/
Evgeniy Dushistov <dushistov@mail.ru> (maintainer:UFS FILESYSTEM)
linux-kernel@vger.kernel.org (open list)
$ ./scripts/get_maintainer.pl -f fs/affs/
Al Viro <viro@zeniv.linux.org.uk> (commit_signer:9/11=82%)
Sage Weil <sage@newdream.net> (commit_signer:3/11=27%)
Christoph Hellwig <hch@lst.de> (commit_signer:3/11=27%)
Miklos Szeredi <mszeredi@suse.cz> (commit_signer:2/11=18%)
Josef Bacik <josef@redhat.com> (commit_signer:1/11=9%)
linux-fsdevel@vger.kernel.org (open list:AFFS FILE SYSTEM)
linux-kernel@vger.kernel.org (open list)
$ ./scripts/get_maintainer.pl -f fs/minix/
Al Viro <viro@zeniv.linux.org.uk> (commit_signer:14/16=88%)
Sage Weil <sage@newdream.net> (commit_signer:3/16=19%)
Christoph Hellwig <hch@lst.de> (commit_signer:3/16=19%)
Josh Boyer <jwboyer@redhat.com> (commit_signer:2/16=12%)
Miklos Szeredi <mszeredi@suse.cz> (commit_signer:1/16=6%)
linux-kernel@vger.kernel.org (open list)
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]
prev parent reply other threads:[~2012-05-09 22:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-09 21:51 [PATCH] allow to create a minix3fs with a blocksize != 1K Vladimir 'φ-coder/phcoder' Serbinenko
2012-05-09 21:56 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-05-15 9:05 ` Karel Zak
2012-06-10 19:58 ` Davidlohr Bueso
2012-06-10 20:21 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-06-11 11:45 ` Davidlohr Bueso
2012-05-09 21:57 ` richard -rw- weinberger
2012-05-09 22:04 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-05-09 22:08 ` richard -rw- weinberger
2012-05-09 22:20 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
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=4FAAEDB3.5060104@gmail.com \
--to=phcoder@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=richard.weinberger@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.