From: "John W. Linville" <linville@tuxdriver.com>
To: Jade Bilkey <herself@thefumon.com>
Cc: linux-wireless@vger.kernel.org, ath5k-devel@venema.h4ckr.net
Subject: Re: [PATCH v2] ath5k: added debugfs file for dumping eeprom
Date: Thu, 11 Sep 2014 14:11:49 -0400 [thread overview]
Message-ID: <20140911181148.GA22872@tuxdriver.com> (raw)
In-Reply-To: <20140909193237.GN29412@tuxdriver.com>
On Tue, Sep 09, 2014 at 03:32:38PM -0400, John W. Linville wrote:
> The original patch was already merged. To make a change, you need
> to post a new patch based on the new head of the tree. This one just
> conflicts with what is already there now.
>
> Also, I think all you really need is a "#include <linux/vmalloc.h>".
>
> Post a v3 that just adds the #include?
Nevermind, Dave M. already merged such a patch in net-next...
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
prev parent reply other threads:[~2014-09-11 18:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-06 17:00 [PATCH v2] ath5k: added debugfs file for dumping eeprom Jade Bilkey
2014-09-09 19:32 ` John W. Linville
2014-09-11 18:11 ` John W. Linville [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=20140911181148.GA22872@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=ath5k-devel@venema.h4ckr.net \
--cc=herself@thefumon.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.