The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Jiri Prchal <jiri.prchal@aksignal.cz>
Subject: Re: [PATCH v1 0/3] misc: at25: Fix issues brought with FRAM support
Date: Fri, 26 Nov 2021 00:01:26 +0200	[thread overview]
Message-ID: <YaAHtmcTYvEHeaEs@smile.fi.intel.com> (raw)
In-Reply-To: <CAK8P3a3Z5o-hJu1LfeZrD2dps+WTTa6U8vCDoQK2aMAO1WEaBw@mail.gmail.com>

On Thu, Nov 25, 2021 at 10:47:43PM +0100, Arnd Bergmann wrote:
> On Thu, Nov 25, 2021 at 10:27 PM Andy Shevchenko
> <andriy.shevchenko@linux.intel.com> wrote:
> >
> > A few fixes to the AT25 driver that have been brought by FRAM support series.
> >
> > Andy Shevchenko (3):
> >   misc: at25: Make driver OF independent again
> >   misc: at25: Don't copy garbage to the at25->chip in FRAM case
> >   misc: at25: Check proper value of chip length in FRAM case
> 
> Looks all good to me,
> 
> Acked-by: Arnd Bergmann <arnd@arndb.de>

Thank you!
There is also cleanup series if you are interested of looking into...

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2021-11-25 22:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-25 21:27 [PATCH v1 0/3] misc: at25: Fix issues brought with FRAM support Andy Shevchenko
2021-11-25 21:27 ` [PATCH v1 1/3] misc: at25: Make driver OF independent again Andy Shevchenko
2021-11-25 21:27 ` [PATCH v1 2/3] misc: at25: Don't copy garbage to the at25->chip in FRAM case Andy Shevchenko
2021-11-25 21:27 ` [PATCH v1 3/3] misc: at25: Check proper value of chip length " Andy Shevchenko
2021-11-25 21:47 ` [PATCH v1 0/3] misc: at25: Fix issues brought with FRAM support Arnd Bergmann
2021-11-25 22:01   ` Andy Shevchenko [this message]
2021-12-01 14:19 ` Andy Shevchenko

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=YaAHtmcTYvEHeaEs@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=arnd@arndb.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=jiri.prchal@aksignal.cz \
    --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