From: David Miller <davem@davemloft.net>
To: f.fainelli@gmail.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
ebiederm@xmission.com, kexec@lists.infradead.org
Subject: Re: [PATCH net 0/2] net: dsa: bcm_sf2: Do not rely on kexec_in_progress
Date: Sat, 22 Oct 2016 16:18:16 -0400 (EDT) [thread overview]
Message-ID: <20161022.161816.874616377296105622.davem@davemloft.net> (raw)
In-Reply-To: <1477084916-26327-1-git-send-email-f.fainelli@gmail.com>
From: Florian Fainelli <f.fainelli@gmail.com>
Date: Fri, 21 Oct 2016 14:21:54 -0700
> These are the two patches following the discussing we had on
> kexec_in_progress.
>
> Feel free to apply or discard them, thanks!
Applied, thanks.
prev parent reply other threads:[~2016-10-22 20:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-21 21:21 [PATCH net 0/2] net: dsa: bcm_sf2: Do not rely on kexec_in_progress Florian Fainelli
2016-10-21 21:21 ` [PATCH net 1/2] Revert "kexec: Export kexec_in_progress to modules" Florian Fainelli
2016-10-21 21:21 ` [PATCH net 2/2] net: dsa: bcm_sf2: Do not rely on kexec_in_progress Florian Fainelli
2016-10-22 20:18 ` David Miller [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=20161022.161816.874616377296105622.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ebiederm@xmission.com \
--cc=f.fainelli@gmail.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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).