All of lore.kernel.org
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Zheng Zhang <zheng.zhang@email.ucr.edu>
Cc: Richard Weinberger <richard@nod.at>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	linux-mtd <linux-mtd@lists.infradead.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Alexander Usyskin <alexander.usyskin@intel.com>,
	Tomas Winkler <tomas.winkler@intel.com>,
	Vitaly Lubart <vitaly.lubart@intel.com>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Zhang Xiaoxu <zhangxiaoxu5@huawei.com>
Subject: Re: kernel BUG in __put_mtd_device
Date: Tue, 1 Aug 2023 08:58:47 +0200	[thread overview]
Message-ID: <20230801085847.46c7db12@xps-13> (raw)
In-Reply-To: <CAC_GQSp7W=MoiWoWo+UFFcZ48JLwsnfL84QWTJm_DNLO7S9AxQ@mail.gmail.com>

Hi Zheng,

zheng.zhang@email.ucr.edu wrote on Mon, 31 Jul 2023 16:58:49 -0700:

> Could you tell me the base Linux version of this patch? It seems that the
> context is not consistent with 6.2 or newest version v6.5.rc4
> Thanks

mtd/next, where new changes have been brought to these functions

https://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux.git/log/?h=mtd/next

Thanks,
Miquèl

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

WARNING: multiple messages have this Message-ID (diff)
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Zheng Zhang <zheng.zhang@email.ucr.edu>
Cc: Richard Weinberger <richard@nod.at>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	linux-mtd <linux-mtd@lists.infradead.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Alexander Usyskin <alexander.usyskin@intel.com>,
	Tomas Winkler <tomas.winkler@intel.com>,
	Vitaly Lubart <vitaly.lubart@intel.com>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Zhang Xiaoxu <zhangxiaoxu5@huawei.com>
Subject: Re: kernel BUG in __put_mtd_device
Date: Tue, 1 Aug 2023 08:58:47 +0200	[thread overview]
Message-ID: <20230801085847.46c7db12@xps-13> (raw)
In-Reply-To: <CAC_GQSp7W=MoiWoWo+UFFcZ48JLwsnfL84QWTJm_DNLO7S9AxQ@mail.gmail.com>

Hi Zheng,

zheng.zhang@email.ucr.edu wrote on Mon, 31 Jul 2023 16:58:49 -0700:

> Could you tell me the base Linux version of this patch? It seems that the
> context is not consistent with 6.2 or newest version v6.5.rc4
> Thanks

mtd/next, where new changes have been brought to these functions

https://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux.git/log/?h=mtd/next

Thanks,
Miquèl

  parent reply	other threads:[~2023-08-01  6:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAC_GQSpE5nbj7Lt=8sXu8GoSQTRd+=fpZb_zpVKQOJ4MxRHzsw@mail.gmail.com>
2023-07-31  5:35 ` kernel BUG in __put_mtd_device Richard Weinberger
2023-07-31  7:46   ` Miquel Raynal
2023-07-31  7:46     ` Miquel Raynal
     [not found]   ` <CAC_GQSp7W=MoiWoWo+UFFcZ48JLwsnfL84QWTJm_DNLO7S9AxQ@mail.gmail.com>
2023-08-01  6:58     ` Miquel Raynal [this message]
2023-08-01  6:58       ` 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=20230801085847.46c7db12@xps-13 \
    --to=miquel.raynal@bootlin.com \
    --cc=alexander.usyskin@intel.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=richard@nod.at \
    --cc=tomas.winkler@intel.com \
    --cc=vigneshr@ti.com \
    --cc=vitaly.lubart@intel.com \
    --cc=zhangxiaoxu5@huawei.com \
    --cc=zheng.zhang@email.ucr.edu \
    /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.