From: Pawan Gupta <pawan.kumar.gupta@linux.intel.com>
To: speck@linutronix.de
Subject: [MODERATED] Re: [PATCH v6 1/9] TAAv6 1
Date: Mon, 21 Oct 2019 13:35:28 -0700 [thread overview]
Message-ID: <20191021203528.GD23497@guptapadev.amr> (raw)
In-Reply-To: <alpine.DEB.2.21.1910151453090.1924@nanos.tec.linutronix.de>
On Tue, Oct 15, 2019 at 02:54:04PM +0200, speck for Thomas Gleixner wrote:
> On Wed, 9 Oct 2019, speck for Pawan Gupta wrote:
> > On Wed, Oct 09, 2019 at 04:34:01PM -0700, speck for Pawan Gupta wrote:
> > > On Wed, Oct 09, 2019 at 04:22:56PM -0700, speck for Pawan Gupta wrote:
> > > > Transactional Synchronization Extensions (TSX) may be used on certain
> > > > processors as part of a speculative side channel attack. A microcode
> > > > update for existing processors that are vulnerable to this attack will
> > > > add a new MSR, IA32_TSX_CTRL to allow the system administrator the
> > > > option to disable TSX as one of the possible mitigations. [Note that
> > > > future processors that are not vulnerable will also support the
> > > > IA32_TSX_CTRL MSR]. Add defines for the new IA32_TSX_CTRL MSR and its
> > > > bits.
> > >
> > > For some reason the "From:" and the "Subject:" lines are not getting
> > > copied to the body. I am using the same "speckify-gitmail" script.
> > >
> > > $ git format-patch --cover-letter -n --thread -v6 -o ../v6 --to speck@linutronix.de v5.3..HEAD
> > > $ speckify-gitmail -s "TAAv6" v6 speck
> > >
> > > Let me see whats wrong and re-send the series. Sorry for the trouble.
> >
> > Speckify-gitmail script is doing the right thing. Dumping the message body
> > content just before gpg.encrypt() shows the correct "From:" and "Subject:". I
> > don't know where it is getting stripped off.
> >
> > Thanks,
> > Pawan
> >
> > --- a/speckify-gitmail
> > +++ b/speckify-gitmail
> > @@ -105,6 +105,7 @@ for f in sorted(infiles):
> > content = 'From: %s\n' %mfrom
>
> Can you try to insert a blank newline before the From:?
>
> content = '\nFrom: %s\n' %mfrom
Thanks, "\n" fixed it.
-Pawan
next prev parent reply other threads:[~2019-10-21 20:41 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-09 23:21 [MODERATED] [PATCH v6 0/9] TAAv6 0 Pawan Gupta
2019-10-09 23:22 ` [MODERATED] [PATCH v6 1/9] TAAv6 1 Pawan Gupta
2019-10-09 23:23 ` [MODERATED] [PATCH v6 2/9] TAAv6 2 Pawan Gupta
2019-10-09 23:24 ` [MODERATED] [PATCH v6 3/9] TAAv6 3 Pawan Gupta
2019-10-09 23:25 ` [MODERATED] [PATCH v6 4/9] TAAv6 4 Pawan Gupta
2019-10-09 23:26 ` [MODERATED] [PATCH v6 5/9] TAAv6 5 Pawan Gupta
2019-10-09 23:27 ` [MODERATED] [PATCH v6 6/9] TAAv6 6 Pawan Gupta
2019-10-09 23:28 ` [MODERATED] [PATCH v6 7/9] TAAv6 7 Pawan Gupta
2019-10-09 23:29 ` [MODERATED] [PATCH v6 8/9] TAAv6 8 Pawan Gupta
2019-10-09 23:30 ` [MODERATED] [PATCH v6 9/9] TAAv6 9 Pawan Gupta
2019-10-09 23:34 ` [MODERATED] Re: [PATCH v6 1/9] TAAv6 1 Pawan Gupta
2019-10-10 1:23 ` Pawan Gupta
2019-10-15 12:54 ` Thomas Gleixner
2019-10-21 20:35 ` Pawan Gupta [this message]
2019-10-09 23:38 ` [MODERATED] " Andrew Cooper
2019-10-09 23:40 ` Andrew Cooper
2019-10-09 23:53 ` Luck, Tony
2019-10-10 0:01 ` Andrew Cooper
2019-10-10 16:51 ` Luck, Tony
[not found] ` <5d9e6daa.1c69fb81.f84ad.88ceSMTPIN_ADDED_BROKEN@mx.google.com>
2019-10-10 6:47 ` [MODERATED] Re: [PATCH v6 3/9] TAAv6 3 Greg KH
2019-10-10 23:44 ` Pawan Gupta
[not found] ` <5d9e6e22.1c69fb81.6df19.ff55SMTPIN_ADDED_BROKEN@mx.google.com>
2019-10-10 6:50 ` [MODERATED] Re: [PATCH v6 5/9] TAAv6 5 Greg KH
2019-10-10 21:18 ` Pawan Gupta
2019-10-10 6:50 ` Greg KH
[not found] ` <5d9e6f13.1c69fb81.d7036.be99SMTPIN_ADDED_BROKEN@mx.google.com>
2019-10-10 6:54 ` [MODERATED] Re: [PATCH v6 9/9] TAAv6 9 Greg KH
2019-10-12 1:41 ` Pawan Gupta
2019-10-13 20:05 ` Ben Hutchings
2019-10-13 21:00 ` Ben Hutchings
[not found] ` <4b15283c29b75be3177eb7c4b8601be5644f630e.157065=?utf-8?q?8889?= .git.pawan.kumar.gupta@linux.intel.com>
2019-10-18 1:21 ` [MODERATED] Re: [PATCH v6 8/9] TAAv6 8 Ben Hutchings
2019-10-21 20:04 ` [MODERATED] Re: [PATCH v6 0/9] TAAv6 0 Josh Poimboeuf
2019-10-21 20:09 ` Pawan Gupta
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=20191021203528.GD23497@guptapadev.amr \
--to=pawan.kumar.gupta@linux.intel.com \
--cc=speck@linutronix.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).