From: Richard Weinberger <richard@nod.at>
To: Mukesh Ojha <mojha@codeaurora.org>
Cc: linux-kernel@vger.kernel.org, Yue Haibing <yuehaibing@huawei.com>,
adrian.hunter@intel.com, linux-mtd@lists.infradead.org,
dedekind1@gmail.com
Subject: Re: [PATCH -next] ubifs: remove unused function __ubifs_shash_final
Date: Thu, 21 Mar 2019 09:09:28 +0100 [thread overview]
Message-ID: <24657306.kQxLvZqZK3@blindfold> (raw)
In-Reply-To: <289f9994-0980-081e-f913-5729b16d16f4@codeaurora.org>
Am Donnerstag, 21. März 2019, 08:54:55 CET schrieb Mukesh Ojha:
> >> Acked-by: Mukesh Ojha <mojha@codeaurora.org>
> > I guess you mean Reviewed-by?
>
> As i am unsure about future scope of this func. i.e why Acked.
Acked-by is usually something I expect from the code author
or the person that owns the code.
Thanks,
//richard
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
WARNING: multiple messages have this Message-ID (diff)
From: Richard Weinberger <richard@nod.at>
To: Mukesh Ojha <mojha@codeaurora.org>
Cc: Yue Haibing <yuehaibing@huawei.com>,
dedekind1@gmail.com, adrian.hunter@intel.com,
linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org
Subject: Re: [PATCH -next] ubifs: remove unused function __ubifs_shash_final
Date: Thu, 21 Mar 2019 09:09:28 +0100 [thread overview]
Message-ID: <24657306.kQxLvZqZK3@blindfold> (raw)
In-Reply-To: <289f9994-0980-081e-f913-5729b16d16f4@codeaurora.org>
Am Donnerstag, 21. März 2019, 08:54:55 CET schrieb Mukesh Ojha:
> >> Acked-by: Mukesh Ojha <mojha@codeaurora.org>
> > I guess you mean Reviewed-by?
>
> As i am unsure about future scope of this func. i.e why Acked.
Acked-by is usually something I expect from the code author
or the person that owns the code.
Thanks,
//richard
next prev parent reply other threads:[~2019-03-21 8:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-20 14:09 [PATCH -next] ubifs: remove unused function __ubifs_shash_final Yue Haibing
2019-03-20 14:09 ` Yue Haibing
2019-03-20 20:05 ` Mukesh Ojha
2019-03-20 20:05 ` Mukesh Ojha
2019-03-20 20:18 ` Richard Weinberger
2019-03-20 20:18 ` Richard Weinberger
2019-03-21 7:54 ` Mukesh Ojha
2019-03-21 7:54 ` Mukesh Ojha
2019-03-21 8:09 ` Richard Weinberger [this message]
2019-03-21 8:09 ` Richard Weinberger
2019-03-22 6:59 ` Mukesh Ojha
2019-03-22 6:59 ` Mukesh Ojha
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=24657306.kQxLvZqZK3@blindfold \
--to=richard@nod.at \
--cc=adrian.hunter@intel.com \
--cc=dedekind1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=mojha@codeaurora.org \
--cc=yuehaibing@huawei.com \
/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.