public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Cc: "backports@vger.kernel.org" <backports@vger.kernel.org>,
	Dan Williams <dcbw@redhat.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 06/18] compat: backport ASYNC_DOMAIN_EXCLUSIVE()
Date: Wed, 10 Apr 2013 21:39:51 +0200	[thread overview]
Message-ID: <1365622791.4235.38.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <CAB=NE6W8wZbwGiCCq2n2LObNreWhxd-uFU7CrX5yJw2Uik9hAg@mail.gmail.com> (sfid-20130410_213320_489401_CDFE35C3)

On Wed, 2013-04-10 at 12:32 -0700, Luis R. Rodriguez wrote:

> >> Oh I agree don't get me wrong, however porting kernel/async.c seems
> >> like a rather separate effort worth considering. As-is though I have
> >> not seen any negative impact though to keep older subsystems from
> >> compiling, ie its a no-op for older kernels as I see it.
> >
> > I guess that's what I don't understand -- I don't see usages of
> > ASYNC_DOMAIN_EXCLUSIVE in any header files, and in e.g. regulator/core.c
> > you'd also need the functions async_schedule_domain() etc. So where does
> > this help even compiling?
> 
> You know what, sorry this was left over from when I tried to backport
> the regulatory to the core of compat, and since I decided to not even
> go there given that it relies on init sections on the vmlinux we can
> safely discard this patch (although what I said still hold, just not
> needed).

Ok. Yeah after looking at the users I actually do agree this won't
really hurt, but it seemed it doesn't help anything at all hence my
confusion... :)

johannes


  reply	other threads:[~2013-04-10 19:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1365593728-5720-1-git-send-email-mcgrof@do-not-panic.com>
     [not found] ` <1365593728-5720-7-git-send-email-mcgrof@do-not-panic.com>
     [not found]   ` <1365600139.4235.4.camel@jlt4.sipsolutions.net>
     [not found]     ` <CAB=NE6UpP-X1NCTNRnoSdv_bk3ioZdg5bO1zz0U0dqeWVxZdLw@mail.gmail.com>
     [not found]       ` <1365614413.4235.29.camel@jlt4.sipsolutions.net>
2013-04-10 17:26         ` [PATCH 06/18] compat: backport ASYNC_DOMAIN_EXCLUSIVE() Luis R. Rodriguez
2013-04-10 18:20           ` Johannes Berg
2013-04-10 19:19             ` Luis R. Rodriguez
2013-04-10 19:27               ` Johannes Berg
2013-04-10 19:32                 ` Luis R. Rodriguez
2013-04-10 19:39                   ` Johannes Berg [this message]
2013-04-10 19:40                     ` Luis R. Rodriguez

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=1365622791.4235.38.camel@jlt4.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=backports@vger.kernel.org \
    --cc=dcbw@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcgrof@do-not-panic.com \
    /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