linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Jesper Juhl <jj@chaosbits.net>
Cc: Greg KH <greg@kroah.com>,
	devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
	linux-wireless@vger.kernel.org,
	Jason Cooper <jason@lakedaemon.net>,
	Arend van Spriel <arend@broadcom.com>,
	Roland Vossen <rvossen@broadcom.com>,
	Dowan Kim <dowan@broadcom.com>,
	Henry Ptasinski <henryp@broadcom.com>,
	Brett Rudley <brudley@broadcom.com>,
	trivial@kernel.org
Subject: Re: [PATCH][trivial] Remove duplicate inclusion of wlc_event.h in drivers/staging/brcm80211/sys/wlc_mac80211.c
Date: Wed, 9 Feb 2011 13:27:10 -0800	[thread overview]
Message-ID: <20110209212710.GA751@suse.de> (raw)
In-Reply-To: <alpine.LNX.2.00.1102092218140.21858@swampdragon.chaosbits.net>

On Wed, Feb 09, 2011 at 10:18:59PM +0100, Jesper Juhl wrote:
> On Wed, 9 Feb 2011, Greg KH wrote:
> 
> > On Sun, Feb 06, 2011 at 10:52:17PM +0100, Jesper Juhl wrote:
> > > We include wlc_event.h twice in 
> > > drivers/staging/brcm80211/sys/wlc_mac80211.c
> > > Once is enough.
> > 
> > Odd, this file isn't even in the linux-next tree anymore, what tree did
> > you make this against?
> > 
> Linus' tree - can't remember what HEAD was at when I made that patch, but 
> I probably pulled it the same day I sent the mail.

Please always send trivial stuff like this against linux-next, otherwise
it often times isn't relevant at all anymore.

thanks,

greg k-h

      reply	other threads:[~2011-02-09 21:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-06 21:52 [PATCH][trivial] Remove duplicate inclusion of wlc_event.h in drivers/staging/brcm80211/sys/wlc_mac80211.c Jesper Juhl
2011-02-09 19:45 ` Greg KH
2011-02-09 21:18   ` Jesper Juhl
2011-02-09 21:27     ` 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=20110209212710.GA751@suse.de \
    --to=gregkh@suse.de \
    --cc=arend@broadcom.com \
    --cc=brudley@broadcom.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=dowan@broadcom.com \
    --cc=greg@kroah.com \
    --cc=henryp@broadcom.com \
    --cc=jason@lakedaemon.net \
    --cc=jj@chaosbits.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=rvossen@broadcom.com \
    --cc=trivial@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;
as well as URLs for NNTP newsgroup(s).