public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Daniel Golle <daniel@makrotopia.org>
Cc: linux-mtd <linux-mtd@lists.infradead.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	Miquel Raynal <miquel.raynal@bootlin.com>
Subject: Re: [PATCH 0/2] ubi: wire up parent device
Date: Tue, 14 Feb 2023 17:21:07 +0100 (CET)	[thread overview]
Message-ID: <290910672.129444.1676391667993.JavaMail.zimbra@nod.at> (raw)
In-Reply-To: <Y+uztjxDdtFy6MJ4@makrotopia.org>

----- Ursprüngliche Mail -----
> I've only recently noticed that this series is marked as 'Accepted' in
> patchwork. However, I fail to find the commits in any public linux
> tree, nor has patchwork sent the usual notification email informing me
> about it being accepted.
> 
> Can it be that it has slipped under the table (or even the carpet)
> somehow?
> 
> Please let me know if there is anything wrong with this series and/or
> if I should re-submit it, or if I shall just wait for it to surface in
> linux-mtd or linux-next.

The patches are in linux-ubifs #next and in linux-next itself.
See:
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=05b8773ca33253ea562be145cf3145b05ef19f86

So, all good. :-)
 
Thanks,
//richard

      reply	other threads:[~2023-02-14 16:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-22 19:32 [PATCH 0/2] ubi: wire up parent device Daniel Golle
2022-12-22 19:33 ` [PATCH 1/2] mtd: ubi: wire-up parent MTD device Daniel Golle
2022-12-22 19:33 ` [PATCH 2/2] mtd: ubi: block: wire-up device parent Daniel Golle
2023-02-14 16:15 ` [PATCH 0/2] ubi: wire up parent device Daniel Golle
2023-02-14 16:21   ` 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=290910672.129444.1676391667993.JavaMail.zimbra@nod.at \
    --to=richard@nod.at \
    --cc=daniel@makrotopia.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=miquel.raynal@bootlin.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