linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Mika Westerberg <mika.westerberg@linux.intel.com>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Bartosz Golaszewski <bgolaszewski@baylibre.com>,
	"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
	ACPI Devel Maling List <linux-acpi@vger.kernel.org>
Subject: Re: [PATCH 0/1 resend] gpiolib: acpi: Add missing __init(const) markers to initcall-s
Date: Fri, 27 Mar 2020 22:13:59 +0100	[thread overview]
Message-ID: <CACRpkdavyR7FRGMZFHZUvRhm9PL-X4SQQszN4HQn-+qpAhJnHw@mail.gmail.com> (raw)
In-Reply-To: <20200325103956.109284-1-hdegoede@redhat.com>

On Wed, Mar 25, 2020 at 11:40 AM Hans de Goede <hdegoede@redhat.com> wrote:

> I know it has not been that long ago since I send this out, but still
> I have the feeling this one seems to have fallen through the cracks?
>
> It has already been Acked by Mika, so if you can queue it up in
> linux-gpio/for-next that would be great.

It requires the fixes I just sent to Torvalds to be applied first.
I simply need that stuff to be upstream before I can apply this.
That is why it is deferred.

Sometimes it happens that random fixes are dependent on
critical fixes, then the critical fixes need to land upstream before
the random fix can be applied, this is one of those cases.

Yours,
Linus Walleij

      parent reply	other threads:[~2020-03-27 21:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-25 10:39 [PATCH 0/1 resend] gpiolib: acpi: Add missing __init(const) markers to initcall-s Hans de Goede
2020-03-25 10:39 ` [PATCH " Hans de Goede
2020-04-16  7:34   ` Linus Walleij
2020-03-27 21:13 ` Linus Walleij [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=CACRpkdavyR7FRGMZFHZUvRhm9PL-X4SQQszN4HQn-+qpAhJnHw@mail.gmail.com \
    --to=linus.walleij@linaro.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=bgolaszewski@baylibre.com \
    --cc=hdegoede@redhat.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.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;
as well as URLs for NNTP newsgroup(s).