From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: OMAP2+: Drop legacy board file for n900
Date: Tue, 21 Jun 2016 04:32:16 -0700 [thread overview]
Message-ID: <20160621113215.GP22406@atomide.com> (raw)
In-Reply-To: <20160621112944.GV29844@pali>
* Pali Roh?r <pali.rohar@gmail.com> [160621 04:32]:
> On Tuesday 21 June 2016 04:25:36 Tony Lindgren wrote:
> > * Tony Lindgren <tony@atomide.com> [160615 05:08]:
> > > * Pali Roh?r <pali.rohar@gmail.com> [160615 04:52]:
> > > > On Wednesday 15 June 2016 04:02:02 Tony Lindgren wrote:
> > > > > Hi,
> > > > >
> > > > > * Pali Roh?r <pali.rohar@gmail.com> [160615 03:58]:
> > > > > > Hi! I just quickly looked at N900 status matrix https://elinux.org/N900
> > > > > > and there is still one thing not finished in DT: It is slot-name for
> > > > > > omap_hsmmc driver. So switch from legacy board code to DT is regression.
> > > > >
> > > > > That's fixed with the following in v4.7-rc series:
> > > > >
> > > > > db863d896681 ("mmc: omap_hsmmc: Check if MMC slot name is passed in pdata")
> > > > > 10c1f7d32bf4 ("ARM: OMAP2+: n900 needs MMC slot names for legacy user space")
> > > >
> > > > Great! Sorry, but now wiki is not fully updated with last changes and I
> > > > do not have in my mind what was finished/merged and what not. It is
> > > > going hard for me to track everything.
> > >
> > > OK well maybe take one more look and then ack if no more issues.
> >
> > Pali, any news on this?
>
> I have not looked at this deeply yet. Please give me some more time.
OK I'd like to apply this series by Monday if no issues to have
enough time for it in Linux next. Does that sound OK to you?
Regards,
Tony
next prev parent reply other threads:[~2016-06-21 11:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-15 10:48 [PATCH 0/2] Drop last two remaining omap3 legacy board files Tony Lindgren
2016-06-15 10:48 ` [PATCH 1/2] ARM: OMAP2+: Drop legacy board file for n900 Tony Lindgren
2016-06-15 10:55 ` Pali Rohár
2016-06-15 11:02 ` Tony Lindgren
2016-06-15 11:49 ` Pali Rohár
2016-06-15 12:05 ` Tony Lindgren
2016-06-21 11:25 ` Tony Lindgren
2016-06-21 11:29 ` Pali Rohár
2016-06-21 11:32 ` Tony Lindgren [this message]
2016-06-22 16:48 ` Pali Rohár
2016-06-22 17:59 ` Pavel Machek
2016-06-22 18:35 ` Ivaylo Dimitrov
2016-06-23 9:16 ` Pavel Machek
2016-06-22 18:34 ` Ivaylo Dimitrov
2016-06-22 19:30 ` Ivaylo Dimitrov
2016-06-23 4:36 ` Tony Lindgren
2016-06-15 13:47 ` Sebastian Reichel
2016-06-15 18:34 ` Aaro Koskinen
2016-06-15 10:48 ` [PATCH 2/2] ARM: OMAP2+: Drop legacy board file for LDP Tony Lindgren
2016-08-05 17:45 ` [PATCH 0/2] Drop last two remaining omap3 legacy board files Sebastian Reichel
2016-08-06 6:26 ` Tony Lindgren
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=20160621113215.GP22406@atomide.com \
--to=tony@atomide.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).