From: Stefan Christ <s.christ@phytec.de>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] ARM: i.MX: bbu-internal: call detect for mmc devices
Date: Thu, 3 Mar 2016 08:30:28 +0100 [thread overview]
Message-ID: <20160303073027.GA2345@lws-christ> (raw)
In-Reply-To: <20160302185422.GT9224@pengutronix.de>
Hi Sascha,
> As it's not a regression or serious bug I applied it to next and not to
> master.
Oh. yes of course. Sry my typing was faster than my thinking. The next branch
is the correct place for it.
Mit freundlichen Grüßen / Kind regards,
Stefan Christ
On Wed, Mar 02, 2016 at 07:54:22PM +0100, Sascha Hauer wrote:
> On Tue, Mar 01, 2016 at 11:56:05AM +0100, Stefan Christ wrote:
> > Hi Sascha,
> >
> > > device_detect_by_name() should be safe to call, I don't think we need
> > > this additional flag. Just always call device_detect_by_name(). We have
> > > to drop the return value checking though.
> > >
> > > In fact we have the following patch in one of our internal customer
> > > trees, this should be suitable for your issue, right?
> >
> > Yep. These two lines of code are sufficent for our use case ;-) Here is my:
> >
> > Tested-by: Stefan Christ <s.christ@phytec.de>
> >
> > Will you apply that patch to master?
>
> As it's not a regression or serious bug I applied it to next and not to
> master.
>
> Sascha
>
> --
> Pengutronix e.K. | |
> Industrial Linux Solutions | http://www.pengutronix.de/ |
> Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
> Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2016-03-03 7:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-25 11:15 Stefan Christ
2016-03-01 9:19 ` Stefan Christ
2016-03-01 9:22 ` Sascha Hauer
2016-03-01 10:56 ` Stefan Christ
2016-03-02 18:54 ` Sascha Hauer
2016-03-03 7:30 ` Stefan Christ [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=20160303073027.GA2345@lws-christ \
--to=s.christ@phytec.de \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.de \
/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