From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: "Ardelean, Alexandru" <alexandru.Ardelean@analog.com>
Cc: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"peterhuewe@gmx.de" <peterhuewe@gmx.de>,
"linux-integrity@vger.kernel.org"
<linux-integrity@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"jgg@ziepe.ca" <jgg@ziepe.ca>, "arnd@arndb.de" <arnd@arndb.de>
Subject: Re: [PATCH V2] tpm_tis_spi: use new `delay` structure for SPI transfer delays
Date: Tue, 17 Dec 2019 03:26:11 +0200 [thread overview]
Message-ID: <f4ac8ac982daf33f5b2a5bdc0bf63f67fd40413a.camel@linux.intel.com> (raw)
In-Reply-To: <6920bc5e8bc932dd85fa8e14755d2e6999512f25.camel@analog.com>
On Thu, 2019-12-12 at 07:21 +0000, Ardelean, Alexandru wrote:
> That's a habit from Github's Markdown.
> We keep our kernel repo on Github and Markdown formats `text` into a
> certain form.
Ah.
> When I open a PR, the PR text is formatted to highlight certain elements
> [that I want highlighted].
> I did not get any comments on it so far.
>
> I can change it if you want.
>
> As a secondary note: Markdown seems to be used on Gitlab and Bitbucket
Please change it.
/Jarkko
next prev parent reply other threads:[~2019-12-17 1:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-04 8:00 [PATCH] tpm_tis_spi: use new `delay` structure for SPI transfer delays Alexandru Ardelean
2019-12-09 19:50 ` Jarkko Sakkinen
2019-12-10 6:56 ` [PATCH V2] " Alexandru Ardelean
2019-12-11 17:37 ` Jarkko Sakkinen
2019-12-12 7:21 ` Ardelean, Alexandru
2019-12-17 1:26 ` Jarkko Sakkinen [this message]
2019-12-17 9:16 ` [PATCH V3] tpm_tis_spi: use new 'delay' " Alexandru Ardelean
2019-12-17 12:04 ` Jarkko Sakkinen
2020-02-26 7:51 ` Ardelean, Alexandru
2020-02-26 15:10 ` Jarkko Sakkinen
2020-02-26 15:11 ` Ardelean, Alexandru
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=f4ac8ac982daf33f5b2a5bdc0bf63f67fd40413a.camel@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=alexandru.Ardelean@analog.com \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=jgg@ziepe.ca \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterhuewe@gmx.de \
/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).