mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Naresh Solanki <naresh.solanki@9elements.com>
To: Mark Brown <broonie@kernel.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] regulator: max5970: Rename driver and remove wildcard
Date: Thu, 27 Apr 2023 16:58:05 +0530	[thread overview]
Message-ID: <cda57ab9-bc08-f756-f13f-aeff71d2aaa6@9elements.com> (raw)
In-Reply-To: <1e1383c5-26ae-4874-8873-cb3b8d1a04f0@sirena.org.uk>

Hi Mark,

On 27-04-2023 04:44 pm, Mark Brown wrote:
> On Thu, Apr 27, 2023 at 12:22:54PM +0200, Naresh Solanki wrote:
>> The previous version of this driver included wildcards in file names and
>> descriptions. This patch renames the driver to only support MAX5970 and
>> MAX5978, which are the only chips that the driver actually supports.
> 
> You've not copied me on the rest of the series so I don't know what's
> going on with dependencies.  When sending a patch series it is important
> to ensure that all the various maintainers understand what the
> relationship between the patches as the expecation is that there will be
> interdependencies.  Either copy everyone on the whole series or at least
> copy them on the cover letter and explain what's going on.  If there are
> no strong interdependencies then it's generally simplest to just send
> the patches separately to avoid any possible confusion.
Thanks for letting me know.
Will resend with maintainers included in every patch.

Regards,
Naresh

  reply	other threads:[~2023-04-27 11:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-27 10:22 [PATCH 1/2] mfd: " Naresh Solanki
2023-04-27 10:22 ` [PATCH 2/2] regulator: " Naresh Solanki
2023-04-27 11:14   ` Mark Brown
2023-04-27 11:28     ` Naresh Solanki [this message]
2023-04-27 11:30 [PATCH 1/2] mfd: " Naresh Solanki
2023-04-27 11:30 ` [PATCH 2/2] regulator: " Naresh Solanki
2023-04-30 15:58   ` Mark Brown
2023-06-02  8:15   ` Lee Jones

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=cda57ab9-bc08-f756-f13f-aeff71d2aaa6@9elements.com \
    --to=naresh.solanki@9elements.com \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --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

all inboxes | Powered by JetHome®