All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lauri Kasanen <cand@gmx.com>
To: Chaitanya Kulkarni <chaitanya.kulkarni@wdc.com>
Cc: linux-mips@vger.kernel.org, tsbogend@alpha.franken.de,
	axboe@kernel.dk, linux-block@vger.kernel.org, cand@gmx.com
Subject: Re: [PATCH 0/9] n64: small cleanups
Date: Tue, 26 Jan 2021 10:00:30 +0200	[thread overview]
Message-ID: <20210126100030.374cd4adbd3b9db72ecaa757@gmx.com> (raw)
In-Reply-To: <20210125233243.5982-1-chaitanya.kulkarni@wdc.com>

On Mon, 25 Jan 2021 15:32:34 -0800
Chaitanya Kulkarni <chaitanya.kulkarni@wdc.com> wrote:

> I've got the reviewed-by tag from the driver owner offline which
> is added to the series.

I confirm this, he sent it privately first. I approve the series.

- Lauri

  parent reply	other threads:[~2021-01-26 17:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-25 23:32 [PATCH 0/9] n64: small cleanups Chaitanya Kulkarni
2021-01-25 23:32 ` [PATCH 1/9] n64: use pr_fmt to avoid duplicate string Chaitanya Kulkarni
2021-01-25 23:32 ` [PATCH 2/9] n64: move module info at the end Chaitanya Kulkarni
2021-01-25 23:32 ` [PATCH 3/9] n64: move module param at the top Chaitanya Kulkarni
2021-01-25 23:32 ` [PATCH 4/9] n64: use enums for reg Chaitanya Kulkarni
2021-01-25 23:32 ` [PATCH 5/9] n64: use sector SECTOR_SHIFT instead 512 Chaitanya Kulkarni
2021-01-25 23:32 ` [PATCH 6/9] n64: remove curly brackets Chaitanya Kulkarni
2021-01-25 23:32 ` [PATCH 7/9] n64: cosmetics changes Chaitanya Kulkarni
2021-01-26  8:53   ` Sergei Shtylyov
2021-01-25 23:32 ` [PATCH 8/9] n64: cleanup n64cart_probe() Chaitanya Kulkarni
2021-01-25 23:32 ` [PATCH 9/9] n64: store dev instance into disk private data Chaitanya Kulkarni
2021-01-26  8:00 ` Lauri Kasanen [this message]
2021-02-21 22:39 ` [PATCH 0/9] n64: small cleanups Thomas Bogendoerfer

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=20210126100030.374cd4adbd3b9db72ecaa757@gmx.com \
    --to=cand@gmx.com \
    --cc=axboe@kernel.dk \
    --cc=chaitanya.kulkarni@wdc.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=tsbogend@alpha.franken.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 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.