From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
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>,
Damien Le Moal <damien.lemoal@wdc.com>,
Chaitanya Kulkarni <chaitanya.kulkarni@wdc.com>,
Jens Axboe <axboe@kernel.dk>
Subject: Re: linux-next: manual merge of the scsi-fixes tree with Linus' tree
Date: Wed, 06 Nov 2019 20:56:34 -0500 [thread overview]
Message-ID: <yq1mud8zbxp.fsf@oracle.com> (raw)
In-Reply-To: <20191106082239.5c4d139c@canb.auug.org.au> (Stephen Rothwell's message of "Wed, 6 Nov 2019 08:22:39 +1100")
Stephen,
[Looks like this mail didn't go out last night]
> 8437bb81853e claims to fix d81e9d494354, however the latter is not an
> ancestor of the former ...
Should be fixed now. d81e9d494354 was part of a series that went through
Jens' tree post -rc1.
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2019-11-07 1:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-05 21:22 linux-next: manual merge of the scsi-fixes tree with Linus' tree Stephen Rothwell
2019-11-07 1:56 ` Martin K. Petersen [this message]
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=yq1mud8zbxp.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=axboe@kernel.dk \
--cc=chaitanya.kulkarni@wdc.com \
--cc=damien.lemoal@wdc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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.