From: Marek Vasut <marek.vasut@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] M28: Fix OB1 bug in GPIO driver
Date: Tue, 22 Nov 2011 23:35:47 +0100 [thread overview]
Message-ID: <201111222335.47838.marek.vasut@gmail.com> (raw)
In-Reply-To: <0691ADAF-BBB6-4B35-A26B-BDAF622ED9D2@delien.nl>
> > Sure, I wrote the code, I know what it does and where you see the
> > problem. It's just to be dead sure. Anyway, I acked it so it means I
> > agree with the change.
>
> Of course. Thanks. Hence my elaboration, to make your checks easier.
Please, ALWAYS Cc the mailing list
next prev parent reply other threads:[~2011-11-22 22:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-22 14:14 [U-Boot] [PATCH] M28: Fix OB1 bug in GPIO driver Robert Deliën
2011-11-22 14:21 ` Marek Vasut
2011-11-22 18:14 ` Marek Vasut
[not found] ` <201111221953.42597.marek.vasut@gmail.com>
[not found] ` <0691ADAF-BBB6-4B35-A26B-BDAF622ED9D2@delien.nl>
2011-11-22 22:35 ` Marek Vasut [this message]
2011-11-22 22:49 ` Marek Vasut
2011-11-25 8:14 ` Stefano Babic
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=201111222335.47838.marek.vasut@gmail.com \
--to=marek.vasut@gmail.com \
--cc=u-boot@lists.denx.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