From: luis@debethencourt.com (Luis de Bethencourt)
To: kernelnewbies@lists.kernelnewbies.org
Subject: [PATCH 0/4] staging: wilc1000: cover letter
Date: Tue, 7 Jul 2015 11:23:37 +0200 [thread overview]
Message-ID: <20150707092337.GA1502@goodgumbo.baconseed.org> (raw)
In-Reply-To: <20150707022209.GD12574@kroah.com>
On Mon, Jul 06, 2015 at 07:22:09PM -0700, Greg Kroah-Hartman wrote:
> On Fri, Jun 26, 2015 at 04:43:44PM +0200, Luis de Bethencourt wrote:
> > Patches to be applied on top of
> > https://patchwork.kernel.org/patch/6655831/
>
> I don't use patchwork, and when on an airplane with no internet access
> (like right now), a url provides no context at all. Always use email
> subject lines or something that I can actually reference properly while
> offline...
>
> thanks,
>
> greg k-h
OK. Sorry. Didn't knew this but noted for the future.
Thanks for the reviews and merges!
Luis
prev parent reply other threads:[~2015-07-07 9:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-26 14:43 [PATCH 0/4] staging: wilc1000: cover letter Luis de Bethencourt
2015-07-07 2:22 ` Greg Kroah-Hartman
2015-07-07 9:23 ` Luis de Bethencourt [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=20150707092337.GA1502@goodgumbo.baconseed.org \
--to=luis@debethencourt.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).