From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: devel <devel@driverdev.osuosl.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-next <linux-next@vger.kernel.org>,
Jim Davis <jim.epost@gmail.com>,
christian.gromm@microchip.com
Subject: Re: randconfig build error with next-20150729, in drivers/staging/most/aim-network/networking.c
Date: Wed, 29 Jul 2015 10:56:28 -0700 [thread overview]
Message-ID: <20150729175628.GA22749@kroah.com> (raw)
In-Reply-To: <20150729170743.GK5180@mwanda>
On Wed, Jul 29, 2015 at 08:07:43PM +0300, Dan Carpenter wrote:
> Randy Dunlap posted a patch for this. It has to depend on NET.
Yes, I should get this merged later this evening, thanks.
greg k-h
prev parent reply other threads:[~2015-07-29 17:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-29 16:18 randconfig build error with next-20150729, in drivers/staging/most/aim-network/networking.c Jim Davis
2015-07-29 17:07 ` Dan Carpenter
2015-07-29 17:56 ` 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=20150729175628.GA22749@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=christian.gromm@microchip.com \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=jim.epost@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).