From: ebiederm@xmission.com (Eric W. Biederman)
To: David Miller <davem@davemloft.net>
Cc: rahul.lakkireddy@chelsio.com, netdev@vger.kernel.org,
kexec@lists.infradead.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, viro@zeniv.linux.org.uk,
stephen@networkplumber.org, akpm@linux-foundation.org,
torvalds@linux-foundation.org, ganeshgr@chelsio.com,
nirranjan@chelsio.com, indranil@chelsio.com
Subject: Re: [PATCH net-next v8 0/3] kernel: add support to collect hardware logs in crash recovery kernel
Date: Mon, 14 May 2018 08:11:24 -0500 [thread overview]
Message-ID: <87a7t2mlfn.fsf@xmission.com> (raw)
In-Reply-To: <20180513.201131.1649805811466916646.davem@davemloft.net> (David Miller's message of "Sun, 13 May 2018 20:11:31 -0400 (EDT)")
David Miller <davem@davemloft.net> writes:
> I'm deferring this patch series.
>
> If we can't get a reasonable review from an interested party in 10+
> days, that is not reasonable.
>
> Resubmit this once someone reviews it properly.
David I am out on vacation this week and last (the reason for the delay).
The last version of this that I looked at I gave my ack. All of my ABI
concerns had been addressed. The only outstanding change I believe was
the Eric Dumazet's asking about something being reviewed.
I just glanced over it again and I don't see any new issues introduced
by the last round of changes.
>From 10,000 feet flyover design perspectie and from an ABI perspective
this patchset seems fine.
Acked-by: "Eric W. Biederman" <ebiederm@xmission.com>
Eric
next prev parent reply other threads:[~2018-05-14 13:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-02 9:47 [PATCH net-next v8 0/3] kernel: add support to collect hardware logs in crash recovery kernel Rahul Lakkireddy
2018-05-02 9:47 ` [PATCH net-next v8 1/3] vmcore: add API to collect hardware dump in second kernel Rahul Lakkireddy
2018-05-02 9:47 ` [PATCH net-next v8 2/3] vmcore: append device dumps to vmcore as elf notes Rahul Lakkireddy
2018-05-02 9:47 ` [PATCH net-next v8 3/3] cxgb4: collect hardware dump in second kernel Rahul Lakkireddy
2018-05-07 20:03 ` [PATCH net-next v8 0/3] kernel: add support to collect hardware logs in crash recovery kernel David Miller
2018-05-14 0:11 ` David Miller
2018-05-14 13:11 ` Eric W. Biederman [this message]
2018-05-14 17:49 ` David Miller
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=87a7t2mlfn.fsf@xmission.com \
--to=ebiederm@xmission.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=ganeshgr@chelsio.com \
--cc=indranil@chelsio.com \
--cc=kexec@lists.infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nirranjan@chelsio.com \
--cc=rahul.lakkireddy@chelsio.com \
--cc=stephen@networkplumber.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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).