public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Damian Muszynski <damian.muszynski@intel.com>,
	linux-kernel@vger.kernel.org,
	Rasmus Villemoes <linux@rasmusvillemoes.dk>,
	Herbert Xu <herbert@gondor.apana.org.au>
Subject: Re: [PATCH v1 1/1] units: Add missing header
Date: Wed, 29 Nov 2023 12:19:21 +0200	[thread overview]
Message-ID: <ZWcQKYlCXUIAGnlK@smile.fi.intel.com> (raw)
In-Reply-To: <20231128180957.ac5caa884abb2b5f00ca47c4@linux-foundation.org>

On Tue, Nov 28, 2023 at 06:09:57PM -0800, Andrew Morton wrote:
> On Tue, 28 Nov 2023 19:44:03 +0200 Andy Shevchenko <andriy.shevchenko@linux.intel.com> wrote:
> 
> > BITS_PER_BYTE is defined in bits.h.
> > 
> > Fixes: e8eed5f7366f ("units: Add BYTES_PER_*BIT")
> 
> This is post-6.6, so the fix should go into this -rc whatever happens, but...
> 
> It would be rather nice to know the effects of this change please.  Did
> some build break?

Not of my knowledge. Fixes tag here to make sure people won't forget that
headers are special and we need a bit stricter rules on how we add a new
stuff (which will require another header) or remove an old one (which may
give a stale inclusion).

-- 
With Best Regards,
Andy Shevchenko



      reply	other threads:[~2023-11-29 10:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-28 17:44 [PATCH v1 1/1] units: Add missing header Andy Shevchenko
2023-11-28 22:25 ` Randy Dunlap
2023-11-29  2:09 ` Andrew Morton
2023-11-29 10:19   ` Andy Shevchenko [this message]

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=ZWcQKYlCXUIAGnlK@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=damian.muszynski@intel.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@rasmusvillemoes.dk \
    /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