linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Dipen Patel <dipenp@nvidia.com>,
	"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linus Walleij <linus.walleij@linaro.org>,
	Bartosz Golaszewski <brgl@bgdev.pl>
Subject: Re: [PATCH v1 1/1] gpiolib: cdev: Fix kernel doc for struct line
Date: Mon, 6 Jun 2022 13:05:54 +0300	[thread overview]
Message-ID: <Yp3Rgo4/09/bsvna@smile.fi.intel.com> (raw)
In-Reply-To: <CA+PwDYdf7JEimfYG9ChTHp=Dds_Ljx1Y2KK-H5zfeu52=NxXFA@mail.gmail.com>

On Sun, Jun 05, 2022 at 01:11:54AM +0200, Thierry Reding wrote:
> On Fri, 3 Jun 2022, 19:28 Andy Shevchenko, <
> andriy.shevchenko@linux.intel.com> wrote:
> 
> > On Fri, Jun 03, 2022 at 08:28:09PM +0300, Andy Shevchenko wrote:
> > > On Fri, May 20, 2022 at 10:10:49AM -0700, Dipen Patel wrote:
> > > > Acked-by: Dipen Patel <dipenp@nvidia.com>
> > >
> > > Thanks!
> > >
> > > Bart, this can be applied, I think.
> >
> > Or do you want it in my PR?
> >
> 
> This would need to go in through the HTE tree.
> 
> I can pick it up, but it looks like Linus isn't happy with this yet anyway.

It's merged as far as I can see. Feel free to pick it up, I'll drop it from my
tree.

-- 
With Best Regards,
Andy Shevchenko



  parent reply	other threads:[~2022-06-06 10:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-20 16:47 [PATCH v1 1/1] gpiolib: cdev: Fix kernel doc for struct line Andy Shevchenko
2022-05-20 17:10 ` Dipen Patel
2022-06-03 17:28   ` Andy Shevchenko
2022-06-03 17:28     ` Andy Shevchenko
     [not found]       ` <CA+PwDYdf7JEimfYG9ChTHp=Dds_Ljx1Y2KK-H5zfeu52=NxXFA@mail.gmail.com>
2022-06-06 10:05         ` Andy Shevchenko [this message]
2022-06-08 16:32           ` Dipen Patel
2022-06-09  9:34 ` Bartosz Golaszewski

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=Yp3Rgo4/09/bsvna@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=brgl@bgdev.pl \
    --cc=dipenp@nvidia.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thierry.reding@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).