From: Alexander Kapshuk <alexander.kapshuk@gmail.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: Greg KH <gregkh@linuxfoundation.org>,
Jim Davis <jim.epost@gmail.com>,
richard@nod.at, "Theodore Ts'o" <tytso@mit.edu>
Subject: Re: ver_linux: proposed implementation feedback request
Date: Tue, 6 Oct 2015 14:28:54 +0300 [thread overview]
Message-ID: <CAJ1xhMU==KR5_c5MgdtNVkBEWgrc_27XdfnGqcFaD0hFi_XGwg@mail.gmail.com> (raw)
In-Reply-To: <20151006081150.GA19014@kroah.com>
On Tue, Oct 6, 2015 at 11:11 AM, Greg KH <gregkh@linuxfoundation.org> wrote:
> On Mon, Oct 05, 2015 at 08:00:40PM +0300, Alexander Kapshuk wrote:
>> Thanks very much for everyone's feedback.
>>
>> Instead of flooding this mailing list with another bunch of ver_linux
>> patches, I thought I would post another implementation, and see if you
>> find any of the proposed changes worth submitting as a patch. I will
>> be happy with whatever feedback you can give me. And we will leave it
>> at that. Thanks.
>
> We can't try to do a diff ourselves in order to try to determine if this
> is "good enough" to take, sorry, that's not hoe kernel development
> works. If you don't think it's "good enough", then we sure don't :)
>
> If you want to redo your series, to fix issues you have found, great,
> please do so and resend them and we will be glad to review them, as we
> have been doing. We can work with that, not with a "raw" file like
> this.
>
> thanks,
>
> greg k-h
Understood. Thanks.
next prev parent reply other threads:[~2015-10-06 11:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-05 17:00 ver_linux: proposed implementation feedback request Alexander Kapshuk
2015-10-06 8:11 ` Greg KH
2015-10-06 11:28 ` Alexander Kapshuk [this message]
2015-10-07 1:25 ` Theodore Ts'o
2015-10-07 18:00 ` Alexander Kapshuk
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='CAJ1xhMU==KR5_c5MgdtNVkBEWgrc_27XdfnGqcFaD0hFi_XGwg@mail.gmail.com' \
--to=alexander.kapshuk@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jim.epost@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=richard@nod.at \
--cc=tytso@mit.edu \
/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;
as well as URLs for NNTP newsgroup(s).