From: Martin Kletzander <mkletzan@redhat.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: devel@driverdev.osuosl.org, linux-rdma@vger.kernel.org,
linux-kernel@vger.kernel.org,
Hal Rosenstock <hal.rosenstock@gmail.com>,
Mike Marciniszyn <infinipath@intel.com>,
Doug Ledford <dledford@redhat.com>,
Or Gerlitz <ogerlitz@mellanox.com>,
Sean Hefty <sean.hefty@intel.com>
Subject: Re: [PATCH] staging: rdma: Fix braces around if/else
Date: Sun, 4 Oct 2015 11:05:50 +0200 [thread overview]
Message-ID: <20151004090550.GA4161@wheatley> (raw)
In-Reply-To: <20151004072009.GA8336@kroah.com>
[-- Attachment #1.1: Type: text/plain, Size: 1300 bytes --]
On Sun, Oct 04, 2015 at 08:20:09AM +0100, Greg Kroah-Hartman wrote:
>On Sun, Oct 04, 2015 at 09:47:52AM +0300, Or Gerlitz wrote:
>> On 10/3/2015 11:55 PM, Martin Kletzander wrote:
>> >Get rid of all ELSE_AFTER_BRACE type errors reported by checkpatch.pl.
>>
>> Hi Greg,
>>
>> Is there a way to signal people/tools that a certain driver parks in staging
>> on their way **out** of the kernel
>> and not the other way around? I guess you (nor Doug) don't want to spend
>> time on fixing such drivers, right?
>
>I'm not spending the time :)
>
>But no, there isn't a way to really show that that I know of, and it's
>fine, we end up getting a number of "cleanup" patches for a kernel
>release or two before the drivers get deleted. It gets people involved
>in kernel development which is the key thing here, it's not like they
>are actually using these drivers...
>
>So it's fine, I take the patches, the people writing the patches are
>happy, and the code gets a bit nicer and feels better about itself
>before we kick it out the door.
>
I didn't mean to waste anyone's time on this. I'm just trying to get
more familiar with the patch submission process into the kernel. And
I'm doing this in my free time despite the address used. I probably
should've noted that below to commit message.
Martin
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 169 bytes --]
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
next prev parent reply other threads:[~2015-10-04 9:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-03 20:55 [PATCH] staging: rdma: Fix braces around if/else Martin Kletzander
2015-10-04 6:47 ` Or Gerlitz
[not found] ` <5610CB98.1090907-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2015-10-04 7:20 ` Greg Kroah-Hartman
2015-10-04 9:05 ` Martin Kletzander [this message]
2015-10-04 10:11 ` Greg Kroah-Hartman
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=20151004090550.GA4161@wheatley \
--to=mkletzan@redhat.com \
--cc=devel@driverdev.osuosl.org \
--cc=dledford@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=hal.rosenstock@gmail.com \
--cc=infinipath@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=ogerlitz@mellanox.com \
--cc=sean.hefty@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox