From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: John David Anglin <dave.anglin@bell.net>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
James Bottomley <James.Bottomley@HansenPartnership.com>,
Bart Van Assche <bvanassche@acm.org>,
linux-parisc <linux-parisc@vger.kernel.org>,
linux-scsi@vger.kernel.org, Greg KH <greg@kroah.com>
Subject: Re: Broken Domain Validation in 6.1.84+
Date: Mon, 08 Apr 2024 10:32:12 -0400 [thread overview]
Message-ID: <yq1le5oorjp.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <450f1fa5-c564-46d6-8066-9becc5091d5a@bell.net> (John David Anglin's message of "Mon, 8 Apr 2024 10:17:50 -0400")
> The patch I received by mail was in html format and wasn't installable
> by simply saving message. So, I used link in message.
>
> I see I can change view of mail to plain text. Maybe I can copy the
> plain text view to a patch file.
Peculiar. You can grab the raw mail from lore:
https://lore.kernel.org/linux-scsi/yq1wmp9pb0d.fsf@ca-mkp.ca.oracle.com/raw
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2024-04-08 14:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-04 16:20 Broken Domain Validation in 6.1.84+ John David Anglin
2024-04-04 16:32 ` Bart Van Assche
2024-04-04 20:07 ` John David Anglin
2024-04-05 19:36 ` Bart Van Assche
2024-04-06 14:30 ` John David Anglin
2024-04-06 15:06 ` James Bottomley
2024-04-06 16:16 ` John David Anglin
2024-04-06 18:51 ` James Bottomley
2024-04-07 6:16 ` Greg KH
2024-04-07 13:19 ` Martin K. Petersen
2024-04-08 0:58 ` John David Anglin
2024-04-08 13:46 ` Martin K. Petersen
2024-04-08 14:17 ` John David Anglin
2024-04-08 14:32 ` Martin K. Petersen [this message]
2024-04-08 15:17 ` John David Anglin
2024-04-08 17:19 ` Martin K. Petersen
2024-04-11 4:40 ` Cyril Brulebois
2024-04-11 7:29 ` Greg KH
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=yq1le5oorjp.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=bvanassche@acm.org \
--cc=dave.anglin@bell.net \
--cc=greg@kroah.com \
--cc=linux-parisc@vger.kernel.org \
--cc=linux-scsi@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.