From: Greg KH <gregkh@suse•de>
To: Randy Dunlap <randy.dunlap@oracle•com>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
driverdevel <devel@driverdev•osuosl.org>,
linux-next@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>
Subject: Re: linux-next: Tree for April 28 (staging/wlan-ng: prism2)
Date: Thu, 28 Apr 2011 19:15:36 -0700 [thread overview]
Message-ID: <20110429021536.GB22138@suse.de> (raw)
In-Reply-To: <20110428092917.039071a4.randy.dunlap@oracle.com>
On Thu, Apr 28, 2011 at 09:29:17AM -0700, Randy Dunlap wrote:
> On Thu, 28 Apr 2011 15:25:34 +1000 Stephen Rothwell wrote:
>
> > Hi all,
>
>
> drivers/staging/wlan-ng/prism2fw.c:1115: warning: the frame size of 4288 bytes is larger than 2048 bytes
>
> Noooooo.
Heh. What caused this? I don't remember changing anything here
recently.
thanks,
greg k-h
prev parent reply other threads:[~2011-04-29 2:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-28 5:25 linux-next: Tree for April 28 Stephen Rothwell
2011-04-28 16:29 ` linux-next: Tree for April 28 (staging/wlan-ng: prism2) Randy Dunlap
2011-04-29 2:15 ` Greg KH [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=20110429021536.GB22138@suse.de \
--to=gregkh@suse$(echo .)de \
--cc=devel@driverdev$(echo .)osuosl.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=randy.dunlap@oracle$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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