From: Sascha Hauer <s.hauer@pengutronix.de>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: barebox@lists.infradead.org,
Michael Schuhmacher <m.schuhmacher@eckelmann.de>
Subject: Re: [PATCH] e1000/flash: Increased erase timeout
Date: Mon, 12 Nov 2018 08:38:36 +0100 [thread overview]
Message-ID: <20181112073836.6jgeccaq2chbyc5m@pengutronix.de> (raw)
In-Reply-To: <20181109090050.jbxk7ymp4mcjytfi@pengutronix.de>
On Fri, Nov 09, 2018 at 10:00:50AM +0100, Uwe Kleine-König wrote:
> Hallo Sascha,
>
> On Tue, Oct 02, 2018 at 08:55:43AM +0200, Sascha Hauer wrote:
> > On Mon, Oct 01, 2018 at 11:19:07AM +0200, Uwe Kleine-König wrote:
> > > From: Michael Schuhmacher <m.schuhmacher@eckelmann.de>
> > >
> > > Serial flash Adesto AT25DF321A specifies the maximal chip erase time as
> > > 40 seconds. Extend timeout accordingly.
> > >
> > > Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> > > ---
> > > drivers/net/e1000/eeprom.c | 2 +-
> > > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > Applied, thanks
>
> The last patch in next touching drivers/net/e1000/eeprom.c was applied
> in July and I cannot find this patch there. What am I missing?
Nothing. It was me who missed the patch. Applied now, thanks
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:[~2018-11-12 7:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-01 9:19 Uwe Kleine-König
2018-10-02 6:55 ` Sascha Hauer
2018-11-09 9:00 ` Uwe Kleine-König
2018-11-12 7:38 ` Sascha Hauer [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=20181112073836.6jgeccaq2chbyc5m@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=m.schuhmacher@eckelmann.de \
--cc=u.kleine-koenig@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