From: "Enrico Weigelt, metux IT consult" <lkml@metux.net>
To: "Enrico Weigelt, metux IT consult" <info@metux.net>,
linux-kernel@vger.kernel.org
Cc: gregkh@linuxfoundation.org, linux-serial@vger.kernel.org
Subject: Re: [PATCH] drivers: tty: serial: amba-pl011: use generic ops request/release port
Date: Mon, 29 Jul 2019 16:46:39 +0200 [thread overview]
Message-ID: <e831001d-0f9c-800c-94d5-7e767fa4fc5a@metux.net> (raw)
In-Reply-To: <1564411445-26933-1-git-send-email-info@metux.net>
On 29.07.19 16:44, Enrico Weigelt, metux IT consult wrote:
> From: Enrico Weigelt <info@metux.net>
>
> Reduce boilerplate by using generic implementation of the trivial
> request_port/release_port operations. For that to work, we have to
> set the mapsize field accordingly.
Shit! Forget it. Somehow cherry-picked the wrong commit ID and forgot
to check before posting. That wasn't supposed to be sent out yet.
Sorry for the noise.
--mtx
--
Enrico Weigelt, metux IT consult
Free software and Linux embedded engineering
info@metux.net -- +49-151-27565287
prev parent reply other threads:[~2019-07-29 14:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-29 14:44 Enrico Weigelt, metux IT consult
2019-07-29 14:46 ` Enrico Weigelt, metux IT consult [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=e831001d-0f9c-800c-94d5-7e767fa4fc5a@metux.net \
--to=lkml@metux.net \
--cc=gregkh@linuxfoundation.org \
--cc=info@metux.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.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
all inboxes | Powered by JetHome®