From: Stephen Rothwell <sfr@canb.auug.org.au>
To: SeongJae Park <sjpark@amazon.com>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
SeongJae Park <sjpark@amazon.de>
Subject: Re: linux-next: Fixes tag needs some work in the scsi-fixes tree
Date: Wed, 24 Jun 2020 17:23:26 +1000 [thread overview]
Message-ID: <20200624172326.43723eca@canb.auug.org.au> (raw)
In-Reply-To: <20200624071447.19529-1-sjpark@amazon.com>
[-- Attachment #1: Type: text/plain, Size: 309 bytes --]
Hi SeongJae,
On Wed, 24 Jun 2020 09:14:47 +0200 SeongJae Park <sjpark@amazon.com> wrote:
>
> Oops, sorry for the mistake. I will send the fixed version in reply to this.
Unless Martin says otherwise, I am not sure it is worth fixing. Just
remember for next time.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-06-24 7:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-24 7:07 linux-next: Fixes tag needs some work in the scsi-fixes tree Stephen Rothwell
2020-06-24 7:14 ` SeongJae Park
2020-06-24 7:17 ` [PATCH v2] scsi: lpfc: Avoid another null dereference in lpfc_sli4_hba_unset() SeongJae Park
2020-06-24 7:23 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-09-03 8:47 linux-next: Fixes tag needs some work in the scsi-fixes tree Stephen Rothwell
2020-09-04 1:51 ` Martin K. Petersen
2020-05-08 11:33 Stephen Rothwell
2020-05-11 23:54 ` Martin K. Petersen
2019-02-05 20:20 Stephen Rothwell
2019-02-06 3:55 ` Vaibhav Jain
2019-02-06 4:34 ` Stephen Rothwell
2019-02-06 13:03 ` Martin K. Petersen
2019-01-29 20:53 Stephen Rothwell
2019-01-23 5:34 Stephen Rothwell
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=20200624172326.43723eca@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=sjpark@amazon.com \
--cc=sjpark@amazon.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).