From: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
To: Richard Weinberger <richard@nod.at>
Cc: Kees Cook <keescook@chromium.org>,
Boris Brezillon <bbrezillon@kernel.org>,
linux-kernel@vger.kernel.org, Marek Vasut <marek.vasut@gmail.com>,
linux-mtd@lists.infradead.org,
Brian Norris <computersforpeace@gmail.com>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH] mtd: cfi_util: mark expected switch fall-throughs
Date: Wed, 20 Mar 2019 18:36:16 -0500 [thread overview]
Message-ID: <e4ab787c-1112-5088-7afc-911f33509ed5@embeddedor.com> (raw)
In-Reply-To: <16526639.hLaf6TFmul@blindfold>
On 3/20/19 6:25 PM, Richard Weinberger wrote:
> Am Mittwoch, 20. März 2019, 22:23:21 CET schrieb Gustavo A. R. Silva:
>> So, if this is too much of a burden for people, I can add all these
>> MTD patches to my own tree for 5.2.
>
> Taking the patches via MTD is not a big deal, let's go that path.
Cool.
> For you it is more work to send many patches and getting them into the individual
> trees. :)
>
Here applies this wise phrase: It is what it is. :)
Thanks
--
Gustavo
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2019-03-20 23:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-08 18:02 [PATCH] mtd: cfi_util: mark expected switch fall-throughs Gustavo A. R. Silva
2019-03-20 20:20 ` Gustavo A. R. Silva
2019-03-20 21:05 ` Richard Weinberger
2019-03-20 21:23 ` Gustavo A. R. Silva
2019-03-20 23:25 ` Richard Weinberger
2019-03-20 23:36 ` Gustavo A. R. Silva [this message]
2019-04-10 21:16 ` Gustavo A. R. Silva
2019-04-15 8:44 ` Miquel Raynal
2019-04-15 12:57 ` Gustavo A. R. Silva
2019-04-16 17:24 ` Miquel Raynal
2019-04-16 20:49 ` Gustavo A. R. Silva
2019-05-07 14:54 ` Gustavo A. R. Silva
2019-05-07 15:49 ` Richard Weinberger
2019-05-07 15:59 ` Gustavo A. R. Silva
2019-05-09 6:53 ` Miquel Raynal
2019-04-10 21:46 ` Kees Cook
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=e4ab787c-1112-5088-7afc-911f33509ed5@embeddedor.com \
--to=gustavo@embeddedor.com \
--cc=bbrezillon@kernel.org \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=richard@nod.at \
/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).