All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nathan Chancellor <nathan@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: kernel test robot <lkp@intel.com>,
	Saurabh Sengar <ssengar@linux.microsoft.com>,
	robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
	kys@microsoft.com, haiyangz@microsoft.com, wei.liu@kernel.org,
	decui@microsoft.com, daniel.lezcano@linaro.org,
	tglx@linutronix.de, virtualization@lists.linux-foundation.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-hyperv@vger.kernel.org, mikelley@microsoft.com,
	ssengar@microsoft.com, dphadke@linux.microsoft.com,
	llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH v4 6/6] Driver: VMBus: Add device tree support
Date: Wed, 8 Feb 2023 07:39:18 -0700	[thread overview]
Message-ID: <Y+O0FtUkLyvJLSrR@dev-arch.thelio-3990X> (raw)
In-Reply-To: <39350ee9-c899-ba88-2e4e-103f93dcd722@linaro.org>

On Wed, Feb 08, 2023 at 11:25:57AM +0100, Krzysztof Kozlowski wrote:
> On 08/02/2023 09:22, kernel test robot wrote:
> > Hi Saurabh,
> > 
> > Thank you for the patch! Perhaps something to improve:
> > 
> > [auto build test WARNING on next-20230207]
> > [cannot apply to robh/for-next tip/timers/core brgl/gpio/for-next wsa/i2c/for-next linus/master v6.2-rc7 v6.2-rc6 v6.2-rc5 v6.2-rc7]
> > [If your patch is applied to the wrong git tree, kindly drop us a note.
> > And when submitting patch, we suggest to use '--base' as documented in
> > https://git-scm.com/docs/git-format-patch#_base_tree_information]
> > 
> 
> All of your recent patches have build errors. Can you at least build
> test them before sending? It's a unnecessary noise in our mailboxes to
> get non-buildable patches, just to trigger compilation which you can
> easily do by your own. GCC is a free software...

For what it's worth, GCC does not have a warning like this, it just
accepts the incorrect location of the attribute, which has gotten others
in trouble before:

https://lore.kernel.org/CAHk-=wgf+kHeSZbpkZumWcTXUD7ordqTMvPRNL6aQVG1DSBDnQ@mail.gmail.com/

So the patch probably did build clean with GCC but that is one of the
reasons that there is no longer a compiler monopoly for the kernel ;)

Cheers,
Nathan

  reply	other threads:[~2023-02-08 14:39 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-07  7:49 [PATCH v4 0/6] Device tree support for Hyper-V VMBus driver Saurabh Sengar
2023-02-07  7:49 ` [PATCH v4 1/6] drivers/clocksource/hyper-v: non ACPI support in hyperv clock Saurabh Sengar
2023-02-08  1:22   ` Michael Kelley (LINUX)
2023-02-08  1:22     ` Michael Kelley (LINUX) via Virtualization
2023-02-07  7:49 ` [PATCH v4 2/6] Drivers: hv: allow non ACPI compilation for hv_is_hibernation_supported Saurabh Sengar
2023-02-08  1:35   ` Michael Kelley (LINUX)
2023-02-08  1:35     ` Michael Kelley (LINUX) via Virtualization
2023-02-07  7:49 ` [PATCH v4 3/6] Drivers: hv: vmbus: Convert acpi_device to more generic platform_device Saurabh Sengar
2023-02-08  1:50   ` Michael Kelley (LINUX)
2023-02-08  1:50     ` Michael Kelley (LINUX) via Virtualization
2023-02-07  7:49 ` [PATCH v4 4/6] dt-bindings: hypervisor: Rename virtio to hypervisor Saurabh Sengar
2023-02-07 18:39   ` Rob Herring
2023-02-07 18:39     ` Rob Herring
2023-02-08  2:51     ` Saurabh Singh Sengar
2023-02-07  7:49 ` [PATCH v4 5/6] dt-bindings: hypervisor: VMBus Saurabh Sengar
2023-02-07 13:00   ` Rob Herring
2023-02-07 13:00     ` Rob Herring
2023-02-07 18:34     ` Rob Herring
2023-02-07 18:34       ` Rob Herring
2023-02-08  2:50       ` Saurabh Singh Sengar
2023-02-07  7:49 ` [PATCH v4 6/6] Driver: VMBus: Add device tree support Saurabh Sengar
2023-02-08  8:22   ` kernel test robot
2023-02-08  8:22     ` kernel test robot
2023-02-08 10:25     ` Krzysztof Kozlowski
2023-02-08 14:39       ` Nathan Chancellor [this message]
2023-02-08 15:36         ` Krzysztof Kozlowski

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=Y+O0FtUkLyvJLSrR@dev-arch.thelio-3990X \
    --to=nathan@kernel.org \
    --cc=daniel.lezcano@linaro.org \
    --cc=decui@microsoft.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dphadke@linux.microsoft.com \
    --cc=haiyangz@microsoft.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=kys@microsoft.com \
    --cc=linux-hyperv@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=llvm@lists.linux.dev \
    --cc=mikelley@microsoft.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=robh+dt@kernel.org \
    --cc=ssengar@linux.microsoft.com \
    --cc=ssengar@microsoft.com \
    --cc=tglx@linutronix.de \
    --cc=virtualization@lists.linux-foundation.org \
    --cc=wei.liu@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.