All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Hawa, Hanna" <hhhawa@amazon.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Wolfram Sang <wsa@kernel.org>,
	Linus Walleij <linus.walleij@linaro.org>,
	<jarkko.nikula@linux.intel.com>,
	<mika.westerberg@linux.intel.com>, <jsd@semihalf.com>,
	<linux-i2c@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<dwmw@amazon.co.uk>, <benh@amazon.com>, <ronenk@amazon.com>,
	<talel@amazon.com>, <jonnyc@amazon.com>, <hanochu@amazon.com>,
	<farbere@amazon.com>, <itamark@amazon.com>
Subject: Re: [PATCH v2 1/1] i2c: designware: set pinctrl recovery information from device pinctrl
Date: Mon, 19 Dec 2022 21:35:37 +0200	[thread overview]
Message-ID: <d60e9cb7-a162-0b49-cd21-33c622ae0e58@amazon.com> (raw)
In-Reply-To: <Y5yE0SsfGrwaB5zA@smile.fi.intel.com>



On 12/16/2022 4:46 PM, Andy Shevchenko wrote:
> Can be simplified with help of Elvis:
> 
>          p = bri->pinctrl ?: dev_pinctrl(dev->parent);

Can't use this, as need to set the bri->pinctrl to dev_pinctrl() in case 
it's not set by the driver.

>> I based my CC/TO on get_maintainer.pl script. Will make sure that Wolfram on
>> CC next time.
> All the same about Linus W., who is pin control subsystem maintainer, and be
> sure the respective mailing lists are also included.

Sure, thanks

Thanks,
Hanna

  reply	other threads:[~2022-12-19 19:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-14 14:27 [PATCH v2 1/1] i2c: designware: set pinctrl recovery information from device pinctrl Hanna Hawa
2022-12-14 16:09 ` Andy Shevchenko
2022-12-15  8:15   ` Hawa, Hanna
2022-12-15 10:27     ` Andy Shevchenko
2022-12-15 14:06       ` Linus Walleij
2022-12-15 14:25         ` Hawa, Hanna
2022-12-15 15:22         ` Andy Shevchenko
2022-12-16 13:50       ` Hawa, Hanna
2022-12-16 14:46         ` Andy Shevchenko
2022-12-19 19:35           ` Hawa, Hanna [this message]
2022-12-20 10:54             ` Andy Shevchenko
2022-12-14 19:14 ` kernel test robot
2022-12-15  0:17 ` kernel test robot

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=d60e9cb7-a162-0b49-cd21-33c622ae0e58@amazon.com \
    --to=hhhawa@amazon.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=benh@amazon.com \
    --cc=dwmw@amazon.co.uk \
    --cc=farbere@amazon.com \
    --cc=hanochu@amazon.com \
    --cc=itamark@amazon.com \
    --cc=jarkko.nikula@linux.intel.com \
    --cc=jonnyc@amazon.com \
    --cc=jsd@semihalf.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    --cc=ronenk@amazon.com \
    --cc=talel@amazon.com \
    --cc=wsa@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.