All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Mauri Sandberg <sandberg@mailfence.com>
Cc: Drew Fustini <drew@beagleboard.org>,
	"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>
Subject: Re: [PATCH] gpio: driver for the NXP 74HC153 chip
Date: Mon, 5 Apr 2021 12:11:56 +0300	[thread overview]
Message-ID: <CAHp75VcTjY5fNsz0J7TSqRC_Eb=5zseH4YdHXgWGB2qX=sWo1g@mail.gmail.com> (raw)
In-Reply-To: <10440931.720197.1617611104977@ichabod.co-bxl>

On Mon, Apr 5, 2021 at 11:25 AM Mauri Sandberg <sandberg@mailfence.com> wrote:
> > From: Andy Shevchenko <andy.shevchenko@gmail.com>
> > On Sun, Apr 4, 2021 at 6:36 PM Drew Fustini <drew@beagleboard.org> wrote:

> I really do hope so. The reason for going for [1] is that it should provide a generic mechanism and
> be manufacturer independent. :)

For some reason I don't see the latest in my mailbox, nevertheless I
have downloaded copy from lore and I'll try to review it sooner than
later.

> > > [1] https://lore.kernel.org/linux-gpio/20210325122832.119147-1-sandberg@mailfence.com/



-- 
With Best Regards,
Andy Shevchenko

      reply	other threads:[~2021-04-05  9:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-23 19:53 [RFC] Driver for the NXP 74HC153 chip Mauri Sandberg
2021-02-23 19:53 ` [PATCH] gpio: driver " Mauri Sandberg
2021-02-23 23:22   ` kernel test robot
2021-02-23 23:22     ` kernel test robot
2021-04-03  9:39     ` Andy Shevchenko
2021-04-03  9:39       ` Andy Shevchenko
2021-02-23 23:47   ` kernel test robot
2021-02-23 23:47     ` kernel test robot
2021-04-02 20:27   ` Drew Fustini
2021-04-04 14:30     ` Mauri Sandberg
2021-04-04 15:35       ` Drew Fustini
2021-04-04 17:17         ` Andy Shevchenko
2021-04-05  8:25           ` Mauri Sandberg
2021-04-05  9:11             ` Andy Shevchenko [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='CAHp75VcTjY5fNsz0J7TSqRC_Eb=5zseH4YdHXgWGB2qX=sWo1g@mail.gmail.com' \
    --to=andy.shevchenko@gmail.com \
    --cc=drew@beagleboard.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=sandberg@mailfence.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.