linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@gmail.com>
To: Chris Clayton <chris2553@googlemail.com>
Cc: linux-wireless@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: Oops in wireless from today's git
Date: Sun, 10 May 2009 23:26:26 +0200	[thread overview]
Message-ID: <4A074682.6010403@gmail.com> (raw)
In-Reply-To: <c6b1100b0905101239n564e4379v5460c281260950bc@mail.gmail.com>

On 05/10/2009 09:39 PM, Chris Clayton wrote:
> I've just done a git pull and built, installed and booted the kernel.
> Unfortunately I got the oops below.

What's your HEAD? Looks like the issue solved by
0cc113d866fa87c1455cbaff8d1f7ac054090bd5.

  reply	other threads:[~2009-05-10 21:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-10 19:39 Oops in wireless from today's git Chris Clayton
2009-05-10 21:26 ` Jiri Slaby [this message]
2009-05-10 22:29   ` Chris Clayton
2009-05-11  6:43     ` Jiri Slaby
2009-05-11  8:38       ` Chris Clayton
2009-05-11  8:45         ` Jiri Slaby

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=4A074682.6010403@gmail.com \
    --to=jirislaby@gmail.com \
    --cc=chris2553@googlemail.com \
    --cc=linux-kernel@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).