From: Greg KH <gregkh@linuxfoundation.org>
To: Dylan Leggio <dleggio1@binghamton.edu>
Cc: aditya.shankar@microchip.com, ganesh.krishna@microchip.com,
linux-wireless@vger.kernel.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: wilc1000: fix two typos in #define's
Date: Fri, 17 Mar 2017 09:31:21 +0900 [thread overview]
Message-ID: <20170317003121.GB28811@kroah.com> (raw)
In-Reply-To: <20170316215112.GA2427@legs>
On Thu, Mar 16, 2017 at 05:51:12PM -0400, Dylan Leggio wrote:
> Signed-off-by: Dylan Leggio <dleggio1@binghamton.edu>
I can't take patches without any changelog text at all, sorry.
greg k-h
next prev parent reply other threads:[~2017-03-17 0:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-16 21:51 [PATCH] Staging: wilc1000: fix two typos in #define's Dylan Leggio
2017-03-17 0:31 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-03-17 0:54 Dylan Leggio
2017-03-17 0:57 Dylan Leggio
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=20170317003121.GB28811@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=aditya.shankar@microchip.com \
--cc=devel@driverdev.osuosl.org \
--cc=dleggio1@binghamton.edu \
--cc=ganesh.krishna@microchip.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@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;
as well as URLs for NNTP newsgroup(s).