All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Yoshinori Sato <ysato@users.sourceforge.jp>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org
Subject: Re: h8300 pull request for 5.14-rc?
Date: Thu, 20 Jan 2022 08:52:33 +0100	[thread overview]
Message-ID: <20220120075233.GA4777@lst.de> (raw)
In-Reply-To: <20210913054915.GA3631@lst.de>

On Mon, Sep 13, 2021 at 07:49:15AM +0200, Christoph Hellwig wrote:
> Hi Yoshinori-san,
> 
> what happened to the h8300 pull request with the set_fs() removal that
> is in linux-next?

Given that we're at the end of yet another merge window:  what is the
status of the h8300 tree?  As far as I can tell the last pull request
was in July 2019, and it has commit since just after that.

  parent reply	other threads:[~2022-01-20  7:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-13  5:49 h8300 pull request for 5.14-rc? Christoph Hellwig
2021-09-13  5:52 ` Randy Dunlap
2021-09-13  5:58   ` Christoph Hellwig
2021-09-13  6:03     ` Randy Dunlap
2022-01-20  7:52 ` Christoph Hellwig [this message]
2022-01-20 23:40   ` Stephen Rothwell
2022-01-24  8:44     ` Geert Uytterhoeven

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=20220120075233.GA4777@lst.de \
    --to=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=ysato@users.sourceforge.jp \
    /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.