From: Richard Weinberger <richard.weinberger@gmail.com>
To: Vignesh Raghavendra <vigneshr@ti.com>
Cc: Richard Weinberger <richard@nod.at>,
Tudor Ambarus <tudor.ambarus@microchip.com>,
MTD Maling List <linux-mtd@lists.infradead.org>,
Miquel Raynal <miquel.raynal@bootlin.com>
Subject: Re: [GIT PULL] mtd: CFI changes for v5.4-rc1
Date: Mon, 16 Sep 2019 07:58:42 +0200 [thread overview]
Message-ID: <CAFLxGvx4AP1y6qeYPN8jUfQv6bnKntZ7jSk9FJb+QMVVV18upw@mail.gmail.com> (raw)
In-Reply-To: <5b0fbde6-7245-92f9-7336-3d376389e0b7@ti.com>
On Fri, Aug 30, 2019 at 11:09 AM Vignesh Raghavendra <vigneshr@ti.com> wrote:
>
> Hi Richard,
>
> Here is the CFI flash related PR for v5.4-rc1
Pulled. :-)
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
prev parent reply other threads:[~2019-09-16 5:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-30 9:10 [GIT PULL] mtd: CFI changes for v5.4-rc1 Vignesh Raghavendra
2019-09-16 5:58 ` Richard Weinberger [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=CAFLxGvx4AP1y6qeYPN8jUfQv6bnKntZ7jSk9FJb+QMVVV18upw@mail.gmail.com \
--to=richard.weinberger@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--cc=tudor.ambarus@microchip.com \
--cc=vigneshr@ti.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 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).