tools.linux.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: tools@linux.kernel.org
Subject: [b4] some issues with b4 ty $fromname
Date: Thu, 7 May 2020 13:50:54 +0100	[thread overview]
Message-ID: <20200507125054.GA19511@e121166-lin.cambridge.arm.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 365 bytes --]

Hi,

I have just run into a name formatting issue with b4 ty command, email
message generated (as an example) attached ($fromname garbled), I am
sure it is a pretty trivial set-up issue with email encoding and my
python environment, please let me know if that's something easy to fix
and thank you very much for this very useful tool.

Thank you,
Lorenzo

[-- Attachment #2: pali_kernel_org_patch_pci_tegra_fix_reporting_gpio_error_value.thanks --]
[-- Type: text/plain, Size: 890 bytes --]

From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: Thierry Reding <thierry.reding@gmail.com>, Andrew Murray <amurray@thegoodpenguin.co.uk>, Pali Rohár <pali@kernel.org>
Cc: linux-kernel@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>, linux-pci@vger.kernel.org, linux-tegra@vger.kernel.org, Jonathan Hunter <jonathanh@nvidia.com>
In-Reply-To: <20200414102512.27506-1-pali@kernel.org>
References: <20200414102512.27506-1-pali@kernel.org>
Subject: Re: [PATCH] PCI: tegra: Fix reporting GPIO error value
Message-Id: <158885274757.4330.6450290398257549869.b4-ty@arm.com>

On Tue, 14 Apr 2020 12:25:12 +0200, =?UTF-8?q?Pali=20Roh=C3=A1r?= wrote:
> Error code is stored in rp->reset_gpio and not in err variable.

Applied to pci/tegra, thanks!

[1/1] PCI: tegra: Fix reporting GPIO error value
      https://git.kernel.org/lpieralisi/pci/c/3f5491b907

Thanks,
Lorenzo

             reply	other threads:[~2020-05-07 12:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-07 12:50 Lorenzo Pieralisi [this message]
2020-05-07 15:57 ` [tools] [b4] some issues with b4 ty $fromname Konstantin Ryabitsev

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=20200507125054.GA19511@e121166-lin.cambridge.arm.com \
    --to=lorenzo.pieralisi@arm.com \
    --cc=tools@linux.kernel.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).