From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Peter Huewe <peterhuewe@gmx.de>,
Marcel Selhorst <tpmdd@selhorst.net>,
Jason Gunthorpe <jgunthorpe@obsidianresearch.com>,
Colin Ian King <colin.king@canonical.com>,
tpmdd-devel@lists.sourceforge.net,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] tpm: constify transmit data pointers
Date: Sat, 9 Sep 2017 00:46:34 +0300 [thread overview]
Message-ID: <20170908214634.2kglubmagnblmrmy@linux.intel.com> (raw)
In-Reply-To: <CAK8P3a2nHEU7y98+jt+nSYfmRA-ju6SZhEJqTXqS_StU1d5p-g@mail.gmail.com>
On Fri, Sep 08, 2017 at 10:58:55PM +0200, Arnd Bergmann wrote:
> On Thu, Sep 7, 2017 at 6:24 PM, Jarkko Sakkinen
> <jarkko.sakkinen@linux.intel.com> wrote:
> > On Thu, Sep 07, 2017 at 03:30:45PM +0200, Arnd Bergmann wrote:
> >>
> >
> > Thank you Arnd. Do you mind if squash this to Colin's commit and your
> > signed-off-by to that one?
>
> Either way works, but if you merge the two commits into one, please
> clarify in the description who did what part, otherwise it might look like
> I just forwarded Jason's original patch to you.
>
> Arnd
I think it could be also a separate patch just to in order to make
that simple and also to retain information for git blame. Thanks.
/Jarkko
next prev parent reply other threads:[~2017-09-08 21:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-07 13:30 [PATCH] tpm: constify transmit data pointers Arnd Bergmann
2017-09-07 16:24 ` Jarkko Sakkinen
2017-09-08 20:58 ` Arnd Bergmann
2017-09-08 21:46 ` Jarkko Sakkinen [this message]
[not found] ` <20170907133130.2463746-1-arnd-r2nGTMty4D4@public.gmane.org>
2017-09-07 20:01 ` Jason Gunthorpe
2017-09-07 20:01 ` Jason Gunthorpe
2017-09-08 21:28 ` Jarkko Sakkinen
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=20170908214634.2kglubmagnblmrmy@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=arnd@arndb.de \
--cc=colin.king@canonical.com \
--cc=jgunthorpe@obsidianresearch.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--cc=tpmdd-devel@lists.sourceforge.net \
--cc=tpmdd@selhorst.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 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.