All of lore.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Robert Baldyga <r.baldyga@hackerion.com>
Cc: sameo@linux.intel.com, aloisio.almeida@openbossa.org,
	lauro.venancio@openbossa.org, k.opasiak@samsung.com,
	linux-nfc@lists.01.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Marek Szyprowski <m.szyprowski@samsung.com>
Subject: Re: [PATCH] drivers: nfc: update Robert Baldyga's email address
Date: Sat, 29 Aug 2020 15:47:53 +0200	[thread overview]
Message-ID: <CAJKOXPf2eMmF7DQKk3FRC4ba2fgDocRRVdxqak-1S5vY53o=2w@mail.gmail.com> (raw)
In-Reply-To: <1458211793-9823-1-git-send-email-r.baldyga@hackerion.com>

On Thu, 17 Mar 2016 at 12:35, Robert Baldyga <r.baldyga@hackerion.com> wrote:
>
> The r.baldyga@samsung.com email address is no longer valid, so
> this commit replaces it with r.baldyga@hackerion.com which is
> employer-agnostic and thus should be valid for foreseeable future.
>
> Signed-off-by: Robert Baldyga <r.baldyga@hackerion.com>
> ---
>  MAINTAINERS                    | 2 +-
>  drivers/nfc/s3fwrn5/core.c     | 4 ++--
>  drivers/nfc/s3fwrn5/firmware.c | 2 +-
>  drivers/nfc/s3fwrn5/firmware.h | 2 +-
>  drivers/nfc/s3fwrn5/i2c.c      | 4 ++--
>  drivers/nfc/s3fwrn5/nci.c      | 2 +-
>  drivers/nfc/s3fwrn5/nci.h      | 2 +-
>  drivers/nfc/s3fwrn5/s3fwrn5.h  | 2 +-
>  8 files changed, 10 insertions(+), 10 deletions(-)

Hi all,

That's a pretty old patch but it was never applied. Robert, can you
rebase and send a recent version?

Best regards,
Krzysztof

  reply	other threads:[~2020-08-29 13:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-17 10:49 [PATCH] drivers: nfc: update Robert Baldyga's email address Robert Baldyga
2020-08-29 13:47 ` Krzysztof Kozlowski [this message]
2016-03-17 11:12 Robert Baldyga
2016-03-17 14:04 ` Robert Baldyga

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='CAJKOXPf2eMmF7DQKk3FRC4ba2fgDocRRVdxqak-1S5vY53o=2w@mail.gmail.com' \
    --to=krzk@kernel.org \
    --cc=aloisio.almeida@openbossa.org \
    --cc=k.opasiak@samsung.com \
    --cc=lauro.venancio@openbossa.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfc@lists.01.org \
    --cc=m.szyprowski@samsung.com \
    --cc=r.baldyga@hackerion.com \
    --cc=sameo@linux.intel.com \
    /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.