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: <wsa@kernel.org>, <linus.walleij@linaro.org>,
	<linux-i2c@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<linux-gpio@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 v3 1/1] i2c: Set pinctrl recovery info to device pinctrl
Date: Tue, 20 Dec 2022 19:07:51 +0200	[thread overview]
Message-ID: <4344f575-65f5-2fde-e2d5-3dd5a18d13cb@amazon.com> (raw)
In-Reply-To: <Y6GUKf5TCumM1Swy@smile.fi.intel.com>



On 12/20/2022 12:53 PM, Andy Shevchenko wrote:
>> Signed-off-by: Hanna Hawa <hhhawa@amazon.com>
> > The same comment about changelog. Place it in the correct position.

Will be fixed.

> 
>> Change Log v2->v3:
>> - Add API to get the device pinctrl
>> - Make the i2c init recovery to get the device pins
>>
>> Change Log v1->v2:
>> - set the rinfo->pinctrl to dev->pins->p instead calling
>>    devm_pinctrl_get()
>> ---
> 
>>   include/linux/pinctrl/devinfo.h | 11 +++++++++++
> 
> This should be a separate patch.

Sure, will move and create cover letter with the change log.

> 
> ...
> 
>> +static inline struct pinctrl *dev_pinctrl(struct device *dev)
>> +{
>> +     return dev->pins && dev->pins->p ? dev->pins->p : NULL;
> 
> GCC supports Elvis, you can use it to simplify the above.

How you suggest to simplify this?
I can use 'return dev->pins ? dev->pins->p ?: dev->pins->p : NULL;'

> 
>> +}
> 
> --
> With Best Regards,
> Andy Shevchenko
> 
> 

  reply	other threads:[~2022-12-20 17:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-19 19:32 [PATCH v3 1/1] i2c: Set pinctrl recovery info to device pinctrl Hanna Hawa
2022-12-20  6:23 ` kernel test robot
2022-12-20  6:43 ` kernel test robot
2022-12-20  8:43 ` Hawa, Hanna
2022-12-20 10:53 ` Andy Shevchenko
2022-12-20 17:07   ` Hawa, Hanna [this message]
2022-12-20 19:18     ` Andy Shevchenko
2022-12-20 19:32       ` Hawa, Hanna
2022-12-21 16:59         ` Andy Shevchenko
2022-12-20 10:57 ` Andy Shevchenko
2022-12-20 17:08   ` Hawa, Hanna
2022-12-20 13:03 ` 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=4344f575-65f5-2fde-e2d5-3dd5a18d13cb@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=jonnyc@amazon.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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.