public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: "Arnd Bergmann" <arnd@arndb.de>
Cc: "Valentin Korenblit" <vkorenblit@sequans.com>,
	linux-mtd@lists.infradead.org, ye.xingchen@zte.com.cn
Subject: Re: [PATCH v4] mtd: rawnand: cadence: support 64-bit slave dma interface
Date: Tue, 18 Oct 2022 11:27:27 +0200	[thread overview]
Message-ID: <20221018112727.5dd2e1f6@xps-13> (raw)
In-Reply-To: <b222053a-9c76-4fdd-9c68-0b04eeb7168a@app.fastmail.com>

Hi Arnd, Valentin,

arnd@arndb.de wrote on Tue, 18 Oct 2022 11:23:04 +0200:

> On Tue, Oct 18, 2022, at 11:20 AM, Valentin Korenblit wrote:
> >
> > I copy/pasted the link that I received in Arnd's email.
> >
> > Maybe this is better:
> >
> > https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org/thread/3NMACGIM5NDUBPXRT5RTBZON6LQE5A3B/  
> 
> To clarify: my point was about using the official 'Link:' tag
> in the changelog text rather than having a free-form link.
> 
> When linking to a mailing list post, the best option
> is usually one from lore.kernel.org. the lists.01.org
> link is probably fine if the thread is not archived on lore.

It is:

https://lore.kernel.org/all/b7e5ebb4-0de8-4958-9bc4-fe06ec4c3635@www.fastmail.com/t/

Valentin, can you eventually send a v5 with this link if you agree?

Thanks,
Miquèl

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

  reply	other threads:[~2022-10-18  9:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-18  9:16 [PATCH v4] mtd: rawnand: cadence: support 64-bit slave dma interface Valentin Korenblit
2022-10-18  9:17 ` Miquel Raynal
2022-10-18  9:20   ` Valentin Korenblit
2022-10-18  9:23     ` Arnd Bergmann
2022-10-18  9:27       ` Miquel Raynal [this message]
2022-10-18  9:25     ` Miquel Raynal

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=20221018112727.5dd2e1f6@xps-13 \
    --to=miquel.raynal@bootlin.com \
    --cc=arnd@arndb.de \
    --cc=linux-mtd@lists.infradead.org \
    --cc=vkorenblit@sequans.com \
    --cc=ye.xingchen@zte.com.cn \
    /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