From: Andy Shevchenko <andy@kernel.org>
To: Philipp Hortmann <philipp.g.hortmann@gmail.com>
Cc: Yu Jiaoliang <yujiaoliang@vivo.com>,
Hans de Goede <hdegoede@redhat.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Hans Verkuil <hverkuil-cisco@xs4all.nl>,
Kieran Bingham <kieran.bingham@ideasonboard.com>,
Jonathan Bergh <bergh.jonathan@gmail.com>,
Kate Hsuan <hpa@redhat.com>,
Dipendra Khadka <kdipendra88@gmail.com>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-staging@lists.linux.dev, opensource.kernel@vivo.com
Subject: Re: [PATCH v1] media: atomisp: Fix typos in comment
Date: Mon, 23 Sep 2024 11:32:10 +0300 [thread overview]
Message-ID: <ZvEniiAeBjZKkyjd@smile.fi.intel.com> (raw)
In-Reply-To: <ZvEmUWD75Huv7vwy@smile.fi.intel.com>
On Mon, Sep 23, 2024 at 11:26:57AM +0300, Andy Shevchenko wrote:
> On Mon, Sep 23, 2024 at 07:57:00AM +0200, Philipp Hortmann wrote:
> > On 9/23/24 5:30 AM, Yu Jiaoliang wrote:
...
> > I cannot apply your patch:
>
> > Fetch URL:
> > git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git
>
> You used the wrong branch.
> AtomISP has it's own tree/branch for development:
> https://git.kernel.org/pub/scm/linux/kernel/git/hansg/linux.git/log/?h=media-atomisp
Talking about this, Yu may use --base next time, so everyone, including CIs,
will know exactly what should be used as a base.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2024-09-23 8:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-23 3:30 [PATCH v1] media: atomisp: Fix typos in comment Yu Jiaoliang
2024-09-23 5:44 ` Philipp Hortmann
2024-09-23 8:28 ` Andy Shevchenko
2024-09-23 5:57 ` Philipp Hortmann
2024-09-23 8:26 ` Andy Shevchenko
2024-09-23 8:32 ` Andy Shevchenko [this message]
2024-09-23 8:30 ` Andy Shevchenko
2024-11-04 11:11 ` Hans de Goede
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=ZvEniiAeBjZKkyjd@smile.fi.intel.com \
--to=andy@kernel.org \
--cc=bergh.jonathan@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=hpa@redhat.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=kdipendra88@gmail.com \
--cc=kieran.bingham@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=mchehab@kernel.org \
--cc=opensource.kernel@vivo.com \
--cc=philipp.g.hortmann@gmail.com \
--cc=sakari.ailus@linux.intel.com \
--cc=yujiaoliang@vivo.com \
/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