From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Lee Jones <lee@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 0/6] mfd: kempld: A few cleanups
Date: Thu, 11 Apr 2024 15:12:28 +0300 [thread overview]
Message-ID: <ZhfTrHrdq58LrZDs@smile.fi.intel.com> (raw)
In-Reply-To: <20240411105607.GE1980182@google.com>
On Thu, Apr 11, 2024 at 11:56:07AM +0100, Lee Jones wrote:
> On Thu, 11 Apr 2024, Andy Shevchenko wrote:
> > On Thu, Apr 11, 2024 at 10:29:28AM +0100, Lee Jones wrote:
> > > On Tue, 02 Apr 2024, Andy Shevchenko wrote:
> > > > On Fri, Feb 23, 2024 at 09:49:49PM +0200, Andy Shevchenko wrote:
> > > > > Just a set of ad-hoc cleanups. No functional change intended.
> > > >
> > > > Any comments?
> > > >
> > > > (I assume the 6+ weeks in the mailing list is enough for all kind of CIs
> > > > to complain. But they hadn't AFAICS.)
> > >
> > > Not sure why these were dropped from my queue.
> > >
> > > Likely another Mutt "feature".
> >
> > Hmm... Using mutt as well, but probably not in advanced way.
>
> I use:
>
> I flag-message toggle a message's 'important' flag
>
> ... to mark messages as requiring review.
I don't (yet?).
> Sometimes Mutt drops them for seemingly no reason. It's also not
> uncommon for me to fetch new mail or open Mutt to find 300 unread mails
> which I've already parsed. When that happens, all of the mails that
> I've previously flagged have also been (not so) helpfully unflagged!
>
> It's just something that I've grown accustomed to.
Okay, thanks for sharing your experience.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2024-04-11 12:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 19:49 [PATCH v1 0/6] mfd: kempld: A few cleanups Andy Shevchenko
2024-02-23 19:49 ` [PATCH v1 1/6] mfd: kempld: Replace ACPI code with agnostic one Andy Shevchenko
2024-02-23 19:49 ` [PATCH v1 2/6] mfd: kempld: Use device core to create driver-specific device attributes Andy Shevchenko
2024-02-23 19:49 ` [PATCH v1 3/6] mfd: kempld: Simplify device registration Andy Shevchenko
2024-02-23 19:49 ` [PATCH v1 4/6] mfd: kempld: Use PLATFORM_DEVID_NONE instead of -1 Andy Shevchenko
2024-02-23 19:49 ` [PATCH v1 5/6] mfd: kempld: Drop duplicate NULL check in ->exit() Andy Shevchenko
2024-02-23 19:49 ` [PATCH v1 6/6] mfd: kempld: Remove dead code Andy Shevchenko
2024-04-02 15:31 ` [PATCH v1 0/6] mfd: kempld: A few cleanups Andy Shevchenko
2024-04-11 9:29 ` Lee Jones
2024-04-11 10:20 ` Andy Shevchenko
2024-04-11 10:56 ` Lee Jones
2024-04-11 12:12 ` Andy Shevchenko [this message]
2024-04-11 10:10 ` Lee Jones
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=ZhfTrHrdq58LrZDs@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=lee@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 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.