public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org>
To: Martin Kletzander <mkletzan-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: devel-gWbeCf7V1WCQmaza687I9mD2FQJk+8+b@public.gmane.org,
	linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Hal Rosenstock
	<hal.rosenstock-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	Mike Marciniszyn
	<infinipath-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
	Or Gerlitz <ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>,
	Sean Hefty <sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: Re: [PATCH] staging: rdma: Fix braces around if/else
Date: Sun, 4 Oct 2015 11:11:45 +0100	[thread overview]
Message-ID: <20151004101145.GB23448@kroah.com> (raw)
In-Reply-To: <20151004090550.GA4161@wheatley>

On Sun, Oct 04, 2015 at 11:05:50AM +0200, Martin Kletzander wrote:
> 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.

No need to say _why_ you are sending kernel patches, I don't care :)

And this is a great way to get familiar with the process, it's why there
are so many things in the drivers/staging/ tree to fix up.  If we really
wanted to get the code "correct", I would just take a few days and fix
it all up myself, but that's not the goal here.

Keep it up, you are doing just fine.

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2015-10-04 10:11 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
2015-10-04 10:11         ` Greg Kroah-Hartman [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=20151004101145.GB23448@kroah.com \
    --to=gregkh-hqyy1w1ycw8ekmwlsbkhg0b+6bgklq7r@public.gmane.org \
    --cc=devel-gWbeCf7V1WCQmaza687I9mD2FQJk+8+b@public.gmane.org \
    --cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=hal.rosenstock-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=infinipath-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mkletzan-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
    --cc=sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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