From: Dan Carpenter <dan.carpenter@oracle.com>
To: Mark Stenglein <mark@stengle.in>
Cc: gregkh@linuxfoundation.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: wlan-ng: hfa384x.h: fixed a newline coding style issue
Date: Tue, 7 Mar 2017 20:40:20 +0300 [thread overview]
Message-ID: <20170307174020.GB4120@mwanda> (raw)
In-Reply-To: <20170307173646.GA6213@ocelotsloth-lentop.byod.gmu.edu>
On Tue, Mar 07, 2017 at 12:36:46PM -0500, Mark Stenglein wrote:
> All,
>
> Thanks for the feedback. Trying to introduce myself and in retrospect
> this seems to be a fairly non-productive way to go about it. Apologies
> for any time lost.
>
It's fine. I'm just rushing through patches as fast as possible. It
doesn't take any time.
regards,
dan carpenter
prev parent reply other threads:[~2017-03-07 17:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-06 2:09 [PATCH] Staging: wlan-ng: hfa384x.h: fixed a newline coding style issue Mark Stenglein
2017-03-06 6:53 ` Greg KH
2017-03-07 17:31 ` Dan Carpenter
2017-03-07 17:36 ` Mark Stenglein
2017-03-07 17:40 ` Dan Carpenter [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=20170307174020.GB4120@mwanda \
--to=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@stengle.in \
/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