Linux-Next Archive on lore.kernel.org
 help / color / Atom feed
From: Sowjanya Komatineni <skomatineni@nvidia.com>
To: Jens Axboe <axboe@kernel.dk>, Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Dmitry Osipenko <digetx@gmail.com>,
	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 block tree
Date: Sun, 11 Apr 2021 19:26:47 -0700
Message-ID: <02ac7276-e3c7-79b2-b3b0-361bbb884d16@nvidia.com> (raw)
In-Reply-To: <0aa24415-74c5-1adc-6e27-edf37285de4e@kernel.dk>


On 4/11/21 7:14 PM, Jens Axboe wrote:
> On 4/11/21 4:34 PM, Stephen Rothwell wrote:
>> Hi all,
>>
>> Commit
>>
>>    6fa6517fe62e ("ata: ahci_tegra: call tegra_powergate_power_off only when PM domain is not present")
>>
>> is missing a Signed-off-by from its author.
> Sowjana, please reply that you're OK with me adding your Signed-off-by to that
> patch.
>
Sorry I should have checked that. Thanks Jens. Sure I am OK with it.

Thank you

Sowjanya


  reply index

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-11 22:34 Stephen Rothwell
2021-04-12  2:14 ` Jens Axboe
2021-04-12  2:26   ` Sowjanya Komatineni [this message]
2021-04-12  2:36     ` Jens Axboe
  -- strict thread matches above, loose matches on Subject: below --
2021-06-08 22:31 Stephen Rothwell
2021-03-18 23:16 Stephen Rothwell
2021-03-18 23:25 ` Jens Axboe
2021-03-19  8:02   ` Stefan Metzmacher
2021-03-19 13:08     ` Jens Axboe
2021-03-19 13:10       ` Stefan Metzmacher
2021-03-04 23:54 Stephen Rothwell
2021-01-25  9:43 Stephen Rothwell
2021-01-25 15:18 ` Jens Axboe
2020-12-02 20:52 Stephen Rothwell
2020-06-26 23:08 Stephen Rothwell
2020-04-08 21:59 Stephen Rothwell
2019-05-22 21:50 Stephen Rothwell
2019-05-22 23:26 ` Jens Axboe
2018-12-16  6:26 Stephen Rothwell
2018-12-16 10:18 ` Christoph Hellwig
2018-12-16 15:33   ` Jens Axboe
2018-08-05 21:51 Stephen Rothwell
2018-08-06  1:16 ` Jens Axboe

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=02ac7276-e3c7-79b2-b3b0-361bbb884d16@nvidia.com \
    --to=skomatineni@nvidia.com \
    --cc=axboe@kernel.dk \
    --cc=digetx@gmail.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

Linux-Next Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-next/0 linux-next/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-next linux-next/ https://lore.kernel.org/linux-next \
		linux-next@vger.kernel.org
	public-inbox-index linux-next

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-next


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git