From: Damien Le Moal <damien.lemoal@opensource.wdc.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: Signed-off-by missing for commit in the libata tree
Date: Wed, 19 Oct 2022 13:47:15 +0900 [thread overview]
Message-ID: <ac0b4f51-acdb-a5d3-07f8-8e96a8a5a6e6@opensource.wdc.com> (raw)
In-Reply-To: <20221019072605.7d6c8cbd@canb.auug.org.au>
On 10/19/22 05:26, Stephen Rothwell wrote:
> Hi all,
>
> Commit
>
> 61503af327ca ("scsi: libsas: make use of ata_port_is_frozen() helper")
>
> is missing a Signed-off-by from its committer.
Oops. My bad. Fixed now.
Thanks !
--
Damien Le Moal
Western Digital Research
prev parent reply other threads:[~2022-10-19 4:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 20:26 linux-next: Signed-off-by missing for commit in the libata tree Stephen Rothwell
2022-10-19 4:47 ` Damien Le Moal [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=ac0b4f51-acdb-a5d3-07f8-8e96a8a5a6e6@opensource.wdc.com \
--to=damien.lemoal@opensource.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 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).