linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Williams <dcbw@redhat.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: reinette chatre <reinette.chatre@intel.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Nico -telmich- Schottelius <nico-linux-next@schottelius.org>,
	"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	"John W. Linville" <linville@tuxdriver.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: iwlagn broken in next-20090514 and next-20090515
Date: Mon, 18 May 2009 14:35:20 -0400	[thread overview]
Message-ID: <1242671720.3845.4.camel@localhost.localdomain> (raw)
In-Reply-To: <1242670211.29049.10.camel@johannes.local>

On Mon, 2009-05-18 at 20:10 +0200, Johannes Berg wrote:
> On Mon, 2009-05-18 at 13:50 -0400, Dan Williams wrote:
> 
> > > > > > Also wpa_supplicant is not happy:
> > > > > > 
> > > > > > + wpa_supplicant -B -Dwext -iwlan0 -c /home/user/nico/ethz/wlan/wpa_supplicant.conf
> > > > > > ioctl[SIOCSIWENCODEEXT]: No such file or directory
> > > > > > ioctl[SIOCSIWENCODEEXT]: No such file or directory
> > > > > > ioctl[SIOCSIWENCODEEXT]: No such file or directory
> > > > > > ioctl[SIOCSIWENCODEEXT]: No such file or directory
> > > > > > 
> > > > 
> > > > There were some changes recently to this ioctl, but I am not familiar
> > > > with details. Johannes will know.
> > > 
> > > Yeah, I'm not sure -- this happens when clearing keys. I'll look into
> > > it, we probably need to accept removing a key that doesn't exist.
> > 
> > Why bother (if that's actually the root cause)?  Maybe the supplicant
> > should be fixed.  Other drivers return ENOENT in this case, so mac80211
> > certainly isn't out-of-common-spec here now.
> 
> I just looked at the code in wpa_supplicant, it doesn't care a bit, just
> prints the error. Problem is users attribute any other breakage to the
> error it prints since our behaviour changed...

I meant "make wpa_supplicant not print anything out on -ENOENT".

Dan

  reply	other threads:[~2009-05-18 18:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-15  5:37 linux-next: Tree for May 15 Stephen Rothwell
2009-05-15 10:26 ` iwlagn broken in next-20090514 and next-20090514 Nico -telmich- Schottelius
     [not found]   ` <20090515102621.GA5735-9ll+q7fL1vOwdVNcq5OhcUB+6BGkLq7r@public.gmane.org>
2009-05-18  7:15     ` iwlagn broken in next-20090514 and next-20090515 Stephen Rothwell
     [not found]       ` <20090518171505.d30d2f64.sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2009-05-18 16:03         ` reinette chatre
2009-05-18 16:16           ` Dan Williams
2009-05-18 16:24           ` Johannes Berg
2009-05-18 17:50             ` Dan Williams
2009-05-18 18:10               ` Johannes Berg
2009-05-18 18:35                 ` Dan Williams [this message]
2009-05-15 13:07 ` linux-next: Tree for May 15 Borislav Petkov
2009-05-17 14:07   ` Stephen Rothwell
2009-05-18  9:48     ` Borislav Petkov
2009-05-18 23:36       ` Stephen Rothwell

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=1242671720.3845.4.camel@localhost.localdomain \
    --to=dcbw@redhat.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=nico-linux-next@schottelius.org \
    --cc=reinette.chatre@intel.com \
    --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 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).