h8300 pull request for 5.14-rc?

h8300 pull request for 5.14-rc?

[Christoph Hellwig]

Hi Yoshinori-san,

what happened to the h8300 pull request with the set_fs() removal that
is in linux-next?

Re: h8300 pull request for 5.14-rc?

[Randy Dunlap]

On 9/12/21 10:49 PM, Christoph Hellwig wrote:
> Hi Yoshinori-san,
> 
> what happened to the h8300 pull request with the set_fs() removal that
> is in linux-next?
> 

Rich Felker says that he will look into handling the arch/sh/ patches.

https://lore.kernel.org/lkml/20210912015740.GJ13220@brightrain.aerifal.cx/

-- 
~Randy

Re: h8300 pull request for 5.14-rc?

[Christoph Hellwig]

On Sun, Sep 12, 2021 at 10:52:04PM -0700, Randy Dunlap wrote:
> Rich Felker says that he will look into handling the arch/sh/ patches.
>
> https://lore.kernel.org/lkml/20210912015740.GJ13220@brightrain.aerifal.cx/

What does that have to do with arch/h8300/?

Re: h8300 pull request for 5.14-rc?

[Randy Dunlap]

On 9/12/21 10:58 PM, Christoph Hellwig wrote:
> On Sun, Sep 12, 2021 at 10:52:04PM -0700, Randy Dunlap wrote:
>> Rich Felker says that he will look into handling the arch/sh/ patches.
>>
>> https://lore.kernel.org/lkml/20210912015740.GJ13220@brightrain.aerifal.cx/
> 
> What does that have to do with arch/h8300/?
> 

Sorry, my bad. Late here. :(

-- 
~Randy

Re: h8300 pull request for 5.14-rc?

[Christoph Hellwig]

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.

Re: h8300 pull request for 5.14-rc?

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 764 bytes --]

Hi all,

On Thu, 20 Jan 2022 08:52:33 +0100 Christoph Hellwig <hch@lst.de> wrote:
>
> 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.

The h8300-next branch (which is what I merge into linux-next) has some
more commits, but even there the last commit is from Aug 2021.  It also
has a lot of old back merges of Linus' tree, and so probably needs a
good clean.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

Re: h8300 pull request for 5.14-rc?

[Geert Uytterhoeven]

On Sat, Jan 22, 2022 at 1:25 AM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> On Thu, 20 Jan 2022 08:52:33 +0100 Christoph Hellwig <hch@lst.de> wrote:
> > On Mon, Sep 13, 2021 at 07:49:15AM +0200, Christoph Hellwig wrote:
> > > 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.
>
> The h8300-next branch (which is what I merge into linux-next) has some
> more commits, but even there the last commit is from Aug 2021.  It also
> has a lot of old back merges of Linus' tree, and so probably needs a
> good clean.

Indeed.

$ git cherry -v v5.17-rc1 uclinux-h8/h8300-next
+ caf3f4bdb535f73c6e7b828bc98097f275f819bb h8300: fix memset return value.
+ 3e138fe1a4fb6aa834b46529e4faaee4ce2d5505 h8300: Add missing symbol
"BOOT_LINK_OFFSET"
+ ece7be2c964c2aa5015e74628ca33c03a5ff4e47 h8300: move definition of
__kernel_size_t etc. to posix_types.h
+ de98871736825349b367275b0790e42ea4157350 h8300: move definition of
__kernel_size_t etc. to posix_types.h
+ 5d90be1ecf44a116b503649e67e952a7ec070745 h8300: Fix BOOT_LINK_OFFSET
+ b2c03bb18a6dd957130ad8a37f660030e4b7932a smc91x: remove GPIOLIB dependency.
+ 2fdf50bd510fd183ee89e4fdea52e7474ed9709c sh-sci: 8bit register fix.
+ 04fffbe01d2df57e600da35d3f31e3cca8ee14f4 h8300: update dts.
+ 951261bc483479d4c18ee435c35f94cccd659012 h8300_timer8: fix count mode.
+ 2c496a11304da8263e1dce9bdcef1ce04c027414 irq-renesas-h8s: fix
interrupt handling.
+ 8bd55b5fce8011d0026f7d233f7b45788f01ad0c irq-renesas-h8300h: Fix
external interrupt contorol.
+ beab3d5cb0e14e6397c4e596b3dbf1d36bf49d06 irq-renesas-h8s: Fix
external interrupt control.
+ 35b34568912cb19c53b83d6daba96fe960941279 h8300: dts: Fix /chosen:stdout-path
+ 8808515be0ed4e33de9bfdc65f4c1b547ee11065 h8300: Replace
<linux/clk-provider.h> by <linux/of_clk.h>
+ 81dd24966885113968dc5599b9b371b60c3bf7b2 h8300: remove memory.c
+ 1ec10274d436fbe77b821fbdf095b45d0888e46d h8300: don't implement set_fs

Some of these are fixes that need more explanation.
Others should be posted to public lists, and go in through a different tree
(if accepted).
Some are +2-year old fixes (perhaps I should send mine to akpm?).
The last two are Christoph's set_fs() work.

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds