linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: John Garry <john.garry@huawei.com>
Cc: mchehab+samsung@kernel.org, linux-mtd@lists.infradead.org,
	linux-kernel@vger.kernel.org, frieder.schrempf@kontron.de,
	linux-doc@vger.kernel.org
Subject: Re: [PATCH] docs: mtd: Update spi nor reference driver
Date: Fri, 6 Sep 2019 09:03:25 -0600	[thread overview]
Message-ID: <20190906090325.330a5945@lwn.net> (raw)
In-Reply-To: <9110efc4-35e6-ff04-1a6d-d5d9f93927de@huawei.com>

On Fri, 6 Sep 2019 15:58:41 +0100
John Garry <john.garry@huawei.com> wrote:

> I don't think that it was appropriate to apply this patch in the end - 
> maybe this could have been communicated better. If you check the 
> subsequent discussion in this thread, it seems that completely new 
> documentation is required:
> 
> "Actually it seems like the whole file is obsolete and needs to be
> removed or replaced by proper documentation of the SPI MEM API."
> 
> But nothing seems to be happening there...

Ah, OK, I lost track of that somewhere along the way.

Unless you object I'll leave it applied, it's not going to do any harm,
methinks.

jon

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

  reply	other threads:[~2019-09-06 15:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-06 16:06 [PATCH] docs: mtd: Update spi nor reference driver John Garry
2019-08-06 16:35 ` John Garry
2019-08-06 16:40   ` Schrempf Frieder
2019-08-16 10:20     ` John Garry
2019-08-19  4:39       ` Vignesh Raghavendra
2019-08-20 14:09         ` John Garry
2019-08-20 16:58           ` Mark Brown
2019-08-21 13:39             ` John Garry
2019-09-06 14:52 ` Jonathan Corbet
2019-09-06 14:58   ` John Garry
2019-09-06 15:03     ` Jonathan Corbet [this message]
2019-09-06 15:10       ` Tudor.Ambarus

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=20190906090325.330a5945@lwn.net \
    --to=corbet@lwn.net \
    --cc=frieder.schrempf@kontron.de \
    --cc=john.garry@huawei.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=mchehab+samsung@kernel.org \
    /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).