Hi all,
The following tree have been removed form linux-next because they have
not been updated in more than a year. If you want a tree reinstated,
just let me know.
fbdev
fsl
generic-ioremap
ieee1394
this contains the single commit
67f8e65e4fc1 firewire: net: remove set but not used variable 'guid'
random
realtek
thermal-rzhang
thermal-soc
y2038
zx2c4
--
Cheers,
Stephen Rothwell
On May 14 Stephen Rothwell wrote:
> The following tree have been removed form linux-next because they have
> not been updated in more than a year. If you want a tree reinstated,
> just let me know.
>
> fbdev
> fsl
> generic-ioremap
> ieee1394
> this contains the single commit
> 67f8e65e4fc1 firewire: net: remove set but not used variable 'guid'
> random
> realtek
> thermal-rzhang
> thermal-soc
> y2038
> zx2c4
Would you be OK with adding linux1394.git (for-next branch) back to
linux-next? There are two patches queued and I am finally aiming to get
them merged. :-)
Christophe JAILLET (1):
firewire: nosy: switch from 'pci_' to 'dma_' API
YueHaibing (1):
firewire: net: remove set but not used variable 'guid'
Thank you,
--
Stefan Richter
-======--=-= -=== --=-=
http://arcgraph.de/sr/
On Jul 05 Stefan Richter wrote:
> On May 14 Stephen Rothwell wrote:
> > The following tree have been removed form linux-next because they have
> > not been updated in more than a year. If you want a tree reinstated,
> > just let me know.
> >
> > fbdev
> > fsl
> > generic-ioremap
> > ieee1394
> > this contains the single commit
> > 67f8e65e4fc1 firewire: net: remove set but not used variable 'guid'
> > random
> > realtek
> > thermal-rzhang
> > thermal-soc
> > y2038
> > zx2c4
>
> Would you be OK with adding linux1394.git (for-next branch) back to
> linux-next? There are two patches queued and I am finally aiming to get
> them merged. :-)
(PS, this is for the /next/ merge window after 5.14 is final, not for the
current window anymore of course.)
--
Stefan Richter
-======--=-= -=== --=-=
http://arcgraph.de/sr/
Hi Stefan,
On Mon, 5 Jul 2021 22:09:35 +0200 Stefan Richter <[email protected]> wrote:
>
> On Jul 05 Stefan Richter wrote:
> >
> > Would you be OK with adding linux1394.git (for-next branch) back to
> > linux-next? There are two patches queued and I am finally aiming to get
> > them merged. :-)
>
> (PS, this is for the /next/ merge window after 5.14 is final, not for the
> current window anymore of course.)
In that case, I will add it after the merge window closes, please
remind me if I forget.
--
Cheers,
Stephen Rothwell
Hi Stefan,
On Mon, 5 Jul 2021 21:57:43 +0200 Stefan Richter <[email protected]> wrote:
>
> Would you be OK with adding linux1394.git (for-next branch) back to
> linux-next? There are two patches queued and I am finally aiming to get
> them merged. :-)
>
> Christophe JAILLET (1):
> firewire: nosy: switch from 'pci_' to 'dma_' API
>
> YueHaibing (1):
> firewire: net: remove set but not used variable 'guid'
>
Readded from today.
Thanks for adding your subsystem tree as a participant of linux-next. As
you may know, this is not a judgement of your code. The purpose of
linux-next is for integration testing and to lower the impact of
conflicts between subsystems in the next merge window.
You will need to ensure that the patches/commits in your tree/series have
been:
* submitted under GPL v2 (or later) and include the Contributor's
Signed-off-by,
* posted to the relevant mailing list,
* reviewed by you (or another maintainer of your subsystem tree),
* successfully unit tested, and
* destined for the current or next Linux merge window.
Basically, this should be just what you would send to Linus (or ask him
to fetch). It is allowed to be rebased if you deem it necessary.
--
Cheers,
Stephen Rothwell
[email protected]