From: Johannes Berg <johannes@sipsolutions.net>
To: Grazvydas Ignotas <notasas@gmail.com>
Cc: "Luis R. Rodriguez" <mcgrof@gmail.com>,
Pavel Roskin <proski@gnu.org>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH] compat: fix uevent_suppress on 2.6.29 or older kernels
Date: Fri, 23 Apr 2010 07:57:21 +0200 [thread overview]
Message-ID: <1272002241.3737.1.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <u2j6ed0b2681004221347z78c15832z3e0ff3ea51b4a5a8@mail.gmail.com>
On Thu, 2010-04-22 at 23:47 +0300, Grazvydas Ignotas wrote:
> On Thu, Apr 22, 2010 at 11:33 PM, Luis R. Rodriguez <mcgrof@gmail.com> wrote:
> > On Thu, Apr 22, 2010 at 9:42 AM, Pavel Roskin <proski@gnu.org> wrote:
> >> On Thu, 2010-04-22 at 09:33 -0700, Luis R. Rodriguez wrote:
> >>
> >>> How was this compiling for older kernels before then?
> >>
> >> Compiling was fine, but loading the firmware was failing sometimes. I'm
> >> glad somebody figured it out. Thank you, Grazvydas!
> >
> > OK Applied. I'm still puzzled, if it compiled, then that means
> > dev_set_uevent_suppress() was being defined somehow for older kernels.
>
> there was already ifdef, old code:
> #if (LINUX_VERSION_CODE >= KERNEL_VERSION(2,6,30))
> dev_set_uevent_suppress(f_dev, 1);
> #endif
>
> new code:
> #if (LINUX_VERSION_CODE >= KERNEL_VERSION(2,6,30))
> dev_set_uevent_suppress(f_dev, 1);
> #else
> f_dev->uevent_suppress = 1;
> #endif
And the argument is that the new code should be
dev_set_uevent_suppress(f_dev, 1);
and some header file should provide
static inline void dev_set_uevent_suppress(...)
{
f_dev->uevent_suppress = 1;
}
which makes perfect sense. Although Luis merged it, a fix would be
useful.
Luis, a patch changing firmware_class.c just entered the tree :P I made
it.
johannes
next prev parent reply other threads:[~2010-04-23 5:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-22 13:54 [PATCH] compat: fix uevent_suppress on 2.6.29 or older kernels Grazvydas Ignotas
2010-04-22 15:17 ` Walter Goldens
2010-04-22 16:33 ` Luis R. Rodriguez
2010-04-22 16:42 ` Pavel Roskin
2010-04-22 20:33 ` Luis R. Rodriguez
2010-04-22 20:47 ` Grazvydas Ignotas
2010-04-23 5:57 ` Johannes Berg [this message]
2010-04-23 6:01 ` Luis R. Rodriguez
2010-04-22 20:50 ` Pavel Roskin
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=1272002241.3737.1.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.com \
--cc=notasas@gmail.com \
--cc=proski@gnu.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).