From: Randy Dunlap <randy.dunlap@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>, Greg KH <greg@kroah.com>,
driverdevel <devel@driverdev.osuosl.org>,
gregkh@suse.de, linux-next@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -next] staging/brcm80211: fix printk format warnings
Date: Thu, 03 Mar 2011 08:08:36 -0800 [thread overview]
Message-ID: <4D6FBD04.6090702@oracle.com> (raw)
In-Reply-To: <20110303072028.GA21427@sdf-MacBook>
On 03/02/11 23:20, Stanislav Fomichev wrote:
>> Maybe due to conflict resolutions in my tree (assuming that Randy based
>> his patch in linux-next).
> We don't have brcm80211/sys/ directory (it was renamed to
> brcm80211/brcmsmac); so it's based on the wrong/outdated tree.
It was based on linux-next of 2011-0301, which is what the patch email
was in reply to.
> And I suppose these errors are already fixed.
Good to know. Thanks.
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
prev parent reply other threads:[~2011-03-03 16:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-01 7:11 linux-next: Tree for March 1 Stephen Rothwell
2011-03-01 18:49 ` linux-next: Tree for March 1 (staging/winbond) Randy Dunlap
2011-03-01 19:10 ` Pekka Enberg
2011-03-01 19:19 ` Randy Dunlap
2011-03-01 19:35 ` Pekka Enberg
2011-03-01 19:39 ` Randy Dunlap
2011-03-01 20:05 ` Pekka Enberg
2011-03-01 20:07 ` Greg KH
2011-03-02 0:29 ` [PATCH -next] staging/brcm80211: fix printk format warnings Randy Dunlap
2011-03-02 14:07 ` Roland Vossen
2011-03-02 21:02 ` Greg KH
2011-03-02 21:05 ` Greg KH
2011-03-02 23:36 ` Stephen Rothwell
2011-03-03 7:20 ` Stanislav Fomichev
2011-03-03 16:08 ` Randy Dunlap [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=4D6FBD04.6090702@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=greg@kroah.com \
--cc=gregkh@suse.de \
--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 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.