From: Greg KH <gregkh@suse.de>
To: Hank Janssen <hjanssen@microsoft.com>
Cc: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
Haiyang Zhang <haiyangz@microsoft.com>
Subject: Re: [PATCH 2/2] Staging: hv: General maintenance of TODO file
Date: Thu, 11 Feb 2010 14:54:52 -0800 [thread overview]
Message-ID: <20100211225452.GA30820@suse.de> (raw)
In-Reply-To: <8AFC7968D54FB448A30D8F38F259C56212E88346@TK5EX14MBXC118.redmond.corp.microsoft.com>
On Thu, Feb 11, 2010 at 10:22:19PM +0000, Hank Janssen wrote:
> >>
> >> Removed two line;
> >> Audit block driver
> >> Audit scsi driver
> >> They were added by us as part of the original code
> >> Submission to make sure these drivers kept on working
> >> Correctly with all the patches that came in from the
> >> Community.
> >
> >Um, no, those things still need to be done.
>
> What additional things are expected? We solved the original
> reason we added the lines
Um, I added the lines, see commit id
51b671f2f40c303fd4d18e346f63af62c9b1f622 for proof of that.
And as far as I can see, no such auditing has been done.
You need to pass the code by the proper subsystem maintainers (block and
scsi) before these items can be removed.
> , so I want to make sure we do additional work as is expected. We are
> going through general code cleanup, and the TODO file now.
>
> >> Added a new line to fix mostly insane camelcase naming
> >> We are working on that right now, but it will take a bit
> >> Due to the pervasive usage of it.
> >
> >That's fine, but it fits under the general "fix coding style issues".
> >
> >Hm, that isn't spelled out, but it is implicit, I doubt this really
> >needs to be documented in the file, it's just common knowledge :)
>
> Want me to add a proper line item for that? Or drop this patch
> completely for the time being?
I say just drop it, you know you have to fix this :)
thanks,
greg k-h
next prev parent reply other threads:[~2010-02-11 22:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8AFC7968D54FB448A30D8F38F259C56212E881A9@TK5EX14MBXC118.redmond.corp.microsoft.com>
2010-02-11 21:32 ` [PATCH 2/2] Staging: hv: General maintenance of TODO file Hank Janssen
2010-02-11 21:38 ` Greg KH
2010-02-11 22:22 ` Hank Janssen
2010-02-11 22:54 ` Greg KH [this message]
2010-02-11 23:04 ` Hank Janssen
2010-02-11 23:20 ` Paul Mackerras
2010-02-11 23:32 ` Greg KH
2010-02-11 23:46 ` Hank Janssen
2010-02-12 0:11 ` Paul Mackerras
2010-02-12 0:09 ` Paul Mackerras
2010-02-12 15:08 ` Haiyang Zhang
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=20100211225452.GA30820@suse.de \
--to=gregkh@suse.de \
--cc=devel@driverdev.osuosl.org \
--cc=haiyangz@microsoft.com \
--cc=hjanssen@microsoft.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