From: "Enrico Weigelt, metux IT consult" <lkml@metux.net>
To: Bartosz Golaszewski <bgolaszewski@baylibre.com>,
"Enrico Weigelt, metux IT consult" <info@metux.net>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
linux-gpio <linux-gpio@vger.kernel.org>
Subject: Re: [PATCH v3] drivers: gpio: put virtual gpio device into their own submenu
Date: Tue, 8 Dec 2020 10:40:55 +0100 [thread overview]
Message-ID: <c839fa75-80ee-31e6-2ccb-87155281e1d4@metux.net> (raw)
In-Reply-To: <CAMpxmJWinRPUrmpcqsLaE62uAQpZ3Cb1ys3s7oHmeKM6rUUqQg@mail.gmail.com>
On 08.12.20 10:15, Bartosz Golaszewski wrote:
> On Mon, Dec 7, 2020 at 9:38 PM Enrico Weigelt, metux IT consult
> <info@metux.net> wrote:
>>
>> Since we already have a few virtual GPIO drivers, and more to come,
>> this category deserves its own submenu.
>>
>> changes v2: fixed menu title (replaced "devices" by "drivers")
>> changes v3: added patch changelog
>
> This should be below the --- under all tags because we don't want this
> in the actual log that goes into git.
Sorry, wasn't aware of that. Does git-am automatically cut it off ?
--mtx
--
---
Hinweis: unverschlüsselte E-Mails können leicht abgehört und manipuliert
werden ! Für eine vertrauliche Kommunikation senden Sie bitte ihren
GPG/PGP-Schlüssel zu.
---
Enrico Weigelt, metux IT consult
Free software and Linux embedded engineering
info@metux.net -- +49-151-27565287
next prev parent reply other threads:[~2020-12-08 9:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-07 20:38 Enrico Weigelt, metux IT consult
2020-12-08 9:15 ` Bartosz Golaszewski
2020-12-08 9:40 ` Enrico Weigelt, metux IT consult [this message]
2020-12-08 9:50 ` Bartosz Golaszewski
-- strict thread matches above, loose matches on Subject: below --
2020-12-07 20:38 Enrico Weigelt, metux IT consult
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=c839fa75-80ee-31e6-2ccb-87155281e1d4@metux.net \
--to=lkml@metux.net \
--cc=bgolaszewski@baylibre.com \
--cc=info@metux.net \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@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®