public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>,
	Linus Walleij <linus.walleij@linaro•org>
Cc: Linux Next Mailing List <linux-next@vger•kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger•kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the gpio tree
Date: Sat, 21 Mar 2020 16:09:45 +0100	[thread overview]
Message-ID: <2195891d-4f41-a4e9-c067-2f2b556a1517@redhat.com> (raw)
In-Reply-To: <20200321162707.5f4b1951@canb.auug.org.au>

Hi,

On 3/21/20 6:27 AM, Stephen Rothwell wrote:
> Hi all,
> 
> In commit
> 
>    1b26f3ba6117 ("gpiolib: acpi: Add quirk to ignore EC wakeups on HP x2 10 CHT + AXP288 model")
> 
> Fixes tag
> 
>    Fixes: aa23ca3d98f7 ("gpiolib: acpi: Add honor_wakeup module-option + quirk mech

I see in my personal tree that I introduced this broken tag, sorry about
that. Linus, if you are ok with doing a forced push to fix it up then
the correct tag should be:

Fixes: aa23ca3d98f7 ("gpiolib: acpi: Add honor_wakeup module-option + quirk mechanism")

OTOH if you dislike forced pushes (which I completely understand)
then we will just have to live with the broken tag.

Regards,

Hans


  reply	other threads:[~2020-03-21 15:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-21  5:27 linux-next: Fixes tag needs some work in the gpio tree Stephen Rothwell
2020-03-21 15:09 ` Hans de Goede [this message]
2020-03-24  9:08   ` Linus Walleij
  -- strict thread matches above, loose matches on Subject: below --
2020-10-07 20:52 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=2195891d-4f41-a4e9-c067-2f2b556a1517@redhat.com \
    --to=hdegoede@redhat$(echo .)com \
    --cc=linus.walleij@linaro$(echo .)org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=sfr@canb$(echo .)auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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