linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: pali.rohar@gmail.com (Pali Rohár)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] Drop more omap3 legacy board-*.c files for v4.2
Date: Fri, 15 May 2015 21:52:39 +0200	[thread overview]
Message-ID: <201505152152.39471@pali> (raw)
In-Reply-To: <20150506144239.GH21061@atomide.com>

On Wednesday 06 May 2015 16:42:39 Tony Lindgren wrote:
> * Pali Roh?r <pali.rohar@gmail.com> [150506 01:53]:
> > On Tuesday 05 May 2015 10:00:21 Tony Lindgren wrote:
> > > * 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
> > 
> > Now I resent "ARM: /proc/cpuinfo: DT: Add support for Revision"
> > patches to MLs again without in-reply-to header.
> 
> OK thanks.
> 
> > Patches for /proc/atags I do not have currently in git format-patch
> > mbox format, so cannot resent it right now...
> 
> Well presumably you'll resend those once you find them then :)
> 
> Regards,
> 
> Tony

Now I sent them. Now you (or anybody else) can review all 4 patches :-)

-- 
Pali Roh?r
pali.rohar at gmail.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20150515/d9fa3d0d/attachment.sig>

      reply	other threads:[~2015-05-15 19:52 UTC|newest]

Thread overview: 15+ 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 ` [PATCH 1/3] ARM: OMAP2+: Remove legacy booting support for cm-t35 Tony Lindgren
2015-05-04 20:01 ` [PATCH 2/3] ARM: OMAP2+: Remove legacy booting support for Overo Tony Lindgren
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-05 10:54 ` [PATCH 0/3] Drop more omap3 legacy board-*.c files for v4.2 Arnd Bergmann
2015-05-05 14:43   ` Tony Lindgren
2015-05-05 14:54     ` Pali Rohár
2015-05-05 15:06       ` Tony Lindgren
2015-05-05 16:39         ` Pali Rohár
2015-05-05 16:58           ` Nicolas Pitre
2015-05-05 17:00           ` Tony Lindgren
2015-05-06  8:52             ` Pali Rohár
2015-05-06 14:42               ` Tony Lindgren
2015-05-15 19:52                 ` Pali Rohár [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=201505152152.39471@pali \
    --to=pali.rohar@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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;
as well as URLs for NNTP newsgroup(s).