From: Sam Ravnborg <sam@ravnborg.org>
To: James Ettle <james@ettle.org.uk>
Cc: linux-nfs@vger.kernel.org, sparclinux@vger.kernel.org
Subject: Re: Unaligned access in gss_{get,verify}_mic_v2() on sparc64
Date: Sun, 28 Jan 2018 21:08:30 +0100 [thread overview]
Message-ID: <20180128200830.GA30041@ravnborg.org> (raw)
In-Reply-To: <2fad5cab-915c-a224-a1f1-b96a77a8546d@ettle.org.uk>
On Sun, Jan 28, 2018 at 04:34:57PM +0000, James Ettle wrote:
> Hi,
>
> Just a polite prod in case it's fallen off the radar. The patch in this thread still applies cleanly to 4.14.15.
I would recommend you to send this as a new mail - with a proper [PATCH] in the title.
Otherwise it may not be picked up.
Posting a patch in the midle of a thread is no-go.
Sam
WARNING: multiple messages have this Message-ID (diff)
From: Sam Ravnborg <sam@ravnborg.org>
To: James Ettle <james@ettle.org.uk>
Cc: linux-nfs@vger.kernel.org, sparclinux@vger.kernel.org
Subject: Re: Unaligned access in gss_{get,verify}_mic_v2() on sparc64
Date: Sun, 28 Jan 2018 20:08:30 +0000 [thread overview]
Message-ID: <20180128200830.GA30041@ravnborg.org> (raw)
In-Reply-To: <2fad5cab-915c-a224-a1f1-b96a77a8546d@ettle.org.uk>
On Sun, Jan 28, 2018 at 04:34:57PM +0000, James Ettle wrote:
> Hi,
>
> Just a polite prod in case it's fallen off the radar. The patch in this thread still applies cleanly to 4.14.15.
I would recommend you to send this as a new mail - with a proper [PATCH] in the title.
Otherwise it may not be picked up.
Posting a patch in the midle of a thread is no-go.
Sam
next prev parent reply other threads:[~2018-01-28 20:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-02 23:28 Unaligned access in gss_{get,verify}_mic_v2() on sparc64 James Ettle
2017-12-02 23:28 ` James Ettle
2017-12-06 19:09 ` J. Bruce Fields
2017-12-06 19:09 ` J. Bruce Fields
2017-12-07 1:42 ` James Ettle
2017-12-07 1:42 ` James Ettle
2018-01-28 16:34 ` James Ettle
2018-01-28 20:08 ` Sam Ravnborg [this message]
2018-01-28 20:08 ` Sam Ravnborg
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=20180128200830.GA30041@ravnborg.org \
--to=sam@ravnborg.org \
--cc=james@ettle.org.uk \
--cc=linux-nfs@vger.kernel.org \
--cc=sparclinux@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.