From: Simon Glass <sjg@chromium.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] patman: make run results better visible
Date: Thu, 4 Sep 2014 16:38:20 -0600 [thread overview]
Message-ID: <CAPnjgZ1Ksy_TKeQDqTz6RM_=VhMkis2QgzonR71Gu7rEhDz2pA@mail.gmail.com> (raw)
In-Reply-To: <CAD=FV=VJ4=c5jPET+zvKsZK9C_whGjWscVJ3s5PFqf_kteHXLw@mail.gmail.com>
On 4 September 2014 12:57, Doug Anderson <dianders@chromium.org> wrote:
> Vadim,
>
> On Thu, Sep 4, 2014 at 10:45 AM, Vadim Bendebury <vbendeb@chromium.org>
> wrote:
> > For an occasional user of patman some failures are not obvious: for
> > instance when checkpatch reports warnings, the dry run still reports
> > that the email would be sent. If it is not dry run, the warnings are
> > shown on the screen, but it is not clear that the email was not sent.
> >
> > Add some code to report failure to send email explicitly.
> >
> > Tested by running the script on a patch with style violations,
> > observed error messages in the script output.
> >
> > Signed-off-by: Vadim Bendebury <vbendeb@chromium.org>
> > ---
> >
> > Changes in v2:
> > - modified the error message for accuracy
> >
> > tools/patman/patman.py | 7 ++++++-
> > 1 file changed, 6 insertions(+), 1 deletion(-)
>
> Reviewed-by: Doug Anderson <dianders@chromium.org>
>
Acked-by: Simon Glass <sjg@chromium.org>
next prev parent reply other threads:[~2014-09-04 22:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-03 19:16 [U-Boot] [PATCH] patman: make run results better visible Vadim Bendebury
2014-09-03 22:14 ` Doug Anderson
2014-09-03 23:00 ` Vadim Bendebury
2014-09-04 4:25 ` Doug Anderson
2014-09-04 17:45 ` [U-Boot] [PATCH v2] " Vadim Bendebury
2014-09-04 18:57 ` Doug Anderson
2014-09-04 22:38 ` Simon Glass [this message]
2014-09-10 18:55 ` Simon Glass
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='CAPnjgZ1Ksy_TKeQDqTz6RM_=VhMkis2QgzonR71Gu7rEhDz2pA@mail.gmail.com' \
--to=sjg@chromium.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.