Linux wireless drivers development
 help / color / mirror / Atom feed
From: Stanislav Fomichev <kernel@fomichev.me>
To: Greg KH <greg@kroah.com>
Cc: brudley@broadcom.com, gregkh@suse.de, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] brcm80211: fix warnings in wl_check_firmwares
Date: Sat, 19 Feb 2011 12:25:17 +0300	[thread overview]
Message-ID: <20110219092422.GA1828@sdf-MacBook> (raw)
In-Reply-To: <20110218205731.GD796@kroah.com>

> On Sat, Feb 12, 2011 at 08:47:00PM +0300, Stanislav Fomichev wrote:
> > Use %zu instead of %d for size_t
> > 
> > Signed-off-by: Stanislav Fomichev <kernel@fomichev.me>
> > ---
> >  drivers/staging/brcm80211/sys/wl_mac80211.c |    4 ++--
> 
> This doesn't apply to linux-next as this file isn't around anymore :(
This is not relevant anymore as I see you included the other patch with
the same title (which is based on the right tree).

-- 
	Stas

      reply	other threads:[~2011-02-19  9:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-12 17:47 [PATCH] brcm80211: fix warnings in wl_check_firmwares Stanislav Fomichev
2011-02-18 20:57 ` Greg KH
2011-02-19  9:25   ` Stanislav Fomichev [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=20110219092422.GA1828@sdf-MacBook \
    --to=kernel@fomichev.me \
    --cc=brudley@broadcom.com \
    --cc=greg@kroah.com \
    --cc=gregkh@suse.de \
    --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