From: Robert Jarzmik <robert.jarzmik@free.fr>
To: David Miller <davem@davemloft.net>
Cc: linus.walleij@linaro.org, nico@fluxnic.net,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Revert "smc91x: retrieve IRQ and trigger flags in a modern way"
Date: Thu, 19 Feb 2015 21:48:49 +0100 [thread overview]
Message-ID: <87egpl8w5q.fsf@free.fr> (raw)
In-Reply-To: <20150219.152841.891912250243016754.davem@davemloft.net> (David Miller's message of "Thu, 19 Feb 2015 15:28:41 -0500 (EST)")
David Miller <davem@davemloft.net> writes:
>> Now if you can make it in -rc2 or -rc3, this revert should be forgotten. But if
>> you can't make it for 3.20, I'll push for the revert.
>>
>> So I think it's up to you now, and let's see what Gregh says about it.
>
> What is the current status of this? I'd like to see this move forward so we
> can get this fixed ASAP.
Hi David,
Linus has submitted the patch [1]. I'll be watching carefully until -rc4 that
this is applied. If it's not, I'll reping you to apply this revert. Until then,
you can forget about it, I'll do the follow-up.
Does that plan sound good to you ?
Cheers.
--
Robert
[1] https://lkml.org/lkml/2015/2/18/310
next prev parent reply other threads:[~2015-02-19 20:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-12 16:59 [PATCH] Revert "smc91x: retrieve IRQ and trigger flags in a modern way" Robert Jarzmik
2015-02-13 2:16 ` Linus Walleij
2015-02-13 8:12 ` Robert Jarzmik
2015-02-13 16:06 ` Robert Jarzmik
2015-02-19 20:28 ` David Miller
2015-02-19 20:48 ` Robert Jarzmik [this message]
2015-02-19 21:22 ` David Miller
2015-03-16 21:06 ` Robert Jarzmik
2015-03-17 19:05 ` David Miller
2015-05-04 13:18 ` Linus Walleij
2015-05-04 19:13 ` David Miller
2015-02-20 9:37 ` Linus Walleij
2015-02-20 15:33 ` Greg KH
2015-02-23 15:14 ` Linus Walleij
2015-02-13 16:08 ` Robert Jarzmik
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=87egpl8w5q.fsf@free.fr \
--to=robert.jarzmik@free.fr \
--cc=davem@davemloft.net \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nico@fluxnic.net \
/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).