From: waltfeasel@gmail.com (Walt Feasel)
To: kernelnewbies@lists.kernelnewbies.org
Subject: [PATCH 0/7] security: apparmor: apparmorfs.c Checkpatch mods
Date: Sat, 26 Nov 2016 11:56:17 -0500 [thread overview]
Message-ID: <20161126165617.GA9754@localhost> (raw)
In-Reply-To: <20161126110550.GD8388@kroah.com>
On Sat, Nov 26, 2016 at 12:05:50PM +0100, Greg KH wrote:
> On Sat, Nov 26, 2016 at 03:43:18AM -0500, Walt Feasel wrote:
> > Make checkpatch modifications to include:
> >
> > Multiple blank lines
> > Blank line after declarations
> > Space after cast
> > WARN_ON vs BUG_ON
> > Align parenthesis
> > Comparison to NULL
> > Line continuations
> >
> > Walt Feasel (7):
> > security: apparmor: apparmorfs.c Multiple blank lines
> > security: apparmor: apparmorfs.c Blank line after declarations
> > security: apparmor: apparmorfs.c Space after cast
> > security: apparmor: apparmorfs.c WARN_ON vs BUG_ON
> > security: apparmor: apparmorfs.c Align parenthesis
> > security: apparmor: apparmorfs.c Comparison to NULL
> > security: apparmor: apparmorfs.c Line continuations
>
> Why are you sending apparmor patches to the kernelnewbies list and not
> the maintainers and subsystem list for this code instead?
>
> thanks,
>
> greg k-h
Because as stated in my patch notes I am not sure how to
fix certain cases.
I have not been able to find reference material other than
other patches and discussions for certain cases and have
to try and reason why.
You wanted me to move out of staging so I have looked to
other areas but do not wish to send in ridiculous patches
and have me seen as being malicious.
Since this is kernelnewbies mailing list isn't that it's
purpose or am I move on again?
Feel free to skip my post should they trouble you.
next prev parent reply other threads:[~2016-11-26 16:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-26 8:43 [PATCH 0/7] security: apparmor: apparmorfs.c Checkpatch mods Walt Feasel
2016-11-26 8:43 ` [PATCH 1/7] security: apparmor: apparmorfs.c Multiple blank lines Walt Feasel
2016-11-26 8:43 ` [PATCH 2/7] security: apparmor: apparmorfs.c Blank line after declarations Walt Feasel
2016-11-26 8:43 ` [PATCH 3/7] security: apparmor: apparmorfs.c Space after cast Walt Feasel
2016-11-26 8:43 ` [PATCH 4/7] security: apparmor: apparmorfs.c WARN_ON vs BUG_ON Walt Feasel
2016-11-26 8:43 ` [PATCH 5/7] security: apparmor: apparmorfs.c Align parenthesis Walt Feasel
2016-11-26 8:43 ` [PATCH 6/7] security: apparmor: apparmorfs.c Comparison to NULL Walt Feasel
2016-11-26 8:43 ` [PATCH 7/7] security: apparmor: apparmorfs.c Line continuations Walt Feasel
2016-11-26 11:05 ` [PATCH 0/7] security: apparmor: apparmorfs.c Checkpatch mods Greg KH
2016-11-26 16:56 ` Walt Feasel [this message]
2016-11-26 17:19 ` Greg KH
2016-11-26 18:02 ` Walt Feasel
2016-11-26 20:40 ` Greg KH
2016-11-26 21:28 ` Bjørn Mork
2016-11-26 22:41 ` Joel Fernandes
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=20161126165617.GA9754@localhost \
--to=waltfeasel@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).