From: Kent Gibson <warthog618@gmail.com>
To: Seamus de Mora <seamusdemora@gmail.com>
Cc: linux-gpio@vger.kernel.org
Subject: Re: [libgpiod] help with GPIOSET_INTERACTIVE
Date: Sat, 30 Dec 2023 14:51:26 +0800 [thread overview]
Message-ID: <20231230065126.GA55355@rigel> (raw)
In-Reply-To: <CAJ8C1XODp8FKbEOqreAUQwKdXw=QgFQxF=KYXEC_zpeCSALa1A@mail.gmail.com>
On Sat, Dec 30, 2023 at 12:49:48AM -0600, Seamus de Mora wrote:
> On Sat, Dec 30, 2023 at 12:43 AM Kent Gibson <warthog618@gmail.com> wrote:
> >
> > On Sat, Dec 30, 2023 at 12:36:37AM -0600, Seamus de Mora wrote:
> > > On Sat, Dec 30, 2023 at 12:29 AM Kent Gibson <warthog618@gmail.com> wrote:
>
> > > But NO - NOT un-burying the hatchet, not un-downvoting what I didn't
> > > downvote in the first place. I clicked a button three times: first was
> > > to up-vote, next was to take the upvote away, 3rd was to restore the
> > > upvote. That is my total recollection - honest.
> >
> > In which case trying to upvote it again now would do nothing.
> > I'll bet you that isn't the case.
>
> There's only one way we're going to find that out. Edit your post &
> remove "the remark". Afterwards, I'll **try** to upvote it. Warning:
> "The system" doesn't allow dual upvotes, so don't try to hold me
> accountable.
Do keep up - I've already done that.
Cheers,
Kent.
next prev parent reply other threads:[~2023-12-30 6:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-29 9:14 help with GPIOSET_INTERACTIVE Seamus de Mora
2023-12-29 15:58 ` [libgpiod] " Kent Gibson
2023-12-30 1:50 ` Seamus de Mora
2023-12-30 2:21 ` Kent Gibson
2023-12-30 4:43 ` Seamus de Mora
2023-12-30 5:03 ` Kent Gibson
2023-12-30 5:45 ` Seamus de Mora
2023-12-30 5:53 ` Kent Gibson
2023-12-30 6:25 ` Seamus de Mora
2023-12-30 6:29 ` Kent Gibson
2023-12-30 6:36 ` Seamus de Mora
2023-12-30 6:43 ` Kent Gibson
2023-12-30 6:49 ` Seamus de Mora
2023-12-30 6:51 ` Kent Gibson [this message]
2023-12-30 6:56 ` Seamus de Mora
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=20231230065126.GA55355@rigel \
--to=warthog618@gmail.com \
--cc=linux-gpio@vger.kernel.org \
--cc=seamusdemora@gmail.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 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).