From: Luis Chamberlain <mcgrof@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Jessica Yu <jeyu@kernel.org>,
Colin Ian King <colin.king@intel.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
patches@lists.linux.dev,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-modules@vger.kernel.org, Aaron Tomlin <atomlin@redhat.com>,
Vimal Agrawal <avimalin@gmail.com>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
Michal Suchanek <msuchanek@suse.de>
Subject: Re: Modules fixes for v5.17-rc5
Date: Thu, 17 Feb 2022 14:20:36 -0800 [thread overview]
Message-ID: <Yg7KNPtnuQkMISx+@bombadil.infradead.org> (raw)
In-Reply-To: <CAHk-=wjR67HKkrPkmHXYET5M0EVwtrfAFC+AvZPd4obpzvXLLw@mail.gmail.com>
On Thu, Feb 17, 2022 at 11:33:23AM -0800, Linus Torvalds wrote:
> On Wed, Feb 16, 2022 at 3:03 PM Luis Chamberlain <mcgrof@kernel.org> wrote:
> >
> > So far only one fix has trickled through for modules. It is part of this
> > pull request. It's a minor build fix for when CONFIG_SYSFS=n. Let me
> > know if there are any issues with this.
>
> The only issue I have is that because you didn't put "[GIT PULL]" in
> the subject line, the pr-tracker-bot doesn't pick up on it, so you're
> not getting a "this has been merged" confirmation email.
>
> My own search criteria for pull requests aren't as strict, so I saw it
> in my pending queue. But then I spent time wondering why I didn't see
> the pr-tracker-bot response when I pushed out, so I actually prefer
> for people to use the stricter rules that the pr-tracker-bot looks
> at...
Got it, consider this a resolved matter for the future.
Thanks for the feedback.
Luis
prev parent reply other threads:[~2022-02-17 22:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-16 23:03 Luis Chamberlain
2022-02-17 19:33 ` Linus Torvalds
2022-02-17 22:20 ` Luis Chamberlain [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=Yg7KNPtnuQkMISx+@bombadil.infradead.org \
--to=mcgrof@kernel.org \
--cc=atomlin@redhat.com \
--cc=avimalin@gmail.com \
--cc=christophe.leroy@csgroup.eu \
--cc=colin.king@intel.com \
--cc=dmitry.torokhov@gmail.com \
--cc=jeyu@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=msuchanek@suse.de \
--cc=patches@lists.linux.dev \
--cc=torvalds@linux-foundation.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®