The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 0/3] spi: bitbang: Clean up the driver
Date: Thu, 6 Jun 2024 13:47:37 +0300	[thread overview]
Message-ID: <ZmGTydYN8ZIVRf8N@smile.fi.intel.com> (raw)
In-Reply-To: <444b20d3-9096-4372-917e-1b997e59cef1@sirena.org.uk>

On Wed, Jun 05, 2024 at 10:21:35PM +0100, Mark Brown wrote:
> On Thu, Jun 06, 2024 at 12:07:14AM +0300, Andy Shevchenko wrote:
> > On Fri, May 17, 2024 at 10:40:19PM +0300, Andy Shevchenko wrote:
> > > A few cleanups to the driver. No functional change intended.
> > > 
> > > Andy Shevchenko (3):
> > >   spi: bitbang: Use typedef for txrx_*() callbacks
> > >   spi: bitbang: Convert unsigned to unsigned int
> > >   spi: bitbang: Replace hard coded number of SPI modes
> > 
> > Hmm... It's not the first time I noticed that the series
> > (despite even appearing in the CI, but then disappearing)
> > left abandoned without clear feedback,
> 
> > Should I do something here?

Okay, it's just an announce is missing.
I found them in the repository. Thanks!

-- 
With Best Regards,
Andy Shevchenko



      reply	other threads:[~2024-06-06 10:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-17 19:40 [PATCH v1 0/3] spi: bitbang: Clean up the driver Andy Shevchenko
2024-05-17 19:40 ` [PATCH v1 1/3] spi: bitbang: Use typedef for txrx_*() callbacks Andy Shevchenko
2024-05-17 19:40 ` [PATCH v1 2/3] spi: bitbang: Convert unsigned to unsigned int Andy Shevchenko
2024-05-17 19:40 ` [PATCH v1 3/3] spi: bitbang: Replace hard coded number of SPI modes Andy Shevchenko
2024-06-05 21:07 ` [PATCH v1 0/3] spi: bitbang: Clean up the driver Andy Shevchenko
2024-06-05 21:21   ` Mark Brown
2024-06-06 10:47     ` 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=ZmGTydYN8ZIVRf8N@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@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