From: Tony Lindgren <tony@atomide.com>
To: "Pali Rohár" <pali.rohar@gmail.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
Nicolas Pitre <nico@linaro.org>,
Russell King - ARM Linux <linux@arm.linux.org.uk>
Subject: Re: [PATCH 0/3] Drop more omap3 legacy board-*.c files for v4.2
Date: Tue, 5 May 2015 10:00:21 -0700 [thread overview]
Message-ID: <20150505170020.GF21061@atomide.com> (raw)
In-Reply-To: <201505051839.36882@pali>
* Pali Rohár <pali.rohar@gmail.com> [150505 09:41]:
> On Tuesday 05 May 2015 17:06:38 Tony Lindgren wrote:
> > * Pali Rohár <pali.rohar@gmail.com> [150505 07:55]:
> > > On Tuesday 05 May 2015 07:43:08 Tony Lindgren wrote:
> > > > * Arnd Bergmann <arnd@arndb.de> [150505 03:56]:
> > > > > On Monday 04 May 2015 13:01:54 Tony Lindgren wrote:
> > > > > > For dropping the remaining omap3 legacy boot support,
> > > > > > we still have the following board-*.c files:
> > > > > >
> > > > > > BOARD REASON NEEDED
> > > > > > board-ldp.c Still used in RMKs boot test
> > > > > > system board-omap3logic.c Getting a .dts file
> > > > > > for v4.2 board-omap3pandora.c Got a .dts file for
> > > > > > v4.1 board-rx51-*.c Needs /proc/atags
> > > > > > support for user space
> > > > > >
> > > > > > I'm hoping we can drop those for v4.3 merge window,
> > > > > > then keep the platform data around for one more merge
> > > > > > window in case of reverting needed, then drop the
> > > > > > platform data too for v4.4 if no issues needing
> > > > > > reverting are found.
> > > > >
> > > > > Sounds great. Has there been a conclusion about what to
> > > > > do for the rx51 /proc/atags support?
> > > >
> > > > I believe we just need to enable /proc/atags also for
> > > > device tree based booting if CONFIG_ARM_ATAG_DTB_COMPAT.
> > > > Pali may have more info on that.
> > > >
> > > > Then looks like Pali's two patches for showing the
> > > > revision are still pending in thread "[PATCH v2 0/2] ARM:
> > > > /proc/cpuinfo: DT: Add support for Revision":
> > > >
> > > > http://www.spinics.net/lists/arm-kernel/msg401535.html
> > >
> > > I think I already sent all need patches to ML. But I did not
> > > check if you merged them or not. I did not get any new
> > > comments for them for a while and right now I do not have
> > > time for looking at it again.
> >
> > Oh OK, do you have link to the /proc/atags patch somewhere?
> >
> > Maybe Arnd and Nico can pick them up and sort out how we
> > should queue them with Russell?
> >
>
> https://lkml.org/lkml/2015/1/26/648
Hmm looks like you should resend all your pending four patches
properly with the people mentioned above in Cc to the LAKML
and linux-omap.. Assuming something will happen to them when
the patches are buried into a middle of some old threads does
not work well.. Best to just follow das protokoll und whine and
follow up until the patches get merged :)
Regards,
Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] Drop more omap3 legacy board-*.c files for v4.2
Date: Tue, 5 May 2015 10:00:21 -0700 [thread overview]
Message-ID: <20150505170020.GF21061@atomide.com> (raw)
In-Reply-To: <201505051839.36882@pali>
* Pali Roh?r <pali.rohar@gmail.com> [150505 09:41]:
> On Tuesday 05 May 2015 17:06:38 Tony Lindgren wrote:
> > * Pali Roh?r <pali.rohar@gmail.com> [150505 07:55]:
> > > On Tuesday 05 May 2015 07:43:08 Tony Lindgren wrote:
> > > > * Arnd Bergmann <arnd@arndb.de> [150505 03:56]:
> > > > > On Monday 04 May 2015 13:01:54 Tony Lindgren wrote:
> > > > > > For dropping the remaining omap3 legacy boot support,
> > > > > > we still have the following board-*.c files:
> > > > > >
> > > > > > BOARD REASON NEEDED
> > > > > > board-ldp.c Still used in RMKs boot test
> > > > > > system board-omap3logic.c Getting a .dts file
> > > > > > for v4.2 board-omap3pandora.c Got a .dts file for
> > > > > > v4.1 board-rx51-*.c Needs /proc/atags
> > > > > > support for user space
> > > > > >
> > > > > > I'm hoping we can drop those for v4.3 merge window,
> > > > > > then keep the platform data around for one more merge
> > > > > > window in case of reverting needed, then drop the
> > > > > > platform data too for v4.4 if no issues needing
> > > > > > reverting are found.
> > > > >
> > > > > Sounds great. Has there been a conclusion about what to
> > > > > do for the rx51 /proc/atags support?
> > > >
> > > > I believe we just need to enable /proc/atags also for
> > > > device tree based booting if CONFIG_ARM_ATAG_DTB_COMPAT.
> > > > Pali may have more info on that.
> > > >
> > > > Then looks like Pali's two patches for showing the
> > > > revision are still pending in thread "[PATCH v2 0/2] ARM:
> > > > /proc/cpuinfo: DT: Add support for Revision":
> > > >
> > > > http://www.spinics.net/lists/arm-kernel/msg401535.html
> > >
> > > I think I already sent all need patches to ML. But I did not
> > > check if you merged them or not. I did not get any new
> > > comments for them for a while and right now I do not have
> > > time for looking at it again.
> >
> > Oh OK, do you have link to the /proc/atags patch somewhere?
> >
> > Maybe Arnd and Nico can pick them up and sort out how we
> > should queue them with Russell?
> >
>
> https://lkml.org/lkml/2015/1/26/648
Hmm looks like you should resend all your pending four patches
properly with the people mentioned above in Cc to the LAKML
and linux-omap.. Assuming something will happen to them when
the patches are buried into a middle of some old threads does
not work well.. Best to just follow das protokoll und whine and
follow up until the patches get merged :)
Regards,
Tony
next prev parent reply other threads:[~2015-05-05 17:00 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-04 20:01 [PATCH 0/3] Drop more omap3 legacy board-*.c files for v4.2 Tony Lindgren
2015-05-04 20:01 ` Tony Lindgren
2015-05-04 20:01 ` [PATCH 1/3] ARM: OMAP2+: Remove legacy booting support for cm-t35 Tony Lindgren
2015-05-04 20:01 ` Tony Lindgren
2015-05-04 20:01 ` [PATCH 2/3] ARM: OMAP2+: Remove legacy booting support for Overo Tony Lindgren
2015-05-04 20:01 ` Tony Lindgren
2015-05-06 16:14 ` Ash Charles
2015-05-06 16:14 ` Ash Charles
2015-05-04 20:01 ` [PATCH 3/3] ARM: OMAP2+: Remove legacy booting support for Beagleboards Tony Lindgren
2015-05-04 20:01 ` Tony Lindgren
2015-05-05 10:54 ` [PATCH 0/3] Drop more omap3 legacy board-*.c files for v4.2 Arnd Bergmann
2015-05-05 10:54 ` Arnd Bergmann
2015-05-05 14:43 ` Tony Lindgren
2015-05-05 14:43 ` Tony Lindgren
2015-05-05 14:54 ` Pali Rohár
2015-05-05 14:54 ` Pali Rohár
2015-05-05 15:06 ` Tony Lindgren
2015-05-05 15:06 ` Tony Lindgren
2015-05-05 16:39 ` Pali Rohár
2015-05-05 16:39 ` Pali Rohár
2015-05-05 16:58 ` Nicolas Pitre
2015-05-05 16:58 ` Nicolas Pitre
2015-05-05 17:00 ` Tony Lindgren [this message]
2015-05-05 17:00 ` Tony Lindgren
2015-05-06 8:52 ` Pali Rohár
2015-05-06 8:52 ` Pali Rohár
2015-05-06 14:42 ` Tony Lindgren
2015-05-06 14:42 ` Tony Lindgren
2015-05-15 19:52 ` Pali Rohár
2015-05-15 19:52 ` Pali Rohár
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=20150505170020.GF21061@atomide.com \
--to=tony@atomide.com \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=nico@linaro.org \
--cc=pali.rohar@gmail.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 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.